Should you really index all your AMP pages for them to be cached by Google?

Why does Google place such emphasis on indexing AMP pages?

The Google AMP cache can only store content accessible to its crawler. If you place a noindex on an AMP page, Googlebot treats it like any other non-indexable page: it is not crawled regularly, it is not cached, and it does not benefit from ultra-fast delivery via Google's CDN.

The AMP cache is an optimized content distribution system that preloads pages and serves them from Google's servers. This infrastructure reduces latency, improves loading times, and facilitates instant display in certain mobile contexts. Without indexing, you lose that advantage.

Does this rule apply to all AMP pages or just to some?

Google is referring to AMP pages whose content “must be visible and used in search results”. If your strategy is to duplicate each article in AMP format to benefit from the cache, then yes, those pages must be indexable.

However, if you have testing, staging, or transitional AMP pages that you do not wish to see appear in SERPs, the noindex remains relevant. Google does not say that all AMP pages must be indexed, it states that those you want to see in the results must be.

What is the difference between indexing and AMP caching?

Indexing means that Google knows your page and can rank it in its results. AMP caching is an additional process that stores a copy of your page on Google's servers for faster delivery.

Without indexing, there is no caching. But the reverse is not always true: a page can be indexed without going through the AMP cache if it is not in valid AMP format or if Google chooses not to cache it for other technical reasons.

• An AMP page with noindex will neither be crawled regularly nor cached.
• AMP caching improves loading speed but does not guarantee a better ranking.
• Core Web Vitals now assess actual performance, not just the page format.
• If you use AMP only for certain types of content (articles, product sheets), only those pages need to be indexable.
• Staging or development AMP pages should remain in noindex, just like any other test page.

Does this statement still reflect the reality of current mobile SEO?

Let’s be honest: AMP has lost much of its strategic interest since Google integrated Core Web Vitals as a ranking factor. Previously, AMP was a shortcut to obtaining a "fast" badge and being featured in the Top Stories carousel. Today, any well-optimized site can achieve the same performance without duplicating its content.

Google's statement remains technically accurate: if you maintain AMP versions, they must be indexable to be cached. But is it still relevant to maintain AMP? For many sites, the answer is no. The cost of maintenance, issues with duplicate content, and limitations in design and interactivity are no longer justified.

What are the risks of unintentionally leaving AMP pages in noindex?

The main risk is fragmenting your indexing. If you have a standard canonical version and an AMP version in noindex, Google may choose to index the standard version even if you would prefer it to display the AMP version in certain contexts. You lose control over the mobile display.

Another issue: if your canonical tags point to the AMP version and that version is in noindex, you create an inconsistency that Google will have to resolve for you. It will likely choose to ignore your canonical and index the version it finds most relevant. This is not ideal for SEO consistency. [To verify]: Google does not release any data on how often these decisions take place or their actual impact on ranking.

Should you still invest in AMP for SEO?

For most sites, no. Modern frameworks (Next.js, Nuxt, SvelteKit) allow for excellent performance without going through AMP. Progressive Web Apps (PWAs) offer a comparable or even superior mobile experience with more flexibility.

AMP remains relevant in specific cases: news sites with massive mobile traffic, simple editorial content without the need for complex interactivity, and sites whose technical infrastructure makes it difficult to optimize for Core Web Vitals. But for e-commerce, standard B2B sites, or a classic corporate blog? The effort no longer seems worth it.

What should you do if you already have AMP pages in production?

Start with an audit of your AMP pages. How many do you have? What portion of your organic traffic passes through these versions? Use Search Console to identify indexed AMP pages and compare their performance (impressions, clicks, CTR) with the standard versions.

If your AMP pages generate less than 10% of your mobile traffic, ask yourself: is it worth maintaining this infrastructure? The cost of development, maintenance, and AMP validation could be redirected towards optimizing Core Web Vitals on your main site.

How do you check that your AMP pages are correctly indexable?

Inspect your AMP pages in Search Console using the URL Inspection tool. Ensure that the indexing status is "URL is present in Google" and that the live crawl test does not encounter any noindex tags. Also, check your robots.txt files to make sure no directive blocks access to AMP resources.

Next, validate your canonical tags. If the AMP version is the preferred version, the canonical tag of the standard page should point to the AMP. If it’s the other way around, the canonical of the AMP should point to the standard version. Any inconsistency here creates confusion for Googlebot and dilutes your link equity.

What strategy should you adopt for new projects?

For a site launch, forget AMP. Focus on a single well-optimized site that meets Core Web Vitals: LCP under 2.5 seconds, FID under 100 ms, CLS under 0.1. Use high-performance hosting, a CDN, smart lazy loading, and compress your resources.

If your sector is ultra-competitive on mobile and your competitors are still using AMP, test an AMP version on a sample of pages to compare performance. But do not generalize until you have clear evidence that it brings measurable gains in traffic or conversions. [To verify] : no recent public study shows a clear SEO advantage of AMP compared to a well-optimized mobile site.

• Audit your existing AMP pages and measure their actual contribution to organic traffic.
• Check in Search Console that your AMP pages are not accidentally in noindex.
• Ensure consistency of your canonical tags between AMP and standard versions.
• If you maintain AMP, regularly test the validity of your pages using the official AMP tool.
• Compare the Core Web Vitals of your AMP pages with your standard pages to identify the best option.
• Clearly document your AMP strategy to avoid configuration errors during updates.