Should you really let users know that they are on an AMP page?

Why does Google ask for transparency on AMP pages?

Google's recommendation is not trivial. It implicitly acknowledges that the AMP experience can confuse users. When a user clicks on a Google result and lands on an AMP page, they often find themselves on a cache.google.com or google.com/amp domain, with a truncated URL and limited features.

This ambiguity creates confusion. The user no longer knows if they are on the original site or a simplified version. Share buttons can generate AMP URLs instead of the canonical address, forms do not always function as expected, and some JavaScript functionalities are limited. Therefore, Google asks webmasters to explicitly signal this transition.

What does this really change for the UX?

An informed user is a user who stays. If someone arrives on your AMP page without understanding why the design differs or why certain interactions fail, the bounce rate mechanically increases. The visitor clicks on “back” and looks elsewhere.

Google suggests adding a visible link to switch to the full HTML version. This is not just a matter of courtesy: it’s a safety net for your engagement metrics. A user who consciously chooses to stay on AMP (because it’s faster) or to switch to the standard site (because they want more features) is making an informed decision. Result: less frustration, better time on site.

Does this recommendation carry algorithmic weight?

Google phrases it as a UX recommendation, not as a direct ranking criterion. But let’s be honest: UX impacts ranking. If your AMP pages generate massive bounces because no one understands where they are, the behavioral signals degrade.

No official documentation states “you will be penalized if you do not indicate that a page is in AMP.” On the other hand, Core Web Vitals and engagement metrics matter. Confusing navigation sabotages these indicators. Indirectly, this recommendation protects your visibility.

• Clearly indicating the presence of AMP reduces confusion and improves engagement signals
• Providing a link to the standard version offers a way out for frustrated users
• The algorithmic impact is indirect: no direct penalty, but degraded behavioral metrics if the UX is poor
• Complex forms and interactions remain a weak point of AMP, hence the importance of this transparency
• Google implicitly acknowledges that the AMP experience is not always equivalent to the full version

Is this statement consistent with the evolution of AMP?

Yes, and it’s even revealing. When AMP was launched, Google presented it as the miracle solution for mobile. Today, this recommendation admits that AMP can disrupt the user to the extent that they need to be explicitly warned. It’s an acknowledgment: AMP is not always transparent.

Since Core Web Vitals replaced AMP as the primary criterion for mobile, AMP’s strategic interest has waned. Google no longer promotes AMP as it once did. This recommendation is made in a context where AMP is becoming optional, not mandatory. If you need to inform users that they are on AMP and offer an exit, it is because the experience is not entirely satisfying.

What are the risks if you ignore this recommendation?

The risk is not a harsh algorithmic penalty. It is a slow erosion of your engagement metrics. Users landing on AMP without understanding what is happening will bounce faster. They will share AMP URLs instead of your canonical URLs, diluting your domain authority.

Some e-commerce sites have observed higher cart abandonment rates on AMP when checkout forms were poorly implemented. If the user does not know they are on a simplified version and a feature fails, they leave. Worse: they do not return because they think your site is broken, not that they are on AMP. [To be verified]: Google has never published quantitative data on the impact of not indicating AMP, but field observations show a clear correlation.

In what cases does this rule not really apply?

If your AMP site is almost identical to your standard version in terms of design and features, the indication becomes less critical. Some publishers have succeeded in creating AMP pages so close to their standard HTML that the user sees no difference. In this case, indicating “you are on AMP” may even seem superfluous.

Another case: purely editorial sites without complex interactions. A minimalist blog that offers only text and images does not need a large disclaimer. AMP UX and standard UX converge. However, as soon as there are forms, dynamic comments, third-party widgets, or custom JavaScript, the difference becomes noticeable. This is where transparency counts.

What should you do concretely on your AMP pages?

Start by adding a clear visual indication at the top of each AMP page. This could be a small discreet banner: “Light version for fast loading.” No need for an alarmist message, just neutral information. The goal is for the user to know where they are.

Next, integrate a link to the standard version. Place it in the same banner or in the footer. The link should point to the canonical URL, not to a redirect or intermediate URL. Test this link from different devices: some AMP caches may block poorly configured redirects. The visitor should be able to switch with one click, without friction.

What mistakes to avoid during the implementation?

Classic mistake: hiding the AMP indication on mobile thinking it clutters the screen. It’s precisely on mobile that the user needs this information, as this is where AMP kicks in. Do not sacrifice clarity to gain 20 pixels.

Another pitfall: using a link to the standard version that only works in JavaScript. AMP limits JavaScript, and some caches disable external scripts. If your “view the full version” button relies on non-AMP JS, it will not work. Use a good old pure HTML link, with a classic ``. Simplicity is key.

How to check that your AMP pages comply with this recommendation?

Test your AMP pages in real conditions. Search for your articles via Google on mobile and click on the AMP results. Check that the indication and link are clearly visible, not hidden in a corner or buried in the content. Ask someone who is unfamiliar with your site to do the same test: if they do not immediately understand they are on AMP and how to return, it’s a failure.

Also monitor your metrics in Google Analytics. Compare the bounce rate and time on site of AMP pages vs. standard pages. If the gap is significant, it often signals that the AMP experience is problematic. A high bounce on AMP without clear indication suggests that users are leaving out of frustration, not disinterest in the content.

• Add a banner or visible message indicating that the page is in AMP version
• Integrate a pure HTML link (not JS) to the standard canonical URL
• Test this link on different devices and from the Google AMP cache
• Ensure that the AMP indication is visible on mobile, not hidden by responsive design
• Compare engagement metrics of AMP vs. standard in Analytics
• Avoid complex redirects or JS links that do not work in AMP