WordPress redirect tutorials

How to troubleshoot WordPress redirect loops and chains

Trace each redirect hop, check competing WordPress and hosting rules, and distinguish cached responses from current configuration before changing a live site.

A redirect loop sends a request back to a URL already visited. A redirect chain reaches a destination through several intermediate URLs. Both need the actual sequence of HTTP responses to diagnose: the browser address bar alone can hide the earlier steps.

Record the first response

Start with one affected URL and record its status and Location header. Follow the next URL and repeat. A sequence such as /a/ to /b/ to /a/ is a loop. A sequence such as /a/ to /b/ to /c/ is a chain; if /c/ is the final replacement, consider mapping /a/ directly there.

Do not repeatedly change several redirect systems at once. WordPress canonical redirects, another plugin, the web server and a CDN can all affect the same request. A correct RedirectNest rule can still be followed by an unexpected redirect from another layer.

Common conflicts to check

  • HTTP-to-HTTPS rules that disagree with proxy or hosting settings.
  • www and non-www rules pointing in opposite directions.
  • Trailing-slash or case rules that undo one another.
  • A destination that redirects back to the original source.
  • A broad wildcard rule taking precedence over the intended exact rule.
  • A browser or CDN serving an earlier permanent redirect.

RedirectNest includes loop protections, but a local rule check cannot prove that an external server or another plugin will never create a loop. Use the built-in path test to understand local matching, then verify the full request in the browser's network panel or with an HTTP client.

Make one reversible correction

Save the existing rules first. Pause the suspected rule on a test site, reproduce the request, and compare the response sequence. Once the conflict is identified, make the smallest change that resolves it. Avoid disabling unrelated security or checkout rules as an experiment.

Use the troubleshooting guide and matching guide together. If a rule change must be undone, retained snapshots restore plugin rules; hosting and CDN configuration need their own recovery plan.

Put the idea into practice.

Explore the field guide ↗