Prices, both directions
A competitor cutting prices matters as much as one raising them, so both are reported. What direction decides is the wording — it is always stated, never left for you to infer.
They changed their pricing three weeks ago
Somebody usually finds out from a customer, in a negotiation, at the worst moment. Radar reads the competitor pages you choose on a schedule and tells you what moved — the day it moves, with the previous value still attached.
Included from the free plan. No card required.
Plans appearing and disappearing
A new tier, a dropped one, a rewritten headline, a changed positioning line, a page that stopped answering. Each with what it said before.
Unreadable is not empty
If a fetch hits a JS shell, a bot wall or a timeout served as 200, Radar records that it could not look — separately from what it found. It will not tell you a competitor deleted their pricing because one request went wrong.
How it works
Point it at the pages that state the offer
Pricing, plans, the main landing. Those are where a competitor commits to something in public and where a change is a real signal.
The first read is the baseline
It is not news, it is the starting point. From then on, every check is compared against the last state we actually managed to read.
Structured data outranks a guess
A price published in schema.org markup is the competitor's own machine-readable claim. A number scraped out of visible text is a guess, and a guess never raises an alert on its own.
You hear about it once
A price that keeps jittering between two values is one recurring story, not a notification every morning. Repeat noise is counted, not resent.
What it does not do
- It reads public pages, the same ones anyone can open. It does not get into anything closed, and it does not look up people.
- It does not explain why they changed the price. It tells you they did, and when, so you are not the last to know.
- It does not invent a number it could not read. An unknown stays an unknown.