Redirect error in Search Console: chains, loops and broken redirect targets

Google could not follow the redirect: a chain too long, a loop, a URL too long or a bad URL in the chain. Redirect straight to the final page in one hop.

The message in Search Console

Redirect error

Page indexing report, group "Not indexed". Spelling as in Google's help page for the report.

By the Crawlerpeek editorial team · Sources checked · Updated · Editorial standards

What Google says

Google experienced one of the following redirect errors:

  • A redirect chain that was too long
  • A redirect loop
  • A redirect URL that eventually exceeded the max URL length
  • A bad or empty URL in the redirect chain

Source: Google Search Console Help: Page indexing report, read 2026-10-30.

Common causes

  • A chain of redirects that each fix one thing: http to https, then to www, then to a trailing slash, then to a new path. Google's crawlers follow up to 10 redirect hops by default (HTTP status codes and Google Search).
  • A loop: two rules that send the URL back and forth, for example a CMS that removes the trailing slash and a server or CDN rule that adds it.
  • A redirect that appends the old path or query string to the new one each time, until the URL is too long.
  • An empty, malformed or relative Location header, or a redirect to a URL that does not resolve.

How to check

  1. List every hop with curl -sIL https://example.com/old | grep -i -E '^(HTTP|location)'. More than one location line means a chain.
  2. Enter the start URL in the AI crawler checker or see a page as a bot: the result shows the final address and its status.
  3. Run URL Inspection's live test on the URL in Search Console, fix the rule, then click Validate fix.

When to fix it and when to leave it

Do not ignore it for a page you want indexed. If the redirecting URL is old and you no longer need it, a plain 404 is acceptable: Google says 404 responses are not necessarily a problem if the page has been removed without any replacement. A redirect that works is a different, usually harmless message: Page with redirect.

AI crawlers and AI search

Google says long redirect chains have a negative effect on crawling (crawl budget guide). Every hop is another request for every crawler that follows it, so a single direct redirect is the safe choice for search and AI crawlers alike. For /robots.txt, Google follows at least five hops and then treats the file as a 404 (Google's robots.txt specification); check yours with the robots.txt validator.

Questions

How many redirects does Googlebot follow?

Google says its crawlers follow up to 10 redirect hops by default. For robots.txt, Google follows at least five hops and then treats the file as not found.

Is a JavaScript redirect a redirect error?

Not by itself, but Google recommends server-side or meta refresh redirects and says to use JavaScript redirects only if you cannot do those, because rendering can fail.

What does a redirect loop look like?

The location headers repeat: A sends to B and B sends back to A. Browsers stop with an error such as too many redirects.

  • Page with redirect · The URL redirects to another page, so Google does not index it and may index the target. Usually fine: update internal links and the sitemap to the final URL.
  • Server error (5xx) · Your server answered Googlebot with a 500-level status, so the page was not indexed. Find the failing requests in your logs, fix the cause, then validate.
  • Search Console Crawl and Indexing Errors

Sources

Google's documentation, each page read on 2026-10-30. Google updates these pages; if its wording has changed since, Google's page is the reference.

Check the URL: robots.txt per bot, HTTP status, noindex and the HTML a crawler gets.Run the checker