A “Redirect error” means Google tried to follow a redirect from one of your pages and couldn’t reach a working final page, so it didn’t index that URL. Unlike “Page with redirect”, which is usually harmless, this one is worth fixing if the page matters to you. Google lists four causes: a redirect chain that’s too long, a redirect loop, a redirect that builds a URL longer than the maximum, or a bad or empty URL somewhere in the chain. The fix is almost always the same idea: make each old address point straight to one working page.
What Google says the error means
Google’s Page indexing report help page (checked 17 November 2026) lists “Redirect error” under reasons a page isn’t indexed, and gives these four causes:
- 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
It suggests using a debugging tool such as Lighthouse to get more detail. That’s good advice for developers, but for most small business owners, a simpler check (below) will tell you which of the four you have.
How long is “too long”?
Google’s guide to moving a site with URL changes (last updated 20 August 2026, checked 17 November 2026) says Googlebot “can follow up to 10 hops” in a redirect chain, but advises redirecting to the final destination directly. If that isn’t possible, it recommends keeping chains short: “ideally no more than 3 and fewer than 5”. It also notes that chains add delay for visitors and that not all browsers handle long chains.
So even a chain that Google technically follows is worth tidying. Every hop is a short wait for the person tapping your link.
The four causes in plain English
| Cause | What it looks like | Common small-site trigger |
|---|---|---|
| Chain too long | A → B → C → D → … | Several redesigns, each adding redirects on top of the last |
| Loop | A → B → A | Two rules fighting, such as “add www” and “remove www”, or “force HTTPS” set in two places |
| URL too long | Each hop adds to the address until it breaks | A rule that appends the path or a parameter on every redirect |
| Bad or empty URL | A → (nothing) or A → a mistyped address | A typo in a redirect plugin, or a redirect to a page that was later deleted |
A hypothetical loop
This is a hypothetical example. A [Business name] tuition centre moves to HTTPS. Their hosting panel has a “force HTTPS” switch, and a security plugin on the website has one too. One sends visitors from http:// to https://www., the other from https://www. back to a version without www, and a third rule sends that back again. In a browser, visitors see “This page isn’t working: too many redirects”. In Search Console, the URL shows as “Redirect error”.
A ten-minute check to find which one you have
- Open Search Console and go to the Page indexing report. Click “Redirect error” to see example URLs.
- Copy one example URL and paste it into a free online redirect checker (search for “redirect checker”). These show each hop and the status code at each step.
- Read the result:
- The same addresses repeating? That’s a loop. - Lots of hops before a working page? That’s a long chain. - The address getting longer each time? That’s the URL length problem. - Ending on an error, a blank address or a page that doesn’t exist? That’s a bad URL.
- Open the URL in a private browser window too. If it fails there, your visitors are hitting the same problem, not just Google.
Google’s URL Inspection tool can also run a live test, but note one quirk from the Page indexing help: the live test follows redirects and tests the final URL without telling you it did. A redirect checker shows the hops more clearly.
How to fix each cause
- Long chain: Change the first redirect so it points straight to the final page. If A goes to B, then C, then D, make A go directly to D. Do the same for B and C.
- Loop: Find the rules that disagree. Decide on one version of your address (for example,
https://withwww) and make sure only one place in your setup enforces it: your host, your CDN or your website, not all three. - URL too long: Look for a rule that adds something on every redirect. This usually needs your developer or hosting support.
- Bad or empty URL: Correct the typo, or point the redirect at the right live page. If there’s no sensible replacement, it may be better to let the old URL return a 404 than to redirect it somewhere irrelevant.
Google’s site-move guide also warns against redirecting many old URLs to one unrelated page, such as the homepage, because that “can confuse users and might be treated as a soft 404”.
Update your own links while you’re there
If your menu, footer or sitemap still links to old addresses, every visit starts a redirect. Point your own links at the final URLs. Google’s site-move guide recommends this to reduce delay for users and load on your server.
After you’ve fixed it
- Test the URL again in the redirect checker. You want one hop (or none) ending on a page that loads.
- Click “Validate fix” on the Redirect error details page in Search Console. The Page indexing help says validation typically takes up to about two weeks, sometimes longer, and that you should wait for one round to finish before starting another.
- Don’t panic if validation lags. Google also updates the count during normal crawling, whether or not you request validation.
When you can leave it alone
If the URL showing the error is an old address nobody links to, and it doesn’t matter whether it’s indexed, you can reasonably leave it. The Page indexing help is clear that not every URL needs to be indexed. Fix redirect errors on pages you care about: service pages, guides people still link to, and anything in your menu or sitemap.
What’s in your control, and what isn’t
In your control: your redirect rules, where they’re set, your own internal links and your sitemap.
Not in your control: when Google recrawls, how fast validation finishes, and whether a fixed page gets indexed. Google says indexing is never guaranteed. Fixing a redirect error removes a barrier that stops a page being indexed. It doesn’t promise a ranking or more traffic.