Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

WordPress Redirection Plugin Not Working: Causes and How to Fix It

WordPress Redirection Plugin Not Working: Causes and How to Fix It

Short answer

The Redirection plugin usually seems broken because your browser or a page cache is serving an old response, the source URL does not match exactly, a server or CDN rule runs first, or the plugin cannot reach the WordPress REST API. Test in a private window and clear every cache first.

Key takeaways

  • Browsers cache 301 redirects, so always test in a private window.
  • Source URLs must match exactly, including slashes, case and query strings.
  • Server, host and Cloudflare redirects run before WordPress and can override the plugin.
  • Regex rules only work when the regex option is ticked on that rule.
  • The Redirection admin screen needs a working REST API.

Why is the Redirection plugin not working?

Redirection usually seems broken because a browser or page cache is serving an old response, the source URL does not match exactly, a server or CDN rule runs first, or the plugin cannot reach the WordPress REST API.

The Redirection plugin is reliable, so most failures come from the setup around it. The fix depends on what you see:

SymptomLikely cause
Old URL still loads the old pageCache, URL mismatch or disabled redirect
Redirect goes to the wrong placeServer, CDN or another plugin redirecting first
Too many redirects errorA loop between two rules
Admin page will not loadREST API blocked
Regex rule never matchesRegex option off or pattern wrong

Start with the cache checks. They solve more cases than anything else.

If you need a refresher on setup, see our guide on how to use the Redirection plugin.

Is a cache hiding your new redirect?

Yes, browsers cache 301 redirects aggressively and page caches store old pages, so test in a private window and clear your caching plugin, host cache and CDN.

Browsers remember permanent redirects. If you earlier visited the URL when it pointed somewhere else, your browser may keep using the old answer without asking the server again. MDN's guide to HTTP redirections explains how permanent redirects are cached.

Test like this:

  1. Open a private or incognito window
  2. Visit the old URL
  3. If it works there, clear your normal browser cache

Page caches are the other half. A caching plugin or host cache may have stored a copy of the old page before you added the redirect.

Clear every layer. Our guide on how to clear cache in WordPress shows where each one lives.

While testing a new rule, consider using a temporary 302 first. Switch to 301 once you are sure it is right.

Also remember that other people may have the old redirect cached too. That is one more reason to get a permanent redirect right before you publish it.

Does the source URL match exactly?

Redirection matches the source URL closely, so a missing slash, different letter case, query string or full domain can stop a rule from firing.

Check these details in the rule:

  • Relative path. Use /old-page/ rather than the full https address.
  • Trailing slash. /old-page and /old-page/ can be treated differently, depending on your settings.
  • Case. Old URLs with capital letters may need the ignore case option.
  • Query strings. A URL with ?ref=abc may not match a rule for the plain path unless query parameters are ignored or passed through.

Open the rule and look at its URL options. Redirection lets you choose how to treat case, trailing slashes and query parameters for each rule or as a site-wide default.

The plugin's documentation at redirection.me explains each matching option.

Is the redirect or its group disabled?

A redirect, or the group it belongs to, can be switched off, so check that both are enabled in Tools > Redirection.

Disabled rules appear faded or marked in the list. Hover over the rule and enable it.

Groups can be disabled as a whole. If you placed a rule in a group that is turned off, none of its redirects work. Open the Groups tab and confirm the group is enabled.

Also check the rule's hits count. If it stays at zero while you visit the old URL, the request is not reaching the rule, which points back to caching or a server rule.

Is another redirect running before Redirection?

Server, host and CDN redirects run before WordPress loads, so a rule in .htaccess, Nginx, your host panel or Cloudflare can override or conflict with the plugin.

Redirection works inside WordPress. Anything that redirects earlier wins.

Places to check:

  • The .htaccess file on Apache servers
  • Nginx configuration on your server or host
  • Redirect tools in your hosting panel
  • Cloudflare redirect rules or older page rules
  • SEO plugins with their own redirect managers
  • Your theme or other plugins

Remove duplicate rules so each redirect lives in one place. Our guide on how to edit the .htaccess file shows how to find old rules safely.

Why do you get a too many redirects error?

A redirect loop happens when two rules send visitors back and forth, such as A to B and B to A, or an HTTPS rule fighting a CDN setting.

Look for:

  • A rule that redirects a page to itself, often through a regex pattern
  • Two rules that point at each other
  • A redirect clashing with an HTTP to HTTPS rule
  • A Cloudflare SSL mode that does not match your server

Disable recent rules one at a time to find the loop. Our guide on fixing too many redirects covers the wider causes, including SSL settings.

Why are regex redirects not matching?

Regex rules only work when the regex option is ticked on that rule, and the pattern must match the path exactly as Redirection sees it.

Open the rule and confirm Regex is enabled. Without it, the pattern is treated as plain text.

Then check the pattern:

  • Start with ^ and end with $ to avoid matching more than you meant
  • Escape dots and other special characters
  • Use capture groups like (.*) and reference them as $1 in the target
  • Remember trailing slashes

Test patterns on a few real URLs before saving. A loose pattern can catch pages you never meant to redirect, including your admin or login pages.

Why will the Redirection admin screen not load?

The Redirection admin uses the WordPress REST API, so if a security plugin, firewall or server rule blocks it, the screen shows an error or keeps loading.

Redirection shows a message when it cannot reach the REST API. The WordPress REST API handbook explains what the API is.

Try these fixes:

  1. Check security plugins for REST API restrictions
  2. Ask your host whether a firewall blocks REST requests
  3. In Redirection's options, try a different REST API setting, such as raw or relative
  4. Make sure permalinks are not set to plain

The plugin's support page can also run checks and show the exact error, which helps when you ask for help.

Do the plugin's database tables need repairing?

Sometimes, yes, because Redirection stores rules in its own tables, and a failed install or migration can leave them missing or out of date.

If Redirection shows a database upgrade or repair notice, back up your database and follow it. Plugin updates occasionally change table structures.

After moving a site, confirm the tables came across with the rest of the database. Some migration tools skip tables with unusual prefixes.

How do you confirm a redirect works?

Test in a private window, check the response with your browser's developer tools, and watch the rule's hit counter and the Redirection log.

In developer tools, open the Network tab, load the old URL and click the first request. You should see a 301 or 302 status and a Location header pointing to the new address.

Redirection's log records every redirect it performs. If the log shows a hit but the browser lands elsewhere, another rule runs after it. If the log shows nothing, the request never reached WordPress.

For the SEO side of redirects, our explainer on what a 301 redirect is covers how search engines treat each type.

Frequently asked questions

Why does my 301 redirect still go to the old page?

Your browser probably cached the earlier response, or a page cache stored the old page. Test in a private window, then clear your browser, caching plugin, host cache and CDN.

Does Redirection work on Nginx servers?

Yes. The plugin works inside WordPress, so it runs on Apache and Nginx. It can also export rules in server formats if you want the server to handle redirects instead.

Why is the Redirection hit counter not going up?

The request is not reaching the rule. A cache may be serving the page, a server or CDN rule may redirect first, or the source URL does not match. Check each in turn.

Can Redirection conflict with Yoast or Rank Math redirects?

Yes, if both have rules for the same URL. The one that runs first wins, which can cause wrong targets or loops. Keep each redirect in a single tool.

How do I fix the Redirection REST API error?

Check security plugins and host firewalls for REST API blocks, make sure permalinks are not plain, and try a different REST API option in the plugin's settings. The support page shows the exact error.

Sources

  1. Redirection plugin WordPress.org Plugins
  2. Redirection documentation redirection.me
  3. Redirections in HTTP MDN Web Docs
  4. REST API handbook WordPress Developer Resources
  5. Redirects Cloudflare Docs

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.