robots.txt report

stripe.com

https://stripe.com

C

74/100

Complexity 82/100

How scoring works
User Agents
2
Rules
21
Sitemaps
1
Warning
3
File Size
643 B
Cached result · Expires in 2 days 13 hours

3 things to look at

1 warning · 2 notice · 9 pass

3 crawlers named · 1 unrecognised

Who this file lets in

  • Archiver all 1 allowed
  • Every other crawler all 1 allowed
  • Developer Helper all 1 allowed

Path Access Checker

Detailed Analysis

Warning

4 rules name a location nobody would have guessed

Rules name a sensitive location made specific by a qualifier or by where it sits, or a spreadsheet by its full path.

Consequence. A bare "/backup" is in every scanner wordlist; "/backup-2023/" is in none. Listing it advertises the location to the readers least likely to honour the rule.

If that is not intended. Put these locations behind authentication or remove them; once they are protected, the line can stay or go. Responses behind authentication are not indexed, so they need no "noindex". Content that is public by design and only has to stay out of search wants a "noindex" without the Disallow: a crawler only sees a noindex on a page it may fetch.

  • Disallow: /sources/test_sourceL11"test" below the first level
  • Disallow: /sources/test_klarnaL12"test" below the first level
  • Disallow: /sources/test_sourceL22"test" below the first level
  • Disallow: /sources/test_klarnaL23"test" below the first level
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: 2L29
Notice

5 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: /docs/api$L5Already covered by "allow: /docs/api" on line 4
  • disallow: /docs$L7Already covered by "disallow: /docs" on line 6
  • disallow: /handoff-healthcheckL13Already covered by "disallow: /handoff" on line 14
  • allow: /docs$L18Already covered by "allow: /docs" on line 17
  • disallow: /handoff-healthcheckL25Already covered by "disallow: /handoff" on line 26
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.

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://stripe.com/sitemap/sitemap.xmlL1
Pass

No syntax problems

Every line parses as a directive crawlers understand.

Pass

File size is 643 bytes

Comfortably within the 500 KB that crawlers will read.