sstripe.com

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

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

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

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

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

All 3 checked user-triggered AI fetches are allowed at the site root.

All 5 checked social link previews are allowed at the site root.

All 6 checked AI training crawlers are allowed at the site root.

The page answered HTTP , 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.

Every declared sitemap is an absolute URL and is crawlable.

• https://stripe.com/sitemap/sitemap.xmlL1

Every line parses as a directive crawlers understand.

Comfortably within the 500 KB that crawlers will read.