Updated
A website migration SEO checklist is the set of checks that keeps your Google traffic when a site changes its URLs, domain, platform or structure. The core of it: list every URL that earns search traffic, map each one to its new URL, put permanent (301 or 308) redirects live on launch day, check every redirect in bulk, then compare traffic by page type with your pre-launch numbers for the next few weeks.
Google’s own guide to site moves with URL changes sets the expectation: a small to medium-sized website can take a few weeks for most pages to move, larger sites take longer, and rankings fluctuate in the meantime. A dip in the first weeks is normal. A dip that stays is almost always a redirect, indexing or content problem you can find and fix.
Which kind of migration is this?
“Migration” covers several different changes. They share the redirect work, but they carry different risks, and only one needs Google’s Change of Address tool.
| Change | Example | Change of Address tool? | What usually goes wrong |
|---|---|---|---|
| Domain change | olddirectory.com → newdirectory.com | Yes, for each verified variant of the old domain | Deep pages left without redirects; old domain allowed to expire |
| HTTPS or www switch | http:// → https:// | No | Internal links and canonicals still point at the old version |
| New URL structure | /austin/plumbers → /plumbers/austin-tx | No | Patterns nobody mapped; chains through older redirects |
| Platform or CMS change | Custom build → WordPress with a directory plugin | Only if the domain changes too | New URL patterns, missing fields, a staging noindex left on |
| Redesign or consolidation | Merging thin city pages into metro pages | No | Content and internal links removed along with the old design |
Source: Google’s Change of Address tool help, which says to use the tool when moving from one domain or subdomain to another, and not for HTTPS switches or path changes within a site.
Before launch
1. Benchmark by page type
Record what you have now, split the way your site is built: clicks, impressions and position for listings, city pages, category pages, category × city pages and guides, plus how much of each Google has indexed. After launch you compare each line with its own baseline. A site-wide total hides a 40% loss on one template behind a gain on another.
Save the top pages by clicks and by impressions for at least the last 3 months, and keep a copy: Search Console only keeps 16 months, and the old URLs’ history is what tells you later whether the new ones caught up.
2. Build the full list of old URLs
Google suggests compiling old URLs from your sitemaps, your most-trafficked pages, your CMS, server logs and Search Console’s Links report, including images, videos, JavaScript and CSS. On a directory add two more sources: every URL with impressions in Search Console (city and category pages that rank on page three still matter), and expired or merged listings that still get links.
3. Map URLs by pattern, then handle the exceptions
A directory with 40,000 URLs does not need 40,000 hand-written rows. It needs one rule per page type, plus a short list of exceptions. Write the rules first, run every old URL through them, and look at what falls out.
| Page type | Old pattern | New pattern |
|---|---|---|
| Category × city | /{city}/{category} | /{category}/{city}-{state} |
| City | /city/{city} | /{state}/{city} |
| Listing | /listing.php?id={id} | /listing/{business-slug} |
| Category | /category/{category} | /{category} |
Exceptions are where migrations leak traffic: cities with the same name in different states (Springfield), categories renamed or merged, listings whose slug changed, and anything with a query string. Every URL that had search traffic needs a target you have looked at.
4. Decide what will not move
Not every old URL needs a redirect. For content you are dropping, Google says the URLs should return a 404 or 410 on the new site. What it warns against is the lazy middle ground: “Don’t redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site.” Redirect when a real equivalent exists; otherwise let the URL go. See which 404s to leave alone.
5. Prepare and crawl the new site on staging
- Keep staging out of Google with a password or noindex, and write down every block you will remove on launch day.
- Crawl staging and compare it with a crawl of the live site: titles, H1s, meta descriptions, main text, structured data and the number of internal links each page type gets.
- Every new page should have a canonical tag pointing at itself, and every internal link should point at a new URL, not an old one that redirects.
- Run the full old-URL list against the staging redirect rules and check the status code, the number of hops and the target of every one.
- Verify the new site in Search Console (a Domain property covers http, https, www and non-www), set up analytics, and make sure the server can take more crawling than usual.
6. Pick the timing and the size
Launch in a quiet traffic period. Google suggests large sites can move in sections; on a directory that can mean moving one state or one category first, checking it, then moving the rest.
Launch day
- Turn on the redirects. Server-side, permanent (301 or 308), straight to the final URL. Google advises “no more than 3 and fewer than 5” redirects in a chain; one hop is the target.
- Remove staging blocks. The noindex tags, the robots.txt disallow and the password. Leftover noindex and robots.txt blocks are on Google’s list of common migration mistakes. See where a noindex can hide.
- Check every old URL that had traffic. Not a sample. More on bulk checks below.
- Inspect a few pages of each type with the URL Inspection tool live test: indexable, canonical correct, content rendered.
- Submit sitemaps. Google’s guide says to submit both the new-URL sitemap and the old-URL one you saved while mapping, so Google crawls the old URLs and sees the redirects. Remove the old one later.
- Domain change only: submit the Change of Address in Search Console for the old property, for every verified variant. You need to be an owner of both properties, with a 301 from the old home page to the new one.
After launch
First week
- Watch server logs and Search Console’s Crawl stats for spikes in 404s and 5xx errors.
- In the Page indexing report, old URLs move into “Page with redirect”. That is expected, not a problem.
- Fix any redirect pattern that lands on the wrong page the same day. Every day it stays wrong, Google records more of it.
Weeks 2 to 6
- Compare clicks and impressions per page type with the baseline. Old URLs’ impressions should fall while the new URLs’ rise.
- Check the indexed share of each new template. A template stuck in “Discovered - currently not indexed” usually has weak internal links on the new site.
- Look for searches that switched to a different page, a sign two new pages now compete. See competing pages.
Months 2 to 12
- Keep the redirects. Google: “Keep the redirects for as long as possible, generally at least 1 year.” After a domain change, keep the old domain registered so the redirects keep working.
- Ask the sites that send you the most traffic to update their links.
- If a page type is still well below its baseline after several weeks, compare old and new pages side by side: content, internal links, title. Something changed besides the URL.
The website migration SEO checklist, in one table
| Phase | Task | How to check it |
|---|---|---|
| Before | Benchmark clicks, impressions and indexed share by page type | Saved export or report per template |
| Before | Full old-URL list, including every URL with impressions | Count matches sitemap + Search Console + CMS |
| Before | Pattern rules for each page type, exceptions listed | Every old URL with traffic has a target |
| Before | Dropped content returns 404 or 410, not the home page | No redirect targets the home page |
| Before | Staging crawled and compared with the live site | Titles, content and internal links match or improve |
| Before | Self-referencing canonicals; internal links to new URLs | Crawl shows no internal links to redirects |
| Before | New site verified in Search Console; analytics live | Both properties visible, data arriving |
| Launch | 301 or 308 redirects, one hop | Bulk check: status, hops, target |
| Launch | Staging noindex, robots.txt block and password removed | Live test in URL Inspection |
| Launch | Old and new sitemaps submitted | Search Console Sitemaps report |
| Launch | Change of Address (domain changes only) | Search Console confirms the move |
| After | Errors and 404s in the first week | Crawl stats, server logs |
| After | Traffic by page type against the baseline | Each template within normal swing of its baseline |
| After | Old URLs fading from results, new ones indexed | Impressions shift from old to new URLs |
| After | Redirects kept for at least a year | Calendar reminder; old domain renewed |
Migrating a directory or listing site
Directories migrate differently from brochure sites because almost every URL is generated. That makes mapping easier (patterns) and mistakes bigger (one wrong rule breaks 3,000 pages).
- Map category × city pages first. They usually carry most of a directory’s search traffic. Check that a city name that exists in several states maps to the right state’s page.
- Listings whose business closed. Send them to the same category in the same city if that page lists comparable businesses, or let them return 410. Not to the home page.
- Pagination and filters. Map page 1 of every list. Parameter URLs that never earned impressions can go; ones that did need a target. Pagination and faceted navigation covers which ones should be indexable at all.
- Don’t clean up during the move unless you have to. Removing thin city pages is often the right call, but doing it in the same release as new URLs makes the result hard to read. If you combine them, record which page types you pruned so you can tell the effects apart. See index bloat.
- Compare before and after by page type, not just for the whole site. A new platform often changes one template (listings losing their description field, for example) while the URLs move cleanly.
How to check redirects in bulk
A bulk redirect check takes the list of old URLs and, for each, follows every hop and records the status codes and the final URL. Then you compare the final URL with your map. Free browser-based bulk redirect checkers handle a few hundred URLs; a desktop crawler in list mode handles more. For a quick check from the command line:
while read url; do
curl -s -o /dev/null -L -w "%{http_code} %{num_redirects} %{url_effective} $url\n" "$url"
done < old-urls.txtEach line shows the final status, the number of redirects and where the URL ended up. Then look for:
- A final status other than 200, or more than one redirect.
- A 302 or 307 where you meant a permanent redirect.
- A final URL that is not the one in your map, or that is the home page.
- A final page with a noindex tag, or a canonical pointing somewhere else.
- Old URLs that return 200 because nothing redirected them.
The list you check matters more than the tool. Check every old URL that had clicks or impressions in Search Console before launch, sorted by that traffic, so the problems that cost the most come first.
How DirectoryLens checks a URL change
In DirectoryLens, URL changes (under Advanced) runs this check for you after go-live. You give it a name, the go-live date and, optionally, a CSV of old URL to new URL (up to 2,000 rows). It takes your top 100, 250 or 500 pages by Google visits in the 28 days before go-live, plus every mapped URL, and visits each one as DirectoryLensBot at one request a second, following redirects hop by hop and reading the noindex and canonical on the page it lands on. URLs your robots.txt blocks are reported, not fetched.
- Redirect issues, each with the pre-launch visits at stake: 404 or error pages, server errors, loops, more than 10 hops, redirects to the home page, robots.txt blocks, chains, temporary redirects, meta refreshes, wrong targets (when you gave a map), noindex targets and canonicals pointing elsewhere.
- Visits from Google by week for the whole site, the old URLs and the pages they now land on, with the go-live day marked.
- Moved URLs by page type: visits a day before go-live against visits a day now on the pages they land on, and the share kept.
- A 0 to 100 risk score built from four parts you can see: broken redirects, weak redirects, traffic carried over (from 14 days after go-live) and old URLs still in Google (from 28 days).
Two limits, honestly. The check starts once the change is live; before launch, use the page type reports for your baseline and URL list. And it is built for URL changes within one site, including HTTPS and www switches: on a move to a new domain it flags the redirects as leaving the site rather than following them, so check a domain move with a crawler as well. You can try the reports on the live demo.