HTTP Guide

Common HTTP status codes explained

Status codes are the first clue in an HTTP header check. They explain whether a request succeeded, redirected, failed, or was blocked.

Status code groups

2xxSuccess responses.The server accepted the request.
3xxRedirect responses.Check the Location header for the next URL.
4xxClient or access errors.The URL, permission, rate limit or request may be the issue.
5xxServer errors.The server, upstream application, proxy or hosting platform failed.

Use the HTTP Header Check tool to see the status code and related headers. A status code is useful on its own, but the surrounding headers often explain the real cause.

Codes you will see often

200 OK means the request succeeded. 301 Moved Permanently and 302 Found mean the server is redirecting the browser. 403 Forbidden means the server understood the request but refused access. 404 Not Found means the path was not found. 429 Too Many Requests means rate limiting. 500 Internal Server Error means the server application failed. 503 Service Unavailable often means maintenance, overload or upstream failure.

For SEO, redirects and error codes deserve attention. A broken 301 chain can slow crawling. A 404 on an important page can lose traffic. A 500 or 503 during a crawl can make search engines temporarily reduce trust in the page availability.

Troubleshooting by status code

  1. For 3xx, inspect Location and make sure the final page is correct.
  2. For 403, check firewall rules, CDN rules, bot protection, file permissions and country restrictions.
  3. For 404, confirm the path, routing rules, deployment output and case sensitivity.
  4. For 429, reduce request rate and check API or security limits.
  5. For 5xx, review application logs, reverse proxy logs, upstream health and hosting status.

Status codes can vary by user agent, IP address, country, cookies and request method. A page may respond differently to HEAD, GET, bots and logged-in users.

FAQ

Is 301 better than 302?

Use 301 for permanent moves and 302 for temporary redirects. Search engines treat them differently over time.

Can a page be down with HTTP 200?

Yes. A server can return 200 for an error page if the application handles failures incorrectly.

Why does a browser work but header check fails?

Some servers treat HEAD requests differently, require cookies, or block automated user agents.

What is a redirect loop?

A redirect loop happens when URLs keep redirecting back and forth without reaching a final page.

Which status code is worst for SEO?

Persistent 5xx errors and broken redirects are especially harmful because they prevent reliable crawling.