What does Google say about SEO? /
Quick SEO Quiz

Test your SEO knowledge in 5 questions

Less than a minute. Find out how much you really know about Google search.

🕒 ~1 min 🎯 5 questions

Official statement

307 and 308 redirects function similarly to 301 and 302 respectively, but they preserve POST request data during the redirect. This is crucial for cases where data needs to remain intact, such as in online transactions.
4:27
🎥 Source video

Extracted from a Google Search Central video

⏱ 8:52 💬 EN 📅 04/11/2026 ✂ 6 statements
Watch on YouTube (4:27) →
✂ Other statements from this video 5 ▾
  1. 1:00 Do 302 redirects really transfer PageRank or not?
  2. 2:24 Should you really favor 301 redirects over 302 for SEO?
  3. 2:58 Why does a 302 redirect hinder canonical consolidation in Google?
  4. 3:40 Do 302 redirects really transmit less PageRank than 301?
  5. 7:16 How can JavaScript redirects sabotage your SEO?
📅
Official statement from (12 days ago)
TL;DR

Google confirms that 307 and 308 redirects preserve POST data during the redirect, unlike 301 and 302 which often convert POST requests into GET. This difference is crucial for e-commerce transactions and sensitive forms. Most sites still predominantly use 301/302 without realizing they are potentially losing critical user data.

What you need to understand

What is the real technical difference between these status codes?

301 (permanent) and 302 (temporary) redirects are ubiquitous in SEO. What many don’t know: these codes typically convert a POST request into a GET during the redirect. The browser follows the redirect but changes the HTTP method.

307 and 308 ensure strict adherence to the original HTTP method. A POST remains a POST. The body data of the initial request is passed to the destination URL. This is a fundamental difference for data integrity preservation.

Why does preserving POST data pose a real SEO issue?

Imagine a payment form that POSTs to a redirected URL. With a 301 or 302, form data is lost. The cart empties, the transaction fails. The user sees a blank page or an error.

This scenario happens more often than one might think: site redesigns, HTTPS migrations, domain consolidations. Developers instinctively implement 301 redirects without analyzing actual POST traffic. The result: silent conversion loss, hard to trace in Analytics.

In which concrete contexts should we prioritize 307 or 308?

Any site accepting user data via POST is affected. E-commerce, of course, but also SaaS with webhooks, public APIs, complex lead generation forms. If your conversion funnel includes successive POSTs, each redirect is a potential friction point.

The 308 is the permanent version (equivalent to 301), while the 307 is temporary (equivalent to 302). The choice depends on the expected duration of the redirect, just as with their classic counterparts.

  • 307/308 maintain the HTTP method (POST remains POST, unlike 301/302)
  • Critical for e-commerce transactions, webhooks, APIs, and sensitive forms
  • 308 = permanent redirect preserving POST, 307 = temporary preserving POST
  • Most sites still use 301/302 by default, losing data unknowingly
  • Google primarily crawls in GET, so the SEO crawl impact is limited, but user experience can be catastrophic

SEO Expert opinion

Does this statement truly reflect observed practices in the field?

Let’s be honest: very few SEO sites actively use 307 or 308 messages. Technical audits reveal an overwhelming dominance of 301/302, even on sensitive user journeys. The reason? Technical ignorance and lack of alerts in standard auditing tools.

SEO crawlers (Screaming Frog, Oncrawl) do not flag this difference as an issue. Google Search Console does not distinguish these codes in its reports. The subject remains invisible in most SEO workflows, even though it directly impacts conversion.

Is Googlebot really concerned about this distinction?

One crucial point rarely addressed: Googlebot mainly crawls in GET method. It does not submit forms or trigger POST. Therefore, Gary Illyes's statement mainly targets the actual user experience, not crawling or indexing.

The SEO impact is indirect: poor management of POST redirects decreases the conversion rate, increases the bounce rate on landing pages, and creates negative user signals. Google can interpret these signals as a quality of experience issue, but the link is never direct.

What are the limitations and gray areas of this recommendation?

The statement remains vague on one point: do all browsers strictly adhere to the POST preservation of 307/308? Empirical tests show that modern browsers do, but some older HTTP clients may still convert POST to GET for safety. [To be verified] in your analytics if you support legacy browsers.

Another limitation: Google’s documentation does not clarify how PageRank flow behaves differently between 301 and 308. Theoretically identical, but no official confirmation. Caution dictates treating 308 as a 301 for pure SEO.

Warning: blindly migrating from 301 to 308 without analyzing actual POST traffic can introduce application bugs. Test first on a subset of critical redirects.

Practical impact and recommendations

How can I identify problematic redirects on my site?

Start by analyzing your server logs to spot POST requests followed by redirects. Grep for 'POST' combined with 301/302 codes reveals hot spots. If you see POSTs to redirected URLs, you are likely losing data.

APM monitoring tools (New Relic, Datadog) can track error rates by endpoint. A spike in 4xx errors or abandoned sessions on a redirected page is a warning sign. Correlate with your website redesign or domain migration events.

When should we really switch to 307 or 308?

Prioritize critical conversion funnels: e-commerce checkout, complex lead generation forms, third-party payment webhooks. If your site uses POST for sensitive business actions and those URLs have been redirected, it's urgent.

For purely informational sites without POST forms, the risk is negligible. Standard 301/302 will suffice. Avoid over-optimizing: each technical modification introduces a regression risk. Focus on actual measurable user flows in your conversions.

What migration strategy should I adopt to limit risks?

Never migrate all your redirects at once. First, test in a staging environment with tools like cURL or Postman to simulate POST requests and ensure that the body is transmitted correctly. Validate that your application stack properly handles 307/308.

Deploy gradually: start with a non-critical URL, monitor for 48 hours, then extend to conversion endpoints. Keep a quick rollback possible. This technical complexity might justify relying on a specialized SEO agency that understands both server issues and conversion impacts, especially if your stack involves CDN, load balancers, or micro-services.

  • Audit logs to identify POSTs followed by 301/302
  • Set up monitoring for errors and drop-offs on redirected pages
  • Test in staging the preservation of POST body with 307/308
  • Gradually deploy, starting with critical e-commerce endpoints
  • Check compatibility with your CDN and load balancer (Cloudflare, Akamai, etc.)
  • Document sensitive redirects in an accessible technical register
307 and 308 are essential status codes for preserving POST data integrity, yet their adoption remains minimal. Prioritize critical conversion tunnels, rigorously test before deployment, and only migrate if you have identified a measurable loss of data. For a purely GET site, the SEO impact is negligible.

❓ Frequently Asked Questions

Google traite-t-il différemment les 301 et 308 pour le PageRank ?
Google n'a jamais confirmé officiellement de différence dans le transfert de PageRank entre 301 et 308. La logique suggère un traitement identique puisque les deux sont des redirections permanentes, mais aucune donnée publique ne l'atteste formellement.
Les 307 et 308 sont-elles plus lentes que les 301/302 ?
Non, la latence de traitement est identique. La différence est purement comportementale : conservation ou non de la méthode HTTP et du body de la requête. Aucun impact mesurable sur le temps de réponse serveur.
Dois-je remplacer toutes mes 301 par des 308 après une migration HTTPS ?
Non, seulement si vous avez identifié du trafic POST vers les anciennes URLs HTTP. Pour un site classique crawlé en GET, la 301 suffit largement et présente moins de risques de régression applicative.
Les CDN comme Cloudflare supportent-ils correctement les 307/308 ?
Oui, les CDN modernes gèrent nativement ces codes. Vérifiez toutefois votre configuration de cache : certains paramètres peuvent altérer le comportement des POST redirigés. Testez avec un POST réel avant déploiement.
Comment savoir si je perds des données à cause de redirections POST mal configurées ?
Analysez vos logs serveur pour repérer les POST suivis de 301/302, puis croisez avec vos taux d'abandon sur ces URLs dans Analytics. Un pic d'exits sans conversion est un indicateur fort de perte de données utilisateur.
🏷 Related Topics
AI & SEO Redirects

🎥 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 →

Related statements

💬 Comments (0)

Be the first to comment.

2000 characters remaining
🔔

Get real-time analysis of the latest Google SEO declarations

Be the first to know every time a new official Google statement drops — with full expert analysis.

No spam. Unsubscribe in one click.