FAQS
The practical questions, answered.
How the first scan starts, what the bot does, what evidence is kept and when deeper browser testing is used.
COMMON QUESTIONS
What teams usually want to know first.
Do I need to install a Shopify app for the first scan?
No. The first pass can start from the public storefront. Protected Shopify data is connected separately only when a test needs it.
Does Shopsteddy crawl everything immediately?
No. The system starts with declared site signals and lightweight requests, respects robots policy and brings in browser runtime when an interaction or visual check requires it.
What kinds of problems does it look for?
Examples include broken links and buttons, missing images, browser or request errors, product and variant issues, slow pages, visual regressions and failures in important customer journeys.
Can I use it across multiple stores?
Yes. The product is positioned for both individual brands and agencies managing a portfolio of Shopify storefronts.
How does Shopsteddy identify automated traffic?
Shopsteddy publishes bot-policy and verification information so site operators can recognise and control its traffic. See the bot documentation for the current technical details.
What happens when a site blocks or rate-limits the bot?
Shopsteddy is designed to reduce or stop traffic rather than rotate identities or try to evade the site’s controls.
Is the pricing calculator final?
The public site currently has one confirmed example: 3,400 monitored products at $0.08 per product per month, totalling $272. Other volumes remain TBC until the full pricing curve is confirmed.