Automation guide
Scheduled SEO monitoring with nightly crawl automation
Agencies and ops teams run XenonFlare crawls on a schedule — cron on a VPS, Kubernetes CronJob, or serverless worker — using the same REST API as CI integrations.
Customer workflow
“We cron a bash script at 2 AM UTC that queues scans for 28 properties, polls until complete, and posts report links to each client's Slack channel via GET /reports.”
Agency ops team on XenonFlare Growth
- 28 sites nightly
- Cron + Idempotency-Key
- reports:read for clients
Nightly workflow
- Create API keys with jobs:write and jobs:read scopes
- Script queue + poll (bash, Node, or Python)
- Schedule with cron — e.g. 2:00 AM UTC daily
- Alert on score delta or new critical issues in your own tooling
- Use reports:read to fetch public report URLs for clients
What you get
- Queue scans with POST /properties/:id/scans and Idempotency-Key per run
- Poll GET /jobs/:id until completed — typical runs finish in minutes
- List shared reports via GET /reports for stakeholder links
- Complements in-app weekly/monthly scan schedules on each property
- Pair with Search Console in the app to prioritize high-traffic URLs
FAQ
- Is scheduled monitoring included on Free?
- The web app supports scan schedules on Free with plan limits. Automated API access requires Starter or Growth for API keys.
- How is this different from in-app scheduling?
- In-app schedules run inside XenonFlare. API scheduling lets you integrate with your own alerting, ticketing, and client portals.
- Can I monitor multiple properties in one cron job?
- Yes. Loop property IDs from GET /properties and enqueue scans sequentially or with your own concurrency limits.
Start on the Free plan
No credit card required. Upgrade when you need unlimited scans, AI fixes, or higher crawl limits.
Get started