1. Start with a public URL
ShopMender validates the domain, reads robots.txt, looks for a sitemap and selects public home, product, collection, linked cart and shipping or return policy pages within the plan's page limit.
URL → evidence → action → monitoring
A storefront check built for decisions.
ShopMender inspects the public experience customers use, explains what it found and helps you decide what deserves attention. It is platform-agnostic, read-only and designed to stay understandable.
2. Check the buying path
HTTP and HTML checks look for unavailable pages, product links, cart continuation signals, broken product images, product data, prices and purchase actions. Checkout pages are excluded; ShopMender never submits a cart or payment.
3. Prioritize observable risk
The Revenue Leak Score summarizes the severity of findings in the pages checked. It is a risk indicator for prioritization, not a financial estimate.
4. Show proof and next action
Each finding includes its category, severity, confidence, affected URL, evidence, potential impact and recommendation. A missing signal in fetched HTML is described as not detected, not proof that the store lacks the feature.
What the scan can and cannot see
ShopMender checks public product and collection pages, cart pages linked by the storefront, shipping and returns policies, links, images, markup and response timing. A cart check reads its public page but does not submit the cart. Checkout pages are excluded. ShopMender does not access orders, customer accounts or private server logs.
Respectful by design
ShopMender identifies itself as ShopMenderBot/1.0, rate-limits requests and caps pages, response size, redirects and timeouts. It respects robots.txt and does not bypass CAPTCHA, Cloudflare, WAFs or anti-bot protections. A restricted or ambiguous check is reported as a coverage limit, not as a confirmed store issue.
See it on your store
No account required · no credit card. Read-only public scan · robots.txt respected