Google has added a direct publishing bridge between Gemini and Google Sites. Interactive apps created in the Gemini app can now be exported into a new private Sites draft, where they remain interactive and can be customized before publication.
The feature removes the awkward step of copying code or rebuilding a Gemini prototype in a separate web tool. It also creates a new responsibility: the exported draft inherits Google Sites and Google Drive rules, so creators still need to review who can edit the draft, who can view the published site and whether any embedded files are shared with the intended audience.
What changed
Google announced the launch on October 19, 2026. From an interactive app in Gemini, the user chooses Export and then Google Sites. Google opens a new Sites draft rather than publishing immediately. The app is placed in that draft as an interactive experience, and the creator can add pages, text, images and other Sites elements before choosing Publish.
That distinction matters. Export is a handoff into an editable site project, not a one-click public release. The draft begins private, while publishing and sharing remain separate decisions controlled in Google Sites.
How the export workflow works
The workflow is short, but it helps to understand what each stage creates:
- Build or open an interactive app in Gemini Canvas. Test the app’s controls, sample data and mobile layout before exporting.
- Open the app’s export menu and choose Google Sites. Google creates a new, private Sites draft.
- Review the imported app in Sites. Add a title, explanatory copy, navigation and any supporting material the audience will need.
- Open the site’s sharing settings and decide who can edit the draft. Keep draft access narrower than published-view access.
- Use Preview to test desktop, tablet and phone layouts. Check interactive controls again after the handoff.
- Choose Publish, select the web address and set who can view the published version.
Google says the feature is available now on the web, Android and iOS for both Rapid Release and Scheduled Release domains. The command may appear in a different place depending on the Gemini surface and screen size, but the result is the same: a separate Sites draft that can be edited and governed like another Google Site.
Who gets it
The export is available to Google Workspace customers, Workspace Individual subscribers and personal Google Account users who already have access to the Gemini app. It does not create a separate Gemini entitlement, so an account without Gemini access will not gain the feature simply because Sites is available.
For work and school accounts, Google Sites must be turned on and the user must be allowed to create and edit sites. Google introduced no new administrator switch specifically for Gemini-to-Sites export. Existing Sites and Drive policies continue to decide what users can create, share and publish.
What administrators should verify
- Google Sites is enabled for the organizational unit or group that needs the workflow.
- Users are permitted to create and edit Sites, not only view published sites.
- External sharing and publishing rules match the organization’s intended audience.
- Drive sharing rules allow required embedded files to be seen without exposing unrelated material.
- A review owner is defined for public, customer-facing or student-facing apps.
Private draft does not mean risk-free
A new export starts as a private draft, which reduces accidental exposure, but privacy can change as collaborators are added. Google Sites maintains separate access controls for the draft and the published site. A creator can restrict editing to named people while allowing a broader group to view the published version.
Editors may be able to publish, change permissions or add people unless the owner disables those capabilities in Sites settings. Teams handling customer, employee or student information should review editor privileges before inviting collaborators, especially when the same site will eventually be visible outside the organization.
The Gemini app has its own sharing model for Canvas apps. Google’s help documentation warns that a public Gemini app link can allow anyone with the link to view and interact with data associated with that app. Exporting to Sites avoids treating that public Gemini link as the final delivery mechanism, but it does not erase the need to inspect what the app stores, generates or requests from visitors.
Embedded Drive content needs separate permission checks
A Sites page can display content from Drive, including documents, presentations, spreadsheets and forms. Publishing the site does not automatically grant access to every embedded file. If the file remains restricted, a visitor may see an access request or an empty embed even though the surrounding page loads correctly.
Before publishing, open the site from a private browser window or a test account that represents the intended audience. Test the interactive Gemini app and every Drive embed. If a file must be shared more broadly, change that file’s permissions deliberately rather than opening an entire folder.
A safer publishing checklist
- Remove real customer, employee, financial, health or student data from prototypes and sample records.
- Confirm the exported app behaves correctly after it is placed in Sites, including on a phone-sized preview.
- Set draft editors first, then configure the published audience separately.
- Disable editors’ ability to publish or change permissions when a single owner should control release.
- Verify each embedded Drive item with a test account that has no extra internal access.
- Add a visible owner, update date and contact path for apps that support an ongoing process.
- Re-test after major Gemini edits instead of assuming the Sites version updated automatically.
Where the feature is genuinely useful
The best uses are lightweight experiences that benefit from a surrounding page. A teacher could create a practice quiz and place instructions, a rubric and class resources around it. A product team could turn a rough calculator or decision tool into an internal launch page. A small business could embed a guided intake prototype beside service details and contact information.
The direct export is less compelling when the app needs authentication, a governed database, payment processing, audit logs or a formal deployment pipeline. Google Sites remains a no-code publishing surface, not a substitute for a production application platform. Treat the workflow as a fast path for explainers, prototypes, classroom activities and controlled internal tools.
What to check before relying on it
Google’s announcement says the exported app is interactive and ready to customize, but it does not promise that every Canvas capability, connected service or stateful behavior will work in every Sites context. Test the exact app rather than assuming parity. Pay particular attention to mobile interaction, sign-in prompts, data persistence and features that call Gemini.
Also keep the source workflow clear. The Sites draft is a new asset, so later edits in the original Gemini conversation should not be assumed to appear automatically on the published site. Record which Gemini app produced the site and who owns the final Sites version.
Practical hardware note
The workflow runs in the browser and does not require a high-end computer. For teams choosing a low-maintenance device for Sites editing, you can compare current Chromebook Plus laptops on Amazon. Check the exact model, memory, storage, seller and return policy before buying; listings and configurations change frequently.
Affiliate disclosure: ReaderSpice may earn a commission from qualifying purchases made through Amazon links, at no additional cost to you.
Bottom line
Gemini-to-Sites export turns an interactive AI prototype into a shareable web project without a manual rebuild. The strongest part of the launch is the private-draft handoff: creators get a chance to add context, test layouts and set permissions before anything becomes public.
The safest approach is to treat export, draft sharing and publication as three separate checkpoints. Verify the app, restrict editors, test embedded files with a clean account and only then publish to the intended audience. That small amount of governance is what separates a useful no-code shortcut from an accidental access problem.
Sources
Google Workspace Updates: Publish interactive apps from the Gemini app to Google Sites
Gemini Apps Help: Create docs, apps and more with Canvas
Google Sites Help: Invite others to edit your site
Google Sites Help: Add Google files, videos and website content