indexifembedded: the robots tag for iframes that few SEOs use well

TL;DR: indexifembedded is a robots directive that lets Google index content when it's displayed embedded on another page via iframe, even if the source page is blocked by noindex. It's useful for widgets, embedded readers and syndicated content. Misused, it fragments your indexing.

What indexifembedded is

indexifembedded is a directive of the X-Robots-Tag and the <meta name="robots"> meta tag introduced by Google in January 2022. Its function is very specific:

It allows content indexing only when it appears embedded inside another URL (typically via <iframe>), even if the original source page has noindex.

In practice it solves a conflict that media outlets and SaaS tools had: wanting to keep the source page out of Google's index (because it doesn't add value on its own) while allowing the content to be indexed when a third party embeds it.

Syntax: two ways to declare it

In HTML meta tag

<meta name="robots" content="noindex, indexifembedded">

In HTTP header

X-Robots-Tag: noindex, indexifembedded

Both are equivalent. The HTTP header is preferable for non-HTML resources (PDF, JSON, videos).

When to use it (valid cases)

indexifembedded isn't for almost anyone. These are the scenarios where it does make sense:

• Embeddable widgets: a calculator, a map or a tool you publish at /widget/calculadora-hipoteca and let other media outlets embed in their articles.
• PDF or document readers: if your PDF viewer loads the document via iframe and you want the PDF content to appear in Google, but not the viewer URL.
• SaaS syndicated content platforms: they embed you on hundreds of sites and you want the content indexed in their context, not yours.
• Video / streaming with your own player: the player shouldn't be indexed, but the page where they embed it should.

When NOT to use it

• On your home, landings or service pages. Those must be indexed normally.
• If all you want is to block duplicate content: canonical exists for that.
• If you're unsure. The general rule in technical SEO is simplicity. Each special directive adds risk.

Common mistakes

• Forgetting noindex. indexifembedded only works in combination with noindex. If you only set indexifembedded, the page is indexed normally and the directive does nothing useful.
• Mixing with nofollow. If you add nofollow, links inside the embedded content don't pass authority. Sometimes that's what you want, sometimes not.
• Expecting fast results. Google crawls iframes with lower priority. It can take weeks for the content to appear indexed via the embedding page.

Difference from other robots directives

| Directive | What it does | |-----------|----------| | noindex | Doesn't index the page | | nofollow | Doesn't follow links | | none | Equivalent to noindex, nofollow | | noarchive | Doesn't save a cached copy | | nosnippet | Doesn't show a snippet in SERP | | indexifembedded | Indexes only if it appears embedded in another URL |

How to verify it works

1. Publish the content with noindex, indexifembedded.
2. Embed it on an external page that is indexed (or create a test one).
3. Wait 1-2 weeks and check with site: or inurl: that the content appears referenced from the embedding page, not from the source.
4. Check Search Console → URL Inspection to validate the status.

Implications for GEO

For generative engines (ChatGPT, Gemini, Perplexity), behavior is different: most enterprise RAG pipelines still crawl and process raw HTML and don't respect indexifembedded the same way Google does.

If your goal is for AI to cite your content embedded on other sites, better publish content directly accessible with index + correct schema, and let the mention network do the work. indexifembedded solves a very specific case of classic SEO, not GEO.

More on how to build an entity profile for AI in exposing data to AI with schema, feeds and entity.

Frequently asked questions

Is it the same as canonical? No. canonical indicates the preferred URL when there's duplication. indexifembedded controls whether Google indexes the content when it appears embedded.

Does it work with Bing? Officially Bing doesn't document support. If you need equivalent behavior in Bing, use robots.txt or X-Robots-Tag with specific rules for bingbot.

Does this affect CWV or performance? Not directly. It's an indexing directive, not a rendering one.

Shall we work together?

If you want to apply this in your company with a team that combines technical SEO, GEO and paid acquisition measured against the income statement, request a no-commitment audit. You can also check real case studies or read the public GEO baselines that Elevam Labs publishes every quarter.