Lost Google rankings after a website redesign? How to find the cause and fix it

A fall in enquiries after a new website goes live is frightening, especially when you have just paid for the site. The useful thing to know is that post-redesign drops are rarely mysterious. They usually come from a handful of mechanical faults that can be found in an afternoon, and the order you check them in matters more than any tool you use.

Is it really the redesign, or something else?

Before changing anything, make sure you are looking at a real fall in Google traffic that started with the launch. Three things regularly get mistaken for a redesign problem:

• Broken tracking. If the analytics code was not added to the new site, or was added twice, your visitor numbers will look wrong while Google traffic is fine. Use Google Search Console (Google's free tool that reports clicks and searches directly from Google) as the source of truth, because it does not depend on code in your pages.
• A Google update. Google regularly changes how it ranks pages. Its Search Status Dashboard lists recent ranking updates with dates. If a core update rolled out the same fortnight you launched, the cause may be partly or wholly unrelated to the redesign.
• Season. Compare the weeks after launch with the same weeks last year, not just with the weeks before launch. A kitchen maker's December is not a fair comparison with its October.

If Search Console shows clicks falling from the launch date, and the pattern does not match last year or a Google update, treat it as a redesign fault. The general version of this diagnosis, for drops with no obvious trigger, is in why did my Google rankings drop.

The first hour: which four checks find the worst problems?

These four faults cause the biggest and fastest losses, and each takes minutes to check. Do them first.

1. Is a noindex tag still on? Test sites are often hidden from Google with a "noindex" instruction, a line in the page code that tells search engines not to list it. If it survived launch, Google will drop your pages. In Search Console, open the Pages report and look for "Excluded by 'noindex' tag". On WordPress, check that the setting that discourages search engines from indexing the site is switched off.
2. Is robots.txt blocking the site? Visit yourdomain.com/robots.txt. If it says Disallow: / under User-agent: *, every search engine is being told to stay out. This is another common leftover from the test site.
3. Do your top old URLs redirect? Take the twenty pages that earned the most clicks before launch (Search Console's Pages tab, set to a date range before launch) and paste each old address into your browser. Each should land on the matching new page. If you see a "page not found" error, you have found the most likely cause.
4. Can Google fetch your key pages? Use Search Console's URL Inspection tool on your homepage and main service pages, and run a live test. It shows whether Google can reach the page and what it sees there.

Missing redirects are the most common single cause of lost rankings after a redesign. If the old addresses of your best pages now show an error, nothing else on this page matters until that is fixed.

How do you find exactly which pages lost traffic?

A sitewide average hides the detail. In Search Console's Performance report, use the date comparison to set the four weeks after launch against the four weeks before, then open the Pages tab. Sort by the difference in clicks.

You will usually see one of three patterns:

• Old URLs lose clicks and no new URL gains them. The redirects are missing, wrong, or pointing to the homepage instead of the matching page.
• Old URLs lose clicks and new URLs gain some of them, but fewer. The redirects work, and either Google is still processing the move or the new pages are weaker than the old ones. Compare the content.
• Clicks fall across every page evenly. Look for a sitewide cause: a noindex tag, a robots.txt block, a much slower site, or a broken template that removed titles or headings everywhere.

Then switch to the Queries tab with the same comparison. If the searches you lost are the ones your old service pages answered, you have confirmed which pages to focus on.

What are the causes, from most to least common?

Can you still fix redirects weeks after launch?

Yes, and you should do it now rather than later. Google keeps revisiting old addresses for a long time, and other sites keep linking to them, so a redirect added late still recovers much of the value. The longer an old URL returns an error, the more likely Google is to have dropped it, and the longer it takes to come back.

If nobody kept a list of the old URLs, you can rebuild one from several places:

• Search Console's Performance report for dates before launch, which lists every page that received clicks or impressions.
• The Pages report, which lists URLs Google tried to crawl and found missing.
• Search Console's Links report, which shows which of your pages other sites link to.
• A backup or export of the old site, and the old sitemap file if your previous developer kept it.
• Public web archives such as the Internet Archive's Wayback Machine, which often hold snapshots of older sites.

Build the map, add the redirects, test each one, and resubmit your sitemap. The method is set out in full in the guide to 301 redirects, and the wider launch checks are in the website migration SEO checklist.

What if the problem is content you removed?

This is the cause owners find hardest to accept, because the new pages often look better. Google, though, ranked the old page for what it said. If a 900-word page explaining your process, prices and service areas became a headline and three short paragraphs, the new page simply has less to rank for.

When restoring content, there is no need to paste the old page back word for word. Keep the topics, the detail and the phrases people search with, and write them better. A page built around the questions buyers actually ask tends to do well in ordinary search and in AI answers alike, as the guide to getting recommended by ChatGPT explains.

How long does recovery take once you fix it?

Nobody can promise a date, and you should be wary of anyone who does. Recovery depends on how quickly Google recrawls the affected pages, how long they were broken, and whether anything else changed in the meantime. Google's own guidance on site moves says a medium-sized site can take a few weeks or more for new addresses to replace old ones, and fixes after a faulty launch follow a similar rhythm.

To help it along:

• Submit an updated sitemap containing only the new addresses.
• Use URL Inspection's "Request indexing" on your few most important fixed pages.
• Update your own internal links, your Google Business Profile and other profiles to the new URLs.
• Track the same searches and pages weekly, so you can see recovery rather than guess at it.

If several weeks pass after the fixes with no movement, the cause is probably one you have not found yet. A structured review covering rankings, the site itself and what AI tools say about you is what the M/AFZAL Visibility Audit does, for a fixed $700. Whoever does it, start with the four first-hour checks above. For the full picture of how to avoid this next time, read how to redesign your website without losing Google rankings.