Ecommerce Watch: Continuous Catalogue & Schema Monitoring
A weekly crawl catches issues; continuous monitoring catches them within hours. Ecommerce Watch runs a low-impact continuous probe across your product catalogue — checking that high-revenue PDPs still load, schema still validates, prices match the source-of-truth, stock signals are correct and rankings on revenue-driving queries haven\'t collapsed. This guide covers the watch strategy, the alert tiers and the integration with merchandising workflows.
What Ecommerce Watch monitors
Watch is the continuous counterpart to the Ecommerce Crawl. Where the crawl produces a full snapshot weekly, Watch maintains a real-time picture by checking critical signals on revenue-driving pages hourly to daily:
PDP AvailabilityHigh-revenue products return 200; not 404, 500, or unexpected redirect.
Schema DriftProduct schema still validates; required fields still present.
Price ConsistencyPrice in schema matches price shown in HTML matches price in your source database.
Stock Signal Consistencyavailability in schema matches the rendered "add to cart" state.
Image LoadingPrimary product image loads; not 404 / mixed-content / oversized.
Ranking TrackingTop revenue queries — daily ranking, position 1-30, with alerts on movement.
Category Page HealthTop categories load, product count plausible, pagination works.
Sitemap DriftXML sitemap product count vs database product count; alerts on divergence.
Picking what to watch
Don't watch every page. Pick the 1-5% of pages that drive 50-90% of revenue:
- Top 100 PDPs by revenue last 90 days
- Top 20 PLPs by entry sessions
- Top 10 category pages by impressions
- Homepage, cart, checkout
- Top 10 brand or franchise pages if applicable
Total watched URLs: 100-200 for most mid-size catalogues. Hourly checks at this volume are cheap; full-catalogue hourly is wasteful.
Alert tiers
| Tier | Trigger | Alert |
|---|
| P0 — Revenue stopped | Cart, checkout, homepage 5xx or 4xx | SMS + on-call immediately |
| P1 — Top product down | Top-100 PDP returning 404/5xx | Slack + email within 5 minutes |
| P2 — Schema broken | Required Product schema field missing on top-100 PDP | Slack within 30 minutes |
| P3 — Ranking drop | Top revenue query drops more than 5 positions | Daily digest |
| P4 — Drift | Sitemap product count drifts more than 1% from DB count | Weekly digest |
Price and stock consistency
The most common ecommerce SEO failure isn't slow pages or broken schema — it\'s the price in schema disagreeing with the price in HTML disagreeing with the price the customer sees on the buy button. Google notices when schema-price doesn\'t match rendered-price and demotes affected pages. Watch checks all three sources every probe and alerts on divergence within minutes.
💡 Price disagreement frequently happens when ecommerce platforms cache schema separately from the rendered template. After a price change in your PIM, schema cache may take hours to clear. Watch makes this lag visible.
Schema drift
Required fields silently disappearing from JSON-LD is a common regression after platform updates, theme changes or merchandising bulk edits. Watch validates Product schema fields against the Google requirements list every probe and alerts the moment a required field stops appearing. This catches accidental data-source disconnects before they affect rankings.
Ranking tracking
For each top revenue query, Watch records daily position 1-30 across Google. Movements of more than 5 positions trigger P3 alerts. Trends over 4-12 weeks reveal whether algorithm updates, competitor moves or your own changes are driving ranking direction.
Integration with merchandising
Watch alerts should route to the right team:
- P0/P1 → on-call engineering
- P2 (schema) → SEO + dev
- Price disagreement → merchandising + dev
- Stock signal drift → inventory ops
- Ranking drop → SEO
Wrong routing turns Watch into noise. Right routing turns it into a daily reliability practice.
Frequently Asked Questions
How often should top PDPs be probed?
Hourly for the top 50 revenue PDPs is the right starting point for most catalogues. More frequent rarely adds value; less frequent misses critical regressions. Cart, checkout and homepage warrant 5-15 minute probes since their failure stops revenue immediately. The lowest-revenue watched URLs can be probed every 6-12 hours.
What's the difference between Ecommerce Crawl and Ecommerce Watch?
Crawl is a full-catalogue snapshot run weekly or monthly — comprehensive, deep, but infrequent. Watch is a continuous narrow probe on revenue-critical pages — fast detection, narrow surface, structured alerting. Use both: Crawl finds structural issues across the whole catalogue, Watch catches regressions on the pages that matter most before they hurt revenue.
Will continuous probing affect my server performance?
Negligible at reasonable cadences. 100 URLs probed hourly = 2,400 requests per day, less traffic than a single moderate-scale Googlebot wave. The probes use HEAD requests where possible and apply backoff if your server returns slow responses. Real bot traffic from Google, Bing and AI engines is many orders of magnitude larger.
Can Watch detect issues outside my top 200 pages?
Not directly — that's what Crawl is for. The trade-off is intentional: continuous monitoring of every page would be expensive and noisy. Watch focuses on the high-impact tail; Crawl finds long-tail issues. Together they cover the whole catalogue at the right cadence for each.
👁 Watch your ecommerce catalogue
Continuous monitoring of PDPs, schema, prices, stock and rankings on revenue-critical pages.
Open Ecommerce Watch →