Get Notified When Website Changes by Email, Slack, Teams or Webhook

Before choosing channels, it helps to agree on what an alert should say. An alert that only reads "page changed" forces someone to open the page, compare it in their head and guess what moved. Most people will not do that more than a few times.

A useful alert answers four questions in a few lines:

• Which page changed, with a name your team recognizes, such as "Competitor A, pricing".
• What changed, in one sentence a manager can act on.
• How important it is, so the reader knows whether to stop what they are doing.
• Where to check, with a link to the full version history.

In WebsiteChange, the second and third answers come from the summary layer. When a real change remains after noise filtering, an AI model writes a short summary, for example "Pro plan price raised from 79 to 99 USD per month; annual discount removed", and scores it as low, medium or high importance. The link opens the version with its screenshot, text diff and visual diff highlighting.

Email is the channel everyone already has, and it is included on every plan. It works best in three situations.

First, for one person who owns a small watchlist, such as a consultant watching a dozen client and competitor pages. Second, for changes that need a paper trail, since an email sits in an archive with a date and can be forwarded to counsel or attached to a ticket. Third, for digests, because a single daily or weekly email that lists every change is easier to read than a stream of messages.

A few tips for email alerts:

• Create a mail filter or label for alerts so they never mix with customer mail.
• Send high importance changes to a person, not to a shared alias nobody owns.
• Use the weekly digest for low importance pages, so your inbox gets one message instead of many.

Chat channels shine when a change concerns a team rather than one person. A competitor price change matters to product marketing, sales leadership and finance at once. Posting it into a shared channel means the discussion happens in one thread, next to the alert, and nobody has to forward anything.

Slack and Microsoft Teams alerts are available on Growth and higher plans. A setup that works for many teams:

• One channel per topic rather than one per page, for example a competitor pricing channel, a vendor terms channel and a regulator updates channel.
• Only medium and high importance changes posted instantly to the channel.
• Low importance changes summarized in a weekly digest message to the same channel.
• A named owner for each channel who checks the thread and decides on follow up.

Chat is a poor archive. Messages scroll away and search is limited, so keep the version history as the record of what a page said and use chat for the conversation about it.

A webhook sends each change as structured data to an address you control. That lets your own tools react without anyone reading a message. Webhooks are available on Growth and higher plans.

Typical uses:

• Create a ticket in your issue tracker when a vendor's terms change at high importance.
• Write competitor price changes into a spreadsheet or data warehouse for weekly reporting.
• Update a pricing dashboard when a product goes out of stock on a competitor's site.
• Trigger an internal review workflow when a regulator page adds a new publication.

On Growth and higher plans, price and stock extraction adds the detected price and stock status as fields, which makes webhook data easier to use in reports. Growth includes a read API, and Business and Enterprise include the full API, so your systems can also pull versions on their own schedule. The website change alert page describes each alert channel in more detail.

Every alert route in WebsiteChange can be instant or batched into a daily or weekly digest. The choice depends on how fast someone needs to act, not on how important the page is in general.

A good rule: if nobody would act on the alert within a day, it belongs in a digest. Instant alerts should be rare enough that people still open each one.

The importance score is the main control for volume. Each change gets a low, medium or high score from the summary, and each alert route has a threshold. A route set to high sends only high importance changes, a route set to medium sends medium and high, and so on.

This lets you watch a page closely without being interrupted by small edits. For example, you can watch a competitor's entire pricing page, send high importance changes to Slack immediately, and let everything else collect in the weekly digest. Price changes, removed plans and new limits score high. A rephrased tagline or a new testimonial block usually scores low.

Thresholds work together with the other noise controls:

• Element watching narrows the monitor to the block that matters, such as the price table.
• Ignore rules remove parts that change on every visit, such as a live counter.
• Sensitivity sets how much content must change before a change counts at all.
• The website change detection engine already filters dates, counters, rotating banners, cookie bars and tracking parameters.

Summaries run only when a real filtered change remains, never on every check, so a quiet page uses checks but no summaries from your monthly allowance.

Here is how three different teams might combine channels, digests and thresholds.

• A product marketing team at a software company watches 40 competitor pages. Pricing pages send high importance changes to a Slack channel instantly. Feature and changelog pages go into a daily digest for the same channel. Careers pages of competitors go into a weekly email digest for the head of marketing.
• An ecommerce pricing manager watches competitor product pages for price and stock. Element monitors on the price block send every change by webhook into a spreadsheet, and a daily email digest summarizes the day's movements for the manager.
• A legal team watches terms of service and privacy policies for its vendors. High importance changes go by email to the privacy lead instantly. Medium changes go to a Microsoft Teams channel as a daily digest. Everything stays in the version history for audits.

For more scenarios, the guide on how to notify when website changes walks through setups for single pages, and the page on monitor terms of service changes covers legal routing in depth.

Alert routing is not a one time setup. Teams change, channels get archived, and the pages that mattered in spring may not matter in autumn. A short monthly review keeps the system honest.

• Look at which monitors produced alerts nobody opened, and move them to a digest or narrow them to an element.
• Check that every channel still has an owner, especially after someone changes roles or leaves.
• Remove monitors for competitors or vendors you no longer track, so your page and check allowance goes to pages that matter.
• Read through the last month of high importance changes and ask whether each one deserved an interruption.

Remember that limits are counted as usage per billing period. Deleting a monitor frees a page slot for a new one, but checks and summaries already used in the period stay counted.

Most alert problems come from the same few habits.

• Everything goes to one inbox. Split by topic and route each topic to the people who own it.
• Every change is instant. Move anything that is not acted on within a day into a digest.
• Full page monitors on busy pages. Narrow the monitor to an element or add ignore rules, and look at the screenshot in the page change monitor view to see what keeps moving.
• Nobody owns the channel. Name one person per channel who reads the thread and decides on follow up.
• Alerts without context. Name each monitor after the company and the page type so the alert is clear at a glance.

If a monitor gets muted in its first week, treat that as a setup problem, not a reason to stop watching the page.