Watch a price, a list, a sitemap or a whole page and get an email when it changes.
Content Monitor keeps looking at the pages you list and tells you what changed. ## The four kinds of watch | Kind | What it follows | |---|---| | 🏷 **Value on a page** | One element: a price, a stock status, a phone number, a headline. | | 📋 **List on a page** | A repeating list: products, news items, job ads. You learn what was added and removed. | | 🗺 **XML sitemap** | New and removed addresses in a sitemap — the quickest way to see what a site publishes. | | 📄 **Whole page (AI)** | The whole page, summarised by AI, which also decides whether a change is worth telling you about. | You can have up to 500 watches in one campaign. ## Setting up a watch - **Selector** — which part of the page to read. Use **🖱 Pick** to click the element on a copy of the page instead of writing a selector by hand, and **👁 Try it** to see exactly what is read right now. - **Value type** (for a single value) — Text, or Number/price. With a number you can ask to be told only when it **falls**, only when it **rises**, or only when it moves by **at least X %** (5 % by default). Other changes are still recorded, just not emailed. - **Load with a browser** — for pages that build themselves with JavaScript. It costs more per read; if "Try it" only finds your value with a browser, the box is ticked for you. Changing a watch's address, selector, attribute, value type or browser option **starts that watch over**: the stored value is cleared, because it can no longer be compared with the new one. ## What you get After every check, one email per recipient with everything worth reporting: up to 15 added and removed items per list, or up to 6 AI highlights for a whole-page watch. The owner also gets an in-app notification. The **first check only records the baseline** — changes are reported from the second check onwards. A watch whose element cannot be found is reported only after it has been missing **two checks in a row**, so a momentary hiccup does not wake you up. ## What it costs Charged per **page read**: one unit per page, a browser-loaded page counts double, one sitemap counts as one read however many files it spans. Several watches on the same page share a single read. There is no minimum charge. Whole-page AI watches add the AI cost, charged per 1,000 tokens actually used, and only when the page really changed. ## The campaign page Tiles for Watching / Changes to report / Last 7 days / Not found, and tabs for **Changes**, **All changes** (including the ones that did not deserve an email), **Watches** (the current value of each) and **Checks** (each run with its log and what it cost). A number watch also keeps a value-over-time chart.