This report has expired. It was fetched on .

robots.txt report

indeed.com

https://indeed.com

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

76/100

Complexity 75/100

How scoring works
User Agents
65
Rules
6837
Sitemaps
0
Warning
2
File Size
13.4 KB

2 things to look at

1 warning · 1 notice · 1 not checked · 7 pass

65 crawlers named · 10 unrecognised

Not checked

Who this file lets in

  • AI Data Scraper14 allowed, 3 blocked
  • Unrecognised6 allowed, 3 blocked
  • Uncategorized1 allowed, 2 blocked
  • Scraper all 2 blocked
  • Intelligence Gatherer4 allowed, 1 blocked
  • Archiver all 1 blocked
  • AI Search Crawler all 7 allowed
  • AI Assistant all 6 allowed

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.

Notice

28 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.

  • allow: /*&start=0&L4Already covered by "allow: /" on line 3
  • allow: /*&start=10&L5Already covered by "allow: /" on line 3
  • allow: /*&start=20&L6Already covered by "allow: /" on line 3
  • allow: /*&start=30&L7Already covered by "allow: /" on line 3
  • allow: /*&start=40&L8Already covered by "allow: /" on line 3
  • allow: /*&start=50&L9Already covered by "allow: /" on line 3
  • allow: /*&start=60&L10Already covered by "allow: /" on line 3
  • allow: /*&start=70&L11Already covered by "allow: /" on line 3
  • allow: /*&start=80&L12Already covered by "allow: /" on line 3
  • allow: /*&start=90&L13Already covered by "allow: /" on line 3
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

AI training crawlers can reach the site

All 6 checked AI training crawlers 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 13.4 KB

Comfortably within the 500 KB that crawlers will read.