Audit rules
Redirect Chain
The requested URL goes through more than one redirect before the final response. In a QuikSEO audit, a failure of this rule has warning 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.redirect_chainWarning01 — 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.redirect_chain- Group
- HTTP
- Severity of a failure
- Warning
- Counts in the score
- Yes, whenever it applies to the page
- Required for a score
- No
Condition and Exceptions
- Condition
- More than one redirect before the final response → fail with the hops
- Exceptions
- 0 or 1 redirect → pass
Sources and Project Decision
- Sources
- Avoid multiple page redirects (Chrome for Developers, Q19)
How HTTP Status Codes Affect Google's Crawlers (Google Search Central, Q01) - Project decision
- Severity warning and the limit of one redirect are project decisions [D].
02 — HTTP
Other Rules in This Group
The other checks of the same group, each with its own condition and sources.
- No Cache Validatorshttp.cache_validators
- HTML Not Compressedhttp.compression
- Page Answers With an Error Statushttp.error_status
- WWW and Non-WWW Both Serve the Pagehttp.host_variant_duplicate
- HTTP Protocol Versionhttp.http2
- HTTP Version Not Redirected to HTTPShttp.http_variant_not_redirected
- Page Not Served Over HTTPShttp.https
- Mixed Contenthttp.mixed_content
- X-Powered-By Version Disclosedhttp.powered_by
- Server Version Disclosedhttp.server_header
- TLS Certificate Expiring Soonhttp.tls_expiring
- Invalid TLS Certificatehttp.tls_invalid