Site Migrations SEO Checklist: Redirects, Canonicals, and Monitoring
A source-backed site migration checklist for SEO: planning, redirects, canonicals, sitemaps, and Search Console validation to reduce risk.
Migrations are process-heavy: the best risk reduction comes from a clear inventory, deliberate mapping, and careful monitoring.
TL;DR (Key takeaways)
- Follow Google’s site move guidance when URLs change — it covers planning, redirects, and validation. (Site move with URL changes)
- Redirect mapping, canonicalization, and sitemaps need to agree on which URL is the “source of truth.”
- Validate with Search Console, monitor errors, and keep a rollback plan.
What we know (from primary sources)
Google Search Central provides a dedicated guide for moving a site with URL changes. It covers recommended steps such as preparing redirects, updating internal links, and monitoring results after launch. (Google: site move with URL changes)
Separately, Google documents how Search treats common HTTP status codes during crawling and indexing — which is directly relevant to redirect behavior in migrations. (HTTP status codes)
Pre-migration: planning and inventory
1) Identify “must not break” pages
Export your top pages by organic traffic and conversions (from Search Console and analytics). In AI-search contexts, also identify pages that act as citation anchors (glossaries, definitions, primary guides).
2) Build a URL mapping (old → new)
Every old URL should have a destination: an equivalent page, an improved page, or a deliberate removal. If content is removed, return the right status code. HTTP Status Codes for SEO
3) Establish canonical rules
Canonicals help search engines understand which URLs should be treated as primary. Read Google’s canonicalization guide and ensure your new site’s templates apply canonicals consistently. (Canonicalization)
Migration launch: technical checklist
- Redirects: 301 from old URLs to the closest new equivalent; avoid redirect chains.
- Internal links: Update to point directly to new URLs (don’t rely on redirects forever).
- Sitemaps: Publish new sitemaps containing only new canonical URLs. (Sitemaps overview)
- Robots directives: Confirm you’re not blocking critical sections. Robots.txt guide and Meta robots guide
- JS rendering: If the new site is more JS-heavy, validate indexing assumptions. JavaScript SEO
Post-migration: monitoring and validation
Search Console checks
- Submit your new sitemap(s) and watch indexing and errors. (Sitemaps report)
- Use URL Inspection to spot-check key URLs and confirm canonical choices. (URL Inspection)
What’s next
If you plan to scale content after the migration (especially with AI), anchor the team on a shared technical baseline and editorial governance:
Why it matters
Migrations are one of the highest-risk SEO activities because they change the identity of your pages. A careful migration preserves discovery, consolidates signals cleanly, and keeps your best “source” pages visible — which matters for both classic search traffic and the citation dynamics of AI answer engines.
For AI context, see AI & SEO trends and AI search monitoring strategy.