Every site has a handful of pages that carry it. The pricing page. The product pages that sell. The landing pages your ads point at. The three blog posts that bring in half your search traffic. If one of them quietly changes in the wrong way, you do not find out from a dashboard. You find out from a traffic report, weeks later.
Starting today, VitalSentinel watches those pages for you. Page Monitoring is live on every plan, including Free. You pick the pages, VitalSentinel checks them on a schedule, keeps every version, and tells you what changed, with a before and after.
The Changes Nobody Reviews
Most changes to a page never go through a review. A CMS update ships a new template. A plugin "fixes" canonicals. A developer working on something else touches the head of the page. A tag manager script rewrites the title after load. None of it is malicious, and most of it is harmless.
The few that are not harmless are expensive:
- A noindex lands on a page that earns most of your clicks.
- A canonical starts pointing at a different page, so Google stops ranking the one you wanted.
- Structured data breaks, and the rich results go with it.
- A page starts redirecting somewhere it should not, or returns an error.
- A price or a stock label changes without anyone signing off.
Yesterday I wrote about Sitemap Monitoring, which tells you when URLs come and go from your sitemaps. Page Monitoring is the closer look: what changed on the pages that matter.
Two Versions of Every Page
Each check records the page twice. Once as the HTML your server sent, and once after JavaScript has run in Chrome, at a phone's screen size. That matters more every year. A lot of what decides how a page ranks is now set or changed by scripts after the page loads, and a check that only reads the source would miss it.
From those two versions, VitalSentinel compares 17 kinds of change with the previous check, grouped here:
- Errors and outages, redirects and their targets
- Noindex and robots directives, and whether robots.txt blocks Googlebot
- Canonical, both the tag and the HTTP header
- Title, meta description, H1 and other headings
- Language and hreflang
- Main content and word count
- Structured data types, errors and key properties
- Links and images, including broken images and images without alt text
- Analytics and tag scripts
- Blank pages and rendering problems
- Response headers and speed, from caching and HSTS to time to first byte (TTFB)
- Your own page elements
Images are only status-checked, never downloaded, and no screenshots are taken.
Changes in Plain Words
I did not want another diff tool that leaves you to work out what a red line means. Every change is one sentence: "Now returns 404 (was 200)", "Now set to noindex, so it can drop out of search", "Canonical now points to /new-page", "Now redirects to /new". Text changes show the before and after with the changed words marked, and a value that got worse is tinted so you see it first.
When you want the full picture, any check opens a comparison with four views: Changes, Text, HTML source, and After JavaScript. You can compare any two checks, not just the last two, which is what you want when someone asks "what did this page look like before the redesign?"
Your Own Elements
The fields above cover what search engines care about. But every site has parts only you know matter. On a product page it might be the price, the stock label and the "Add to cart" button. On a SaaS pricing page it might be the plan names and the trial length.
So you can name your own elements with a CSS selector, like .product-price, and test the selector on the live page before you save it. Element changes are listed first, and an alert rule can fire when an element changes, disappears, or contains a given text. Paid plans get up to 10 custom elements per page.
Signal, Not Noise
The hardest part of change monitoring is not finding changes. It is not drowning in them. A few things keep the feed readable:
- Changes that can hurt the page in search or for visitors are flagged Needs attention. You can mark them as seen, snooze them, or mark them as normal for this page or for every page.
- A field that changes on most checks, like a "last updated" timestamp, gets a Changes often chip and is never flagged.
- Minor changes, like a navigation link that rotates or a small speed difference, are recorded but collapsed.
- The same edit on several pages in one day shows as one row: "Title changed on 18 pages".
Did It Cost You Clicks?
A change only matters if it changes something. With Google Search Console connected, each watched page shows its clicks and impressions with every change marked on the chart, and a note when clicks fall after one. Next to it, How Google sees this page shows whether the page is indexed, which canonical Google chose, and when Googlebot last visited.
That is the question I kept asking during audits: not "did the page change?" but "did the change hurt?" Now the answer sits on the same screen.
Site Moves
Migrations are where pages break in bulk. Each watched page can carry a migration check: it should redirect to a new address, redirect to another page of the site, or stay where it is. Upload a CSV with the old and the new URL, and a whole site move is set up at once. If a redirect breaks or points to the wrong place, it shows on the next check.
Getting Pages In
There are four ways to add pages:
- Enter URLs, one per line, with the interval and labels you want.
- Upload a CSV of up to 500 pages.
- Keep my top pages watched, which follows your pages with the most Google clicks and updates the list every week.
- Watch in Page Monitoring, a one-click button in the page tables of RUM, Search Console, Indexing, Server Logs and Site Health.
Page Monitoring only runs on a domain you have verified as yours, through Google Search Console, Cloudflare, a DNS record, or a meta tag or file. VitalSentinel does not fetch a single page before that. The first check runs within about five minutes, and changes show from the second check onward.
Alerts and the Digest
You choose what is worth an interruption. Alert rules cover every kind of change, from "Page stops loading or errors" and "Noindex or robots directive changed" to "Canonical changed", "Structured data changed" and "Page element changed", on all watched pages or only the ones you pick. Alerts arrive in the app and by email. Everything else can wait for the Page and site change digest, daily or weekly.
Plans
Page Monitoring is on every plan. Watched pages are counted for the whole workspace:
- Free: 5 pages, checked every 24 hours
- Starter: 10 pages, checked every 24 hours
- Lite: 100 pages, checked as often as every 4 hours
- Standard: 500 pages, checked as often as every 4 hours
- Advanced: 1,000 pages, checked as often as every 4 hours
Change history is kept 12 months on paid plans and 14 days on Free. The pricing page has the full breakdown.
Where to Start
Verify your domain, then add the five pages you would least like to see break. If Search Console is connected, turn on Keep my top pages watched and let it pick the rest.
The Page Monitoring introduction is the place to read first, followed by Watching pages and Changes. The feature page has the overview.
Then the next time someone asks "did anything change on that page?", you will already know, and you will know what it did to your clicks.
Written by
Martin Stepanek
Enterprise Technical SEO Consultant
15+ years building enterprise websites and designing the infrastructure behind them, and 5+ in technical SEO and web performance. My work is making companies findable – not just on Google, but inside ChatGPT and the other AI engines people now ask first. I write a regular newsletter and blog on technical SEO at TechSEO Vitals, and I built VitalSentinel because the gap between something breaking and someone noticing should be minutes, not days.
