SEO Alerts in Slack for Your Agency

Getting SEO alerts in Slack comes down to connecting a monitoring tool to a Slack channel through an incoming webhook, so that a message posts when something changes on a site. The harder part for an agency is choosing which events get a message and which channel they land in, because a channel full of low-value notifications gets muted within a week.

Email still has its place for digests. The trouble is that an alert in one person's inbox is not visible to the rest of the team, and a noindex on a client's category page should not wait until that person is back from holiday. In a shared Slack channel, whoever is around can pick it up.

Creating the webhook

Slack incoming webhooks belong to a Slack app, even a very simple one you create for this purpose.

1. Create a channel for the alerts, for example #seo-alerts or one channel per client such as #client-acme-alerts.
2. Go to api.slack.com/apps, choose Create New App, then From scratch, and pick your workspace.
3. Under Features, open Incoming Webhooks and switch Activate Incoming Webhooks on.
4. Click Add New Webhook to Workspace and choose the channel.
5. Copy the URL. It looks like https://hooks.slack.com/services/T…/B…/…, and anyone who has it can post to that channel, so store it like a password.
6. Paste it into your monitoring tool's Slack settings and send a test.

Each webhook is tied to one channel. If you want urgent and informational alerts in different places, create one webhook per channel. Workspace admins sometimes restrict app installation, in which case step 4 becomes a request that someone has to approve.

Which changes deserve a message

Keep Slack for the events that cost traffic or data if they sit for a day. A noindex appearing on a page that was indexed is the most urgent; our guide on catching a noindex in production explains why. Close behind are robots.txt edits that add Disallow rules, canonicals that change or point somewhere unexpected, and URLs dropping out of the sitemap. The site going down belongs here too, as do an SSL certificate or domain nearing expiry and a GA4 or GTM tag disappearing.

Title and meta description edits are a judgment call. Clients change them legitimately, so on sites with active content teams they are better suited to a daily email.

Designing the channels

For a handful of clients, one shared channel works. Past ten or so, most agencies find one channel per client easier, because account managers can join only the channels they own and the client name is obvious from the channel rather than the message.

Another common split is by severity: an urgent channel with notifications turned on for the team, and a quieter one for informational changes that gets reviewed once a day. Whatever you choose, the test is simple. If people have muted the channel, it is producing too many messages, and a muted channel is worse than none because it looks like coverage.

A useful alert message is readable without clicking anything. Something like "example.com: 3 URLs now return noindex, detected today" tells the reader what to do. A block of raw HTML does not.

Slack alerts from Deltio

Deltio posts to Slack through an incoming webhook and sends the same alerts by email, configured per site, so you can point each client at its own channel. The alerts cover the events above: noindex, robots.txt and canonical changes, title, meta description and H1 changes, sitemap URLs added or removed, uptime, SSL and domain expiry, and GA4, GTM and Meta Pixel tags going missing. Each message names the site and the affected URLs and links to the detail in the dashboard.

One limit to keep in mind: Deltio checks sitemaps and pages on a daily cycle, so a Slack message tells you about a change the day it is detected, not seconds after a deploy. For turning the same events into a monthly deliverable, see website monitoring in client reports, and for choosing the events themselves, SEO change alerts.