No Redirect Chains
Checks that redirects go directly to the final URL — no A→B→C chains.
What this check measures
We follow redirects with a max hop count. Chains of 2+ redirects are flagged — each hop loses ~15% ranking equity and costs extra request time.
Why it matters
Redirect chains waste crawl budget, slow down users, and leak ranking through each hop. A→B→C loses ~30% of original A's equity by the time it reaches C.
How our audit detects it
Follow redirects from entry URL, count hops. Flag chains of 2+.
Typical findings
- error_outlinehttp://example.com → https://example.com → https://www.example.com.
- error_outlineLegacy /old → /new → /newest.
How to fix
Update all redirects to point directly to the final URL. If you have HTTP→HTTPS→www redirects, consolidate to HTTP→https://www directly.
Frequently asked questions
How many hops is too many?expand_more
Want this checked on your site?
Pantra runs the full audit (SEO, Security, GEO, Performance, Schema, Technical, Images) in 10 seconds and generates stack-specific fix prompts.
Scan my siteRelated checks
SSR / Pre-rendering
Checks if the page is server-rendered or statically pre-rendered.
TechnicalHTTP Status Codes
Checks that pages return proper status codes — 200 for live, 404 for missing, 301 for moved.
TechnicalNo Client-Side Redirects
Checks that redirects happen server-side, not via JavaScript.
TechnicalViewport Meta Tag
Checks for <meta name="viewport" content="width=device-width, initial-scale=1">.