Monitoring
Know the day something breaks, not the month after
Catalogues break quietly. A plugin update on Tuesday shows up in revenue in March.
A one time audit is a photograph. Stores change constantly: themes update, plugins change their output, suppliers change prices, and products go out of stock. Webshop Vitals re-checks on a schedule, compares each scan with the last, and tells you what changed rather than showing you the same report again.
Free scan, no credit card, results in minutes.
- High1 store
We could not find a return or refund policy page
No return or refund policy page was reachable from the homepage or at the conventional URLs we checked.
TRUST_RETURNS_MISSING - High11 products
Products are missing a product identifier
Branded items without a GTIN or MPN are limited by Google rather than disapproved, so the loss is invisible.
PD_IDENTIFIER_MISSING - Medium24 products
Shipping information is not machine readable
Delivery details appear in page text only, so they cannot be surfaced in results.
SD_SHIPPING_INFO_MISSING
Example findings, shown with the rule codes the product reports.and 2 more in the full report
The problem
Nothing announces a regression
The failure mode is silence. A theme update drops structured data from product pages and the store looks perfect. Nothing errors, nothing alerts, and the cost appears weeks later as a slow decline that is hard to attribute to anything.
- A traffic decline no one can trace to a change
- Issues you fixed that quietly returned
- Feed problems discovered by a customer rather than by you
- Audits that get run once and never again
What we check
Inside the automated store monitoring
Every check below runs on your real store and reports findings you can act on, with the affected products named.
Scheduled re-scans
Weekly on Pro and daily on Growth, with the same rules applied every time.
Change detection
Each scan is compared with the previous one and reported as fixed, new, or returned.
Regression tracking
Findings that were resolved and came back are marked, because a repeat is a process problem.
Score history
Scores over time, so a drop can be lined up against the date of a deployment.
Notifications
Alerts when something meaningful changes rather than a report on a fixed schedule.
Use this as your own checklist
0 of 5How it works
Three steps from question to answer
No plugin to install, no code to add, and nothing to change on your store.
- 1
Pick a frequency
Weekly or daily depending on plan, or run a manual scan whenever you ship a change.
- 2
We diff the results
Findings are fingerprinted so the same issue is recognised across scans rather than reported as new.
- 3
You hear about deltas
Notifications describe what appeared, what cleared and what came back.
The report
What this check looks like in your dashboard
Findings land next to the score they moved and the products they affect, so a result always has somewhere to go next.
Website Readiness
89out of 100
- Product structured data30% 76
- Crawlability20% 97
- Product content20% 98
- Trust and merchant info15% 87
- AI commerce readiness15% 96
Products
Sorted by data quality| Product | Quality | Status |
|---|---|---|
3D & Collagen Snow Solution SKU ISOV-3DC-01 | 100 | Approved |
pH Balance Cleansing Cream SKU CORTHE-PH-08 | 80 | Limited |
Anti-Wrinkle Eye Mask SKU not set | 55 | Disapproved |
Holy Grow Lash Serum SKU BLOSSCO-LS-02 | 100 | Approved |
Since your last scan
- 7
- Issues fixed
- 2
- New issues
- 1
- Returned
- +4
- Readiness
Structured data returned on 24 products after a theme update. Caught the same day.
What you get
What changes after the first scan
Concrete outputs, not a grade with no next step.
- A short list of what changed instead of a full report to re-read
- Regressions caught in days rather than in quarters
- A dated score history you can line up against deployments
- Confidence that a fix stayed fixed
Questions
Automated Store Monitoring questions, answered
The things merchants ask before they run their first scan.
Weekly suits most stores. Daily makes sense for large or fast moving catalogues, and for the period right after a migration or a theme change when regressions are most likely.
Keep reading
Related checks
Google Merchant Center Audit
Read every account and product issue Google reports, grouped by root cause.
Ecommerce Crawlability Audit
Check robots rules, sitemaps, canonicals and redirects across your product pages.
Product Feed Audit
Compare what your feed sends against what your product pages actually show.
See where your store actually stands
Run a free scan and get a prioritised report of what to fix first, with the affected products named.
No credit card needed for the free scan.