Page Structure for Extraction
Engines read your HTML, not your design. A clean heading outline, real lists and tables, and short self-contained sections make every passage easy to find, label and lift.
Headings are labels
Use one H1 for the page topic, H2s for the main questions and H3s for sub-questions. Write headings as the question or as a clear noun phrase ("GST rate on software services"), never as clever teasers. The heading tells the engine what the passage under it answers.
Self-contained sections
Each section should make sense if it is the only thing a reader sees. Repeat the key noun instead of "it", define abbreviations the first time in that section, and avoid "as mentioned above".
HTML that machines understand
- Use
<ol>for steps and<ul>for unordered lists. - Use
<table>with a header row for comparisons. - Keep the answer text in the HTML on first load; content injected late by JavaScript or hidden in tabs is weaker.
- Add a short summary or "key points" block near the top for long guides.
Jump links and table of contents
A table of contents with anchor links helps readers and gives the engine named sections it can link to directly. Google sometimes shows these as "jump to" links in results.
<h2>How long does ERP implementation take?</h2>
<p>A custom ERP for a small manufacturer usually takes
three to six months to implement, depending on the
number of modules and the state of existing data.</p>
<ol>
<li>Process mapping: 2 to 3 weeks</li>
<li>Build of first modules: 6 to 10 weeks</li>
<li>Data migration and testing: 3 to 4 weeks</li>
<li>Training and go-live: 1 to 2 weeks</li>
</ol> Question heading, standalone answer sentence, then a real ordered list. Each part can be lifted on its own.
Pro tips
- Run the page through a text-only view; if the answer is not visible there, engines may miss it.
- Keep sections between roughly 100 and 300 words so each has one clear job.
- Name tables and figures with a caption that states what they show.
Common mistakes
- Using headings for styling ("Our Approach", "Why Us") with no informational meaning.
- Faking lists with line breaks or emoji bullets.
- Putting the main answers inside accordions that load only after a click.
Use question headings, self-contained sections and real HTML lists and tables, with the answer present on first load.