Moving or redesigning a website: reducing search visibility risks
Plan URL mappings, redirects, launch checks and monitoring to reduce search visibility risks during a site move or redesign.
- Change one thing at a time
- Google's example: move the domain, then change the layout - not domain, CMS and layout together.
- Map every old URL
- Permanent server-side redirects (301, 308) straight to the final destination; avoid chains and irrelevant catch-all targets.
- Expect temporary ranking changes
- Google says medium sites can take a few weeks or more to show new URLs, and large sites longer. Keep redirects as long as possible, generally at least a year.
All wording checked against Google's site-move documentation linked in Sources; Google promises no ranking recovery timeline.
If a redesign changes your URLs, Google has to learn the new addresses. Google's guide to site moves covers HTTP to HTTPS, domain changes and URL path changes. We read it in full on 15 November 2026. Everything attributed to Google below comes from that page. It does not cover infrastructure-only changes such as hosting, where URLs stay the same.
The five steps
- Learn the general best practices.
- Prepare the new site and test it.
- Map every old URL to its new URL.
- Start the move with server redirects.
- Monitor traffic on old and new URLs.
- Learn the general best practices.
- Prepare the new site and test it.
- Map every old URL to its new URL.
- Start the move with server redirects.
- Monitor traffic on old and new URLs.
General rules from Google
- Split a large move into smaller steps where technically possible, starting with a section that changes rarely. Google notes a test section is not necessarily representative of a whole-site move.
- Change one thing at a time. Its example: move the domain, then change the layout, not domain, CMS and layout together.
- Pick a lower-traffic time. Fewer people are hit by problems and more server capacity goes to Googlebot.
- Expect temporary ranking changes. Google says medium sites can take a few weeks or more to show new URLs and large sites longer. A sitemap can speed discovery.
- Link credit: Google says 301 and other permanent redirects do not cause a loss in PageRank.
- Be patient. The move is done when Googlebot has visited every old and new URL at least once, URL by URL, with no fixed crawl frequency.
- All at once or in sections? Google recommends small and medium sites move all URLs at the same time; large sites may go section by section.
Preparing the new site
- Set up the CMS (preferably the one the old site used) and import content.
- Move images and downloads such as PDFs, which may already get traffic or links.
- For HTTPS, install the TLS certificates.
- Prepare robots.txt. If you blocked crawling or used noindex in development, write down what the files should look like at launch and which URLs need noindex removed.
- Where removed content has no relevant replacement, return 404 or 410. If content is merged into a relevant replacement, redirect the old URLs to that replacement, as described below.
- Verify every variant of both sites in Search Console (www and non-www, HTTP and HTTPS). Check that your verification method still works after the move.
- Review the current Search Console settings available for the new site and any existing disavow file. Do not assume every historical setting still exists. On a recently bought domain, check for old manual actions and leftover URL removals.
- Set up analytics for both sites.
- Make sure the server can cope: Google says it temporarily crawls the new site more heavily after a move because old-URL crawls are redirected too. Tell your host if the site is very large.
Building the URL map
- Small simple moves such as a domain change may only need a wildcard server redirect. Complex ones need a list of old URLs mapped to new ones.
- Find old URLs from sitemaps, server logs or analytics (top traffic), Search Console's links report, and the CMS. Include images, videos, JavaScript and CSS files.
- On the new site: give each new URL a self-referencing rel="canonical" tag, update hreflang annotations if you use them, and change internal links to the new URLs.
- Save a sitemap of the new URLs and a list of sites that link to your old URLs.
Redirect plan
- Use server-side permanent redirects, such as 301 and 308, if you can. Client-side redirects are a last resort.
- Avoid chains. Googlebot can follow up to 10 hops, but Google advises redirecting straight to the final destination, and if not possible, keeping chains ideally to no more than 3 and under 5.
- Do not redirect many old URLs to one irrelevant page such as the new homepage: it can confuse users and may be treated as a soft 404. Redirecting several old pages to one new page that consolidates them is fine.
Launch day
- Turn on the redirects.
- Check canonical tags and robots meta rules (remove migration-only noindex).
- Test redirects, with the URL Inspection tool for single URLs or scripts for many.
- For a change of domain or subdomain only, submit Change of Address in Search Console for every verified variant of the old domain. It is not needed for HTTP to HTTPS, www to non-www, or path changes within a domain.
- Keep redirects as long as possible, generally at least a year per Google. For users, consider keeping them indefinitely, and update your own links and high-volume incoming links, since redirects are slow.
- Submit the new sitemap; the old one can then go.
Then update internal links, external links (contact the sites on your list, most-visited first), social profile links and ad campaigns.
Monitoring
Watch old and new sites in Search Console (sitemaps, index coverage, search queries) and in server logs and analytics. Google says old-site traffic should fall and new-site traffic rise. Warnings on the old-URL sitemap that its URLs redirect are normal.
Common mistakes Google lists
Leftover noindex or robots.txt blocks (and a missing robots.txt should return 404); wrong or non-existent redirect targets; spikes of other crawl errors; not enough server capacity; sitemaps not updated.
Limits
One Google page, read in full. It gives no promise that rankings or traffic will return, and it does not say how long any specific site will take. The third-party checklists and tools it links to were not read. Deleted-content handling beyond 404/410 is not detailed on the page. See our articles on redirects (301, 302, 308) and sitemaps for details.
By Omnistu.