Apps
Overwatch features are packaged as five 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 |
| Performance | performanceEnabled |
on | Daily CrUX sync; the Core Web Vitals report |
| Uptime | uptimeEnabled |
on | Multi-region monitors; the uptime reports |
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 shared crawl
Section titled “The shared crawl”The Broken Links, Accessibility, and SEO apps share the crawl as infrastructure: the crawl is scheduled when any of them is enabled and unscheduled only when all three 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. Disabling one app never silently disables the others’ data source.
SEO adds no metered work of its own — it rides the crawl’s page allowance.
Consequences to be aware of:
POST /v1/sites/{id}/crawlresponds409when all three crawl-consuming apps are off.GET /v1/sites/{id}/reportresponds404when Broken Links is off — an a11y-only site’s crawls record no dead-link rows.
Uninstall semantics
Section titled “Uninstall semantics”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. - 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.