Does AMP really redistribute mobile traffic without generating more?

Is AMP a traffic growth lever or just a redistributor?

John Mueller's statement cuts through a persistent misconception: implementing AMP does not generate extra traffic. What Google clearly states is that the overall number of visitors remains the same. The only thing that changes is the distribution among your different page versions.

How does this work in practice? If you receive 10,000 mobile visitors per month on your site, activating AMP will not bring you 11,000. Those 10,000 visitors will simply be redirected to your AMP pages instead of your standard mobile pages, on devices that support them. The total traffic remains constant; only the final destination changes.

What devices trigger this preference for AMP?

Google refers to AMP-compatible devices, a deliberately vague term. In practice, this mainly concerns modern smartphones and tablets using Chrome or Google mobile search. Desktop browsers are generally not affected by this preference.

This compatibility is not binary. Some devices will systematically display the AMP version when it exists, while others will switch depending on the search context or connection quality. Google does not publish a comprehensive list of affected devices, which makes auditing difficult.

Why does this redistribution impact your analytics?

The first visible effect is in your measurement tools. Your analytics will show a drop in traffic on standard mobile URLs and a proportional increase on AMP URLs. This migration can skew your historical comparisons if you do not segment correctly.

Technically, AMP pages often use distinct URLs (with /amp/ or ?amp=1), creating apparent duplicates in your reports. You need to set up consolidated views to avoid counting the same user twice or misinterpreting traffic curves.

• AMP does not generate additional traffic: it redistributes existing mobile traffic to a different technical version
• The preference activates only on compatible devices: mainly modern smartphones and tablets on Chrome
• Significant analytics impact: apparent drop in standard mobile traffic compensated by an increase in AMP, with no change in total
• Essential segmentation: configure your tools to group standard mobile and AMP in your historical analyses
• No direct SEO benefit: the volume of organic clicks remains the same; only the page format differs

Does this statement truly reflect what we're seeing on the ground?

Mueller's position is consistent with observations from most sites that have implemented AMP. Case studies indeed show a redistribution of traffic rather than pure growth. However, some publishers report indirect gains related to featured snippets or Top Stories carousels that historically favored AMP.

The problem is that Mueller oversimplifies. There are scenarios where AMP can indirectly increase traffic: better click rates due to the lightning bolt badge (now gone), preferred positioning in certain SERP formats, or improved bounce rates that boost overall ranking. These side effects are not mentioned.

What nuances should we consider regarding this claim?

First point: this statement dates back to a time when AMP was still a ranking criterion for certain SERP features. Since then, Google has considerably softened this preference. Core Web Vitals have replaced AMP as a mobile performance signal, making the technology less strategic than before.

Second nuance: saying that AMP does not generate more traffic implies that your standard mobile pages offer the same user experience. If your mobile site is slow, poorly optimized, or hindered by third-party scripts, AMP may indeed improve engagement and indirectly benefit SEO. [To be verified]: Mueller does not clarify whether this neutrality also applies to sites with poor basic mobile performance.

In what cases does this rule not fully apply?

News sites represent a special case. For years, access to the Top Stories carousel was conditional on AMP. In this specific context, implementing AMP could generate additional traffic by unlocking a SERP feature otherwise inaccessible. This dependency has been lifted, but some publishers still observe a residual preference.

Another exception: sites with limited technical resources. If your team cannot properly optimize standard mobile, AMP can serve as a shortcut to better performance. In this case, the traffic gain comes from improving UX, not from AMP itself. It's a band-aid, not a lasting solution.

Should you still invest in AMP today?

The short answer: probably not, except in very specific cases. If you haven't implemented AMP yet, focus on optimizing your standard mobile site through Core Web Vitals. Google has clearly deprioritized AMP as a ranking signal, and the technology no longer provides the SERP benefits it offered a few years ago.

If you already have AMP in production, the question is different. Decommissioning AMP may create temporary disruptions in your analytics and potentially affect some positions if your standard mobile is not up to par. Audit your standard mobile performance first before making a decision.

How can you verify the real impact of AMP on your traffic?

In Google Analytics, create a custom segment isolating AMP traffic (filter by /amp/ in the URL or use a UTM parameter if you have set one up). Compare the volume of AMP sessions with total mobile traffic over a recent period. If AMP represents less than 10% of mobile and your Core Web Vitals are good, the impact of its removal will be minimal.

Also check Search Console: view the Performance report and filter by URLs containing /amp/. Compare impressions, clicks, and CTR between AMP and non-AMP pages. If the metrics are similar, that confirms that AMP does not provide you with any measurable visibility advantage.

What mistakes should you avoid when managing AMP?

The classic mistake: maintaining incomplete or buggy AMP pages due to lack of resources. A poorly implemented AMP page (truncated content, missing images, broken scripts) provides a degraded experience that harms your brand. If you cannot maintain AMP properly, it is better to abandon it.

Another pitfall: neglecting the canonicalization between mobile and AMP. Each AMP page must point via rel=canonical to its standard mobile version. Conversely, the mobile version must also point to AMP with rel=amphtml. A mistake here and Google may index the wrong versions or dilute your ranking signals.

• Audit your mobile Core Web Vitals: if your standard mobile is already in the green, AMP adds no value
• Segment your analytics to isolate AMP traffic and measure its real weight in your mobile mix
• Verify the bidirectional canonicalization between mobile and AMP to avoid index duplication
• Regularly test your AMP pages with the Google validation tool to detect errors and degradation
• If you decommission AMP, implement 301 redirects to the mobile URLs to preserve link equity
• Document the traffic distribution before and after any AMP changes to measure the actual impact