In short. noimageindex restricts image indexing through a page, while a noindex header on the image itself applies wherever that image appears.

Definition: noimageindex is a robots instruction that tells Google not to index images embedded in a particular page. The same images may still be indexed through other pages that display them.

As of 17 October 2026, Google's robots meta tag specification defines noimageindex as a page-level image indexing restriction, available through an HTML meta tag or an HTTP response header.

Key facts

Google's robots specification requires crawl access to the page containing the instruction so that Google can read and follow it.
Google's image removal documentation recommends a noindex response header on an image itself to block it wherever it appears.
Google's noindex guide explains that Googlebot must revisit a resource to read a newly added meta tag or response header.

How is noimageindex added to a page?

A robots meta tag is an HTML element containing crawler instructions. Following Google's meta tag placement instructions, this tag belongs in the page's <head>:

<meta name="robots" content="noimageindex">

The same documentation allows any robots meta rule in an X-Robots-Tag, an HTTP response header carrying crawler instructions. The equivalent header on the page's response is:

X-Robots-Tag: noimageindex

These are alternative delivery methods for the page-level rule. The specification treats rule values as case-insensitive and allows multiple rules in a comma-separated list.

What happens when the same image appears elsewhere?

Google's image removal guide explicitly says that an image embedded in a page with noimageindex may still enter the index through another page. A shared image therefore requires a decision about the image resource itself.

For exclusion wherever the image appears, the guide specifies this header on the image file's own HTTP response:

X-Robots-Tag: noindex

Googlebot must be allowed to crawl the image URL to read that header. The guide also documents image exclusion through robots.txt, the file containing crawl rules for a site. It advises against combining a crawl block with the header method because the block prevents Googlebot from extracting the header.

How can the implementation be checked?

The page's delivered HTML and HTTP response headers are the places to inspect for noimageindex. Google's robots specification says that a robots.txt crawl block prevents indexing and serving rules on that URL from being read.

For an image-level noindex implementation, Google's debugging guidance requires checking that the resource remains accessible to Googlebot. For HTML pages, it recommends the URL Inspection tool to view the HTML Googlebot received. This helps check the delivered tag rather than relying solely on a content management system's setting.

FAQ

Does noimageindex remove the page itself from Google Search?

noimageindex addresses images embedded in the page. To exclude the page itself, you can use noindex, which Google's indexing exclusion guide defines as the instruction for removing a crawled page from Search results.

How does it differ from max-image-preview?

Google's robots specification assigns max-image-preview to the maximum image preview size in search results. Its none value requests no image preview; noimageindex addresses indexing images on the page.

Sources

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