How to Redesign a Website Without Losing Google Traffic

You can redesign a website without losing Google traffic if you treat the relaunch as a technical move, not just a visual one. Keep every URL that earns traffic, 301-redirect every URL that has to change to its closest equivalent, make sure nothing from staging blocks indexing, and watch Search Console closely for the first weeks. The design itself is rarely what hurts you.

Reports of traffic loss after a relaunch are common enough to take seriously. One vendor analysis published in August 2026 tied badly executed ecommerce migrations to organic traffic losses of 20 to 40 percent, with recovery taking months. It is a vendor study, so read it as a direction rather than a law, but the pattern matches what practitioners describe: the loss comes from execution, not from having a new look.

Why do redesigns lose Google traffic?

Because Google does not rank your design, it ranks URLs. Each page on your domain has an address, a history of links pointing to it and a record of what it answers. When a redesign changes those addresses, merges pages or deletes them without telling Google where they went, that accumulated trust has nowhere to land.

Most of the damage comes from a short list of causes: URLs that changed with no redirect, redirects that send everything to the homepage, a staging setting that tells search engines to stay away, pages that quietly disappeared because they did not fit the new sitemap, and content that was rewritten so heavily that it no longer answers the query it used to rank for. None of these is visible on launch day. The site looks perfect. The graph drops three weeks later.

A useful rule: a redesign that changes colours, layout and copy but keeps the URLs is low risk. A redesign that restructures the site map is a migration, whether or not anyone called it that, and it deserves migration-level care.

What should you do before the redesign starts?

Start with an inventory, not with mood boards. Export every URL you can find: your current sitemap, a crawl of the live site, the pages listed in Search Console, and the pages that receive organic visits in your analytics. Old sites are almost always bigger than their owners think, with campaign pages, PDFs and old blog posts that still bring visitors.

Then record a baseline. Note organic sessions, impressions, clicks and the top 20 landing pages for the last three months. Without a baseline you cannot tell a normal post-launch dip from a real problem, and you cannot show a client or a boss that it recovered.

Finally, sort the pages into three groups: keep at the same URL, move to a new URL, and retire. Be stingy with the third group. A page with no traffic and no links can go, but a page that ranks, even for one odd phrase, is an asset you are about to throw away. If you must merge pages, merge them into the page that best matches the same question.

How do you handle redirects properly?

Every old URL that changes needs a permanent redirect (301, or 308) to the most relevant new page. Search Engine Journal's summary of Google's guidance puts it simply: send each old page to its equivalent, and pages you are dropping entirely do not need one. Do not point dozens of different old pages at the homepage. To a crawler that looks like a soft 404, and you lose the relevance the old pages had built.

Avoid chains too. If an old URL goes to a second URL that goes to a third, fix it so the first points straight at the last. Each extra hop slows crawling and is one more thing that can break.

How long should the redirects stay? Google's Gary Illyes has said at least a year, and indefinitely is better when you can manage it. In practice, never delete a redirect just to tidy the config file. It costs almost nothing to keep and the old links never fully disappear from other people's websites.

Which technical settings break silently?

These are the ones we check on every relaunch, because none of them throws an error:

- A `noindex` tag or a `Disallow: /` rule left over from the staging site, which can remove a whole site from results within days.

- Canonical tags pointing at the staging domain or at the old URLs instead of the new ones.

- A sitemap that still lists old URLs, or that was never submitted for the new structure.

- Structured data that existed on the old pages and was not rebuilt, so rich results vanish.

- Internal links hard-coded to the old addresses, so every click goes through a redirect.

- Analytics or tag manager that was not reinstalled, so the weeks you most need to measure are a blank.

- On a bilingual site, hreflang annotations that still point at the previous URL patterns.

The reason a custom build helps here is practical rather than magical. When routes and redirects live in code, the whole URL map can be read and compared against the old inventory before launch, and a script can crawl the staging build and flag every old URL without a destination. Doing that by hand across hundreds of pages is exactly the kind of tedious check that gets skipped.

Should you also change content and speed during the redesign?

Be careful about doing everything at once. If you change URLs, rewrite the copy and swap the platform in one release, you will not know which change moved the numbers. Where you can, keep the headings and the core answer on pages that already rank, and improve around them. Faster loading is a safe change to make, and Core Web Vitals are worth fixing in the same project as long as the content that earns traffic stays recognisable.

If the redesign is large, consider staging it: first the platform and structure with minimal content change, then the visual and copy refresh once the traffic is stable.

What should you monitor after launch?

On launch day, run a crawl of the live site and confirm there is no noindex, that canonicals point at the right pages, and that a sample of old URLs reach the right destinations in a single hop. Submit the new sitemap in Search Console, and consider keeping the old one submitted for a while so Google rediscovers the redirects sooner.

Over the next two weeks, check the indexing and crawl reports daily for 404 spikes. Expect a small dip in the first weeks, even on a clean move, because Google needs time to process the changes; Search Engine Land notes it can take several months for everything to settle. A clean relaunch usually stabilises and returns to the baseline. A broken one keeps sliding, and that is your signal to go back to the redirect map.

What should you ask a web agency before you sign?

Three questions reveal most of the risk. Will the URL structure change, and where is the mapping document? Who verifies the redirects after launch, and how? Is the monitoring period part of the scope or a separate invoice? A vague answer to any of them usually means the technical migration was assumed, not planned.

If you are planning a relaunch, we would rather map the URLs before we design a single screen. Our web design service includes that groundwork, you can see how a project runs in how we work, and the Black Friday prices continue through Christmas, with −50% on every package until 31 January 2027.