How does Google choose which content version to display between PWA, desktop, and AMP?

Why does Google require choosing a primary version?

When the same content exists in multiple forms — traditional desktop site, Progressive Web App, AMP page — Google must decide which one to index as the reference. Without clear guidance, the engine risks treating each version as distinct content, thereby creating internal cannibalization.

The Splitt directive is not new, but it clarifies a point often misunderstood: it's up to the site to declare its preference, not for Google to guess. The phrase “suitable for the largest number of users” means the most comprehensive, stable version that represents the experience you want to offer by default.

How does Google decide which version to show next?

Once the primary version is designated through the appropriate canonical tags, Google may choose to serve another version in the results if it better fits the search context. For example, an AMP page for a mobile user quickly seeking news, or the PWA for a returning user.

This mechanism relies on contextual signals: type of device, search intent, browsing history, estimated connection speed. Google does not communicate the exact weighting of these criteria — [To be verified] — but field observations indicate that loading speed and mobile compatibility weigh heavily.

What changes for an SEO managing multiple versions?

The directive imposes an explicit hierarchy among versions. Gone are the days when one could coexist desktop and AMP without clear canonical tags hoping that Google would “understand”. Today, each non-primary version must point to the reference version via rel=canonical.

For PWAs, this is less straightforward as they often act as an overlay of the desktop experience. If the PWA and desktop site serve exactly the same HTML at the same URL, there is technically only one version in Google's eyes. The problem arises when the PWA uses distinct URLs or implements significant client-side rendering.

• Designate a clear primary version via canonicals to avoid index duplication
• Link all variants (AMP, mobile, PWA) to this primary version
• Test the consistency of canonical and alternate media tags to ensure Google understands the hierarchy
• Do not assume Google will automatically make the right choice without explicit direction
• Monitor Search Console coverage reports to detect unwanted indexed versions

Is this directive consistent with practices observed in the field?

Yes, largely. SEO audits regularly reveal cases of cannibalization between poorly configured desktop and AMP versions, where Google indexes both URLs as distinct and dilutes the ranking signal. The Splitt directive confirms what we observe: without explicit canonical tags, Google does not perform miracles.

However, the passage “Google will decide which to show based on user needs” remains deliberately vague. What “needs” exactly? Speed? Compatibility? Enriched content? Google does not publish a decision matrix, and A/B tests show that this choice can vary for the same query depending on context. [To be verified] with your own organic traffic data.

What nuances should be added to this recommendation?

Splitt operates under the assumption that different versions serve the same content. But in reality, AMP often entails compromises (limited JavaScript, restricted CSS, curtailed features). If your AMP page is a stripped-down version of the desktop experience, is it really worth offering it as an alternative?

The second nuance: for sites generating client-side dynamic content (React, Vue, Angular as PWA), the “primary version” seen by Googlebot may differ from that seen by the user. JavaScript hydration sometimes creates a gap between the initial HTML (what Google indexes) and the final experience. In these cases, the directive to “choose the version that suits the most users” becomes ambiguous.

In what cases does this rule not apply directly?

If you have only one version of content — for example, a classic responsive site without AMP or separate PWA — this guideline does not concern you. This is the majority case for e-commerce and corporate sites that have abandoned AMP or never adopted it.

Another exception: sites using a differentiated content strategy by channel (mobile app with exclusive content, desktop version with advanced modules). In this case, you do not have “multiple versions of the same content,” but several distinct contents — so no canonical to impose, but an information architecture to document.

What practical steps should be taken to declare a primary version?

The first step: audit all active URLs to identify the variants (desktop, mobile, AMP, PWA if it uses distinct URLs). List each URL and its type. Then, decide which version represents the reference experience — generally, this is the desktop site or the primary responsive version.

Next, implement the canonical tags on all secondary versions pointing to the primary version. For AMP, also add the tag <link rel="amphtml"> on the primary version pointing to the AMP, and <link rel="canonical"> on the AMP page pointing to the primary. This bidirectionality is essential.

What mistakes should be avoided when implementing canonicals?

Classic mistake: creating canonical loops where page A points to B, and B points back to A. Google ignores these contradictory directives and chooses arbitrarily. Another trap: pointing all variants to a URL that itself redirects (301 or 302) — the canonical must point to the final URL, not a redirection.

Do not assume that Google will “understand” if you omit canonicals on certain pages. Every AMP page must have its canonical, every alternative mobile version must point to the desktop (unless you are using a pure responsive design, in which case there is only one URL). Omissions create unwanted indexing and dilute ranking.

How to check that Google respects your directives?

Use the coverage report in Search Console to list indexed URLs. Filter by page type (AMP, mobile, desktop). If you see indexed AMP URLs while you have set canonicals to the desktop, either the tags are incorrectly coded, or Google is ignoring them (which happens if the primary version is inaccessible or very slow).

Also test with the URL inspection tool: submit an AMP page and check that Google correctly detects the canonical to the primary version. If the canonical declared by Google differs from the one you have coded, check for multiple or contradictory canonical tags in the HTML.

• Audit all URL variants (desktop, mobile, AMP, PWA) and document their roles
• Designate the primary version and implement canonicals from all other versions
• Add alternate amphtml tags on the primary version if using AMP
• Test each page with the Search Console inspection tool to validate canonical detection
• Monitor the coverage report for unwanted indexing
• Avoid loops or chains of redirection in canonical URLs