Google AI Mode answer text tracking
AI Mode answers are long, structured and highly variable between samples. We store all of them verbatim, which is the only way to explain a moving number.
How it renders
The full multi-section answer body, captured before parsing.
Sampling
Every sample is stored, not just the modal one. Divergence between samples is the raw material for the volatility metrics.
Gotcha
What the API returns
A single collection call against Google AI Mode for the answer text field, sampled n times and returned as one object per prompt.
{
"engine": "google_ai_mode",
"field": "answer_text",
"prompt": "best ai visibility tracking tool",
"country": "GB",
"language": "en",
"n": 30,
"samples": [
{
"sample_index": 1,
"tokens": 214,
"text": "Several APIs return AI answer data…",
"captured_at": "2026-08-03T09:14:22Z"
}
]
}Response fields
| Key | Type | Notes |
|---|---|---|
| text | string | Verbatim answer, markup stripped. |
| html | string | Original markup, for citation position reconstruction. |
| tokens | integer | Approximate length, useful for drift detection. |
| captured_at | timestamp | UTC collection time for this sample. |
| sample_index | integer | Which of the n samples this is. |
What it costs
Included. Evidence retention defaults to 90 days and is configurable.
See credit pricing →Google AI Mode answer text FAQ
- How long are AI Mode answers?
- Roughly three times the length of a classic query response, which is why per-sample storage costs are real and we surface them honestly.
- Can I diff two samples?
- Yes — every sample is retrievable individually through the evidence export.
Keep the receipts for every AI Mode number
Let's scope evidence retention that matches your reporting cycle.
Other Google AI Mode data
Across every engine
Compare how answer text behaves on every engine we track.
Answer text across all engines →