---
title: "Trigger a site audit"
method: POST
path: "/api/mcp/projects/{projectId}/audits"
tags: ["Audits & Issues"]
---

# Trigger a site audit

`POST /api/mcp/projects/{projectId}/audits`

Trigger a site audit (technical + AEO) for the project's pages and return the orchestrator job id; results land on GET /audits. Audits every tracked page by default, or the optional pageIds. Always audits the project's own verified domain. Action endpoint — enforces runnable-state, blocks pitch projects, and consumes the monthly audit quota. Requires the `write` scope. Supports `Idempotency-Key` replay.

## Path parameters

- `projectId` string, uuid, required

## Headers

- `Idempotency-Key` string

## Request body

- AuditTriggerRequest
  - `pageIds` string[] — Pages to audit. Omit to audit every tracked page in the project.

## Response `200`

Audit started.

- AuditTriggerResponse
  - `success` boolean, required
  - `jobId` string, required
  - `projectId` string, uuid, required
  - `pageCount` integer, required
  - `pageIds` string[]
  - `baseURL` string, uri
  - `message` string

## Other responses

- `400` — Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.
- `401` — Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.
- `403` — Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.
- `404` — Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.
- `409` — Another request with the same `Idempotency-Key` is still executing. `Retry-After` (5 seconds) is always present — retry with the SAME key once it elapses.
- `429` — Rate limited. Usually the per-API-key REST limit (600 requests/minute); on Google-backed endpoints it can also relay an upstream Google rate limit. `Retry-After` (seconds) is present when the limit was applied by Searchable's own rate limiter; it may be absent when an upstream provider rate-limits.

---

[API](https://skmtc.net/searchable/apis/searchable-rest-api.md) · [All operations](https://skmtc.net/searchable/apis/searchable-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/searchable/searchable-rest-api/revisions/301b04e800ed/schema)