Google updates its guidance on removing images from search
Google clarified its guidance for urgent and non-urgent image removal from Search. The distinction matters: a temporary search removal request is different from permanently controlling an image on your site.
Removing images from Google's index
Google provides different methods for urgent removal and longer-term control of images you manage.
The guidance covers several practical questions:
- How to request rapid removal.
- What to do when you cannot control the image CDN or your CMS does not provide indexing controls.
- How robots.txt rules apply to images.
- Using wildcards in robots.txt.
- The limitations of the noimageindex directive.
How can an image be removed quickly?
Google distinguishes temporary removal from a permanent solution:
For an urgent request involving images on a site you control, use Search Console's Removals tool. To keep them out after the temporary request expires, also remove the images or apply an appropriate lasting control. A removal request alone does not delete the files from the internet.
Images and robots.txt
Rules must apply to the host serving the image. Where the file is on a separate host, such as a https://yoursite.example.com/robots.txt“ , check the controls available on that host rather than assuming the main site's file governs it.
Path matching needs care:
An asterisk matches a sequence of characters, while a dollar sign can mark the end of a URL pattern.
In practice:
A wildcard can cover several image paths with one rule. Test the scope before deployment. A page-level noimageindex directive does not necessarily prevent the same image being indexed from another page.