Notifications

A digest in the channel, not another dashboard.

Most of Murkuz is something you ask. This is the one part that speaks first. Point a site at a Slack incoming webhook and Murkuz posts a scheduled summary of how search traffic moved and which pages are sliding, so nobody has to remember to go and look.

What You Get

The movement, on a schedule

Clicks and impressions for the period, with how each one changed against the period before. Read from your own Search Console property, so it is the same number your agent would quote.

Pages losing ground

The pages that dropped since the last digest, listed with the size of the drop. It is a nudge to go and ask a proper question, not a verdict on your site.

Findings Murkuz has stored

Any findings held for the site are summarised in the same message, with the type of each one. The detail stays where you can interrogate it, in the chat.

One channel per site

Each site carries its own webhook, so a portfolio can send each property to the channel that owns it. Name each connection so you can tell them apart later.

How It Works

1

Create an incoming webhook

In Slack, create an incoming webhook for the channel that should receive the digest. Murkuz does not install a bot and never reads your messages.

2

Paste it into the site

Open the site in Murkuz, add the webhook under integrations, and give the connection a name. The URL is stored encrypted.

3

Pick a cadence

Daily, weekly or monthly, at an hour you choose. There is a test message so you can see exactly what lands before you leave it running.

4

Ask the follow-up in the chat

The digest is deliberately thin. When something in it matters, the whole tool surface is one question away in Claude or ChatGPT.

Full Capabilities

Clicks and impressions for the period, with the change on the period before
Pages that lost position since the last digest, with the size of the drop
A summary of the findings Murkuz has stored for that site
Daily, weekly or monthly cadence, at an hour you choose
One webhook per site, so each property can post to its own channel
Several named connections per site, if more than one channel needs it
A test message on demand, so you see the format before you commit
The webhook URL is stored encrypted and is never shown back to you
Outbound only: Murkuz posts to the channel and reads nothing from Slack
Google Search ConsoleAll IntegrationsThe Full Tool ListSee Pricing

Connect the sources once. Ask from then on.

Murkuz reads Google Search Console, Google Analytics 4 and Bing Webmaster Tools through the official APIs and hands the rows to Claude or ChatGPT. Read-only, with your own permissions, revocable from your own account at any time.

Every paid plan connects all three sources. Free connects Search Console alone.