Official statement
Other statements from this video 42 ▾
- 42:49 Peut-on vraiment utiliser hreflang entre plusieurs domaines distincts ?
- 48:45 Peut-on vraiment utiliser hreflang entre plusieurs domaines distincts ?
- 58:47 Faut-il vraiment éviter de dupliquer son contenu sur deux sites distincts ?
- 58:47 Faut-il vraiment éviter de créer plusieurs sites pour le même contenu ?
- 91:16 Faut-il vraiment indexer les pages de recherche interne de votre site ?
- 91:16 Faut-il bloquer les pages de recherche interne pour éviter l'indexation d'un espace infini ?
- 125:44 Les Core Web Vitals influencent-ils vraiment le budget de crawl de Google ?
- 125:44 Réduire la taille de page améliore-t-il vraiment le budget crawl ?
- 152:31 Le rapport de liens internes dans Search Console reflète-t-il vraiment l'état de votre maillage ?
- 152:31 Pourquoi le rapport de liens internes de Search Console ne montre-t-il qu'un échantillon ?
- 172:13 Faut-il vraiment s'inquiéter des chaînes de redirections pour le crawl Google ?
- 172:13 Combien de redirections Google suit-il réellement avant de fractionner le crawl ?
- 201:37 Comment Google segmente-t-il réellement vos Core Web Vitals par groupes de pages ?
- 201:37 Comment Google segmente-t-il réellement vos Core Web Vitals par groupes de pages ?
- 248:11 AMP ou canonique : qui récolte vraiment les signaux SEO ?
- 257:21 Le Chrome UX Report compte-t-il vraiment vos pages AMP en cache ?
- 272:10 Faut-il vraiment rediriger vos URLs AMP lors d'un changement ?
- 272:10 Faut-il vraiment rediriger vos anciennes URLs AMP vers les nouvelles ?
- 294:42 AMP est-il vraiment neutre pour le classement Google ou cache-t-il un levier de visibilité invisible ?
- 342:21 Pourquoi le contenu copié surclasse-t-il parfois l'original malgré le DMCA ?
- 342:21 Le DMCA est-il vraiment efficace pour protéger votre contenu dupliqué sur Google ?
- 359:44 Pourquoi le contenu copié surclasse-t-il votre contenu original dans Google ?
- 409:35 Pourquoi vos featured snippets disparaissent-ils sans raison technique ?
- 409:35 Les featured snippets et résultats enrichis fluctuent-ils vraiment par hasard ?
- 455:08 Le contenu masqué en responsive mobile est-il vraiment indexé par Google ?
- 455:08 Le contenu caché en CSS responsive est-il vraiment indexé par Google ?
- 563:51 Les structured data peuvent-elles vraiment forcer l'affichage d'un knowledge panel ?
- 563:51 Existe-t-il un balisage structuré qui garantit l'apparition d'un Knowledge Panel ?
- 583:50 Pourquoi la plupart des sites n'obtiennent-ils jamais de sitelinks dans Google ?
- 583:50 Peut-on vraiment forcer l'affichage des sitelinks dans Google ?
- 649:39 Les redirections 301 transfèrent-elles vraiment 100 % du jus SEO sans perte ?
- 649:39 Les redirections 301 transfèrent-elles vraiment 100% du PageRank et des signaux SEO ?
- 722:53 Faut-il vraiment supprimer ou rediriger les contenus expirés plutôt que de les garder indexables ?
- 722:53 Faut-il vraiment supprimer les pages expirées ou peut-on les laisser avec un label 'expiré' ?
- 859:32 Les mots-clés dans l'URL : facteur de ranking ou simple béquille temporaire ?
- 859:32 Les mots dans l'URL influencent-ils vraiment le classement Google ?
- 908:40 Faut-il vraiment ajouter des structured data sur les vidéos YouTube embarquées ?
- 909:01 Faut-il vraiment ajouter des données structurées vidéo quand on embed déjà YouTube ?
- 932:46 Les Core Web Vitals impactent-ils vraiment le SEO desktop ?
- 932:46 Pourquoi Google ignore-t-il les Core Web Vitals desktop dans son algorithme de classement ?
- 952:49 L'API et l'interface Search Console affichent-elles vraiment les mêmes données ?
- 963:49 Peut-on utiliser des templates différents par version linguistique sans pénaliser son SEO international ?
Google claims that AMP does not directly influence organic ranking. However, until the Page Experience update, AMP was required to access the Top Stories carousel on mobile. Since then, non-AMP pages with excellent Core Web Vitals can also vie for this premium visibility — changing the game for sites that were hesitant to implement AMP.
What you need to understand
Does AMP really boost ranking in standard SERPs?<\/h3>
The answer is no<\/strong>, and John Mueller states this plainly. AMP is not a direct ranking criterion in Google's algorithm. An AMP page and a standard HTML page with identical content and similar performance theoretically have the same chances of ranking.<\/p> What creates confusion is that for years, AMP was mandatory to appear in the Top Stories carousel on mobile<\/strong> — an ultra-visible position that generates significant traffic. Many publishers have invested in AMP not for a hypothetical ranking bonus, but to access this feature. And from the outside, it looked like an SEO advantage.<\/p> With the rollout of the Page Experience update (initially intended for May, ultimately stretched over several months), Google opened Top Stories to non-AMP pages<\/strong> — as long as they display excellent Core Web Vitals and adhere to news content criteria.<\/p> Specifically, if your mobile site offers a Largest Contentful Paint (LCP) under 2.5 seconds, a First Input Delay (FID) below 100 ms, and a Cumulative Layout Shift (CLS) under 0.1<\/strong>, you can now compete for Top Stories without going through AMP. This is a major change for sites that found the AMP stack too restrictive or difficult to maintain.<\/p> Yes, but only in certain specific contexts. AMP ensures ultra-fast loading times by design through a centralized cache and optimized components<\/strong>. For publishers who do not have the technical resources to optimize their Core Web Vitals to the required levels, AMP remains a viable shortcut.<\/p> Moreover, some advertising formats or third-party widgets can degrade the performance of a standard page. In these cases, AMP enforces strict discipline<\/strong> that prevents deviations. But let's be clear: if you master frontend optimization, you no longer need AMP to access Top Stories.<\/p>What has changed with the Page Experience Update?<\/h3>
Does AMP still have technical relevance?<\/h3>
SEO Expert opinion
Is this statement consistent with what we observe in the field?<\/h3>
Absolutely. Field tests confirm that AMP alone does not improve organic positioning<\/strong>. Sites that migrated from AMP to optimized HTML pages reported no loss in organic traffic — as long as they maintained equivalent performance. However, abandoning AMP without an alternative optimization has sometimes caused a fall in Top Stories, reinforcing Mueller's thesis: AMP was a pass for certain features, not a ranking lever.<\/p> What remains unclear is the granularity of the Core Web Vitals thresholds required for Top Stories<\/strong>. Google communicates general tiers (good / to improve / poor), but in an ultra-competitive segment like news, it's unclear whether micro-differences in LCP or CLS affect eligibility. [To be verified]<\/strong>: Google has never publicly documented these precise thresholds for Top Stories.<\/p> First point: even if AMP is not a direct factor, speed is. And AMP mechanically speeds up loading. So indirectly, an AMP site may rank better than a slow site — but it's speed that matters, not the AMP label. The semantic nuance is important: it’s not AMP that boosts, but the performance it dictates.<\/p> Second point: Mueller's statement primarily concerns mobile<\/strong>. On desktop, Top Stories has never required AMP. And on mobile, the transition to Core Web Vitals as an eligibility criterion took time — some sites benefitted from preferential treatment during the transition phase simply because they were already AMP. Today, this ambiguity has dissipated, but it fueled years of debate.<\/p> If your site operates in a niche where Top Stories or Google News represent a significant share of traffic<\/strong> — news, sports, real-time finance — the question is not whether AMP boosts ranking, but whether it remains the easiest way to meet the required performance thresholds.<\/p> Additionally, some CMS or technical stacks make optimizing Core Web Vitals extremely costly in time and resources. In these contexts, AMP may remain a pragmatic solution<\/strong> — not for a hypothetical SEO bonus, but to ensure eligibility for certain features without overhauling the entire frontend architecture.<\/p>What nuances should be added to this statement?<\/h3>
In what cases does this rule not apply?<\/h3>
Practical impact and recommendations
Should you abandon AMP if you have already implemented it?<\/h3>
Not necessarily. If your AMP implementation is working well, generates no technical debt, and your Core Web Vitals are good<\/strong>, there is no urgent need to migrate. However, if AMP forces you to maintain two versions of each page, with extended publication times and recurrent bugs, it is time to reassess.<\/p> The right approach: audit your Core Web Vitals on your standard HTML pages<\/strong>. If they meet the thresholds (LCP < 2.5s, FID < 100 ms, CLS < 0.1), you can gradually switch. Start with a low-risk sample of pages, monitor the impact on Top Stories and overall traffic, and then generalize if the results are conclusive.<\/p> Relentlessly optimize your Core Web Vitals<\/strong>. LCP: reduce the weight of above-the-fold images, use a performant CDN, enable lazy loading on non-critical resources. FID: minimize blocking JavaScript, defer third-party scripts. CLS: specify the dimensions of images and iframes to avoid reflows.<\/p> Then, ensure your site adheres to Google News editorial criteria<\/strong>: original content, editorial transparency, identified authors, no aggressive clickbait. Without this, even with perfect Core Web Vitals, you will not be eligible. And check that your structured markup (Article, NewsArticle) is flawless.<\/p> First mistake: removing AMP suddenly without monitoring<\/strong>. If your standard pages are not up to par, you will lose access to Top Stories overnight. Test first in parallel, measure impact, and then switch.<\/p> Second mistake: believing that optimizing Core Web Vitals is a one-off task. It is a continuous project<\/strong>. Every theme update, every new plugin, every third-party script can degrade your performance. Set up automated monitoring (PageSpeed Insights API, Lighthouse CI, CrUX) to detect regressions before they affect your eligibility.<\/p>How can you ensure eligibility for Top Stories without AMP?<\/h3>
What mistakes should be avoided in this transition?<\/h3>
❓ Frequently Asked Questions
AMP améliore-t-il le classement dans les résultats organiques classiques ?
Peut-on accéder à Top Stories sans AMP aujourd'hui ?
Quels Core Web Vitals faut-il atteindre pour Top Stories ?
Dois-je abandonner AMP si je l'ai déjà implémenté ?
AMP reste-t-il pertinent pour certains sites ?
🎥 From the same video 42
Other SEO insights extracted from this same Google Search Central video · duration 996h50 · published on 12/03/2021
🎥 Watch the full video on YouTube →Related statements
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.
💬 Comments (0)
Be the first to comment.