Documentation
Scheduled reports in Slack, Teams or a webhook
Post a property's clicks, impressions, CTR and position, with its top queries, pages or ranking movers, to a channel daily, weekly or monthly.
A scheduled report posts one message per property on a rhythm you set. Each message compares the last 7 or 28 days of Search Console data with the same number of days before, gives clicks, impressions, CTR and average position with their change, and adds a ten-row table of queries, pages or ranking changes. It can go to any channel you have added: Slack, Microsoft Teams or a webhook.
Create a schedule
Click New scheduled report in the Scheduled reports section (the button needs at least one channel), then fill in the form:
- Channel: where the message goes.
- Report: one of the four types below.
- Period: Last 7 days vs the 7 before or Last 28 days vs the 28 before.
- Cadence: Daily, Weekly (with a Day of week) or Monthly (with a Day of month).
- Send at: an hour from 00:00 to 23:00 UTC. New schedules start at 08:00 UTC.
- Properties: tick the ones to report on.
- Enabled: untick it to save the schedule paused.
Click Create schedule, then Send now on its row if you want to see the first message straight away (read what that does to the schedule below).
The four report types
Every type opens with the same four headline figures. The table underneath, and the page behind Open report, differ.
| Report | Table in the message | Open report goes to |
|---|---|---|
| Performance summary | The ten queries with the most clicks, with the earlier period's clicks and the change | The property's dashboard |
| Top queries | The same ten queries | Queries |
| Top pages | The ten pages with the most clicks, with the earlier period's clicks and the change | Pages |
| Ranking movers | The five queries that gained the most positions and the five that lost the most, with position before and after, the change and clicks | Rank Changes |
Ranking movers looks at queries with at least one click in either period. A query that stopped appearing is shown with 100 as its new position.
Which dates a report covers
The period always ends on the day before the send, counted in UTC, because Search Console needs time to collect and process each day (Search Analytics API reference). A weekly report with a 7-day period sent on Monday 12 October 2026 covers 5 to 11 October and compares it with 28 September to 4 October. The message spells out both windows.
Cadence and period are independent. A daily report with a 28-day period posts a rolling four-week view every day, while a monthly report with a 7-day period shows only the final week before the send.
Day, hour and the once-per-period rule
- Daily sends once per UTC calendar day, Weekly once per ISO week (Monday to Sunday), Monthly once per calendar month.
- Day of month 31 means the last day of every month. A day a month does not have, such as 30 in February, also falls on its last day.
- The hourly job starts on the hour, so a report set for 08:00 UTC arrives during that hour. There is no time zone setting: convert your local time to UTC when you pick the hour.
- Send now posts at once and counts as the period's delivery. Use it on Tuesday for a weekly report due on Thursday, and nothing more is posted that week.
- Changing the day or hour after this period's report went out takes effect from the next period.
- A send that fails still uses up its period. Fix the cause, then use Send now rather than waiting.
One property or many
Tick one property for a focused report, or several to get one message each. With nothing ticked the schedule covers every property in your account, looked up again at each send, so properties you add later are included automatically. Each message stands alone with its own Open report link.
Managing schedules
Each schedule is a row showing its type, period and properties, the channel, the timing in words (for example Weekly · Monday 08:00 UTC), when it last ran and how that went. The last column reads sent with the number of messages, partial when some properties failed, failed or skipped, followed by the reason.
- Edit changes anything, the channel and report type included.
- Pause keeps the schedule but stops it posting; Resume brings it back.
- Delete removes it for good.
When a trial ends without a plan, every due report is recorded in Delivery history as skipped, with the reason, and nothing is posted until a plan is active.
For a one-off message, use Send to Slack on a report page instead. It posts the table you are looking at, with your filters and dates (Using AutoPSEO in Slack).