Official statement
Other statements from this video 5 ▾
- 1:00 Do 302 redirects really transfer PageRank or not?
- 2:58 Why does a 302 redirect hinder canonical consolidation in Google?
- 3:40 Do 302 redirects really transmit less PageRank than 301?
- 4:27 Do 307/308 redirects truly protect your POST data better than 301/302?
- 7:16 How can JavaScript redirects sabotage your SEO?
Google follows all redirects, both 301 and 302, without distinction during crawling. However, for selecting the canonical URL displayed in search results, a permanent redirect (301) sends a clearer and more reliable signal. Specifically, a 302 may delay or complicate canonical consolidation, especially during migrations or redesigns.
What you need to understand
What's the difference between a 301 and a 302 from Googlebot's perspective?
Both HTTP status codes indicate a redirect, but their semantic intention differs. A 301 signals that the content has moved permanently, while a 302 indicates a temporary move. Gary Illyes confirms that Googlebot follows both types of redirects without technical blocking: the bot accesses the final content in both cases.
The issue lies elsewhere, regarding interpretation for canonicalization. When Google has to choose which URL to display in SERPs — the source URL or the target URL — it relies on multiple signals: type of redirect, site history, age of the redirect, and signal consistency (sitemaps, internal linking, backlinks). A 301 sends a clear signal: the old URL is obsolete, favor the new one. A 302 remains ambiguous: should the old URL stay indexed or switch to the new one?
Why doesn't Google simplify matters by treating all redirects the same way?
Because there are legitimate use cases for 302s: geolocated A/B tests, temporary maintenance pages, seasonal redirects (pop-up shops, events). If Google were to canonically redirect every 302's target, these scenarios would become unmanageable. The search engine must maintain logical contextual interpretation.
In practice, Google observes the duration of the redirect. A 302 kept for several months often ends up being treated as a 301 de facto. But this timing remains vague, undocumented, and varies based on the site's authority. Instead of letting Google interpret, it's better to clarify the intent from the start with the correct HTTP code.
What are the real risks of using a 302 instead of a 301?
The main danger is a dilution of canonical consolidation. For weeks, or even months, Google may hesitate between the old and new URL, displaying one or the other in search results. Ranking signals (backlinks, age, click history) fragment between the two URLs instead of concentrating on the new one.
In practice, this results in position fluctuations, temporary visibility drops, and a prolonged migration process. On sites with a high volume of pages, the cumulative effect can become significant. In contrast, a well-implemented 301 generally allows for a quicker and clearer transition, even if Google always maintains a reevaluation delay.
- Googlebot follows 301 and 302 without technical distinction during crawling
- The difference lies in the selection of the canonical URL in SERPs
- A 302 sends an ambiguous signal that can delay the consolidation of ranking signals
- 302s maintained for long periods often end up treated as 301, but with no guarantee of timing
- Favoring 301 for any permanent migration limits the risks of authority fragmentation
SEO Expert opinion
Is this statement consistent with real-world observations?
Yes, largely. Empirical tests confirm that Google eventually canonicalizes to the target of a 302 if it remains active for several months. But the timing varies greatly: I've seen 302s on authoritative sites switch in a few weeks, while others on smaller sites linger for six months. Illyes' statement remains cautious and realistic: Google does not guarantee any strict behavior, it simply recommends the best practice.
A rarely highlighted point: redirect chains (URL A → 302 → URL B → 301 → URL C) amplify the problem. Google follows up to 5 jumps, but each layer of 302 adds uncertainty. In these cases, canonicalization can become completely unpredictable. Cleaning chains and converting all permanent redirects to 301 becomes a priority. [To be verified]: Google has never published numeric data on the average consolidation timing of a 302 vs 301.
When is a 302 still justified despite this recommendation?
Geolocated or contextual redirects: a French user sees the FR version, an American sees the EN version, but the original URL remains relevant for other contexts. A/B tests with distinct URLs (even if modern solutions favor client-side JavaScript). Maintenance pages or temporary events where the original URL must take its place afterward.
The trap: many sites use 302 out of laziness or ignorance, not as a strategic choice. Poorly configured CMS, developers thinking a 302 'costs less' in terms of crawling (false), or 'temporary' migrations that end up lasting. Regularly auditing redirects and challenging each 302: is it really temporary, or just poorly labeled?
What margin of error does Google tolerate on this point?
Google partially compensates for redirection errors via other signals: if all backlinks point to the new URL, if the old one disappears from the XML sitemap, if internal linking no longer references it, the engine eventually understands the intent even with a 302. But this compensation comes at a cost: time. And on competitive sites where each week of floating impacts traffic, this lost time adds up.
Another element: server redirects vs JavaScript. A 302 redirect via client-side JavaScript (window.location) transmits no HTTP signal usable by Google. The bot must execute the JS, detect the redirect, and then interpret the intent — an even riskier path. In this regard, Illyes' statement concerns only server-side HTTP redirects, not front-end hacks.
Practical impact and recommendations
How to audit existing redirects on a site?
Start with a complete crawl using Screaming Frog or Oncrawl, activating redirect tracking. Export all URLs in 301 and 302, then sort by age (cross-reference with server logs or Google Search Console). Any 302 active for more than 3 months deserves examination: is it really temporary, or should it be switched to 301?
Also, check redirect chains: the 'Redirection Chains' report in Screaming Frog lists them. The goal: flatten as much as possible, ideally one direct redirect from A to C. Also use Search Console, Coverage section: the excluded URLs with the status 'Redirected' indicate what Google has detected, but don’t distinguish between 301 and 302. Cross-referencing with server logs gives the true picture.
What mistakes to avoid during a site migration?
The classic mistake: implementing all redirects as 302 'for safety', with the idea of switching to 301 later. Result: you forget to make the switch, and Google hesitates for months. Another trap: mixed redirects, where 80% of URLs are 301 but some strategic sections remain in 302 without documented reason. Google interprets this as a contradictory signal.
On large sites, be careful with htaccess or Nginx rewrite rules that stack conditions. A too-generic rule can create unintentional 302s where you wanted 301s. Systematically test a sample of URLs with curl or a HTTP testing tool to verify the actual status code before pushing to production.
What to do if Google is slow to canonicalize after a 301 migration?
Patience first: even with perfect 301s, Google can take 4 to 8 weeks to recrawl and reevaluate the entire site, especially if it is large or not crawled frequently. Speed up the process by resubmitting the XML sitemap with the new URLs and actively deindexing the old ones via Search Console (temporary removal request, then waiting for Google to remove them naturally).
Also force the recrawl of strategic pages via the URL Inspection tool in Search Console. Finally, ensure that internal linking exclusively points to the new URLs: any internal link to an old URL slows consolidation, as Google receives mixed signals. You can’t control external backlinks, but internally, it’s non-negotiable.
- Crawl the entire site and list all active 302 redirects for over 3 months
- Verify that each 302 has a valid business justification (geolocation, A/B testing, maintenance); if not, switch to 301
- Eliminate all redirect chains: one direct redirect per URL
- Test a sample of URLs post-migration with curl to validate the actual HTTP code
- Update the XML sitemap with only the final URLs, not the redirected URLs
- Clean up internal linking to point exclusively to the final canonical URLs
❓ Frequently Asked Questions
Une redirection 302 transmet-elle le PageRank comme une 301 ?
Combien de temps Google met-il pour canonicaliser une 302 vers sa cible ?
Faut-il convertir toutes les 302 en 301 même si elles fonctionnent actuellement ?
Une chaîne de redirections 302 puis 301 pose-t-elle problème ?
Les redirections JavaScript sont-elles équivalentes aux 302 HTTP ?
🎥 From the same video 5
Other SEO insights extracted from this same Google Search Central video · duration 8 min · published on 04/11/2026
🎥 Watch the full video on YouTube →
💬 Comments (0)
Be the first to comment.