Is AMP really neutral for Google rankings, or does it hide an invisible visibility lever?

Does AMP really not impact rankings?

Google plays on words. AMP is not a ranking signal in the core algorithm — an AMP page and a standard page with the same content will theoretically have the same organic position. But this ignores a crucial detail: for years, certain premium search features were reserved for AMP pages.

Top Stories, the visible carousel at the top of mobile SERPs for news queries, only displayed AMP content. The result? Media outlets dropping AMP lost this privileged access, and thus traffic. Not because of rankings, but due to exclusion from a high-CTR feature. Technically, Google was not lying. Practically, AMP conditioned visibility.

What changes with the Page Experience update?

The update mentioned (deployed between June and August) opened Top Stories to non-AMP pages. The entry ticket is no longer the AMP framework, but compliance with Core Web Vitals and Page Experience criteria (HTTPS, no intrusive pop-ups, mobile-friendly).

What does this mean? If your mobile site loads in under 2.5 seconds (LCP), responds quickly to interactions (FID), and remains visually stable (CLS), you can compete for Top Stories without AMP. The technical barrier falls — but performance requirements remain high.

Why did some sites see their traffic drop after removing AMP?

There are two common scenarios. First case: the site abandons AMP before the Page Experience update. It instantly loses access to the AMP-only carousels, with no alternative. Traffic from Top Stories collapses.

Second case: the site removes AMP after the update, but its standard pages do not meet Core Web Vitals. Google ejects them from Top Stories due to insufficient performance. The drop comes from slow loading times, not from the absence of AMP itself. In both situations, the symptom is the same — the cause differs.

• AMP is not a direct ranking signal in Google's organic ranking algorithm
• Some premium search features (Top Stories) required AMP until the Page Experience update
• Since the update, non-AMP pages can access Top Stories if they meet Core Web Vitals
• Removing AMP without optimizing mobile performance causes traffic loss by excluding features, not due to a ranking penalty
• Google's statement is technically true but strategically incomplete — AMP indirectly influences visibility

Is this statement consistent with field observations?

Absolutely, but it deserves decoding. A/B tests conducted by several media outlets (notably in tech and news) confirm: an AMP page and its standard version achieve identical organic positions in classic results. Zero difference in pure ranking.

On the other hand, analytics consistently show a traffic delta between AMP and non-AMP sites until May-June. The source? Placements in Top Stories, which generated 15 to 40% of mobile traffic for news sites. Google is technically right — but omits the massive indirect impact. This is a classic of their communication: factually accurate, strategically incomplete.

In what cases does AMP retain a competitive advantage?

Let's be honest: for sites that cannot meet Core Web Vitals with their current tech stack. If your CMS is heavy, your infrastructure slow, and reworking the architecture would take months, AMP remains a technical shortcut to achieve ultra-fast pages.

AMP imposes a strict framework (limited CSS, controlled JavaScript, pre-optimized components) that ensures good performance. For a WordPress site overloaded with plugins, implementing AMP can be quicker than optimizing the main theme. But it's a band-aid, not a sustainable solution. [To verify]: some also observe that Google's AMP cache remains more responsive than the standard cache — an undocumented advantage.

What interpretation errors should be avoided?

The first error: believing that AMP boosts SEO. No. It opens access to features — a critical nuance. If you're not eligible for Top Stories (no news content, no structured Article tag), AMP is of no use in terms of visibility.

The second error: thinking that removing AMP is neutral if you have good Core Web Vitals. False. The transition requires a clean technical migration (redirections, canonicals, sitemap), under penalty of duplicating content or losing signals. Several sites experienced ranking fluctuations for 2-4 weeks post-migration, while Google reprocessed the signals.

Should you keep or remove AMP from your site?

The decision depends on three variables: your eligibility for reserved features (Top Stories, news carousels), your current mobile performance, and your technical ability to optimize without AMP. If you're a news media outlet with a slow site, keeping AMP makes sense in the short term.

If you're in e-commerce, SaaS, or a blog without news dimensions, AMP has never had SEO value. You could keep it for speed, but today’s modern frameworks (Next.js, Nuxt, static sites) offer equivalent performance without AMP's constraints. In this case, removing AMP simplifies your stack without risking traffic.

How to cleanly migrate away from AMP without losing traffic?

First step: ensure that your standard pages meet Core Web Vitals under real conditions (PageSpeed Insights, Chrome UX Report). LCP under 2.5s, FID under 100ms, CLS under 0.1. If not, optimize first — otherwise, you’ll lose access to premium features.

Next, implement a gradual technical migration. Start by removing the amphtml tags from the heads of standard pages, then redirect AMP URLs to the canonical versions with a 301. Monitor Search Console for indexing errors and drops in clicks. Wait 2-3 weeks before completely disabling the AMP cache — Google may take time to reprocess the signals.

What metrics should you monitor after an AMP change?

In Search Console, segment traffic by search appearance type (Discover, Top Stories, standard organic results). A global decrease may mask a specific drop in Top Stories countered by an organic increase — or vice versa.

On the analytics side, track the bounce rate and session time. AMP pages often have degraded UX (limited features, approximate analytics). Switching to full standard pages can enhance engagement even if initial session counts decrease slightly. Also measure Core Web Vitals continuously via the CrUX Report — a silent regression can eject you from features with no visible alert.

• Audit your Core Web Vitals under real conditions (75th percentile mobile, not just lab tests)
• Check your content’s eligibility for features requiring high performance (Top Stories, Discover)
• If you remove AMP, implement clean 301 redirections and remove amphtml tags from the canonical pages
• Monitor Search Console by appearance type for 4-6 weeks post-migration to identify anomalies
• Test the impact on user engagement (bounce rate, session duration) — AMP pages sometimes have limited UX
• Document the decision and KPIs before/after to justify the choice to stakeholders