AISaysYouCheck
How we read your site.
When someone runs the instant check on a website, our server fetches a few of its public pages once, the way an answer-engine crawler would, and reports what it could and could not read. This page says exactly what that fetch does and how to stop it.
What we request
robots.txt, the home page, up to five internal pages chosen from the home page's own links (about, contact, safety, fleet or capabilities, locations, the airport page if one was named), sitemap.xml and llms.txt. At most nine requests per run, GET or HEAD only, no cookies, no forms, no logins. We follow up to three redirects and read at most 1.5 MB of any page.
How we identify ourselves
Mozilla/5.0 (compatible; AISaysYouCheck/1.0; +https://aisaysyou.com/check/bot)
declared, not a browser impersonation. If your firewall refuses declared crawlers, the report says so; it is the same door OAI-SearchBot and PerplexityBot knock on.
What we obey
robots.txt for AISaysYouCheck and for *. Disallow: / under either stops the run after robots.txt. Crawl-delay is honored up to two seconds. One run per domain per ten minutes; the same link is served again in between.
What we keep
Findings only: short quotes of up to 300 characters, page URLs, status codes and headers, for 30 days under a private link. No page copies. Anyone holding the link can delete the report.
How to block us
User-agent: AISaysYouCheck Disallow: /
or use the contact form with the domain and we add it to a deny list within one business day.
Why we fetch as a declared bot rather than a browser
Because the point of the check is what a crawler can read. A browser-shaped fetch would hide exactly the problem the site owner needs to see.