The six sheets › Sheet VI
Sheet VI of VI
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.
A permanent redirect tells Google to show the new URL in results; a temporary one keeps the old URL showing.
| Kind | Permanent | Temporary | Google’s note |
|---|---|---|---|
| Server-side HTTP | 301, 308 | 302, 303, 307 | The best way to make sure Google and people reach the right page; needs access to server configuration. |
| Meta refresh | Instant (0 seconds) | Delayed (more than 0) | An alternative where server-side redirects aren’t possible. |
| JavaScript location | Treated as permanent | None listed | Only if neither of the above is possible; if rendering fails, Google might never see it. |
| “Crypto” redirect: a link saying the page moved | Possibly | None listed | Don’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.
Before the move
rel="canonical" on each new URL, hreflang pointing at new URLs, internal links changed to new URLs.Move day
noindex rules that kept the new site hidden, and check canonicals now use the new URLs.If the domain changed
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.
The weeks after
180 days, and a year
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.
Google’s troubleshooting list is short, and worth reading before the move rather than after:
noindex or robots.txt block left over from development;The sheets on robots.txt, sitemaps and canonical URLs cover each of those pieces in more depth.