robots.txt report

github.com

https://github.com

B

80/100

Complexity 100/100

How scoring works
User Agents
12
Rules
1339
Sitemaps
1
Warning
3
File Size
14.2 KB
Cached result · Expires in 23 hours 7 minutes

3 things to look at

1 warning · 2 notice · 2 info · 8 pass

13 crawlers named · 2 unrecognised

What this file says about crawlers

Who this file lets in

  • AI Data Scraper2 allowed, 1 blocked
  • Intelligence Gatherer all 3 allowed
  • AI Search Crawler all 2 allowed
  • Undocumented AI Agent all 1 allowed
  • Search Engine Crawler all 1 allowed
  • Fetcher all 1 allowed
  • Unrecognised all 1 allowed
  • Every other crawler all 1 allowed

Path Access Checker

Detailed Analysis

Warning

3 rules name a secret or data file

Rules name version-control directories, credential files, databases, dumps, archives or logs.

Consequence. If this file is served, it is a critical exposure; listing it here suggests it exists. robots.txt is public and among the first files a scanner reads, and it protects nothing: it only tells readers where to look.

If that is not intended. Check whether these paths answer. Remove the files from the web root or block them at the server, then delete the lines. If a .env file or a .git directory was ever served, rotate every credential it held.

  • Disallow: /.git/L32Secret file or directory (.git)
  • Disallow: /.git/L200Secret file or directory (.git)
  • Disallow: /.git/L382Secret file or directory (.git)
Notice

Crawl-delay is declared 2 times 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: 1L10
  • Crawl-delay: 1L358
Notice

4 rules 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: /copilot/c/L16Already covered by "disallow: /copilot/" on line 15
  • disallow: /copilot/c/L184Already covered by "disallow: /copilot/" on line 183
  • disallow: /copilot/c/L355Already covered by "disallow: /copilot/" on line 354
  • disallow: /copilot/c/L366Already covered by "disallow: /copilot/" on line 365
Info

1 of 6 AI training crawlers are blocked

Blocked: Bytespider.

  • BytespiderByteDanceL178

    ByteDance model training

    "Disallow: /" blocks Bytespider.

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.

Info

3 rules suggest sensitive files may exist

Wildcard patterns name no location, but suggest such files may exist under public paths.

Consequence. A pattern such as "/*.sql$" discloses nothing a reader can request directly. It does say what kind of file the site expects to have lying around.

If that is not intended. Verify that files matching these patterns are not served.

  • Disallow: */.git/L33Secret file or directory (.git)
  • Disallow: */.git/L201Secret file or directory (.git)
  • Disallow: */.git/L383Secret file or directory (.git)
Pass

Search engines can reach the site

All 6 checked search engines are allowed at the site root.

Pass

AI answer engines can reach the site

All 4 checked AI answer engines are allowed at the site root.

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.

Pass

No indexing directives on the requested page

The page sends no robots meta tag and no X-Robots-Tag header.

Pass

1 sitemap declared

Every declared sitemap is an absolute URL and is crawlable.

  • https://github.com/sitemap_marketing.xmlL3
Pass

No syntax problems

Every line parses as a directive crawlers understand.

Pass

File size is 14.2 KB

Comfortably within the 500 KB that crawlers will read.