# Structuring Pages for Retrieval

> AEO Content Masterclass, Lesson 2: structure pages for retrieval with question H2s, self contained sections, tables, lists and summaries.

Source: https://mentionx.ai/learn/courses/aeo-content/structuring-pages-for-retrieval  
Author: Dipuck Jones, founder of MentionX  
Updated: 31 October 2026  
Level: Beginner

**To structure a page for retrieval, organise it as a set of clearly labelled, self contained sections, each answering one question, with tables for comparisons, numbered lists for steps and a short summary.** AI engines retrieve and quote passages, so a page built from clean, standalone answers gives them more to use, and makes it far easier for readers to scan.

**In this lesson**

- How retrieval sees a page
- Question H2s and self contained sections
- When to use tables, lists and summaries
- Technical basics that keep structure visible
- Exercise and quiz

> **Key takeaways**
>
> - Retrieval systems pull passages, so pages work best when each section answers one question on its own.
> - Use question style H2s, an answer first opening sentence, and tables or lists for comparisons and steps.
> - Google says there's no chunking requirement for its AI features: structure pages for readers, not to suit a machine.
> - Keep the main content in plain HTML, and write as long as the question needs, not to a word count.

*Checked on 31 October 2026. "Our view" marks MentionX opinion. Ledgerline is a fictional company used for illustration.*

## How does retrieval "see" a page?

Retrieval augmented systems find relevant passages from documents and pass them to a model that writes the answer ([Lewis et al.](https://arxiv.org/abs/2005.11401)). In practice, a page is split into pieces, and the pieces most relevant to a question are used. If a section only makes sense after reading three earlier sections, it's weaker as a standalone passage.

Google's guidance on AI features doesn't require special formatting. It says the same SEO best practices apply ([Google](https://developers.google.com/search/docs/appearance/ai-features)). Good structure is simply what makes content easy for both people and systems to understand.

## Why use question style H2s?

People ask AI assistants questions, often long and specific ones. A question H2 such as "How much does a sitemap cost to maintain?" does three things:

1. It tells readers exactly what the section answers.
2. It matches the way the question is likely to be asked.
3. It forces the writer to answer, not wander.

Not every heading has to be a question. Labels like "Checklist" or "Sources" are fine.

## What makes a section self contained?

| Do | Don't |
|---|---|
| Name the subject: "IndexNow submits URLs…" | Start with "It also…" |
| Answer in the first 1 to 2 sentences | Hold the answer for the end |
| Include the key qualifier in the section | Rely on a caveat stated earlier |
| Link to related sections | Repeat whole sections |

A useful test: copy one section into an empty document. If a stranger can understand it, it's self contained.

## When should you use tables, lists and summaries?

| Format | Use it for | Example |
|---|---|---|
| Table | Comparing options on the same criteria | Plans by price and features |
| Numbered list | Steps in order | Setup instructions |
| Bulleted list | Unordered items | Requirements |
| Checklist | Actions to verify | Prelaunch checks |
| Summary / key takeaways | The page in brief | 3 to 5 bullets near the top or end |

Keep tables simple: clear column headers, one fact per cell, and no merged cells that make the meaning ambiguous.

## Which technical basics keep the structure visible?

- **Use real HTML headings** (`<h2>`, `<h3>`) in order, not styled `<div>` text.
- **Render key content in HTML.** Content that only appears after JavaScript runs may be missed by some crawlers. Google can render JavaScript ([Google](https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics)), but not every AI crawler documents that it does.
- **Avoid hiding answers in images or tabs** that aren't in the page HTML.
- **Keep one topic per page** so sections don't compete with each other.

## How long should a page be?

As long as it takes to answer the main question and the important follow ups, and no longer. Google's helpful content guidance warns against writing to a particular word count because you've heard search engines prefer it ([Google](https://developers.google.com/search/docs/fundamentals/creating-helpful-content)). A focused 700 word page with clear sections usually beats a padded 3,000 word one. If a section grows large enough to answer a distinct question on its own, consider giving it its own page and linking to it.

## From MentionX data: which kinds of pages get cited

**Method.** Read only aggregate queries over MentionX scans from 22 August to 29 October 2026 (UTC): 2,217 engine runs (2,154 completed) across 18 anonymised projects and six engines.

Structure matters most on the page types engines actually cite. Across 9,750 citations in our sample, articles and homepages made up the largest shares:

| Cited URL type | Share of 9,750 citations |
| --- | --- |
| Blog or article | 19.6% |
| Homepage | 10.0% |
| Review page | 2.7% |
| Docs | 2.6% |
| Pricing | 1.9% |
| Wikipedia | 1.6% |

Pricing, docs and review pages each made up a small share, but they often answer the buyer's most specific questions. Well structured blog and article pages are the most common way into a cited answer; well structured pricing and docs pages make sure the details quoted are right.

*Our view:* apply the structure in this lesson to your best articles first, then to pricing and docs, where a wrong quote costs most.

**Limits.** A convenience sample of mostly B2B software projects, run through engine APIs, which can behave differently from the consumer apps. Perplexity, Copilot and DeepSeek figures come from a single day (26 October 2026), so treat them as a snapshot, not a trend.

## Worked example: restructuring Ledgerline's pricing page

*Ledgerline is a fictional accounts payable tool. Figures are illustrative.*

Ledgerline's pricing page lists three plans in paragraphs of marketing copy. Buyers ask AI assistants "How much does Ledgerline cost for 20 users?" and get vague or outdated answers.

The team restructures it. The page now opens with one sentence summarising the plans and starting price. A table compares plans by price per user, invoice volume and integrations. Question style H2s follow: "Is there a free trial?", "What happens if we go over our invoice limit?", "Can we switch plans?", each answered in the first sentence. All content is in the HTML, with no tabs that hide prices until clicked.

Within a few weeks, two engines quote the starting price correctly and cite the page directly.

> **Pro move:** Read each section with the rest of the page hidden. If it doesn't make sense alone, add the missing subject or context in its first sentence.

## Does Google require you to chunk content?

No. Google's guide to its generative AI features lists splitting content into small chunks among the things you don't need to do, alongside creating llms.txt files or rewriting content in a special style ([Google](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide)). Its systems can work with ordinary, well organised pages.

That's a useful balance to this lesson. The structure we recommend, clear headings, answer first sections and tables, is good writing for people first. It also happens to make passages easier to retrieve and quote. Don't cut pages into fragments, repeat context in every paragraph or add headings for their own sake. If a change makes the page worse for a human reader, it's the wrong change.

*Our view:* think of structure as making your answer easy to find, for a person skimming or a system retrieving. Both benefit from the same things.

## How do you restructure an existing page?

Work in four steps:

1. List the questions the page should answer, using sales calls, support tickets and search data.
2. Turn the most important into H2s, in the order a buyer would ask them.
3. Rewrite the first sentence under each H2 so it answers the question directly.
4. Move comparisons into tables and steps into numbered lists.

Keep the URL, and keep any content that still earns links or traffic. Restructuring usually improves a page without needing a new one.

## How do you check structure is visible to crawlers?

View the page with JavaScript disabled, or use the URL Inspection tool in Search Console to see the rendered HTML. Check that headings, tables and key facts are present. Content loaded only after a click, inside an image or behind a login won't be used reliably by any engine.

## How do headings help readers and engines differently?

For readers, headings make a page scannable: they find their question and jump to it. For retrieval, a heading gives a passage context, telling the system what the following text is about. A heading phrased as a real question helps both, as long as it matches how people ask. Avoid clever or vague headings such as "The bottom line" when "How much does it cost?" would do.

## When is a single long page better than several short ones?

Keep related questions together when buyers usually ask them together, such as pricing, plan limits and billing. Split topics when they serve different readers or intents, such as a pricing page and a technical integration guide. If one section grows long enough to answer a distinct question on its own, give it its own page and link to it.

## How do you keep structure from going stale?

Pages drift. New features get added as extra paragraphs, prices change in one place but not another, and headings stop matching what buyers ask. Review your most important pages each quarter: check that every H2 still reflects a real question, that the first sentence under each still answers it and that tables match current facts. Fix the structure at the same time as the content, rather than adding new sections to the bottom.

Keep a short style guide for structure, covering heading style, when to use tables and how to open a section, so that every writer on the team produces pages that follow the same pattern. Consistency helps readers find answers quickly, and it makes reviews faster because everyone knows what a finished page should look like before it goes live.

## Common questions

**Should every H2 be a question?** Not every one, but question style headings work well where buyers ask questions.

**Do tables help AI answers?** They make comparisons clear and easy to quote; keep them in HTML, not images.

**Does structured data replace good structure?** No. Google says structured data isn't required for its AI features; clear visible structure matters more.

## Page structure checklist

- Answer first opening
- H2s phrased as the questions readers ask
- Each section answers in its first 1 to 2 sentences
- Sections make sense on their own
- Comparisons in tables; steps in numbered lists
- A short summary or key takeaways
- Real HTML headings; key content visible without JavaScript
- Sources linked where claims are made

## Exercise

**Restructure one page: question H2s, a table, a summary.**

1. Pick a page with long paragraphs and few headings.
2. List the 5 to 8 questions it answers, or should answer.
3. Turn each into an H2 and move the relevant content under it.
4. Open each section with a direct answer.
5. Convert one comparison into a table.
6. Add a three bullet summary near the top.

## Quiz

1. **Why should sections be self contained?**
   a) Retrieval systems often use individual passages b) It makes the page longer c) It's required by HTML
   *Answer: a*
2. **Which format suits comparing plans on the same criteria?**
   a) A paragraph b) A table c) An image
   *Answer: b*
3. **What does Google say about special formatting for AI features?**
   a) It requires a special schema b) The same SEO best practices apply c) Tables are mandatory
   *Answer: b*
4. **Which opening makes a section weaker as a standalone passage?**
   a) "IndexNow submits URLs to search engines…" b) "It also does this…" c) "A sitemap lists URLs…"
   *Answer: b*
5. **Why render key content in HTML?**
   a) Some crawlers may not run JavaScript b) It's faster to write c) Images are banned
   *Answer: a*

**Next:** [Lesson 3: Comparison and best of pages](https://mentionx.ai/learn/courses/aeo-content/comparison-and-best-of-pages)

## Sources

- Google, [AI features and your website](https://developers.google.com/search/docs/appearance/ai-features)
- Google, [JavaScript SEO basics](https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics)
- Google, [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content)
- Lewis et al., [Retrieval-Augmented Generation for Knowledge-Intensive NLP Tasks](https://arxiv.org/abs/2005.11401)
- Google Search Central, [Optimizing your website for generative AI features on Google Search](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide), accessed 31 Oct 2026

## Frequently asked questions

### Why use question style H2s?

They mirror how people ask AI assistants questions, and they make each section a clear answer to one specific question.

### How long should a section be?

Long enough to answer one question fully. Many good sections run 100 to 300 words, but there's no fixed rule.

### Do tables help AI answers?

Tables make comparisons explicit and easy to extract. No engine publishes a rule that it prefers tables, so use them where they help readers.

---

Written and reviewed by Dipuck Jones for MentionX Academy. The HTML version of this page: https://mentionx.ai/learn/courses/aeo-content/structuring-pages-for-retrieval
