Himanshu SharmaSoftware engineer
Let’s talk

AI Search: AEO and GEO · Lesson 8 of 20

Headings, lists, tables and FAQs that answer questions

Structure a page so people and systems can scan it with logical headings, useful lists and tables, and FAQ sections that earn their space.

12 minWriting, entities and trustUpdated 14 November 2026

Awaiting technical review. This lesson is readable but not yet listed in search engines.

By the end of this lessonStructure a page with a clean heading outline, lists and tables where they help, and an FAQ section that adds real value.

Structure helps everyone

After this lesson you can take a messy page and give it a clean outline, with the right use of lists, tables and an FAQ. The reasons are mostly about humans: people scan. Automated systems benefit for similar reasons, though how much is not documented.

Google's generative AI guide (2026-05) recommends clear headings, sections and readable paragraphs, and semantic HTML where practical. That part is documented. The rest of this lesson is established practice unless marked.

Headings as an outline

Think of headings as a table of contents. A page has one h1 (the title), then h2 headings for the main sections, and h3 for parts within them. Skip nothing, and choose headings for meaning, not font size (use CSS for size).

html
<article>
  <h1>Caring for a cast iron pan</h1>
  <h2>How do I clean it?</h2>
  <p>Wash with hot water and a brush, then dry it straight away.</p>
  <h2>How do I season it?</h2>
  <h3>What oil should I use?</h3>
  <p>Any thin layer of cooking oil with a high smoke point works.</p>
  <h3>How often?</h3>
  <p>After each wash if it looks dull, otherwise a few times a year.</p>
</article>

Notice that headings are question-shaped where the content answers a question and plain noun phrases elsewhere. Do not force every heading into a question; it reads as repetitive.

Lists

Use an ordered list for steps where order matters and an unordered list for sets of equal items. Keep list items parallel: all start with a verb, or all are noun phrases. A list of three words is rarely better than a sentence.

Tables

Tables suit comparisons across the same attributes. A fictional bookshop comparing membership options:

Plan Discount Free delivery
Reader 5% Over a set order value
Collector 10% Always

(Illustrative; no real shop or prices.) Use real table, th and td elements, not a picture of a table and not layout tables. A screenshot of a table is invisible to anything that reads text and to screen reader users.

FAQ sections

An FAQ section earns its place when readers genuinely have follow-up questions the main text would clutter. Rules:

  • Use real questions from real users.
  • Each answer should lead with the answer, then add the condition.
  • Keep it short. Five good questions beat fifteen padded ones.
  • Do not repeat the main body in different words.
  • Do not stack many near-duplicate questions with the same answer.

Be aware that Google's rich result for FAQ markup no longer appears in Search (details in lesson FAQPage, HowTo and Q&A markup after the deprecations). An FAQ section remains useful for readers regardless.

Paragraphs and other signals

Short paragraphs with one idea each; descriptive link text (not "click here"); alt text on images; captions where useful. Google's guide also recommends relevant images and video. These are accessibility and readability habits first.

What is hypothesis

  • "AI systems prefer pages with at least N headings."
  • "Answers in a bulleted list are cited more than prose."
  • "Question headings raise citation rates."

They might be true for some systems on some queries. Nobody has documented them for Google, and Google's list of tactics to ignore includes chunking content into small pieces for LLMs. The honest framing: structure for readers; any extraction benefit is a bonus you cannot count on.

A quick audit method

  1. Print the outline: list every heading in order. Does it make sense alone?
  2. Check that each section's first sentence tells what the section is about.
  3. Look for content that would work better as a list or table, and the reverse.
  4. Check for headings that are just images, or text styled to look like headings.

The site's own audit script checks that each exported page has exactly one h1, a good example of automating the cheapest part of this audit.

Common mistakes

  • Using heading tags for visual styling, producing a nonsense outline.
  • Hiding an FAQ in an accordion that is not in the HTML until clicked, so the text is missing at crawl time. See Rendering, speed and clean HTML.
  • Padding with generic questions ("Why choose us?") nobody asked.
  • Making a table of one column.
  • Chopping a flowing explanation into disconnected fragments.

Exercise

  1. Extract the headings from one of your pages. Rewrite the outline so that it reads like a sensible contents page.
  2. Convert one comparison paragraph into a table, and one paragraph of steps into an ordered list. Then decide whether the result is truly clearer; revert if not.
  3. Write a five-question FAQ for a fictional tutoring service, using only questions a parent might genuinely ask.
Show a sample answer

Sensible FAQ items: "Do you offer a trial lesson?", "How are tutors checked?", "What if my child misses a session?", "Can we change tutor?", "How do we cancel?" Each answer starts with the direct answer. Placeholders for facts (fees, policies) must come from the real business, not invented.

Previous: Direct answers. Next: Original information and first-hand experience.

Key points

  • One h1, then h2 and h3 headings that form a logical outline, is established practice and helps accessibility and parsing.
  • Use lists for steps and sets, and tables for comparisons; do not force content into them.
  • An FAQ section works best for real questions that the main text does not already answer.
  • Google's guide recommends clear headings and semantic HTML where practical.
  • Whether any specific format raises AI citations is hypothesis.

Check yourself

1. Which outline is healthiest?
2. When is a table the right choice?
3. What is a good FAQ question?
4. Which claim is documented by Google rather than hypothesis?

Free tools for this lesson