Where these come from
Redirect errors often appear after a redesign or platform move, when new redirect rules stack on top of old ones, or when http, https, www and trailing-slash rules disagree.
Google could not finish following the redirect for this URL. The usual causes are a redirect loop, a chain that is too long, or a redirect to an empty or malformed address.
Redirect errors often appear after a redesign or platform move, when new redirect rules stack on top of old ones, or when http, https, www and trailing-slash rules disagree.
Use a permanent (301) redirect when a page has moved for good. Google treats it as a strong signal that the target should be shown in results.
| Check | How to tell | Fix |
|---|---|---|
| Is there a loop? | Follow the redirect hop by hop with a redirect checker or Lighthouse and see whether an address repeats. | Remove the rule that sends the URL back to an earlier address.[1] |
| Is the chain too long? | Count the hops. Google follows up to 10 redirect hops by default. | Point every old URL straight at its final address in one hop.[2][3] |
| Is the target valid? | Check the final address loads with a 200 status and is not empty or over-long. | Correct the redirect target, or return 404 if the page is gone with no replacement.[1] |
Your website, fully managed — no big upfront cost.
We design, build, host, maintain and keep improving your site for one simple monthly fee.
A one-off custom build you own outright.
A defined scope and a single fixed quote — delivered once, and yours to keep.
Get a free, no-obligation quote for your project. We respond within 24 hours.