The six sheets › Sheet VI

Sheet VI of VI

Moving a website: migrations and redirects

To move a site or change its URLs while keeping the harm to your Google Search results as small as possible, map your old URLs to their new ones, then redirect each old URL to its new home with a permanent server-side redirect. After that, it is mostly patience: Google says a small to medium site can take a few weeks for most pages to move, and larger sites take longer.

General information from Google’s own documentation, not advice for your particular site. Google’s Search Central documentation is the place to check before you change anything, and it is updated over time.

Renaming streets is easy on paper. The hard part is that letters, signs and people’s memories still carry the old names. A migration is the same problem: other sites, bookmarks and Google’s index all know your old addresses, and every one of them needs a forwarding note.

Google’s guide covers three kinds of move: HTTP to HTTPS, a change of domain name (or merging domains), and changes to URL paths. If the URLs stay the same and only the hosting changes, Google has a separate guide.

Redirects, and which kind to use

A permanent redirect tells Google to show the new URL in results; a temporary one keeps the old URL showing.

Redirect types Google recognises, roughly from most to least reliably understood
KindPermanentTemporaryGoogle’s note
Server-side HTTP301, 308302, 303, 307The best way to make sure Google and people reach the right page; needs access to server configuration.
Meta refreshInstant (0 seconds)Delayed (more than 0)An alternative where server-side redirects aren’t possible.
JavaScript locationTreated as permanentNone listedOnly if neither of the above is possible; if rendering fails, Google might never see it.
“Crypto” redirect: a link saying the page movedPossiblyNone listedDon’t rely on it unless there’s no other choice; not all search engines recognise it.

Two reassurances from Google: 301 and other permanent redirects don’t cause a loss in PageRank, and it isn’t unusual for Google to keep showing old URLs for a while after a domain move, as “alternate names” that fade without you doing anything.

  1. Before the move

    Prepare the new site and the map

    • Change one thing at a time. Google’s example: move the domain first, then change the layout, not both at once.
    • Choose a quiet time if your traffic has seasonal or weekly dips.
    • List your old URLs, most important first: from your sitemaps, server logs or analytics, Search Console’s links report, and your CMS. Include images, video, JavaScript and CSS.
    • Map each old URL to a new one, in a database or as rewrite rules for common patterns.
    • Update the new site: a self-referencing rel="canonical" on each new URL, hreflang pointing at new URLs, internal links changed to new URLs.
    • Return 404 or 410 for content you aren’t moving.
    • Verify both sites, every variant, in Search Console (www and non-www, HTTP and HTTPS), and carry over any verification file or tag.
    • If the domain is newly bought, check its history: manual actions for earlier spam, and leftover URL removals from the previous owner.
    • Plan for more crawling; Google crawls a moved site more heavily than usual for a while.
  2. Move day

    Turn on the redirects

    • Small or medium site: Google recommends moving all URLs at once. Large sites can move in sections, which makes problems easier to spot.
    • Redirect straight to the final address. Googlebot can follow up to 10 hops, but Google advises ideally no more than 3 and fewer than 5, because chains slow users down.
    • Don’t send everything to the home page. Many old URLs redirected to one irrelevant page can confuse users and may be treated as a soft 404. Redirecting several old pages to one page that genuinely merges them is fine.
    • Remove development blocks. Lift any robots.txt or noindex rules that kept the new site hidden, and check canonicals now use the new URLs.
    • Test the redirects with the URL Inspection tool, or with scripts for many URLs.
    • Submit the new sitemap in Search Console.
  3. If the domain changed

    Tell Google with Change of Address

    Search Console’s Change of Address tool is for moves from one domain or subdomain to another, used after the site has moved and redirects are working. It isn’t needed for HTTP to HTTPS, www to non-www on the same domain, moving paths within a domain, or a move with no visible URL change.

    You must own both properties with the same Google account, and the tool doesn’t move subdomains, so run it for each verified variant of the old domain, including www and non-www. Google also advises against chaining moves (A to B, then straight on to C) and against folding several sites into one location at once.

  4. The weeks after

    Update links and watch both sites

    • Ask sites that link to you to update their links, prioritising those that send the most visits; update your profiles and ad campaigns too.
    • Expect rankings to fluctuate while Google recrawls; Google calls this normal.
    • In Search Console, watch indexed URLs in the old sitemap fall and in the new sitemap rise. Warnings that old URLs redirect are expected.
    • Check server logs for Googlebot and for URLs returning unexpected errors.
  5. 180 days, and a year

    Keep the forwarding notes

    After a Change of Address, Search Console shows a move notification for 180 days, and Google asks you to keep redirects for at least that long, and longer while Google Search still sends traffic to them. After the 180-day period, Google treats the old site as unrelated if it is still present and crawlable.

    For any move, Google’s guide says to keep redirects as long as possible, generally at least a year, and from users’ point of view, consider keeping them indefinitely. It also recommends continuing to pay for the old domain for at least a year so nobody else can buy it and use it for malicious purposes.

The mistakes Google sees most

Google’s troubleshooting list is short, and worth reading before the move rather than after:

  • a noindex or robots.txt block left over from development;
  • redirects pointing to the wrong, non-existent URLs;
  • a spike in other crawl errors on the new site;
  • a server without the capacity for heavier crawling;
  • sitemaps not updated with the new URLs.

The sheets on robots.txt, sitemaps and canonical URLs cover each of those pieces in more depth.