Traffic Dropped After Your Redesign: A Week-by-Week Diagnosis

The new site launched on a Tuesday. By the following Monday the weekly report showed sessions down by a third, and the agency's explanation was that "Google needs time to re-index". Sometimes that is true. Often it is a cover for a tag that no longer fires, a staging noindex that shipped to production, or a hundred URLs that now return 404.

This guide gives you an order of checks for the first eight weeks, each tied to the evidence that confirms or rules it out, so that you fix the real cause and stop worrying about the ones that do not apply. It assumes you kept Search Console access; if URLs changed as part of the redesign, read the redirect checklist alongside this, and browse the guides index for the indexing and homepage-structure guides it refers to.

Week 1, day 1: is the drop real or just unmeasured?

The fastest way to lose a third of your traffic is to lose a third of your measurement. New templates frequently omit the analytics snippet on some page types, load it after a consent banner that nobody configured, or load an old property ID. The symptom is identical to a ranking drop in your analytics dashboard, but Search Console, which measures Google's side, will show no change in clicks.

Open a handful of pages of each template type with the browser's network panel filtered to your analytics domain and confirm the request fires. Check the real-time report while you browse. Confirm the consent setup, if any, matches the old site's. If the tag is missing, fix it, annotate the date, and accept that the gap in data is permanent. Do not proceed to SEO theories until this row is settled.

Week 1, days 2-3: did anything block Google?

Google's guide to debugging traffic drops groups causes into technical issues, security issues, manual actions, algorithmic updates and seasonality. After a redesign, technical issues come first. Check, in this order:

1. robots.txt on the live domain: a staging rule that disallows everything is a classic launch leftover.
2. The noindex meta tag or X-Robots-Tag header on live templates: Google's site-move documentation specifically advises preparing the list of URLs where development noindex rules must be removed at launch.
3. Search Console's Pages report for a spike in "Excluded by noindex", "Not found (404)" or "Redirect error" after the launch date.
4. Server availability: a new host or theme that times out under crawl load produces "server error (5xx)" entries.
5. The Security Issues and Manual Actions reports, which should both be empty.

Each of these has a yes or no answer today, and fixing one usually explains most of the drop. Do not request re-indexing of hundreds of URLs by hand while a noindex is still in place; remove the block, resubmit the sitemap, and let crawling do the work. Our guide to sitemaps, Search Console and indexing covers the discovery mechanics.

Week 1, days 4-5: what changed about the pages themselves?

A redesign that keeps every URL can still lose rankings by changing what is on the page. Compare the old and new versions of your top twenty landing pages from before the launch, which the Performance report's page filter identifies, against an archived copy or the staging export.

Look for: headings reduced to decorative text, body copy shortened to fit a new layout, internal links removed from navigation or footers, images that replaced text, pages merged without redirects, and titles rewritten to taglines. Search Console's comparison mode, which Google's debugging guide recommends, lets you compare the same pages across two periods and see whether impressions, position or click-through rate moved. A click-through drop with stable position points at titles and snippets; a position drop points at content or links.

If the homepage absorbed what used to be separate service pages, the loss is structural rather than technical. Homepage and service-page structure explains why specific searches need specific pages.

Do not rewrite the content back blindly. Restore the elements that search relied on, such as the descriptive title, the H1, the first paragraph and the internal links, and keep the design improvements that did not touch them.

Weeks 2-4: redirects, canonicals and the long tail

If URLs changed, redirects decide everything. Export the old sitemap or a crawl of the old site, request every old URL, and confirm a single 301 to the correct new page rather than to the homepage or through a chain. Check that canonical tags on new pages point to themselves and not to staging hostnames. Both failures are common and both are cheap to fix.

Google's site-move guidance sets expectations: for medium-sized sites it can take a few weeks or more for new URLs to replace old ones in results, and longer for large sites, with speed depending on URL count and server performance. That is the only documented timeline, and it applies to URL changes specifically. A redesign that kept URLs should not need it.

Use this period to watch the long tail. Pages that ranked for hundreds of small queries often lose more than headline pages, and they show up as a broad, shallow decline in the Performance report rather than a few obvious losers. Sorting queries by click loss, one query filter at a time as the debugging guide suggests, finds them.

The case against spending these weeks on new content: until the redirects and canonicals are verified, new pages compete with your own unresolved duplicates. Fix plumbing first.

Weeks 5-8: separate what you can fix from what you wait out

By week five you should be able to put every lost page into one of three groups.

Google's debugging guide recommends the 16-month date range precisely so that a seasonal dip is not mistaken for damage. Check the published ranking updates list for your launch window as well. If a documented update coincides with your launch, compare heavily changed pages with barely changed ones; a uniform drop points away from the redesign.

Effort is typically 2-4 hours in the first week and 30 minutes a week thereafter. Developer repairs to redirects or templates typically cost CAD 300-1,200 as an editorial planning range, not a quote. Rolling back the whole site is rarely cheaper than fixing the identified stage, and it resets whatever indexing progress the new site has made.

Finally, record what you found. The next redesign brief should include the tag check, the noindex sweep, the redirect test and the title comparison as launch-day gates, so that the next Monday report is boring.

— Editorial team. Facts current as of 2026; we revise guides when the ground shifts.