Errors in Google Search Console
Search Console separates missing pages, server failures, redirect problems, and pages that look like errors despite returning a successful response. The right fix depends on whether the URL should still exist. Redirecting every missing page to the homepage can leave visitors without the content they expected.
Where to start
- Check the actual HTTP response and the content shown at an affected URL.
- Restore a page that should exist, or redirect it to a relevant replacement when one is available.
- For intentionally removed pages without a replacement, remove obsolete internal links and sitemap entries and serve an appropriate missing-page response.
Choose the status or metric you’re seeing
How to Fix Soft 404 Errors on Thin or Empty Pages
Soft 404s on thin pages — empty category filters, zero-result search pages, sparse location pages — need a different fix than a broken template. Here's the practical playbook.
Redirect Error: What It Means + How to Fix It
“Redirect error” in Google Search Console means Googlebot couldn't follow your redirect to a working page. Here's why it happens — and exactly how to fix it.
Server Error (5xx): What It Means + How to Fix It
“Server error (5xx)” in Google Search Console means Googlebot got a 5xx response trying to crawl your page. Here's why it happens — and exactly how to fix it.
Soft 404 Error: What It Means + How to Fix It
“Soft 404” in Google Search Console means a page returns a 200 OK status but looks empty or missing to Google. Here's why it happens and exactly how to fix it.
Submitted URL Not Found (404): What It Means + How to Fix It
“Submitted URL not found (404)” in Google Search Console means you submitted a URL that returns a 404. Here's why it happens — and exactly how to fix it.