Notifications and Webhooks

Choose what you hear about in the dashboard and by email, set your digest, and send events to your own systems.

RankDebug tells you about things in three ways: notifications in the dashboard, emails, and webhooks to your own endpoints. The first two are personal settings; webhooks belong to the workspace.

Notifications and email

Settings → Notifications lists each kind of event with a switch for the dashboard and, where it applies, for email:

  • Agent: the agent finished something you asked for.
  • Support: a reply or status change on one of your tickets.
  • Site Health: a site check or crawl found something that got worse.
  • Reports: a report was shared with your workspace, or someone replied to your comment.
  • Connections: an SEO tool export you uploaded is out of date.
  • Site Digest: your scheduled digest.

There is also a switch to mute dashboard notifications altogether. Security, billing and account email always arrives, whatever you choose.

Email digests

The digest is a short email per workspace with search clicks and impressions against the period before and the pages and queries that moved most, the open findings from the latest site check and which of them are new, the deploys in the period, and any connection that stopped syncing.

It goes out around 8 in the morning in the workspace's timezone, weekly on Monday by default or daily if you choose. Set the frequency under Email Digests in Settings → Notifications. Each person picks their own, per workspace.

Webhooks

A webhook sends an event to an HTTPS endpoint of yours when something happens in the workspace, signed so you can verify it came from RankDebug. Two events exist today, site_check.regression and site_crawl.regression, both sent when a high-severity problem appears that was not there before.

Manage webhooks on the Webhooks page or through the API. The webhooks section covers the events, the payload, signature verification and retries.

Related documentation
  • Guide

    How the parts of RankDebug fit together, and where to find each one in the dashboard.

  • Connections

    How data sources connect to a workspace, how often they sync, and what happens when you disconnect one.

  • Search Console

    Connect Google Search Console with read-only access. What RankDebug pulls and what it is used for.

  • Google Analytics

    Connect Google Analytics with read-only access to see what search visitors did after they landed.

  • Cloudflare

    Connect Cloudflare with a read-only API token to see which crawlers reach your site and what the edge did to them.

  • Bing Webmaster Tools

    Connect Bing Webmaster Tools with an API key to add Bing search data and crawl statistics.

  • GitHub

    Connect a GitHub repository so production deploys are recorded on their own, with the SEO-relevant files each one changed.

  • GitLab

    Connect a GitLab project with a read-only token so production deploys are recorded on their own.

Was this helpful?

On this page