Traffic usually drops after a redesign because URLs changed and the old ones weren't redirected, so pages that used to rank now return errors. Most of the fix happens before launch: list every URL that brings in traffic, map each one to its new address, set up permanent 301 redirects and check that the content that ranked survived the redesign.
Why redesigns cause ranking drops
The pattern is familiar. A business pays for a new website, the design looks much better and the developer hands it over. Within a month, organic traffic has fallen sharply and nobody knows why.
The cause is usually the same. The URL structure changed and nobody set up redirects, so the old URLs Google had indexed now return 404 errors. Each of those was a page that used to rank, and its rankings go with it.
This is preventable, and the prevention work takes an afternoon or two before launch. It often gets missed because it falls outside the designer's or developer's scope, and the client doesn't know to ask for it.
The pre-launch checklist that prevents traffic loss
Step 1: list every URL worth keeping
Two weeks before launch, build a full list of the old site's URLs. Export the indexed pages from Search Console's Page indexing report, the pages in the Performance report that get impressions and clicks, and a crawl of the old site from a tool such as Screaming Frog. Add any URLs that other sites link to. Every URL on this list that doesn't redirect to a working page on the new site becomes a 404 at launch.
Step 2: map every old URL to a new one
Work through the list and find the matching new URL for each entry. Most will map cleanly: /about-us becomes /about, /services/bookkeeping stays the same, and /blog/2019/post-title becomes /blog/post-title if the date was dropped from the URL.
Some old pages won't have a direct equivalent. Map each of those to the closest relevant page, so a retired service page points to the main services page and a deleted post points to the most relevant remaining article.
Step 3: set up 301 redirects before launch
Every line on the map becomes a permanent 301 redirect, in place before the new site goes live. Test them all on the staging site. Google's redirects documentation explains why the type matters. A permanent redirect tells Google the target "should be canonical" and shows the new URL in search results, while with a temporary 302 the old URL can stay in results.
Point each redirect straight to its final URL rather than through a chain of hops, and keep the redirects in place long term. Google's site move guidance says to keep them "generally at least 1 year".
Work With John
If your site isn't bringing in enquiries, that's fixable.
I work with US service businesses and B2B brands on SEO, websites and lead follow-up. On a free strategy call, I'll tell you what's holding your site back, without a sales pitch.
Book a free strategy callContent changes that cost rankings even with correct redirects
Redirects stop the 404s, and they can't protect rankings from content changes. If the redesign shortened your service pages, removed headings that matched what buyers search for or cut FAQ content, those pages can slip regardless of the redirects.
Before launch, compare your most important pages with their redesigned versions: the content, the heading structure, the title tags and the internal links. If a new page has lost substance the old one had, raise it before launch, while it's still easy to fix.
What to monitor after launch
For the first three months, check Search Console every week. The Page indexing report shows new 404 errors, which point to redirects you missed. The Core Web Vitals report shows whether the new design introduced speed problems, and the Performance report shows which pages lost impressions or position, which often means they lost content that helped them rank.
Some fluctuation is normal. Google's site move guidance says medium-sized sites can take "a few weeks or more" to show the new URLs in place of the old ones, and larger sites longer. Rankings that settle and then decline weeks later deserve a closer look, since that usually points to a content or technical problem.
The migration Google can't see
Some redesign losses have nothing to do with redirects or content. They come from a platform change that alters how pages render. A site that moves from server-rendered pages to an app that builds everything in the browser with JavaScript can be harder for crawlers to read.
Google can render JavaScript, but its JavaScript SEO guide notes that server-side or pre-rendering "is still a great idea because it makes your website faster for users and crawlers, and not all bots can run JavaScript." If your redesign includes a platform change, confirm the new site renders content on the server or at build time. After launch, the live test in Search Console's URL Inspection tool shows how Googlebot renders a page.
A redesign that protects rankings is only half the job if the new pages still don't convert. SEO gaps your competitors leave open covers what to fix once the technical risk is handled.
