Does Google really treat AMP Cache URLs as original URLs for ranking?

What does this URL substitution by Google mean?

When Google crawls a page in AMP Cache, it records the original URL in its ranking indexes. The AMP cache hosts a copy of your content on cdn.ampproject.org or google.com/amp, but Google attributes ranking signals to your source domain.

This mechanism aims to prevent publishers from losing PageRank or authority when their AMP content is served from a third-party CDN. In theory, a link to cdn.ampproject.org/s/yoursite.com/article is treated as a direct link to yoursite.com/article.

Why is Google highlighting this point now?

This statement addresses a persistent confusion among SEOs. Many believed that backlinks to cache URLs diluted link equity or created duplicate content harmful to rankings.

Google clarifies that its algorithm performs this URL normalization internally. Popularity metrics, link anchors, and trust signals are redirected to your site's canonical URL, not to the cache.

Does this substitution apply to all SEO signals?

Google explicitly mentions ranking calculations, which includes inbound link signals. The question remains open for other dimensions: engagement metrics, behavioral signals, Core Web Vitals data measured on the cache.

The AMP specifications include a fallback system that allows the browser to switch to the original URL in certain contexts. Google likely utilizes this mechanism to consolidate signals, but the technical details remain opaque.

• AMP cache URLs are replaced with original URLs in the ranking index
• Backlinks to an AMP cache pass their authority to the source domain
• This substitution prevents dilution of PageRank between your site and the CDN
• The statement covers ranking but remains vague on other signals (UX, engagement)

Is this statement consistent with field observations?

Most SEO audits actually show that AMP pages do not lead to cannibalization of organic traffic between the AMP version and the standard version. Backlinks to AMP caches rarely appear in third-party tools like Ahrefs or Majestic, suggesting either a normalization on Google's side or invisibility to external crawlers.

However, several use cases reveal inconsistencies. Some sites have noted ranking fluctuations when links pointed heavily to cache URLs rather than original URLs. [To verify]: Does Google apply this substitution only for official AMP Project caches, or also for third-party CDNs implementing AMP?

What nuances should be added to this claim?

Google refers to “links to AMP caches” without specifying if this includes social shares, non-clickable citations, or temporary 302 redirects from a cache. The devil is in the details of implementation.

Moreover, this substitution does not solve the issue of brand visibility. A user sharing an AMP Cache URL on social media spreads a google.com URL, not your domain. Technical SEO may be preserved, but the branding impact remains negative. Publishers lose control over the URL displayed in browsers and shares.

In what cases might this rule not apply?

Orphaned AMP pages (without a canonical HTML version) raise questions. If your content exists solely in AMP and is hosted only on a cache, can Google really substitute to a non-existent original URL? Logic would suggest not.

Another gray area is dedicated AMP subdomains. Some publishers serve their AMP pages on amp.example.com rather than example.com/amp/. Does Google treat these configurations as third-party caches or as original URLs? The statement remains silent on this.

What should you check on your current AMP pages?

Start by auditing your canonical tags. Every AMP page must point to its standard HTML version via a <link rel="canonical"> tag. Conversely, the HTML page should declare the AMP version via <link rel="amphtml">. This reciprocity helps Google consolidate signals.

Also, verify that your AMP pages comply with the official specifications using the AMP validator. A technically invalid page risks not benefiting from this URL substitution, and Google may treat it as distinct content.

What mistakes should be avoided in your AMP strategy?

Never create exclusive content in AMP without an HTML equivalent. If your article only exists on the AMP cache, you lose control of the canonical URL, and Google has nothing to substitute signals to.

Also, avoid blocking third-party AMP caches in your robots.txt. Some publishers blacklist cdn.ampproject.org thinking they can avoid duplicate content, while Google actually needs access to these caches to perform normalization.

How can you optimize the transmission of popularity through AMP?

If you are obtaining backlinks to AMP cache URLs, document them in your link tracking. Even if Google claims to account for them, a direct link to your domain is always preferable for brand visibility and traceability in third-party SEO tools.

Consider gradually migrating to alternative solutions like Signed Exchanges (SXG). This technology allows serving content from a CDN while displaying your URL in the address bar, thereby solving the branding issue without sacrificing performance.

• Audit all canonical/amphtml tags to ensure consistency
• Technically validate each AMP page with the official tool
• Check that the robots.txt does not exclude legitimate AMP caches
• Monitor backlinks to cache URLs in your link profile
• Evaluate a migration to Signed Exchanges to regain control of displayed URLs
• Avoid any AMP exclusive content without a canonical HTML version