In short. Google documents noimageindex as page-specific and recommends X-Robots-Tag: noindex on the image response for image-level control.
Definition: Yes. Google documents
noimageindexas a page-level rule: it prevents images embedded in the page carrying the rule from being indexed, while the same image on another page might still be indexed through that page. For a restriction attached to the image URL itself, Google documents thenoindexX-Robots-Tagresponse header.
Key facts
- Google's image removal documentation says that
noimageindexaffects images embedded in the particular page and that the same images might be indexed through other pages. - Google's robots meta tag specification defines
noimageindexas “Do not index images on this page.” - Google's noindex documentation says an
X-Robots-Tagresponse header can be used for non-HTML resources, including image files.
What does noimageindex apply to?
noimageindex is a page-level robots rule. Google's robots meta tag specification describes the robots meta tag as a “page-specific approach” for controlling an individual HTML page, and its rule table says: “Do not index images on this page.” A matching HTML declaration is:
<meta name="robots" content="noimageindex">
The page-specific scope matters when one image URL is embedded in more than one HTML page. Google's image removal documentation states that the rule prevents images embedded in the page from being indexed, then says that the same images might get indexed through other pages. The rule therefore describes the image's use on that page, rather than a universal instruction attached to the image file.
Why is X-Robots-Tag the image-level alternative?
An X-Robots-Tag is an HTTP response header returned for a URL. Google's robots meta tag specification says that rules available in a robots meta tag can also be specified as an X-Robots-Tag, and it gives this response-header form:
X-Robots-Tag: noindex
When this header is returned with the image response, the instruction is associated with the image URL. Google's image removal documentation says that the image URLs must remain crawlable so Googlebot can extract the noindex rule. The same documentation directs site owners to this header when they want a particular image blocked wherever it appears.
Google's noindex documentation also identifies response headers as the mechanism for non-HTML resources, including image files. It says that a noindex rule is effective only when the resource is accessible to the crawler and is not blocked by robots.txt; otherwise, the crawler cannot see the rule.
How should a site owner check the configuration?
First identify whether the restriction is in the HTML page or in the response for the image URL. A page carrying the following declaration has page-level scope:
<meta name="robots" content="noimageindex">
Then inspect the response for the image URL and look for:
X-Robots-Tag: noindex
Google's image removal documentation requires crawling of the image URL for the header rule to be extracted. Google's noindex documentation adds that a robots.txt block prevents the crawler from seeing the rule. These checks separate a page instruction from an instruction delivered with the image resource.
Related terms
FAQ
Can the same image appear in search through another page?
Yes. Google says that if the same images appear in other pages, they might get indexed through those pages after noimageindex is added to a particular page.
What header should you return with the image?
Return X-Robots-Tag: noindex in the HTTP response for the image URL. Google says the image URL must be crawlable so Googlebot can read the rule.
Does the HTML page need the header?
No. The header belongs to the response for the image resource. Google documents X-Robots-Tag for non-HTML resources such as image files.
Sources
- Google Search Central, "Remove images hosted on your site from search results", 2025-12-10
- Google Search Central, "Robots meta tag, data-nosnippet, and X-Robots-Tag specifications", 2025-12-10
- Google Search Central, "Block Search Indexing with noindex", 2025-12-10
Check how a page reads to answer engines. Open the GEO score analyzer