SiteAuditLint checklist library
What this checklist covers
A website migration SEO checklist protects rankings and traffic when you change domains, URLs, platforms, or site structure, by inventorying old URLs, mapping redirects, validating staging, and comparing pre and post migration crawls.
It is organized into 15 sections: Pre-Migration Crawl, URL Mapping, Redirect Plan, Canonicals, Internal Links, XML Sitemap, Robots.txt, Metadata, Structured Data, Analytics, Staging Validation, Launch Day, Post-Migration Crawl, Compare Old vs New and Monitor. Each check lists exactly what to verify and a priority, so you can work through the highest impact items first.
For background on the concepts behind these checks, see Redirects lesson, Audit comparison, Site audits course.
Testing method: For a row-by-row method to test your redirect map, with result codes for every URL, see redirect map validation.
Who it is for:
Download the website migration seo checklist
Use the interactive version below, or download it to share with your team, attach to tickets, or work through offline.
Website Migration SEO Checklist
Work through each check
0 of 18 checks complete
Pre-Migration Crawl
URL Mapping
Redirect Plan
Canonicals
Internal Links
XML Sitemap
Robots.txt
Metadata
Structured Data
Analytics
Staging Validation
Launch Day
Post-Migration Crawl
Compare Old vs New
Monitor
Progress is saved in this browser only.
Detailed explanations
Each section below explains what to check, why it matters, the problems you will usually find, how to fix them, and how to confirm the fix.
Pre-Migration Crawl
On this checklist: crawl the old site; export top pages. Explained in full in the Technical SEO Checklist.
URL Mapping
On this checklist: map old to new URLs. Explained in full in the On-Page SEO Checklist.
Redirect Plan
On this checklist: build redirect rules. Explained in full in the Technical SEO Checklist.
Canonicals
On this checklist: update canonicals. Explained in full in the Indexability Checklist.
Internal Links
On this checklist: update internal links. Explained in full in the On-Page SEO Checklist.
XML Sitemap
On this checklist: prepare new sitemap. Explained in full in the Technical SEO Checklist.
Robots.txt
On this checklist: prepare production robots.txt. Explained in full in the Robots.txt Checklist.
Metadata
On this checklist: preserve metadata. Explained in full in the On-Page SEO Checklist.
Structured Data
On this checklist: preserve schema. Explained in full in the On-Page SEO Checklist.
Analytics
What to check:
- Migrate tracking. Analytics and conversions track on the new site.
Why it matters: Without tracking you cannot measure the impact of launches, migrations, or fixes. Missing tags after a deployment create gaps that cannot be backfilled.
Common problems:
- Analytics missing on new templates
- Duplicate tags inflating sessions
- Conversion events lost after a redesign
- Search Console not verified on the new domain
How to fix it: Deploy analytics through a tag manager across all templates, verify Search Console, and test conversion events before launch.
How to verify: Use tag assistant and real time reports to confirm tags fire on each template and that conversions record.
Learn more: Tracking and analytics audit, Tracking pixel audit, Tracking missing on page issue, SEO KPIs lesson.
How SiteAuditLint helps: it checks analytics across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
Staging Validation
What to check:
- Crawl staging. Staging crawl matches the URL map.
Why it matters: Migrations change URLs, templates, and infrastructure at once. Every old URL that does not redirect correctly loses its rankings and backlinks.
Common problems:
- Missing redirects for long tail URLs
- Redirects to the homepage instead of equivalents
- Staging blocks shipped to production
- Metadata lost on new templates
How to fix it: Map every old URL to its best equivalent, test redirects on staging, and compare old and new crawls field by field.
How to verify: Crawl the full list of old URLs after launch and confirm each returns a single 301 to a 200 page.
Learn more: Redirects lesson, Audit comparison, Redirects troubleshooting.
How SiteAuditLint helps: it checks staging validation across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
Launch Day
What to check:
- Deploy redirects. Sample old URLs return 301 to correct pages.
- Submit sitemaps. New sitemap submitted in Search Console.
Why it matters: Launches often ship staging settings to production. A single forgotten noindex or Disallow can keep a new site out of search for weeks.
Common problems:
- Staging noindex left on production
- Robots.txt still disallowing everything
- Canonicals pointing to the staging domain
- Analytics not installed
How to fix it: Use a launch runbook that removes staging protections, swaps domains in canonicals and sitemaps, and verifies tracking.
How to verify: Crawl production immediately after launch and compare against the final staging crawl.
Learn more: Pre-launch website checklist, Run your first audit, Noindex issues.
How SiteAuditLint helps: it checks launch day across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
Post-Migration Crawl
What to check:
- Crawl old URL list. Every old URL returns a single 301 to a 200.
- Crawl new site. No new 4xx, noindex or canonical errors.
Why it matters: Search engines can only rank what they can discover. See the earlier section on this topic for common problems.
How to verify: Run a full crawl, compare discovered URLs with your sitemap and analytics landing pages, and review the crawl depth report for any important URL deeper than three clicks.
How SiteAuditLint helps: it checks post-migration crawl across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
Compare Old vs New
What to check:
- Compare crawls. Titles, canonicals and indexability match expectations.
Why it matters: Comparing crawls before and after a change is the only reliable way to catch regressions. Many SEO problems are invisible on a single page but obvious in a diff across thousands of URLs.
Common problems:
- Changes to titles, canonicals, or noindex hidden in a release
- Removed internal links reducing link equity to key pages
- URL count changes nobody intended
- Schema dropped from a template
How to fix it: Keep a baseline crawl, compare every new crawl against it, and investigate every unexpected change before it reaches production or within hours of release.
How to verify: Run a crawl comparison report and review changes by field: status, indexability, canonical, title, H1, links, and schema.
Learn more: Audit comparison, SEO testing guide, Scheduled SEO audits.
How SiteAuditLint helps: it checks compare old vs new across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
Monitor
What to check:
- Monitor traffic and indexing. Organic traffic and indexed pages tracked daily for 4 weeks.
Why it matters: SEO issues often appear days after a change, as search engines recrawl. Ongoing monitoring catches drops in indexing and traffic before they become expensive.
Common problems:
- No baseline to compare against
- Traffic drops noticed weeks late
- New 404s from old backlinks going unfixed
- Index coverage declining unnoticed
How to fix it: Schedule recurring crawls, set alerts for indexability and status code changes, and review Search Console coverage and performance weekly.
How to verify: Compare scheduled crawl results and Search Console trends against the pre change baseline.
Learn more: Scheduled SEO audits, Slack SEO alerts, Site health score.
How SiteAuditLint helps: it checks monitor across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
Common mistakes
Not crawling the old site before migration
Redirecting everything to the homepage
Leaving redirect chains from earlier migrations
Forgetting images, PDFs, and long tail URLs in the redirect map
Losing titles, schema, or internal links on new templates
Stopping monitoring after the first week
When to run the checklist
- Domain changes
- HTTP to HTTPS moves
- CMS or platform migrations
- URL structure changes
- Site mergers and consolidations
- Major redesigns
How to verify fixes
Save a baseline crawl before you change anything. Fix high-priority and template-level issues first, since one template fix resolves many URLs, then re-crawl with the same start URL and settings and compare the two audits with audit comparison. Finally, confirm important pages in Search Console with URL Inspection. See how to prioritize audit findings.
SiteAuditLint workflow
Most checks in this list run automatically in a SiteAuditLint crawl. Use audit comparison to diff crawls and scheduled audits to monitor for regressions.
All SEO checklists
See the full checklist library, with a guide to choosing the right checklist for each job.