7 min read
How to monitor a competitor's pricing page
The short answer
To monitor a competitor's pricing page, watch the page itself rather than a summary of it, narrow the watch to the plan names, prices, and feature lists, and check daily. When a change lands, compare the old and new version side by side, because a price rise often arrives with quieter changes to what each plan includes.
The price is not the only thing worth watching
Competitors rarely announce a pricing change. They ship it, and the page quietly starts saying something different. The number itself is the obvious signal, but it is often the least interesting one.
The changes that tell you more are the ones around it. A plan that quietly loses a feature. A usage limit that drops from unlimited to a cap. A new enterprise tier that appears above the old top plan. A free trial that turns into a demo request. Each of those tells you something about their strategy that the headline price does not.
What to watch on a pricing page
Watch the parts that carry meaning and ignore the parts that move on their own.
- Plan names and the number of plans. A new tier appearing is a strategy change.
- The price of each plan, monthly and annual. Annual often moves first.
- Feature lists and usage limits. This is where quiet repackaging shows up.
- The primary call to action. A shift from 'Start free' to 'Book a demo' is a move upmarket.
Set it up
Competitor pricing pages do not change often, so the setup should favour reliability over speed.
- Use the canonical pricing URL. If they have separate monthly and annual views driven by a toggle, monitor whichever one you compare against, and consider watching both.
- Say what you want to hear about, for example 'alert me when a plan price or a plan feature changes'.
- Check daily. A competitor's pricing page is not a race, and a daily check keeps the alerts meaningful.
- Send alerts to the channel your team already reads, so the change gets discussed rather than archived.
Reading a change properly
When the alert arrives, the useful question is not 'what number changed' but 'what did they stop offering'. Put the previous version next to the current one and read the feature lists first, then the price.
A snapshot history matters here. One change is a data point. Four changes over a year is a pricing strategy, and that is the thing worth taking to a planning meeting.
Is monitoring a competitor's public page allowed?
Reading a public web page is what a browser does every time anyone visits a site. Monitoring one is the same request on a schedule. The lines worth respecting are the ordinary ones: only fetch pages that are publicly readable without a login, fetch them at a polite rate rather than hammering the server, identify yourself honestly in the user agent, and respect robots.txt.
Anything behind a login, a paywall, or an account is not publicly readable, and should not be monitored.