Skip to content

Apps

Overwatch features are packaged as six apps, installed per site. Each app is a toggle on the site row, set at registration (POST /v1/sites) or later (PATCH /v1/sites/{id}), and each contributes its own report to the API and to the stakeholder report.

App Toggle Default What it does
Broken Links scannerEnabled on Periodic dead-link crawl; the dead-link report
Accessibility a11yEnabled off Rendered axe-core scan; the accessibility report
SEO seoEnabled on On-page checks during the crawl; the SEO report
AI readiness aiEnabled on* AI-crawler access and readability checks during the crawl; the AI readiness report
Performance performanceEnabled on Daily CrUX sync; the Core Web Vitals report
Uptime uptimeEnabled on Multi-region monitors; the uptime reports

* When aiEnabled is omitted at registration, AI readiness defaults on only if Broken Links, Accessibility or SEO is on. It rides an existing crawl but never schedules one by default; send aiEnabled: true to run it on its own.

Performance and Uptime default on because they are inert until there is CrUX data for the origin, respectively a registered monitor — installing them costs nothing.

The Broken Links, Accessibility, SEO, and AI readiness apps share the crawl as infrastructure: the crawl is scheduled when any of them is enabled and unscheduled only when all four are off. Broken Links records dead-link rows during the crawl; SEO extracts on-page fields (titles, descriptions, canonicals, robots, structured data) from the same page fetch; Accessibility renders the crawl’s persisted page set on its own cadence; AI readiness reads the same fetched HTML for crawler access, snippet directives and structured data. Disabling one app never silently disables the others’ data source.

SEO and AI readiness add no metered work of their own — they ride the crawl’s page allowance. (AI readiness makes one extra GET /llms.txt per run.)

Consequences to be aware of:

  • POST /v1/sites/{id}/crawl responds 409 when all four crawl-consuming apps are off.
  • A PATCH only changes the toggles it sends. To stop all crawling, send aiEnabled: false along with scannerEnabled, a11yEnabled and seoEnabled — AI readiness alone keeps the crawl scheduled.
  • GET /v1/sites/{id}/report responds 404 when Broken Links is off — an a11y-only site’s crawls record no dead-link rows.

Toggling an app off keeps its data:

  • Uptime off stops probing all the site’s monitors immediately, but the monitors and their history remain; toggling back on resumes the previously enabled ones.
  • Accessibility off unschedules the render pass; past runs and reports stay readable.
  • SEO off stops the extraction and makes the report respond 404; past runs’ snapshots are kept and the report returns when re-installed.
  • AI readiness off stops the extraction and makes the report respond 404; past runs’ snapshots are kept and the report returns when re-installed.
  • Performance off stops the CrUX sync and makes the report respond 404.

Each app’s consumption is metered separately against per-site allowances — see Quotas & usage.