HTTP Status Codes
Three-digit codes a server returns for every request, telling crawlers whether a page loaded, moved or failed.
The Definition
Every response from a web server carries a status code. 2xx means success (200 OK). 3xx means the page moved (301, 302, 307, 308). 4xx means a client error, such as 404 Not Found, 410 Gone or 403 Forbidden. 5xx means the server failed, such as 500 or 503.
Why It Matters
Search engines index pages that return 200. A 404 or 410 eventually drops a page from the index. Repeated 5xx errors make Googlebot slow down crawling. A 'soft 404', an error page that returns 200, wastes crawl budget and confuses indexing.
Best Practices
Return 200 only for pages that really exist
Return 404 or 410 for removed pages; use 410 when the removal is permanent
Return 503 with a Retry-After header during planned maintenance
Fix internal links that point at 4xx or 3xx URLs
Watch the Search Console Page indexing report for server errors
Mistakes to Avoid
- 1
Serving error pages with a 200 status (soft 404)
- 2
Redirecting every removed page to the homepage
- 3
Leaving 5xx errors unmonitored until rankings drop
- 4
Blocking error pages in robots.txt so Google can't see the status
Audit Checks
How Digispot AI identifies and fixes related issues
This page returned a "not found / forbidden" style error (a 4XX status).
Impact: A broken page can't rank, wastes crawl budget, and loses the value of any links pointing to it.
Restore the page if it should exist. • Otherwise 301-redirect it to the closest live page. • Remove or update internal links that point to it.
The page shows an "not found"-style error message but still returns a success (200) status code.
Impact: Google keeps crawling and may index these empty pages, wasting crawl budget and cluttering results.
Return a real 404 (or 410) status for pages that no longer exist. • Redirect to a relevant live page if there is one. • Avoid showing error text on a 200 page.
A redirect hop downgrades the connection from HTTPS to HTTP before resolving.
Impact: It exposes users to an insecure hop (MITM/mixed-content) and signals distrust to search engines, bleeding ranking equity.
Rewrite the redirect target to stay on HTTPS. • Make sure no hop drops to http://. • Re-crawl to confirm the chain stays secure.
The server failed to deliver this page (a 5XX error).
Impact: Search engines can't index a page that errors, and lots of them can slow crawling of your whole site.
Check server/application logs for the cause. • Fix the error so the page returns a healthy 200. • Re-crawl to confirm it resolves.
The page could not be fetched at all — the request never returned a usable document (redirect loop, timeout, DNS failure, or refused connection).
Impact: Visitors and search engines hit the same dead end: the page can't be read, indexed, or ranked, and any links pointing at it are wasted.
Open the URL in a browser and confirm the failure (e.g. "too many redirects" or a timeout). • Fix the server, DNS, or redirect rule responsible so the URL returns a healthy 200. • Re-run the audit to confirm the page is reachable again.
We could not read this page's content properly — the HTML may be broken or the page returned an error mid-load.
Impact: If our crawler cannot read the page, search engines likely struggle with it too, so it may not rank.
Open the page and confirm it loads fully without errors. • Validate the HTML for unclosed tags or broken markup. • Re-run the audit once the page loads cleanly.