Robots.txt for images controls search engines’ access to graphic files on a website. This file can be used to specify which images can be indexed and which cannot. By default, search engines ignore both HTML and media files if they are open. When a website works with a large amount of visual content, controlling indexing becomes part of technical optimization.
The robots.txt file is located in the root directory of the website and is read by the bot before it starts crawling. If the directives block access to images, the bot does not view them and does not add them to Google Images. If access is open, images can be indexed and appear in visual search results. This affects traffic, visibility, server load, and crawling volume.
Prohibiting image indexing is used when images are not valuable for search or should not be distributed. It is also a way to reduce unnecessary crawl budget and remove duplicate content. Blocking graphics does not prevent images from being displayed on the site — it only affects the behavior of robots. For sites focused on content promotion, configuring robots.txt is not a formality, but a way to control the entry point for bots into media sections.
When to use image blocking via robots.txt
Images are loaded and indexed in the same way as HTML pages. If the file is accessible via a direct link and is allowed in robots.txt, it will be indexed. If it is closed, it will not. This applies to all formats: .jpg, .png, .webp, .gif.
Image blocking is used in the following cases:
- photos are taken from paid stock sites and should not be distributed
- graphics are duplicated on dozens of pages
- visual content does not add value to search results
- some images relate to protected data or confidential material
- media files are created automatically (e.g., previews without uniqueness)
- it is necessary to speed up navigation through other sections of the site
Both individual images and entire directories can be blocked. This is done using the standard Disallow directive.
Read also: What is crawl budget.
Examples of robots.txt settings for images
Prohibiting indexing of all images:
- User-agent: Googlebot-Image
- Disallow: /
- Allowing indexing of all images:
- User-agent: Googlebot-Image
- Allow: /
Prohibiting a specific folder:
- User-agent: Googlebot-Image
- Disallow: /uploads/
Prohibiting by file type:
- User-agent: *
- Disallow: /*.jpg$
- Disallow: /*.png$
Googlebot-Image is only responsible for Google Images. Other agents work for HTML pages with these images.
How robots img settings affect SEO
When images are indexed, they can participate in visual search results. Unique, optimized images with correct ALT tags and file names provide additional traffic from image searches. In e-commerce, blogs, recipes, tourism, design, and visual search, this is an additional source of traffic. In other niches, it does not make sense.
If images are:
- stock
- identical for different products
- have no informational value
- are duplicated between language versions
- create a load on the crawler
- …they do not need to be indexed.
For pages where images are the main content, it is beneficial to index them. This applies to projects where media is meaningful: galleries, work examples, landing pages with infographics, reviews.
Optimizing images for indexing
If images should be included in search results:
- use unique file names
- add keywords to ALT
- compress the size without losing quality
- load images from your own host, not from a CDN
- specify logical URLs (/images/seo-audit.png, not /media/file123.png)
- avoid JS-loaded images that are not visible to bots
Media content should only be indexed if it enhances the page, provides additional value, and can be found through specific search queries.
Errors when configuring robots.txt for images
Prohibiting everything without analysis is a major mistake. This blocks all images, even if some of them generate organic traffic. Or, conversely, it allows everything, including junk.
Other mistakes:
- blocking all media via Disallow: / without separating types
- using outdated directives
- unverified wildcard masks (*, $)
- accidentally closing the necessary folders (for example, /img/, where all the site’s visuals are stored)
- no verification of the result in the search results or GSC
- blocking images from external sources embedded in pages
Another common situation is when images are open but are not useful: there is no ALT, the names are uninformative, and the loading speed is low.
How to check image indexing
Google query:
- site:domain.com filetype:jpg
- If there are results, the images are indexed. If there are no results, check robots.txt.
In Google Search Console, you can check whether Googlebot is bypassing the path to the image and whether it can see it. Checking the URL will provide information about access, response code, and scan status. Additionally, use X-Robots-Tag: noindex in server headers if you need to control access to individual files through the backend, not just through robots.txt.
Read also: What is index bloat and how to avoid it.
When images in the index are bad
Images that are worthless, massively duplicated, or technical increase the overall size of the index without any benefit. This slows down the updating of key pages and reduces the overall visibility of the site. This is especially noticeable in online stores, where thousands of products use the same icon, background, or watermark.
Also bad:
- if images from the /admin/ folder appear in search results
- if protected banners are used by competitors
- if content illustrations are copied and you lose the original source
File protection starts with a proper robots.txt file and restricting unnecessary access at the server level.
The relationship between robots.txt settings and visual content
For websites where images are part of the promotion, it is important not just to open them up for indexing, but to integrate them into your strategy:
- optimized ALT
- semantic names
- content around the image
- correct format (webp is preferable)
- fast loading
- structured data, if applicable (product, recipe, article)
If a visual is not planned to be promoted, it is closed, removed from the sitemap, and does not participate in internal linking. This saves resources and simplifies SEO work. When ordering SEO services in Kyiv at affordable prices, competent robots.txt configuration is included in the basic check. This is not a separate element, but a control point over indexability and load.
What to do before configuring robots.txt for images
- Understand whether images are needed in search results
- Check what is already indexed
- Decide which directories are open and which are closed
- Configure access by User-agent: Googlebot-Image
- Check masks and exceptions Assess the impact of changes on speed and traffic
- Monitor the results in Google Search Console
Robots.txt for images is not a formality. It is a filter. It either helps or hinders. If your site works with media, configuration is mandatory. If not, you need to exclude everything unnecessary and keep the index under control.
What is robots.txt for images?
Robots.txt for images is a file that controls the access of search robots to graphic files on the site. With its help, you can enable or disable indexing of images in search engines. It helps control which visual elements will be displayed in image search results. The correct setting of robots.txt allows you to better manage the visibility of media content.
Why limit the indexing of images through robots.txt?
Restricting indexing is necessary to protect copyrights, reduce the load on the server, or manage the site's reputation. Sometimes resource owners want to prevent images from appearing in search results to preserve content exclusivity. In other cases, the ban is needed to optimize the crawling budget. The decision to block should be made depending on the goals of the project.
How to configure robots.txt to prevent indexing of images?
In order to prevent the indexing of images, instructions are added to the robots.txt file that prohibits access to folders with graphic files. For example, you can use the Disallow directive for specific directories. At the same time, it is important to consider that by denying access, you not only block indexing, but also limit the display of images in the search engine. The setting should be conscious and correspond to the site strategy.
What are the consequences of banning the indexing of images?
When indexing is disabled, images will not be displayed in search results, which may reduce additional traffic from image searches. This solution is suitable if the images have a purely official role or must remain closed. However, for sites where visual content plays an important role in attracting visitors, a ban can be a mistake. It is important to assess the pros and cons of such a step in advance.
Is it possible to allow indexing of only individual images?
Yes, with the help of the correct robots.txt setting, it is possible to flexibly control access to individual folders or files. For example, you can close one category of images for indexing and leave others open. This allows you to promote the necessary visual content while protecting technical or irrelevant images. Fine-tuning helps to better control the visibility of media materials.
How to check whether robots.txt works correctly for images?
The check can be carried out with the help of tools for webmasters, which allow you to test the rules of robots.txt. It is also worth manually analyzing the availability of images through image search. If the file is configured correctly, prohibited images will not be displayed in the search results. Regular checking helps to detect errors in accessing graphic content in a timely manner.
