Is fixing every crawl error worth it, or only some?
- Published November 6, 2026
- Linked from 1 answer
- In a cluster of 77
Only some. Entries in Search Console’s reports can describe URLs that are behaving exactly as they should: pages you deleted on purpose, URLs you blocked on purpose, parameter variants you never wanted indexed. Google’s own Page indexing report help says so: “It might not always make sense to fix and validate a specific issue on your website: for example, URLs blocked by robots.txt are probably intentionally blocked.” The goal is not an empty report. It is no errors on URLs that should work.
One question sorts the list
For each reported URL, ask: should this URL load and be findable in search?
| Answer | Example | Action |
|---|---|---|
| No, and it is gone on purpose | A discontinued product with no successor, an old campaign page | Leave the 404 |
| No, and it is blocked on purpose | Admin paths, internal search results, cart URLs | Leave the block |
| Yes, it should work | A live product returning 404 after a migration, a page returning a server error | Fix it now |
| It is gone, but something still points to it | Internal links, your sitemap, or other sites' links lead to the dead URL | Update your own links and sitemap; redirect if a true replacement exists |
The last row is where the real work hides. A 404 is not a problem in itself, but your own site sending people and crawlers to it is. Google’s HTTP status code documentation notes that 4xx errors other than 429 have no effect on crawl rate, so a pile of intended 404s is not slowing anything down; broken links on your own pages are a visitor problem you can fix in minutes.
Errors that always deserve attention
- Server errors (5xx). Google slows crawling when a site returns them, and indexed URLs that keep failing are eventually dropped. A brief spike during a deploy is not a crisis, but errors that persist or recur deserve a fix; watch the Crawl Stats host status rather than reacting to each entry.
- Redirect errors. Loops and broken chains stop both visitors and Googlebot.
- Soft 404s on pages that should be real. The page loads but looks empty or broken to Google.
- Any error on a page that earns traffic or links. Check the Links report for external links to a URL before deciding it can stay dead.
How to work the report
Filter to the URLs in your sitemap first; errors on pages you have told Google matter are the ones to fix. Then sort the rest by whether anything links to them. A clean-looking report can still hide quiet failures, the ones covered in what technical issue silently kills rankings without an error in Search Console. When you fix a group, use Validate fix so Google rechecks those URLs, and leave the intended 404s and blocks alone.
Add a comment