Guide

Website monitoring explained: uptime, performance and change monitoring

PageWatch team · November 11, 2026 · 4 min read

Short answer: "Website monitoring" means three different things. Uptime monitoring checks that a site answers (your own site, every minute). Performance monitoring measures how fast and healthy it is for visitors. Change monitoring watches what a page says (often someone else's page) and tells you when the content changes. They use different tools. If you're waiting for a restock, a new job post or a policy change, you want the third.

1. Uptime monitoring: is it up?

An uptime monitor requests a page every minute or few minutes from several locations and alerts you when it fails: no answer, a timeout, or an error status. HTTP status codes tell the story: the 2xx range means success, 4xx client errors (like 404 Not Found), 5xx server errors (like 500 or 503).

Who it's for: anyone running a website or an API. What to watch: your homepage, login, checkout, API health endpoint. Typical alert: "example.com returned 503 from 3 locations."

2. Performance monitoring: is it fast and healthy?

Performance monitoring measures load time, Core Web Vitals, errors in the browser and slow backend calls. It comes in two flavours: synthetic tests (a robot loads the page on a schedule) and real-user monitoring (a script measures real visits).

Who it's for: teams responsible for a site's conversion and SEO. Typical alert: "Checkout got 40% slower after Tuesday's release."

3. Change monitoring: did the content change?

Change monitoring reads a page on a schedule, compares the content with the previous check and tells you what changed. It's the only kind that cares about meaning: a price, a stock status, a deadline, a sentence in a policy.

Who it's for: shoppers, job seekers, researchers, marketers watching competitors, compliance teams, anyone waiting for something to appear online. What to watch: product pages, careers pages, terms and policies, competitor pricing, official notices, documentation. Typical alert: "Size 42 is back in stock" or "Section 7 of the terms was rewritten."

How change monitoring works

  1. Fetch the page (respecting robots.txt).
  2. Extract the text, optionally just one part (a CSS selector like .price).
  3. Compare with the previous version, line by line.
  4. Decide whether the change matters: a new timestamp shouldn't trigger an alert, a price change should.
  5. Notify with the lines that changed, and keep the history.

Step 4 is where tools differ most. Older tools alert on any change and leave you to filter. Newer ones let you set conditions (keywords, numbers) or, like PageWatch, describe what you're waiting for in plain words and have an AI model judge each change against it.

Which one do you need?

You want to know… Type Check every…
If your site is down Uptime 1–5 minutes
If your site got slower Performance Every deploy, or continuously
When a product is back in stock Change Hour
When a company posts a job Change Hour to day
When terms or prices change Change Day
When a competitor launches a page Change (sitemap) Day to week

Setting up change monitoring well

  • Watch the narrowest part that answers your question. A selector on the price or the job list removes most false alerts.
  • Write the condition as you'd say it. "Below $80", "mentions remote", "refund policy changes".
  • Pick a sensible frequency. Hourly for restocks; daily for policies; weekly for competitor pages. Checking more often than you need wastes everyone's resources, including the site's.
  • Respect the site. Public pages only, robots.txt honoured, no logins or paywalls. Many sites publish sitemaps, whose <lastmod> dates hint at changes; archives like the Wayback Machine capture pages but with a lag of hours and gaps.
  • Keep the history. The lines that changed, with dates, are useful later.

Common mistakes

  • Using an uptime tool to watch content. It will tell you the page is "up" while the price changes.
  • Watching the whole page. Rotating banners and timestamps produce noise.
  • Alert fatigue. Ten emails a day get ignored. Prefer one digest.
  • Watching pages you shouldn't. Logged-in areas and pages blocked by robots.txt are off limits.

FAQ

Is website change monitoring legal? Reading public pages is generally fine; respect each site's robots.txt and terms, and never get around logins or paywalls.

How often should I check a page? As rarely as still gets you there in time: hourly for stock, daily for most other things.

What's the easiest way to start? Paste a page into PageWatch, optionally add a condition, and choose daily checks. Three pages are free. More detail in how to check when a website was last updated.

Sources