Key takeaways
- A page change detector works on one URL, re-reads the page on a schedule and reports the difference from the stored copy.
- AyeWatch takes a rule written in plain English, reads the rendered page and names the change in a short summary.
- It cannot see content behind a login, keep a visual archive, replace uptime monitoring, or open pages that block automated visits.
A page change detector is a monitor that re-reads a public web page on its own schedule and reports what differs from the copy it saw last time. On AyeWatch you describe the change in plain English, and the alert arrives as a short summary of the delta rather than a screenshot or a wall of markup.
Most people arrive through one stubborn page: a pricing table, a stock line, a job board, a policy document. A detector turns that refresh habit into something a machine handles while you sleep.
What a detector is looking at
A detector works on a URL you paste, not on a search phrase. It loads the page, compares the new read with the stored one, and decides whether the difference is the kind you asked about. That last part separates a useful detector from a noisy one.
Ask one question before you add anything: which sentence on this page would make me act? If the answer is a number, watch the number. If it is a clause about data retention, watch that section, not the whole document.
How to set one up in plain English
- Copy the address of the page that carries the fact, not the home page or the category page.
- Write the rule the way you would say it to a colleague: "tell me when the price on this page changes", or "tell me when the page starts taking applications". AyeWatch reads the rendered page, so there is no selector.
- Choose where the alert lands. Push and the in-app feed come with every plan. Email, Slack, Discord, webhooks and the API need a paid plan.
- Read the first alert before you trust the second. If it fired on a cookie banner, tighten the wording and let it run again.
The missing selector matters more than it sounds. Sites redesign navigation and move a price into a differently built table. A rule about meaning survives that; a CSS path often does not.
What comes back
| The rule you write | What the alert should tell you |
|---|---|
| tell me when the price changes | the old price, the new price, and which plan it covers |
| tell me when a new job appears | one line naming the role that was added |
| tell me when this page drops the word beta | the sentence where it went missing |
A summary is a triage tool. You decide in seconds whether the page deserves a click, and the alert names the change, so you are not opening a diff to find out.
What it cannot see
Four limits to know.
- Anything behind a login. AyeWatch does not sign in for you, so a dashboard or a members-only page is out of reach.
- Pixels. It reports words and data, and keeps no visual archive. If the evidence you need is a screenshot trail for counsel, a visual diff tool is the right purchase.
- Server health. This is not uptime monitoring. A page can return 200 and still be useless.
- Pages that only render for a signed-in browser, or that sit behind bot protection. Test the exact URL before you build a routine around it.
When a screenshot tool wins
Visualping and Distill are better when the artifact is the point: a highlighted screenshot for a legal file, or one exact DOM node inside a complex app. AyeWatch is built for pages that hold a fact, and returns the sentence you would have written after reading the diff.
Cost and the first test
Paid plans start at $9 a month, billed in monitoring credits, and the web app gives a 7 day trial. Start with the page that already costs you attention; that comparison survives a second week.
FAQ
Does a detector need a CSS selector?
No. AyeWatch takes a rule in ordinary words and reads the rendered page. Selector tools fit better when you must watch one exact element inside a busy app.
Can it watch a page that needs a login?
No. It reads public pages only, so anything behind an account, a paywall or a member area stays invisible to it.
How much does AyeWatch cost?
Paid plans start at $9 a month, billed in monitoring credits, and the web app offers a 7 day trial.
Frequently asked questions
Does a detector need a CSS selector?
No. AyeWatch takes a rule in ordinary words and reads the rendered page. Selector-based tools are still the better fit when you must watch one exact element inside a busy application.
Can it watch a page that needs a login?
No. It reads public pages only, so anything behind an account, a paywall or a member area stays invisible to it.
How much does AyeWatch cost?
Paid plans start at $9 a month, billed in monitoring credits rather than as a flat fee, and the web app offers a 7 day trial before you commit.
Sources
- AyeWatchAyeWatch
- AyeWatch pricingAyeWatch
- Web page change monitoring: tools comparedAyeWatch



