How to monitor competitor website changes automatically

In this article, we'll show you how to set up automated competitor website monitoring — from picking the right pages to getting notified every time something visually changes.

Keeping tabs on competitors manually is the kind of task that quietly slips off the radar. The first week, you check their site every day. Then every other day. Then you forget for a month. When you finally come back, the pricing is different, the landing page has been rewritten, and the features page has new sections you've never seen. When exactly did all of that happen? No idea, because nobody saved the previous version. We went through this pattern ourselves and wrote about why manual screenshot folders stop scaling after a few days.

Automated monitoring fixes exactly this problem. Screenshots are taken on a schedule, each one is compared to the previous capture, and the only time you hear about it is when something actually changed.

Why text-based change alerts don't work for most competitor tracking

There are tools that monitor a page's HTML and notify you when text changes. For certain tasks, that works fine — for example, if you need to know when a competitor updates their terms of service (we covered this in a separate article on tracking ToS and privacy policy changes).

But most competitor website changes are visual — a new banner, a rearranged page layout, swapped content blocks, updated illustrations. Text-based monitoring misses all of this. It sees the code, but not what the page actually looks like to visitors. We collected six types of website changes we caught with automated screenshots — most of them wouldn't have shown up in an HTML diff at all.

This is the difference between monitoring source code and monitoring what users actually see. A screenshot captures the second — the real state of the page at a specific moment.

Which competitor pages are worth monitoring first

Monitoring an entire competitor website is a bad idea. You'll get dozens of alerts from banner rotations, dynamic content, and random A/B tests. Instead, pick 5-10 pages that actually reflect the competitor's strategic decisions.

We broke this down in detail in our article on which competitor pages to monitor, but here's the short version:

Pricing page — the most informative one. Any change in pricing directly reflects business strategy. A competitor raises their starter plan from $9 to $12? Worth knowing. They add a new enterprise tier? That tells you where they're heading. We described a practical approach to this in our guide to monitoring SaaS pricing pages.

Homepage — usually reflects current positioning. When a competitor changes their headline from "Fast screenshots" to "Enterprise-grade visual testing," that tells you something about a target audience shift.

Feature pages and changelog — show what the competitor is shipping and what they consider significant enough to put on the website.

Ad campaign landing pages — if you know the URLs of a competitor's landing pages (from ad research tools like SpyFu), monitoring them shows you how the messaging and offers shift from week to week.

How to set up automated monitoring: a step-by-step process

Let's walk through the setup with a concrete example. Say you work at a SaaS company and want to track three competitors — specifically their pricing pages and homepages.

Step 1: Collect your URLs. Sounds obvious, but verify that the URL doesn't redirect. Some sites show different pricing versions depending on the visitor's region — make sure you're monitoring the right one.

Step 2: Pick a screenshot frequency. For pricing pages, once a day is usually enough. A homepage can be checked weekly — it changes less often. If you're monitoring promo landing pages during an active competitor campaign, bumping the frequency to several times a day makes sense.

Step 3: Handle popups. Nearly every website greets first-time visitors with a cookie banner, a newsletter popup, or a welcome modal. If you don't dismiss them, your screenshot will show the banner instead of the actual content. In Snapshot Archive, the click selector handles this — it clicks the dismiss button before taking the screenshot. We also covered cookie banner handling in more detail in a dedicated guide.

Step 4: Decide what to capture — full page or a specific element. A full-page screenshot works well for landing pages and homepages where you want the big picture. But for a pricing table or feature grid, it's better to use clip to element — capturing a specific block by CSS selector. This cuts out the noise from headers and footers, so you only see the content that matters. We compared both approaches in our full page vs viewport screenshots article.

Step 5: Enable visual diff and notifications. After the first screenshot, every subsequent capture is automatically compared to the previous one. If something changed, you get a notification. If nothing changed, silence. We explained how pixel-by-pixel comparison works in our visual diff article, and if you ever wonder why a page that looks the same still shows 22% changed, we dug into what the change percentage actually means in a separate piece.

What to expect in practice: false positives and how to deal with them

Competitor monitoring in practice is messier than it sounds. Here's what you'll run into:

Dynamic content. Blog feeds, news tickers, counters like "X customers trust us" — these change constantly and generate false alerts. The fix is to monitor specific pages (pricing, features) rather than a blog or a homepage loaded with dynamic widgets, or use clip to element to isolate just the stable part of the page.

Layout shifts. A promotional banner appears in the navigation and pushes the entire page down by 40 pixels. Technically nothing meaningful changed, but the diff screams that everything did. We ran into this exact problem when monitoring an Amazon product page and wrote about how layout shifts break price monitoring and what to do about them.

Competitor A/B tests. If a competitor is running a split test, you may see different page variants with each screenshot. This looks like constant changes, but it's usually easy to spot — the diff will show the same two variants alternating back and forth.

Cookie walls and geo-targeted content. Some sites serve different content based on IP or cookies, which means your scheduled captures can look inconsistent for reasons that have nothing to do with the competitor actually changing anything. Setting up custom cookies helps stabilize the session so each screenshot sees the same version of the page.

We covered all types of false positives and how to handle them in our article on false positives in screenshot monitoring.

Real-world example: monitoring pricing pages of three SaaS competitors

Here's a concrete scenario. Say you're launching a product in the project management space and want to keep an eye on the pricing pages of three competitors.

You set up three URLs for monitoring, configure daily screenshots, add a click selector to dismiss cookie banners, and enable clip to element to capture just the pricing table.

A week later, you get your first notification: one competitor removed their free tier. The diff shows exactly what changed — the "Free" column is gone, and "Starter" now begins at $8 instead of $5. A couple of weeks later, another competitor adds an "Enterprise" tier that wasn't there before.

That's the kind of data you can actually act on — adjusting your own pricing based on what competitors are doing right now, not what you remember from three months ago. We described a similar approach with real data in our article on e-commerce price monitoring.

What not to monitor (and why)

Not every page is a good fit for screenshot monitoring. A few types tend to create more noise than value:

Blog pages. These change with every new post, which turns your diff into a stream of "something changed" alerts that all mean the same thing. If you need to know when a competitor publishes something new, an RSS feed or a text-based monitor is a better fit.

Pages with heavy animation. Each capture lands on a slightly different animation frame, so the diff will light up even though nothing meaningful has changed. When there's static content on the page that you actually care about, clip to element lets you isolate it and skip the animated parts entirely.

Dashboards and pages behind authentication. Screenshot monitoring works with publicly accessible pages, and anything behind a login needs a different approach — usually custom cookies or a separate authenticated session setup.

Getting started: a quick checklist

Here's the minimum you need to begin. Pick 3–5 competitors and, for each one, choose 2–3 pages that actually reflect strategic decisions — pricing, homepage, and maybe a feature page or an active landing. Set the capture frequency to once a day for pricing and promo pages, weekly for the homepage, and add a click selector so cookie banners don't cover half the screenshot. If you're tracking a pricing table or a specific block, clip to element keeps the diff focused on what matters and cuts out header and footer noise. Finally, turn on notifications — email works for most people, webhooks are there if you want to pipe alerts into Slack or a dashboard.

Snapshot Archive's free plan lets you monitor 3 URLs — enough to try this on the pricing pages of your two main competitors and see whether the approach works for your niche.

If you already know which pages you want to track, you can get started in a couple of minutes. And if you're not sure where to begin, we put together recommendations in our detailed guide on choosing pages to monitor.