New and lost referring domains
Consecutive completed link reviews are diffed, and the domains that appeared or disappeared become the alert body.
Alerts
Hear about the change, not the dashboard you forgot to open.
Rules per site, delivered to email, a Slack incoming webhook, or your own HMAC-signed endpoint. Each confirmed transition sends once and keeps the evidence pair that triggered it.
Rules, channels, evidence
One alert per change, with the proof attached.
Delivery is keyed to the observed transition, so a retry never turns into a second message.
Three channels
Email on every paid tier; Slack incoming webhooks and HMAC-signed generic webhooks from Pro upward.
Exactly once
Delivery is keyed to the transition it describes, so re-running detection cannot re-send an alert you already received.
A delivery log you can audit
Sent, failed, and suppressed states beside the frozen before-and-after evidence pair that produced the alert.
Product truth
An alert describes a diff between two stored reviews.
This illustrative frame mirrors normalized output. It is not a live monitor.
| Signal | What the product shows | Source |
|---|---|---|
| New referring domains | Present in the latest review, absent from the previous one | Provider observation |
| Lost referring domains | Present in the previous review, absent from the latest | Provider observation |
| Evidence pair | Both review identifiers, frozen at send time | Provider observation |
How it runs
Detection sweeps stored reviews; delivery is unmetered.
Cadence, source, and channel rules stay visible beside every rule.
Swept, not polled per rule
A background sweep reads settled observations and enqueues delivery. Your rules do not each open their own schedule.
Stored reviews only
Detection reads completed link reviews already stored for the site. Enabling alerts triggers no extra vendor request.
Rules are capped, deliveries are not
Your plan caps how many rules a site may hold. The alerts those rules send are never metered or charged per message.
What we don't doHonest limit Honest limit Honest limit
Three things this feature will never claim.
Every limit below is enforced in the product, not written on a disclaimer page.
Rank-drop rules do not fire yet
Rank-drop rules can be created, stored, and delivered from a confirmed rank-drop observation — but the shipped rank pipeline does not yet produce a confirmed row. Backlink change alerts are the channel that fires today, and we would rather say so than let you rely on a silent rule.
One alert per transition, not per domain
A review that adds hundreds of links sends one alert carrying a bounded sample of up to 50 domains plus the honest full count. A first link review has no baseline and produces no alert at all.
No Slack app, no OAuth
Slack delivery is a webhook URL you paste yourself. There is no RankMeFast Slack app, no bot user, and no workspace permission to grant or revoke.
Every limit below is enforced by the product, not a disclaimer.
Delivered, not dashboarded
Let the change come to you.
Create an account to set up your first rule, or begin with a free site audit.