Use a table when each item has three or more related attributes. Use a list when each item has one. Give the table a heading that names the comparison, introduce it with a full sentence, label every column with units, and mark up header cells with <th>. These rules come from Google's style guide and W3C's accessibility guidance, and they make a comparison easier to read, parse and reuse. They do not guarantee a snippet or a rich result.
When a table beats prose, and when it does not
Google's developer style guide says tables suit data with three or more related pieces of information per item, and lists suit simpler structures [1]. It also says to use a table only for two-dimensional data that makes sense in rows and columns, not for long one-dimensional lists or code snippets [1].
| Content shape | Best format | Why |
|---|---|---|
| One attribute per item (steps, names, requirements) | List | One dimension. A table adds columns with nothing in them. |
| Three or more attributes per item (plans, tools, specs) | Table | Rows and columns carry the comparison. |
| Reasoning, trade-offs, exceptions | Prose | Needs "because" and "unless", which cells handle badly. |
| Code or commands | Code block | Not tabular data [1]. |
A practical test: if you can state the comparison as "for each X, here are A, B and C," it is a table. If you find yourself writing "X is A, and also B, and also C" in three paragraphs, it was a table all along.
Keep prose around the table for the judgment calls. The table says what differs; the paragraph says which difference matters.
Build the table
Put it under a heading that names the comparison
A heading like "Pricing" is vague. "Pricing by plan: seats, storage and support" says what is being compared. Put one table under that heading and introduce it with a complete sentence, which Google's style guide recommends [1]. For how headings and hierarchy work more broadly, see H1, H2, H3: how heading structure affects SEO.
## Plan comparison: seats, storage and support
The table below compares the three plans on seat limit, storage and support response time.
Write a real header row, with units in the headers
Google's guide asks for clear, concise column headings [1]. Put the unit in the header so the cells stay clean and every value is unambiguous.
Before:
| Plan | Users | Space | Support |
|---|---|---|---|
| Starter | up to 5 users | 10 gigabytes | within a day |
| Team | 25 | 100 GB | 4 hrs |
After (example values):
| Plan | Seats (max) | Storage (GB) | Support response (hours) |
|---|---|---|---|
| Starter | 5 | 10 | 24 |
| Team | 25 | 100 | 4 |
What changed:
- Each unit appears once, in the header, instead of in every cell.
- Every cell in a column uses the same unit and format.
- Header text is short and says what the column measures.
Also:
- Put the item name in the first column so each row reads as one record.
- Fill every cell. If a value does not apply, write "None" or "Not included" rather than leaving it blank or using a dash with no meaning.
- Keep a column's values the same type: all numbers, or all short phrases.
- Do not merge cells in a simple comparison. Merged cells make the structure harder to read for people using assistive technology and harder to parse.
Mark it up as a data table
W3C's tables tutorial says accessible data tables need markup that identifies header cells and data cells and defines the relationship between them [2]. Header cells need <th> and data cells need <td> [2].
<h2>Plan comparison: seats, storage and support</h2>
<p>The table below compares the three plans on seat limit, storage and support response time.</p>
<table>
<caption>Plan limits and support response time</caption>
<thead>
<tr>
<th scope="col">Plan</th>
<th scope="col">Seats (max)</th>
<th scope="col">Storage (GB)</th>
<th scope="col">Support response (hours)</th>
</tr>
</thead>
<tbody>
<tr>
<th scope="row">Starter</th>
<td>5</td>
<td>10</td>
<td>24</td>
</tr>
<tr>
<th scope="row">Team</th>
<td>25</td>
<td>100</td>
<td>4</td>
</tr>
</tbody>
</table>
The row label ("Starter") is a <th scope="row">, not a <td>. The <caption> is optional but gives the table its own accessible name.
For more complex tables, W3C says explicit associations with scope, id and headers may be needed [2]. In practice that means a table with multi-level headers, where a data cell sits under two header cells.
<th id="q1" scope="col">Q1</th>
<th id="eu" scope="row">EU</th>
<td headers="q1 eu">1,200</td>
If you can split a complex table into two simple ones, do that first.
Avoid building tables from <div> elements, images of tables or screenshots. A visible, real HTML table is the content. It does not need schema markup to be a table.
Lists: use them for one dimension
Lists fit steps, requirements and short enumerations with one attribute each [1]. A few habits keep them clean:
- Use a numbered list only when order matters.
- Start each item the same way (all verbs, or all nouns).
- Keep items to one idea each, short enough to scan.
- Put a lead-in sentence above the list that says what the list contains.
- Do not turn a long list into a table just to look structured. Google's guide advises against tables for long one-dimensional lists [1].
For list content that is really a procedure, see HowTo schema deprecated: what still works for step content.
Lists for featured snippets: what is known
Google says featured snippets appear when its systems judge that people want an answer found in a short piece of a page, and that the snippet is chosen automatically from page content [3]. A clear list or table is a reasonable way to present that kind of content. Formatting is not a switch, though. Google's structured data guidelines say that even correctly marked-up pages are not guaranteed a rich result [4], and the same caution fits snippets.
If you want out of featured snippets, Google documents two routes: nosnippet to block all snippets, or a setting that blocks featured snippets only [3].
Structured data is a separate layer
Most Search structured data uses schema.org vocabulary, but Google says its Search Central documentation is the definitive source for Google Search behavior [6]. Google also said in a June 12, 2025 blog post that it is phasing out support for some structured data features in Search over the coming weeks and months [5]. So do not plan a comparison page around a markup feature. Make the visible table correct first, and treat markup as an addition. For the types that remain relevant, see Schema.org markup for AI search.
One rule from Google's guidelines applies here: a structured data issue can lead to a manual action that removes eligibility for rich result appearance, though it does not affect web-search ranking [4]. Markup that describes content not visible on the page is the kind of mismatch to avoid.
Pair the table with a quotable lead
A table shows differences, but it does not define what is being compared. Open the section with a one-sentence definition or summary, then the table. The pattern is covered in How to write a quotable definition for the top of a page.
Checklist before publishing
- The table sits under a heading that names the comparison.
- A complete sentence introduces it [1].
- The first row is a header row using
<th>; data cells use<td>[2]. - Units are in the headers, not repeated in cells.
- No empty cells, no merged cells in simple tables.
- Every column holds one kind of value.
- Complex tables use
scope, oridandheaders[2]. - Single-attribute content is a list, not a table [1].
- The table is real HTML, not an image.
What to do next
Pick one page where you compare things in paragraphs, such as plans, tools or specs. Count the attributes per item. If there are three or more, rebuild it as a table under a heading that names the comparison. Check the markup in browser dev tools to confirm the header cells are <th>, then tab through the page with a screen reader or keyboard to see how it reads.