How to recognise Shopsteddy traffic.

Our bot identifies itself as

The User-Agent is the easiest way to recognise Shopsteddy in ordinary logs. Like any User-Agent, it can be copied by someone else, so it should not be treated as proof on its own.

Look for the Shopsteddy identifiers

We identify the bot as NBTBot/1.0. We also attach a unique Shopsteddy-Scan-Id to the scan so you can quote it back to us if you want us to investigate the traffic.

Direct Shopsteddy crawler requests are signed with Web Bot Auth. The public key is published at the well-known directory below. Browser-based QA runs through Cloudflare Browser Run, which attaches its own non-removable Web Bot Auth signature; Shopsteddy still supplies its published User-Agent and scan ID so the run remains traceable.

If you want us to check a request

1. Look for NBTBot/1.0.That is the User-Agent we publish for Shopsteddy crawling and testing.
2. Copy the Shopsteddy-Scan-Id if it is present.That is the quickest way for us to trace the run internally.
3. Check the page was on your approved domain.Shopsteddy is designed to stay within the site it was asked to test.
4. Ask us if anything looks wrong.Send the scan ID, timestamp, host and path. A Cloudflare Ray ID is useful too if you have one.

Shopify store owners can approve Shopsteddy directly.

If your store is on Shopify, Shopify Admin can create a crawler signature for the domain you want us to test. Shopsteddy can use that approval on requests to your storefront without needing your Admin password.

Our public signing-key directory

When signed requests are in use, the public keys needed to verify them are published here. The private signing key is never published.