Redirect error
What Is a “Redirect Error”?
“Redirect error” is an error status shown in Search Console’s Page indexing report as a reason a page was not indexed. The official help page says “Google experienced one of the following redirect errors” and lists four cases. GSC Help Center The four are: a chain that is too long, a loop, a URL that exceeds the maximum length, and a bad or empty URL.
A redirect is a normal feature that automatically sends visitors who arrive at one address to another. A typical example is using a 301 redirect to connect an old address to a new one when you change URLs. A “redirect error” reports that this guidance broke down and Googlebot never reached the final page. Think of a post office mail-forwarding request gone wrong. A letter sent to the old address follows the forwarding notice to the new one, but if the notices chain on more than ten times, or point back to the original address, the letter can never be delivered.
How Urgent Is It?
As the name says, it’s a problem you need to fix. Its sibling status, “Page with redirect,” is a natural exclusion where the redirect works and the destination URL becomes the indexing candidate. A “redirect error,” by contrast, means Googlebot failed to reach the destination. Urgency still varies. An old address you abandoned long ago can wait, but if it’s a key page right after a site renewal or domain migration, link signals and visitors are being cut off midway, so act immediately.
Googlebot Follows Only Up to 10 Redirects
Google’s documentation on HTTP status codes explains that “any content Google received from the redirecting URL is ignored, and the final target URL’s content is processed for indexing.” Google (official) In an error state, Google never reaches the destination, so there’s no content to process and the page drops out of the index. The same document also states the limit: “By default, Google’s crawlers follow up to 10 redirect hops.” A hop is a single redirect, one jump.
A loop traps both search engines and users in endless repetition. Ahrefs guide Browsers also give up after following the redirects and show an error screen (ERR_TOO_MANY_REDIRECTS in Chrome), so visitors can’t open the page either. And as Googlebot keeps circling the same path, it wastes the whole site’s crawl budget.
Why It Happens: Four Causes
- Redirect chain too long – Rules pile up layer on layer, sending http to https, then to the www address, then to the trailing-slash address, so the number of hops grows.
- Redirect loop – A sends to B, and B sends back to A, so the chain returns to where it started and never reaches a final destination.
- Redirect URL exceeded the max URL length – This usually comes from a faulty rule that adds a tracking tag (parameter) with every redirect, making the address grow without end.
- Bad or empty URL in the redirect chain – The response field that gives the new address (the Location header) is empty or malformed.
How to Trace the Path
- Step 1 – In the Page indexing report, click the “Redirect error” row to see the list of affected URLs.
- Step 2 – Run the problem URL through the live test in the URL Inspection tool to see whether the same error still occurs.
- Step 3 – Trace the path. The official help page also advises, “Use a web debugging tool such as Lighthouse to get more details about the redirect.” GSC Help Center
curl -sIL "https://example.com/old-page"
HTTP/1.1 301 Moved Permanently
Location: https://example.com/renewal-page
HTTP/1.1 301 Moved Permanently
Location: https://example.com/final-page
HTTP/1.1 200 OK
Above is an example of following the path with the curl command in a terminal. Count how many 301s are chained, and check that it ends with a 200 (OK). If there’s no 200, an address you already passed reappears, or the Location is empty, that is the actual error Search Console caught.
How to Fix It, and What to Watch Out For
Cleaning Up Chains: Straight to the Final Destination
Google’s site move documentation sets the standard. Sending visitors straight to the final page is best, and “If you can’t redirect in one step, keep the number of redirects in the chain low, ideally no more than 3 and fewer than 5.” Google (official)
The work has two steps. Replace the multi-hop path with a single 301 that goes directly to the working (200) page, and update internal links pointing to the old address so they point straight to the final URL, reducing the need to go through redirects at all. Ahrefs guide
Cleaning Up Loops: Break the Circle
Decide which URL is the true destination, then remove the misconfigured rule or fix the destination so that the final page doesn’t redirect anywhere else. Semrush guide Breaking just one of the rules that form the circle stops the loop.
Rules to Follow When Setting Up Redirects
Server-side (HTTP) redirects are the first choice. Google’s official documentation lists the redirect methods and explains that “they’re listed in order of likelihood that Google interprets them correctly (for example, a server-side redirect has the highest chance of being interpreted correctly),” and insists that JavaScript redirects be used only when no other method is possible. Google (official) The same document also distinguishes the types: “Permanent redirect: Show the new redirect target in search results. Temporary redirect: Show the source page in search results.” If you’ve moved an address for good, a 301 (permanent) is the right choice.
Keep fixed redirects in place for a long time. John Mueller advised keeping redirects for at least a year, because Google’s systems need to see a redirect several times before confirming and recording the address change (2021). John Mueller’s remarks If the destination genuinely replaces the original page, you don’t need to worry about ranking signals. In 2016, Google’s Gary Illyes declared that 30x redirects no longer lose PageRank (the ranking signal built up through links). Gary Illyes’s remarks
Telling It Apart from Similar Statuses
Page with redirect is not an error. The official help page describes this status as “This is a non-canonical URL that redirects to another page. As such, this URL will not be indexed.” GSC Help Center It’s a normal state where the redirect worked properly, so there’s nothing to fix.
Not found (404) means the destination itself doesn’t exist, and Server error (5xx) means the server failed to respond. A redirect error means the server does respond, but that response (the forwarding instruction) is tangled. It’s the difference between a warehouse with nothing in it (404), a warehouse with its shutters down (5xx), and a road where the signs to the warehouse keep sending you in circles (redirect error).
References
- Page indexing report – Google Search Console Help
- How HTTP status codes affect Google’s crawlers – Google Search Central
- Redirects and Google Search – Google Search Central
- Site moves with URL changes – Google Search Central
- Google advises keeping 301 redirects for at least a year – Search Engine Journal (2021)
- A guide to 301 redirects – Ahrefs
- Types of redirects and how to fix them – Semrush
Jul.2026By Studio JT