Competitor tracking

See what your competitors changed, and when they changed it

Pricing pages, homepages and campaign landing pages are where strategy becomes visible. Capture them on a schedule and you get a timeline of your market instead of a vague sense that something moved.

Why manual competitor checks stop working

You notice late

A price moved six weeks ago. You found out when a prospect mentioned it in a call, which is six weeks of losing deals you did not understand.

Checking is nobody's job

It gets done enthusiastically for a month, then whenever someone remembers, then not at all.

You cannot show what changed

Without a before image, an observation is an assertion. Nobody can act on it with confidence.

You only see your own country

Competitors run different pricing and messaging by market. Your browser shows one of them.

Personalisation distorts the picture

Repeat visits, cookies and A/B tests mean the page you see may not be the page a new prospect sees.

Findings live in DMs

Screenshots pasted into chat are gone in a fortnight. There is no accumulating picture.

Standing up a competitor watch

Ten minutes of setup per competitor buys you a permanent, dated record of their public moves.

  1. 1

    Pick the pages that reveal decisions

    Pricing, plan comparison, homepage, key product pages and any live campaign landing pages. These are where a company's strategy is forced into public view.

  2. 2

    Capture daily, from the right countries

    Daily full-page captures at a fixed width, routed through the locations your buyers are in, so you record the offer each market is being shown rather than only your own.

  3. 3

    Review the timeline, not each capture

    Scan the history for the days where the page visibly changed. Tag captures by competitor so a quarterly review is a filter rather than an archaeology project.

Turning captures into competitive intelligence

Collecting competitor screenshots is easy. Getting anything useful out of them is a discipline, and most teams fail at the same three points: they watch too many pages, they cannot tell real changes from noise, and nobody ever looks at what was collected.

Watch the pages where decisions surface

A company's website is mostly stable prose. The parts that move are the parts where a decision has been made, and there are fewer of them than you would think.

  • Pricing and plan comparison pages. The single highest-signal page. Price changes, tier renames, limits quietly adjusted, features moved between tiers.
  • The homepage hero. Positioning changes show up here first: which audience they are addressing, which capability leads.
  • Campaign landing pages. The most perishable and often the most revealing, because they show what they are actively spending to promote. They also disappear without trace, which is why capturing them matters.
  • Careers pages. Underrated. Roles being hired describe the roadmap more honestly than any product page.

Three or four pages per competitor is plenty. Twenty pages produces a volume of captures nobody reviews, which is the same as capturing nothing.

Removing the false positives

The reason competitor tracking gets abandoned is usually that every capture looks different, so no capture means anything. Almost all of that variation is self-inflicted.

Fix the viewport and scale so responsive breakpoints stay constant. Strip consent banners and ads, which otherwise rotate on every load and dominate the image. Pin the capture location so you are not alternating between two countries' pricing. Where the page has a lot of unrelated churn, capture the pricing table alone and let the rest of the page change without bothering you.

Geography is usually the missed variable

Any competitor selling internationally is showing different prices, currencies and often different messaging by market. Watching from a single connection gives you one slice of their strategy and quietly hides the rest — including, frequently, aggressive pricing in a market you are also trying to win.

Running the same page as two or three schedules from different locations costs a little more allowance and routinely turns up the most actionable findings.

Make somebody look at it

The failure mode is a beautiful archive nobody opens. Put a recurring half-hour in the calendar — fortnightly is enough — to scan the timelines for the days where something visibly moved. Because captures are dated and evenly spaced, this is a scanning exercise rather than an investigation, and the changes that matter are usually obvious at a glance.

When you do find something, you have the before and after images to show, which is the difference between "I think they dropped their entry price" and a dated pair of screenshots that ends the discussion.

Neighbouring uses of the same setup

Once the schedules exist, extend them. Capturing how partners and resellers present your product is brand monitoring; keeping the same captures as a long-term record is web archiving. It is the same mechanism pointed at different pages.

FAQ

Questions about this use case

Is it legal to screenshot a competitor's website?

Capturing publicly accessible pages is ordinary browsing, automated. That said, how you may use what you collect depends on copyright, database rights, the site's terms and your jurisdiction — take your own advice before republishing anything. Our acceptable use terms prohibit bypassing access controls or placing abusive load on a third-party site.

How often should I capture a competitor's pricing page?

Daily is the usual choice: frequent enough to date a change to within a day, cheap enough in capture allowance to run across several competitors. Move to hourly only for a specific event such as a launch or a sale period.

Can I see prices as customers in another country see them?

Yes. Captures can be routed through a chosen location, so you record the currency, price and messaging shown to visitors in that market rather than the version your own connection receives.

Where does a capture come from?

From our own capture servers, as an ordinary visit to a public page - and, when you choose a country, from an address in that country supplied by one of our proxy providers. It does not come from your company's network. We do not bypass logins, paywalls or CAPTCHAs, and captures respect the load limits described in our acceptable use terms.

Can I capture just the pricing table rather than the whole page?

Yes. Element capture with an XPath selector isolates a single component, which makes visual comparison far easier when the surrounding page changes for unrelated reasons.

How do I avoid A/B tests looking like real changes?

Capture consistently and look for changes that persist across several days. A variant that appears once and vanishes is a test; a change that holds is a decision. A fixed viewport and location remove the other common sources of false differences.