Should you link your AMP pages together or redirect to the standard mobile versions?

Why does Google give webmasters this choice?

This statement from Mueller reveals that Google does not technically favor any approach for managing links on AMP pages. The engine can handle both an AMP-to-AMP linking structure as well as a redirect to traditional mobile versions.

In practical terms, this means that the link architecture among your AMP pages is a strategic choice for your site, not a technical obligation for crawling or indexing. Google simply follows the links present and interprets the structure you provide.

What is the only technical constraint imposed?

The restriction mentioned by Mueller concerns internal navigation. Links must necessarily point to pages belonging to the same site, without redirecting the user to an external domain.

This rule aims to ensure a consistent user journey and to avoid visitors inadvertently leaving your ecosystem. For Google, the key is that navigation signals remain traceable within the same domain to accurately analyze the site's structure.

How does Google interpret these two approaches differently?

A pure AMP-to-AMP linking theoretically creates a subgraph of pages in Google's index. PageRank and authority signals then circulate within this parallel ecosystem, with its own internal depth and popularity metrics.

In contrast, systematic redirection to standard mobile versions centralizes all signals on a single set of pages. This approach avoids the potential dilution of PageRank between two versions of the same page, but can complicate technical management if the redirections are not perfectly configured.

• Google neither penalizes nor favors either of the two link architectures for ranking
• The only strict requirement: navigation links must remain internal to the domain
• An AMP-to-AMP structure creates a distinct subgraph in the index
• Redirections to standard mobile pages centralize authority signals
• The choice depends more on your content strategy than on measurable SEO benefits

Does this flexibility reflect Google's uncertainty about the future of AMP?

The neutrality displayed by Mueller on this technical subject can be interpreted as an admission: Google itself doesn't know which approach will best serve webmasters in the long run. This ambivalence contrasts with the usually decisive guidelines on other technical aspects (canonicals, hreflang).

Since the gradual decline of AMP as a differentiating ranking factor, this statement takes on particular significance. It suggests that Google sees AMP as a format among others, without expecting webmasters to build their entire link strategy around this technology. [To be verified]: no large-scale study shows measurable ranking impact between the two approaches.

Which approach should you favor based on your site's architecture?

For a site with a limited content volume and a simple structure, redirecting to standard mobile versions drastically simplifies maintenance. You avoid maintaining two parallel navigation trees and centralize popularity signals.

Conversely, a site with a massive catalog (e-commerce, news) can benefit from a pure AMP-to-AMP linking if the AMP pages provide a genuinely differentiated experience. This keeps the user in an ultra-fast conversion tunnel without interruption. But beware: this approach requires absolute consistency in internal linking to avoid dead ends.

Do systematic redirections pose crawl or dilution problems?

Redirecting each AMP link to the standard mobile version technically generates an additional leap for Googlebot. If your site contains thousands of AMP pages, this multiplies HTTP requests and can marginally impact the crawl budget on very large sites.

However, in practice, the impact remains negligible for the majority of sites. Well-configured 301 or 302 redirections pass PageRank without significant loss. The real risk lies elsewhere: misconfigured redirections (redirect chains, loops) can create indexing errors or content duplications.

How do you choose between pure AMP linking and redirection to mobile?

The decision rests on three criteria: content volume, navigation complexity, and maintenance resources. If you publish fewer than 500 pages per month and your structure remains linear, prioritize redirections to standard mobile to simplify management.

For news or e-commerce sites with thousands of AMP pages, an AMP-to-AMP linking structure becomes relevant if you have the resources to maintain a consistent navigation. Test first on a section of the site before generalizing and measure the impact on engagement metrics (bounce rate, pages per session).

What technical errors should be absolutely avoided?

The most common mistake is to mix the two approaches inconsistently. Some links point to other AMP pages, while others go to mobile versions, without apparent logic. This fragments navigation signals and complicates Google's interpretation of your site structure.

Another trap is forgetting to configure the canonical and amphtml tags in accordance with your linking strategy. If your AMP pages redirect to mobile versions but the canonicals point to desktop versions, you create a signal conflict that can confuse indexing. Also, ensure that your navigation links never point to external domains, even inadvertently through third-party scripts.

How do you audit the consistency of your current strategy?

Crawl your site with Screaming Frog or Oncrawl by enabling mobile mode to identify all outgoing links from your AMP pages. Sort them into three categories: links to AMP, to standard mobile, to desktop or external. If you find more than 10% of links outside of your stated strategy, you have a coherence issue.

Next, analyze the server logs to identify redirect chains or loops. A tool like Botify or Oncrawl Log Analyzer can automate this detection. Finally, compare performance in the Search Console: do AMP pages have a different click-through rate or average position based on whether they link to AMP or mobile? This data will guide you in refining your choice.

These technical optimizations require specialized expertise and tools. If your team lacks resources or if the audit reveals complex structural inconsistencies, hiring a specialized SEO agency can save you months of trial and error and secure your migration or redesign.

• Define a unique linking strategy (pure AMP OR redirection) and apply it without exception
• Audit all outgoing links from AMP pages with a crawler configured in mobile mode
• Verify coherence between links, canonicals, and amphtml tags on a representative sample
• Monitor server logs for redirect chains or loops
• Test impact on engagement metrics (pages/session, time on site) before generalizing
• Document the chosen strategy for technical and editorial teams