robots.txt report

securityheaders.com

https://securityheaders.com

All reports for securityheaders.comPage not read: bot challenge
D

53/100

Complexity 9/100

How scoring works
User Agents
1
Rules
1
Sitemaps
0
Warning
2
File Size
22 B
Cached result · Expires in 1 day 1 hour

2 things to look at

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

1 crawlers named · 1 unrecognised

Not checked

Who this file lets in

  • Every other crawler all 1 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

Every URL is open to every crawler

The file declares user agents but no effective Disallow rule.

Consequence. Every URL is crawlable, including any that exist only for internal use. Crawl budget is spent evenly rather than on pages worth ranking.

If that is not intended. Consider disallowing sections with no search value — internal search results, faceted or parameterised URLs, cart and account pages.

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 22 bytes

Comfortably within the 500 KB that crawlers will read.