Resolving drift events
======================

When you review a drift event you have three choices: save the current page as the new baseline, mark it resolved, or dismiss it. Here is exactly what each one does and when to use it.

Category: Monitoring & Drift | Last updated: 2026-07-07

Open a drift event to see what changed and the recommended action, then decide how to handle it. There are three ways to clear an open event, and they are not interchangeable. Picking the right one keeps your baseline honest so future checks stay meaningful.

YOUR THREE CHOICES

Save baseline (accept the current state): Treat the live page as correct going forward. SuperSchema captures the current page as the new baseline, and all open change alerts for that page are cleared. Use this when the change was intentional and the page is right as it stands.

Mark resolved: Mark the event as handled while keeping your original baseline. Use this after you have fixed the page back to how it should be, so it once again matches the baseline.

Dismiss: Clear the alert without changing anything. It will not appear in your open issues. Use this to acknowledge a minor, expected change you do not need to act on.

Note: Save baseline is a per-page action: it clears every open change alert for that page at once and resets the reference point. Mark resolved and Dismiss are per-event: they clear the single event you are viewing.

WHICH ONE SHOULD I PICK?

You edited the page on purpose and it is correct now | Save baseline
A republish dropped your schema; you re-deployed and verified it | Mark resolved
A price or title changed and you regenerated the schema to match | Mark resolved (or save baseline)
A tiny, expected change you do not care about | Dismiss
You are not sure yet | Leave it open and investigate

FIXING A PAGE THAT LOST ITS SCHEMA

For a "schema missing" event, do not just mark it resolved. The schema is genuinely gone from the live page, and clearing the alert will not put it back. Fix it in the right order so monitoring can confirm the fix is actually live:

1. Re-generate the schema for the page if needed, then re-deploy it (paste it back into the page head, or redeploy through your integration).
2. Verify the deployment so SuperSchema confirms the schema is live on the page again.
3. Mark the event resolved, or run "Check for changes now" so the next check sees a clean page.

Warning: Marking a "schema missing" event resolved without re-deploying just hides the alert. The page stays bare to AI systems until the schema is actually back on it and verified.

WHEN EVENTS CLEAR THEMSELVES

Some events resolve automatically, so you do not always have to act:

- Re-generate schema for a page and its open drift events are auto-resolved, marked "Auto-resolved when schema was re-generated."
- When a scheduled or manual check finds the page back in line with its baseline, any leftover open events for that page are cleared automatically.

Tip: After you handle events, filter your list by status. Events move from open to resolved, dismissed, or auto-resolved, each stamped with when it happened, so you can always see what you did and when.

Note: You can run "Check for changes now" on a single page, or "Check all pages now" across a domain, to re-read the live pages immediately instead of waiting for the next scheduled check. There is a short cooldown between manual checks on the same page.

QUESTIONS THIS ANSWERS

- How do I clear a drift alert?
- What does saving a new baseline do?
- What is the difference between resolve and dismiss?
- How do I fix a page that lost its schema?
- What happens if I dismiss an event?
- How do I confirm a fix actually went live?
- Do drift events ever clear themselves?