Traffic dropped after a website redesign or migration

If organic search traffic fell after your new site launched, the redesign is the first suspect. Four other causes can start in the same weeks: a Google update, a seasonal or demand change, a change on the results page and a tracking change. The decision tree below tells them apart, mostly with Google Search Console.

The decision tree in six questions

Ask these questions in order, because each answer rules a cause in or out before you look at the next one. The first five need only Search Console, Google Analytics 4 and a browser; the sixth is where the work changes hands.

1. Did Search Console clicks fall, or only your analytics sessions? If Search Console clicks held steady, the drop is in measurement: check the analytics tag, the consent banner and the data stream before anything else.
2. Did the drop begin inside a Google update rollout instead of at launch? Then wait for the rollout to finish and compare again before you change anything on the site.
3. Did the same weeks fall last year, or did searches for your top queries fall everywhere? Then seasonality or a shift in demand explains the drop, and the relaunch only shares its timing.
4. Did impressions hold while clicks fell? Then the results page changed around your listing: new titles or snippets from the redesign, lost rich results, or an AI Overview on your top queries.
5. Did the lost clicks gather on pages whose URL, template or content changed? Then check those URLs for relaunch defects: redirects, noindex rules, robots.txt, canonical tags and missing content.
6. Do the answers point at the relaunch, while no URL, template or setting explains the drop? That is the point to bring in the Named-Cause Diagnosis, which crawls your old URLs on the live site and compares Search Console data URL by URL around your launch date.

A yes at one question does not clear the others. A redesign can launch in the same week as a core update, so keep going until one cause fits the dates, the pages and the metric that fell.

How each cause shows up in Search Console

Each cause leaves its own pattern in the Performance report of Search Console, so read the pattern before you choose a fix.

Google’s guide to traffic drops draws the same line between the two metrics: “If your impressions remain the same but your clicks drop, you might not be generating the best page title and snippet that you could”¹. The same guide separates site-wide technical issues from page-wide ones, such as a misplaced noindex tag, which “would depend on Google crawling the page, meaning there would be a slower drop in traffic”¹.

A gradual slide after launch can therefore still be a relaunch defect. A noindex tag left on the new templates takes effect page by page, as Google recrawls each one.

Rule out a tracking change before anything else

A tracking change can look exactly like a traffic drop, so compare Search Console with Google Analytics 4 (GA4) before you touch the site. For most result types, Search Console counts a click when a result sends the user to a page outside Google⁶, so a tag missing from your new templates cannot lower its numbers.

Put Search Console clicks and GA4 organic sessions for the same weeks side by side. If Search Console held and GA4 fell from launch day, look for one of these changes in the relaunch:

• the GA4 tag missing from some of the new templates, or firing twice;
• a new consent banner, or new settings in the old one;
• the site sending data to a different GA4 property or data stream;
• reports, segments or filters built on old URL paths that no longer exist.

A consent banner changes what GA4 records: when visitors deny consent, “instead of storing cookies, tags send pings to Google”, and Google Analytics “fills the data collection gaps with conversion modeling and behavioral modeling”¹⁰. A banner added during the redesign can therefore lower the sessions GA4 reports while the clicks Search Console counts stay level.

Search Console has reporting changes of its own, listed on its Data anomalies page. That page records a logging error that affected impression counts from 13 May 2025 to 27 April 2026, and it notes that “clicks were not affected by the error”⁷. If your launch falls near those dates, judge the drop by clicks rather than impressions.

Line the drop up with launch day, Google updates and last year

Put three sets of dates on one calendar: your launch day, Google’s update rollouts and the same weeks a year earlier. Google’s traffic-drop guide recommends setting the Performance report to “Last 16 months” so that you can see whether the drop is one “that happens every year due to a festivity or a trend”¹.

If the drop began inside an update rollout

Google posts the start date and duration of each announced core and spam update on the Google Search Status Dashboard³. The eight core updates charted above took between 6 days, 4 hours (December 2024) and 23 days, 13 hours (November 2024) to roll out³.

Google’s core updates guide asks you to “Confirm that the core update has finished rolling out”, and adds: “We recommend waiting at least a full week after a core update completes before analyzing your site in Search Console”². The guide then suggests comparing that week with a week before the rollout started.

Dates alone can mislead in both directions. Google also makes smaller core updates that “are not announced because they aren’t widely noticeable”², and a relaunch can land inside an announced rollout. When both overlap, compare the pages the relaunch changed most, such as moved or merged pages, with the pages it barely touched: a loss concentrated on the changed pages points back at the relaunch.

A public thread shows how the two get tangled. Posted to the Google Search Central Help Community on 1 October 2026 by an SEO whose site lost impressions after a redirect migration and the May 2026 core update, it reports that “the developers’ tools reported the redirects as working fine” while “the inconsistency was only visible from the outside / in Search Console”¹¹. That is why the checks further down test the old URLs from the outside, with a crawler.

If the same weeks fell last year

Seasonality shows up as a dip that repeats. Google’s guide illustrates it with a 16-month chart where “the recent drop happened exactly as it did the previous year”¹; the Compare tab’s option for the last 3 months year over year checks yours.

Demand can also shift without a yearly pattern. Google suggests filtering the Performance report to one top query at a time and checking it in Google Trends “to understand if the drop was only for your website or throughout the web”¹.

After a domain change, the history from before launch sits in the old domain’s Search Console property, so keep that property verified. Google’s site-move guide says to “Verify data for each property separately in Search Console”⁴.

Find the pages and queries that lost clicks

Compare the weeks after launch with the same number of weeks before it, then sort the Pages tab by the clicks each page lost. Google’s guide names that sort, “Select Clicks Difference to order it based on pages that lost the most traffic”, and the question it answers: whether the drop happened “across the whole site, a group of pages, or even just one very important page in your site”¹.

After a URL change, read each old URL together with its mapped page. Search Console assigns click data “to the canonical URL that Google selects for each page”⁶, so clicks move from an old URL to its new one as Google switches canonicals. An old URL that lost clicks while its mapped page gained them is not a loss.

Then group the pages that did lose clicks by what the relaunch did to them:

• URL changed: the old URL should redirect, with one 301 redirect, to its mapped page.
• Page merged or removed: the queries it answered need a page that still answers them.
• Template changed: the old and new versions need the same title, H1, main text, internal links and structured data, which is what a parity check compares.
• Nothing changed: the cause more likely sits outside the relaunch, in an update, in demand or on the results page.

On the Queries tab, a query that kept its impressions but lost clicks points at the results page. Look at what your listing now shows there: a title or description the new templates rewrote, rich results the redesign stopped qualifying for, or an AI Overview above the results. Google changes the page too: FAQ rich results stopped appearing in Google Search on 7 May 2026, and reported FAQ impressions dropped with them⁷.

For AI Overviews, Search Console counts a click on a link inside the overview as a click and gives every link in it the same position⁶. When you search a query to look, remember that results are “specific to the time, place, device, and recent history of the person searching”⁵.

Check the losing URLs for relaunch defects

A relaunch defect is an old URL that no longer reaches an indexable page with its old content. Run these checks on the pages that lost the most clicks; the label after each one says what it needs.

1. List the old URLs (Search Console). Export the Pages tab of the Performance report for the months before launch and add the old sitemap if you kept it. If no list was kept, rebuild one this way and pair each URL with its new page in a redirect map.
2. Crawl the old URLs on the live site (needs a crawler). Run the old URLs through a crawler in list mode and record each URL’s status code, redirect hops and final URL. Google’s site-move guide suggests “other tools such as Screaming Frog to crawl your own site and see if the redirects work as expected”⁴.
3. Inspect the top losing URLs (Search Console). In URL Inspection, “Indexing allowed?” shows whether a noindex rule blocks the page, and the Google-selected canonical shows which URL Google treats as the main version⁹.
4. Check the WordPress search setting (WordPress admin). Under Settings > Reading, the box “Discourage search engines from indexing this site” asks “search engines not to index this site”, and since WordPress 5.3 it adds a noindex, nofollow robots meta tag to the site’s pages when the theme calls wp_head¹². A staging copy built with the box ticked can carry it to the live site.
5. Open robots.txt and the sitemap (browser). Google’s site-move guide says “Don’t forget to remove any noindex or robots.txt blocks that were only needed for the migration” and “Be sure that your sitemaps are all updated with the new URLs”⁴.
6. Compare the old and new versions of each top losing page (needs the old version). Check the title, H1, main text, internal links and structured data against a backup or an archived copy of the old page.

Two checks need server access: the redirect rules in the server configuration or the redirect plugin, and the access and error logs, where Google’s site-move guide suggests checking “for crawling by Googlebot, any URLs that unexpectedly return HTTP error status codes, and normal user traffic”⁴. If you cannot reach either, that is where the work changes hands.

The Page indexing report gives each URL that Google did not index a reason⁸. After a relaunch, these reasons point at a defect or rule one out:

When the checks point at the relaunch but name no cause

Bring in outside help when your checks point at the relaunch, but no URL, template or setting you found explains the size of the drop. By then the remaining work needs a crawler run over every old URL, a comparison of Search Console data URL by URL across 16 months, and sometimes server access.

If organic search brings in inquiries or sales, you can order the fixed-price diagnosis, from $490 / £390. It names the cause with dated evidence and quotes a fixed price for the fixes in scope, so you see the cost before anything on the site changes. If the site earns nothing from search, the checks above are the place to stop.

No one can say when clicks will return after a fix, because Google decides when it recrawls the fixed URLs and how it ranks them.

Before the next redesign

Google’s site-move guide advises changing one thing at a time: when a relaunch would combine a domain change, a platform switch and a new layout, its advice is to “do them one at a time”⁴. A relaunch that changes one thing leaves one suspect when clicks fall.

Staging and launch-day checks for a redesign are set out in the redesign SEO checklist. If search brings your business inquiries and the site runs on WordPress, you can plan the next redesign around them: every URL on an inventory you sign is mapped before launch and crawled again on day 7 and day 30.