Why my site no longer appears on Google after the redesign

A traffic drop after a redesign is a loss of Google visibility caused by what the launch changed: page addresses, indexing rules, or the text Google can read on each page. To Google, the new site is a set of new pages, and it has to work out how they relate to the old ones. When the launch gives it the wrong answer, rankings that took years to earn fall within days.

This brief is for the person who paid for the redesign and is now watching a line fall in Search Console: a founder, a marketing lead, whoever runs digital in the company. It covers how to tell a normal dip from a fault, the five causes we check first, a test you can run in thirty minutes without an engineer, and what to ask the team that shipped the site.

Is the drop normal, or a fault in the launch?

Some movement is expected. Google's own site move documentation says to expect temporary fluctuation in ranking while it recrawls a changed site, and that a small to medium-sized site can take a few weeks for most pages to move. Larger sites take longer.

A fault looks different. Open the Performance report in Search Console, compare the 28 days after launch with the 28 days before, and look at the shape of the line. Google's guide to debugging drops in Search traffic sorts drops by that shape: a gradual slide points to seasonality or changing interest, a sharp fall across the whole site points to a technical issue, a security or spam problem, or an algorithmic update. A sharp fall that starts on launch day and hits every page and query is the launch.

Two more signals separate a fault from a dip:

• Impressions fell along with clicks. If impressions hold and clicks fall, the pages still rank and something else changed: titles, snippets, a new feature on the results page. If impressions fall too, Google is showing the pages less often, or not at all.
• The Page indexing report grows a new category. A spike in pages excluded by a noindex tag, not found (404), with a redirect, or blocked by robots.txt in the week of the launch names the cause for you.

Search Console keeps 16 months of data, so you can also compare against the same weeks last year and rule out a seasonal dip.

The five causes we check first

They're listed in the order we check them, quickest first. Each one can arrive with a launch on its own, and two or three often ship together.

1. Old addresses with no redirect. The new site renamed its pages (/services/web-design became /what-we-do/design) and the old URLs now return a 404. Every link from another site, every bookmark and every ranking pointed at the old address. Google's guidance is a permanent redirect (301 or 308) from each old URL to its closest new page, kept for as long as possible, generally at least one year. A variant of the same fault: sending every old URL to the home page. Google warns this can be treated as a soft 404, which carries nothing over.
2. A staging block that went live. Sites in development hide from search behind a noindex rule or a Disallow line in robots.txt. If either ships to production, the new site asks Google to drop it. The two also get in each other's way: Google's documentation explains that a page blocked by robots.txt is never crawled, so Google sees neither the noindex rule on it nor its removal.
3. Canonical tags pointing to the wrong place. A canonical tag tells Google which address is the real one. Templates copied from staging sometimes keep the staging domain in it, or point every page at the home page. Google then favours the address the tag names, which may not exist.
4. Content the new templates removed. The new design is shorter, cleaner, and missing the 600 words that ranked the old services page. Or the text is still there but appears only after a click, in a tab or an accordion built in the browser. Internal links move too: a page the old menu linked from everywhere may now sit three clicks deep.
5. Redirect chains from earlier redesigns. A 2019 URL redirects to a 2022 URL, which now redirects to the 2026 one. Google follows chains but recommends no more than 3 hops, and fewer than 5. Each redesign that adds a link to the chain, instead of pointing old URLs straight at the final address, makes it longer.

A 30-minute test you can run without an engineer

You need access to Search Console and a list of the ten pages that brought the most traffic before the launch. The Performance report gives you that list: set the date range to the three months before launch and sort pages by clicks.

1. Open each of the ten old URLs in a browser. Each should land on the matching new page in one hop. A 404, the home page, or a page about something else is cause 1.
2. Open yoursite.com/robots.txt. A line reading Disallow: / under User-agent: * blocks the whole site. That's cause 2. Google's robots.txt introduction explains what each line does.
3. Check the home page and two service pages with the URL Inspection tool. It tells you whether the page is indexed, whether indexing is allowed, and which canonical Google picked. "Excluded by noindex tag" is cause 2. A Google-selected canonical on another domain is cause 3.
4. In the same tool, open the crawled page. Search its HTML for a sentence you expect on the page. If it isn't there, Google doesn't see it either: cause 4.
5. Open the Page indexing report. Compare the number of indexed pages before and after the launch. A fall of a third or more means something took pages out of the index, and the report lists which ones and why.

If all five checks pass and the drop is still there four weeks after launch, the cause is more likely the content or a ranking change than a faulty launch. Google's troubleshooting guide for pages missing from Search is the next stop.

What to ask the team that shipped the redesign

A redesign that protects search traffic leaves a paper trail. Four requests show whether it exists:

• The redirect map. A spreadsheet with every old URL in one column and its new URL in the next, built from a crawl of the old site before launch. Without a map, the redirects were written from memory.
• The launch checklist. When the staging noindex came off, who checked robots.txt, when the new sitemap went into Search Console.
• A crawl before and after. The count of indexable pages on the old site and on the new one. A gap needs an explanation.
• Access. Search Console verified for the domain, with you as an owner. You should never need the agency's login to see your own site's data.

Whether lost traffic is the agency's responsibility depends on what the contract said about search. If the loss matters commercially, take that question to a lawyer with the contract in hand.

How long does recovery take?

Fixing the fault is quick. Google noticing the fix takes longer. Once redirects, robots.txt and noindex are corrected, submit the updated sitemap and request indexing for the most important pages with the URL Inspection tool. For pages Google considers less important, its own documentation warns that a revisit may take months.

Plan in weeks, counted from the fix, and keep comparing the same 28-day windows. Rankings that came from links to the old URLs return as Google follows the redirects and moves those signals across, which is why the redirects stay in place for at least a year. Content that was removed comes back only when someone puts it back.

What to require before the next redesign

A redesign brief can make search a deliverable with acceptance criteria, the same way it does for the design. These are the four we write into ours:

• A crawl of the current site and the redirect map, reviewed and signed off before development ends.
• Every page that drew organic traffic in the last 12 months kept, merged with a redirect, or retired on purpose, with the decision written down.
• A launch checklist covering robots.txt, noindex, canonical tags, the sitemap and Search Console, run on the production domain on launch day.
• 30 days of monitoring after launch, with the 28-day comparison and the Page indexing report reviewed every week.

The full list for a product launch is in our technical SEO checklist for a B2B SaaS launch, and large sites with a split sitemap will find the indexing side in sitemap strategy for a large content site. With those four items in the brief, a redesign changes how the site looks and keeps the addresses Google already trusts.

Sources

• Google Search Central, Site moves with URL changes
• Google Search Central, Block Search indexing with noindex
• Google Search Central, Debugging drops in Google Search traffic
• Google Search Central, Introduction to robots.txt
• Search Console Help, Performance report (Search results)
• Search Console Help, Why is my page missing from Google Search?