01The flow
New here? Start at the pillar page for the full picture.
Get complete files out of Gemini: ask it to emit each one in full rather than describing changes. From there it is the now-what guide: repository, signup, live. If Gemini worked inside Google AI Studio, export the project; a coding agent can reorganise the files into a repository shape that deploys on a plain push.
02Two Google-specific checks
03Two Google-specific checks
04Two Google-specific checks
Client-side Google services (Maps embeds, Fonts, Analytics) keep working after the move: they are references in the page, not hosting. What does not carry is any suggestion to host on a Google platform: that was advice, not a dependency. Second check: if the output is a framework project rather than plain HTML, have your agent run the build and commit the built output, per the publishing flow.
05What stays true afterwards
The site answers to you. The repository is in your account, the deploys happen on push, the domain is yours, and switching builders later changes nothing on the hosting side. The host serves the files; it has no opinion on which AI wrote them, today or next year.
06Frequently Asked Questions
Does Gemini connect to LoomWeb directly?
No integration needed. Git is the integration, and any tool that can push to GitHub can deploy here.
Gemini gave me React code. Does that deploy?
If it builds to static files, yes: run the build, commit the output, deploy. Plain client-side React often serves as-is; test on the preview address.
What if I switch to a different builder later?
The repository accepts files from anyone. Hosting never locks you to the tool that started the site.
Build it with your AI. Host it here.
Deploys on every push, from Australia, with nothing to maintain.