404 Error vs Crawl Error: The Core Distinction
A 404 error is a specific HTTP status code — the server received the request, understood it, and responded with a clear message: this resource does not exist. The communication between the crawler or browser and the server completed successfully; the answer was simply 'not found.' That precision matters because a 404 is a resolved transaction with a defined outcome.
A crawl error is an umbrella term for any condition that prevents a search engine bot from successfully accessing and processing a URL. Crawl errors include DNS failures, server timeouts, connection refused responses, redirect loops, and yes — 404 responses. A 404 is always a crawl error. A crawl error is not always a 404. Understanding that hierarchy is the foundation for diagnosing technical SEO problems correctly.
How Each Is Triggered and Detected
A 404 fires when Googlebot or any HTTP client requests a URL and the server returns status code 404. Common triggers on ecommerce stores include deleted product pages, restructured URL paths after a platform migration, expired promotional landing pages, and broken internal links pointing to removed category pages. The server responds; the problem is at the content level, not the infrastructure level.
Other crawl errors fire before or instead of any HTTP response code. A DNS resolution failure means Googlebot cannot even find the server — no status code is ever returned. A connection timeout means the server acknowledged the connection but never completed the response. A 5xx server error means the server responded but reported an internal failure. In Google Search Console, these categories appear separately under the Coverage and Page Indexing reports, allowing for precise triage.
Impact on Indexing and Rankings: Where They Diverge
A 404 response signals to Google that a URL is definitively gone. After repeated 404 responses over several crawl cycles, Google drops the URL from its index. For ecommerce stores, this is the primary risk when product lines are discontinued or SKUs are removed without redirects — indexed pages that drove organic traffic simply disappear from search results.
Non-404 crawl errors carry a different implication. A URL returning server errors (5xx) or timing out is not treated as gone — Google holds it in a pending state and retries. If a product page returns 503 errors for an extended period, Google interprets this as temporary unavailability rather than permanent deletion. That sounds better, but it means critical pages stay unindexed during the error window, suppressing organic visibility without the clean resolution that a proper 404 or redirect would provide.
Redirect loops and chains are a distinct crawl error subtype that cause Google to abandon the crawl of a URL without assigning it a final status. On large ecommerce catalogs with complex faceted navigation, redirect chains from multiple legacy migrations accumulate quickly and silently drain crawl budget.
How 404 Errors and Crawl Errors Interact in Practice
The overlap zone is where most ecommerce SEO audits get confused. When Google Search Console lists a URL under 'Not Found,' that is a confirmed 404 — the server responded and gave a definitive status. When a URL appears under 'Crawl anomaly' or similar labels, the server either did not respond or responded in a way that prevented Google from processing the page. These require completely different fixes.
A real-world interaction: a store migrates from one platform to another and sets up redirects for top product pages but misses long-tail variants. The missed variants return 404s — confirmed, fixable with 301 redirects. The new platform's server intermittently throttles Googlebot under load, causing connection timeouts on high-traffic category pages — crawl errors, fixable through server configuration and crawl rate settings. Both show up in the same Search Console report but have zero overlap in their root cause or resolution path.
Diagnosing Which Problem You Actually Have
In Google Search Console, navigate to Indexing > Pages and filter by reason. 'Not found (404)' is a 404 error. 'Crawl anomaly,' 'Server error (5xx),' and 'Redirect error' are crawl errors of different subtypes. Export both lists separately — treating them as one combined problem list produces wasted effort and missed fixes.
For crawl errors that are not 404s, run a server log analysis alongside Search Console data. Log files show exactly what status code the server returned for every Googlebot request, including response times. This identifies whether a crawl error is a hard failure (connection refused, DNS) or a soft failure (timeout, 429 rate-limiting). For 404 errors specifically, cross-reference against your internal link audit and sitemap to find the sources pointing to dead URLs — that is where the fix chain begins.
Action Plan: Resolving Each Type Correctly
For 404 errors: audit which 404 URLs have existing inbound links or historical organic traffic. Pages with traffic history warrant a 301 redirect to the closest live equivalent — a discontinued product redirects to its parent category, or to a replacement product if one exists. Pages with no inbound links and no organic history can be left as clean 404s; Google handles those without penalty. Never redirect all 404s to the homepage — Google treats mass homepage redirects as soft 404s and ignores them.
For non-404 crawl errors: prioritize by URL importance. A 5xx error on a top-revenue category page demands immediate server-level investigation. A redirect loop on a legacy parameter URL is lower priority. Fix DNS and server connectivity issues at the infrastructure level before any content-level work. After fixes are deployed, use the URL Inspection tool in Search Console to request re-crawl of high-priority URLs rather than waiting for the next natural crawl cycle.
Document every error type separately in your site health tracking. Mixing 404 counts with general crawl error counts in a single metric creates noise that hides whether the store's technical health is actually improving or just shifting between error types.