How Long Do 301 Redirects Last?

The short answer is that a 301 redirect lasts as long as you keep it in place on your server. There is no built-in expiration. But the more useful question is: how long does the cached version of a 301 redirect last in browsers and search engines after you remove it? That answer depends on where the redirect is cached, and it is the source of most confusion around 301 duration.

For background on what 301 redirects are and when to use them, see the HTTP Redirect Guide and 301 Moved Permanently Explained.

How Browsers Cache 301 Redirects

When a browser encounters a 301 response, it caches the redirect locally. The next time you type or click the original URL, the browser skips the server entirely and goes straight to the destination URL. This is by design. A 301 means "permanent," so the browser takes you at your word and stops checking.

Chrome

Chrome caches 301 redirects in its internal redirect cache. This cache persists across browser restarts and does not have a fixed expiration time. In practice, Chrome can hold onto a cached 301 for weeks or months. The exact duration depends on available cache space, how recently the redirect was encountered, and whether the cache entry gets evicted to make room for newer data.

Chrome does respect Cache-Control headers on redirect responses. If your 301 response includes Cache-Control: max-age=3600, Chrome will re-check the redirect after one hour. Without explicit cache headers, Chrome uses its own heuristics, which tend toward long-lived caching for 301s.

Firefox

Firefox also caches 301 redirects, though historically it has been somewhat less aggressive about it than Chrome. Firefox's redirect cache follows standard HTTP caching rules. If the response includes cache headers, Firefox respects them. If not, it applies heuristic caching based on the Last-Modified or Date headers in the response.

Safari

Safari caches 301 redirects as well. Safari on macOS and iOS shares some cache behavior, but mobile Safari tends to have a smaller cache that gets evicted more frequently due to storage constraints.

The Practical Impact

If you set up a 301 redirect and a user's browser caches it, that user will be redirected even after you remove the redirect from your server. They will not see your change until their browser cache expires or is cleared manually. This is the most common source of "I removed the redirect but people are still being redirected" complaints.

How Search Engines Handle 301 Duration

Search engines treat 301 redirects as permanent signals to update their index. Google, Bing, and other search engines follow the redirect, visit the destination URL, and eventually replace the old URL with the new one in their index.

Google's Recommendation

Google Search Central explicitly recommends keeping 301 redirects in place indefinitely. [1] Their guidance is clear: if you set up a 301, leave it there. Google considers a 301 a strong signal that the old URL should be replaced by the new one, and they will transfer ranking signals (link equity, PageRank) to the destination URL over time.

Google has stated that they will continue to follow a 301 redirect every time they encounter it. Even after they have updated their index, Googlebot still crawls the old URL periodically and follows the redirect to confirm it is still in place. If the redirect disappears, Google may eventually re-index the old URL if it returns content.

How Long Until Google Updates Its Index

After you set up a 301, Google does not instantly update its index. The timeline depends on how frequently Googlebot crawls the old URL. For popular pages, the index update can happen within days. For less-trafficked pages, it might take weeks or even months.

You can speed this up by submitting the new URL in Google Search Console and requesting a re-crawl of the old URL. But even with these steps, the index update is not instantaneous.

Bing and Other Search Engines

Bing follows similar behavior to Google but tends to be slower in processing redirects. Other search engines vary. The general principle is the same: a 301 signals a permanent move, and the search engine will eventually update its index.

What Happens When You Remove a 301

Removing a 301 redirect creates different outcomes depending on what you put in its place.

The Old URL Returns Content (200)

If you remove the redirect and the old URL now serves actual content with a 200 status code, search engines will eventually notice. On their next crawl, they will find content instead of a redirect. Over time, they may re-index the old URL. However, the new URL has already been indexed and has accumulated ranking signals. You now have two URLs competing for the same rankings, which is a duplicate content problem.

Browsers that cached the 301 will continue redirecting until their cache expires or is cleared. New visitors will see the content at the old URL. Previous visitors will still be sent to the new URL.

The Old URL Returns 404

If you remove the redirect and the old URL returns a 404 Not Found, search engines will eventually drop the old URL from their index. The new URL retains the ranking signals that were transferred. This is the cleanest outcome from an SEO perspective, but it means anyone with a bookmark or external link to the old URL gets a 404 error.

The Old URL Returns a Different Redirect

If you change the 301 to point to a different destination, you create a new redirect that conflicts with the cached version. Browsers that cached the original 301 still go to the old destination. Search engines will follow the new redirect on their next crawl and eventually update their index, but this takes time and creates a confusing transition period.

How to Clear a Cached 301

If you removed or changed a 301 redirect and need users to stop following the cached version, here are your options.

For Your Own Browser

Chrome: Clear the browser cache or do a hard refresh. Go to chrome://settings/clearBrowsingData, select "Cached images and files," and clear. Alternatively, open Developer Tools (F12), right-click the refresh button, and select "Empty Cache and Hard Reload."

You can also clear Chrome's redirect cache specifically by visiting chrome://net-internals/#dns and clicking "Clear host cache," though this primarily affects DNS rather than HTTP redirect caching.

Firefox: Clear the cache through Settings, or press Ctrl+Shift+Delete (Cmd+Shift+Delete on macOS) to open the clear data dialog.

Safari: Go to Safari > Settings > Privacy > Manage Website Data and remove data for the specific domain.

For Your Users

You cannot force other people's browsers to clear their redirect cache. This is the fundamental problem with removing a 301. The "permanent" part of "301 Moved Permanently" means browsers are entitled to cache it for as long as they want.

Your options are limited:

Wait. Browser caches eventually expire or get evicted. Most users will see the change within a few weeks as their cache turns over naturally.

Set cache headers on the redirect response before removing it. If you are planning to remove a 301 in the future, first change the response to include Cache-Control: max-age=0 while keeping the 301 in place. Browsers that re-visit the redirect will update their cache to not cache it. After enough time has passed, remove the redirect. This is a proactive approach that requires planning.

Switch to a 302 first. Before removing the redirect entirely, change it from a 301 to a 302. Browsers treat 302s as temporary and do not cache them as aggressively. Leave the 302 in place for a few weeks, then remove it. This gives browsers time to update their cached behavior.

When It Is Safe to Remove 301 Redirects

Despite Google's recommendation to keep them indefinitely, there are practical situations where removing a 301 makes sense.

The Old Domain Has Expired

If the old domain has expired and you are not renewing it, the redirect is gone regardless. Make sure Google has fully indexed the new URLs before letting the domain expire. Check Google Search Console for the old domain to confirm that all important pages have been processed.

Traffic Has Fully Migrated

If your server logs show zero traffic to the old URL (not just organic traffic, but all traffic including direct, referral, and cached), and this has been the case for several months, the redirect is no longer serving anyone. Removing it is unlikely to cause problems.

The Redirect Infrastructure Has a Cost

If maintaining the old server, domain, or configuration specifically for redirects has a real cost, and traffic to the old URLs is negligible, the business case for keeping the redirect weakens over time. Weigh the cost of the infrastructure against the risk of losing a small amount of traffic or link equity.

You Are Consolidating Hundreds of Redirects

Large sites accumulate redirect rules over years. At some point, the redirect configuration becomes unwieldy. Auditing and removing redirects that no longer receive traffic is part of redirect hygiene. See Redirect Management Strategy for a systematic approach.

How Long Should You Keep a 301? A Practical Timeline

While "forever" is the safest answer, here is a practical framework.

0 to 6 months: The redirect is essential. Search engines are still processing the move. Traffic is still arriving at the old URL from cached search results, bookmarks, and external links. Do not remove the redirect.

6 months to 1 year: Search engines have likely updated their index. Check Google Search Console and your server logs. If the old URL still receives meaningful traffic, keep the redirect. If traffic is minimal, you could consider removing it, but there is little reason to.

1 to 3 years: Most organic and referral traffic has migrated. Direct traffic from bookmarks is the main remaining source. If the redirect has no infrastructure cost, keep it. If it does, evaluate based on remaining traffic.

3+ years: The redirect has served its purpose. Remaining traffic is likely near zero. If you are paying to maintain infrastructure specifically for this redirect, it is reasonable to remove it. Monitor for any traffic impact after removal.

How 301 Caching Differs from 302

This is where the difference between 301 and 302 has practical consequences. A 302 redirect is "temporary," and browsers treat it accordingly. Most browsers do not aggressively cache 302 redirects. When you remove a 302, browsers check the original URL again on their next visit and see whatever response is there now.

A 301 is "permanent," and browsers cache it accordingly. Removing a 301 does not immediately change behavior for users who have already visited the URL because their browsers still have the redirect cached.

If you know a redirect might need to be changed or removed in the future, use a 302 instead of a 301. You lose some SEO signal transfer, but you gain the ability to change direction without fighting browser caches. For temporary situations where you need both SEO signal transfer and flexibility, this is one of the genuine tradeoffs in redirect management.

References

1. Google Search Central, "Redirects and Google Search," https://developers.google.com/search/docs/crawling-indexing/301-redirects