What this check tests
For each page the audit crawled (the homepage plus up to nine more), it counts <ul>, <ol> and <table> elements in the whole document. A page is counted when it has at least one list or at least one table. The score is the share of counted pages, rounded:
| Result | When |
|---|---|
| Pass | 50 or more |
| Partial | 1 to 49 |
| Fail | 0 |
The message reads like "8/10 pages use lists or tables". The check does not look inside the main content. It does not tell a content list from a navigation menu, a footer link list or a cookie-banner list, and it does not look at whether a table has headers. Almost every site whose menus are built from <ul> passes, so a fail usually means the pages are built from <div> elements throughout, or they are shells with no server-rendered markup. It also cannot flag a layout table.
Why it matters to agents
Lists and tables carry structure that plain paragraphs do not. MDN describes <ul> as a list of items with no meaningful order, and <table> as tabular data in rows and columns. Software that reads the HTML can tell where one item ends and the next begins, and which cell belongs to which column header.
That is the extent of what the sources fetched support. Google's guidance on generative AI search recommends organizing pages by paragraphs and sections, with headings that give a clear structure. It does not mention lists or tables, and it says there is no requirement to split content into small pieces for AI. No source fetched says an assistant is more likely to use content that sits in a list or table. The main reasons to use the right elements are for readers and for assistive technology.
Given how easily it passes, treat a pass as a weak signal.
How to fix it
Only where content really is a list or a table:
- Mark up steps as
<ol>and unordered items as<ul>, rather than lines separated by<br>or<div>s with bullet characters. - Put comparisons, specifications and pricing grids in a
<table>, with<th>header cells,scopeattributes where the layout is complex, and a<caption>. MDN's table accessibility article covers this. - Do not use a table for page layout, and do not add lists to pad a page. This check cannot tell, but readers and screen readers can.
- If the audit reports a fail, view the source of the pages. A page with no lists at all, including a menu, is probably generated from non-semantic elements; see semantic HTML and no JavaScript dependency.
Related: heading hierarchy covers the headings that divide sections, and content length and answer-first content the text itself.