# Direct answers for answer engines

German title: Direktantworten für Answer Engines

> A direct answer is a short factual paragraph at the top of a page that answers the lead question, complemented by FAQ, tables and lists. These are editorial rules of this website. Google requires no special structure, FAQ rich results are discontinued, and preferential use by AI systems is not verified.

Manfred Sulzmann: “The direct answer is your elevator pitch for machines. One sentence that says it all—without buzzwords.”

## Facts

- **Position:** Direct answer at the top (editorial rule)
- **Google:** no special structure required
- **FAQ rich results:** discontinued (note 8 May 2026)
- **Effect on AI citations:** not verified

## Direct answer (editorial rule)

- The first sentence answers the lead question in a complete sentence.
- The second sentence gives the limitation or context.
- Sources follow at the end; promotional language is omitted.

A target of 50–75 words is a convention of this website and not a verified threshold. A meta description sits in the head and serves the preview; the direct answer is in the visible text.

## Other structures

Format and benefit for readersFormat Purpose
Definition at the start Clarify the topic immediately
Table Comparable details side by side
Numbered list Order of steps
FAQ block Answer real user questions briefly (two to four sentences, with a source)

## Status of FAQ markup

- August 2023: HowTo rich results removed; FAQ rich results only for well-known government and health sites (Google blog, read here through a secondary source).
- 8 May 2026: note in Google's documentation that FAQ rich results are discontinued.

If FAQPage markup is output, it must mirror the visible questions and answers; a benefit for Google rich results is not to be expected.

## What Google says about structure

For AI Overviews Google requires no special structure. The documentation stresses that content should be text-based, indexed and snippet-eligible. The helpful-content guidance asks about value for people (Who, How, Why), not about a format.

## Not verified

The 2023 Google blog post was not readable in this check; the 2023 details rely on a secondary source. The note of 8 May 2026 was read in Google's documentation; according to Google the documentation page was removed on 15 June 2026 and can no longer be linked.

## Sources

- Google Search Central: AI features and your website (primary source)
- Google Search Central: Influencing your title links (primary source)
- Google Search Central: Creating helpful, reliable, people-first content (primary source)
- Google Search Central Blog: Changes to HowTo and FAQ rich results (Aug 2023) (primary source)
- Red Shark Digital: Google HowTo/FAQ rich results update (secondary source)

Checked on: 24 October 2026.

## Questions

### Direct answer or meta description?

The meta description sits in the head and serves the preview; the direct answer is in the visible text.

### How long must a direct answer be?

There is no verified value. This website follows the convention of a short paragraph.

### Is FAQPage markup still worthwhile?

Not for Google rich results. As part of a well-structured document it does no harm if it mirrors visible content; a benefit for AI answers is not verified.

### Are structured paragraphs cited more often?

That is not verified.

### Do I always need tables?

No. They pay off for comparisons and items with several attributes.

## Related

- [What is AEO? Answer engine optimization explained](https://munichmedia.com/reports/was-ist-aeo.md)
- [FAQ structure: value and status of FAQ markup](https://munichmedia.com/reports/faq-struktur-fuer-aeo.md)
- [Google AI Overviews: what Google documents](https://munichmedia.com/reports/google-ai-overviews.md)

Canonical HTML: https://munichmedia.com/reports/direktantworten-answer-engines