Export a Gamma site to HTML: embeds, motion and hosting

01

Choose a public Gamma website URL

Open the published address in a browser where you are not signed in. If it asks for workspace access, publish the intended page first. FNJ reads the public response; it does not log into Gamma or retrieve private presentation data.

Capture a single page first and compare its card order, headings, links and images with the published version. For a multipage website, use site scope and check the report against the pages you expect visitors to reach.

02

Review cards, embeds and transitions

Check the exported page at narrow and wide widths. Text wrapping and card height matter more than one desktop screenshot: a layout that appears correct at one width may hide content on a phone.

Click embedded video, document and presentation controls. Some actions and transitions may still need Gamma scripts or a third-party service. Decide which to keep as external integrations and which to replace with your own HTML, CSS or JavaScript.

03

Turn the snapshot into a maintainable site

Edit the downloaded files or use your connected FNJ agent for supported content changes. Public HTML is a snapshot, so later edits inside Gamma do not automatically sync to the exported files.

Deploy to a temporary URL, test every outbound link and embed, then use your final domain. Keep your original published site available until the exported version has passed the checks your audience needs.

Edit, deploy and protect your search URLs

Keep the downloaded HTML, CSS and assets together. Store a copy in your own GitHub repository to track changes; a repository is source storage, so configuring a deployment is a separate step. You can publish static files to your own Cloudflare account or another compatible static host.

For changes through an AI agent, connect it to FNJ MCP and give it the intended site and a specific task. Review the draft and its preview before publishing. Use the agent prompt library for content, links and CMS tasks, and the deployment guide for the next steps.

Keep existing page paths when practical. Map changed URLs to their closest replacements with permanent redirects. Check titles, descriptions, canonical URLs and internal links on the final domain, then submit its sitemap in Search Console. These checks help search engines find the replacement pages; they do not guarantee unchanged rankings.