Naver answer text tracking
naveranswer_textAnonymous
Naver answers are stored verbatim in Korean, so a Korean-market report can quote the sentence rather than paraphrase a translation of it.
How it renders
The answer body, stored unmodified.
Sampling
Every sample is stored, not just the modal one. Divergence between samples is the raw material for the volatility metrics.
Gotcha
Korean sentence structure puts qualification at the end. A truncated or translated excerpt frequently reverses the meaning of a Naver answer, so we store the whole thing in the original.
What the API returns
A single collection call against Naver for the answer text field, sampled n times and returned as one object per prompt.
{
"engine": "naver",
"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 →Naver answer text FAQ
- Do you translate Naver answers?
- Only at report time, always alongside the Korean original.
- Is anything truncated?
- No. Korean qualifiers land at the end of the sentence, so truncation is actively dangerous here.
Quote the Korean answer, not a paraphrase
We will scope verbatim retention for your Korean prompt set.
Across every engine
Compare how answer text behaves on every engine we track.
Answer text across all engines →