In short. Google's indexifembedded rule permits indexing content embedded in another page when the source page also carries noindex.

Definition: As of 17 October 2026, Google's robots meta tag specification defines indexifembedded as a rule that permits indexing a page's content when it is embedded in another page, despite noindex. The rule only takes effect alongside noindex, which excludes the source page from search results.

Key facts

Google's robots meta tag specification permits this exception for content embedded through iframe, an HTML element that embeds another page, or similar HTML tags.
Google's announcement places noindex and indexifembedded on the page supplying the embedded content and also identifies object as an embedding mechanism.
Google's noindex documentation requires the page carrying the rule to remain accessible to crawlers, including through robots.txt permissions.

What changes when a page is embedded?

Google's announcement describes media publishers who want their content indexed within third-party pages while keeping their own media pages out of search results. Adding indexifembedded alongside noindex permits that embedded use during indexing.

Google illustrates the distinction with a podcast page at podcast.host.example/playpage?podcast=12345 embedded in recipe.site.example/my-recipes.html. With both rules on the podcast page, Google can incorporate its content into the recipe page during indexing. These are Google's example addresses. The source page retains its noindex rule; the exception concerns its content within the embedding page.

Where do the rules go?

Google's implementation example combines the rules in a meta tag on the embedded source page. A meta tag supplies information about an HTML document; googlebot targets Google's search crawler. The robots meta tag specification places meta tags in the document's <head>:

<meta name="googlebot" content="noindex,indexifembedded" />

The announcement also permits separate meta tags, one for each rule. Alternatively, an HTTP response header carries the instructions in the server's response for that source URL:

X-Robots-Tag: googlebot:noindex,indexifembedded

Google calls this response header X-Robots-Tag. The combined value expresses both the exclusion of the source page and permission for indexing its embedded content. Adding indexifembedded alone has no effect, according to Google's specification.

How can the implementation be checked?

Google's noindex troubleshooting guidance recommends the URL Inspection tool in Search Console to view the HTML Googlebot receives. For a meta tag implementation, checking the source URL's received HTML establishes whether the combined rule is present where the embedded content is served.

Robots.txt is the file that controls crawler access. Blocking the source URL there prevents Googlebot from reading its indexing instructions. The same guidance explains that Google must crawl a page after a rule is added and allows a recrawl request through URL Inspection. Search Console's Page Indexing report also monitors pages where Googlebot extracts noindex.

FAQ

Can I use indexifembedded without noindex?

No. Google's specification states that indexifembedded only has an effect when accompanied by noindex.

Should I put the tag on the page containing the iframe?

Google's example puts both rules on the source page loaded inside the embedding element. Apply them to the page supplying the content for which this indexing exception is intended.

Sources

Check how a page reads to answer engines. Open the GEO score analyzer