use case · monitoring

Website change monitoring for whole sites, not single pages

Track every page in a section — a regulator’s guidance library, a competitor’s changelog — and get a clear summary of what changed. Cookie banners, timestamps and rotating widgets never raise an alert.

No card. 1,000 credits to start. Blocked pages, 404s and unchanged pages are never charged.

508,290
gov.uk URLs mapped from 29 sitemap files in a single discovery run.
01the problem

Why most page monitors let you down

They watch one URL at a time. They alert on every banner. They miss JavaScript content. And they cannot tell a page that was deleted from a page that simply failed to load.

02what is different

Whole sites, and only the changes that matter

  • Whole-site coverage: monitor a section like /guidance/* through its sitemap. New pages appear as added the day they are published.
  • Noise filtered first: consent banners, rotating widgets and “last updated” stamps are removed before anything is compared.
  • Changes you can act on: the exact paragraphs that moved, plus field-level changes to titles, dates, canonicals and prices.
  • Removals you can trust: a run that reached under 90% of the site holds its removals back and says why, so an interrupted crawl never reads as a mass deletion.
  • Alerts where your team works: Slack, Discord, Teams, Google Chat, email digests or signed webhooks, with an optional model-written summary focused on what you care about.
03who watches what

Who uses it

  • Compliance and legal: regulator guidance, consultations and policy pages.
  • Public affairs and journalism: government pages that change — or disappear.
  • Product and competitive intelligence: pricing, feature and changelog pages.
  • Partnerships and procurement: supplier terms and tender portals.
questions

Frequently asked questions

How do I track changes on a website?

Create a project with the site’s URL and the sections you care about, choose a schedule — hourly, daily or weekly — and connect Slack, email or a webhook. The first run sets the baseline; every run after it reports what changed.

How often can MeshArc check for changes?

As often as hourly. For prices that move every few minutes, a live feed is a better fit than a crawler.

Does it detect changes on JavaScript-heavy pages?

Yes. Pages are rendered in a real browser when they need one, and compared like any other page.

Stop checking. Start knowing.

One project covers a whole section, and says nothing on the days nothing moved.