NeovaAdvanced SEO Platform

Site Migration Checklist: Before, During and After the Move

A site migration is any change big enough to move URLs, hosts or templates: a new domain, a new CMS, HTTPS, a redesign. Most traffic lost in a move is lost to small things nobody listed: a URL with no redirect, a noindex left over from staging, a canonical still pointing at the old host. This site migration checklist puts every step in order, with the numbers Google publishes.

Audits, Logs and Monitoringsite migration checklistUpdated November 21, 2026By the Neova team

Which Kind of Migration Is It?

The checklist is the same for every move, but how much of it applies depends on what changes. Google's guide to site moves with URL changes covers the moves where addresses change; a redesign on the same URLs is lighter but still worth a full before and after crawl.

MoveURLs changeRedirectsChange of Address toolRisk
HTTP to HTTPS✓Every URL–Low
www to non-www✓Every URL–Low
New domain✓Every URL✓High
New URL structure✓Changed URLs–High
New CMS or platform◐Changed URLs–High
Redesign, same URLs–None–Medium
Merging two sites✓One site✓High

Google says the Change of Address tool in Search Console is only needed when you move from one domain or subdomain to another. Protocol and www changes on the same domain do not need it. SEO ProCheck's site migration FAQ answers the edge cases, such as moving a blog from a subdomain into a folder.

Step 1: Inventory Every URL Before You Touch Anything

The redirect map can only be as complete as the list of old URLs. A list built from the XML Sitemap alone is never complete. Collect every source, then merge them:

SourceWhat it addsKeep
Full crawlEvery linked URLStatus, title, canonical
XML SitemapsWhat the CMS listsEvery file
Search ConsoleURLs with clicks16 months
Analytics 4Landing pages12 months or more
Server logsURLs bots request30 days or more
Backlink toolURLs other sites link toTop linked URLs

We found this on our own site. Our full crawl of seoprocheck.com on October 17, 2026 fetched 10,222 URLs in 61 minutes. The XML Sitemaps listed 1,835 URLs. The crawl reached 2,727 URLs that no sitemap listed, and 1 URL sat in the sitemap that no link reached. A redirect map built from the sitemap alone would have left thousands of addresses with no rule.

Save the crawl of the old site. It is the baseline you compare everything against after launch, and the only record of what each URL said before the move. The how to crawl a website guide covers the settings for a complete crawl.

Step 2: Build the Redirect Map

A redirect map is a two column list: every old URL and the one new URL it should send visitors to. The rules that keep it clean:

  • One to one where you can. Each old page goes to the new page that covers the same topic, not to the home page.
  • Permanent redirects. Google recommends HTTP permanent redirects, 301 or 308, if possible.
  • One hop. Point old URLs at the final new URL, including the last change of protocol, host and trailing slash. The redirect chains guide shows how stacked rules become three hops.
  • Old redirects too. URLs that already redirect today need their target updated, or the move adds a hop to every one of them.
Old URL isDo this
Page with an equivalent301 to that page
Page with no equivalent301 to closest parent
Page with no value404 or 410
Already redirectingPoint at final URL
Parameter or filter URLRule by pattern
Image or PDF with links301 to new file

Write pattern rules for large groups, such as a whole folder moving, and single rules for the pages that matter most. Then test the map: request every old URL and check where it lands.

Step 3: Test the Staging Site Against Production

Crawl the staging site before launch and compare it with the production crawl URL by URL. Keep staging behind a login, not only robots.txt: a disallow rule hides nothing, and a staging robots.txt copied to production blocks the whole site on launch day. SEO ProCheck explains the risks in managing staging environment SEO risks.

CompareStaging shouldCommon surprise
Status codeMatch productionPages now 404
noindexOnly where plannedSitewide noindex
CanonicalName the new URLOld host left in
Title and H1Match or improveTemplate default text
Meta descriptionCarried overEmpty on every page
Internal linksPoint at new URLsLinks to staging host
hreflangReciprocal, new URLsReturn links missing
Structured dataCarried overDropped by new theme
URLs only in oneExplainedWhole sections missing

Rendering matters here too. A new front end that builds links or canonicals with JavaScript can look fine in a browser and empty to a crawler that reads the raw HTML. The JavaScript SEO crawler guide covers how to compare the two.

Step 4: Launch Day Checklist

TaskWhenHow to confirm
Remove staging noindex and blocksBefore switchCrawl the live site
Publish the new robots.txtAt switchFetch /robots.txt
Turn on redirectsAt switchRequest old URL list
HTTP to HTTPS 301At switchRequest http:// home
Unknown URLs answer 404At switchRequest a made up URL
Submit new XML SitemapsDay 1Search Console Sitemaps
Change of AddressDay 1, domain movesSearch Console tool
Update internal linksDay 1No links to redirects
Analytics and tags firingDay 1Real time report
Update profiles and adsWeek 1Links point at new URLs

Google adds that you can remove the old sitemap once the new one is submitted, since Google uses the new sitemap from then on.

What We Found on Our Own Site

Two of the launch day checks above come straight from our own SEO pass on neova.app on November 20, 2026. Neither looked wrong in a browser:

RequestExpectedWe gotFixed
http://neova.app301 to https200✓
Unknown address404503 coming soon page✓

The first meant every page existed twice, once on each protocol. The second told crawlers that every mistyped URL was a temporary outage worth retrying. Both are the kind of rule a migration replaces without anyone noticing, which is why the checklist asks you to request them by hand.

Step 5: After Launch, Watch for a Year

Google says a medium sized site can take a few weeks or more before most new URLs show in place of the old ones, and asks you to keep redirects for at least 1 year, generally as long as possible. Plan the follow up the same way:

WhenCheckSource
Day 1Full crawl, compare with baselineCrawler
Days 1 to 7404s and 5xxServer logs
Week 1Old URLs still getting clicksSearch Console
Weeks 2 to 4Indexed pages, new vs oldPage indexing report
Month 1 to 3Clicks by page groupSearch Console
Month 12Redirects still in placeList crawl of old URLs

Some drop in the first weeks is common; a drop that keeps growing after a month points at a missing redirect, a blocked section or lost internal links. SEO ProCheck's site migration SEO checklist goes deeper on recovery. For ongoing watching after the move, see SEO monitoring.

Site Migrations With Neova

Neova has a Migration and Staging toolset built from two crawls:

  • Redirect Map matches every URL of the old site crawl to the new site crawl with a confidence, for a move on the same domain or to another one.
  • Live Redirect Check checks each old URL's live redirect against the map and flags the wrong or missing ones. Old URLs as a List crawls the old URLs to see where each one lands.
  • Staging vs. Production compares status code, noindex, canonical, title, meta description, H1 and the URLs found in only one crawl. Swap Crawls flips which side is which.
  • Crawl a Staging Site ignores robots.txt and goes faster on a site you confirm is yours, with HTTP authentication and custom headers. When a staging start page links mostly to the live site, New Crawl offers the URL Rewriting rule and the live XML Sitemaps in one click.

The checks that catch migration mistakes:

Neova runs on and in the browser with Neova Online. The Free plan crawls up to 1,000 URLs with all 694 checks; see Features or download Neova.

Questions

What should a site migration checklist include?

An inventory of every old URL, a one to one redirect map, a staging crawl compared with production, a launch day list (robots.txt, redirects, sitemaps, Change of Address for domain moves) and a follow up plan for at least a year.

How long should I keep redirects after a site migration?

Google asks for at least 1 year, and generally as long as possible. Old links, bookmarks and other sites keep sending people to the old URLs long after search results have changed.

How long does it take Google to process a site move?

Google says a medium sized site can take a few weeks or more before most pages show under their new URLs. Large sites take longer, and some fluctuation in that time is normal.

Do I need the Change of Address tool for an HTTPS migration?

No. Google says the tool is only for moves from one domain or subdomain to another. HTTP to HTTPS and www changes on the same domain only need permanent redirects.

Should I block my staging site with robots.txt?

Use a login instead. A disallowed URL can still be indexed from links, and a staging robots.txt that reaches production on launch day blocks the whole new site.

Take this with you

The assistant links open with a question about this page already written.

Crawl your site with NeovaThe Free plan runs every check on Mac, Windows and Linux. No credit card required.

Keep Reading