In Neova Needs your Google Search Console or Analytics 4, connected read-only.
Rule last reviewed October 17, 2026 · Guide updated October 17, 2026
A URL still getting search clicks should not return 404 or 410 unless the content is truly gone. If it moved, 301 to the closest equivalent; if it is gone with no replacement, a 404 is fine and Google will drop it.
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-009 · Not Found (4XX) URL Received 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
Element Code: OR-011
TL;DR: A 4XX page still pulling traffic means real people and bots are landing on a broken URL, most often a 404. Every one of those hits is a visitor who wanted something and got an error instead. Find them, and either bring the page back, redirect to the right replacement, or fix the links pointing at them.
SEVERITY
High
AREA
Crawl / UX
COMMON CODE
404 / 410
FIX EFFORT
Low to medium
MAIN TOOL
GA4 + Search Console
What a "4XX Gets Traffic" Issue Is
The 4XX family is HTTP status codes in the 400 to 499 range, which mean the client request failed. The ones you meet in the wild are 404 (not found), 410 (gone, deliberately removed), 401 and 403 (auth or forbidden), and 400 (bad request). When a report says a 4XX page is getting traffic, it means a URL that returns one of these error codes is still receiving visits, from users clicking links, from other sites linking in, from search results that have not caught up, or from your own internal links pointing at a dead target.
A 404 with zero traffic is housekeeping. A 404 with steady traffic is money and link equity leaking out of a hole in the floor. Those are the ones worth your afternoon.
Why It Matters
You lose visitors mid-intent. Someone wanted your product, your article, your contact page. They got an error and, unless your 404 page is unusually helpful, they leave.
Link equity evaporates. If external sites link to a URL that now 404s, the ranking value those links carried is largely wasted. Redirect the URL and you recapture it.
Reports fill with noise. Crawl budget is not the cost here, since Google treats a 404 or 410 as a strong signal not to crawl that URL again, but trafficked dead URLs clutter your reports and hide the problems that matter.
It signals neglect. A pile of trafficked 404s usually means a migration went wrong, a plugin broke slugs, or internal links were never updated.
Decision Path: What to Do With Each 4XX URL
Trafficked 4XX URLShould this pagestill exist?YESNORestore the pageor fix broken slugIs there a closereplacement?YESNO301 to replacementReturn 410,helpful 404 page
How to Find Them
GA4. Filter your page report by page title or path for your 404 template (for example, title contains "Page not found"). Sort by views to see which dead URLs actually get traffic. Add the referrer dimension to learn where the clicks come from.
Search Console. The Pages report under Indexing lists "Not found (404)" URLs Google has tried to crawl. The Links report shows which of your dead pages still have external links worth recapturing.
Screaming Frog or Sitebulb. Crawl the site to find internal links pointing at 4XX targets. The "Response Codes" tab plus "Inlinks" tells you exactly which pages contain the broken link so you can fix the source.
Server logs. The ground truth. Grep the access log for 404 and 410 responses to see real request volume, including bot hits you will never catch in analytics.
Which Fix for Which Situation
Situation
Right Response
Why
Page removed by mistake
Restore it, return 200
Traffic wanted that exact content
Slug or link typo
Fix the internal link
Cheaper than a redirect, cleaner crawl
Replaced by newer page
301 to the replacement
Recaptures links and sends users on
Gone for good, no equivalent
410 plus a helpful 404 page
Tells Google to drop it, guides users
Should be login-gated
Confirm 401/403 is intended
Not every 4XX is a bug
Step by Step Fix
List the trafficked 4XX URLs. Pull from GA4 and Search Console, sort by traffic, and grab referrers and external links for each.
Decide the intent per URL. Use the decision path above. Do not blanket-redirect everything to the homepage; a soft 404 to the homepage is worse than a clean 404.
Restore what should exist. If a real page was deleted or its slug broke, bring it back at the original URL and confirm it returns 200.
Redirect deliberate replacements. Add 301 redirects to the closest genuinely relevant page. One-to-one, not one-to-homepage.
Retire the truly dead. Return 410 for content that is gone with no replacement, and make sure your 404 template offers search and popular links.
Fix the source links. Update internal links pointing at dead URLs. For high-value external links, ask the linking site to update, or at minimum keep a redirect in place.
Validate. Recrawl with Screaming Frog, use the URL Inspection tool in Search Console, and watch the 404 count trend down over the next few weeks.
What "Good" Looks Like
Trafficked 404s trend toward zero. Removed pages either redirect one-to-one to a relevant replacement or return a clean 410. External links to old URLs are recaptured via 301. Your internal links point only at live pages, so Screaming Frog shows no internal 4XX. And your 404 page, for the stragglers that will always exist, actually helps: search box, top links, no dead end. You will never hit a perfect zero, but you should never see a 404 quietly eating a thousand visits a month either.
DO
Prioritize 404s by traffic and inbound links
Redirect one-to-one to genuinely relevant pages
Use 410 for content deliberately retired
Fix the internal links causing the errors
Make your 404 page useful, with search and links
DON'T
Blanket-redirect every 404 to the homepage
Ignore 404s just because they still get clicks
Leave a soft 404 returning a 200 status
Forget the external links pointing at dead URLs
Assume all 4XX codes are accidents (some are intended)
FAQ
Do 404 Pages Hurt My Rankings?
A normal number of 404s is fine; Google expects them and says they do not directly harm your site. The damage is indirect: lost users, wasted link equity, and noisy reports when trafficked URLs stay broken. Fix the ones with traffic and inbound links first.
Should I 301 Every 404 to My Homepage?
No. Google treats a redirect to an irrelevant page, usually the homepage, as a soft 404 and largely ignores it. Redirect only to a genuinely relevant replacement. If there is no good match, a clean 404 or 410 is the better answer.
What Is the Difference Between 404 and 410?
404 means not found, which could be temporary. 410 means gone, a deliberate permanent removal. Google tends to drop 410 URLs from the index a little faster, so use 410 when you know the content is never coming back.
Where Does the Traffic to a 404 Even Come From?
Usually four sources: outdated external links from other sites, stale search results still indexing the old URL, your own internal links pointing at a dead target, and bookmarks or shared links. GA4's referrer dimension and Search Console's Links report tell you which one applies.
Drowning in trafficked 404s after a migration?
Broken URLs with real traffic and inbound links are recoverable value. We map every dead page to the right fix, recapture the link equity, and clean up your reports.