If you've ever caught yourself refreshing a page hoping to see something change, this guide is for you. Whether you're watching a competitor's pricing page, a job posting, a regulatory document, or a "back in stock" notice, the approach is the same: pick the page, pick what to watch, pick how often, and route the alerts somewhere you'll actually see them.
Step 1: Decide what kind of change you care about
Before picking a tool, get specific. Are you watching:
- A specific value — a price, a stock status, a version number, a single line of text?
- A section of the page — a pricing table, a changelog, a "what's new" block?
- The whole page — any meaningful edit anywhere?
The narrower the target, the fewer false alerts you'll get. A monitor that watches an entire homepage will fire every time someone updates a banner. A monitor that watches the .price element only fires when the price actually moves.
Step 2: Pick a tool that matches your needs
There are three common approaches:
- Browser extensions like Distill or Visualping's extension. Cheap, but only check while your browser is open and your device is on.
- Self-hosted tools like changedetection.io. Free if your time is free — you handle the server, Docker, updates, and downtime.
- Cloud monitoring services like PageChange, Visualping, or Wachete. You pay a small monthly fee and the service runs 24/7 in the cloud.
For most people watching more than a couple of pages, a cloud service is the right answer. You don't want to learn that your laptop being asleep cost you a flash sale or a regulatory deadline.
Step 3: Set up your first monitor
Walking through the setup using PageChange. The same steps apply to most cloud monitoring tools.
- Paste the URL. Any public page that doesn't require login works. The tool fetches a baseline so you can confirm the right content loaded.
- Choose the scope. Watch the whole page, or use a CSS selector to target one element. The visual selector picker lets you click directly on the element instead of writing CSS.
- Pick a check cadence. 15 minutes is a sensible default for most use cases. Hourly is plenty for stable pages. Daily is fine for things like terms of service or job posting roundups.
- Connect an alert channel. Email is always available. Slack, Discord, and Telegram each take a minute to set up via their webhook flows. Webhooks let you route alerts into any tool that accepts HTTPS POSTs.
- Trigger a manual check. Hit "Check now" once to confirm the monitor is capturing what you expect. Always do this before walking away.
Step 4: Decide how you'll handle alerts
This is the step most people skip. An alert that lands in your inbox at 2am with no clear action attached is just noise.
- Route to the channel you actually watch. If your team lives in Slack, send alerts there. If you watch email, route there. Don't pile everything into a "monitoring" folder you never check.
- Match the channel to urgency. Price drops on flagship SKUs → Slack with a direct mention. Routine content updates → daily digest email.
- Set quiet hours if you can. Most tools support muting non-critical alerts outside work hours.
Common mistakes to avoid
- Monitoring entire dynamic pages. If a page rotates banners or pulls in recommendations, you'll get false alerts constantly. Use a CSS selector.
- Setting cadences faster than you need. 5-minute checks eat your monthly quota and don't make you noticeably faster than 15-minute checks for most use cases.
- Forgetting to confirm what was captured. Always run a manual check after setup. Selector picks the wrong element more often than you'd think.
- Trying to monitor login-walled pages. Cloud monitors usually can't get past authentication. If the page is behind a login, you'll need a self-hosted tool with browser automation.
What about pages that require JavaScript to render?
Some single-page apps build their content client-side in the browser, so a server-side fetch only sees an empty shell. If you're watching a price or status that only appears after JavaScript runs, you'll need a tool with a real browser engine. The fastest way to find out whether a page works with a given tool is to add it on a free plan and look at the first snapshot.
How much does this cost?
Most cloud monitoring tools have a free plan that covers a handful of monitors. PageChange's free plan includes 3 monitors and 5,000 checks per month, which is enough to watch a few competitor pages or a couple of important documents at hourly cadence. Paid plans start around $15–$20/month for tens of monitors.
Where to go from here
Pick one page you actually want to know about — a competitor's pricing page, a product you want to buy on sale, a regulatory document. Set up a monitor with a 15-minute cadence and a Slack or email alert. Let it run for a week and see what you learn.
If you want to skip the comparison-shopping, you can start with PageChange free — no credit card, 3 monitors, all alert channels included. Or read the docs for a deeper look at how monitoring, selectors, and alerts work.