How to redesign your website without losing your Google rankings

A new website should bring more enquiries, not fewer. Yet a redesign is one of the most common reasons a business suddenly loses its search traffic. The cause is rarely the design itself. It is usually a handful of avoidable technical mistakes made during the switch-over.

Here is the process we follow to protect rankings through a relaunch.

1. Benchmark before you touch anything

You cannot tell whether a launch went well without a baseline. Before work starts, record:

• Organic traffic and conversions by page, from Google Analytics.
• Clicks, impressions and average position by page and query, from Google Search Console.
• A full crawl of the current site, listing every URL, title, meta description and heading. Tools such as Screaming Frog do this in minutes.
• Your most-linked pages, from Search Console’s Links report or a backlink tool.

2. Decide what happens to every important URL

This is the step that matters most. For every URL that gets traffic, has backlinks or appears in search results, decide on one of three outcomes:

• Keep: the URL stays exactly the same. Simplest and safest.
• Move: the page lives at a new address. Add a permanent (301) redirect from old to new.
• Retire: the page is removed. Redirect it to the closest relevant page, not to the homepage by default.

Put this in a spreadsheet with the old URL in one column and the new URL in the next. It becomes both your redirect list and your testing checklist.

3. Protect the content that ranks

Pages rank because of what they say. Redesigns often “simplify” copy and quietly remove the paragraphs, FAQs or product details that were earning the traffic. Before cutting content from a page that performs well, check which queries it ranks for in Search Console and make sure the new version still answers them. Improving a ranking page is fine; hollowing it out is not.

Carry across the on-page basics too: title tags, meta descriptions, a single clear H1, image alt text and internal links.

4. Build on a staging site that Google cannot see

Develop the new site on a separate staging address and keep it out of search results with password protection. A noindex tag works too, but it is easy to forget to remove at launch, which is one of the most damaging and most common mistakes we see.

5. Test before launch

• Crawl the staging site and look for broken links, missing titles, duplicate titles and pages that are not linked from anywhere.
• Check that canonical tags point to the live domain, not the staging address.
• Test pages on real phones and run key templates through PageSpeed Insights.
• Confirm analytics and conversion tracking fire on the new templates.

6. Launch day

• Remove password protection and any noindex tags. Check robots.txt is not blocking the site.
• Upload the redirects and test every row of your spreadsheet: each old URL should land on its new page with a 301 status in one hop.
• Make sure the whole site loads on HTTPS and that one version of the domain (with or without www) redirects to the other.
• Submit the new XML sitemap in Search Console.

7. Watch closely for the next month

Some movement in the first couple of weeks is normal while Google recrawls the site. Check Search Console daily at first for crawl errors, 404s and pages dropping out of the index, and compare traffic against your benchmark. Most problems found early, such as a missed redirect or a page accidentally set to noindex, can be fixed before they do lasting damage.

The short version

Keep URLs where you can, redirect them where you cannot, keep the content that ranks and test everything before and after launch. A redesign done this way should hold its rankings and, with a faster, clearer site, usually improve them.