Start with the published landing page

Paste the live carrd.co or custom-domain URL. Page scope is a practical choice for a one-page portfolio or landing page. It captures that page rather than exploring other public links as a full-site crawl.

Check the result from top to bottom, including content reached through section navigation. A section that appears only after an interaction may depend on scripts, so compare the behavior as well as the visible layout.

Keep section links and contact actions usable

Test every anchor link and browser back action after deployment. If you change a section ID while editing the HTML, update the links that point at it. Also check links to external booking, payment or social pages.

Give each form a working submission service. An exported form design alone does not deliver messages. Test validation, successful submission and failure feedback on the new host, and check any embedded third-party tools separately.

Review the page on a phone before launch

Compare text wrapping, image crops, button size and spacing on a narrow screen. Test keyboard navigation too; preserving the appearance is only one part of a usable landing page.

Deploy a preview in your own account, confirm the final title and description, then switch your custom domain. Keep a copy of the original and the exported files so later changes have a clear starting point.

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.

Google Search Central: moving a site with URL changes

Your Carrd launch checklist

Check anchor navigation on a phone as well as a desktop screen.
Send a test message through every form on the new host.
Verify embeds and custom-domain links after the export is deployed.

Should I use page or site scope for Carrd?

Page scope is usually the starting point for a one-page Carrd site. Choose site scope if you need FNJ to discover additional linked public pages, then inspect the capture report.

Export Carrd to HTML: one-page site and form migration