Gemini apps can now be exported to Google Sites and shared as web pages

From chat to web page

Google has added a way to take an interactive app you made in Gemini and move it onto a website. As SammyGuru reported, the export goes to Google Sites, Google's tool for building simple web pages, and it skips the usual chores of copying code or rebuilding the project somewhere else.

The kinds of things in scope are practical ones: a calculator, a quiz or a dashboard. A dashboard is a single screen of charts and figures that shows how something is going. Google's own demonstration was a team performance dashboard with charts, progress indicators and other interactive parts.

The problem it solves is plain. Sharing something you made in Gemini used to mean pointing people to your conversation and hoping they found the right prompt. A website gives them something they can simply open and use.

How the export works

The steps are short. Inside Gemini, you pick Export, then Google Sites. Google then creates a draft page with your app already embedded, meaning placed inside the page so it runs there. The draft starts out private, so nothing is public yet.

From there you work in Google Sites like any other page. You can add headings and supporting text, and you can pull in files from Google Drive. That matters because an app alone is often not enough. A quiz might need instructions, and a dashboard might need a short note on what the numbers mean.

Only when you are happy with the page do you publish it. That draft-first order gives you a natural moment to look things over before anyone else sees it.

Who can use it

The feature is not locked to people who pay for a business plan. Google says it is open to eligible Google Workspace users, Workspace Individual users and people with a personal Google account. It works on the web, Android and iOS.

For organizations, there is no new admin setting to switch on. What a person needs is permission to create and edit Google Sites. If that permission already exists in your account, the export should be available to you.

The source names two obvious users. One is a teacher who builds a quiz for students. The other is a team member who wants to share a dashboard with colleagues. Both gain the same thing: the audience does not need to know anything about Gemini to use the result.

Who sees the finished page

Publishing is where the care comes in. According to the report, the sharing settings on the site decide who can reach the finished page. In other words, access is handled by Google Sites, not by Gemini.

That is a familiar system for many people, but it is worth using deliberately. A few checks make sense before you publish:

• What does the app touch? If it displays numbers or names from your own work, make sure you are comfortable showing them to the intended audience.
• Who can open the link? Review the site's sharing settings rather than assuming they match what you want.
• Can you remove it later? The source does not cover this, so look at how Google Sites handles unpublishing before you rely on it.

The source also does not mention cost or the limits of what the embedded apps can do. For now, treat a first published version as a prototype, not a system customers depend on.

What this changes

The change is modest but real. The distance between a good idea and something shareable gets shorter. Students putting together a portfolio, small business owners testing a customer tool, and creators trying out an idea for an audience can all get a working page without learning how to host a site.

It also nudges Gemini from a place where you chat into a place where you build things that live elsewhere. Whether people actually use it that way will depend on how reliable the exported apps are and how easy publishing control feels in practice.