Website migration SEO checklist
What to export before the move, what to do on launch day and what to check in Search Console for eight weeks after.
Free, no sign-up · works in Excel, Google Sheets, Numbers, Notion or any Markdown editor
At a glance
- Sections
- 7
- Type
- Checklist · spreadsheet
- Formats
- xlsx · csv · md
- Cost
- Free, no sign-up
- From the guide
- Website migration SEO: a Search Console checklist
The whole template, on one page.
The downloads hold exactly this. Jump to a section from the list.
Website migration checklist: [old site] → [new site]
01Migration type
If any visible URL changes, treat it as a move with URL changes. Don't combine a URL move with a redesign or new CMS.
| Migration type | Example | URLs change? | Change of Address tool? |
|---|---|---|---|
| Domain move | example.com to example.org, or shop.example.com to example.com | Yes, every URL | Yes |
| HTTP to HTTPS | http://example.com to https://example.com | Yes, the protocol | No, Google detects it |
| URL structure | /blog/post-name to /articles/post-name | Yes, some or all paths | No |
| Platform or hosting | New CMS or CDN, same URLs | No | No |
02Before the move
| Step | Task | Done |
|---|---|---|
| URL inventory | List every old URL from sitemaps, server logs, analytics, Search Console's links report and the CMS, including images, PDFs and parameter URLs that earn links | |
| Performance baseline | Export the Pages tab of Performance > Search results for the last 3 months (16 if seasonal); use the API or BigQuery past 1,000 rows | |
| Top queries | Save the top queries of the top pages, to check they land on the new URLs later | |
| Indexed count | Screenshot Indexing > Pages filtered to All submitted pages | |
| Redirect map | One old URL → one equivalent new URL, one hop; 404 or 410 for dropped content, never a blanket redirect to the homepage | |
| Verify the new site | Add the new property in Search Console (a Domain property covers every variant) | |
| Test on staging | Self-referencing canonicals, internal links and hreflang on new URLs, a sitemap with only new URLs; note the staging noindex and robots.txt rules |
03Redirect map
Check the top few hundred URLs by baseline clicks by hand.
| Old URL | New URL | Status code | Baseline clicks | Checked |
|---|---|---|---|---|
04Launch day
Redirects go live first; Search Console comes after.
| Order | Task | Done |
|---|---|---|
| 1 | Remove the staging noindex tags and robots.txt disallow rules | |
| 2 | Switch on server-side permanent redirects (301 or 308) | |
| 3 | Spot-check the top baseline URLs: one 301 to the right new URL, which returns 200 | |
| 4 | Submit the new sitemap in Indexing > Sitemaps; keep the old one submitted for a while | |
| 5 | Domain moves only: run the Change of Address tool | |
| 6 | Update links you control: social profiles, other sites, ads, email templates |
05Change of Address (domain and subdomain moves only)
| Step | Task | Done |
|---|---|---|
| 1 | Be an owner of both properties; the old homepage 301s to the new site | |
| 2 | Open the old domain-level property in Search Console | |
| 3 | Settings > Change of address | |
| 4 | Pick the new site and let the checks run | |
| 5 | Submit, and repeat for each verified variant of the old domain (www included) | |
| 6 | Keep the redirects and the old domain for at least a year |
06After the move
Judge the combined total of old and new URLs, not the old URLs alone.
| When | Page indexing | Performance | Sitemaps | Status |
|---|---|---|---|---|
| Week 1 | New property: indexed count starts to rise. Old property: Page with redirect grows. No spike in Not found (404), Redirect error or Server error (5xx) | Top 50 baseline URLs: impressions start moving to the new URLs | New sitemap read with no errors | |
| Week 2 | Validate fix on any new error reason. Check Duplicate, Google chose different canonical than user on new URLs | Total impressions old plus new near the baseline | Old sitemap's indexed count falling, new one rising | |
| Week 4 | Most submitted new URLs indexed. Old URLs mostly Page with redirect | Clicks per section vs baseline. Baseline queries land on new URLs | New URLs that are submitted but not indexed | |
| Week 8 | Indexed count close to the pre-move number | Clicks vs the same weeks before the move, and vs last year if seasonal | Remove the old sitemap once its indexed count is near zero |
07Common failures
| Failure | Symptom or fix |
|---|---|
| noindex or robots.txt block left from staging | New property's indexed count stays flat; URL Inspection reports the page as blocked |
| Redirects to the homepage or a category | May be treated as soft 404s; point each URL at its equivalent |
| Redirect chains from an earlier migration | Flatten them in the map so every old URL takes one hop |
| Canonicals still on old URLs | Conflicting signals; Google may keep old URLs as canonical |
| Internal links left on old URLs | Every click hits a redirect and Google keeps crawling old URLs |
| Missing URLs | Pages that earned traffic or links now return 404; add them to the map |
The .xlsx, .csv and .md downloads contain the same content.
How to use it.
4 steps, start to finish.
- 01
Name the migration type
Domain, protocol, URL structure or platform. It decides whether URLs change and whether you need the Change of Address tool.
- 02
Export the baseline first
Before anything changes: clicks and impressions per URL, top queries for the top pages and the indexed page count. You can't get them back afterwards.
- 03
Work the launch steps in order
Staging blocks off, redirects on, spot checks, then the sitemap and Change of Address.
- 04
Check on a fixed schedule
Weeks 1, 2, 4 and 8, rather than refreshing the reports every day. Roll back only if the new site is broken in ways you can't fix within days.
With Serplyze
Measure the migration against your baseline with Serplyze
Serplyze keeps your Search Console history, so the baseline is already there. On paid plans, log the launch as a Technical action on the migrated pages or a page group: Serplyze compares 28 days before with 28 days starting a week after, sets it against the whole site's trend and marks the launch on your charts. Traffic's Lost and New views list URLs that stopped or started getting impressions.
Questions.
Google says that for a medium-sized site it can take a few weeks or more for most new URLs to show in search, longer for large sites, and rankings can fluctuate while it recrawls.
Only for domain and subdomain moves. Not for HTTP to HTTPS (Google detects it), www to non-www on the same domain, or moving some pages within a site.
At least a year. Google forwards signals for 180 days after a Change of Address, and its site move guide recommends keeping redirects generally for at least a year; keep the old domain registered for as long.
Rarely. Most problems are fixed forward, and a reversal makes Google process a second move. Consider it only when the new site is broken at a level you can't fix within days.
More free templates.
All templates- Report
Monthly SEO report template
Nine sections that answer what happened, why, and what you do next, in under five minutes of reading.
Open the template - Brief
Content brief template
Turn a cluster of Search Console queries into a brief a writer can act on, with a success check set before you publish.
Open the template - Checklist
SEO audit checklist
Nine Search Console checks, in order, with where to click and what counts as a finding. One hour a month.
Open the template