Competitor website monitor
The loop that answers this question directly. In build; not on sale yet.
Solutions · by problem
What changed on my competitors' websites?
Your rival launched a new range. You heard about it from a customer. The competitor website monitor is in build: it will read the sites you choose on a cadence you set and list what changed since the last run, each change linked to its page. It is not on sale yet.
Answer in buildWhat changed since the last run
- ChangedRival A · pricesHouse blend 1kg: 24.00 → 21.50 GBP, read from product data
- NewRival A · offersHomepage banner: free delivery on first order
- NewRival B · pages/subscriptions/office — new page in sitemap
- Not checkedRival C · pagesSitemap partly unreadable this run — no page marked as removed
The problem
What owners say.
- I only found out they'd launched that range because a customer told me.
- Did they put their prices up, or was that always there?
- They seem to add a new page every month. What are they writing about?
- I used to check their site every week. I stopped.
Composite phrasings of a common problem, not quotes from named customers.
Why it is hard
Why checking by hand fails.
Checking rival sites by hand is dull, so it stops. When you do check, you compare the page with your memory of it.
The monitor keeps a snapshot on each run and compares it with the last. "I think they changed something" becomes a list: these pages are new, these went, this price moved, this promotion started.
Some changes read more reliably than others. A sitemap lists a site's pages. Product structured data carries prices in a fixed format. Promotions sit in page text and need reading in context. The monitor is built in that order.
The limits. Nothing runs for customers today. When it ships it reads public pages only, so a price behind a login will not show, and it respects each site's robots rules.
Until then, the free Insight Report gives you a dated reading of your rivals' sites. That reading is the baseline any later change is measured against.
What we read
Each source, and the code that reads it.
Every source names the module in our code that reads it. A source marked in build does not run for customers yet.
- Each rival's sitemapPages added and removed since the last run.
src/lib/firecrawl.ts - Product structured dataPrices published in a fixed format on product pages, compared run to run.
src/lib/firecrawl.ts - Pages you pickOffers, promotions and messaging on the pages you choose to watch.
src/lib/firecrawl.ts - Snapshot historyEach run stored and compared with the last, on the same pattern as the live continuous assessment.
src/lib/assessment/store.ts
What you get
What you get back.
- A 'what changed' feed per rival, each change linked to the page it came from
- New and removed pages, price moves and promotions, kept apart so you can scan them
- A digest by email, on the cadence you set
Today and in build
What runs today, and what is in build.
Live tools run now. Loops in build will answer it again on a cadence you choose. They are not on sale.
Where it comes up
Industries that ask this.
Each industry page puts the problem in that trade's terms.
FAQ
Questions about “What changed on competitor sites”
Can I turn the monitor on today?
No. It is being built and does not run for customers yet. The loops page has a link to hear when it ships.
How often will it check?
On a cadence you choose when you turn it on. Each run is compared with the last.
Will it read every page on a rival's site?
It reads the sitemap for new and removed pages, product data for prices, and the pages you pick for offers and messaging. It respects each site's robots rules.
What can I do in the meantime?
Run the free Insight Report with your rivals named. It records their sites as they stand now, the baseline any later change is measured against.
Name the rivals you lose to.
The free report reads your site beside theirs, five buyer types on one rubric. No account and no card to start.