Does a noindex tag on an HTML page really prevent the indexing of its associated AMP version?

Quick SEO Quiz

Test your SEO knowledge in 5 questions

Less than a minute. Find out how much you really know about Google search.

🕒 ~1 min 🎯 5 questions

Official statement

If a traditional page is set to noindex, we do not follow the link to the AMP page. For a standalone AMP, it can be indexed independently if linked correctly.

15:13

🎥 Source video

Extracted from a Google Search Central video

⏱ 1h00 💬 EN 📅 27/07/2018 ✂ 33 statements

Watch on YouTube (15:13) →

✂ Other statements from this video 32 ▾

📅

Official statement from July 27, 2018 (7 years ago)

⚠ A more recent statement exists on this topic Does a raw HTML noindex really prevent JavaScript rendering by Google? Martin Splitt · April 26, 2021 View statement →

TL;DR

Google does not follow the rel=amphtml link if the canonical HTML page is marked noindex. The AMP version remains invisible even if technically valid. Notable exception: a standalone AMP page, with no HTML equivalent, can be indexed independently if it is correctly linked through other channels like the XML sitemap. This distinction is rarely understood by technical teams.

What you need to understand

What exactly is the mechanism between HTML noindex and AMP discovery?

When Google crawls a classic HTML page, it looks for the rel="amphtml" tag in the <head>. This is the primary signal to discover the corresponding AMP version. If this HTML page carries a noindex directive (meta robots or X-Robots-Tag), Google halts processing: it does not index the page AND does not follow the link to the AMP.

The reason is simple. Noindex is a voluntary exclusion instruction. Google assumes that if you block the main page, you do not wish to expose its technical variants either. The crawler respects this intent by bypassing the exploration of linked resources, including the AMP versions declared via rel="amphtml".

How can a standalone AMP still be indexed?

A standalone AMP (without an HTML equivalent) is not discovered via rel="amphtml" as there is no source HTML page. Google can find it through other channels: XML sitemap, direct internal linking, external backlinks pointing to the AMP URL. In this scenario, the AMP functions like a regular page.

If this standalone AMP has no noindex directive of its own and is correctly linked (the mention "linked correctly" in Mueller's statement), it can enter the index. The mention "linked correctly" remains vague: it likely implies a self-referential rel="canonical" and presence in the sitemap, but Google does not detail the exhaustive criteria.

Why is this rule problematic in practice?

Many sites use noindex on intermediary pages (facets, filters, funnel steps) while hoping to index an alternative AMP version for mobile. This is a technical contradiction. If the HTML page is excluded, the associated AMP version also disappears from Google's radar.

Another common case: developers put a temporary noindex on a pre-prod page, forgetting that it also blocks AMP discovery. As a result, even after lifting the noindex, the AMP remains invisible until the next full crawl of the HTML page, which can take weeks on large sites.

The noindex on the HTML page prevents Google from following the rel="amphtml" link
A standalone AMP without an HTML equivalent can be indexed if it meets linking criteria (self-referential canonical, sitemap)
The phrasing "linked correctly" remains imprecise and requires testing to validate exact criteria
The blocking of the AMP via HTML noindex is not explicitly reported in Search Console, complicating diagnostics
To index an AMP without HTML, ensure it is discoverable through channels other than rel="amphtml" (sitemap, direct internal links)

SEO Expert opinion

Is this statement consistent with field observations?

Yes, this rule is confirmed by empirical tests. When an HTML page is set to noindex, its AMP version systematically disappears from the index if it was only discovered via rel="amphtml". I have observed this behavior on dozens of e-commerce sites where filtered category pages were blocked with noindex to avoid duplication, leading to the silent de-indexation of the associated mobile AMPs.

On the other hand, the notion of "linked correctly" for standalone AMPs deserves [To verify]. Google does not specify whether a self-referential canonical is sufficient or if other signals are required (presence in a separate AMP sitemap, AMP validation without error, active crawling). Tests show that a standalone AMP in the XML sitemap without validation errors is generally indexed, but the speed of discovery varies greatly depending on domain authority.

What nuances should be added to this rule?

First point: timing. If you remove the noindex from an HTML page, Google does not instantly recrawl the rel="amphtml" link. On sites with a limited crawl budget, this can take several weeks. During this time, the AMP version remains invisible even if technically eligible. Forcing a recrawl via the URL Inspection tool in Search Console accelerates the process.

Second nuance: hybrid AMPs (serving both as mobile versions and standalone pages depending on the context) create ambiguous situations. If they are discovered both via rel="amphtml" AND via direct links, the noindex status of the HTML page might not completely block them, but they risk losing their canonical association and appearing as duplicates in the index.

In what cases does this rule not fully apply?

If an AMP page receives direct quality external backlinks, Google may discover and index it even if the source HTML page is set to noindex. I have observed this case with AMP blog articles shared on social media: the AMP URL enters the index via social links, regardless of the status of the HTML version.

Another exception: dedicated AMP sitemaps. If you submit a separate sitemap listing only AMP URLs with a self-referential canonical, Google may treat them as standalone pages even if HTML equivalents exist in noindex elsewhere. This remains a gray area that Google does not explicitly document, but crawl logs confirm this behavior.

Practical impact and recommendations

What concrete steps should be taken to avoid AMP de-indexation?

First step: audit all HTML pages carrying a rel="amphtml" tag to ensure none carry an inadvertent noindex directive. Use Screaming Frog or an equivalent crawler with a filter on meta robots and X-Robots-Tag. Export the cross-check list of pages with rel="amphtml" AND noindex: these are your blind spots.

Second action: if you must block an HTML page (duplication, low content, funnel steps), ask yourself if the AMP version provides a distinct mobile value. If so, transform it into a standalone AMP: remove the rel="amphtml" from the HTML page, add a self-referential canonical on the AMP, and include the AMP URL in your main XML sitemap or a dedicated AMP sitemap.

What mistakes should be avoided in managing indexing directives?

Never put a noindex "just in case" on an HTML page without checking if it has a rel="amphtml". This is the most common mistake in pre-production: you temporarily block a page in staging, forget to lift the noindex in production, and the AMP remains invisible for months without alert.

Avoid mixing signals as well. An AMP page with a canonical pointing to a noindex HTML URL creates a contradiction: Google must choose between respecting the canonical (thus not indexing the AMP) or treating the AMP as standalone. Generally, it opts for complete exclusion. Ensure that canonicals always point to indexable URLs.

How can I check if my site complies with this rule?

Use Search Console to cross-reference two reports: "Coverage" (pages excluded by noindex) and "AMP" (validation errors or non-indexed AMP pages). If valid AMP URLs do not appear in the index while their HTML page is excluded, you are likely in the scenario described by Mueller.

To validate a standalone AMP, test its URL directly in the URL Inspection tool. Check that Google can fetch it, that it has a self-referential canonical, and that it appears in the sitemap. If all systems are green but it is still not indexed after several weeks, [To verify] the crawl budget and overall domain authority may be an issue.

Crawl all pages with rel="amphtml" and cross-check with noindex directives (meta robots + X-Robots-Tag)
Transform critical AMPs into standalone versions if the HTML page must remain noindex
Add standalone AMP URLs into a dedicated XML sitemap with a self-referential canonical
Check in Search Console that valid AMPs properly appear in the mobile index
Test the URL Inspection tool on standalone AMPs to validate fetching and the canonical
Monitor crawl logs to detect AMPs discovered via sitemap vs rel="amphtml"

Managing noindex directives and their impacts on AMPs requires careful coordination among developers, SEO specialists, and editorial teams. Hybrid architectures (HTML + associated AMP, or standalone AMP depending on cases) multiply the risks of contradictory configurations. If your site handles a significant volume of AMP pages or if you notice unexplained discrepancies between indexed HTML pages and their AMP equivalents, it may be wise to enlist a specialized SEO agency to audit your technical stack and secure the indexing of your mobile content.

❓ Frequently Asked Questions

Si je retire le noindex d'une page HTML, combien de temps faut-il pour que Google réindexe l'AMP associée ?

Cela dépend de votre crawl budget. Sur des sites à forte autorité, quelques jours suffisent. Sur des domaines moins prioritaires, cela peut prendre plusieurs semaines. Forcer un recrawl via l'outil d'inspection d'URL de Search Console accélère le processus.

Une AMP autonome peut-elle être indexée si elle n'apparaît dans aucun sitemap ?

Oui, si elle reçoit des liens internes directs ou des backlinks externes. Google peut la découvrir par crawl classique. Cependant, l'inclusion dans un sitemap XML accélère significativement la découverte et réduit le risque d'oubli par le crawler.

Que se passe-t-il si une page AMP porte un canonical vers une URL HTML en noindex ?

Google traite généralement cette configuration comme une exclusion volontaire et n'indexe ni la page HTML ni l'AMP. C'est une contradiction technique qui entraîne souvent une désindexation silencieuse de l'AMP sans alerte dans Search Console.

Comment détecter rapidement les AMP bloquées par un noindex HTML dans Search Console ?

Croisez le rapport "Couverture" (pages exclues par noindex) avec le rapport "AMP" (statut d'indexation). Les URLs AMP valides qui n'apparaissent pas dans l'index alors que leur HTML est exclu sont probablement dans le scénario décrit par Mueller.

Faut-il créer un sitemap AMP séparé ou inclure les URLs AMP dans le sitemap principal ?

Les deux approches fonctionnent. Un sitemap AMP dédié facilite le suivi et le diagnostic, surtout si vous gérez des milliers de pages. L'inclusion dans le sitemap principal simplifie la maintenance mais peut compliquer l'analyse des logs de crawl spécifiques aux AMP.

🏷 Related Topics

AMP noindex indexation canonical crawl budget sitemap XML Search Console mobile-first

Domain Age & History Crawl & Indexing Links & Backlinks Mobile SEO

🎥 From the same video 32

Other SEO insights extracted from this same Google Search Central video · duration 1h00 · published on 27/07/2018

🎥 Watch the full video on YouTube →

Related statements

« Previous

Crawl Speed and Server Infrastructure...

« Back to results