Websites change constantly. Someone edits a page, a template gets updated, a republish silently drops your schema, a price moves, a page starts returning a 404. Monitoring watches your verified pages on a regular schedule so you find out when something changes, instead of discovering months later that your schema disappeared or no longer matches the page. It reads your public pages only. It never logs in and never changes your live site.
How monitoring works #
- A page is verified. Once SuperSchema confirms your schema and AI-readable files are live on the page, that page becomes eligible for monitoring.
- A baseline is captured. SuperSchema saves a snapshot of the page as it is right now: its structured data, its content fingerprint, and its AI readability signals.
- The page is re-checked on a schedule. SuperSchema re-reads the page and compares it against the baseline.
- Drift events are raised. If something meaningful changed, SuperSchema records a drift event with a before and after view so you can see exactly what moved.
- You review and clear events. You decide whether each change was intentional, needs a fix, or can be ignored.
What a baseline captures #
The baseline is the reference point every future check compares against. It is a fingerprint of the page at the moment it was verified, not a full copy of your content. It records:
- Structured data: the JSON-LD on the page, the schema types present, and a hash of the whole block so changes are easy to detect.
- Content fingerprint: the page title, meta description, the H1 heading, a hash of the body text, the author, and the published and modified dates.
- AI readability signals: an AI readability score plus whether the page has a definition-first structure, self-contained sections, and clear entity references.
- Access signals: the HTTP status, the canonical URL, and robots directives.
What monitoring checks for #
Each check runs several detectors against the page. Together they cover the changes most likely to hurt how AI systems read and cite you:
- Schema changes
- Structured data removed entirely, a schema type dropped, or individual properties added, removed, or changed since the baseline.
- Content changes
- A new page title, an edited meta description, a changed H1, a rewritten body, a different author, or important page entities disappearing.
- Freshness changes
- Published or modified dates going stale, or a title that references a year now more than a year in the past.
- Commercial changes
- For Product, Service, and similar types: pricing or offers removed, a price change, an availability shift, a service area removed, or ratings dropped.
- Access changes
- The page returning an HTTP error, redirecting, being set to noindex or nofollow, or its canonical URL changing.
How often pages are checked #
Check frequency depends on your plan. Essential and Growth re-check monitored pages weekly. Portfolio and Enterprise re-check daily. You can also run a check yourself at any time with "Check for changes now" on a page, which re-reads the live page immediately and compares it against the baseline.
| Plan | Check frequency | Drift history kept |
|---|---|---|
| Essential | Weekly | 30 days |
| Growth | Weekly | 90 days |
| Portfolio | Daily | 1 year |
| Enterprise | Daily | Unlimited |
What monitoring does not do #
- It does not edit or fix your site. When a page changes, monitoring tells you and recommends an action, but you decide what to do.
- It does not log in. It reads your public pages the same way a search or AI crawler would.
- It does not monitor pages that are not verified. Verify a page first, then it can be added to your monitoring roster.