Start with a decision, then choose the signal.
Write down what would make you act: a price below your budget, a new job in a particular team, or a revised paragraph in a supplier’s terms. “Tell me when anything changes” is sometimes useful, but it also includes changes you may not care about.
Check whether the publisher already offers an email subscription or feed. That may be enough for new announcements. Manual checking can work for a one-off decision. A page monitor becomes useful when you need repeated checks of a known URL or a particular part of it.
| Your question | A useful starting point |
|---|---|
| Did this wording change? | Text monitoring of the relevant page section. |
| Is the price now below my budget? | A selected price with a numeric threshold. |
| Can I buy it now? | Availability based on the site’s visible stock wording. |
| Was a new job or article added? | New-item monitoring of a listing, or a feed/source watch. |
| Does the page look different? | Cloud visual monitoring of a consistent region. |
| Was this document revised? | PDF text monitoring of the direct public document URL. |
These are different questions, even when the source is the same. The feature overview helps you choose a capture type; the rule reference explains the controls.
Build a monitor around one useful selection.
Open the page or paste its URL.
Start in Add monitor, or use the Chrome extension to select an element on the page. Choose the workspace whose members should be able to review the captures.
Choose where the check runs.
Try Cloud HTML for content already delivered in the HTML. Use Cloud Browser when JavaScript is needed. Choose Local in the extension when the check should use your Chrome profile; Chrome must stay running on an awake computer.
Select the content and rule.
Choose a page section rather than navigation, advertising and every footer link. For a price, select the current amount and verify its currency and decimal format. For stock, check the actual wording instead of assuming a button means availability.
Inspect the actual preview.
A Cloud capture can differ from the page in your browser. A Local test opens a fresh inactive tab. Check that the selected value is present and belongs to the correct product, account and variant before saving.
Save a baseline and choose delivery.
The first confirmed capture is the starting point, not a change alert. Select an allowed interval, then configure email or other available notification destinations on the monitor’s details page.
Try a change with a predictable outcome.
A desk lamp crosses your budget
What this meansA Price rule set to falls below USD 75 matches this transition. A move from $89 to $79 would not cross that threshold.
Download the monitoring example kit. It includes a before and after product page, two PDF versions, sitemap samples and instructions. To test an actual saved monitor, publish the before product file at a public HTTPS URL you control, select #price and save the baseline. Replace that file with the after version at the same URL, then wait for the next successful check.
The files are static. Opening two different sample URLs does not make a saved monitor detect a transition. If you do not have somewhere to publish them, use the PageFluxer demo to explore the workflow, then start with a real page you already follow.
Set a schedule you can use, not just the fastest one.
A monthly policy review and a short-lived product restock have different timing needs. Shorter intervals can reduce the gap between a change and its next capture, but they consume more checks and cannot guarantee every intermediate state is seen.
Estimate the workload before adding many pages: ten pages checked hourly would require about 7,200 scheduled attempts over a 30-day month. That is a planning example, not a guarantee of completed checks. Compare the relevant HTML, Cloud Browser or Local allowances on the pricing page.
Local timing also depends on an awake computer, Chrome, connectivity and browser scheduling. Cloud checks have their own capacity limits, website failures and retry behavior. Review check health alongside the change history.
Reduce noisy alerts without hiding the useful change.
Start by narrowing the selection. A product price usually needs less context than a whole product page; a policy clause may need its heading and nearby definitions. Avoid clocks, rotating recommendations and unrelated announcements when they are not part of your question.
Use a specific rule when the decision is specific. A threshold is more useful than every numeric movement if you only want to buy below a budget. For visual checks, keep the viewport and region consistent and review the available noise controls. Optional AI tools have their own supported capture types, consent and allowances.