API-first
CrawlVitals API
Run scans, submit URLs, receive webhooks, compare competitors, generate llms.txt files, and generate MCP discovery files from API routes. Server-to-server routes use Bearer API keys.
Authentication
Use an API key from the app dashboard:
Authorization: Bearer vo_your_api_key
Core routes
POST /api/v1/scan
Run indexability, GEO, and agent-readiness scans.
POST /api/v1/submit
Submit eligible URLs through configured submission channels.
POST /api/v1/webhooks/sitemap-change
Receive CMS/plugin sitemap-change notifications and queue scans.
POST /api/v1/competitors/geo
Compare a competitor URL against optional owned URL scoring.
POST /api/v1/llms
Generate llms.txt content through the API.
POST /api/v1/mcp-discovery
Generate an MCP discovery JSON file through the API.
POST /api/app/indexnow/setup
Generate IndexNow key setup instructions for signed-in users.
POST /api/app/indexnow/verify
Verify an IndexNow key file is reachable.
POST /api/app/indexnow/submit
Submit index-ready URLs to IndexNow.
POST /api/app/search-console/inspect
Inspect Google status for connected Search Console properties.
POST /api/app/push-campaigns
Create Standard or Priority Push campaigns.
POST /api/app/backlinks/monitor
Monitor third-party backlink visibility signals.
Notes
- API keys are hashed at rest.
- Plan gates enforce URL limits and premium features.
- Search Console routes require a connected Google integration.
- IndexNow routes require a verified key file before production use.
- The API returns structured JSON suitable for dashboards, workflows, and automation.