Monitor webpage for changes in six practical steps

To monitor a webpage for changes, you need more than a reload button and a good memory. This guide walks through the six settings that decide whether a monitor tells you something useful or buries you in noise: the URL, the element, the schedule, the sensitivity, the ignore rules and the alert channel. Each step takes a minute in WebsiteChange, and the choices you make here are the same ones that matter in any careful setup.

Start watching See pricing

Overhead view of a white desk, two printed proofs of the same page with one cell circled in red pencil and a clipped stack of earlier printouts on the left, reading glasses and a red ink stamp on the right

Step 1. Paste the exact URL you care about

Start with the most specific address you can find. A competitor's pricing page is better than its home page, and a single product page is better than a category listing that reshuffles every hour. If a page has regional versions, pick the one your buyers see.

WebsiteChange fetches the public page, renders it the way a browser would, and stores three things on every check: the visible text, the HTML structure and a full-page screenshot. That first snapshot becomes the baseline every later version is compared with.

Step 2. Pick the element that matters

Most pages mix the part you care about with parts you never want to hear about. Narrow the monitor to one element and the rest of the page stops producing alerts.

Click-to-select on the snapshot. Hover over the pricing table, the terms section or the job list, and click it.
CSS selector. Type a selector such as a table class or a section id when you know the markup.
Whole page. Leave the element empty when any edit matters, for example on a short policy page.

A narrow element is the single biggest noise reducer you have. A monitor on the plan cards of a pricing page ignores the blog teaser, the testimonial carousel and the footer links next to it.

Step 3. Choose a schedule that matches how fast you need to act

Check frequency is a business decision, not a technical one. Ask how quickly someone would act on the change.

Pricing pages of close competitors. Hourly on Starter, every 15 minutes on Growth, every 5 minutes on Business.
Product availability before a buying decision. Every 15 minutes or faster.
Terms of service, privacy policies, regulator guidance. Daily is usually enough.
Career pages and feature pages. Daily or weekly.

Every check counts toward the monthly check limit of your plan, so a daily schedule on slow pages leaves room for frequent checks where speed pays off.

Step 4. Set the sensitivity

Sensitivity decides how large an edit has to be before it counts. A low setting reports a single changed word, which suits contracts and price blocks. A higher setting waits for a meaningful amount of changed text, which suits long feature pages where a rephrased sentence is not news.

Step 5. Add ignore rules for the parts that always move

Even inside one element, some content changes on every load. WebsiteChange already filters dates, counters, rotating banners, cookie bars and tracking parameters. Ignore rules handle the rest of the page you have chosen.

Ignore a sub-element, such as a "people viewing now" counter inside a product block.
Ignore text that matches a pattern, such as a timestamp format.
Ignore a region of the screenshot for visual comparison.

Step 6. Decide where the alert goes

An alert nobody reads is worse than no alert. Send it where the person who acts already works.

Email for individuals and for Starter plans.
Slack, Microsoft Teams or a webhook on Growth and up.
Instant for high importance changes, a daily or weekly digest for the rest.

When a real change remains after filtering, an AI model writes a short summary, for example "Pro plan price raised from 79 to 99 USD per month; annual discount removed", and scores it low, medium or high. You can route only high importance alerts to a channel and leave the rest in the digest. More routing ideas are on the page about how to notify when website changes.

Tips for dynamic and script-heavy pages

Modern pages load prices with scripts, personalize banners and shuffle content blocks. A few habits keep these monitors clean.

For a full look at how filtering works, see website change detection, and for the screenshot side see the page change monitor.

Watch the rendered element, not the raw source. Because each check renders the page, prices loaded by scripts are captured.
Avoid elements that hold random order lists. If a list shuffles, watch the container that holds the fact you need, or add an ignore rule for order.
Check the first three versions. If the first days produce changes you would never act on, tighten the element or add a rule.
Use visual comparison for layout changes. The screenshot diff shows a moved button or a new badge that text alone misses.

What WebsiteChange reads and what it does not

We only read publicly reachable pages and respect robots.txt. We never log in on your behalf, never solve CAPTCHAs, and never bypass paywalls or access controls. Requests to each host are spaced politely. If a page needs a login to see, it cannot be monitored here.

Starter covers 50 pages, Growth 250, Business 1,000 and Enterprise 5,000. Compare the limits on the website change monitoring pricing page.

Yes. Click the element on the snapshot or enter a CSS selector, and only that element is compared between versions.

Nothing reaches you. If the only differences are noise that the filters remove, no summary is written and no alert is sent.

Yes. Every version is kept with a screenshot, a text diff and a visual diff for as long as your plan's history allows, as shown in website archive tools.

Start watching your first page

Paste a URL in the demo on the home page, see the first snapshot and a sample change summary, and pick a plan when you are ready.