Watch rival Shopify storefronts — act only on real changes
Add a competitor by domain. Comver verifies it is a Shopify store, renders and screenshots its homepage, a product page and the cart, and diffs each new snapshot against the last — only a real change on the page becomes a signal. Every signal is ranked, interpreted by Copilot and paired with a response you can send straight to your Action Plan. Under it all, an eight-dimension AI CRO audit of every rival, from real scans.
- Shopify stores only — verified before tracking
- Before / after side by side, never speculative
- Nothing installed on your storefront
AI Commerce Competition · Alerts
aurelle.shop · product page · scan 2 of 2 compared with scan 1
Subscription option and free-shipping bar added to hero products
aurelle.shop · Previous signal: one-time purchase only · Current signal: subscribe & save 15% + free shipping over $50
Copilot interpretation
They are moving the hero product to replenishment revenue and lowering the first-order threshold. Impact: potentially meaningful — worth a test on your store.
Recommended response
Show your Subscribe & Reward option and the free-delivery threshold on the serum PDP; A/B test against the current page.
10
Competitors tracked per store
Any public Shopify storefront; up to 3 selected as Primary for the side-by-side matrix
5
Screenshots per scan
Homepage, product page and cart on desktop, plus mobile homepage and PDP — full-page, cookie banners dismissed first
8
CRO audit dimensions per rival
Homepage, PDP, trust, offer, cart, mobile UX, checkout readiness, CRO fundamentals — 0–100 each
2
Snapshots behind every signal
The two latest completed scans are diffed deterministically; the first scan is the baseline
Beta. Scans run when a competitor is added and on demand; a monitoring cadence is stored per competitor and scheduled scans are coming. Competitor revenue, traffic, conversion and AOV are shown as unavailable rather than estimated.
Verified Shopify, before the first scan
Type a public store domain and Comver checks three independent sources of evidence — HTML signatures, x-shopify response headers and live /products.json and /cart.js probes — and combines them into one confidence score. Confirmed stores are tracked; anything below the line is refused rather than tracked with guesses. Pick a monitoring cadence and the alert types you care about, and the first scan starts on the spot.
- Only public HTTP(S) domains — localhost, private IP ranges and internal networks are blocked before any storefront request
- Up to 10 tracked competitors per store, each with Daily, Twice weekly or Weekly monitoring and 14 selectable alert types
- Pause and resume monitoring per competitor; run a scan or refresh a storefront on demand at any time
Add competitor
Comver verifies the public Shopify storefront, captures its identity and starts the first monitored scan. 6 / 10 tracked.
Public store domain
Segment
Monitoring frequency
Alert types
Select all · Clear allShopify verification
Three independent evidence sources, one confidence score
Tracked from 0.6. Below that the store is refused, never tracked with guesses.
Two snapshots. One real difference.
Every scan extracts the same structured storefront data Comver uses for your own CRO scan and captures full-page screenshots. From the second scan onward, the two latest completed snapshots are diffed deterministically — offer or promo messaging added or removed, trust signals, hero and CTA copy, PDP reviews, upsells, delivery info and sticky add-to-cart, cart type, cart upsells, the free-shipping bar, catalog growth. Nothing is inferred from a single page.
- The AI interprets each diff — intent, a qualitative CRO impact, a 0–100 relevance score and a priority
- Only high and medium priority changes become alerts; high-priority ones also land on the AI CRO Copilot timeline
- The first scan is the baseline: “Changes will appear after the next completed scan.”
Product page · aurelle.shop
Desktop 1280×800Before · scan 1 · 8d ago
After · scan 2 · 2h ago
Detected changes — aurelle.shop
Differences detected between consecutive scans. Only a real change on the page becomes a signal.
A queue that opens on what matters
Every signal is scored for severity and impact — low, medium, high, critical — and shown with before and after side by side, the previous and current signal, a Copilot interpretation, the potential business impact and a recommended response you can send to execution.
Triage by priority, by competitor or on a timeline
A scan status strip — needs attention, unread, monitoring capacity, last scan — then the alert list with severity badges and unread markers, and the alert detail: before / after previews, previous and current signal, Copilot interpretation, potential business impact, recommended response. Mark resolved, compare with your store, or open the live storefront.
Competition Alerts
Market intelligence liveReview meaningful competitor moves, understand their impact and route the right response into execution.
Needs attention
High-impact changes to review
2
Unread
New market signals
2
Monitoring
Systems healthy
6/10
Next scan
Last 2h ago
On demand
Alerts · 4 market changes
2 unreadSubscription option and free-shipping bar added to hero products
Aurelle · aurelle.shop
Before
After
Copilot interpretation · Moving the hero product to replenishment revenue and lowering the first-order threshold — worth a test on your store.
An eight-dimension CRO audit of every rival
Each competitor gets the same audit your own storefront gets: homepage, PDP, trust, offer, cart, mobile UX, checkout readiness and CRO fundamentals, each scored 0–100 and weighted into one overall CRO score. The audit names top strengths and weaknesses, what they do better than your store, what your store does better, recommended actions with evidence, and ideas to test — generated by AI from real scan data, with hard rules against inventing anything.
- Weights: PDP 25%, cart 18%, homepage 15%, trust 14%, offer 13%, mobile 8%, checkout 7%
- The AI overall score is clamped within ±30 of a deterministic heuristic reference; if AI is unavailable, the heuristic audit runs and is labelled “Heuristic”
- Competitor traffic, revenue, conversion rate and AOV are not publicly measurable and are shown as unavailable rather than estimated
AI CRO Audit — aurelle.shop
AI auditOverall CRO score
Generated by AI from real scan data. Clamped within ±30 of the heuristic reference.
Weights: PDP 25% · cart 18% · homepage 15% · trust 14% · offer 13% · mobile 8% · checkout 7%
What they do better than your store
- Subscription offer on the hero PDP with visible savings
- Free-shipping threshold announced above the fold
- Reviews with photos directly under the price
What your store does better
- Sticky add-to-cart on mobile product pages
- Cart drawer with upsells and payment badges
- Returns and delivery info on every PDP
Recommended actions for your store
Test a subscribe-and-save option on the serum PDP
Their hero product now sells on replenishment; yours sells once.
Evidence: offer_messaging added on aurelle.shop · Subscribe & Reward module available
Announce the free-delivery threshold above the fold
They lowered the first-order barrier; your threshold only appears in the cart.
Evidence: free_shipping_bar added · Cart Rewards milestone already configured
Everything Comver reads from a rival storefront
The scanner renders each storefront in a real browser — desktop 1280×800, plus an iPhone-class mobile context — dismisses cookie banners and popups, and extracts structured data with the same pipeline that audits your own store.
Homepage
Title, meta description, hero text and the primary call to action — the first promise the store makes.
Product page
Add-to-cart, reviews, shipping info, upsells, urgency, sticky add-to-cart, payment badges and returns info on the first visible PDP.
Cart
Cart type (drawer or page), free-shipping bar, cart upsells and trust signals — after a best-effort add-to-cart.
Offer signals
Bundles, urgency, volume discounts, gift with purchase, loyalty, discount codes and subscription incentives.
Trust signals
Reviews, payment badges, shipping and returns, FAQ, about, social, contact and UGC.
Catalog & technical
A sampled catalog from /products.json, platform confirmation, status code, load time, HTML size, script and image counts.
From a domain to the first alert
- 1
Add a competitor
Enter a public domain, choose a monitoring cadence and the alert types you care about, and click “Verify & start tracking”. Comver confirms Shopify and starts the first scan.
- 2
The scan runs
Structured extraction, full-page screenshots of home, PDP and cart (plus mobile), the eight-dimension AI CRO audit and the category leadership board. The first scan is the baseline.
- 3
Detect and rank
From the second scan onward the two latest snapshots are diffed. Each real change is interpreted, scored for relevance and given a priority; high and medium become alerts.
- 4
Respond
Read the before / after, the Copilot interpretation and the recommended response. Send it to the Action Plan, draft an A/B test, or mark it resolved. Re-scan on demand whenever you like.
Frequently asked questions
Public Shopify storefronts only. Comver confirms Shopify via HTML signatures, response headers and live /products.json and /cart.js probes; if it cannot confirm, the store is refused rather than tracked with guesses. Up to 10 competitors per store, with up to 3 selected as Primary for the side-by-side matrix.
Full-page screenshots of the homepage, a product page and the cart on desktop, plus the mobile homepage and PDP, and structured data: hero and CTA copy, a sampled catalog, PDP elements (reviews, upsells, shipping info, sticky add-to-cart, payment badges), cart type and upsells, the free-shipping bar, offer signals and trust signals.
It diffs the two latest completed snapshots deterministically — offer or trust signals added or removed, CTA or hero copy changed, PDP reviews, upsells, delivery info or sticky add-to-cart toggled, cart type or upsells changed, free-shipping bar added or removed, catalog growth. The AI then interprets intent, estimates a qualitative CRO impact, scores relevance 0–100 and sets a priority; only high and medium changes raise alerts.
No — and it says so. Those are not publicly measurable, so they are shown as unavailable rather than estimated. What is measured is the Comver CRO Score family: overall, homepage, PDP, trust, offer, cart, mobile UX, checkout readiness and CRO fundamentals, plus product counts and detected changes.
The first scan runs the moment a competitor is added, and you can trigger “Run scan now” or a storefront refresh at any time. Each competitor also stores a monitoring cadence — Daily, Twice weekly or Weekly; scheduled scans on that cadence are coming with the Beta.
It lands in the Alerts priority queue with a severity, before / after storefront previews, a Copilot interpretation, the potential business impact and a recommended response. High-priority alerts also appear on the AI CRO Copilot timeline and in the notification bell. One click on “Create response plan” turns it into an Action Plan recommendation, from which you can draft an A/B test or a change proposal.
No. There is no theme embed, script or extra Shopify scope — Comver only reads competitors’ public sites from its own scanner. You enable the Competition module (Beta) in Comver and add domains.
The prompts forbid inventing traffic, revenue, conversion or AOV, require every score to be justified by detected signals and every recommendation to cite competitor evidence and propose a testable adaptation. If AI is unavailable, a deterministic heuristic audit runs instead and is labelled “Heuristic”. AI scores are clamped to within 30 points of the heuristic reference, and impact language stays qualitative — validate with an A/B test before assuming revenue impact.
Know when a rival storefront moves — and what to do about it
Install Comver, enable Competition and add your first competitor domain. Verified Shopify, real screenshots, only real changes — in Beta today.
14-day free trial · Live on Shopify in minutes · Checkout stays in Shopify