Set schedules, alerts, and team notifications

Choose a useful cadence and keep urgent changes separate from routine summaries.

01

Match cadence to change rate

Use frequent crawls for sites that release often and a slower cadence for stable properties. The plan controls which timing options are available. A schedule consumes crawl allowance when it runs, while opening an existing report does not.

02

Separate alerts from summaries

Immediate alerts are for material changes, such as a broken robots rule, missing sitemap, or strong regression. Digests summarize saved health, search, link, ranking, traffic, and AI visibility movement on a routine schedule.

03

Test delivery

Send a test digest before relying on Monday delivery. When using a Slack-compatible webhook, confirm the destination channel and remove stale endpoints when team ownership changes.

Apply the guideReturn to the evidence and complete one verifiable action.
Open the app ↗
Did this guide solve the task?No account or workspace data is recorded here.