Collected data

ChatGPT: citations

Available source links accompanying collected answers.

Collection target: chatgpt. Field availability depends on the provider output shown below.

Understand the collected data

Chatbot responses expose sources with title and url. Google AI Overview sources appear inside aioverview when an overview is present. Source links do not prove which document a model read or which claim it supports.

Collected data

Sources can be empty. Citation frequency, domain grouping and claim attribution are customer-built analysis, not response fields.

The chatgpt target collects responses through the web interface. Each successful run carries its run identity, capture time, text, markdown, pageUrl and sources. Text, markdown and pageUrl can be null; sources can be empty. Answers and sources vary by run. Country routing is a request option, not a guarantee of a particular language or provider location. Build your own analysis from the collected responses.

Provider output examples

These are illustrative successful run excerpts, not full result files or calculated metrics. Submit POST /v1/crawl-jobs, track completion, then download the authenticated result. Outputs depend on the target; a chatbot has no news articles or Google position fields.

{
  "runNumber": 1,
  "runTaskId": "9a7536e7-b610-420a-a34c-5f829956f4d3",
  "status": "completed",
  "capturedAt": "2026-10-09T10:01:00.000Z",
  "text": "Illustrative captured answer text.",
  "markdown": null,
  "pageUrl": "https://chatgpt.com/",
  "sources": []
}
Illustrative provider output. Empty lists and null fields are valid; inspect failedRuns in the result file.
Full result format and failed-run handling →

Citations FAQ

Does the API calculate citations?
Chatbot responses expose sources with title and url. Google AI Overview sources appear inside aioverview when an overview is present. Source links do not prove which document a model read or which claim it supports.
How should failed or empty collections be handled?
Inspect per-target failedRuns and each successful run identity. Empty sources or null fields are valid output; a missing failed run is not an empty successful answer. A completed job can contain failed collections.

Use collected data to build your own reporting and analysis. Our team arranges API access and follows up with next steps.