Developer API
SEO automation API for agencies, SaaS teams, and DevOps
Operate SEO at scale: schedule nightly crawls, gate deploys in CI, and manage properties from internal tools — all through organization-scoped Bearer keys.
Combine jobs:write for crawls with jobs:read for polling. Search Console metrics sync in the web app today; queue crawls via API.
Customer workflow
“Our ops team runs POST /scans/batch every night across 40 client properties. Webhooks notify Slack when a job fails, and we export API activity logs monthly for compliance.”
Agency portfolio automation on XenonFlare Growth
- 40 sites nightly
- Batch scans + webhooks
- GSC + crawl correlation
What you get
- Organization-scoped keys with explicit permission scopes
- Test keys (`xf_test_…`) for CI and integrator sandbox — writes are no-ops
- Queue scans and crawls — same seo-scan job type under the hood
- Filter jobs by status, propertyId, and type
- Usage and plan limits via GET /usage and GET /limits
- Works alongside WordPress apply and GSC sync in the web app
- OpenAPI spec for Insomnia, codegen, and API clients
FAQ
- Who is the SEO API for?
- Agencies monitoring client portfolios, SaaS teams guarding marketing sites, and engineering orgs running SEO checks in CI before production deploys.
- Does the API include Google Search Console data?
- Search Console sync runs in the web app (read-only OAuth). Use the API to automate crawls; use the dashboard to correlate GSC metrics with crawl scores.
- What are the default rate limits?
- Read requests are capped per API key per hour; writes have a lower hourly cap plus an org-wide daily safety limit. See the API docs for current defaults.
Ready to automate?
Upgrade to Starter or Growth, create scoped API keys, and follow the guides for cron or CI integration.
Create workspace