How to Redesign Your Website While Reducing the Risk of Losing Rankings
Nobody can promise that a redesign will leave your Google rankings untouched – Google itself tells site owners to expect temporary fluctuation in rankings when a site moves. What you can do is remove the avoidable causes of lost traffic, and those are well known: old URLs that disappear without redirects, content that ranked being cut or merged carelessly, and leftovers from development such as a noindex rule. Plan for them before the new design is built, not in the week after launch.
First, be clear about what is changing
"Redesign" covers very different projects, and the risk grows with how much changes at once:
| Type of change | What changes for Google | Main risk |
|---|---|---|
| New design, same URLs and content | Layout and code | Lowest; check that texts, headings and internal links survive the new templates |
| New hosting, same site | Only the server | Downtime, or a firewall blocking Googlebot; Google says a short dip in crawling right after the move is normal |
| New platform or CMS | Often URLs, templates and technical tags | URL patterns change unnoticed; canonical, hreflang and meta tags get lost |
| New site structure | URLs, merged and removed pages | Pages that ranked disappear or are merged into weaker ones |
| New domain | Every URL | Highest; every redirect matters |
Google's site move guide advises planning changes one after the other rather than all at the same time. If you can, keep the URLs while you change the design, or move to the new domain first and redesign later. When that isn't practical – and often it isn't – the steps below matter even more. If you are still deciding whether you need a full redesign at all, see website redesign or small improvements.
Before you start: record what you have
- A full list of URLs. Crawl the current site and combine the result with the sitemap, Search Console's Performance report (pages with impressions and clicks), your analytics (pages with visits) and the pages other sites link to. Google suggests starting with your most important URLs and including images, videos, CSS and JavaScript files, not only pages.
- A baseline. Export clicks, impressions, top queries and top pages from Search Console for as long a period as you can, and note how many enquiries or sales you get per month. Without this you can't tell later whether anything was lost.
- Your most valuable pages. Mark the pages that bring search traffic or enquiries. They get the most careful treatment in everything that follows.
Keep URLs where you can
The safest redirect is the one you don't need. If a page keeps existing with the same purpose, keep its address. Changing /services/roof-repair to /roof-repair-services only because a new system prefers that pattern adds risk without any benefit.
Map every changed URL to its new home
For every URL that does change, decide where it goes and write it down – old URL, new URL, notes. Then implement the map with these rules:
- Permanent server-side redirects (301 or 308). Google treats them as a strong signal that the new URL should be the one shown in results. Temporary redirects (302, 307) don't send that signal, and JavaScript redirects should be a last resort.
- The closest equivalent, not the home page. Google warns against redirecting many old URLs to one irrelevant destination, such as the home page of the new site, which may be treated as a soft 404.
- No chains. Google's crawlers follow up to 10 redirect hops, but every extra hop is one more thing that can break. Point each old URL straight at its final destination – including URLs that were already redirected after a previous redesign.
- Pages with no replacement. Redirect to the closest related page if there is one; otherwise let the URL return 404. Google notes that a 404 is not necessarily a problem when a page was removed without a replacement.
- Keep the redirects. Google recommends keeping them for as long as possible, generally at least a year.
Don't lose the content that ranked
Many redesigns lose traffic because of content rather than redirects. The new design calls for "less text", and a service page that ranked with a detailed description becomes three sentences and an icon. Before you shorten or merge a page, look up the queries it appears for in Search Console. If one new page replaces three old ones, it must actually contain what those three covered. Improve content during a redesign; don't remove what search visitors came for.
Also check what the new templates do with text. Headings turned into images, descriptions moved into sliders, or content that loads only after a click can leave Google with less than visitors see. Check your key pages with the URL Inspection tool in Search Console before and after launch.
Launch-day checklist
- Remove noindex rules and robots.txt blocks that were used on the staging site – Google's site move guide specifically reminds you of this.
- Give each new page a self-referencing canonical tag with its new URL.
- On a multilingual site, update hreflang to the new URLs. Each language version must list itself and all other versions, annotations that don't point back to each other are ignored, and the URLs must be absolute, including https. More in planning a multilingual website.
- Submit the new XML sitemap in Search Console.
- Update internal links – menus, footers, links inside texts – to the new URLs instead of relying on redirects.
- Carry over or improve titles, meta descriptions, structured data and image alt texts.
- Make sure analytics and conversion tracking work on the new site.
- If you move to a different domain or subdomain, use the Change of Address tool in Search Console; other kinds of changes don't need it.
After launch: check, then watch
- Test every redirect in your map with a crawler or a script, not by clicking a few by hand: the status code should be 301 or 308, and the target should load normally.
- Inspect your most important pages with the URL Inspection tool.
- Watch the Page indexing report. More "Page with redirect" entries for old URLs are expected; new "Not found (404)" or server errors on URLs that should work are not.
- Compare clicks and impressions with your baseline, by groups of pages, week by week.
Google's general rule is that a small to medium-sized site can take a few weeks for most pages to move, and larger sites take longer. Some movement during that time is normal. A steady decline on particular pages usually has a particular cause – a missing redirect, a page that lost its content, a forgotten noindex. For measuring over the longer term, see how long SEO takes and how to measure progress.
Example: splitting our own site into two domains
Until recently seoandweb.eu had two language versions in folders, /bg/ and /en/. The new site runs on two domains: Bulgarian on seoandweb.bg and English on seoandweb.eu. That was a domain change and a restructuring at the same time, so we:
- crawled the old site and recorded every URL;
- redirected seoandweb.eu/bg/page to seoandweb.bg/page and seoandweb.eu/en/page to seoandweb.eu/page, keeping the same page names;
- merged seven old service pages into one Services page;
- redirected the URLs of the previous seoandweb.bg site to their new equivalents;
- connected the two language versions with hreflang.
In total that meant about 45 permanent (301) redirects, all checked after launch. At the same time we introduced cookie consent with Google Consent Mode v2. Any change to consent or tracking changes what your analytics records, so when you compare search performance before and after a move like this, Search Console's clicks and impressions, which don't depend on your site's tracking code, are the steadier reference. Ours is a small site, but the steps are the same for a shop with thousands of URLs – the map is just longer and the checks have to be automated.
If you are planning a redesign, a new platform or a domain change, the URL map and the content review belong in the project from the first week, not the last. That is how we approach website development and redesign. Get in touch to plan yours.
Sources
- How to move a site with URL changes – Google Search Central
- Redirects and Google Search – Google Search Central
- How HTTP status codes, and network and DNS errors affect Google Search – Google Search Central
- Tell Google about localized versions of your page – Google Search Central
- Changing your web hosting and SEO – Google Search Central
- Page indexing report – Search Console Help