Homepage redirect chain
low Crawlability homepage_redirect_chain
What we check
The homepage takes more than one redirect hop to reach a 200 page (for example http → https → www → /en/).
Why it matters
Each hop costs a round trip for every first-time visitor and a little crawl budget. Long chains also make it easier to break things when a rule changes.
How to fix it
Point every legacy variant straight at the final URL in one 301. Most hosts let you combine the HTTPS and host rules into one rewrite.
How to confirm the fix
curl -sIL http://yoursite.com/ | grep -i ^location should print a single line. Glossary: Redirect chain.
In the API response
When this check fails, output.technical_issues contains an item with "id": "homepage_redirect_chain", the affected URLs as evidence and the fix. If it is among the highest-priority problems it also appears in actions (as finding_id) and in plan.
Related checks
- HTTP does not redirect to HTTPS
- www and bare domain both serve the site
- Internal links point at redirects
Run the full audit on your site. One call checks every item in the check reference and ranks the fixes.
Open the playground Endpoint details