Website change monitoring

Know when your site changes without anyone telling you.

A deploy strips a canonical. A plugin rewrites a title. Someone edits the headline on your busiest page and tells no one. Page Pulse compares each tracked page to its last crawl, so you hear about it before your traffic does.

  • Titles, meta, canonicals, headings, copy and links compared on every crawl
  • Email or Slack alerts, filtered by page and change type
  • Old and new values side by side, scored 0 to 100
Free for 50 pagesNo card needed
app.pagepulse.dev/changes
Site watchToday
Canonical changed on /pricing
Meta · no ticket filed
Critical
H1 removed on /enterprise
Headings · changed overnight
High
Title edited on /blog
Meta · Oct 12
Low
The problem

Your site changes without you. The damage shows up weeks later.

Deploys, CMS edits and marketing tests all touch live pages. By the time a ranking slips, the change behind it is buried.

Catch the changes that cost traffic

A dropped canonical, a removed H1, a rewritten title. Each change is scored 0 to 100, so the likely problems rise above the noise.

Every edit, logged automatically

Copy, headings, links, title tags, meta descriptions, canonicals and Open Graph tags on every tracked page, compared on every crawl.

The right person hears about it

Scope alerts by tag or page and send them to email or a Slack channel. Webhooks push them anywhere else.

Why it matters

When a page slips, the first question is "what changed?"

Page Pulse already has the answer, dated and scored. Here's a real one from our own site: in August 2026 our canonical tags still pointed at http. When we fixed them, the timeline logged each page, old and new.

Daily

crawls on paid plans, every 3 days on free

0 to 100

impact score on every change

Forever

change history kept, on every plan

When a page slips, the first question is "what changed?"
DetectedPageCanonical beforeCanonical after
Aug 1, 2026 /help/project-dashboard-explained/ http://pagepulse.dev/help/project-dashboard-explained/ https://pagepulse.dev/help/project-dashboard-explained/
Aug 5, 2026 /workflows/traffic-drop-cause/ http://pagepulse.dev/workflows/traffic-drop-cause/ https://pagepulse.dev/workflows/traffic-drop-cause/

See if the fix worked, too

Connect Search Console and GA4 and Page Pulse measures the page before and after a change, so you can tell whether the traffic came back.

See the Impact Model Score
How it works

Protect your key pages in an afternoon.

1

Add the pages you can't afford to break

Your money pages, your templates and anything a deploy touches. The first crawl sets the baseline.

2

Decide what deserves an alert

Alert on content, headings, links or meta, and on new, edited or removed items. Send it right away or roll it into a digest.

3

Hear about it after the next crawl

You get the old and new values, scored by impact, by email or Slack.

FAQ

Questions, answered

Uptime tells you the page is up. Page Pulse tells you the page changed (the headline, the canonical, the body copy) and, with Google connected, what that did to your traffic.
Yes, as long as they change the page. Page Pulse compares what each crawl finds, so it doesn't matter whether the edit came from a deploy, the CMS or a plugin.
Four kinds of change: content, headings, links and meta, which covers title tags, meta descriptions, canonicals and Open Graph tags. You can narrow it to new, edited or removed items, and to specific pages or tags.
Not as tracked changes. Page Pulse doesn't log robots directives, redirects, HTTP status codes, schema or image alt text. Over MCP you can ask it to check a tracked page's live robots directives and status at any time.
Yes, with Google connected. Page Pulse compares the page's performance before and after a meaningful change against its expected baseline.

Nothing should change on your site without you knowing.

Add your most important pages and get an alert the next time one changes.

Free for 50 pages · No card needed