Skip to content

DOCUMENTATION · 7 min

Alerts: Slack, Teams and webhooks

The workspace can send alerts and scheduled reports to Slack, Microsoft Teams and signed webhooks. This page lists the alert types, how a channel chooses what to receive, how to set up each destination and how to verify a webhook signature.

✓ Checked in the workspace code · 7 October 2026

Where alerts can go

The workspace can push alerts and scheduled reports out of the app, so you do not have to open it to learn that something changed. Three destinations are supported: Slack, Microsoft Teams and outbound webhooks for Zapier, Make, n8n or your own service. The page is in the account menu as “Slack, Teams & Webhooks”.

What can trigger an alert

Alert typeFires when
Broken or restored Google connectionthe Google sign-in stops or resumes working
Core Web Vitals regression or recoverypage experience metrics worsen or recover
Google algorithm updatea Google ranking update starts
Indexing warningsan indexing problem is detected
Traffic anomalies and sustained traffic shiftsa day is unusual, or the level moves for good (advanced analysis)
Content decaypages keep losing clicks
Experiment readoutsa page-group experiment has a result (experiments)
URL Inspection quota, IndexNow failuresthe daily inspection allowance is reached, or an IndexNow submission fails (IndexNow)
Bing crawl issuesBing reports a crawl problem

Each alert has a severity: critical, high, medium, low or info.

Choosing what a channel receives

  • Alert types: tick only the types the channel should get.
  • Minimum severity: a channel receives alerts at or above its minimum; the default is medium. Use critical or high for a channel that wakes people up.
  • Test: send a sample alert to check that the destination works.

Microsoft Teams

  1. In the Teams channel open the ··· menu and choose Workflows.
  2. Choose “Post to a channel when a webhook request is received”, select the team and channel and create it.
  3. Copy the generated URL and paste it into a new Teams channel in the workspace. Legacy Incoming Webhook URLs also work.

Teams receives a formatted card with the alert title, message, type and severity, with no Zapier or Power Automate flow of your own.

Slack

Use “Add to Slack” to connect a workspace. Then create Slack subscriptions: scheduled reports and alert routing to chosen channels. Slack reports use Search Console data, which usually lags by about three days, so a daily report covers the latest complete day.

Outbound webhooks and signatures

A webhook sends each event as JSON by POST. Every request carries two headers so your service can check that it came from SEOKit:

  • X-SEOKit-Timestamp: the time of sending, in seconds.
  • X-SEOKit-Signature: sha256= followed by the HMAC-SHA256 of the timestamp, a dot and the raw request body, using the webhook’s secret.

The secret is shown once, when you create the webhook; save it then. Verify the signature on your side and reject old timestamps to resist replays. The body has an id, the alert type, severity, time, the source “SEOKit” and the event data. Your endpoint should answer within 12 seconds.

Destination rules

  • The URL must use https on the standard port, without a username or password.
  • Addresses that are local or private, such as localhost or .local names, are refused, and so are hosts that resolve to non-public addresses.
  • The URL and the secret are stored encrypted.
  • Every delivery is logged with its status and HTTP code, so you can see failures.

If something looks wrong

MessageCause and fix
https_url_requireduse an https URL without credentials
https_port_requireduse the standard port 443
private_addressthe host is local or private; use a public endpoint
host_not_foundthe name does not resolve; check the URL
Deliveries failyour endpoint did not answer within 12 seconds or returned an error; check the delivery log
No alerts arrivethe minimum severity is higher than the alerts being sent, or the type is not selected

Alerts, answered

Can I see the webhook secret again?

No. It is shown once; create a new webhook if you lose it.

Why did I not get an alert?

Check the selected types and the minimum severity of the channel.

Do I need Zapier for Teams?

No. A Teams workflow URL is enough.

Continue

Next, see annotations and the MCP server.

SEOKIT · GROQ

SEOKit assistant

0 / 1000