"Redirect error": what it means and how to fix it
The redirects for this page are broken, too long, or go in a circle.
By Bruno Amorim · ·
What it means
Google tried to follow the redirects from this page and failed. Usually the redirects go in a circle, there are too many, or one points to a bad address.
The fix, in short: Send each old address straight to the final page in one redirect, and remove any rule that sends visitors back.
Which of your pages have this problem? Find out for free.
Get my free reportCommon causes
- Two rules send visitors back and forth to each other.
- Many redirects in a row after a site move.
- A redirect address that is too long or empty.
How to fix it
- Send old addresses straight to the final page, in one step.
- Test the page with a redirect checker, and remove any circles.
If "Validate fix" failed
Validation fails here when the chain still loops or runs too long. Google generally follows up to 10 redirect hops. Test the exact address from the report with a redirect checker, with and without www and the slash at the end. See what each validation result means.
Fixes by platform
On Blogger
Check three settings in Blogger: HTTPS redirect, Redirect domain (which sends your bare domain to www), and Custom redirects under Errors and redirects. If your domain registrar also forwards one version of the domain to the other, the two can send visitors in a circle. Let only one of them do it.
On Webflow
Webflow's "too many redirects" fix is to check your DNS records against Webflow's, then click Make default next to the root domain or the www domain, and publish. Also check Site settings > Publishing > 301 redirects for a rule whose target redirects back to it. More in Webflow site not showing on Google.
On Next.js
Loops usually come from a redirect in Proxy (middleware) or next.config that also matches its own target, or from a rule that fights trailingSlash. redirect() called after streaming starts sends a meta tag, not an HTTP redirect. Redirect in next.config or Proxy instead, so Google gets a real 308 or 307. More in Next.js pages not indexed.
On Squarespace
Squarespace's help says this can refer to your http address redirecting to https, or the bare domain redirecting to www. If that is the case for these pages, you can ignore it. More in Squarespace website not showing on Google.
How to find these pages
In Search Console, open Indexing > Pages and click the "Redirect error" row. Search Console shows up to 1,000 example pages. CrawlCoach checks up to 50,000 pages per site and sorts them by reason, so you know which pages to fix first.
Questions
What counts as a redirect error?
Google's help lists four cases: a chain that is too long, a loop, a redirect address that is too long, and a bad or empty address in the chain.
Why does Blogger show Redirect error in Search Console?
Check whether your custom domain redirects in two places: in Blogger and at your domain registrar. Two redirects for the same domain can send visitors in a circle. Keep one. The Blogger note above lists the settings to check.
Related guides
- "Page fetch: Failed" in URL Inspection: each reason and its fix
- "Sitemap could not be read" and General HTTP error: how to fix it
- Bing "URLs that are redirecting": when to fix it
- "Page fetch: Failed: Redirect error": how to fix it
- Sitemap URL errors: URL not allowed, Path mismatch, and Invalid URL
- The best Google index checker tools
Sources
- Search Console Help: Page indexing report
- Google Search Central: How HTTP status codes affect Google's crawlers
- Blogger Help: Manage your blog's settings
- Webflow Help: Fix the too many redirects error
- Next.js docs: redirect
- Next.js docs: trailingSlash
- Squarespace Help: Understanding Google SEO emails and console errors
Which of your pages have this problem?
Get my free reportFree for up to 500 pages. No card needed. Sign in with the Google account you use for Search Console.