No redirect chain
What the check finds
Reaching this page takes more than one redirect. It resolves, but each hop wastes crawl budget and adds latency.
Why it matters for AI answers
Each extra hop is another request for a crawler. Some crawlers give up after a few hops, and long chains slow down fetching for search and AI bots alike.
How to fix it
- Update each old redirect to point straight at the final URL in one hop.
- Change internal links, canonicals and sitemap entries to the final URL.
- Keep http to https and host changes in a single rule rather than separate hops.
Related checks
Review this finding in context: Indexability and crawlability guide ›
Still stuck? Contact support ›