Traffic drop after a website redesign: how to find the release that caused it

Why does traffic drop after a website redesign?

Traffic drops after a website redesign when the relaunch changes something search engines or your analytics depend on: URLs, redirects, indexable content, internal links or the tracking tag. A new look on its own rarely explains a loss; the edits that ship with it usually do.

Most redesigns bundle many changes into one release date. New templates, a new CMS, a cleaned-up URL structure, merged pages, a new cookie banner and a reinstalled tag all go live together. That is why the first weeks after a relaunch are hard to read: several possible causes share the same date.

The usual suspects:

• Changed URLs without redirects. Old URLs return 404, so the rankings and links they earned are not passed to the new pages.
• Wrong redirects. Temporary redirects (302, 307) where permanent ones were meant, chains of several hops, or many old pages sent to the new home page.
• Removed or merged content. Pages that ranked for long-tail queries were cut or folded into a shorter page.
• Staging leftovers. A robots.txt disallow or a noindex tag from the test site shipped to production.
• Changed templates. New titles, headings or navigation that drop the words a page used to rank for, or fewer internal links to deep pages.
• Broken tracking. The analytics tag or consent setup was not carried over, so traffic looks lower than it is.

If your drop started on a date without a relaunch, the broader article on why organic traffic drops covers algorithm updates and other causes.

Is the drop real, or did the redesign break tracking?

Check this first, because a broken tag after a relaunch looks exactly like lost traffic. Compare GA4 with Google Search Console: if Search Console clicks held steady while GA4 sessions fell on launch day, the problem is measurement, not visitors.

1. Open the new site and watch the GA4 Realtime report. Google says data should start appearing there within minutes of the tag firing correctly.
2. Use DebugView or Tag Assistant to confirm that page views and key events fire on the new templates, including forms and thank-you pages.
3. Check whether the consent banner changed with the redesign, since a new banner setup can stop tags from firing.
4. Compare organic clicks in Search Console with organic sessions in GA4 for the same days. A gap that opens on launch day points at tracking.

Give standard reports time: Google advises allowing 24 to 48 hours for full processing, so don't judge a relaunch on same-day reports. For a step-by-step check, see how to tell a tracking problem from a real loss of visitors and our Tag Assistant walkthrough. If conversions fell but traffic did not, look at forms and thank-you URLs too: our Google Ads conversion tracking article lists the edits that change the counts.

How long does traffic take to recover after a redesign or migration?

If URLs changed, expect some movement. Google's site move documentation says to expect ranking fluctuations during a move, and that for a medium-sized site it can take a few weeks or more for most pages to move in Google's index; larger sites take longer.

A move is only complete when Googlebot has visited every old and new URL at least once, and Google has no fixed crawl frequency. So a slow, uneven recovery is normal in the first weeks. What is not normal is a loss concentrated in pages whose old URLs return errors, or pages that are no longer indexed at all.

Google also recommends keeping redirects for as long as possible, generally at least 1 year, so signals can transfer to the new URLs (Google's site move guide). Removing them early because traffic "came back" can start the problem again.

Which redesign changes should you check first?

Start with the changes that take pages out of Google's index, then the ones that change what pages say. Redirect and indexing mistakes can cut traffic quickly; template and content changes tend to show up as a slower slide.

Redirects

Google recommends server-side permanent redirects (301 or 308) from every old URL to its closest new equivalent. Temporary redirects (302, 303, 307) tell Google the old URL is still the canonical one. Avoid chains (ideally no more than 3 hops and fewer than 5) and don't send many old URLs to one unrelated page such as the home page. JavaScript redirects are a last resort, because rendering can fail and Google might never see them (redirects and Google Search).

404s and removed pages

According to Google, 404 errors don't harm the indexing or ranking of the rest of your site. The loss comes from 404s on pages that moved: if the content has moved, add a redirect. Export the old URLs that earned clicks and check each one.

Indexing rules

Look for a robots.txt disallow or a noindex tag copied from staging, and for canonical tags that point to the old domain or the wrong page. The URL Inspection tool shows how Google sees a single URL.

Templates and content

Compare old and new titles, headings, body text and internal links on your top landing pages. A shorter page, or a menu that no longer links to category pages, can lose rankings without any technical error.

How do I isolate which release caused the traffic drop?

Date the drop precisely, split it by page group, then match each affected group to the release that touched it. A redesign is rarely one change; it is a series of releases, and the one that matches both the date and the pages is your cause.

1. Rule out tracking
2. Split the drop by page group
3. Match each group to a release
4. Test one fix at a time

In Search Console, compare clicks for the four weeks before and after launch, then filter by page or URL pattern such as /blog/, /products/ or /services/. If only one group lost clicks, the cause sits in what changed for that group: its URLs, its template or its redirects. Then check outside events on the same days, such as a Google update or a paused campaign, so you don't blame the redesign for something else.

The hard part is the dates. A relaunch is usually followed by hotfixes, redirect batches, a new consent banner and content edits over several days, while paid campaigns keep changing in parallel. With every change on one timeline, you would see that the blog redirects went live on Tuesday, two days after launch and on the exact day blog clicks fell. In Changeline, the team logs each release with its date, owner and reason, and Google Ads edits are imported automatically next to them, so site and campaign changes sit on the same timeline.

Example: a client asks why organic leads fell 30% two weeks after the relaunch. Lining up the changes from the days before shows that on day 3 the agency merged 40 service pages into 8 and redirected the rest to the home page. Clicks to service pages had been falling since that date, while the blog was stable. Redirecting each old page to its closest new service page explained the drop to the client and gave a clear fix. (Names and numbers are illustrative.)

How do I fix a traffic drop after a redesign?

Fix what keeps pages out of the index first, then restore the content that ranked, and change one thing at a time so you can see what worked.

1. Collect the old URLs from old sitemaps, server logs, analytics, your CMS and Search Console, as Google's site move guide suggests, and build a URL mapping from old to new.
2. Add permanent redirects for every moved URL, and fix chains and redirects to the home page.
3. Remove leftover noindex tags and robots.txt blocks, and correct canonical tags.
4. Submit the new sitemap in Search Console. Keep the old one for a while to watch its indexed pages fall toward zero, then remove it.
5. Restore titles, headings, sections and internal links on the pages that lost the most clicks.
6. Record each fix with its date, so the recovery can be read against it later.

If the domain itself changed, use Search Console's Change of Address tool on the old site. Google says it is for domain or subdomain changes, not for HTTP to HTTPS moves, www changes on the same domain or path changes within a domain.

How do I plan the next redesign so every change is on record?

Take a baseline before launch and keep a dated record of every release after it. Most post-redesign arguments are about dates nobody wrote down.

• Save your top landing pages by clicks and conversions for the last 3 months, plus a sitemap of the old URLs.
• Ship in stages when you can (templates, then URL changes, then content), so each stage has its own date.
• Write down each release: date and time, pages affected, what changed, owner and reason.
• Mark the launch in your analytics as well; our GA4 annotations guide shows how.
• Agree with the client before launch how long you will wait before judging the results.

A website change log makes this a habit, and the marketing change log guide explains how to keep site and campaign changes together. Our marketing change log template has the columns ready, and when a client asks what happened, this guide to explaining a drop to a client helps with the conversation.