Should you really configure the AMP page as the mobile URL with a reverse canonical?

Why does Google recommend treating AMP as the main mobile version?

Mueller's statement is based on a logic of mobile-first architecture. Since Google prioritizes indexing mobile versions, it makes sense to define AMP as the canonical mobile variant. The rel="canonical" then points to the desktop version, creating an inverted parent-child relationship compared to traditional schemas.

This setup avoids conflicting signals that Google might receive if AMP were treated as just another alternative variant. By clearly designating AMP as the mobile version, we simplify the site's structural understanding for crawlers. This is particularly relevant for sites with three versions: desktop, mobile responsive, and AMP.

How does this approach differ from traditional setup?

Traditionally, the main desktop page contains a rel="amphtml" pointing to the AMP, while the AMP references a canonical to the desktop. This structure indicates that the desktop is the reference version. Mueller suggests reversing this hierarchy by positioning AMP as an independent mobile version.

The distinction is subtle but important for mobile-first indexing. If Google is primarily indexing via the mobile version, it’s better that this version is clearly identified as AMP rather than a regular responsive version. This avoids diluting signals between two competing mobile versions.

Is this recommendation still relevant with the decline of AMP?

AMP has lost its status as a preferred ranking factor after Google abandoned the lightning bolt badge and AMP-first in mobile results. Core Web Vitals have replaced AMP as a performance criterion. However, some publishers maintain their AMP pages for speed or existing infrastructure reasons.

If you still use AMP, this setup remains technically valid. But the strategic question becomes: should you still invest in AMP? Most sites have migrated to optimized responsive solutions. Mueller's advice applies, therefore, to an increasingly narrow scope of legacy sites or publishers facing specific constraints.

• AMP should be configured as the main mobile variant if it is maintained
• The rel="canonical" from AMP points to the desktop version, not the other way around
• This structure clarifies the hierarchy for mobile-first indexing
• AMP is no longer a direct ranking factor, making this setup less strategic
• Sites with three versions (desktop, responsive, AMP) must determine which mobile version to prioritize

Is this recommendation consistent with observed practices in the field?

The setup proposed by Mueller is technically consistent with mobile-first indexing, but it poses a major practical problem: it unnecessarily complicates the architecture for marginal benefit. In practice, the majority of high-performing sites have abandoned AMP in favor of optimized responsive pages with good Core Web Vitals.

The rare sites now using AMP generally utilize the traditional setup (desktop canonical, AMP as a variant via rel="amphtml") without facing penalties. Google manages this traditional structure very well. [To be verified]: no public data demonstrates that reversing the canonical to the desktop improves crawling or ranking. This recommendation seems more theoretical than practical.

What risks does this reverse configuration present?

Configuring the canonical from AMP to the desktop creates an unusual asymmetry that some CMS and SEO tools may misinterpret. Automated audits might potentially signal canonical errors, even if the setup is technically correct according to Google. This generates noise in reports and complicates maintenance.

More problematic: if your responsive mobile version is well optimized, why force Google to index AMP? You lose control over which mobile version gets indexed. Many sites have limited functionality in AMP (forms, interactivity, tracking) that they would prefer in the responsive version. Forcing AMP as the main mobile version might degrade the indexed user experience.

In what cases does this configuration really justify itself?

This approach makes sense if your AMP is objectively superior to your mobile responsive version in terms of speed and user experience. This is rare, but some large publishers have heavy responsives and ultra-optimized AMPs. In this case, it is better for Google to index the best version.

Another case: sites with technical constraints that prevent optimizing the responsive but have a mature AMP infrastructure. Rather than maintaining two mediocre mobile versions, it’s better to clarify that AMP is the reference version. Let's be honest: this scenario concerns less than 5% of sites today.

What actions should be taken if AMP pages are maintained?

The first step is to audit your current architecture. Check if your AMP is configured as a variant (rel="amphtml" from the desktop) or in a reverse canonical. Most sites use the former approach. If your mobile performance is stable, changing this setup is probably not a priority.

If you decide to adopt Mueller's recommendation, modify the rel="canonical" in the header of your AMP pages to point to the desktop version. Ensure that the desktop page does not have a canonical pointing to AMP, otherwise, you create a loop. Test on a few pilot pages before rolling it out widely.

What mistakes should be avoided during this reconfiguration?

The classic mistake is to forget to remove or modify the rel="amphtml" on the desktop side. If the desktop points to the AMP AND the AMP has a canonical to the desktop, Google will receive conflicting signals. It might arbitrarily choose which version to index, creating instability in mobile results.

Another trap: configure this structure when your AMP has truncated or limited content compared to the responsive. If Google indexes AMP as the main mobile version, mobile users might see a potentially stripped-down version. Ensure that your AMP provides an equivalent or superior experience before promoting it as the canonical mobile.

How to verify that the configuration is correct?

Use the URL inspection tool in Search Console to test both the desktop version and the AMP. Google should recognize AMP as the mobile version and display the canonical pointing to the desktop. Also, check that the mobile rendering correctly uses AMP, not the responsive.

Monitor the metrics in Search Console, especially mobile impressions and clicks. If you notice a drop after reconfiguration, it may be that Google preferred your responsive. In that case, consider reverting to the traditional configuration or, better yet, abandoning AMP entirely if your responsive can be optimized.

• Audit the current canonical architecture between desktop, mobile responsive, and AMP
• Verify that AMP offers a user experience equivalent to or better than the responsive
• Modify the rel="canonical" of AMP to point to the desktop (not the other way around)
• Test the configuration on a sample of pages before complete deployment
• Monitor Search Console for 2-3 months to detect any mobile volatility
• Document the strategic reasons for maintaining AMP rather than migrating to optimized responsive