MCPRemote MCP server for Cursor and Claude Code, on your existing API key→ Read the docs
QuikSEO.com
Sign inStart Free Audit

Audit rules

Page Answers With an Error Status

The final response of the page, after redirects, has a 4xx or 5xx status, so Google does not index its content. In a QuikSEO audit, a failure of this rule has error severity and counts against the score. Below are the exact condition, its exceptions and the sources behind it, followed by the other rules of the same group.

http.error_statusError

01 — Definition

How This Rule Is Checked

The rule is a pure function of the fetched page: no extra requests, no account settings. The same input always gives the same result.

Rule Severity and Score

Rule id
http.error_status
Group
HTTP
Severity of a failure
Error
Counts in the score
Yes, whenever it applies to the page
Required for a score
No

Condition and Exceptions

Condition
Fetched page whose final status (after redirects) is 4xx or 5xx → fail; when the page is declared as not expected to be indexed (expect_indexing false) → review (warning)
Exceptions
2xx → pass; HTML mode or no final status → not_checked; a final 1xx/3xx → not_checked; 401, 403 and 429 never reach the rules (access blocked)

Sources and Project Decision

Sources
How HTTP Status Codes Affect Google's Crawlers (Google Search Central, Q01)
Project decision
Severity error is a project decision [D]: a 4xx or 5xx page cannot be indexed. When the owner declared that the page is not expected to be indexed (the "Should be indexed" setting set to no), the result is review. 401, 403 and 429 answers never reach the rules (the audit is reported as access blocked).

02 — HTTP

Other Rules in This Group

The other checks of the same group, each with its own condition and sources.