Simple 301 Redirects Not Working? Here’s a Fix

You picked a redirection plugin to help manage your links, but now it’s creating the exact problem you hoped to prevent. 

The ‘Simple 301 redirects not working’ message is a common issue that many WordPress users face. 

While the impact on your traffic and SEO is serious, the solution is usually straightforward. This guide provides a direct checklist to diagnose the issue and get your redirects working correctly.

TL;DR: Fix Simple 301 redirects not working by clearing caches, checking for plugin conflicts, and inspecting your .htaccess file for errors. If the problem persists or to prevent issues, always use a backup plugin to safeguard your site.

Quick fixes to try

Before you begin editing server files, run through these simple checks. In our experience, one of these steps solves the issue more than half the time.

1. Clear all caches. A browser or content delivery network (CDN) can hold onto an old, broken redirect and show you a cached error even after you have fixed it.
   • Browser cache: Clear your browser’s history, cookies, and cached files completely.
   • CDN cache: If you use a service like Cloudflare, log in to its dashboard and purge the cache.

2. Use an independent redirect checker. Your browser can be misleading. Use an external tool like httpstatus.io to see the real server response code. This shows what the server is actually doing, not what your browser thinks is happening.

3. Perform final sanity checks.
   • Check for typos. A single misplaced character in the source or destination URL will break the entire redirect.
   • Confirm your SSL certificate. An invalid SSL setup can stop redirects from working correctly on HTTPS sites.
   • Try a different browser. Use a different browser or an incognito window to confirm the issue is not specific to your primary browser’s cache.
   • Check WordPress URL settings. In your WordPress dashboard, go to Settings> General. Ensure the WordPress Address (URL) and Site Address (URL) match exactly.
   • Look for trailing slashes. Be consistent. A URL ending with / is different from one without it. Make sure both your source and destination URLs are correct.

In-depth troubleshooting for failing 301 redirects

If the quick fixes didn’t do the trick, the problem is a little deeper. We’ll walk through it step-by-step: 

⚠️ Note: Have a backup of your WordPress site in place before you proceed. This gives you a safety net to fall back on.

1. Make sure you are telling Google the right thing

A redirect is like a change of address form for a webpage, and there are two main types. It is important to use the correct one for search engines.

Your redirect should be set to 301 (Permanent). This signals to search engines that the page has moved forever and that all of its ranking power should be transferred to the new address. 

🚚 Note: Website migration is the most common scenario where hundreds of 301 redirects are necessary. A proper plan ensures you transfer all SEO value without creating broken links or redirect chains.

If you use a 302 (Temporary) redirect, it indicates the move is not permanent, which prevents that SEO value from being passed along.

2. Consolidate to one “official” address

A single webpage can often be reached through multiple URL variations:

• http://yoursite.com
• http://www.yoursite.com
• https://yoursite.com
• https://www.yoursite.com

While they appear the same, search engines see them as four separate addresses. All versions of your URL must automatically point to one official version (usually the https://www. one). 

If they do not, your website’s ranking power becomes split across multiple duplicate addresses. Forcing everything to point to one official URL ensures all that power is concentrated in one place.

💡 Note: Hardening WordPress security goes hand-in-hand with enforcing HTTPS. A secure URL is the foundation for protecting user data and preventing common attacks.

3. Check the website’s configuration file

Your website has a master rulebook that tells it how to handle requests. This is a text file called .htaccess on most servers, and it contains all your redirect instructions.

You should look for old or conflicting instructions in this file. The server reads this rulebook from the first line to the last. If an old, forgotten rule is at the top, the server will follow that instruction and may never reach the new rule you added at the bottom. This is a very common reason why a new redirect fails to work.

4. Identify and fix redirect loops

A redirect loop happens when your website gets confused. It sends a visitor from Page A to Page B, but Page B immediately sends them right back to Page A.

Your web browser gets trapped in this endless circle, going back and forth until it gives up and shows an error like “Too Many Redirects.” When this happens, nobody can access your page.

To fix this, you need to find and remove the conflicting instruction that is causing the loop. Follow these steps to find the source of the problem.

1. Scan your site: Before checking for configuration errors, rule out a security breach. Malicious code from an attack can cause unexpected redirects. Use a reputable security plugin to run a complete scan.

2. Clear browser cache: Clear your browser’s cache and cookies to ensure you are not seeing an old error.

3. Test your theme: Temporarily switch to a default WordPress theme (like “Twenty Twenty-Four”) to rule out a theme conflict.

4. Disable plugins: This is the most common cause. Deactivate plugins one by one until the error stops to find the culprit.

5. Check URL settings: In Settings > General, make sure your WordPress Address and Site Address URLs are identical.

6. Ask about a dedicated IP: Contact your host to see if a dedicated IP is needed to resolve rare SSL conflicts.

7. Restore the .htaccess file: Rename your .htaccess file to .htaccess_old. Then, go to Settings > Permalinks and click Save Changes to generate a fresh, clean one.

Alternative approaches for redirection

If you cannot find the source of the problem, you still have options.

• Switch to a different redirect plugin. Sometimes a plugin is simply not compatible with your server setup or another plugin. The easiest next step is to try a different, well-regarded redirect plugin.

⭐ Note: Testing plugins on a staging site first is the safest way to see if a new redirect plugin is compatible with your setup before deploying it on your live website.

• Implement manual redirects. Adding 301 redirects directly to your server’s .htaccess file or functions.php file is a reliable method. It bypasses any potential plugin conflicts entirely.
• Contact your web host. If you are not comfortable editing server files, contact your hosting provider. Give them the specific source URL, the intended destination URL, and the troubleshooting steps you have already taken.

Best practices to prevent Simple 301 redirects not working

Properly managing redirects is about being systematic. Follow these rules to prevent most future problems.

☄️ Note: Website backups should be your first step before implementing any changes from your documentation. This ensures you have a secure restore point if a new redirect rule causes an issue.

Parting thoughts

Remember, a 301 redirect is an instruction for your server. Because caching is the most common reason a redirect seems to fail, always trust an external checker tool over what your browser shows you.

Once you’ve confirmed the server-side redirect is working, two final steps are crucial for good site management. First, update all internal links to point directly to the new URL instead of relying on the redirect for navigation. Second, document your changes. This simple step will prevent a lot of headaches down the road.

FAQs