Friday, January 21, 2022<\/p>\n
\n Today, we’re introducing a new robots tag, \n The \n The new robots tag, \n To enable your content to be indexed only when it’s embedded on other pages, make sure to add \n Alternatively, you can specify the tag in the HTTP header:\n<\/p>\n Presently, only Google supports the \n We hope you find this new tag useful. If you have questions or comments, find us on
\n indexifembedded<\/code><\/a>,
\n that brings you more control over when your content is indexed. With the
\n indexifembedded<\/code> tag, you can tell Google you’d still like your content indexed when
\n it’s embedded through
\n iframes<\/code><\/a>
\n and similar HTML tags in other pages, even when the content page has the noindex<\/code> tag.\n<\/p>\nindexifembedded<\/code> tag addresses a common issue that especially affects media
\n publishers: while they may want their content indexed when it’s embedded on third-party pages,
\n they don’t necessarily want their media pages indexed on their own. Because they don’t want the
\n media pages indexed, they currently use a noindex<\/code> tag in such pages. However, the
\n noindex<\/code> tag also prevents embedding the content in other pages during indexing.\n<\/p>\nindexifembedded<\/code>, works in combination with the
\n noindex<\/code> tag only when the page with noindex<\/code> is embedded into another
\n page through an iframe<\/code> or similar HTML tag, like
\n object<\/code><\/a>.
\n For example, if
\n podcast.host.example\/playpage?podcast=12345<\/code> has both the noindex<\/code> and
\n indexifembedded<\/code> tag, it means Google can embed the content hosted on that page in
\n recipe.site.example\/my-recipes.html<\/code> during indexing.<\/p>\n
\n indexifembedded<\/code> in combination with the noindex<\/code> tag. For example:\n<\/p>\nindexifembedded<\/code> tag.<\/p>\n
\n Twitter<\/a> and in our
\n Help Forums<\/a>.\n<\/p>\n