Guides
How to get alerts when a website changes, in five steps
No code, no selectors. Open the page as a stranger sees it, describe the change, pick a channel and test the first alert.
Here is how to get alerts when a website changes, and it takes about five minutes. None of it requires code. The steps below assume you have one page in mind, the kind you check by hand because nobody will tell you when it moves.
Step 1: open the page the way a stranger sees it
Use a private window. If the content still appears, a monitor can read it. If it asks you to sign in, stop: no watcher can see that version, and you need a public page such as a changelog, a status page or an announcement post instead.
Copy the address from that private window. This matters more than it sounds, because a URL copied while signed in can include a session parameter or land on a personalised view.
Step 2: write the change as a sentence
Describe what you want to hear in plain words. Two ingredients make it work.
- Where to look: "the pricing table", "the open roles", "the changelog".
- What counts: "a price rises", "a new role appears", "an entry mentions a breaking change".
Put a number in when a number is the point. "Tell me when the annual plan passes $2,000" is testable. "Tell me if it gets expensive" is a feeling, and the page does not contain feelings.
Step 3: choose where the message lands
Push notification is fastest and suits one person. Email leaves a record. A shared channel such as Slack or Discord suits a team. If you run scripts, a webhook lets the change start a job of your own.
On AyeWatch, push and the in app feed come with every plan. Email, Slack, Discord, webhooks and API access need a paid plan, and paid plans start at $9 a month after a 7 day trial.
Step 4: let one check run, then read it
The first alert is a test. Does the summary name what moved? Does the link open the right page? Is the wording too broad, so a cookie banner would set it off? Adjust the sentence now, while you still remember what you meant.
| If the first alert is | Change this |
|---|---|
| Too vague | Name the section and the movement |
| Too frequent | Narrow the region |
| Silent on a page that moves | Point at the part that actually changes |
| Missing entirely | Check the page loads without a login |
Step 5: set a review reminder
Once a quarter, open the list and ask two questions. Has this page produced anything useful? Does anyone still act on it? Pages retire, projects end and competitors get acquired. A short list that fires beats a long list that nobody reads.
What happens when it fires
You get a short summary of the change and a link. What you do next is your call: read the clause, check the price against your budget, forward it to whoever owns the relationship. The tool does the watching. The judgment stays with you.
A short list to start with
If you are unsure what to watch, three pages cover most beginnings. A pricing page, because numbers move without an email. A status page, because an incident changes what you can promise customers. A career page, because roles appear and close in silence. Watch those for a month, then add the one page that annoyed you most this week.
FAQ
Do I need to know any code?
No. The condition is a sentence, not a selector. Code only enters the picture if you want a webhook to trigger your own automation.
Can I watch a page that needs a login?
No. Watchers read the public copy of a page. Look for a public changelog, status page or announcement instead.
What does it cost to start?
AyeWatch gives a 7 day trial on the web, and paid plans start at $9 a month, billed in monitoring credits. Pushing alerts to your phone and keeping a feed are included on every plan.