A crawl error is what happens when a search engine bot tries to visit one of your pages and can't get a proper answer back. It can strike anyone running a website, from a one-page portfolio to a sprawling online store, and it usually shows up in Google Search Console first, sometimes weeks before you notice the traffic dip that follows.
Why should you care? Because a page Google can't crawl can't be indexed, and a page that isn't indexed might as well not exist. The good news is that most crawl errors have boring, fixable causes: a deleted page, a mistyped redirect, a server that buckled under load. This guide shows you how to find them and fix each type before it quietly buries pages you've worked hard on.
Crawl errors are failed requests. Googlebot asks your server for a URL, and something goes wrong: the page is gone, the server times out, or access is blocked. That's different from indexing problems, where Google reaches the page fine but decides to leave it out of search results.
Here's the distinction:
You fix these in different ways, so identifying your bucket comes first; chasing a noindex problem with redirect fixes wastes your afternoon.
Start with Google Search Console, where the Page indexing report lists every URL Google knows about, grouped by status, with the error groups right at the top. Google's own documentation on the Google's documentation on HTTP and network errors explains each status, and it's worth a read before you start clicking around.
Don't stop there, though: run a crawl of your own site to see your pages the way a bot does. A spider simulator shows you exactly which URLs return errors, which ones redirect, and which ones load cleanly, without waiting for Google to re-crawl.
Most sites face the same handful of errors again and again, and these five cover ninety percent of what Search Console throws at you.
This is the classic error: the page doesn't exist at that URL anymore. If the page moved, set up a 301 redirect to its new home. If you removed it on purpose and nothing equivalent exists, a clean 404 (or a 410) is honestly fine. The sin isn't the 404 itself; it's a 404 on a page that should still be live, or one that important pages still link to.
A 500, 502, or 503 means your server failed to deliver a page. Occasional blips happen during traffic spikes, but persistent 5xx errors tell Google your site is unreliable, and crawl rate drops fast. Check your hosting resources, look for plugin or theme conflicts, and talk to your host if errors cluster at certain times.
Redirect chains that loop forever, chains that run too long, and redirects pointing at dead pages all land here. Map every chain and cut it so each old URL reaches its destination in one hop.
Sometimes the bot never gets through the door: a stray line in robots.txt can block entire folders, and DNS failures mean Google couldn't resolve your domain at all. Test your robots file after every change, and treat DNS errors as urgent, since they usually signal a hosting problem, not an SEO one.
When you sit down to clean up, work through this list in order, from highest impact to lowest.
The guides on the Seovaro blog cover sitemaps, redirects, and page speed too, and they pair well with a cleanup session like this one.
For most sites, a monthly check is plenty; bigger sites and anyone mid-migration should check weekly. The real rule is simple: check whenever you delete pages, restructure URLs, switch themes, or change hosts, because those are the moments errors are born.
Don't panic over every single 404. Panic, just a little, over patterns: climbing errors, errors on money pages, or server errors at any scale, because patterns mean something broke.
Ready to see your site through a bot's eyes? Run your key URLs through the free spider simulator on Seovaro and find your crawl errors today, while they're still small enough to fix over a coffee.
No. A 404 on a page you deliberately removed, with no replacement and no important links pointing to it, is normal. What hurts is 404s on pages that should exist, pages with backlinks, or pages your own site still links to.
It depends on how often Google crawls your site. Important pages on active sites may be re-checked within days, while deep pages can take weeks. Validating the fix and requesting indexing for priority URLs speeds things along.
Please don't. Redirecting unrelated deleted pages to your homepage confuses visitors, and Google treats many as soft 404s anyway. Redirect to the closest relevant page, or let the URL return a genuine 404 if nothing matches.
A crawl error means the fetch failed outright. A soft 404 means the page loaded with a 200 status but its content tells Google it's really a "not found" page, like an empty product page or a dressed-up "no results" message.
