SEO alerts · supplied snapshot evidence

Evaluate alert rules before you automate them

Import two audit, backlink, page-change, ranking, analytics, sitemap, or AI visibility snapshots. OpenWebmaster checks added, removed, changed, status-change, and numeric movement rules locally before any email, webhook, or schedule exists.

SNAPSHOT ROWS5,000 EACHRULES20DELIVERYEXPORT ONLY
SNAPSHOT IMPORTS

Load the earlier and later evidence files

Use CSV/TSV, JSON arrays, OpenWebmaster opportunity plans, action ledgers, page-change rows, backlink observations, or plain lists. Keys are matched by source, metric, and item.

BASELINEEarlier snapshot
CURRENTLater snapshot

Files stay in this browser. Blank rows are ignored, duplicates are reported, and unsupported JSON is surfaced as an import note.

RULE SETTINGS

Customize local alert logic

Rules are saved in this browser.

Ready for two real evidence snapshots.

No example alert, notification, rank movement, backlink, crawler visit, or traffic change appears before you provide data.

Alert workflow

Decide what deserves notification before adding automation

Use stable keys

Keep source, metric, and item keys consistent across snapshots so added, removed, and changed rows describe comparable evidence.

Separate event from cause

An alert event says a supplied row changed. It does not explain the reason or prove a search, traffic, or business outcome.

Export the contract

Use the JSON export as a future automation contract when durable accounts, schedules, recipients, and provider credentials are available.