Documentation

Change monitors

Watch a page or a region of it and get told when the content or appearance changes.

A change monitor answers "did this change?" Use it for pricing pages, terms and policies, a competitor's homepage, a product listing, or any region that shouldn't drift without you knowing.

How it works

  1. The first run captures a baseline — a screenshot and the page text.
  2. Every later run captures again and compares against the baseline, both as text and pixel by pixel.
  3. If the difference is significant, the run is marked change detected, you're alerted, and the new capture becomes the baseline for the next comparison.

Because the first run only establishes the baseline, a brand-new change monitor never reports a change on run one. Run it a second time to see a comparison.

Full page or a region

  • Full page captures everything. Simple, but on busy pages rotating ads, "latest news" panels, and timestamps can trigger changes you don't care about.
  • Selected region captures only the part you pick. Click Pick visually, then click the element on the preview. This is the right choice for most pages: it ignores everything outside the region.

When you pick a region, Simrix saves both a CSS selector and the element's position. If the selector stops matching later (the site changed its markup), the monitor falls back to the saved position so it keeps working.

Sensitivity presets

  • Fast — text comparison only. Quickest and cheapest; misses purely visual changes such as swapped images.
  • Balanced — text and visual comparison. The default, and right for most pages.
  • Focused — high-sensitivity visual comparison. Catches subtle changes, but is more likely to flag dynamic content as changed.

What the run shows

A change run includes the before and after screenshots, a visual diff highlighting what moved, the words added and removed, and an AI-written summary of what the change means — for example "Price changed from $49 to $79." Changes are also classified by significance (minor to critical) and category (content update, price change, and so on).

You can annotate a change from the run detail page — for instance "expected, we updated pricing" — so the history stays meaningful.

Avoiding false positives

  • Prefer Selected region over Full page, and pick a region that excludes ads, feeds, and clocks.
  • Simrix hides common ad containers and dismisses cookie banners before capturing, but not every site uses standard markup. If a full-page monitor keeps flagging changes, switch it to a region.
  • If the region includes something that legitimately changes often, move the region or use Fast (text only) so images don't count.

Frequency

Same options as workflow monitors, and the same run-allowance arithmetic. Most change monitors don't need to run faster than hourly; a policy page can happily run daily. See Billing and plans.