A WordPress redirect loop happens when a browser is sent from one URL to another and then back again, so the page never finishes loading. The fastest way to troubleshoot it is to stop making broad changes, identify which URLs are looping, and check the redirect layers one at a time.
Start by noting whether the problem affects the whole website, only the WordPress admin area, only one page, or only one version of the domain. That distinction often points toward the cause.
First, confirm that it is actually a redirect loop
A redirect loop is different from a broken link, a slow page, or a server timeout. Common signs include a browser message about too many redirects, a page that repeatedly reloads, or a login page that keeps sending you back to itself.
Test the affected URL in a private browsing window and, if possible, on another device. This does not fix the underlying problem, but it can help show whether stale browser cookies or cached redirect behavior are part of what you are seeing.
Check whether the problem affects one URL or the whole site
If the homepage, internal pages, and WordPress login all fail, the issue is probably site-wide. If only one page loops, look for a redirect rule, plugin setting, or page-level configuration tied to that URL.
If only the login or admin area loops, cookies, security settings, URL configuration, or a plugin can be more likely than a general page redirect.
Compare the WordPress Address and Site Address
WordPress keeps settings for the WordPress Address and Site Address. If those values disagree with the domain visitors are actually using, redirects can bounce between different versions of the site.
Pay close attention to differences such as:
- http versus https.
- http://www.example.com versus example.com.
- An old domain versus a new domain after a migration.
- A temporary or staging URL that was never fully replaced.
Do not change these values casually on a live site. An incorrect URL setting can make the dashboard harder to reach. If you are planning a broader URL or domain change, the WordPress website migration checklist covers checks that are useful before moving or changing site locations.
Check HTTP and HTTPS rules next
One common redirect-loop pattern is that one layer forces HTTPS while another layer sends the request back to HTTP. A similar conflict can happen when a host, CDN, security plugin, or redirect plugin each tries to control the same protocol change.
If the site recently moved to HTTPS, confirm that WordPress, the hosting environment, and any proxy or CDN agree on the secure URL. Mixed content is a separate HTTPS-related problem that can be handled after the main redirect issue is resolved.
Check www and non-www consistency
Your website should normally settle on one preferred hostname. If one rule forces the www version while another forces the non-www version, the browser can be trapped between them.
Write down the exact address you want visitors to reach, then compare that choice against WordPress settings, hosting redirects, CDN rules, and any redirect plugin. The goal is not to add more redirects. It is to remove conflicting instructions.
Clear caches only after you understand what changed
Browser caches, WordPress cache plugins, server caches, and CDNs can preserve an old redirect after a configuration change. Clearing the relevant cache is useful, but it should not be the first response to every loop.
If a redirect rule is still wrong, clearing the cache simply makes the bad rule run again. First identify the likely source, correct it, then clear the affected cache so you can test the new behavior.
Temporarily isolate redirect and security plugins
A redirect plugin, SSL plugin, security plugin, membership plugin, or caching plugin may add rules that affect login pages or front-end URLs. If the loop began after a plugin change, that timing is an important clue.
When possible, test plugin changes on a WordPress staging site instead of experimenting on the live website.
On a live site, disable or change only one suspected component at a time. If several plugins are changed together, you may fix the loop without learning which setting caused it.
Review redirect rules at the server level
Redirects can exist outside WordPress. Depending on the hosting setup, rules may live in the web server configuration, a control panel, a CDN, or an .htaccess file.
Look for duplicate rules that attempt to do the same job, especially rules involving HTTPS, www, trailing slashes, old domains, or renamed pages.
If you are not comfortable editing server-level rules, do not delete them at random. A bad change can turn one redirect problem into a broader outage.
Check recent changes in a useful order
When a redirect loop appears suddenly, work backward from the most recent change. A simple sequence is:
- Confirm the exact URL that loops.
- Test whether the problem affects the whole site or only part of it.
- Compare WordPress Address and Site Address values.
- Check HTTP versus HTTPS behavior.
- Check www versus non-www behavior.
- Review recent plugin, CDN, hosting, or redirect-rule changes.
- Clear the relevant caches after correcting the suspected cause.
- Retest in a private window and on another device.
Protect the site before changing deeper settings
Before editing server rules, database values, or several WordPress settings, make sure you have a usable backup. A backup is most valuable when you know it can actually be restored, so it is worth reviewing how to test a WordPress backup before a high-risk change.
Also record the original values before editing anything. That gives you a clear path back if the change does not solve the problem.
What can wait until after the loop is fixed
Do not start by redesigning pages, changing themes, installing multiple optimization plugins, or rebuilding the website. Those changes add variables without addressing the redirect path itself.
Fix the loop first. Then handle secondary issues such as mixed content, stale links, performance, or cleanup.
When professional troubleshooting makes sense
Professional help is useful when the site is completely inaccessible, the loop started after a migration, multiple redirect systems are involved, server configuration needs to be edited, or you cannot safely reach the WordPress dashboard.
The WordPress troubleshooting service is relevant when the cause needs to be narrowed across plugins, hosting, redirects, and WordPress settings instead of guessed at from one symptom.
A redirect loop is usually easier to solve by removing conflict
Most redirect loops become easier to diagnose when you trace the request in a fixed order: domain version, protocol, WordPress URL settings, plugins, cache, then server-level rules. The goal is to find the two or more instructions that disagree and make the site settle on one correct destination.
If your WordPress site is stuck in a redirect loop and you are not sure which layer is causing it, 651 Web Design can help you narrow down the source and identify the safest next step.