Not found (404) in Google Search Console: What to do (and what to ignore)
0.765 min read/
/
A practical guide to the GSC status 'Not found (404)': how to classify URLs (keep/move/remove), when to 301 vs 410, and how to stop crawl waste.
Start with the main guide
GSC Indexing Statuses Explained: What They Mean and How to Fix Them (2026)
A practical map of Google Search Console indexing statuses (Coverage): what each status means, the most common root causes (canonicals, duplicates, robots, redirects, soft 404s), and the fastest way to validate fixes.
Key takeaways
- A practical guide to the GSC status 'Not found (404)': how to classify URLs (keep/move/remove), when to 301 vs 410, and how to stop crawl waste
Contents
Start with the map:
What this status means
Googlebot tried to fetch the URL and got a 404.
That is not automatically a problem. The problem is when 404s create crawl debt and keep Google busy on junk.
Classify URLs (this decides the fix)
Classify each URL into:
- Keep: should be 200 and indexable
- Move: 301 to a true successor page
- Remove: 410 if intentionally removed; otherwise 404
If you want the full playbook:
Fix checklist
- Remove dead URLs from sitemap.
- Fix internal links pointing to 404s.
- 301 only when there is a real successor.
- Use 410 for intentional removals.
Validation
- GSC URL Inspection: confirm the final status code you intend.
- Watch the Pages report for 1-2 weeks (it lags).
Tags
More reading
GSC indexing statuses
View cluster- GSC Indexing Statuses Explained: What They Mean and How to Fix Them (2026)
- Redirect loop: How to find it and fix it (SEO + GSC)
- GSC redirect error: The fastest fix checklist (chains, loops, and canonical URLs)
- robots.txt unreachable: Why it happens and how to fix it
- Blocked due to access forbidden (403): Fix checklist for Googlebot
- Crawl anomaly in Google Search Console: What it means and how to debug