🔍 Why Does the Redirect Still Happen?
When you deactivate a redirect rule in the Search Atlas plugin, the rule is removed from the plugin's configuration immediately. However, a 301 redirect is cacheable by design — browsers, CDNs, hosting servers, and edge networks are all permitted to store and serve a 301 response without checking the origin server again. This means the redirect can continue firing even after the rule no longer exists, because a cached copy is being served from one or more layers in the delivery chain.
Common sources of a cached redirect include:
- Browser cache — your own browser or a visitor's browser has stored the 301 locally
- CDN or proxy cache — services like Cloudflare, Fastly, or a hosting-level proxy cache the response at the edge
- Server-level page cache — caching plugins (e.g. WP Rocket, W3 Total Cache, LiteSpeed Cache) or server software (Nginx, Apache) may have cached the redirect response
- Search Atlas backend cache — in some configurations, redirect responses routed through Search Atlas infrastructure may be held in a short-lived cache
🛠️ Step-by-Step: Clear the Redirect From Every Layer
- Confirm the rule is deactivated in Search Atlas. Go to the Search Atlas plugin → Settings tab and turn on the Disable Redirection toggle to disable the feature. Save your changes.
- Clear your browser cache. In Chrome or Edge, open Settings → Privacy and Security → Clear Browsing Data and select Cached images and files. In Firefox, go to Settings → Privacy and Security → Clear Data. Alternatively, open the URL in a private/incognito window to test without any local cache.
- Purge your caching plugin or server cache. If you use WP Rocket, LiteSpeed Cache, W3 Total Cache, or a similar plugin, navigate to its dashboard and click Purge All or Clear All Cache. If your host provides a server-level cache (e.g. SiteGround, WP Engine, Kinsta), log in to your hosting dashboard and clear the cache there as well.
- Purge your CDN cache. If your site runs behind Cloudflare or another CDN, log in to your CDN dashboard and purge the specific URL or purge everything. Refer to your CDN provider's documentation for the exact steps to clear a cached URL.
- Test with a redirect checker. Use a tool such as httpstatus.io or redirectdetective.com to trace the redirect chain for the affected URL. If the 301 no longer appears, the cache has been cleared successfully. If it still appears, note which server or IP address is returning the redirect — this helps identify which cache layer is still holding the response.
- Wait for TTL expiry if needed. If you cannot manually purge a particular cache layer, the redirect will eventually stop once the cached entry's TTL (time to live) expires. TTL values vary by CDN and server configuration but are typically between a few minutes and 24 hours.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.