Does AMP really enhance your Google rankings?

Has AMP ever been a direct ranking signal?

Gary Illyes has repeatedly emphasized: AMP has never been a ranking factor in itself. The framework developed by Google improves mobile page loading speed, but its adoption does not guarantee any automatic algorithmic boost.

The AMP badge that was displayed in mobile SERPs — which is now being gradually phased out — played a role that was purely visual and informative. It signaled to users that a page would load quickly, without influencing its ranking in organic results.

Why does this confusion persist among SEO practitioners?

For years, AMP was mandatory to appear in the Top Stories carousel on mobile. This requirement created a mental association between AMP and increased visibility, fostering the belief that AMP boosted ranking.

Since the integration of Core Web Vitals as a ranking factor, Google has expanded access to the Top Stories carousel to all pages that meet its quality criteria, AMP or not. The equation has clarified: what matters is actual performance, not the technical format.

What does "not a ranking signal" really mean?

When Google states that an element is not a ranking signal, it means that the algorithm does not use it directly as a scoring variable. No bonus is granted simply for the presence of the AMP tag in the source code.

This doesn't mean the impact is nil. A well-optimized AMP page loads faster, improving user experience and reducing bounce rate. These behavioral signals, in turn, influence ranking — but it's the indirect effect of speed, not the AMP framework itself.

• AMP is not a direct ranking factor: no algorithmic advantage tied to the format
• The AMP badge remains purely informational: no impact on organic positioning
• The benefits come through speed: Core Web Vitals capture the performance effect
• Access to the Top Stories carousel no longer requires AMP: any fast, quality page can appear there
• Indirect behavioral signals matter: loading times, bounce rates, engagement

Is this statement consistent with on-the-ground observations?

Absolutely. A/B testing conducted on news and e-commerce sites shows that switching to AMP without a substantial improvement in actual speed changes nothing to ranking. Observed gains consistently stem from reducing load time, not from the framework itself.

In contrast, the psychological effect of the AMP badge on CTR was real as long as it was displayed. In certain verticals, the badge generated up to 15-20% more clicks — a purely UX benefit, confirming that the badge served an informational role, not an algorithmic one.

What nuances should be added to this statement?

Stating that AMP is not a ranking factor does not mean it is useless. In certain contexts — high-traffic mobile news sites, viral content — AMP remains a user experience accelerator that can compensate for average server infrastructures.

However, the cost-benefit ratio has shifted. Maintaining a parallel AMP version requires development, maintenance, and debugging resources. If your technical stack already allows achieving excellent Core Web Vitals without AMP, the investment is no longer justified. [To be verified]: public data on the declining AMP adoption rate confirms this strategic pivot.

In what cases does this rule not apply?

There are no algorithmic exceptions. AMP never becomes a ranking factor, regardless of the industry. However, certain business contexts may still justify its use for non-SEO-related reasons.

Publishers who monetize through Google Ad Manager sometimes find AMP to be an optimized advertising ecosystem. Websites syndicating their content on third-party platforms (Google News, Apple News) may benefit from facilitated distribution. These are business advantages, not ranking levers.

What should you do if you are already using AMP?

Assess the performance gap between your AMP and non-AMP pages on real Core Web Vitals (CrUX data, Search Console). If the standard version already meets the recommended thresholds (LCP < 2.5s, FID < 100ms, CLS < 0.1), AMP becomes redundant.

Moving away from AMP requires a careful 301 redirect strategy and close monitoring of ranking signals for 4 to 6 weeks. Sites that have abandoned AMP without degrading their actual speed reported no loss of organic traffic — some even saw gains by simplifying their architecture.

What mistakes should be avoided in the AMP vs non-AMP arbitration?

Do not confuse perceived speed and actual speed. AMP preloads certain elements through Google’s cache, which accelerates initial display but does not change the server-side scoring of Core Web Vitals. If your stack is slow without AMP, it remains slow algorithmically.

Another trap: maintaining AMP solely to keep the badge or access to the Top Stories carousel. These advantages have disappeared or are now accessible without AMP. Continuing to support two parallel versions for an obsolete benefit dilutes your development resources.

How can I check that my site no longer needs AMP?

Compare the metrics of your standard pages against the Core Web Vitals thresholds on a representative sample of devices and connections. Use PageSpeed Insights, Lighthouse, and CrUX data to obtain field measurements, not just lab data.

If 75% of your pages meet the recommended thresholds on mobile, AMP no longer provides SEO value. The ultimate test: temporarily disable AMP on a segment of low-traffic pages and monitor ranking + Core Web Vitals over 3 weeks. No degradation confirms that you can migrate safely.

• Audit the real Core Web Vitals (CrUX) on AMP and non-AMP pages
• Compare CTR and user engagement between the two versions
• Evaluate the technical maintenance cost of the AMP stack
• Test the migration on a low-risk sample before global deployment
• Implement clean 301 redirects and monitor Search Console for 6 weeks
• Monitor organic traffic and ranking signals post-migration