robots.txt report

cdnfonts.com

https://cdnfonts.com

All reports for cdnfonts.comPage not read: bot challenge
B

79/100

Complexity 75/100

How scoring works
User Agents
33
Rules
33
Sitemaps
0
Warning
1
File Size
2.6 KB
Cached result · Expires in 21 hours 54 minutes

1 thing to look at

1 warning · 3 info · 1 not checked · 4 pass

33 crawlers named · 6 unrecognised

What this file says about crawlers

Not checked

Who this file lets in

  • AI Data Scraper all 14 blocked
  • Unrecognised all 5 blocked
  • Undocumented AI Agent all 3 blocked
  • AI Search Crawler all 3 blocked
  • Intelligence Gatherer all 2 blocked
  • Developer Helper all 2 blocked
  • Search Engine Crawler all 1 blocked
  • Uncategorized all 1 blocked

Path Access Checker

Detailed Analysis

Warning

No sitemap is declared

The file contains no "Sitemap:" line.

Consequence. Crawlers have to discover every URL by following links. Pages that are deep, newly published, or poorly linked internally take longer to be found, and some may never be. A sitemap is the most direct way to hand a crawler the full list.

If that is not intended. Publish an XML sitemap and declare it with an absolute URL, e.g. "Sitemap: https://example.com/sitemap.xml". The line is global — it belongs outside any User-agent group and applies to every crawler.

Info

1 of 6 search engines are blocked

Blocked: Baiduspider.

  • BaiduspiderBaiduL81

    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

1 of 4 AI answer engines are blocked

Blocked: Google-Extended.

  • Google-ExtendedGoogleL54

    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

6 of 6 AI training crawlers are blocked

Blocked: GPTBot, ClaudeBot, Bytespider, meta-externalagent, CCBot, Amazonbot.

  • GPTBotOpenAIL57

    OpenAI model training

    "Disallow: /" blocks GPTBot.

  • ClaudeBotAnthropicL48

    Anthropic model training

    "Disallow: /" blocks ClaudeBot.

  • BytespiderByteDanceL42

    ByteDance model training

    "Disallow: /" blocks Bytespider.

  • meta-externalagentMetaL75

    Meta model training

    "Disallow: /" blocks meta-externalagent.

  • CCBotCommon CrawlL45

    Common Crawl, widely redistributed as training data

    "Disallow: /" blocks CCBot.

  • AmazonbotAmazonL36

    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.

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

User-triggered AI fetches can reach the site

All 3 checked user-triggered AI fetches 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.

Not checked

Page directives were not checked

The page answered HTTP 403 with a bot challenge instead of its content, so its meta robots tags and X-Robots-Tag headers were not read.

Consequence. Nothing is known about whether this page asks to be kept out of search results. Its absence of directives here proves nothing either way.

If that is not intended. Analyse the page again once it answers normally to our bot.

Pass

No syntax problems

Every line parses as a directive crawlers understand.

Pass

File size is 2.6 KB

Comfortably within the 500 KB that crawlers will read.