Paired AMP: Is it really the regular HTML that matters for indexing?

What exactly is a paired AMP configuration?

A paired AMP configuration consists of two versions of the same page: a classic HTML version and an AMP (Accelerated Mobile Pages) version. These two versions are linked through rel="amphtml" tags in the normal HTML and rel="canonical" in the AMP page.

The classic HTML version remains accessible at the original URL. The AMP version usually lives on a dedicated subdomain or subdirectory. Google detects this linking and understands that these are two representations of the same resource.

Why is Mueller's statement important?

Because it resolves a recurring debate: which version matters for indexing and ranking? Many SEOs feared that Google would prioritize the AMP version for ranking or mix signals between the two versions.

Mueller clarifies: Google indexes normal HTML. The AMP page is an alternative display format. It may appear in the AMP carousel on mobile, but it does not replace the canonical page in the index. Therefore, all your efforts for structured data, internal linking, and semantic optimization should focus on the classic HTML version.

How does Google decide which version to display to the user?

When a mobile user clicks on a result in the regular SERPs, they land on the normal HTML version. However, in certain contexts — particularly in the Top Stories AMP carousel or specific displays — Google may serve the AMP version directly to speed up loading.

This decision is based on the browsing context and the device's capabilities, not on ranking criteria. The AMP version is just a technical wrapper to improve speed, not a quality signal in itself.

• Google indexes the normal HTML version, even in a paired AMP configuration.
• The AMP version serves as an alternative mobile display, not a canonical version.
• On-page optimizations (tags, content, structured data) should be done on the classic HTML.
• The AMP page may appear in specific contexts (Top Stories carousel, AMP cache).
• The linking between the two versions is done via rel="amphtml" and rel="canonical".

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

Yes, and it's actually one of the few cases where Google's discourse aligns exactly with what we observe. Crawl and indexing tests consistently show that Googlebot indexes the classic HTML version, even when an AMP version exists and is correctly linked.

Search Console audits confirm this as well: coverage reports, Core Web Vitals, structured data — everything tracks back to the normal HTML version. The AMP version sometimes appears in specific AMP reports, but never as an indexed canonical URL.

Should you still invest in AMP in a paired configuration?

It depends on your priorities. If you aim for the Top Stories carousel or ultra-fast display contexts, AMP still holds tactical interest. But let's be honest: since the Page Experience update and the removal of the AMP lightning badge, its strategic relevance has diminished.

For most sites, optimizing the classic HTML for Core Web Vitals provides a better ROI than maintaining a dual HTML + AMP setup. The paired AMP remains relevant for media that want to maximize their mobile presence in carousels, but it has become one of many acquisition channels, not an SEO necessity.

What pitfalls should you avoid with paired AMP?

The number one pitfall: believing that the AMP version automatically inherits the optimizations of the HTML version. This is not the case. If you add structured data Article to the HTML but forget it on the AMP, the latter won't be eligible for the Top Stories carousel.

Another common mistake: a reversed canonical. Some sites point the HTML page's canonical to AMP instead of the other way around. Result: Google considers the AMP as canonical, creating inconsistency and potentially degrading indexing. Always verify that the AMP page points its canonical to the normal HTML, and that the HTML points its amphtml to the AMP.

What should you actually do with a paired AMP configuration?

First, focus your SEO efforts on the normal HTML version. That version matters for indexing, so it should carry your optimizations: title/meta tags, structured data, internal linking, enriched editorial content. The AMP version should be just a lightweight, technically compliant copy, but secondary.

Next, check the consistency of linking tags. The HTML page should contain a rel="amphtml" link to the AMP, and the AMP page should point its rel="canonical" to the HTML. Use the URL inspector in Search Console on both versions to confirm that Google links them correctly.

How to verify that Google properly indexes the HTML version and not the AMP?

Perform a search for site:yourdomain.com "exact-page-title" in Google. The URL that appears first should be the normal HTML version, not the AMP URL. If the AMP URL appears as canonical, there's a configuration problem.

Also, use the URL inspection tool in Search Console. Enter the normal HTML URL: Google should indicate it's indexed and that an alternative AMP version exists. If you inspect the AMP URL, Google should indicate it points its canonical to the HTML.

Should you still create AMP pages or migrate to optimized HTML?

If you don’t have AMP yet and are wondering: don't start now. Instead, invest in optimizing your classic HTML for Core Web Vitals. The mobile display gains from AMP no longer outweigh the maintenance of a double technical stack.

If you already have AMP in place and it's performing well (carousel traffic, high click-through rates), keep it but don’t exhaust yourself maintaining it. If maintenance becomes cumbersome or AMP traffic is marginal, consider a gradual migration to optimized single HTML. Many media outlets have made this transition in recent years without losing traffic.

• Ensure the HTML page contains a rel="amphtml" link to the AMP
• Ensure the AMP page contains a rel="canonical" link to the HTML
• Inspect both versions in Search Console to confirm the linking
• Focus on on-page optimizations (structured data, content, linking) on the HTML version
• Run the site: search to confirm Google indexes the HTML as canonical
• Monitor AMP reports in Search Console for linking errors