Do non-AMP pages really penalize an entire AMP site?

Is AMP still a ranking factor in 2025?

Google's statement confirms that AMP is not a technical requirement for an entire site. A domain can operate in hybrid mode, with some sections in AMP and others in standard HTML, without facing algorithmic penalties.

What changes is access to preferred features in search results. Non-AMP pages notably lose eligibility for Top Stories carousels, enriched positions on mobile, and certain advantageous visual formats. The intrinsic speed gain of AMP also disappears, which directly impacts Core Web Vitals.

Why does Google maintain this distinction between AMP and non-AMP pages?

The technical architecture of AMP is based on strict performance constraints: drastic limitation of JavaScript, asynchronous loading of resources, aggressive caching via Google servers. These constraints ensure a predictable and fast user experience.

By not imposing AMP across an entire site, Google acknowledges that some pages require features incompatible with AMP — complex forms, interactive interfaces, advanced advertising tracking. This coexistence then becomes a pragmatic compromise.

What constitutes an "AMP-compatible" page according to Google?

A valid AMP page must comply with the technical specifications of the AMP framework: exclusive use of AMP HTML components, validation by the official tool, absence of critical errors in the console. The mere speed of a standard page is not sufficient.

Validation is done through the AMP test in the Search Console, which detects syntax errors, prohibited tags, or blocking resources. A page that fails this test will never benefit from AMP advantages, even if it loads in 0.5 seconds.

• A site can mix AMP and non-AMP pages without global penalties
• Only valid AMP pages gain access to preferred positions (Top Stories, carousels)
• Speed alone does not replace AMP technical compliance
• The Search Console remains the reference tool to check AMP validity
• AMP advantages primarily concern mobile and news formats

Is this statement consistent with real-world observations?

On paper, Google's position seems clear. In reality, the actual impact of AMP on ranking remains unclear. Since the removal of the visible AMP label in the SERPs and the integration of Core Web Vitals, many sites have abandoned AMP without experiencing a significant drop in traffic. [To be verified]: data shows that the correlation between AMP presence and Top Stories positions has weakened since 2022.

The promise of "preferential presentation" is actually conditioned by numerous competing criteria — content freshness, domain authority, user engagement. A mediocre AMP page will never surpass a fast and high-quality HTML page, even if Google hints otherwise in this statement.

In what cases does this rule really not apply?

The coexistence of AMP/non-AMP works poorly on e-commerce sites with a strong interactive component. Product pages often require features (configurators, real-time comparators, complex checkout) that are incompatible with AMP restrictions. Maintaining two parallel versions quickly becomes unmanageable.

Another problematic case involves sites with a high volume of dynamic pages. Generating and maintaining AMP versions for thousands of listings requires a solid technical infrastructure. Even a minor generation bug can create cascading errors that the Search Console may take weeks to report.

What nuances should be added to this official statement?

Google talks about "speed advantages", but the reality is more nuanced. A perfectly optimized classic HTML site can match or even exceed AMP performance on Core Web Vitals. The real gain from AMP is caching on Google servers, which ensures an almost instantaneous LCP from the SERPs.

The "preferential presentation" concept is also fluid. Top Stories carousels have lost visibility since 2023, and many enriched formats are now accessible without AMP (FAQ, How-to, Product). The ROI of an AMP migration must be reevaluated on a case-by-case basis, not accepted as a given.

What should I concretely do if my site mixes AMP and standard HTML?

The first step is to precisely map which sections are AMP and which are not. Use a crawler (Screaming Frog, Oncrawl) with a filter on the <html amp> tags to identify the current distribution. This will provide you with a clear view of the coexistence areas.

Next, check the configuration of canonical tags between AMP and non-AMP versions. Each AMP page should point via rel="canonical" to its standard HTML version and vice versa via rel="amphtml". An error here can create conflicting signals for Google and dilute your link equity.

How to measure the real impact of AMP on my rankings?

Isolate in Search Console the queries for which your AMP pages appear in Top Stories or carousels. Compare the CTR and average position with your standard HTML pages on similar queries. If the gap is less than 15-20%, AMP likely does not bring enough value to justify maintenance.

Also test the correlation between AMP presence and mobile traffic. Create an Analytics segment filtering only organic mobile traffic, then compare sessions from AMP pages versus non-AMP pages. If bounce rates and session times are equivalent, it means your standard HTML is already performing adequately.

What mistakes should be avoided in a hybrid AMP/non-AMP strategy?

Don't fall into the trap of fully duplicating your site in AMP "just in case". It's a waste of time and resources. Focus AMP on editorial content with high Top Stories potential (news, guides) and leave the rest in optimized HTML.

Also avoid neglecting the maintenance of AMP pages once the initial deployment is done. AMP specifications evolve, new components emerge, and others are deprecated. An AMP page that becomes invalid immediately loses all its advantages, with no visible warning on the user side.

• Audit the AMP/non-AMP distribution with a technical crawler
• Check the consistency of canonical/amphtml tags on all page pairs
• Monitor AMP errors in the Search Console weekly
• Measure the real ROI of AMP via Analytics (CTR, bounce rate, conversions)
• Test Core Web Vitals on non-AMP pages to identify priority optimizations
• Document the coexistence strategy to avoid inconsistencies during site changes