SEO migration: switch without downtime
An executable path for moving an existing project to SEO, with a rollback plan.
Quick answer
How do I keep canonical and sitemap hostnames consistent?
Both must read site.origin (the Astro site config). Hardcoded hostnames break the moment you change domain or run a Preview, and the page gets flagged as duplicate content.
Machine-readable page data: /data/seo-migration.json
In-depth analysis
SEO is fundamentally about making canonical signals (canonical link, sitemap, structured data) clear and traceable so search engines never classify your pages as duplicates. Migration runs in parallel with validation and gradual cutover — keep a switch that rolls back in seconds so business never breaks.
# public/robots.txt
User-agent: *
Allow: /
Disallow: /links/
Disallow: /api/
Sitemap: https://aicode8.com/sitemap-index.xmlSEO Migration · Key takeaways
- Full branch build passes
- All 8 Preview drills green
- Production and Preview KV isolated
- Rollback switch ready
FAQ & pitfalls
How often does search engine cache refresh?
Bump lastmod to trigger a sitemap re-crawl, paired with an independent canonical. Do not rely on forcing a CDN purge — after the static output updates, crawlers return naturally.
Explore the hub
See all 5 guides in Edge ArchitectureSame category as this article, sorted across the codebase.
AI Search migration: switch without downtime
An executable path for moving an existing project to AI Search, with a rollback plan.
Astro migration: switch without downtime
An executable path for moving an existing project to Astro, with a rollback plan.
Cloudflare Pages migration: switch without downtime
An executable path for moving an existing project to Cloudflare Pages, with a rollback plan.
Cloudflare Pages deployment guide
A hands-on, zero-ops edge deployment using Git-driven Cloudflare Pages.
Share & save
What readers are asking
Questions that keep coming back in reader feedback, already answered.
- 01
How do the canonical and sitemap domains stay in sync?
Both must read site.origin (the Astro site setting). A hardcoded domain breaks everywhere the moment you change domains or use a Preview URL, and the pages get treated as duplicates.
See the full guide → - 02
How do I stop generated pages being flagged as duplicate content?
Every page needs a unique canonical, its own title, and genuinely differentiated body copy. Pages that only swap a keyword while keeping an identical structure must gain real differences, or search engines fold them together.
See the full guide → - 03
Why is my Astro component's interactivity not working?
Components ship as zero-JS HTML by default, so an interactive one needs a client:* directive (client:load, client:visible, …). Without it the script is never bundled into the page.
See the full guide →