Redirect (3XX) URL Received Organic Search Traffic
In Neova Needs your Google Search Console or Analytics 4, connected read-only.
Rule last reviewed October 17, 2026 · Guide updated July 1, 2026
If a redirecting URL still gets search clicks, Google still shows the old URL. Use a permanent redirect (301 or 308) for permanent moves, point internal links and sitemaps at the target, and allow time for recrawl.
How Neova Finds It
From your Google Search Console data, when you connect it (read-only).
Why It Matters
Analytics insights reveal indexation issues and performance opportunities.
The Ticket It Writes
OR-014 · Redirect (3XX) URL Received Organic Search Traffic
How to Check the Fix: 1. Run the check again in Neova 2. Spot-check sample URLs across affected templates 3. Record the re-check date and period label next to the baseline
Neova writes this ticket for every affected page group and sends it to Jira, Linear, Asana and the rest, after you approve it.
The Full Guide
TL;DR: A URL that is supposed to redirect is still pulling organic clicks and impressions on its own. That means Google is treating the old address as a live, rankable page instead of folding its authority into the target. Confirm the redirect is a clean single-hop 301, kill any stray internal links to the old URL, and give Google time to reprocess.
Check code
RE-024
Category
Organic
Severity
Medium
Detect with
GSC + logs
Typical fix
Verify + wait
What This Check Is Actually Flagging
You redirected a URL. Weeks later, that same old URL is still showing up in your Search Console performance report with its own clicks and impressions, and maybe it is still the address Google lists in the SERP. That is what "Redirect Gets Traffic" means: the source of a redirect is behaving like an independent, indexable page instead of a page whose value has been passed forward to the destination.
In a healthy migration, a 301 tells Google "this content moved, treat the new URL as canonical." Google eventually drops the old URL from the index and consolidates the ranking signals (links, historical relevance, engagement) onto the target. When the old URL keeps earning organic traffic in its own right, that consolidation has not happened, or something is actively blocking it. You end up with authority stranded on an address you told everyone to stop using.
Why a Lingering Redirect Source Hurts You
Two problems. First, split equity. If Google still ranks the old URL for some queries and the new URL for others, neither page is getting the full weight of your backlinks and topical history. You are competing with your own ghost. Second, user experience friction. Every visitor who lands on the old URL from search eats an extra hop before they see content. On mobile and on slow connections that hop is measurable latency, and chained redirects make it worse.
There is also a diagnostic angle. A redirect source that keeps ranking is often a symptom of a deeper config issue: a redirect that is really a 302, a redirect chain, a canonical tag that contradicts the redirect, or internal links that keep feeding the old URL fresh crawl signals. The traffic is the smoke. You want the fire.
How Google Should Process a Redirect (And Where It Stalls)
Clean 301: signals consolidateOld URLreturns 301New URLreturns 200Old URL drops from indexequity passes to target
Stalled: old URL still ranksOld URL302 / chain / mixedGoogle keeps old URLindexed and rankableSplit equitytwo weaker pages
How to Detect It Properly
Do not trust a single tool. Triangulate.
Search Console, Performance report. Filter the Pages tab for the old URL. If it still shows clicks and impressions in the last 28 days, Google is still surfacing it. Compare that curve against the new URL: is the new one climbing as the old one falls, or are both flat?
URL Inspection. Paste the old URL into GSC URL Inspection. A properly processed redirect reports "Page with redirect" and points at the target. If it says "Submitted and indexed" or shows the old URL as its own canonical, the redirect is not being honored.
Screaming Frog. Crawl the old URL directly and read the status code and the redirect chain. You want exactly one hop, a single 301, landing on a 200. Frog will expose 302s, meta refreshes, JavaScript redirects, and chains of three or four hops.
Server logs. Look at how Googlebot hits the old URL and what status your server actually returns. Logs do not lie the way a CDN cache or a plugin sometimes does.
curl. A quick curl -I against the old URL confirms the raw response header before any browser or cache muddies it.
Reference: What the Symptom Usually Means
What You See
Likely Cause
Move
Old URL returns 302
Temporary redirect, Google keeps old URL
Change to 301
Two or more hops before 200
Redirect chain, signals leak at each hop
Collapse to one hop
Old URL canonical points to itself
Contradictory canonical vs redirect
Remove or fix canonical
Internal links still hit old URL
Crawlers keep rediscovering it
Update links to target
Clean 301, still ranks after weeks
Google has not reprocessed yet
Wait, resubmit sitemap
How to Fix It, Step by Step
Confirm the response is a single 301. Not a 302, not a 307, not a meta refresh, not a JS redirect. A permanent redirect is the only signal that reliably consolidates ranking equity.
Collapse chains. If the old URL hops through an intermediate before landing, rewrite the rule so it points straight at the final destination in one step.
Kill contradictory signals. If the old page still emits a self canonical or is listed in your sitemap, remove those. You cannot tell Google "this moved" and "this is canonical" at the same time.
Fix internal links. Search your codebase, menus, and content for links to the old URL and repoint them at the target. Every internal link to a redirect wastes crawl budget and keeps the old address alive in Google's memory.
Resubmit and nudge. Update your XML Sitemap to list only the new URL, submit it, and use URL Inspection on the old URL to request Google reprocess it.
Then wait. Consolidation is not instant. On a well linked site it can take a few weeks; on a large or slowly crawled site, longer. If the redirect is clean and everything else is consistent, patience is the fix.
DO
Return a single, permanent 301 from old to new
Point every redirect straight at the final URL
Repoint internal links and sitemaps to the target
Verify with Frog, logs, and URL Inspection together
Give consolidation real time before you panic
DON'T
Use a 302 when the move is permanent
Leave a self canonical on the redirected page
Keep the old URL in your XML Sitemap
Stack redirects into a chain of hops
Assume traffic on the old URL is free bonus traffic
What Good Looks Like
The old URL returns one clean 301 to the target. URL Inspection reports "Page with redirect." No internal links point at it, it is out of the sitemap, and its clicks in Search Console are trending toward zero while the target absorbs them. The destination page holds the rankings the old URL used to have, plus whatever it earned on its own. One strong page, not two weak ghosts.
FAQ
Is a Redirect That Still Gets Traffic Always a Problem?
Not always. Right after a migration it is normal for the old URL to keep some traffic while Google reprocesses. It becomes a problem when the redirect is not a clean 301, or when the old URL is still ranking weeks later with no downward trend.
How Long Should Consolidation Take?
There is no fixed number. For a frequently crawled page it can be a couple of weeks. For deep pages on large sites it can take much longer. Google has said 301s pass signals, but reprocessing depends on crawl frequency.
Does a 302 Pass Ranking Signals?
Google has stated it can eventually treat a long lived 302 like a 301, but you should not rely on that. For a permanent move, use a 301 so the intent is unambiguous.
Should I Resubmit the Old URL in a Sitemap to Speed Things Up?
No. Keep the old URL out of your sitemap entirely and list only the target. Submitting a redirected URL sends a mixed signal. Use URL Inspection on the old URL if you want to prompt a recrawl.
Redirects Still Splitting Your Rankings?
Migrations that never fully consolidate quietly cap what a site can rank for. If old URLs keep bleeding traffic, get a proper audit of your redirect map and index signals.