Saves time and development costs by instantly turning AI prototypes into shareable internal tools or customer-facing pages.
What Is the Gemini Google Sites Export?
Google added a one-click export that moves an interactive app built in the Gemini app into a new, private Google Sites draft, fully interactive and ready to customize, according to the official Workspace Updates announcement.
You trigger it from Export > Google Sites on your interactive app, and from there you can add more content, publish the site, and share it like any other Google Site.
The feature is available now on web, Android, and iOS, which matters because the prototypes people build in the Gemini app rarely stay on one device.
The announcement’s framing is blunt about the value: no code to copy and nothing to rebuild.
The prototype-to-shareable-page step just became a menu item.
How Does the Gemini Google Sites Export Work?
Select Export > Google Sites on the interactive app inside the Gemini app, and the app opens directly in Google Sites as a new draft, ready to edit and publish.
The draft is private at creation, so the tool lands in your Sites account rather than on a public page, and you control the moment it goes live.
Publishing and sharing then follow the standard Google Sites flow, which the Workspace Learning Center documents step by step from the Publish button to the web address settings.
Once published, the site behaves like any other Google Site you manage, and Google’s Sites help documentation covers the editing and publishing controls end to end.
The Learning Center’s publish flow walks through the web address settings, viewer permissions, and the Publish button, and none of those steps change for an exported draft.
The draft also lives in Sites from the moment it lands, so hosting and access ride on the infrastructure your organization already runs rather than a new service to evaluate.
Mechanically it is one export action followed by the Sites workflow your team already knows.
How Is Exporting to Google Sites Different From Rebuilding by Hand?
The old path from prototype to shared page meant recreating the layout, repasting the logic, and re-testing the interactions in a separate tool.
The export removes both steps by carrying the app over fully interactive, which the announcement states directly.
The export covers the app itself, and the surrounding page content stays yours to write, which the announcement signals when it calls the draft ready to customize.
What it does not do is replace custom development: the destination is Google Sites, with the structure and limits Sites already has.
For shareable internal tools the export wins on speed, and for anything beyond the Sites format you are still building.
A coaching business builds a pricing calculator in the Gemini app on a Thursday, and it sits in the chat window where only the person who prompted it can touch it.
Friday’s client call needs that calculator in the client’s hands, and the old answer was screenshots or a weekend with a page builder.
One export later it is a private draft on the business’s own Sites account, editable and publishable before the call starts, which is the entire distance between a demo and a deliverable.
Who Can Use the Gemini Google Sites Export?
Availability covers Google Workspace customers, Workspace Individual subscribers, and personal Google accounts with access to the Gemini app.
Educators get a specific callout in Google’s own framing: the announcement names teams, customers, and students as the sharing audience for the exported apps.
Admins get no new control to configure: the gate is whether Google Sites is turned on for the user and whether that user is allowed to create and edit sites.
Sites created this way follow the organization’s existing Google Sites and Google Drive policies, so governance inherits rather than resets.
If Sites is already enabled in your tenant, your users can do this today without filing a ticket.
Does the Gemini Google Sites Export Change Anything for Your Business This Quarter?
Inventory the interactive things your team built in the Gemini app and never shipped, because each one is now one click away from a private draft.
Internal calculators, client-facing quote tools, and training widgets are the obvious first candidates, especially for teams already paying for Workspace.
Before you publish anything customer-facing, run it through your existing Sites and Drive sharing rules, because the export inherits them rather than adding new ones.
For a wider view of where this fits among your options, compare it against the page builders we rate for small business sites before you standardize on one path.
Treat the first export as a pilot: ship one internal tool, watch whether teammates actually use it, and let that usage decide whether the workflow becomes standard practice.
The change is real but scoped: faster shipping of Gemini-built tools inside Google Sites, nothing more.
Source: workspaceupdates.googleblog.com
