Should you really keep 301 redirects for at least a year?

Why does Google set this minimum one-year deadline?

The recommendation is based on the average crawl frequency observed by Google. One year allows the bot to pass multiple times over each redirected URL, even those buried deep in the site structure.

The key figure: at least two passes per URL. This ensures that Google has properly recorded the new destination and transferred signals (PageRank, anchors, trust). Below this threshold, there is a risk of loss—especially if the first visit encounters a network error or a timeout.

Are all URLs treated the same way?

No. Google explicitly differentiates between less significant or rarely crawled URLs. An orphan page, without backlinks, with no traffic history can wait months before being visited for the first time.

On a site with thousands of pages, the crawl distribution is uneven. Strategic pages—those linked from the homepage, enriched with backlinks—are visited weekly. The others? Quarterly, or even never, if they generate no signals.

What happens if you remove a redirect too early?

The old URL returns a 404 . Google may then deindex the old address without transferring all signals to the new one. If backlinks still point to the old URL, their juice is lost.

Worse: if the new URL has only been crawled once, Google may consider the redirect as temporary or uncertain. The transfer of PageRank remains incomplete, and the new page struggles to reach its ranking potential.

• A minimum of one year ensures that Google has visited each redirected URL at least twice
• Orphan or low-crawl pages often require more than twelve months
• Removing a redirect prematurely exposes you to 404 errors and PageRank loss
• The complete transfer of signals (anchors, trust, history) requires multiple bot passes
• The duration depends on the crawl frequency : a slow or low-authority site must extend redirects

Is this recommendation consistent with field observations?

On high-authority sites, with daily crawling, one year seems prudent but sufficient . Server logs confirm that Google visits strategic URLs at least twice (often more) within this timeframe.

In contrast, on medium or low-authority sites, with a tight crawl budget, URLs are often still being visited for the first time after twelve months. Maintaining redirects beyond a year then becomes necessary—especially if the site has thousands of poorly linked pages.

What uncertainties remain in this statement?

Google does not specify how to define a less significant URL. Is it a matter of backlinks? Traffic history? Age? This vagueness requires analyzing logs to identify pages that are truly being crawled.

Another unclear point: the exact timing of PageRank transfer . Do two passes suffice to transfer 100% of the juice, or is more needed? [To be verified] Internal tests show variations depending on the sector and competition for keywords.

In what cases can we deviate from this rule?

If the old URL has no backlinks , no traffic history, and does not appear in any sitemap file, the redirect becomes optional after a few months. The risk of loss is nil.

Conversely, a highly strategic page—with hundreds of quality backlinks—merits a permanent redirect. Some SEOs maintain these redirects indefinitely , as the technical cost is low compared to the risk of breaking a link in the link graph.

What should you do concretely during a migration?

Plan 301 redirects for a minimum duration of twelve months , adding an extra six months if your crawl budget is low. Document the date each batch of redirects is implemented to monitor the deadline.

Segment your redirected URLs by level of importance : strategic pages with backlinks on one side, orphan pages on the other. The former may justify a permanent redirect, while the latter will be reassessed after a year.

How to ensure all URLs have been crawled twice?

Analyze your server logs to track Googlebot's visits to each old URL. If a page has only been visited once in twelve months, extend the redirect for at least six more months.

The Search Console also provides hints via the coverage report, but logs remain the most reliable source. Cross-reference this data with your backlink mapping: a URL still cited by external sites should maintain its redirect as long as those links exist.

What mistakes should you absolutely avoid?

Never remove redirects in bulk without prior audit. Some URLs may still receive residual traffic —via bookmarks, email links, external PDFs—that is invisible in Analytics but detectable in logs.

Avoid redirect chains : if you redirect A to B, then B to C, Google may lose some of the signal along the way. Always consolidate towards the final destination from the outset.

• Maintain all 301 redirects for a minimum of twelve months after creation
• Extend by an additional six months for low-crawl sites or infrequently visited pages
• Audit server logs to ensure each URL has been crawled at least twice
• Segment redirects by level of importance (backlinks, traffic history, position in the structure)
• Maintain indefinitely redirects for strategic pages with many backlinks
• Avoid redirect chains : always point to the final destination
Managing 301 redirects requires rigorous monitoring and detailed analysis of server logs—time-consuming tasks that demand specialized technical skills. If your migration involves hundreds or thousands of URLs, assistance from a specialized SEO agency can ensure the PageRank transfer and prevent losses in organic traffic. These experts have the tools and methodologies to audit each redirect, identify at-risk URLs, and optimize the duration of maintenance according to your crawl profile.