The short version
A buying guide tells you what a competitor wants shoppers to believe. A price change on a compatible store tells you what they did. Content Radar keeps publishing evidence and Product Events in separate paths so your team can compare the two kinds of evidence before a merchandising decision.
Useful for
Ecommerce growth, merchandising, and content teams watching a defined set of stores.
Content side
Buying guides, category pages, seasonal campaigns, and editorial.
Catalog side
Compatible public Shopify, WooCommerce, and structured custom stores.
The situation
A competitor publishing a run of gift guides in October is stating a seasonal intent. A competitor adding forty products and dropping prices on a category in October has already acted. The first is a plan you can still respond to, and the second is a change you are reacting to. Confusing them leads to responding at the wrong speed.
Reading them together is where the value sits. A new buying guide that maps onto products the competitor added the same week may be part of a coordinated campaign. A guide without observed catalog movement could serve an existing range; neither pattern establishes traffic or campaign performance.
Product Monitoring
Product Monitoring runs on compatible public Shopify, WooCommerce, and structured custom stores. Each detected change becomes a Product Event you review in Recent Changes and in-app alerts, with persistent product change history recorded in Product Events, separate from Workspace History.
Content surfaces
Sitemaps
New buying-guide and editorial URLs that pass the sitemap content filter. Category and collection pages may be excluded; review selected pages manually.
Learn moreCompetitor blogs
Buying guides and gift guides, which reveal the terms a store wants to own before the season starts.
Learn moreResource hubs
Sizing guides, care instructions, and comparison content that sits outside the blog.
Learn moreBoundaries
The catalog side is deliberately bounded. These are the edges worth knowing before you rely on it.
No. Compatibility is confirmed first, and monitoring covers compatible public Shopify, WooCommerce, and structured custom stores. A store that fails the compatibility check cannot be monitored on the catalog side, though its content surfaces may still be available.
It means two checks recorded different values in the same currency for the same product. Whether that reflects a campaign, a clearance, or a permanent reposition is a reading your team makes, usually after several events rather than one.
Keep the records separate and read them side by side. Mixing them tends to produce conclusions that neither source supports on its own.
Product capability
Plan the response
Add a compatible competitor store and attach its content surfaces, then review each record on its own terms.