StoreDeployBot
StoreDeployBot runs the readiness scan on storedeploy.com. It only ever runs because somebody typed a domain into the scanner, so it is not a background crawler and it does not discover sites on its own.
User agent
StoreDeployBot/1.0 (+https://storedeploy.com/bot; agentic-commerce readiness scanner)What it requests
/.well-known/ucp— the UCP business profile/robots.txt— to read your crawler policy/sitemap.xmland one child sitemap — to locate product pages/llms.txt— if present- Your homepage, and up to three product pages
- One machine-readable product endpoint, such as
/products.json
Limits
Around a dozen GET requests per scan, sequential, with a 7 second timeout each and a 25 second cap on the whole scan. It sends no POST requests, submits no forms, never authenticates, and ignores anything behind a login. It reads only what it needs for the four checks and stores no copy of your pages.
Blocking it
Add this to your robots.txt and it will stop:
User-agent: StoreDeployBot
Disallow: /Scans of your store will then report as unverified rather than guessing. If a bot filter already blocks it, the report says so instead of marking your store as broken.
To be precise about what we obey: a rule that names StoreDeployBot stops us. A blanket User-agent: * rule does not, because the scan is requested by someone about their own site rather than crawled out of the blue. If that is not what you want, name us.