If this crawler visited your store, it’s because someone asked for an AI-readiness report of that store — usually the owner, sometimes us ahead of reaching out, or a subscriber’s scheduled sqrly Pulse monitoring scan. It reads a store the way an AI shopping agent would, so the report can say what those agents can and can’t see.
How it identifies itself
Requests come from our cloud infrastructure; contact us for IP details. We don’t disguise the user-agent, rotate identities, or crawl through proxies.
What it reads
A small, bounded sample per scan: robots.txt, the sitemap, llms.txt if present, up to a few dozen public pages (home, a handful of product pages, policy and about pages), and public machine-readable endpoints your platform already exposes — for example Shopify’s /products.json. Nothing behind a login, nothing in a cart or checkout, no form submissions, no personal data. Scans are occasional: once for a free report, weekly-to-monthly for Pulse subscribers.
How to block it — or let it in
To keep it out, add this to your robots.txt and we’ll stop at the door — the scan ends and the report says so honestly:
If your bot protection (Cloudflare, Akamai, and friends) is challenging us, the scan reports your store as “couldn’t be read” rather than guessing — we never score a store from pages we didn’t actually see. Worth knowing either way: many AI shopping crawlers (ClaudeBot, GPTBot, PerplexityBot, OAI-SearchBot) hit the same walls, so how you treat crawlers is itself part of how visible your store is to AI assistants.
Questions or complaints
Write to florian@sqrly.ai — you’ll get the founder, not a queue. If the crawler misbehaved on your site, include the timestamps and we’ll dig into the logs the same day.