No direct-answer pattern follows a question heading
question_heading_without_direct_answer · Opportunity
This notice appears when an English or Ukrainian page has a supported definition question, such as “What is sourdough?” or its Ukrainian equivalent, and the first paragraph in the same section does not begin with the same topic followed by “is”, “are”, “was” or “were” (in Ukrainian, a dash or a supported linking word), or no paragraph follows before the next heading or section. Opening with a direct answer can help readers; the notice is optional and checks only this wording pattern.
Severity: Notice. An optional opportunity, not an error: it checks a wording pattern, not whether the answer is right.
Why it matters
A research paper on generative engine optimisation reports benchmark experiments in which content edits changed how visible a source was in generated answers; it is research, not a search-engine policy, and does not promise that this pattern earns citations. A clear first sentence also helps readers who scan headings.
What to do
- Open the finding: it lists each question heading checked, with the first paragraph after it and why it was reported.
- Where it helps the reader, start that section with a sentence that names the topic and answers, such as “Sourdough is bread leavened with…”.
- Keep that answer in a paragraph directly under the heading, in the same section, before any list, table or image.
When to leave it as it is: If the section is better served by another form, such as a list or a story, dismiss the notice.
What we read
We read the original HTML of indexable pages that returned 200 and have one unique explicit main region, when the page declares English or Ukrainian; there is no minimum word count. Only headings H1–H6 that end with “?” or “？” are questions, and only “What is/are …?”, “Who is/are …?” and the supported Ukrainian equivalents are checked. A declarative heading such as “How we work” is not a question.
For each, we take the first paragraph after the heading in the same section or article, looking through plain div wrappers but never past the next heading or into another section. It passes when it begins with the same topic followed by is/are/was/were (or a dash or a supported linking word in Ukrainian) and more text. A missing paragraph, or one that opens differently, is reported.
A list, table, code block, image, or hidden or unclear content in that place, a heading or paragraph in another language, and other question forms such as “How …?” or “Why …?” leave the heading not checked. Identical headings on one page cannot be told apart and stay not checked, and more than 64 question headings make the inventory incomplete. Supported cases already read may still be reported, but that incomplete inventory cannot prove a fix.
Example & evidence
Illustrative example — schematic HTML, not a live audit.
<h2>What is sourdough?</h2>
<p>Great question! Let's dive in.</p>The paragraph does not open with the topic and an answer, so the heading is reported.
<h2>What is sourdough?</h2>
<p>Sourdough is bread leavened with a starter of wild yeast and bacteria.</p>A possible correction: open the section with the topic and the answer.
Confirm & check again
Check for yourself: read the first sentence under each question heading: it should name the topic and answer the question.
Check again: Full audit — run a new full audit of the site. A reported heading closes only when the same heading is found again and its first paragraph is checked and opens with the answer pattern. Removing or renaming the heading, or fixing a different question, does not close it, and a page that cannot be read completely does not prove a fix. All unresolved headings are retained through subsequent reports; if their stored union exceeds 256 keys, incomplete coverage prevents automatic closure.
Limits & sources
It checks one opening pattern, in English and Ukrainian only. It does not judge whether the answer is correct, complete or useful, and it does not promise search or AI citation.
Confidence: Medium This is a static wording heuristic with a high chance of false positives; dismiss it where the pattern does not suit the content.
Sources
- arXiv, GEO: Generative Engine Optimization — reports benchmark experiments in which content edits changed a source's visibility in generative-engine answers; it is research, not a search-engine policy or a guaranteed uplift. Checked 7 October 2026.
- IANA, Language Subtag Registry — lists the registered language subtags, such as en and uk, against which a page's declared language is validated. Checked 3 October 2026.
- IANA, Language Tag Extensions Registry — lists the registered extensions that may appear in a declared language tag. Checked 3 October 2026.
Editorial review: 2 November 2026