How to Fix Redirect Loops in WordPress

A “too many redirects” error means the browser is being sent from one URL to another in a loop. One rule may force HTTP to HTTPS while another sends HTTPS back to HTTP, or two versions of the domain may keep redirecting to each other.

The solution is to find the conflicting rule—not to keep adding new redirects.

Clear the Local Browser State

Delete cookies and cached data for the affected domain, then test in a private window. Try another network or device if possible.

If only one browser fails, stale cookies are the likely cause. If every device fails, continue with the website configuration.

Confirm the WordPress URLs

In Settings → General, check WordPress Address and Site Address. Both should use the intended domain and protocol. Decide whether the canonical address includes www, then use that form consistently.

If the dashboard is inaccessible, the values can be temporarily defined in wp-config.php or corrected in the database. Make a backup first and ask your host for help if you are unsure which URL is correct.

Check HTTPS Configuration

Confirm that the SSL certificate is valid and the site loads directly over HTTPS. Review redirects at every layer:

• WordPress or an SSL plugin
• .htaccess or Nginx configuration
• Hosting control panel
• CDN or reverse proxy

Only one layer needs to enforce the canonical HTTPS destination. The official WordPress HTTPS guide notes that reverse proxies must pass the correct protocol information; otherwise WordPress can enter a loop.

Clear Every Relevant Cache

Purge the WordPress page cache, hosting cache, object cache, and CDN cache. Then close the browser and test again.

Do not cache login, cart, checkout, or account pages. A cached redirect response can keep causing trouble after the original rule is fixed.

Disable Redirect and Security Plugins

On staging, temporarily deactivate redirect, SSL, caching, maintenance, and security plugins. If the loop stops, reactivate them individually and inspect their rules.

Without dashboard access, rename the suspected plugin folder using SFTP or the hosting file manager. Avoid disabling all protection on a busy live site unless you have a controlled maintenance window.

Inspect Server Redirect Rules

Back up .htaccess before editing it. On Apache, you can temporarily regenerate WordPress permalink rules by saving Settings → Permalinks after access returns. Custom HTTPS, domain, or language redirects outside the WordPress block deserve special attention.

On Nginx or managed hosting, ask support to trace the redirect chain. A redirect-checking tool can show each hop, but remove private query strings before sharing results.

Test Important Pages

Once the homepage works, test /wp-admin/, login, a post, forms, and WooCommerce checkout if applicable. Confirm both the HTTP and alternate-domain versions reach the canonical HTTPS URL in a single deliberate path.

Conclusion

Redirect loops usually come from two systems trying to control the same URL. Set one canonical domain, keep WordPress URLs consistent, pass HTTPS correctly through proxies, and remove duplicate rules. The cleanest redirect setup is usually the easiest to maintain.