Website Update Alerts

Website update alerts tell you the moment a page you care about ships a real change. "Real" is the word that matters. A new hero image is not an update you needed. A new price is.

Most alert products cannot tell those apart. They hash the HTML or the pixels and fire on both. You mute the channel. The next real update dies in the same mute.

Ask for the change in English

Name the fields. Price. Plan names. Availability. A clause in the TOS. A job title. AyeWatch reads the page and writes a short summary. That is the alert. You should not need a second tab to learn what happened.

Visual diffs still help when design QA is the job. For everyone else, a sentence beats a heatmap. See alert fatigue if your current tool already trained you to ignore it.

Speed versus noise

Daily is fine for a policy page. Six hours is the Pro default for pages that can move on a weekday afternoon. ASAP is Max and Ultra. Free Preview is Daily or slower, six lifetime runs, three topics, push and in-app. Do not buy ASAP for a page that changes twice a year.

Paid adds email, Slack, Discord, and webhooks. Pro is $9 a month and 50 topics. That is the usual cutover from the free proof.

What not to expect

AyeWatch is not a design review tool. It will not circle a two-pixel shift in a button. It will not buy the concert ticket. It will not crawl a login wall. It will tell you when the public page you named actually updated in the way you described.

Paste the URL you already babysit. If the first alert is a change you would have screenshot for a teammate, keep going. Website update alerts fail in two ways: they never fire, or they fire so often you stop reading. Semantic rules fix the second. The first is usually a URL that never actually changes, or a check interval slower than the event you care about. Match the interval to the page. A quarterly TOS does not need ASAP. A restock page might.