An HTTP status code is the three-digit number a web server returns with every response, such as 200 for a page that loaded normally or 404 for one that could not be found.
| Term | HTTP Status Code |
|---|---|
| Category | Page Structure and Technical SEO |
| Also known as | Status Code |
| Where it appears | Activity diagnostics and page audit |
What it means in RankGear
Every time RankGear requests a URL — during a crawl, a page audit, or the Activity diagnostics that log each fetch — it records the status code the server sent back. That number is the first signal of whether the page is even reachable. A 200 confirms RankGear pulled the live HTML it needs to score; a 3xx says the request was redirected elsewhere; a 4xx or 5xx means the fetch failed and there is no usable page behind that URL. Because scoring depends on the rendered response, the status code decides whether the rest of the audit can run at all.
How to interpret it
Read the code by its leading digit rather than in isolation. The 2xx range means success, 3xx means the request was redirected, 4xx points to a client-side problem such as a missing or forbidden page, and 5xx points to a server-side failure. A single 404 on a retired URL may be intentional; the same code on a page you expect to rank is a problem worth fixing. Watch for redirect chains that eventually resolve to a 200 but waste crawl budget, and for pages that return 200 while showing an error in the body — a soft 404 that the status code alone will not reveal.
| Code class | What it tells you |
|---|---|
| 2xx (e.g. 200) | Success — the page loaded and can be scored. |
| 3xx (e.g. 301, 302) | Redirect — the request was sent to a different URL. |
| 4xx (e.g. 404, 403) | Client error — the page is missing, forbidden, or otherwise unavailable. |
| 5xx (e.g. 500, 503) | Server error — the server failed to return the page. |
Example
Suppose you audit a product URL that used to rank, and RankGear’s Activity log shows it now returns a 301 to a broad category page instead of a 200. The status code explains the drop before you read a single content metric: the specific page no longer exists to be scored, and the equity it held is being handed to a page that may not match the original query as closely.
Important considerations
- The status code reports reachability, not quality — a 200 confirms the page loaded but says nothing about whether its content is competitive.
- A page can return 200 and still be effectively broken (a soft 404 with error text in the body); check the rendered content, not just the code.
- Status codes are diagnostic signals, not ranking scores. A clean 200 does not make a page rank, and any comparison with ranking pages is comparative context, not a causal lever.
- Codes are captured at fetch time and can change; a transient 5xx during one crawl may resolve on the next, so confirm that an error persists before acting on it.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.