Skip to the content
searchboar.

Crawling and indexing

What is an HTTP status code?

An HTTP status code is a three-digit response describing what happened when a server processed a request, such as 200 for success, 301 for a permanent redirect or 404 for content not found.

Also known as: HTTP status code · response code

At a glance

  • Interpret the response code together with the content and intended behavior.
  • A successful 200 response does not guarantee indexing or useful content.
  • A correct 404 for removed content differs from an accidentally unavailable service page.
On this page
A browser requests content from a server that can return cards representing different response statuses.
An HTTP status code provides a technical signal about the request’s result; it is not the page’s text.

Where does the status code appear?

When you open a URL, your browser requests it from a server. The response includes more than the visible page: it also contains a status and headers. Browsers do not normally display the code prominently, so an attractive error page can conceal an incorrect technical response.

You can inspect the code in browser developer tools or a suitable URL-checking tool. Search crawlers receive these responses too. A content editor showing “published” is not enough to establish what a visitor or crawler actually receives.

What do the main groups mean?

GroupGeneral meaningExample
2xxSuccessful processing200: successful response.
3xxRedirection or another response-handling step301: permanent move.
4xxA request or access problem404: not found.
5xxA server-side problem503: temporarily unavailable.

The group does not replace the precise meaning of each code. A 401 can require authentication, a 403 refuses access, and a 404 indicates a missing resource. Do not swap them merely to make an error report look cleaner.

Why must the code match the content?

A missing product might display “Not found” while returning 200. The technical response says success, but the content describes absence. A search engine may interpret that as a soft 404.

The reverse is also possible: a useful article appears in the browser but arrives with an error code. Google’s technical requirements distinguish a successful response from indexable content. Both deserve checking.

Even when a page returns 200, indexing remains a separate decision. The code means the request succeeded, not that the page will appear in search.

A genuine HTTP 404 response is appropriate when the requested resource cannot be found and there is no suitable replacement. The page can still offer a useful explanation and navigation. Redirecting every missing address to the homepage does not make the original content available again and can leave the visitor without the answer they requested.

An example: three event pages

Imagine a training provider managing three old event URLs. One course has moved to a genuine replacement page. Another has ended permanently with no successor. A third registration page is unavailable during a short outage.

A permanent redirect may suit the first case. A not-found response can accurately describe the second. The third requires handling a temporary server problem and restoring the service; declaring the page permanently removed would describe a different situation.

All three can look like “I cannot see the original page,” yet they call for different responses.

How should you investigate a URL?

Record the complete address and what it should show. Inspect the first response and the final destination after any redirects. Some tools show only a final 200 and hide a long or faulty chain before it.

Test without being signed in when checking a page intended for the public. Your own session may grant access that a new visitor does not have. This does not mean making private content public; it means checking the intended boundary.

One 404 does not prove the whole site is broken. One 200 does not prove everything works. One 503 does not reveal the duration or impact of an outage. Useful technical SEO diagnosis records the URL, time, actual response and expected result together.

Sources

  1. Google Search: HTTP status codes and network errors
  2. Google Search: technical requirements
  3. Google Search: redirects and Google Search