HTTP 4xx and 5xx possibilities

When a URL returns a client error (4xx) or server error (5xx), browsers and crawlers cannot load the intended content. Fixing the underlying response protects user experience and crawl efficiency.

What we look for

We use the HTTP status recorded on the latest crawl for the URL (first-hop status as stored). Client errors usually mean “not found” or access rules; server errors mean the origin failed while handling the request. HTTP 410 Gone is skipped, because it is an intentional signal that the resource was permanently removed.

What to do

• 4xx — Restore content at the URL, fix incorrect links pointing here, or return an appropriate permanent redirect if the resource moved.
• 5xx — Resolve application, database, or hosting errors; verify origin capacity and configuration.

Example

HTTP status is decided by the server, not by HTML. After you fix the response (for example restore a 200 with real content), your page markup might look like this:

<!DOCTYPE html>

<html lang="en">
<head>
<title>Leather tote — Acme Handbags</title>
</head>
<body>
<h1>Leather tote</h1>
<p>Product details load here when the URL returns HTTP 200.</p>
</body>
</html>

Technical details

Status comes from our crawl record for that URL. See How the crawler works.