uusefathom.com

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: /affiliates/fathom-affiliate-assets.zipL16Data file (.zip)

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: /stickers-confirmedL12Already covered by "disallow: /stickers" on line 17

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://usefathom.com/sitemap-index.xmlL1

Every line parses as a directive crawlers understand.

Comfortably within the 500 KB that crawlers will read.