list_page_audits

list_page_audits returns a project's page optimizations, newest first: the page, the prompt it was optimized for, the status, how many changes were proposed and whether the user applied them. Legacy page audits, created before September 2026, come in the same list with their original figures (GEO score, modification count), read-only.

When to use

• Before run_page_audit, to skip a page already optimized for the same prompt.
• After a batch, to see which optimizations reached COMPLETED without polling each auditId.
• To report progress: appliedAt tells which optimizations the user has put live.

Input

Response

{
  "data": [
    {
      "id": "clx_page_42",
      "version": 3,
      "pageUrl": "https://example.com/services",
      "pageTitle": "Websites for craftsmen",
      "prompt": { "id": "clx_prompt_7", "text": "best web designer for craftsmen" },
      "status": "COMPLETED",
      "changeCount": 6,
      "geoScore": null,
      "appliedAt": "2026-09-30T08:12:00.000Z",
      "createdAt": "2026-09-29T10:00:00.000Z",
      "updatedAt": "2026-09-29T10:01:32.000Z"
    },
    {
      "id": "clx_rep_11",
      "version": 2,
      "pageUrl": "https://example.com/",
      "pageTitle": "Home",
      "prompt": null,
      "status": "COMPLETED",
      "changeCount": 13,
      "geoScore": 58,
      "appliedAt": null,
      "createdAt": "2026-08-02T09:00:00.000Z",
      "updatedAt": "2026-08-02T09:01:10.000Z"
    }
  ],
  "pageInfo": { "hasMore": false, "nextCursor": null, "totalCount": 2 }
}

• version: 3 for an optimization, 1 or 2 for a legacy page audit.
• prompt: the target prompt, null for a legacy audit (they had none).
• changeCount: changes proposed (modifications for a legacy audit).
• geoScore: legacy audits only, null otherwise.
• appliedAt: when the user marked the changes as applied.

The full result of one row is one get_page_audit call away.

Tips and patterns

• Filter on failures with filters.status: ["FAILED"] to find optimizations to relaunch.
• Group by page client-side on pageUrl to see every prompt a page was optimized for.
• Compare before and after: an optimization with appliedAt set can be checked against list_prompt_results on the same prompt.

Related tools

• run_page_audit: start an optimization.
• get_page_audit: fetch one result.
• list_prompt_results: check citations after the page went live.