Redirects Are Working But Traffic Still Dropped

Published Read 6 min read

On this page

A redirect that verifies clean in a crawler proves one thing only: the hop resolves with a 301 and lands on a live page. It does not prove that the destination still deserves the source’s rankings. After a migration, Google re-evaluates the new URL on its own merits for the queries the old one ranked for, and a green redirect map is silent about whether that re-evaluation went your way. So when traffic drops despite a technically valid redirect map, the cause is almost never the redirect mechanism. It is intent mismatch, internal-link equity loss, or redirect-chain latency, usually several at once, and the redirect verification told you nothing about any of them.

It helps to separate two things a redirect does. It transfers location, telling Google and users where the content moved, and Google’s documented position is that a single 301 passes PageRank with no meaningful loss (the old “lose 15%” rule was retired years ago). What a redirect does not do is transfer relevance for a query if the thing the user lands on no longer answers that query as well. Redirects are a location signal, not a ranking signal. Rankings are reassessed against the new page.

Intent mismatch is usually the hidden cause

This is the dominant reason a clean redirect still bleeds traffic, and it is invisible in any technical audit. Suppose a short, fast “how to reset X in 30 seconds” page ranked for a quick-answer query. During the redesign it was redirected to a new comprehensive 4,000-word guide that covers resetting X among ten other things. The redirect is perfect. But the query was satisfied by speed and a single answer, and the new page makes the user hunt. Engagement collapses, the page no longer demonstrates that it satisfies that intent, and the ranking erodes for that specific query even though it may rank fine for broader ones.

The diagnostic signature is a drop concentrated on queries where the format changed. If the old URL served a narrow intent and the destination serves a broader or different one, you have an intent mismatch, and no amount of redirect tuning fixes it. The fix is content: restore the original content approach on the new URL for the queries that mattered, even if that means a focused page alongside the comprehensive one.

The “changed three things at once” trap

Redesigns routinely bundle a URL restructure, a visual redesign, and a content rewrite into one launch. When traffic drops afterward, the cause is unattributable because three plausible culprits moved simultaneously. Was it the redirects, the new template’s page experience, or the rewritten copy serving different intent? You cannot tell, because you changed all three at once.

The discipline that prevents this is variable isolation: migrate URLs 1:1 first, changing nothing but the address, let it stabilize, then run content consolidation or rewrites as a separate, later project. A traffic drop then has one diagnosable cause instead of three entangled ones. Teams resist this because shipping everything together feels efficient, but it trades a week of sequencing for months of undiagnosable decline.

A page’s rankings depend partly on the internal links pointing at it, and a restructure quietly rewrites the internal-link graph. A destination URL that inherited a clean redirect but lost half its inbound internal links, because the new navigation, breadcrumb, or related-content modules no longer point at it, lost internal PageRank regardless of how well the redirect itself works. The redirect transferred the external equity from the old URL; it did nothing about the internal links the page used to receive from elsewhere on the site and now does not.

This is why the inlink graph belongs in the diagnosis. Compare inbound internal-link counts to the top landing pages before and after the migration. A page that dropped from heavily-linked to nearly-orphaned in the new architecture will lose rankings even with a flawless redirect, and the remedy is to restore those internal links, not to touch the redirect.

Redirect-chain latency and consolidation wounds

Two more self-inflicted causes:

  • Chains. A single 301 passes signals cleanly, but old-URL to interim-URL to final-URL adds hops, and each hop adds latency and a chance for signals to erode or a step to break. Crawl this and flatten every chain to one hop pointing straight from the original URL to the final destination. Chains accumulate invisibly: a migration two years ago left old-to-interim, this migration added interim-to-final, and nobody updated the first rule to skip the middle step. The flattening is mechanical once you have the crawl data, but you have to look for it, because no crawler flags a working chain as a problem when every hop returns a valid status.
  • Consolidation during migration. Merging several pages that ranked for distinct queries into one “better” page is a consolidation decision disguised as a redirect. The merged page cannot rank for every query its sources owned; the long-tail and secondary intents collapse into whatever the new page actually targets. If two old pages ranked for genuinely different queries, redirecting both into one sacrifices the rankings of at least one. Keep distinct-intent pages distinct unless you have decided, deliberately, to give up the queries you are merging away.

Diagnostic order

Work it in the order that isolates cause from noise:

  1. Engagement metrics for intent. Compare pre- and post-migration engagement on the top landing pages: engagement rate and average engagement time in GA4. A sharp drop signals the new page is not satisfying the query the old one did, which points at intent mismatch or consolidation.
  2. The inlink graph for equity. Diff internal-link counts to those same pages before and after. A page that lost inbound internal links lost equity; restore the links.
  3. Redirect timing and shape for latency. Confirm every redirect is a single hop, flatten chains, and check the migration timing against when the drop began.

If page experience is in scope, hold it to the documented thresholds (LCP at or under 2.5 seconds, INP at or under 200 milliseconds, CLS at or under 0.1), but treat it as a contributing factor, not the headline, unless the new template clearly regressed.

The reframe that prevents the whole mess: a verified redirect proves the door opens, not that the room behind it answers the question the visitor came to ask. Isolate your variables so that when traffic moves, you can name the one thing that moved it.

Frequently Asked Questions

If my 301s all verify, why would I lose rankings at all?

Because verification only confirms the hop resolves to a live page. Google still re-evaluates the destination against the queries the old URL ranked for, and if the new page serves a different intent, lost internal links, or sits behind a redirect chain, it can rank worse despite a perfect redirect.

Do 301 redirects lose PageRank?

A single, direct 301 passes PageRank with no meaningful loss per Google. The old “about 15% is lost” figure was publicly retired. Chains are the real risk: every extra hop adds latency and a chance for signals to erode, so flatten them to one hop.

How do I tell intent mismatch from an equity problem?

Check engagement first. If engagement on the destination collapsed, the new page is not satisfying the query (intent mismatch). If engagement held but rankings fell, diff the internal-link graph; lost inbound internal links point to an equity problem instead.

Sources

Redirects and Google Search – Google Search Central: https://developers.google.com/search/docs/crawling-indexing/301-redirects
Core Web Vitals (LCP, INP, CLS thresholds) – web.dev: https://web.dev/articles/vitals

Related posts:

  1. SEO Reporting Automation That Executives Actually Read Executives stop reading SEO reports for one reason: the report tells them what the team did, not what the business got. Rankings climbed, impressions rose, the technical-health score improved, a......
  2. Your Mega Menu Is Leaking PageRank to Low-Value Pages A sitewide mega menu and a bloated footer put the same large set of links on every page of your site, so the link equity and crawl signaling flowing out......
  3. Why Changing Your CMS Broke Links You Never Touched A platform migration changes URL structure in ways you did not plan, and that is why URLs you thought you preserved now return 404. Trailing-slash handling, default permalink and path......
  4. Your Chatbot Widget Is Injecting Thousands of Hidden Links A third-party widget (live chat, social embed, review badge, support tool) loads its own markup into your DOM, and that markup often includes links to the vendor and to the......
  5. Your Brand Name Is a Dictionary Word: SEO Survival Guide When your brand is a common word, Google is doing its job correctly, not failing you. The engine is disambiguating: for the bare token "bridge" or "monday" or "apron," it......
  6. Google Demoted Your Page for a Schema Error You Can’t Find Your schema passes every validator, the Rich Results Test reports no errors, and yet the rich results are gone and there is no manual action in Search Console to appeal.......
  7. Why Removing Dates from URLs Killed Your Traffic Stripping the date segment out of your URLs is a full URL migration, and the traffic drop almost never comes from "losing the date" itself. It comes from three stacked......
  8. Why Query Parameters After Hash Symbols Don’t Exist to Google Everything after the # in a URL is a fragment, and the browser never sends it to the server. So when your filter or state lives after the hash, /properties#bedrooms=3......
  9. Why Your Staging Site Is Ranking Instead of Production Staging out-ranking production is a canonical signal inversion, not a simple case of an exposed test server, and treating it as the latter is why the usual fixes fail. Production,......
  10. How to Reverse Engineer Google’s Quality Raters Guidelines for Your Site The Search Quality Rater Guidelines are a public document describing exactly what Google trains its algorithms to detect, which makes them a usable blueprint for self-auditing. You reverse-engineer quality by......
  11. Neighborhood-Level SEO: Why “Local” Isn’t Local Enough Anymore TL;DR Local SEO strategies treating entire metro areas as single markets are leaving rankings on the table. Search behavior varies dramatically between neighborhoods within the same…...
  12. Informational SEO is Dead. Here’s What’s Left. Publishing top-of-funnel informational content primarily to capture search clicks has lost its economics. AI Overviews now answer "what is" and "how to" queries directly inside the results page, so the......
  13. Edge SEO: Implementing Changes at the CDN Layer Edge SEO ships header, redirect, hreflang, schema, and meta changes in hours by running serverless workers at the CDN layer, instead of waiting weeks for an engineering backlog to clear.......
  14. Your Contact Page Ranks Higher Than Your Service Pages A contact page outranks your service pages for the queries you actually care about when two things stack: it carries more internal-link weight than the service pages, and it contains......
  15. Google Keeps Choosing the Wrong Canonical A canonical tag is a hint, not a directive, and Google says so directly: it takes your declared canonical into consideration, but it can and does select a different URL......