Website Redesign SEO: Keep Your Rankings and Leads

You are about to sign a redesign contract. The mockups look great. Nobody in that meeting said the words 'redirect map', and the statement of work has a line item for 'SEO-friendly build' with no definition attached.

That is how service businesses lose half their organic leads in a month. Not because the new site is ugly. Because four specific, boring, entirely preventable things got broken during the cutover, and nobody was assigned to check them.

This is the checklist. Run it before your developer flips DNS, not after your calls dry up.

Does a website redesign always cost you rankings?

No. A redesign that keeps every URL identical and every page's words intact should cost you close to nothing, because Google's ranking systems read URLs, links, and text — not your color palette. Traffic loss is not a side effect of new design. It is a side effect of changing the things Google indexes without telling Google.

There are two very different projects people call 'a redesign', and they carry completely different risk:

The honest verdict: a reskin is safe and a rebuild is not, and most agencies sell you a rebuild while pricing the risk of a reskin. If your current URLs work and your pages rank, the cheapest SEO decision available to you is to keep the URLs. Ask for that in writing. We cover the platform side of that trade-off in our breakdown of Next.js versus WordPress for a marketing site.

What are the four failure modes behind almost every redesign traffic loss?

Almost every redesign traffic drop traces to one of four causes, and each one has a different fingerprint in Search Console. Diagnose the mode first; do not start 'improving content' at random.

Three of these four are the developer's doing, not the designer's. That is exactly why nobody catches them: the person who signed the contract was reviewing mockups, and the person who could have caught it was never invited.

What belongs in a redirect map - and why 'redirect everything to the homepage' kills you

A redirect map is one row per old URL, mapped to exactly one new URL, and Google explicitly warns against the lazy version. Its site-move documentation states: 'Don't redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site. This can confuse users and might be treated as a soft 404 error.' A soft 404 does not rank. It does not even stay indexed.

Google does allow one exception: 'if you have consolidated content previously hosted on multiple pages to a new single page, you can redirect the older URLs to that new, consolidated page.' Consolidation is fine. Dumping the whole site into the homepage is not.

Build the map as a spreadsheet before a single new page is coded. Six columns, no more:

Use a permanent redirect, not a temporary one. Google's redirect documentation is explicit: with a permanent redirect, 'the indexing pipeline uses the redirect as a signal that the redirect target should be canonical.' With a temporary redirect, 'the indexing pipeline doesn't use the redirect as a signal that the redirect target should be canonical.' A 302 on a permanent move tells Google to keep the old URL as the canonical — which is the opposite of what you want.

Keep the redirects up. Google's guidance: 'Keep the redirects for as long as possible, generally at least 1 year. This timeframe allows Google to transfer all signals to the new URLs.' Redirects are not a launch-week task you delete during the next cleanup sprint.

Why does a prettier site with 60% fewer words rank worse?

Because Google ranks the text, and a redesign that cuts a 1,400-word service page down to a 300-word hero and three icons has deleted most of what the page was ranking for. This is the failure mode that returns a clean 200 status, passes every technical check, and still bleeds rankings for months.

Designers are not villains here. They are optimizing for a visual comp, and a wall of text ruins a comp. But the copy on your top service pages is a ranking asset with a dollar value. It gets treated as filler because nobody put a number on it.

So put a number on it. Before the rebuild, export your top 20 pages by organic clicks and record, for each: word count, H1 text, title tag, the H2 set, and the internal links pointing in. That is your content parity baseline. After launch, compare. Anything that lost its H1 or more than about 20% of its body copy goes back in — the design accommodates the content, not the other way around.

If your old page copy is already gone and you never took a baseline, pull it from the Wayback Machine before the crawl of your old site ages out. It is not a guarantee, but it is free and it has saved more than one migration. A structured content audit is the version of this you do on purpose instead of in a panic.

What is the go/no-go checklist to run before your developer flips DNS?

Nine checks, and any single failure is a no-go — the launch date moves, not the checklist. Every one of them takes minutes to verify and days to weeks to recover from if missed.

The staging noindex check is first for a reason. Google's own documentation on blocking indexing spells out the trap that makes it so hard to spot: 'For the noindex rule to be effective, the page or resource must not be blocked by a robots.txt file, and it has to be otherwise accessible to the crawler.' Teams block staging in robots.txt, then also add a noindex tag, then ship the tag to production. The site goes dark and the analytics look normal for two weeks, because rankings decay on a delay.

If you want a second pair of eyes on the build before it goes live, that is exactly what a pre-launch technical SEO pass is for. It is a lot cheaper than a recovery.

What changes if you are also changing domain names?

A domain change adds three obligations on top of everything above, and the biggest one runs on a 180-day clock. Google's Change of Address tool 'forwards various signals from the old site to the new site, and tells Google to prefer the new site over the old when determining canonical pages' — but per Google's own documentation, 'these actions continue for 180 days after you start migration in Search Console.'

After that window, in Google's words, 'Google does not recognize any relationship between the old and new sites.' So the redirects have to outlive the tool. Google's advice is to 'maintain the redirects for at least 180 days — longer if you still see any traffic to them from Google Search', while the broader migration guide says keep them at least a year. Take the year.

Blunt advice: do not change the domain and rebuild the site in the same week unless you have a genuine business reason. If both happen at once and traffic drops, you cannot tell which one did it, so you cannot fix it. Sequence them a month apart and you keep the ability to diagnose.

Your traffic already dropped - how do you diagnose which failure mode you have?

Start with Search Console's Page Indexing report and compare the four weeks after launch to the four weeks before. The report tells you which of the four failure modes you have in about fifteen minutes, and the signature is different for each one.

On timing: Google says of a migration that 'a small to medium-sized website can take a few weeks for most pages to move, and larger sites take longer.' So a two-week dip after a clean migration is normal and you should not panic-edit through it. A drop that is still deepening at week six is not normal, and it is a diagnosis, not a waiting game.

One trap: do not undo the migration. Rolling back to the old site adds a second migration on top of a broken one and doubles the signal loss. Fix forward.

What should you demand in the SOW before you sign a redesign contract?

Six clauses, and every one of them is a line you can add to a contract today. If a $12,000 redesign proposal contains none of them, the agency is selling you pictures and quietly transferring the SEO risk onto you.

• A 1:1 redirect map is a named deliverable, reviewed and approved by you before launch
• Content parity on the top 20 organic pages is written in as an acceptance criterion, not a nice-to-have
• A pre-launch technical check on staging is a gate, and launch cannot happen until it passes
• You get 30 days of post-launch monitoring of Search Console coverage and 404s, in writing
• You own everything at handover: the codebase, the CMS access, the domain, the analytics, the redirect map itself
• No launch on a Friday, and no launch during your busy season

The last two are not SEO clauses. They are the ones that save you. A Friday launch means a broken redirect map sits live for 72 hours before anyone looks at it.

We build conversion-focused websites and we run the SEO on them, which means we do not get to hand off a beautiful site that lost your rankings and call it someone else's problem. If you already have a redesign quote in hand and you are not sure whether it protects your traffic, we will look at your current URLs, your top pages, and the proposal itself. Get my free audit — no contract, no lock-in, and you keep the redirect map either way.