Support
For Free Trial, onboarding, project setup, and general questions.
Support & Feedback
Use support for Free Trial, onboarding, billing questions, and general help. Use feedback for Proof clarity, false positive, false negative, page classification, or bug reports.
For Free Trial, onboarding, project setup, and general questions.
For Proof Card clarity, false positive, false negative, page classification, or bug reports.
Nothing is sent from this page. Fill these in, copy the text, and email it using one of the addresses above.
Do not include passwords, API keys, payment data, customer data, order data, or private admin screenshots.
First response target during Free Trial: within 2 business days.
Use the support@merchantpatrol.net or feedback@merchantpatrol.net link above to send it.
Demo guide
Use the homepage, Store sample, and the branded graceful boundary result. The public demo is scripted and cautious. It is designed to show public evidence validation, not arbitrary crawling.
Do not demo scan modes the public page does not offer. Current public demo guidance is Store sample only.
Store sample is a bounded public evidence sample. It uses public sitemap discovery to find candidate product evidence. It does not claim whole-store validation and does not deep crawl every page.
It means the public evidence path was unavailable, blocked, slow, or outside the quick-scan budget. Merchant Patrol reports the evidence boundary instead of spinning forever or pretending success.
No. Merchant Patrol reports publicly observable evidence. It does not guarantee Google Merchant Center approval, legal compliance, or platform acceptance.
No. The public Store sample does not claim whole-store validation. It reports what was observed and what remains outside the evidence boundary.
No. Merchant Patrol does not enter Shopify admin, does not modify the storefront, and does not automatically fix issues. It observes, validates, records, and explains public evidence.
Merchant Patrol helps Shopify agencies validate publicly observable storefront evidence before or after deployment and produce client-ready proof with explicit evidence boundaries.
Open the homepage, explain public evidence only, run Store sample, then explain the result. If the public sitemap cannot be read, show that no validation claim was made and that the boundary is explicit.
Show the agency problem, the Merchant Patrol homepage, Store sample submission, and either a Store Proof Card or branded boundary result. Avoid claims about whole-store validation, legal compliance, or approval guarantees.