Is AMP still necessary to rank in Top Stories on mobile?

What led Google to initially impose AMP in Top Stories?

AMP (Accelerated Mobile Pages) was launched to force the media ecosystem to drastically accelerate mobile loading. The format imposed strict constraints: no heavy third-party JavaScript, limited CSS, pre-loaded resources.

Google made it mandatory for Top Stories in 2016 — an ultra-visible carousel that drives massive traffic to news sites. The message was clear: adopt AMP or you don't exist in this premium area. The result? Forced adoption, even among those who hated the format’s limitations.

What specific changes come with this announcement?

Starting from May 2021, the requirement disappears. Non-AMP pages become eligible for Top Stories, provided they meet Page Experience criteria. We move away from a binary logic (AMP = yes/no) to a continuous assessment based on Core Web Vitals, HTTPS, mobile-friendliness, and absence of aggressive interstitials.

Google positions Page Experience as a ranking factor for Top Stories. This means that two fresh news pages on the same topic will no longer be differentiated solely by relevance and authority — UX signals are now part of the equation. But beware: Google remains vague about the exact weight of this factor. [To be verified]

Does AMP retain any residual advantage after this update?

Google claims that AMP is no longer required, but doesn’t explicitly state that AMP loses all advantage. In practice, a well-built AMP page breezes through Core Web Vitals — the format is designed for that. It also keeps the lightning icon in some search contexts, a visual signal that can influence CTR.

The real question: does Google continue to implicitly favor AMP through its algorithms, despite the official rhetoric? Field observations vary. Some publishers report a drop in visibility after abandoning AMP, while others see no impact. The lack of transparency about the exact weighting leaves significant strategic ambiguity.

• End of the AMP requirement for mobile Top Stories starting May 2021
• Page Experience becomes a ranking criterion in Top Stories (weight not disclosed)
• Core Web Vitals, HTTPS, mobile-friendly, no interstitials become the new technical prerequisites
• AMP remains compatible and may maintain practical advantages (native performance, iconography)
• Well-optimized standard pages can now compete with AMP on an equal theoretical footing

Is this statement consistent with observed practices in the field?

Google presents this change as a democratization: no need to adopt a proprietary format to compete in Top Stories. On the surface, it’s a liberating message. However, the reality on the ground is more nuanced. Many publishers who abandoned AMP post-May 2021 have observed fluctuations in visibility in Top Stories, sometimes downward.

The problem is that Google provides no figures on the weight of Page Experience in the Top Stories algorithm. Is it 5% of the scoring? 20%? That changes everything. Without this transparency, it’s hard to know if a non-AMP site with average Core Web Vitals (LCP at 2.8s, for instance) can genuinely compete with an AMP competitor that shows 1.2s. [To be verified]

What biases or blind spots exist in this communication?

Google sidesteps the question of the infrastructure required to maintain excellent Core Web Vitals on dynamic content filled with ads and analytics scripts. AMP solved this problem by severely restricting everything. Now, publishers must replicate this performance without the safety nets of AMP, demanding serious technical investment.

Another blind spot: Google does not address multi-format contexts. A site can very well serve standard for Top Stories and keep AMP for other uses (Discover, Google News app in certain countries). The statement remains vague regarding hybrid strategies and their implications.

In what situations might this rule not apply as announced?

If you operate in an ultra-competitive niche (finance, health, breaking political news), every millisecond counts. In these contexts, AMP may still provide a marginal advantage—not by algorithmic obligation, but because it’s the shortest path to perfect Core Web Vitals.

Conversely, for less contested topics or B2B verticals where Top Stories generates little traffic, all this discussion is secondary. Focus your resources elsewhere—internal linking, semantic optimization, content strategy. The race for milliseconds only matters if the Top Stories carousel represents significant volume in your acquisition mix.

What should you do if you are still on AMP?

First step: measure the true weight of Top Stories in your traffic. If it’s less than 5% of your organic sessions, the stakes are likely overestimated. However, if Top Stories represents 20%+ of your mobile traffic, every technical decision must be tested carefully.

Next, compare the Core Web Vitals of your AMP pages versus your standard pages. If your normal pages already meet the thresholds (LCP < 2.5s, FID < 100ms, CLS < 0.1), you might consider a gradual migration. Start with a cluster of low-stakes content, monitor Top Stories traffic for 4-6 weeks, then expand if the metrics hold.

What mistakes should you avoid during the transition?

Don’t cut AMP abruptly, thinking that Google will automatically index your standard pages in Top Stories. The re-indexing time can take several weeks, and during this period, you risk a visibility drop. Use a hybrid approach: keep AMP active while Google crawls and validates the standard versions.

Another classic pitfall: believing that passing Core Web Vitals in lab (Lighthouse) is sufficient. What matters is the field data in the Chrome User Experience Report (CrUX). A site can score 95/100 on Lighthouse and fail on actual CrUX metrics if visitors have slow connections or low-end devices. Monitor Search Console > Core Web Vitals for real-world data.

How can you check if your site is eligible for Top Stories post-AMP?

Use the Google Rich Results test (formerly structured data testing tool) and ensure that your articles include valid NewsArticle or Article markup. Also check that you comply with Google News content policies—no invasive interstitials, HTTPS required, mobile-friendly design.

Next, audit your Core Web Vitals on a representative sample of URLs. If over 75% of your pages meet CrUX thresholds, you’re in the green zone. If you hover between 50-75%, prioritize optimization: lazy-load images, pre-load critical resources, reduce third-party JavaScript.

• Measure the share of Top Stories traffic in your organic mix (Search Console > Performance > Search Type > News)
• Compare AMP vs. standard Core Web Vitals on a sample of URLs via CrUX or PageSpeed Insights
• Test a partial migration on a cluster of secondary content before large-scale deployment
• Keep AMP active during the transition phase (at least 4-6 weeks) to avoid visibility gaps
• Monitor Search Console > Core Web Vitals and Google News traffic daily during the switch
• Validate the NewsArticle/Article markup and Google News policies on all candidate pages