Not supplied by this target

Perplexity: position is not supplied

Perplexity responses do not supply a position field or source ranking.

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

What this target supplies instead

Perplexity sources contain title and url. Their array order is not a documented ranking or citation position. The API does not supply avg_position or other position aggregates.

Not supplied by this target

Google Search and Google News have module-specific positions. Those fields do not apply to chatbot responses; do not invent a ranking from source array order.

The perplexity target returns text, markdown, pageUrl and sources with the successful run identity and capture time. Source lists may be empty and response fields may be null. Perplexity may use operator-configured sessions. Availability depends on deployment configuration and provider behavior; no response or citation count is guaranteed.

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://www.perplexity.ai/",
  "sources": []
}
Illustrative provider output. Empty lists and null fields are valid; inspect failedRuns in the result file.
Full result format and failed-run handling →

Position FAQ

Does the API calculate position?
Perplexity sources contain title and url. Their array order is not a documented ranking or citation position. The API does not supply avg_position or other position aggregates.
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.