What Search Console data is sent to Microsoft Teams?

Only what the card shows: the property, the metric and dates behind the alert, the numbers such as actual against expected, and a link back to the report. Anyone who can read that Teams channel can read those numbers, so pick the channel deliberately. Nothing is read back out of Teams: GSC Wizard holds a webhook URL and no permission on your tenant.

Can different properties go to different Teams channels?

Yes. Add one Teams channel per destination in GSC Wizard, each with its own webhook URL, its own alert types and its own minimum severity. A channel for critical incidents and a channel for weekly content decay is a common split.

Search Console SEO alerts, in Microsoft Teams

Q: How do Google Search Console alerts get into Microsoft Teams?

Through a channel webhook URL that Teams gives you. In Teams, open the channel, choose Workflows from its menu, and create one from the template "Post to a channel when a webhook request is received". Paste the URL it hands you into GSC Wizard under Account, then Slack, Teams and Webhooks. When a detector fires, GSC Wizard posts an Adaptive Card to that URL and Teams renders it in the channel.

Your Google Search Console data lands in the Teams channel your team already watches. GSC Wizard raises an alert when something changes state and posts it as a native card, so nobody has to remember to open a dashboard.

Set up Teams alerts How to set it up

No Teams app to install and no admin approval. Included in every paid plan and in the free trial.

SEO › Alerts

Posted within minutes of detection

GSC Wizard WORKFLOW 09:12

Traffic anomaly: Clicks

example.com

Clicks were below their expected range on Thursday 27 August.

Actual

412

Expected

980

Change

-58%

Compared to the same weekday baseline. Search Console data lags around 3 days, so this is the latest complete day.

Open anomaly detection

An alert as it arrives in Microsoft Teams. Cards are colour-coded by severity and link straight to the report they came from.

Nothing in between

A Teams channel, a URL, and that is the integration

Most tools reach Microsoft Teams through Zapier, Power Automate expressions, or a raw JSON dump in the channel. GSC Wizard speaks the card format Teams renders natively.

No app, no admin ticket

There is nothing to add to your Microsoft 365 tenant and nothing for IT to approve. Anyone who can create a workflow on a channel can turn this on, and deleting that workflow turns it off.

Cards, not JSON

Each alert arrives as an Adaptive Card: a headline coloured by severity, the property and the numbers behind it, and a button opening the exact report, already filtered to that property.

Within minutes, not daily

Detection is separate from delivery. A detector writes one event and the delivery job ticks every ten minutes, so a broken connection or an indexing warning reaches the channel while it still matters.

Want scheduled daily, weekly or monthly Search Console reports posted to a channel as well? That is what the Slack app does today. Teams channels receive the alerts.

Alert types

What can raise a card in your channel

Enable the ones you want per channel, with a minimum severity. Recoveries are their own cards, so a resolved problem closes its own loop.

Google connection broken

A Search Console token stopped refreshing, so ingest and monitoring would otherwise fail quietly. A recovery card follows when the account is reconnected.

Indexing warnings

Tracked URLs that went deindexed, stopped being crawled, errored, came back, or whose checks were paused.

Core Web Vitals regressions

A weekly CrUX scan that reports the metric, the form factor and the move between buckets, with a recovery card when it comes back.

Traffic anomalies

A day that falls outside its own day-of-week baseline. Set the sensitivity, the metrics, and whether spikes count as news.

Sustained traffic shifts

Change points: a level shift that held, not a single bad day. When the date overlaps a known Google update, the card says so.

Algorithm update rollouts

Google core, spam and reviews updates as they start and finish, taken from Google's own status feed.

Content decay

Pages that newly became severe or moderate decayers this week. The standing set is never re-announced.

Experiment readouts

A weekly result for each running SEO experiment: uplift with its confidence interval, the p-value, and a warning when the test is underpowered.

Quota, IndexNow and Bing

URL Inspection quota exhausted for a property, failed IndexNow submissions, and new Bing Webmaster crawl issues.

Every alert type is documented, detector by detector, in the alerts reference.

How to set it up

Teams hands out the channel URL, GSC Wizard posts to it. Three steps, about two minutes.

Create the workflow in Teams

Open the channel, click its ··· menu, choose Workflows, and pick the template “Post to a channel when a webhook request is received”. Copy the URL it gives you.

Paste it into GSC Wizard

Sign in, open Account, then Slack, Teams & Webhooks, and add a Teams channel. Tick the alert types it should receive and set a minimum severity.

Send a test card

One click posts a test card to the channel, and a second button posts four example alerts so you can see exactly what each kind looks like. Nothing inside the workflow needs editing.

Open Teams settings

Need an account first? Start free. Step-by-step version: Microsoft Teams docs.

Data and permissions

What actually moves between GSC Wizard and Teams

Posting your search performance into a channel is the whole feature, so it is worth being exact about it.

Into Teams

The property the alert is about, and the date or period it covers.
The numbers behind it: the metric, the actual against the expected value, the size of the change.
For indexing and decay alerts, the affected URL or query.
A link back to the report inside GSC Wizard, which still requires a login to open.

Each entry posts to exactly one channel. Everyone who can read that channel can read those numbers, so choose it deliberately: a private channel stays private.

Out of Teams

Nothing.

GSC Wizard holds one webhook URL per channel and no permission on your Microsoft 365 tenant. It cannot read messages, list channels, see members or post anywhere you did not paste a URL for. Requests are sent over HTTPS to public endpoints only, and every URL is re-checked on each send, including redirects.

Turning it off

Two ways, either is enough. In GSC Wizard, disable or delete the channel entry and delivery stops immediately. In Teams, delete the workflow and the URL stops accepting posts; GSC Wizard retries a failing endpoint a few times, then disables the entry on its own and shows the reason in settings.

Full detail lives in the Privacy Policy and the Terms of Service. Questions go to support@gscwizard.com.

Frequently asked questions

How do Search Console alerts get into Microsoft Teams?

Through a channel webhook URL that Teams gives you. Open the channel, choose Workflows from its menu, and create one from the template “Post to a channel when a webhook request is received”. Paste the URL it hands you into GSC Wizard under Account, then Slack, Teams & Webhooks. When a detector fires, GSC Wizard posts an Adaptive Card to that URL and Teams renders it in the channel.

Do I need to install an app or get admin approval?

No. There is no GSC Wizard app to add to Microsoft Teams and nothing to approve tenant-wide. Anyone who can create a workflow on a channel can set it up. A legacy Incoming Webhook connector URL also works, though Microsoft is retiring connectors in favour of Workflows.

What Search Console data is sent to Teams?

Only what the card shows: the property, the metric and dates behind the alert, the numbers such as actual against expected, and a link back to the report. Anyone who can read that channel can read those numbers, so pick the channel deliberately. Nothing is read back out of Teams.

Can I get scheduled Search Console reports in Teams?

Not yet. Teams channels receive event-driven alerts. Scheduled daily, weekly and monthly reports are posted by the Slack app, which has a bot able to hold a conversation in the channel. If you want scheduled reports today, use Slack; if you want to know the moment something breaks, Teams covers it.

Can different properties go to different channels?

Yes. Add one Teams channel per destination, each with its own webhook URL, alert types and minimum severity. A channel for critical incidents and a channel for weekly content decay is a common split.

What does it cost?

Nothing extra. It is included in every paid GSC Wizard plan and in the free trial, with no per-channel or per-alert charge.