OUR BOT
How Shopsteddy uses your site.
Shopsteddy needs to visit a store to test it, but that does not mean it should behave like an unrestricted crawler. We keep each run within the agreed site and keep traffic measured.
What we normally check
- Public pages and assets on the authorised store.
robots.txtand the store's sitemap files.- Links, products, variants and other storefront elements needed for the configured test.
- Customer journeys such as navigation, search, cart and checkout entry where those checks are part of the run.
What we don't do
- We don't crawl pages outside the approved domain and validated first-party scope.
- We don't probe private or internal network addresses discovered in page content or sitemaps.
- We don't ignore robots.txt restrictions for ordinary crawling.
- We don't collect passwords, payment card details or customer secrets as part of normal monitoring.
- We don't try to bypass a block, rate limit or security challenge by changing identity.
- We don't run vulnerability exploitation as part of normal store monitoring.
If the site tells us to slow down
Rate limit
If the site asks us to slow down, we back off. That pause also applies to other queued work for the same site so we don't keep piling on requests.
Block or challenge
We record what happened and stop or defer the affected work. We don't keep changing identities to force the request through.
Wider Shopify problem
If several stores fail in the same way at the same time, we can reduce Shopify-wide checks rather than repeatedly hitting every store.
Evidence from a scan
We keep enough evidence to confirm what Shopsteddy checked, when the scan ran and what result it saw. That gives store owners a useful record and lets us investigate a scan if something is disputed. Where a status, timing, hash or parsed value is enough, we keep that rather than a full copy of the page. Screenshots and larger captures are used when they genuinely help explain a problem and follow the account's retention settings.