Alerts

Alert rules are configured per site and deliver by email, Slack incoming webhook, or an HMAC-signed generic webhook. Deliveries are not metered.

<!-- docs-truth: metric=none; unit=none-deliveries-not-metered; cache-hits=not-applicable; refund=not-applicable; cadence=on-observed-transition; estimates=provider-observation -->

What fires today

New and lost referring-domain alerts fire from two consecutive completed link reviews. The alert carries the frozen before-and-after evidence pair that produced it.

Rank-drop rules fire only after a drop is confirmed: a scheduled rank check finds the drop, and a fresh second check of the same keyword in the same market still shows it. If the keyword recovers, or the second check can't run, the rule stays silent. See Confirmed rank alerts.

One alert per transition

Delivery is exactly-once, keyed to the observed transition rather than to each domain. A review that adds 300 links sends one alert containing a bounded sample of up to 50 domains alongside the honest full count.

A first link review has no baseline to diff against and therefore produces no alert. The delivery log records every attempt as sent, failed, or suppressed.

Channels

Email is available on every paid tier. Slack and the generic webhook are Pro and above. Structural limits allow 2, 10, and 50 alert rules on Starter, Pro, and Agency.

Slack is a user-pasted incoming-webhook URL — there is no RankMeFast Slack app and no bot. Generic webhooks are signed so your receiver can verify the payload came from RankMeFast.

Honest limits

An alert reports an observed change between two stored snapshots. It is not a judgement about link quality and not a prediction of a ranking effect.

If a transport fails, the delivery is recorded as failed rather than retried indefinitely, and the observed transition is never re-sent as a second alert.

For units and plan limits, see Pricing.

Before acting, compare this guide with the stored evidence and status shown in RankMeFast.

Back to the docs index