Pick a channel, pick a property, pick a cadence. GSC Wizard posts the scheduled report and raises an alert when something changes state, so nobody has to remember to open a dashboard.
Included in every paid plan and in the free trial. Install starts from your GSC Wizard account.
Page 1: 14 entered, 6 left
A weekly report as it arrives in Slack. Sections are per subscription, so you can switch any of them off.
Reports arrive on a schedule you set. Alerts arrive when something actually changes, not on a timer.
Not on Slack? The same alerts post to Microsoft Teams as native cards.
Daily, weekly or monthly, for one property or all of them. You choose the hour, the weekday or day of month, and the timezone. Every message names its data window, because Search Console data lags around three days.
Post the moment a detector fires, or bundle a day's worth into one message. Pick the alert types you want per channel and set a minimum severity so the noisy end stays out.
Every alert carries Acknowledge and Snooze buttons. Clicking one rewrites the message in place with who handled it, so the channel can tell at a glance what is still open.
A summary sized for a channel, not a dashboard dumped into chat. Each section is a toggle on the subscription.
Clicks, impressions, CTR and average position, each against the matching earlier period so the delta means something.
The queries or pages that gained and lost the most clicks. Switch the dimension per subscription.
How many queries entered or left page one, plus the biggest rank gains and drops for the period.
Newly decaying pages, open indexing warnings and traffic anomalies, each one a link straight to the report that explains it.
Enable the ones you want per channel. Recoveries are their own messages, so a resolved problem closes its own loop.
A Search Console token stopped refreshing, so ingest and monitoring would otherwise fail quietly. A recovery message follows when the account is reconnected.
Tracked URLs that went deindexed, stopped being crawled, errored, came back, or whose checks were paused.
A weekly CrUX scan that reports the metric, the form factor and the move between buckets, with a recovery message when it comes back.
A day that falls outside its own day-of-week baseline. Set the sensitivity, the metrics, and whether spikes count as news.
Change points: a level shift that held, not a single bad day. When the date overlaps a known Google update, the message says so.
Google core, spam and reviews updates as they start and finish, taken from Google's own status feed.
Pages that newly became severe or moderate decayers this week. The standing set is never re-announced.
A weekly result for each running SEO experiment: uplift with its confidence interval, the p-value, and a warning when the test is underpowered.
URL Inspection quota exhausted for a property, failed IndexNow submissions, and new Bing Webmaster crawl issues.
Type /gscwizard check https://example.com/page and GSC Wizard runs Google's URL Inspection on that URL and answers in the channel, visible only to you.
The command runs against the property the channel is already subscribed to, uses that property's inspection quota, and never reveals which teammates connected the workspace.
Indexed. Last crawled 3 days ago. Google-selected canonical matches the submitted URL.
The install starts inside GSC Wizard, because a subscription needs a Search Console property as well as a channel.
Sign in to GSC Wizard with Google and connect the properties you want to report on.
Open Account, then Slack, and click Add to Slack. Approve the app for the workspace and you are returned to the settings page.
Pick the channel, the property, report or alerts, and the schedule. Invite the bot to the channel first if it is private.
One click posts a test to the channel, so you know it is wired up before the first scheduled send.
Need an account first? Start free.
Posting your search performance into a workspace is the whole feature, so it is worth being exact about it.
Each subscription posts to exactly one channel. Everyone who can read that channel can read those numbers, so choose it deliberately: a private channel stays private.
The app holds no message-history permission, so it cannot read channel conversations. Bot tokens are encrypted at rest with AES-256-GCM and are never shown in the browser.
Disconnect in Account, then Slack: the bot token is revoked with Slack and that workspace's subscriptions are removed. Or remove the app from the Slack workspace, which invalidates the token; GSC Wizard notices on its next send, marks the workspace revoked and pauses its subscriptions instead of retrying forever. The same happens when a channel is archived or the bot is removed from it: the subscription is disabled and the reason is shown in settings.
Full detail lives in the Privacy Policy and the Terms of Service. Questions go to support@gscwizard.com.
It posts two things into channels you choose: scheduled Google Search Console reports on a daily, weekly or monthly cadence, and event-driven SEO alerts. Alerts cover a broken Google connection, indexing warnings, Core Web Vitals regressions, algorithm update rollouts, traffic anomalies, sustained traffic shifts, content decay, weekly experiment readouts, URL Inspection quota exhaustion, IndexNow submission failures and Bing crawl issues. Alert messages carry Acknowledge and Snooze buttons so the channel can see who picked something up.
Sign in to GSC Wizard, open Account and then Slack, and click Add to Slack. Slack asks you to approve the app for a workspace. You are returned to the settings page, where you create a subscription: pick the channel, the property, whether it is a report or alerts, and the schedule. Invite the bot to a private channel first if you want to post there.
Only what the message shows, and only to the channel a subscription names: the property URL, the metrics for the period with their comparisons, the top queries or pages that moved, the counts behind the watch items, and the details of any alert you enabled. Anyone who can read that channel can read those numbers, so pick the channel deliberately.
No. The app holds no message-history scope, so it cannot read channel conversations. It reads the workspace channel list so you can pick a destination, and it receives what you explicitly send it: a slash command you type, or a button click on one of its own alert messages.
Yes. Each person connects the workspace from their own GSC Wizard account, and each subscription posts with its owner's data access. You can only subscribe a property you own or have been granted access to.
Either side works. In GSC Wizard, open Account and then Slack and click Disconnect: the bot token is revoked with Slack and the workspace subscriptions are removed. In Slack, a workspace admin can remove the app from workspace settings, which invalidates the token; GSC Wizard detects the dead token, marks the workspace revoked and pauses its subscriptions.
The same SEO alerts as native Adaptive Cards in a Teams channel. No app to install and no admin approval.
The same alerts as signed JSON, for Zapier, Make, n8n, an incident tool, or a service you wrote yourself.
Ask your Search Console data questions directly from an AI assistant over MCP, with a revocable API key.
Connect a workspace, pick a channel, and the first report lands on your next scheduled send.