Web Page Change Detector

A web page change detector watches HTML and copy, then alerts you when the substance moves. Substance is a number, a clause, a listing, a job. A new tracking pixel in the footer is not substance.

People search this phrase after a visual tool cried wolf. The overlay looked urgent. The page still said $29. They want a detector that reads.

HTML is the input, not the alert

Raw HTML diffs are honest and noisy. Timestamps, CSRF tokens, shuffled class names. You can filter some of that with ignore lists. You will never finish the list. AyeWatch uses the page as evidence and writes the change in English. The HTML is not what you paste into Slack.

Hexowatch and Visualping still help when the job is "show me the picture." Distill still helps when you already own selectors. The page change alerts guide is the method map.

Setup without a DOM lesson

Paste the URL. Write the rule. Pick the interval. Free Preview is Daily or slower, six lifetime runs, three topics, push and in-app. Pro is $9 a month. Paid adds Slack and webhooks. There is no "inspect element" step.

JavaScript-heavy pages can still fail to render a useful snapshot. If the public HTML is an empty shell, say so in the trial. Do not assume every SPA will read cleanly.

Use it on pages that hold a fact

Pricing. TOS. Jobs. Changelogs. Listings. Agency notices. Those pages have a fact you can name. Homepages with rotating campaigns are a bad first watch. Start where the fact lives.

If the first alert names the fact, you picked the right detector class. If it sends a screenshot of a carousel, you did not. A web page change detector should survive a redesign of the header. If your current tool broke because a class name moved, you were detecting HTML, not the fact. Point AyeWatch at the same URL and name the fact again. If the summary names the price, you are done. That is a web page change detector doing the job the overlay kept missing. Name the fact. Ignore the restyle.