robots.txt keeps Google's image crawler off the site's images
Images on the homepage are under a path the robots.txt group for Googlebot-Image disallows (that crawler obeys its own group, else Googlebot's, else the * group). Those images cannot appear in Google Images or as image results, and a page whose pictures are blocked loses them in visual search. The usual cause is a Disallow on an uploads or assets folder written to save crawl budget. 2,437 sites had this problem when we measured them in the last 7 days. The list gives each one with its domain, name where known, platform, every technology we detected, its A–F grade with all its findings, location where known, and what it serves AI crawlers.
- 2,437 sites, last 7 days
- 399 US local businesses
- 6% also block an AI crawler
- $199 once, 30 days of downloads
Who has it
Platform
No CMS detected 74%WordPress 14%Next.js 10%Drupal 3%Webflow 0%Shopify 0%
Grade
F 28%D 27%C 26%A 13%B 6%
Where
Wider corpus 59%US local businesses 16%Government and education 13%SaaS and software 12%
| Where | Category | Grade | Platform | AI crawlers |
|---|---|---|---|---|
| SaaS and software | Publisher | A | No CMS detected | blocked |
| SaaS and software | Other | C | Next.js | allowed |
| SaaS and software | Saas | C | No CMS detected | allowed |
| SaaS and software | Saas | C | Next.js | allowed |
| SaaS and software | Other | A | Next.js | allowed |
| SaaS and software | Saas | A | Next.js | allowed |
| SaaS and software | Other | C | No CMS detected | allowed |
| SaaS and software | Saas | B | Next.js | allowed |
A sample from the live files. Names and websites are withheld here; they are in the file you buy. A business found with a defect is never named publicly before its owner has been contacted.
Every field: what a row holds · 25 free rows · a problem, country or industry we do not list: order a custom dataset.