Website change alert that reaches the right people
An alert is only useful if it lands where your team already works and says enough to act on. WebsiteChange sends each website change alert to email, Slack, Microsoft Teams or your own webhook, right away or bundled into a digest, and only for changes that pass the importance level you set.
Four channels, one setup
Pick one channel or several for each monitor or for a whole workspace.
Starter includes email alerts. Growth, Business and Enterprise include email, Slack, Microsoft Teams and webhooks. The payload format for webhooks is described on the website change monitoring api page.
- Email goes to any seat in the workspace, one alert per change or one digest per period.
- Slack posts into the channel you choose, so pricing changes land next to the team that reacts to them.
- Microsoft Teams posts into a team channel in the same way.
- Webhook sends a JSON payload to your own endpoint, ready for a CRM, a ticket queue or an internal dashboard.
Instant alerts or a calm digest
Some changes need a reply today. A competitor that cuts its price on a Friday afternoon should not wait until Monday. Other changes are context, worth reading once a week with a coffee.
For each channel you choose between:
- Instant, sent the moment the change is detected and summarized.
- Daily digest, one message per day with every change from the last 24 hours.
- Weekly digest, one message per week, grouped by monitor.
A common setup is instant Slack posts for high importance and a weekly email digest for everything else. Your sales lead sees the price cut in minutes, and your product marketer reviews the copy edits on Monday.
Filter by importance, not by volume
Every real change gets an importance score of low, medium or high from the ai website monitoring layer. Each alert rule has a minimum importance.
- High only, for channels that should stay quiet unless something big happens, such as a price change, a removed plan or a new clause in a contract.
- Medium and high, for the people who own the page or the competitor.
- Everything, for a digest that doubles as a weekly reading list.
Filtered changes are never lost. They stay in the version history and show up in digests that include low importance, so you can review them later.
Route alerts per workspace and per team
A workspace holds its own monitors, seats and alert rules. Agencies use one workspace per client, larger companies use one per team or region.
- Starter has 1 workspace, Growth 3, Business 15 and Enterprise unlimited.
- Each workspace sends to its own Slack channels, Teams channels, email lists and webhooks.
- On Business and Enterprise, digests can be set per team, so legal receives its weekly policy digest, product marketing receives its pricing digest and neither sees the other's noise.
Routing follows the monitor, not the person. When someone joins or leaves the team, the alerts keep going to the same channel.
What every alert contains
An alert is meant to be read in ten seconds and acted on without opening five tabs.
Digests carry the same details for each change, grouped by monitor, with the highest importance at the top.
- A one-line summary of the change, for example "Pro plan price raised from 79 to 99 USD per month; annual discount removed".
- The importance score, low, medium or high.
- The monitor name and the page address.
- A link to the full diff with text and page change monitor highlighting.
- A screenshot thumbnail of the changed area.
- The time of the check that found the change.
Alerts in practice
A pricing analyst at an ecommerce brand watches the product pages of three retailers. Stock changes on a key product go instantly to Slack, and everything else arrives in a daily email digest.
A procurement team watches the terms pages of its ten largest vendors. Only high importance changes alert instantly by email, because a new clause on data use or liability needs a review before renewal.
A product marketing team watches competitor homepages, pricing pages and changelogs. Its Microsoft Teams channel gets medium and high changes, and the weekly digest covers the rest.
A developer team sends every change to a webhook that opens a ticket in its own tracker, with the diff link in the ticket body.
Website change alert questions
Starter includes email. Growth, Business and Enterprise include email, Slack, Microsoft Teams and webhooks. Business and Enterprise also add digests per team.
Yes. Choose a daily or weekly digest for any channel, and set the minimum importance that goes into it.
No. Dates, counters, rotating banners, cookie bars and tracking parameters are filtered out before a change can trigger an alert.
Yes. Each workspace has its own alert rules and channels, and on Business and Enterprise digests can be set per team.
Set up your first alert
Paste a public URL, see the first snapshot and the kind of summary your alerts carry. No card needed for the demo.