Questions and answers (mobile)

QAPage markup lets Yandex display a question and its answers as a structured block in mobile search results, selecting what it judges to be the best answer.

Content requirements

• The microdata must be error-free — check it in the console validator.
• One question per page, with its answers. The algorithm picks a single best answer for the snippet. A page collecting twenty questions is not a candidate.
• Long answers may be truncated, ending with either Más (expanding inside the snippet) or Read more (opening your page).

The fields

• name (Text) — the question title, as a property of Question.
• acceptedAnswer o suggestedAnswer (Answer) — the best or an ordinary answer.
• text (Text) — the answer text, on Answer.
• upvoteCount (Integer) — votes for that answer, on Answer.
• isAccessibleForFree (Boolean) — and this one is a lever rather than a description.

The isAccessibleForFree decision

Set it to false and the answer is truncated regardless of length, with a Read more link to your page. Set it to true, or omit it, and a short answer can be read entirely inside the search results.

That is a genuine choice, not a technicality. Full display serves the user and may cost the visit; truncation guarantees the click and gives a worse experience. Yandex has made the trade explicit, which is unusual and worth using deliberately — a support answer is best given in full, a piece of expertise that leads somewhere is not.

Where this fits

The natural candidates are single-question support pages, community answer threads, and detailed FAQ entries given their own URL. A combined FAQ page has to be split before this markup can apply, which is a content-structure decision with consequences well beyond the snippet.

The usual caveat

Yandex does not guarantee the information will appear, and may use it in whole or in part, in any of its services.