Get page content-intelligence report

Returns a detailed content-intelligence report for a single tracked page, covering SEO performance, AI citations, conversion funnels, traffic, SERP position, keywords, page lifecycle, or activity.

Example: “Show me the SEO performance report for this page”

Usage: pick the report you want with report_type and pass the id of the page to report on. The keyword, SERP, and target-keyword reports need a market to be chosen. Scope the numbers with a date window, and for the AI-citations and keyword reports you can narrow by search text. The longer reports come back in pages of up to 100 (50 by default). Find the page id first by listing pages on the dashboard with the page URL or title.

Response: the requested report for that page: its metrics, trends, and the supporting rows for the chosen report type.

POST /api/v1/business/content-intelligence/page-report

Get page content-intelligence report

cURL

curl --request POST \
  --url https://api.example.com/api/v1/business/content-intelligence/page-report \
  --header 'Content-Type: application/json' \
  --header 'x-project-id: <x-project-id>' \
  --data '
{
  "page_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "market_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "curr_start": "2023-12-25",
  "curr_end": "2023-12-25",
  "prev_start": "2023-12-25",
  "prev_end": "2023-12-25",
  "keyword_intent": [],
  "page": 1,
  "size": 50,
  "sort": "<string>",
  "search": "<string>",
  "category": "all",
  "cursor": "<string>"
}
'

422

{
  "detail": [
    {
      "loc": [
        "<string>"
      ],
      "msg": "<string>",
      "type": "<string>",
      "input": "<unknown>",
      "ctx": {}
    }
  ]
}

Headers

x-project-id · string<uuid> · required

Project ID for tenant scoping

X-Workspace-Id · string<uuid> | null

Overrides the key's workspace

X-API-Key · string | null

User API key

Body

application/json

report_type · enum<string> · required

Which per-page report to return.

Available options: seo_performance, keywords, ai_citations, geo_visibility, lifecycle_status, ai_citations_prompts, ai_citations_platforms, ai_citations_topics, ai_activity, ai_search_funnel, seo_funnel, marketing_traffic, serp_intelligence, search_referrals, content_signals, activity_log, target_keywords, metadata

page_id · string<uuid> · required

The content-intelligence page to report on. Resolve it via get_ci_dashboard view=pages, search= — the page is never referred to by id in natural language.

market_id · string<uuid> | null

Market id; required for keyword/serp/target-keyword reports.

curr_start · string<date> | null

Current window start date - pairs with curr_end/prev_start/prev_end: provide all four or omit all four (defaults to trailing 30 days), else 422. Each range needs start<end, equal current/prior length, and prev_end<=curr_start.

curr_end · string<date> | null

Current window end date - see curr_start.

prev_start · string<date> | null

Comparison window start date - see curr_start.

prev_end · string<date> | null

Comparison window end date - see curr_start.

keyword_intent · enum<string>[] | null

Keyword-intent filter.

The /pages keyword_intent filter: classifies a page by whether its primary target keyword contains any of the project's brand aliases. Modelled on statuses (multi-select; both-or-none selected = no filter). An intent signal, not a traffic signal.

Available options: branded, non_branded

page · integer · default: 1

Page number for paginated reports.

Required range: x >= 1

size · integer · default: 50

Page size for paginated reports.

Required range: 1 <= x <= 100

sort · string | null

Sort for AI-citations tab reports as ':

' (dir=asc|desc); valid keys are per-tab.

search · string | null

Substring filter for AI-citations tab reports (prompt/platform/topic) and the keywords report.

Maximum string length: 200

category · enum<string> · default: all

Category filter for the activity_log report.

Available options: all, changes, impact, alerts

cursor · string | null

Opaque pagination cursor for the activity_log report.

Response

200

application/json

Successful Response