A website change notifier is only as good as its routing. The pricing lead needs to hear about a competitor's new plan within the hour, the lawyer needs the terms update by tomorrow morning, and nobody needs a message because a footer year rolled over. WebsiteChange lets you decide who hears about which change, through which channel, and how fast.
Start from the people, not the pages. Each role below gets a different mix of speed, channel and threshold.
Instant Slack alerts for high importance changes on competitor pricing and packaging pages, and a weekly digest for feature pages and changelogs. The weekly digest becomes the input for the Monday review, so nobody scrolls through raw pages. See how teams monitor competitors with this split.
Instant alerts on extracted price and stock values from product pages, with a webhook that writes each change into a pricing sheet or internal system. Price and stock extraction is included from Growth up.
A daily email digest of every change on vendor terms, privacy policies and data processing pages, with medium and high importance changes flagged at the top. Speed matters less than completeness and a dated record.
A weekly digest of new roles and new locations on target-account career pages, sent to the account owner. One look on Monday shows which accounts are hiring.
The two modes answer different questions. An instant alert says "act now". A digest says "here is what moved this week".
You can mix both on one monitor. High importance changes go out instantly, and everything else waits for the digest.
Some teams do not want alerts at night or during a launch week. Instead of muting a monitor and losing changes, move it to a digest for that period. Checks keep running, every version is stored, and the changes arrive together at the time you chose. Nothing is dropped, it simply waits.
After noise filtering, each real change gets a short summary from an AI model and a score of low, medium or high. A wording tweak in a hero line scores low. A removed plan or a new fee scores high. Set a threshold per alert rule.
The scores and summaries are explained on the ai website monitoring page.
Teams that track several rivals often create one channel per competitor, such as a channel for each of the three closest rivals. Each monitor on that rival's pages posts into its channel, so the history of one company reads like a timeline. Product, sales and leadership join only the channels they care about. Slack and Microsoft Teams alerts are included on Growth, Business and Enterprise.
When a change should become work, send it as a webhook. The payload carries the page, the summary, the importance score and links to the text and visual diffs, so your ticketing tool can open a task automatically.
Payload details are on the website change monitoring api page.
Dates, counters, rotating banners, cookie bars and tracking parameters are filtered before any comparison. Ignore rules you set remove the rest. If nothing real remains, no summary is written and nobody is notified. That is why a good setup feels quiet until the day it matters. For the full set of alert options, see website change alert.
Yes. Add several alert rules to one monitor, each with its own channel, mode and importance threshold.
Starter sends email. Growth adds Slack, Microsoft Teams and webhooks. Business adds digests per team, and Enterprise includes all channels.
No. The schedule sets how often a page is checked. A digest only changes when you hear about the results.
The limits count monitored pages, checks and AI summaries per billing period. Deleting a monitor does not give back checks or summaries already used.
Try the demo with any public URL, then create an account and route changes to the people who need them.