“yoursite.com redirected you too many times.”

“Redirected you too many times” means your site sent the browser from one address to another and back again, until the browser stopped trying.

• WordPress Address (URL) and Site Address (URL) in Settings › General don't match: one has https and one http, or only one has www.
• Your host, or a service in front of your site, passes https visits to WP as plain http. WP sends them back to https, and round it goes.
• A redirect rule in a plugin sends a page to an address that sends it back, like your homepage to /home/ when /home/ is your homepage.
• 2 plugins, or a plugin and your host, both force https or www, each in its own way.
• Rules in .htaccess (a settings file your web server reads before WP starts) that send visitors to https or www.
• Old cookies in your browser from before an address change. If the site loads in a private window, that's the cause.

What you see

Chrome shows “This page isn't working” and, under it, “yoursite.com redirected you too many times.” Firefox says “The page isn't redirecting properly”. Both mean the same thing.

A redirect is your site saying “not here, go there”. That's normal. A loop is when “there” sends the browser straight back, so it goes round until it gives up after about 20 tries.

Sometimes only your homepage loops and your dashboard still opens (the screens you log in to at yoursite.com/wp-admin). Sometimes every page loops, the login page too. Either way, your posts and pages are still in your database.

How to find the cause

Is it only you?

Open your site in a private window, or on your phone with Wi-Fi off. If it loads there, old cookies in your browser are the cause. Delete your browser's cookies for your site and reload.

Which pages loop?

Try your homepage, a post, and yoursite.com/wp-login.php. If only one address loops, look for a redirect rule on that address. If every address loops, look at your site's addresses and https.

An online redirect checker lists each step of the loop. Paste your address in and read the list. If it swaps between http and https, or between www and no www, the cause is your addresses or https.

What changed last?

Loops start after a change. Think back to a new SSL certificate (what puts the padlock and https in front of your address), a new redirect rule, a new plugin, a new domain, or a change at your host.

How to fix each cause by hand

Your site addresses

If you can log in, open Settings › General. WordPress Address (URL) and Site Address (URL) should match: both https, and both with www or both without. Fix them and press Save Changes.

If you can't log in, open wp-config.php in your site's main folder with your host's file manager. Above the line with “That's all, stop editing!”, add these 2 lines with your own address:

define( 'WP_HOME', 'https://yoursite.com' ); define( 'WP_SITEURL', 'https://yoursite.com' );

These lines win over the settings screen, and those 2 boxes turn grey. Once your site loads, you can leave them in.

https at your host

Some hosts, and services that sit in front of your site, take an https visit and pass it to WP as plain http. WP sees http and sends the visitor back to https. Round it goes.

Ask your host, or that service, to connect to your site over https too. Tell them you see a redirect loop and when it started. They see their own settings; you don't.

A redirect rule in a plugin

Open the plugin's list of redirects and look for a rule on the address that loops. A rule that sends your homepage to /home/ loops when /home/ is your homepage, because WP sends it straight back.

Delete the rule, or point it somewhere else. Can't reach your dashboard? Add -off to the plugin's folder in wp-content/plugins, and WP switches it off.

Its rules stay saved while it's off. When you switch it back on, go straight to its redirects and fix the rule. Then test in a private window.

An https, cache or security plugin

Plugins that force https or www can clash with your host or with each other. Add -off to their folders one at a time, and reload in a private window after each. When the loop stops, you've found it.

A cache plugin keeps ready-made copies of your pages, so it can keep handing out an old redirect after you fix the cause. Clear its cache, and your host's cache if it has one.

The .htaccess file

On many hosts, a file called .htaccess sits in your site's main folder. Your web server reads its rules before WP starts, and some rules send visitors to https or www.

Rename it to .htaccess-off and reload. If the loop stops, a rule in it was the cause. Log in, open Settings › Permalinks and press Save Changes. WP writes a fresh file with its own rules.

Keep the old file. Any rules your host added are in it, so ask them which ones to copy back.

How to stop it coming back

Change your site's address in one place, and change both boxes in Settings › General together.

When your host adds https, ask whether they already send visitors to it. If they do, don't add a plugin that does the same.

After you save a new redirect rule, open the old address and the new one in a private window. A loop shows up right away.

What we saw on our test site

On Oct 14, 2026 we broke our test site (a WP site we run to try every task before we write about it) with a redirect plugin. A rule sent the homepage to /home/, and WP sent /home/ straight back.

CMSHands was already on the site. It found that rule was the cause, and a person at CMSHands approved switching the redirect plugin off. Then it checked the homepage, login page, dashboard and a post, and all loaded.

The rule stayed saved in the plugin. The chat said so, and said to delete it before switching the plugin back on.

Our first try used a rule on the exact homepage address, and the check didn't see that loop. The limits on this page say why.