Website migration SEO is the work that lets Google, and your customers, follow your pages when their addresses change or your site moves somewhere new. The job comes down to four things: list every old URL, send each page that has a new home there with a permanent redirect, test the new site before launch and watch Search Console afterward. Google’s site move guide says to expect “temporary fluctuation in site ranking during the move,” and that for a medium-sized site “it can take a few weeks or more” before Google shows the new URLs in place of the old ones. The steps below follow Google’s site move documentation, so you can run a move yourself or check the plan someone hands you.
In short
- A hosting change keeps your URLs. A new domain, an HTTPS switch or a new URL structure changes them, and each changed URL needs a plan.
- Build the redirect map from a full list of old URLs, and send each page that moved or has a clear replacement straight there with a permanent server-side redirect (301 or 308).
- When an old page has no real replacement, let it return 404 or 410 instead of redirecting it somewhere unrelated.
- Google’s Change of Address tool is only for moving from one domain or subdomain to another.
- Google says to keep redirects “for as long as possible, generally at least 1 year.”
What counts as a website migration
A website migration, which Google calls a site move, is any change to where your pages live or how they’re served. What decides the work is whether your URLs change.
Google’s guide to moving a site with URL changes covers HTTP to HTTPS, new domain names and new URL paths (for example, example.com/page.html becoming example.com/page.htm). Its guide to changing your hosting is “only for migrations that don’t affect the user-visible URL,” such as a new hosting provider or a content distribution network (CDN).
| Change | Do URLs change? | What to do | Change of Address tool? |
|---|---|---|---|
| New hosting provider or CDN | No | Copy and test the site, update DNS, watch both servers, then shut the old hosting down | No |
| HTTP to HTTPS | Yes | Redirect each HTTP URL to its HTTPS version | No. Google “will figure out your changes for you” |
| New domain | Yes | Redirect each old page to its new address, then file a change of address | Yes |
| New URL structure, same domain | Yes | Google says to “just add redirects, and update your sitemaps as appropriate” | No |
| Redesign or new platform | Only for pages that get new addresses | Redirect renamed pages and change one thing at a time | No, unless the domain changes too |
That last point is Google’s advice for any move. If you want a new domain, a new content management system (CMS) and a new layout, it says to “do them one at a time: move to a new domain, then change your site’s layout.” Its Change of Address help warns that combining a move with a redesign of the content and URL structure means “you will probably see some traffic loss as Google might need to relearn and reassess the individual pages.”
Step 1: List every old URL and save a baseline
Your redirect map can only cover URLs you know about, so start with the pages that matter most. Google’s site move guide suggests these sources:
- Your sitemaps, since “it’s likely your most important URLs have been submitted in Search Console that way.”
- Your analytics or server logs, for “the URLs that get the most traffic.”
- Search Console’s Links report, whose Top linked pages table shows “which of your pages have the most backlinks from other sites.”
- Your CMS, which “can typically provide a straightforward way to get a listing of all URLs that host content.”
We’d add the Pages tab in Search Console’s Performance report, which lists your pages by their clicks and impressions in Google Search. Don’t forget files: Google says images and downloads such as PDFs “might already be getting traffic from Google Search or links.”
Then record a baseline before anything changes, so you can tell later what the move did. Our guide to SEO KPIs and baselines covers which numbers to save. While you’re in Search Console, Google recommends verifying “all variants of both the old and new sites” and making sure your verification file or tag carries over to the new site.
Step 2: Build the redirect map
A redirect map is a sheet with one row per old URL: the old address, the new address and the status code it should return. Once you have the list, Google’s guide says, “decide where each one should redirect to.”
For pages that have moved for good, use a permanent redirect. Google’s guide to redirects recommends “a permanent server-side redirect whenever possible” when a page’s URL changes, and says the 301 and 308 status codes mean “a page has permanently moved to a new location.” Permanent redirects show the new address in search results; temporary ones keep showing the old one. If you’ve heard that a 301 redirect costs you SEO value, the site move guide says “301 and other permanent redirects don’t cause a loss in PageRank.”
Point each old URL straight at its final page. Googlebot can follow up to 10 redirect hops, but the site move guide advises “redirecting to the final destination directly,” and otherwise keeping chains “ideally no more than 3 and fewer than 5.” Look for redirects left from an earlier redesign that point at pages you’re about to move, and update them too. Check 6 of our technical SEO checklist covers redirect types and hops.
How you add the redirects depends on your setup. Google mentions rules in an .htaccess file on an Apache server or “redirect functions in your CMS,” with client-side redirects only “as a last resort.” On Apache, each row of the map can become one line in the format Google’s redirect guide shows:
# Apache (mod_alias): one line per row of the redirect map
Redirect permanent "/weddings.html" "https://example.com/weddings/"
Redirect permanent "/zones.html" "https://example.com/delivery/"
Step 3: Decide what happens to pages with no new match
Redirect an old page only when the new site has a clear replacement. If the page is gone and nothing similar replaces it, let it return a 404 or 410.
Google’s guide to crawling errors covers both cases. If a page “has moved or has a clear replacement on your site,” return a 301. If you removed it and “there’s no replacement page on your site with similar content,” return a 404 (not found) or 410 (gone). Search Console’s Page indexing help adds that 404 responses “are not necessarily a problem, if the page has been removed without any replacement.”
Sending every leftover URL to the homepage doesn’t give visitors what the old link promised. A helpful 404 page does more: Google suggests links to your most popular pages and your home page, as long as the server still returns a real 404 status code.
Step 4: Test on a staging copy Google can’t index
Build and test the new site at a temporary address, and keep that copy out of Google until launch.
Google’s hosting guide suggests a testing environment, “perhaps with IP-restricted access,” and says that to keep a test site from being indexed, you can “add the noindex robots rule to the HTML or the HTTP headers of your pages.” Its page on controlling what you share says password protection also keeps content out of Google Search. A robots.txt block alone doesn’t, and checks 1 and 3 of our technical SEO checklist for business websites explain why.
Write down every block you add. Google’s site move guide says to prepare what robots.txt should look like at launch and “a list of URLs from which you’ll remove the noindex rules when you start the site move.”
On staging, check:
- Pages, images, forms and downloads, the list Google gives for testing a new host.
- Each new page’s canonical tag, which Google says should be “self-referencing.”
- Menus, buttons and internal links, changed to the new URLs instead of leaning on redirects.
- A new XML sitemap that lists only the new URLs.
Step 5: Move day
On launch day, turn on the redirects, remove the staging blocks and confirm that everything points at the new URLs:
- Turn on the redirects. For a small or medium site, Google recommends “moving all URLs on your site simultaneously instead of moving one section at a time.”
- Remove every temporary block, including the noindex rules, password and robots.txt lines you used on staging.
- Check canonical tags on the live site. Google says to make sure they “are using the new URLs.”
- Test the redirects. Google suggests the URL Inspection tool for single URLs, “or command line tools or scripts to test large numbers of URLs.” Confirm each old URL lands on its new page in one hop.
- File a change of address if the domain changed.
- Submit the new sitemap in Search Console. “This will help Google learn about the new URLs,” Google says.
- For a hosting change, update DNS and shut the old hosting down only once “the traffic to the old provider reaches zero.”
If you can choose the date, Google suggests moving during a quieter stretch if your traffic “is seasonal or dips on certain weekdays.”
When to use Google’s Change of Address tool
Use it only when you move from one domain or subdomain to another. Google’s Change of Address help says to use it “after you’ve moved and redirected your site,” and not for HTTP to HTTPS, moving pages within your site, switching between www and non-www on the same domain, or changing hosts without user-visible URL changes. You must own both Search Console properties under the same Google account, and Google says to “use this tool for all subdomain variants of the old domain, including www and non-www.”
Step 6: Update links outside your site
Redirects catch old links, but Google says “redirects are slow for users,” so update the links you control and ask about the ones you don’t. Its site move guide lists:
- Links from other sites. Contact them, “prioritizing your efforts by the number of inbound visits for each link.”
- Profile links, “such as from Facebook, Twitter, and LinkedIn.”
- Ad campaigns, pointed at the new landing pages.
Add your Google Business Profile’s website link to that list. Business Profile Help says to enter the full URL, including the http:// or https:// part, and that Google reviews changes before they go live on your profile. For directories and other sites that list your business, the advice on keeping your business details consistent across the web (Step 5 of our local SEO guide) applies to your new website address too.
Step 7: Watch Search Console after the move
Expect some movement, then watch the new URLs replace the old ones and fix errors as they appear. Google says that “to consider a site move complete, Googlebot will have to visit every URL on your old and new site at least once,” and the move happens one URL at a time.
| Where to look | What Google says you should see |
|---|---|
| Sitemaps report | The old URLs’ indexed count “would drop to zero with a corresponding increase of indexing of the new URLs” |
| Page indexing report | Old URLs under Page with redirect, which “will not be indexed,” and no “spike in other errors” |
| Performance report | The new URLs “getting search impressions and clicks” as more of them are indexed |
| Server logs | Googlebot crawling the new site, and no URLs that “unexpectedly return HTTP error status codes” |
| Crawl rate, after a hosting change | “a temporary drop in Googlebot’s crawl rate immediately after the launch, followed by a steady increase over the next few days” |
If you keep the old sitemap submitted to track the switch, Google says warnings about its URLs redirecting are “normal and you can ignore these warnings.” Make sure your hosting can take extra load, too: “after a migration, Google will temporarily crawl your new site more heavily than usual.”
Pages on the new site that Google crawls or discovers but leaves out of its index are a separate question, covered in our guide to crawled currently not indexed. If traffic drops and doesn’t recover, Google’s traffic drop guide says to “check the site move troubleshooting section for common mistakes,” and our guide to Google algorithm updates covers ruling out the other usual causes.
How long to keep your redirects
At least a year, and longer for your visitors’ sake. Google’s site move guide says to keep them “for as long as possible, generally at least 1 year,” which gives Google time “to transfer all signals to the new URLs, including recrawling and reassigning links on other sites that point to your old URLs.” It adds: “From users’ perspective, consider keeping redirects indefinitely.”
After a change of address, Google’s help page sets a floor of 180 days, longer “if you still see any traffic to them from Google Search,” and recommends paying for the old domain “for at least a year to prevent others from buying and using your abandoned domain for malicious purposes.”
Common website migration mistakes
Google’s troubleshooting section and the steps above point to the same short list:
- Staging blocks left on. “Don’t forget to remove any noindex or robots.txt blocks that were only needed for the migration.”
- Redirects to pages that don’t exist. Google says it frequently sees “people redirecting to the wrong (non-existent) URLs on the new site.” Test every row.
- Chains and loops, which the Page indexing report lists as redirect errors.
- A sitemap that still lists old URLs. “Be sure that your sitemaps are all updated with the new URLs.”
- Letting the old domain lapse, which Google warns lets others buy it.
A worked example (made up)
Pemberfold Flowers is a made-up florist in the made-up town of Velloway. The owner is moving her 38-page site from an old site builder to a new platform on the same domain, and most page addresses will change. Same domain, so no change of address.
She builds her URL list from the sitemap, the Performance report’s Pages tab and the Links report, which shows two wedding blogs linking to her flower care PDF. Part of her map:
| Old URL | New URL | Status | Note |
|---|---|---|---|
/index.html | / | 301 | Homepage |
/weddings.html | /weddings/ | 301 | Same page, new address |
/weddings-2.html | /weddings/ | 301 | Used to redirect to /weddings.html; now points at the final page |
/delivery.html | /delivery/ | 301 | Same page, new address |
/zones.html | /delivery/ | 301 | Merged into the delivery page |
/flower-care.pdf | /flower-care/ | 301 | PDF turned into a page; two sites link to it |
/spring-sale.html | none | 410 | Old promotion, nothing similar on the new site |
She tests on a password-protected staging address and launches with the move day steps above. Then she checks her Business Profile and social profiles for links to old page addresses, emails the two wedding blogs about the new flower care page, and checks the Sitemaps and Page indexing reports each week while Google recrawls.
How we handle this for clients
On-site technical SEO is part of our monthly plan. If you’re planning a redesign, a new platform or a new domain, we work through steps like these on your site, fix what we find and list each task in your monthly report. You keep ownership and full control of your website and accounts and give us access to do the work.
Frequently asked questions
Will a website migration hurt my rankings?
Expect some movement, and no one can promise how a move will turn out. Google says to expect “temporary fluctuation in site ranking during the move,” and that a medium-sized site can take a few weeks or more before Google shows the new URLs in place of the old ones. Google also says that combining a move with a redesign of the content and URL structure will probably mean some traffic loss while it reassesses the pages.
How long should I keep redirects after a site move?
At least a year. Google’s site move guide says to keep them “for as long as possible, generally at least 1 year,” and to consider keeping them indefinitely for visitors. After a change of address, keep them at least 180 days, longer while Google Search still sends traffic to them, and keep paying for the old domain for at least a year.
Should I redirect old pages to my homepage?
Not as a catch-all. Google says to redirect a page that “has moved or has a clear replacement on your site,” and to return a 404 or 410 for a removed page with no similar replacement. Your old homepage should redirect to the new one, and other pages to their own new versions. Sending them all to the homepage makes visitors start over.
Do I need Google’s Change of Address tool?
Only when you move from one domain or subdomain to another, such as example.com to example.org. Google says not to use it for HTTP to HTTPS, moving pages within your site, www and non-www changes on the same domain, or a new host with the same URLs. File it after your redirects are live.
Does changing web hosts affect SEO?
A hosting change that keeps every URL needs no redirects and no change of address. Google says it’s normal to see a temporary drop in Googlebot’s crawl rate right after launch, “followed by a steady increase over the next few days.” Keep your Search Console verification working, remove any test blocks and keep the old host running until its traffic reaches zero.
Is a website redesign a migration?
It is if your URLs change. Google’s site move guide covers URL path changes, so a redesign that renames pages needs a redirect map like any other move. A redesign that keeps every URL and your host isn’t covered by Google’s site move guides, but rerun your technical checks after launch, and follow Google’s advice to change one thing at a time.
Planning a move and want the SEO side handled every month? See what’s included in our plan, or send us a question first.
