Schedules

Manual crawls and pipeline checks are valuable, but they depend on someone triggering them. A schedule adds a steady rhythm against your live sitemap so you are not relying on memory or a deploy to discover issues.

• Catch regressions early. Broken links, redirect problems, and SEO signals often appear after content or infra changes. Regular runs surface them while the change is still fresh.
• See trends, not snapshots. Comparing runs over time makes it easier to spot new clusters of issues or gradual drift instead of judging a single crawl in isolation.
• Complement CI and ad-hoc checks. Pipelines usually run on staging or after deploy; a schedule hits production on a fixed clock and reflects what search engines and users actually see.
• Low ongoing effort. Set the sitemap, recurrence, and limits once—then review results when it suits you, without starting every audit by hand.

Schedules guide — recurrence (UTC/cron), execution mode, and how runs appear in history.