Skip to content

Changelog

Track changes to the Sitechecker Public REST API, including new endpoints, changed parameters, changed response fields, deprecated behavior, and breaking changes.

The API is in beta, so the contract can still change between releases. Changes that require a client to be updated are labelled Breaking; see Access & Limits for what the beta covers.

2026-08-13 — Cross-module metrics on the project list

The project list can now attach the metrics of every Sitechecker module to each project row, so one request replaces a fan-out over the per-module endpoints.

  • Breaking The Site Audit metrics of a project row moved into a nested site_audit object. website_score, crawled_pages, criticals, warnings, opportunities and notices are no longer returned at the top level of a row; read them from site_audit instead. The row still needs include=site_audit for them to be present at all.
  • Added include accepts ga4_insights, gsc_insights, rank_tracker and ai_visibility, and several keys may be combined in one comma-separated request. Each requested module is returned as its own nested object on every project row.
  • Added Every metrics block carries a status of ok, no_data or not_connected, so a project without that integration is reported explicitly instead of returning zeros. Outside ok the metrics of the block read null, which is not the same as a measured zero.
  • Added The analytics blocks echo the window their numbers cover in period and comparison_period, and report each metric alongside a *_change field. The endpoint takes no date parameters: it serves stored aggregations, so the window is the one the project last synced — a stale project reports a stale window rather than an empty one. *_change is the relative change between the two windows in percent, not in percentage points, and is null when there is no baseline to compare against.

2026-07-31 — Public REST API v1 beta release

Released the first beta version of the Sitechecker Public REST API.