**A redirect should be a single, clean hop — not a chain.** This check follows the full redirect path for a URL, counts how many hops it takes to reach the final page, detects loops, and flags a temporary `302` used where a permanent `301` belongs. Long chains waste crawl budget, slow the page, and give impatient AI fetchers a reason to give up before they ever reach your content.
It follows the URL's redirect chain from start to finish and evaluates how clean that path is. It looks at several things:
- Hop count — how many redirects it takes to reach the final page. Direct or one hop is healthy.
- Redirect type — whether a permanent move uses a 301 (passes ranking signal) or a 302/307 (temporary, which doesn't transfer value the same way).
- Loops — a chain that points back on itself and never resolves, trapping the crawler.
- Chain end — whether the chain finishes at a real 200 page or at an error.
A direct 200 or a single clean 301 passes; two hops is a warning; three or more, a loop, or a chain ending in an error fails.
GEObubbly requests the URL and follows each Location redirect, recording every hop and its status code until it reaches a final response — flagging loops and noting where a 302 is used for what looks like a permanent move. It's a core check worth 2 points in Crawlability & Indexability and runs partially, since following the full chain depends on the live server responses.
Every extra redirect hop adds latency and consumes crawl budget — the limited number of requests an engine will spend on your site. On large sites, chains can mean important pages get crawled less often. Each hop also risks losing a little ranking signal, and using a 302 for a permanent move tells engines not to pass authority to the new URL at all, which can quietly suppress the destination's rankings. For GEO the stakes are higher still: AI fetchers run on tight timeouts and are quicker than search bots to abandon a slow, redirect-heavy URL before reaching the content — so a chain can keep you out of AI answers entirely. The fix is simple: point each redirect straight at the final destination with the correct 301, so there's at most one hop. Clean redirects keep the rest of the Crawlability & Indexability signals working and the page fast for both search and AI.
A redirect chain is when a URL redirects to another URL, which redirects again, before finally reaching the destination — two or more hops instead of one. It's bad for SEO because each hop adds latency, consumes crawl budget, and risks losing a little of the ranking signal passed to the final page. Crawlers may also give up before reaching the end of a long chain. The goal is to point every redirect directly at the final URL so there's at most a single hop between the original link and the live page.
A 301 is a permanent redirect: it tells engines the page has moved for good and to pass the old URL's ranking signal to the new one. A 302 (and 307) is temporary: it says "this is a short-term detour, keep indexing the original." The common mistake is using a 302 for a move that's actually permanent — engines then don't transfer ranking value to the destination, which can suppress it. Use a 301 whenever the change is permanent; reserve 302 for genuinely temporary redirects.
Aim for zero or one. A direct 200 (no redirect) or a single clean 301 to the final URL is ideal. Two hops is a warning worth cleaning up. Three or more hops — or any redirect loop — is a real problem: it wastes crawl budget, slows the page noticeably, and can cause crawlers, especially AI fetchers on tight timeouts, to drop the URL before reaching your content. If a page sits behind a chain, update the links and redirects to point straight at the destination.
A redirect loop is when URLs redirect to each other in a cycle that never resolves — for example, A redirects to B and B redirects back to A — so the page never loads and crawlers (and browsers) eventually give up with an error. It usually comes from conflicting rules: an HTTP-to-HTTPS rule fighting a www/non-www rule, or a CMS and server config both trying to redirect the same path. To fix it, map out every redirect rule touching the URL and make sure they all funnel to one single canonical destination without sending anything back.
Yes, and often more sharply than classic search. AI crawlers like GPTBot and PerplexityBot run on tight timeouts and are quicker than search bots to abandon a slow or redirect-heavy URL before they reach the content. A long chain can therefore keep a page out of AI answers even when it would eventually be indexed by Google. Because being cited by AI depends on the crawler actually reaching and reading your content, minimising redirects — a single clean 301 at most — directly improves your odds of being included in AI-generated answers.