Crawl-delay is declared 1 time and Google ignores it
Crawl-delay was never part of the standard. Google has never supported it; Bing and Yandex do.
Consequence. Any rate limit intended for Googlebot is not being applied. If the goal was to reduce load from Google specifically, it is not working.
If that is not intended. Set the crawl rate for Google in Search Console instead. Keep the directive if the limit is meant for Bing or Yandex, which do honour it.
Crawl-delay: 5L113
Notice
1 rule can never take effect
A broader rule of the same type already covers these paths.
Consequence. These lines change nothing. They are harmless, but they add length to a file that has a size limit, and they make the real policy harder to read.
If that is not intended. Remove the redundant rules, or narrow the broader rule if it is catching more than intended.
disallow: /genre/*L13Already covered by "disallow: /genre/" on line 12
If that is the intention. If your intention is to keep the site out of AI-generated answers, the current configuration achieves that for these crawlers — the rest of the group is still allowed.
Consequence. The site cannot be cited as a source in AI-generated answers. Unlike training crawlers these send referral traffic, so blocking them forfeits those visits.
If that is not intended. Remove the matching Disallow rule, or allow these agents on the sections you want cited.
Info
1 of 3 user-triggered AI fetches are blocked
Blocked: ChatGPT-User.
ChatGPT-UserOpenAIL47
A ChatGPT user opening this page
"Disallow: /" blocks ChatGPT-User.
If that is the intention. If your intention is to prevent assistants from fetching pages when a person asks for them, the current configuration achieves that for these crawlers — the rest of the group is still allowed.
Consequence. When someone asks an assistant to open a page on this site, it cannot be retrieved. These requests are made because a person asked for that specific page, not to collect content in bulk.
If that is not intended. Allow these agents globally, or only on the sections you want retrievable.
Common Crawl, widely redistributed as training data
"Disallow: /" blocks CCBot.
If that is the intention. If your intention is to prevent this content being used as model training data, the current configuration achieves that for these crawlers — the rest of the group is still allowed.
Consequence. These crawlers cannot retrieve content from the site, so it will not be collected as training data. They send no traffic back, and blocking them does not affect search rankings.
If that is not intended. Remove the site-wide block, or replace it with narrower path restrictions.
Pass
Search engines can reach the site
All 6 checked search engines are allowed at the site root.
Pass
Social link previews can reach the site
All 5 checked social link previews are allowed at the site root.
Pass
Page indexing directives are consistent
3 meta tags and 0 X-Robots-Tag headers, with no contradictions.
<meta name="robots" content="max-image-preview:large">Page HTML
<meta name="robots" content="noai, noimageai">Page HTML
<meta name="robots" content="index, follow">Page HTML
Pass
2 sitemaps declared
Every declared sitemap is an absolute URL and is crawlable.
https://variety.com/sitemap_index.xmlL1
https://variety.com/news-sitemap.xmlL2
Pass
No syntax problems
Every line parses as a directive crawlers understand.
Pass
File size is 1.8 KB
Comfortably within the 500 KB that crawlers will read.