Can you really audit the complete indexing of your AMP pages in Google?

What exactly does Google say about the visibility of indexed AMP pages?

Google confirms that there is no dedicated interface to individually list the AMP pages present in the index. Search Console only displays a total number of indexed AMP pages, without details on the specific URLs.

This limitation contrasts with traditional coverage reports, which allow page-by-page exploration of indexing issues. For AMP, you know how many pages are indexed, but not which ones or why some are missing.

Why does this lack of granularity pose a problem?

An SEO needs to concretely verify which AMP versions are indeed in the index, especially after a deployment or migration. Without a detailed list, it's impossible to quickly spot that an entire category of AMP pages is not indexed.

You find yourself needing to cross-reference several sources: server logs, Google Analytics, manual comparisons with site: and inurl: queries. This turns an audit that should take 10 minutes into an investigation that takes several hours.

What alternative methods are available?

To bypass this limitation, you can use advanced search operators in Google (for example, site:yourdomain.com/amp/), but the results are incomplete and unreliable on a large scale.

Server logs can help identify Googlebot crawls on AMP URLs, which provides indirect indication. But crawling does not mean indexing. Some third-party tools attempt to reconstruct a partial view by cross-referencing Search Console API data and simulated crawls, without a guarantee of completeness.

• Search Console displays a global count, without URL detail
• No equivalent to the traditional coverage report for AMP pages
• Incomplete site: operators and unreliable for a comprehensive audit
• Server logs and third-party tools remain the only options to reconstruct a partial view
• Crawl does not guarantee indexing, hence the difficulty in validating the true status

Is this limitation consistent with Google's AMP strategy?

Google has always marketed AMP as a technical simplification for publishers. However, the lack of granular monitoring tools contradicts this promise. In practice, many SEOs observe that Google seems to have stopped investing in the AMP ecosystem since Core Web Vitals replaced AMP as a performance criterion.

This statement from John Mueller feels more like an admission than a confirmed feature. Google is not saying 'we are working on it'; they are simply noting that the tool does not exist. [To be verified] whether this absence is a technical choice or a sign that AMP is no longer an internal priority.

What nuances should be added to this statement?

Mueller mentions "direct visualization," which implies that there are indirect methods. In practice, these methods are tedious and unreliable. The Search Console API allows querying the indexing status URL by URL, but at a rate of a few requests per second, auditing 10,000 AMP pages takes hours.

Some also observe that the global count displayed in Search Console does not always match the actual number of AMP pages crawled in the logs. Discrepancies of 15 to 30% have been noted across several e-commerce sites, with no official explanation from Google.

In what scenarios does this lack of tools become critical?

For a site with a few dozen AMP pages, the problem remains manageable. But for a media outlet with thousands of articles or an e-commerce site with AMP product listings, the lack of visibility becomes a major operational hindrance.

If you manage both AMP and non-AMP versions in parallel, you must be able to verify that Google correctly indexes the desired canonical version. Without a detailed report, you are flying blind and risk situations where the AMP version is indexed while you have removed the format, or vice versa.

What should you do to monitor AMP indexing effectively?

Set up a regular monitoring of the global count in Search Console. Track the weekly changes to quickly identify abnormal drops. Simultaneously, configure an automated export of server logs to identify Googlebot crawls on your AMP URLs.

Use the Search Console API to query the indexing status of a representative sample of AMP pages (for example, 5% of your portfolio). This will give you a partial yet actionable view. Cross-reference this data with your analytics to identify AMP pages that generate traffic without being officially indexed according to the API.

What mistakes should you avoid in monitoring AMP pages?

Do not rely solely on site: operators to count your indexed AMP pages. These queries are notoriously inaccurate and can yield fanciful results, especially on large sites. Google itself advises against relying on site: for professional audits.

Also, avoid assuming that a crawled page is automatically indexed. Server logs show Googlebot visits, but between crawling and indexing, there is a quality filter that Google never details. A page can be crawled 50 times without ever entering the index if Google deems it of low added value.

How can you check if your AMP strategy is still relevant?

Analyze the actual contribution of AMP pages to your organic traffic. If they account for less than 5% of your sessions and you no longer gain a boost in Top Stories, reconsider the relevance of maintaining this infrastructure.

Compare the Core Web Vitals performance of your AMP pages against non-AMP pages. Since Google removed the AMP badge and Core Web Vitals became a ranking criterion, many sites achieve better performance with optimized standard pages than with AMP. If your standard pages meet CWV thresholds, AMP becomes a technical burden.

• Monitor the weekly changes in the global AMP count in Search Console
• Set up an automated export of server logs to track Googlebot AMP crawls
• Query the Search Console API on a sample of 5 to 10% of AMP URLs
• Cross-reference Search Console data, logs, and analytics to detect inconsistencies
• Compare CWV performance between AMP and non-AMP pages to validate the format's relevance
• Never use the site: operator as the sole source of truth regarding indexing