How to use the Site Audit and Site Monitoring API

The Site Audit and Site Monitoring API lets you pull your technical SEO data out of Sitechecker into your own tools and reports: the current state of a crawl, the full list of issues and affected pages, deep per URL context, and every change and content event between crawls.

For exact paths, full field lists, and a live request builder, keep the API reference open alongside this article.

What it is

Both are modules inside the Sitechecker Public REST API, sharing the same key, projects, and error handling. They answer two questions:

Site Audit API answers "what is the state now?" It returns the latest finished crawl: summary score, issues, crawled pages, and per URL context.

Site Monitoring API answers "what changed, and when?" It returns deltas and events between crawls or across a date range.

In short: Site Audit is the snapshot, Site Monitoring is the log.

If you need the current state of a page, use Site Audit. If you need to know a title changed last Tuesday, use Site Monitoring. Monitoring points you back to Site Audit for current detail rather than repeating it.

Who can use it

Public API access is a plan-level entitlement, available on Premium and Enterprise plans. Without it, requests return MISSING_PUBLIC_API_ACCESS . You also need your API key and a project with a finished crawl.

Setup

Authentication and project setup are the same as the rest of the Public API. Follow the getting started guide for your API key and project_id . In short: send the key as Authorization: Bearer <your_api_key> and use the base path https://sitechecker.pro/api/v1 . You can only access your own account's projects.

Grab your project's segments first so you can scope calls to the pages that matter (Sitechecker auto creates "All pages" and "Indexable pages," plus any custom ones):

curl --url 'https://sitechecker.pro/api/v1/segments?project_id=12345' \
  --header 'Authorization: Bearer <your_api_key>'

The endpoints

Site Audit (current state)

Endpoint	What it returns
`audit_summary`	Website Score, crawled pages, and issue counts by severity, each with a diff vs the previous crawl.
`audit_issues`	Detected issues, filterable by `category` , `severity` , `segment_id` .
`audit_pages`	Crawled URLs with key audit attributes (filter by `issue_id` , `url` ).
`page_details`	Deep technical audit context for one URL (on demand).
`page_content`	Heavier page level content data for one URL (on demand).

Site Monitoring (changes)

Endpoint	What it returns
`site_audit_updates_summary`	Trend points, added/removed issue counts, and Website Score movement over a range.
`site_audit_updates`	Which issues changed in a crawl, and how many URLs added or removed.
`site_audit_update_pages`	The URLs added or removed for one issue change (list only).
`content_updates_summary`	Total events, new/deleted/changed pages over a range.
`content_updates`	Content and page events: URL, event type, before/after, `content_update_id` , `has_details` .
`content_update_details`	The specifics of one content update (by `content_update_id` ).
`page_monitoring_summary`	Trend points for one URL: which crawls had changes and how many.
`page_monitoring_changes`	Drilldown for one URL in one crawl (audit issues and content events).
`page_monitoring_change_details`	Conditional, only where the drilldown cannot carry enough detail.

Shared: projects , segments , segment_details .

Example, critical issues on a segment:

curl --url 'https://sitechecker.pro/api/v1/audit_issues?project_id=12345&severity=critical&segment_id=<segment_id>&limit=50' \
  --header 'Authorization: Bearer <your_api_key>'

Rules to remember

Site Audit is current state, Site Monitoring is changes. Do not rebuild current state from deltas; monitoring points you to page_details for current detail.
direction vs change_source are different. direction is added / removed / all (delta direction). change_source is all / site_audit / content (Page Monitoring source, default all ).
Issue changes and content events are separate objects. Site Audit Updates covers issues; Content Updates covers content and page events.
Segments scope everything. Pass segment_id to focus summaries, issues, and monitoring on the pages that matter.
Heavy endpoints are per URL and on demand (page_details , page_content ).
Chain IDs (issue_id , crawl_id , content_update_id ) into downstream calls.

Use cases: how agencies use it

White label technical audits at scale. Pull audit_summary and audit_issues per client into branded reports. No per seat fees means you can cover the whole portfolio.
Continuous monitoring and alerting. Poll site_audit_updates and content_updates and push spikes in critical issues or content changes to Slack or email.
Unauthorized change and tamper detection. content_updates surfaces unexpected edits or injected code early, so a hacked page is caught fast.
Deploy regression checks. After a release, diff crawls with site_audit_updates and check key templates with page_monitoring_changes for broken titles, canonicals, or status codes.
Migration and launch QA. Compare before and after crawls at scale: which issues appeared, which URLs dropped, which pages changed.
AI assisted triage. Pipe audit_issues and site_audit_updates into an AI assistant to prioritize fixes and draft client commentary.
Prioritize by segment. Pull summary and issues per segment_id so reports lead with the health of the money pages.
Custom dashboards and fast prospect audits. Feed clean JSON into BI tools, or run one audit_summary call to open a sales conversation with a Website Score.

Common errors

INVALID_API_KEY / REVOKED_API_KEY (bad or revoked key),

MISSING_PUBLIC_API_ACCESS (no entitlement, check plan),

ACCESS_DENIED (project belongs to another account),

PROJECT_NOT_FOUND / SEGMENT_NOT_FOUND , CRAWL_IN_PROGRESS / CRAWL_NOT_FOUND (no finished crawl yet),

INVALID_DATE_RANGE / INVALID_FILTER , RATE_LIMIT_EXCEEDED (slow down and retry).

FAQ

What is the difference between the two? Site Audit returns current crawl state; Site Monitoring returns changes over time. Use Audit for "what is the state now," Monitoring for "what changed and when."

How do I authenticate and get my project ID? Bearer token in the Authorization header plus a project_id , both covered in the getting started guide.

Can I monitor for unexpected content changes? Yes, the Content Updates endpoints report new, deleted, and changed pages, used to catch tampering early.

Need help?

Questions? Reach us at support@sitechecker.pro, or see the API documentation. Happy auditing!