Redesigning Without Losing the Traffic You Already Have

The drop is usually self-inflicted

A redesign that loses traffic rarely lost it because Google disliked the new look. It lost it because URLs moved, text was cut, internal links were restructured, or something technical broke quietly and nobody looked for three weeks.

All of that is preventable with a checklist, which is what this is.

Before you touch anything: take an inventory

1. Export every URL that has received a visit or an impression in the last twelve months, with sessions and clicks against each.
2. Export your top landing pages by search traffic. These are the pages that need protecting above all else.
3. Record current rankings for your priority terms so you have a before picture.
4. Crawl the existing site and save it. Titles, descriptions, headings, internal links, status codes.

This takes a morning and it is the difference between diagnosing a problem in an hour and guessing for a month.

Mistake one: changing URLs without a mapping

New CMS, new structure, tidier slugs — and suddenly a thousand URLs are 404s. Every one of those was an asset with links pointing at it.

If you change a URL, a 301 redirect to the closest equivalent page is not optional. Redirecting everything to the homepage is barely better than a 404 — search engines treat it as a soft 404 and users bounce.

Build the mapping as a spreadsheet before launch, old URL to new URL, one row per page. Then test it after launch with an automated crawl of the old list.

Mistake two: cutting the words that were doing the ranking

Modern design favours short pages. Search favours pages that answer the question thoroughly. A redesign that halves the copy on a page that ranks well will usually cost you that ranking.

The fix is not to refuse good design — it is to keep the substance and present it better: accordions, tabs, well-structured sections. Keep the text in the HTML.

Mistake three: launching with the staging site still indexed

A staging environment that was crawlable now competes with the live site for the same content, and sometimes wins. Equally common in the other direction: the noindex used on staging gets deployed to production, and the whole site drops out of the index within a week.

• Protect staging with authentication, not just robots.txt
• Check the live site's robots directives on launch day, before the coffee
• Verify the canonical tags point at production, not staging
• Submit the new sitemap and watch coverage reports for a fortnight

Launch day checklist

1. Crawl the old URL list and confirm every one returns a 200 or a single 301 to a relevant page
2. Check robots.txt and meta robots on a sample of live pages
3. Confirm analytics and conversion tracking still fire — this breaks constantly and silently
4. Submit the sitemap and request indexing for the top twenty pages
5. Check Core Web Vitals on the new templates, especially layout shift on hero sections

What to expect afterwards

Some fluctuation for two to four weeks is normal even when everything is right — search engines need to recrawl and reassess. A 10–20% wobble that recovers is not a crisis.

What is a crisis: an immediate drop of more than a third, or a decline that keeps deepening after three weeks. In both cases go back to redirects and indexability first. It is nearly always one of those two.

Frequently asked questions