robots.txt report

skimlinks.com

https://skimlinks.com

A

93/100

Complexity 91/100

How scoring works
User Agents
12
Rules
14
Sitemaps
1
Notice
1
File Size
785 B
Cached result · Expires in 1 day 1 hour

1 thing to look at

1 notice · 4 info · 1 not checked · 4 pass

12 crawlers named · 1 unrecognised

What this file says about crawlers

Not checked

Who this file lets in

  • AI Data Scraper all 7 blocked
  • AI Search Crawler all 2 blocked
  • AI Assistant all 1 blocked
  • Search Engine Crawler all 1 blocked
  • Every other crawler all 1 allowed

Path Access Checker

Detailed Analysis

Notice

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: 10L38
Info

1 of 6 search engines are blocked

Blocked: Baiduspider.

  • BaiduspiderBaiduL34

    Baidu

    "Disallow: /" blocks Baiduspider.

If that is the intention. If your intention is to keep the site out of the major search indexes, the current configuration achieves that for these crawlers — the rest of the group is still allowed.

Consequence. These search engines cannot crawl the site, so its pages will not appear in their results. Note that robots.txt does not remove URLs that are already indexed — it stops them being re-crawled.

If that is not intended. Remove the matching Disallow rule, or give these crawlers their own group with an Allow rule. Path matching is longest-wins, so a specific Allow overrides a broader Disallow.

Info

2 of 4 AI answer engines are blocked

Blocked: OAI-SearchBot, Google-Extended.

  • OAI-SearchBotOpenAIL10

    ChatGPT search results

    "Disallow: /" blocks OAI-SearchBot.

  • Google-ExtendedGoogleL19

    Google AI Overviews and Gemini grounding

    "Disallow: /" blocks Google-Extended.

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-UserOpenAIL7

    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.

Info

5 of 6 AI training crawlers are blocked

Blocked: GPTBot, ClaudeBot, Bytespider, CCBot, Amazonbot.

  • GPTBotOpenAIL4

    OpenAI model training

    "Disallow: /" blocks GPTBot.

  • ClaudeBotAnthropicL13

    Anthropic model training

    "Disallow: /" blocks ClaudeBot.

  • BytespiderByteDanceL28

    ByteDance model training

    "Disallow: /" blocks Bytespider.

  • CCBotCommon CrawlL16

    Common Crawl, widely redistributed as training data

    "Disallow: /" blocks CCBot.

  • AmazonbotAmazonL25

    Amazon model training and Alexa

    "Disallow: /" blocks Amazonbot.

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

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

1 meta tag and 0 X-Robots-Tag headers, with no contradictions.

  • <meta name="robots" content="index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1">Page HTML
Not checked

1 declared sitemap was not checked

These sitemaps were not seen: each was blocked for our bot, left out by a limit, or did not answer in time. Each line says which.

Consequence. Nothing is known about whether they work. They are not counted against the file.

  • https://www.skimlinks.com/sitemap_index.xmlL43Not fetched: it is on another origin, whose robots.txt could not be read
Pass

No syntax problems

Every line parses as a directive crawlers understand.

Pass

File size is 785 bytes

Comfortably within the 500 KB that crawlers will read.