Check library · Technical and crawl
Redirect chain
Why it matters
Each extra hop loses a little authority and adds latency.
What to do about it
Point the first URL straight at the final destination.
The engine generates this fix itself using the flatten_redirect strategy. It arrives in your queue as a complete artefact, because an incomplete fix never reaches the queue, and once you approve it the change is pushed and the page re-fetched to confirm it is live.
How it is weighted
These are the values the scoring actually uses, not a description of them. Priority is derived from all three rather than chosen, which is why a high-impact, low-effort finding surfaces above a severe one that would take a quarter to fix.
- Severity
- medium
- Impact
- 40% of the weight this category can carry
- Effort
- 30%, where 100% is a project rather than a change
- Confidence
- 80% that a hit is a real problem rather than a pattern we misread
- Area
- Technical and crawl
Other checks in Technical and crawl
criticalPage is blocked from indexingpage_noindexneeds a decisioncriticalServer errorpage_5xxneeds a decisioncriticalRedirect loopredirect_loopneeds a decisioncriticalrobots.txt blocks a page that should rankrobots_blocks_importantneeds a decisioncriticalPage is not served over HTTPSno_httpsneeds a decisionhighBroken internal linkpage_404_linkedfix writtenhighNo XML sitemap foundno_sitemapfix writtenhighHTTPS page loads insecure resourcesmixed_contentneeds a decision
Check your own site for this
The whole catalogue over a real crawl, in about four minutes, in your browser. No account and no card.