Search Console 404 Errors: How to Find, Prioritize, and Fix Them

Search Console 404 errors aren’t automatically “bad SEO” — they’re a signal you need to classify. If the URL was never meant to exist (spam links, typos), ignore it. If it’s in your sitemap, internally linked, or used to get traffic/backlinks, fix it fast.

This guide shows you exactly how to find 404s in Google Search Console, decide what action to take (ignore vs 301 vs 410 vs restore), and how to set up ongoing monitoring so new 404s don’t quietly accumulate. Examples are written for ecommerce sites (Shopify/WooCommerce), where discontinued products and faceted URLs create 404 noise.

Why Search Console 404 errors matter (and when they don’t)

Google has been consistent on this: a 404/410 is a normal part of the web. A page that doesn’t exist should return 404. The problem is when important URLs accidentally become 404s — or when you create “soft 404s” by redirecting everything to the homepage.

404s you should fix (high impact):

In your XML sitemap (your sitemap should only list indexable URLs)
Linked internally from navigation, collections/categories, blog posts, or footer links
Previously received organic traffic (even small traffic can mean money for ecommerce)
Have external backlinks (you’re leaking link equity)

404s you can usually ignore (low/no impact):

Spam/bot-generated URLs Google discovered from the wider web
Typos that never existed on your site
Random old URLs that have no internal links, no sitemap inclusion, and no traffic history

Search Engine Journal summarized John Mueller’s guidance clearly: if the page isn’t meant to exist, returning 404 is expected — don’t redirect those URLs to your homepage (that often becomes a soft 404).

Where to find Search Console 404 errors

In Google Search Console:

Open your property
Go to Indexing → Pages
Scroll to Why pages aren’t indexed
Click Not found (404)
Export the affected URLs (you’ll use this to categorize and prioritize)

Google Search Console: the Pages report is where 404 errors show up.

The 404 decision tree (ignore vs 301 vs 410 vs restore)

Use this decision tree so your team handles 404s consistently (and you don’t waste time “fixing” harmless noise).

Step 1: Was the URL ever meant to exist?

No (spam links, random strings, fake product URLs) → Ignore. Keep it 404.
Yes → go to Step 2.

Step 2: Is the 404 caused by your site?

Check these three sources first:

Sitemap: is the URL still listed?
Internal links: does any page on your site link to it?
Recent URL changes: did you rename products/collections, change URL structure, or migrate platforms?

If the answer is “yes” to any of the above, it’s a site-caused 404 and should be fixed.

Step 3: Choose the right fix

Option A — 301 redirect to the closest equivalent

Best when there’s a clear replacement (new product version, merged article, renamed collection).
Preserves relevance and link equity.

Option B — 301 redirect to the parent category / collection

Best when the exact item is gone, but the intent still makes sense at a broader level (e.g., discontinued SKU → category page).
Common ecommerce pattern for discontinued products.

Option C — return 410 (Gone)

Use when the content is intentionally removed with no replacement (legal removals, test pages, duplicates).
410 is a stronger signal than 404 that the URL is permanently removed.

Option D — restore the page

Best when the URL had meaningful backlinks/traffic and you can republish updated content (or a product page as an “archived/discontinued” page with alternatives).

Ecommerce-specific 404 scenarios (Shopify/WooCommerce)

If you manage an ecommerce catalog, most 404 problems come from a few predictable patterns:

Discontinued products

If there’s a successor product: 301 → successor
If there’s no successor but category still matches intent: 301 → category
If you never want it indexed again and there’s no substitute: 410
If the product still has backlinks (reviews, affiliates): consider restoring an “archived product” page with alternatives

Out-of-stock vs discontinued

Don’t 404 a temporarily out-of-stock product. That creates churn in Google’s index and wastes any existing rankings. Keep the page live, show “out of stock,” and link to substitutes.

Faceted navigation / filter URLs

Filters can generate many low-value URLs. If they’re 404ing, fix the internal links that generate them. If they’re indexable but shouldn’t be, use canonical/noindex rules — don’t rely on 404 as your “strategy.”

Using DataVessel to classify 404s faster (no dashboards)

DataVessel is a Slack-native AI agent platform that connects your business data sources (including Google Search Console). Instead of exporting CSVs and stitching tools together, you can ask for the exact cut you need and automate monitoring.

Example prompts (copy/paste):

“List new 404s from the last 7 days and group them by source (sitemap, internal links, external links).”
“Which 404 URLs were previously getting organic clicks or impressions?”
“Which 404s are internally linked from our top pages?”
“Create a prioritized fix list: redirect candidates vs 410 vs ignore.”

Slack alert spec: monitor 404 spikes automatically

Finding 404s once is an audit. Catching them early is an operating system.

Recommended alerts (daily digest to #marketing or #ops):

New 404 URLs (24h) with counts
404 spike alert: alert if new 404s today > (7-day average × 2) and baseline ≥ 10/day
Sitemap 404s: any 404 URL present in sitemap (always actionable)
Internally-linked 404s: URLs linked from your site that now 404
High-value 404s: previously had clicks/impressions or known backlinks

This is where scheduled agents help: you can run the checks every morning and post a short, structured report to Slack so someone fixes issues before they accumulate.

Key takeaways

Search Console 404 errors are a classification problem: many are safe to ignore.
Don’t redirect spam 404s to your homepage — that often creates soft 404s.
For ecommerce, discontinued products and filters cause most 404 churn. Use consistent redirect/410 rules.
Automate monitoring so 404 spikes become a Slack message, not a quarterly surprise.

Want this to run automatically? Try DataVessel free and set up a scheduled agent that monitors new 404s and posts a prioritized fix list to Slack.