Why does Google sometimes show both HTML and AMP versions of the same page simultaneously in the SERPs?

What do these simultaneous appearances really mean for indexing?

When Google correctly indexes an AMP page, it must establish a canonical link between the standard version and its accelerated variant. Under normal circumstances, the engine serves only one URL in mobile organic results: the AMP version if it exists and is valid, otherwise the HTML.

The appearance of both versions in the SERPs signals that Google has not detected the equivalence relationship between the two URLs. It treats them as independent entities, each eligible for ranking. This malfunction usually occurs when rel="amphtml" and rel="canonical" tags are missing, improperly implemented, or when the content diverges too much between the two versions.

How is Google supposed to handle alternative versions?

The AMP protocol mandates an explicit bidirectional declaration: the HTML page must point to its AMP variant via rel="amphtml", and the AMP page must point to the canonical version via rel="canonical". Google uses these signals to consolidate ranking signals and present only one URL.

In the News carousel specifically, only valid AMP pages are eligible for display. If an HTML version appears in this context typically reserved for AMP, it indicates that the technical validation has failed or that Google has not detected the existence of the accelerated variant.

What are the concrete symptoms of this indexing problem?

The first indicator is the presence of two distinct URLs in the results for the same branded or navigational query. Typically, you will see example.com/article and example.com/article/amp appearing one above the other, or in different positions depending on the queries.

The second symptom appears in Google Search Console: you will observe two separate performance reports, with impressions and clicks divided between the two versions. Core Web Vitals data will also be fragmented, hindering a consolidated view of actual performance.

• Bidirectional canonical declarations are mandatory to link HTML and AMP
• Separate indexing = dilution of ranking signals between two URLs
• Potential content duplication if Google does not recognize equivalence
• Loss of control over the served version: Google may alternate based on opaque criteria
• Fragmentation of metrics in Search Console and analytics tools

Is this unique indexing rule always respected by Google?

On paper, the AMP protocol is clear. In practice, Google regularly presents inconsistencies between what is documented and what actually happens in the SERPs. I have observed cases where pages with perfect canonical implementation still appeared in duplicate, particularly during index updates or migrations.

The consolidation delay also plays a role: after publishing a new page or correcting the tags, it can take several weeks before Google recognizes the relationship and merges the URLs in the results. During this transition period, both versions coexist, even with flawless technical implementation. [To be verified]: no Google documentation specifies this consolidation delay.

What nuances should be added to this declaration?

Mueller talks about "valid AMP pages" without specifically defining this validation threshold. In reality, Google tolerates minor AMP errors without demoting the page. However, certain violations — unauthorized JavaScript, forbidden tags, excessive loading times — completely invalidate the AMP version without necessarily giving you a clear warning in Search Console.

Another point not addressed is the issue of content. If your AMP version is significantly poorer than the HTML (less text, missing images, absent features), Google may decide to serve the HTML even on mobile, considering the degraded user experience. This is not officially documented, but it has been observed in the field for years.

In what contexts might this double indexing be intentional?

There are edge cases where the simultaneous appearance is not a bug but a deliberate choice by the publisher. Some sites maintain both AMP and HTML versions with sufficiently different content for Google to treat them as distinct pages: free vs. premium version, shortened content vs. full content, differentiated geographic targeting.

In these scenarios, the absence of a cross-canonical tag is intentional. But be careful: you then lose all the benefits of the AMP protocol in terms of ranking consolidation. This is a risky strategy that requires deep consideration of potential cannibalization and authority dilution.

How to quickly diagnose this issue on my site?

The first reflex: perform a search site:yourdomain.com "exact title of the article" on mobile. If you see two distinct URLs (standard version + /amp/), you have confirmation of the problem. Repeat the process on several pieces of content to gauge the extent.

Next, inspect the source code of your HTML page. Check for the presence and syntax of <link rel="amphtml" href="...">. Do the reverse on the AMP page: look for <link rel="canonical" href="...">. Both should point to the correct URLs, with no intermediary redirects or extraneous parameters.

What corrective actions should be implemented immediately?

If the canonical tags are missing, add them as a priority. If they exist but are malformed — relative URLs instead of absolute, missing HTTPS, inconsistent trailing slashes — correct them. Then use the Google AMP Test tool to validate that your accelerated version meets all specifications.

Once the corrections are deployed, force a new crawl via Search Console to expedite the acknowledgment. But be patient: consolidation in the results can take 2 to 6 weeks depending on your site's crawl frequency and the complexity of your architecture.

Should AMP pages always be prioritized?

Let’s be honest: AMP has lost much of its strategic value since Google opened the News carousel to non-AMP pages that meet Core Web Vitals. If your mobile site is already fast and well-optimized, maintaining a parallel AMP infrastructure often represents a disproportionate technical cost.

Before investing in fixing a double AMP indexing issue, ask yourself: should I keep AMP or remove these versions to simplify my architecture? If you choose to remove it, redirect all /amp/ URLs to their HTML equivalents with a 301 redirect, and monitor Search Console to confirm gradual deindexing.

• Search site: on mobile to detect indexed duplicates
• Check the presence and syntax of rel="amphtml" and rel="canonical" tags
• Test each AMP page with the official Google tool to validate compliance
• Force recrawl via Search Console after correcting tags
• Monitor the evolution of impressions in performance reports for 4-6 weeks
• If removing AMP, implement 301 redirects and disavow /amp/ URLs in the sitemap