Key Takeaways
- Crawl the live site fully before touching the new environment.
- Export every indexed URL and its current rankings.
- Map the backlink profile and identify high-value links that need redirect coverage.
- Build a 301 redirect map for every high‑value page.
- Set a pre-migration performance baseline to prove post-migration value.
Website migrations, by nature, are high-risk endeavours. When not done right, your client’s ranking and website traffic can take a major hit. Most migrations that skip the pre-migration audit experience everything from broken redirect chains and vanishing crawl paths to stripped metadata and page speed regressions.
To avoid all of this, use the following checklist. It works for any migration: domain change, HTTP to HTTPS, CMS switch, or structural URL updates.
The Site Migration SEO Checklist For 2026
A successful migration starts with a complete audit of the current website. The best way to do this is to break the entire process down into manageable phases.
Phase 1: Crawl The Existing Site
Run a full technical crawl of the client’s live site. Do this at least one week before migration. Use any SEO audit tool that can crawl. You need a complete inventory of every URL, image, and script.
The crawl report should show you:
- Broken links (4xx and 5xx responses)
- Redirect chains longer than three hops
- Orphan pages with no internal links pointing to them
- Duplicate content and missing meta tags
This is your baseline, and you will need this information to determine what, if anything, breaks post-migration.
Phase 2: Audit URL Indexation And Rankings
You also need to know which URLs Google has indexed, along with which keywords are currently driving traffic.
Document these three things before the migration:
- All indexed URLs from your crawl.
- Top 50 ranking keywords for each important page.
- Current click‑through rates and positions.
This step is essential because without this information, you cannot build accurate redirect maps.
Phase 3: Build A Complete Redirect Map
Create a 301 redirect for every URL that has traffic, backlinks, or rankings. Point each old URL to the most relevant new URL.
Approach this phase like so:
- Identify all high‑value URLs from your pre‑migration crawl.
- Map each old URL to a specific new URL. No catch‑all redirects.
- Test redirect rules on a staging environment before go‑live.
- Flag any old URL that would return a 404 if not redirected.
Better yet, export the redirect map as a CSV and test every line systematically.
Phase 4: Validate Structured Data And Internal Links On Staging
Migration breaks schema markups and internal links. You will see the impact of this only after go‑live unless you check and verify them during staging first.
On the staging server, run a crawl that scans for:
- JSON‑LD and microdata syntax errors after URL changes,
- Internal links still pointing to the old domain or old URL paths,
- Image alt text and anchor text that reference old URLs.
Fix every error before pushing to production, and document each broken internal link with its line number from the HTML.
Phase 5: Post‑Migration Validation In The First 72 Hours
Once the site has been migrated, run another crawl and compare both reports side by side.
Here, you should be on the lookout for:
- New 4xx and 5xx errors were introduced during migration.
- Redirect chains that appeared (soft 404s, temporary redirects).
- A drop in internal link count for any important page.
- Robots.txt or sitemap.xml is blocking new pages.
Fix any critical issues as soon as possible.
Phase 6: 30‑Day Monitoring And Backlink Reclamation
Rankings will never stabilise post-migration immediately. Monitor keyword positions for 30 days, and if a keyword drops, trace it to a missing redirect or a content change.
At this phase, you must also audit those lost backlinks, if any:
- Identify which old URLs still have external links pointing to them.
- Check whether those URLs now 301 correctly to new pages.
- Contact referring sites to update links if the redirects are broken.
This last step separates good agencies from great ones.
Summing It Up
Site migrations never fail because agencies lack technical knowledge or the relevant skills. They almost always fail cause they overlook the critical pre-migration SEO audit. Doing things right will not only preserve the client’s SEO performance post-migration but will also demonstrate your agency as one they can trust and recommend.
Ready to run a faster, more thorough pre-migration audit? XOVI gives you crawling, rank tracking, backlink analysis, and white-label reporting all in one place. Start your 14-day free trial with XOVI today.
Frequently Asked Questions
Can I crawl a staging server before go‑live?
Yes. Most crawling tools let you enter a staging URL or IP address directly. Crawl the staging environment, fix all errors, then compare with your pre‑migration report. Confirm everything works before you launch.
How do I automatically check redirect chains?
Use a crawler that follows every redirect in a chain and reports the total hops. Flag any chain longer than three hops. Distinguish permanent 301s from temporary 302s. Watch for soft 404s where a redirect lands on an error page.
What is the biggest SEO risk in a site migration?
Missing redirects, i.e., when a URL changes without a 301 in place, every backlink pointing to it stops passing equity. Map every URL that will change before migration begins.
Should the audit happen before or after the migration?
Before. The audit builds the protective measures, like redirect maps, content preservation lists, and performance benchmarks, that go live with the migration. Auditing after means diagnosing damage rather than preventing it.
Do JavaScript-heavy sites need a different audit approach?
Yes. Standard crawlers pull static HTML and miss content that only renders after JavaScript executes. For SPAs and modern eCommerce platforms, use a JavaScript-rendering crawler; otherwise, URL discovery and on-page analysis are incomplete.

