Website change alerts for a page you do not control
You cannot edit the competitor's pricing page or the supplier's terms, so the alert has to do the work. The condition you write decides whether it stays useful.
4 min read
Website change alerts exist for the pages you cannot edit. You have no account on the site, no access to its code and no way to ask the owner to tell you when something moves, so the only lever left is watching the public address and describing the change you want to hear about. That is the whole method, and the sentence you write is where it succeeds or fails.
AyeWatch is built around that shape of work. You paste a public URL, say in plain English what counts as a change, and it checks on a schedule and sends a short summary of what moved. Paid plans start at $9 a month, with a 7 day trial on the web.
A monitor sees the page a stranger sees
No tool can read the version of a page your browser shows after you sign in. A monitor fetches the public copy, the one a logged out visitor gets, and compares it with the previous copy. That is enough for pricing pages, changelogs, job boards, status pages, terms of service, regulatory guidance and supplier portals, which is most of what people actually want to watch.
The comparison is the other half of the job. Raw page diffing fires on a cookie banner, a rotating testimonial or a copyright year. AyeWatch compares meaning, so the footer changing from 2025 to 2026 can pass while a pricing tier disappearing does not. The filter is your sentence, so the sentence has to be specific.
What to write in the condition
Three parts make a condition that stays quiet and still catches the event you care about.
- Name the region. "The plan table", "the changelog entries", "the open roles in the Berlin office". A region gives the monitor something to ignore.
- Name the movement. "A plan is removed", "a new entry appears", "the price rises", "a role closes".
- Put a number in it when a number is what matters. "The annual price passes $2,000" is testable. "It gets expensive" is not.
| Page | Condition that holds up | Why it works |
|---|---|---|
| Competitor pricing | Tell me when a plan is removed or a listed price rises | Prices move in steps, and a step is easy to spot |
| Vendor status page | Tell me when a new incident is posted | Incident posts are dated entries, not prose |
| Terms of service | Tell me when the data retention section changes | Names the clause, so layout edits stay silent |
| Job board | Tell me when a solutions engineer role opens in Europe | One role and one region, both named |
| Docs changelog | Tell me when an entry mentions a breaking change | A phrase the page already uses |
Conditions that fail
"Tell me about any change" is the common mistake, and on a busy page it produces a daily digest you will stop reading by Friday. "Tell me if something important happens" fails the other way, because important is not a thing the page contains. Both are fixable by adding a region and a movement.
A condition aimed at a page behind a login cannot work at all. Point the alert at the public changelog, the status page or the announcement feed instead. The change you wanted is usually described there in the end.
Where the message lands
Push and the in app feed are part of every plan, and they suit one person who reacts. Email, Slack, Discord, webhooks and the API need a paid plan, and they suit a team channel, a record or your own automation. Pick the room where the answer will be read, not the one with the most settings.
Four steps to the first alert
Open the page in a private window first, so you know what the monitor will see, then copy that address. Add it to AyeWatch, give the topic a name you will recognise in a list of twenty, and write the condition with a region and a movement in it. Choose a channel, let the first check run, then read the result and tighten the sentence if the summary is vague. Billing runs in monitoring credits rather than a flat fee, so a burst of pages does not force a permanent upgrade, and plans start at $9 a month.
FAQ
Can I set an alert on a page I have no account for?
Yes, as long as the page loads for a logged out visitor. That covers most competitor, government and supplier pages. If the content sits behind a sign in, watch the public changelog instead.
Do I need to know CSS selectors?
No. The condition is a sentence about meaning. Selector based tools are the other route, and they are a reasonable choice when you want to be told about every byte that moves inside one element.
What does it cost?
Paid plans start at $9 a month, billed in monitoring credits, and the web app offers a 7 day trial. Push and the feed come with every plan.
FAQ
Can I set an alert on a page I have no account for?
Yes, as long as the page loads for a logged out visitor. That covers most competitor, government and supplier pages. If the content sits behind a sign in, watch the public changelog instead.
Do I need to know CSS selectors?
No. The condition is a sentence about meaning. Selector based tools are the other route, and they are a reasonable choice when you want to be told about every byte that moves inside one element.
What does AyeWatch cost?
Paid plans start at $9 a month, billed in monitoring credits, and the web app offers a 7 day trial. Push and the feed come with every plan.
Originally published on claudegpt.si