Headings, lists and tables: structure machines can parse
Use real headings that name what each section answers, lists for steps and options, and simple tables for facts that compare, such as hours by location or plans accepted at each office. Structure helps patients skim and helps screen readers and crawlers understand the page. Google says its systems understand multiple topics on a page without special chunking, so structure for the reader, not for a bot.
Why structure matters
A patient on a phone does not read a practice page top to bottom. They scan headings, look for the one that matches their question, and read that section. A page that is one long block of text forces them to read everything to find anything.
Structure also matters to people using assistive technology. The W3C's accessibility tutorials note that browsers, plug ins and assistive technologies can use headings to provide in page navigation, which lets a screen reader user jump straight to the section they need. The CDC's plain language guidance recommends headings, lists and tables for the same reason: they make information easy to find.
Machines benefit for related reasons. Google says people generally appreciate pages organized by paragraphs and sections with headings, and clear structure makes it obvious which text answers which question.
Headings that work
A good heading tells the reader what the section answers. "Recovery" is fine; "How long recovery takes after hip replacement" is better, because it still makes sense when read alone or in a list of headings.
A few rules:
- Use one main heading for the page, describing the whole page.
- Nest the rest in order: sections under the main heading, subsections under sections. The W3C advises that skipping heading ranks can be confusing and should be avoided where possible.
- Use real headings, not bold text made large. Your website editor has a heading option; bold paragraphs look like headings to a sighted reader but not to a screen reader or a crawler.
- Write headings in the patient's words, with the clinical term where helpful.
Google's SEO Starter Guide notes that, from a Google Search perspective, heading order does not matter. It matters for accessibility, which is reason enough to get it right.
Does ChatGPT recommend your practice?
The Surge Score measures five things about your practice website: how often ChatGPT, Gemini and Perplexity recommend you, your PageSpeed, your structured data, your indexing and your reviews, each with its evidence and date. Free.
Lists for steps and options
Lists make two kinds of content far easier to follow.
Numbered lists for sequences, where order matters: how to prepare for a colonoscopy, what happens at a first visit, how to request records.
Bulleted lists for options or items, where order does not: what to bring to an appointment, symptoms to watch for, the treatments you offer for a condition.
Keep each item short and parallel, starting the same way where possible. Avoid lists of one or two items, which read better as a sentence, and avoid nesting lists more than one level deep, which becomes hard to follow on a phone. If an item needs a paragraph of explanation, it probably deserves its own heading instead.
Tables for facts that compare
Tables are underused on practice sites and ideal for facts patients compare across two dimensions. Examples:
- Hours by location and day of the week
- Insurance plans accepted at each office
- Which providers see patients at which locations, and on which days
- Visit types, how long they take and whether they can be booked online
- Self pay prices for common services
Keep tables simple: one header row, one fact per cell, no merged cells, and a short sentence before the table saying what it shows. Build them as real tables in your website editor rather than as images, so they can be read by screen readers, crawlers and patients who zoom in on a phone. On narrow screens, check that the table scrolls or stacks sensibly rather than cutting off columns.
Structure that hides content
Some formatting choices look tidy but hide content from the people and systems trying to read it.
- Text in images. An image of your hours or a grid of insurance logos is unreadable to a screen reader unless someone wrote alt text for it, and a crawler gets at best that alt text, not a table it can use. Put the text on the page.
- PDFs for key facts. Insurance lists, new patient instructions and price lists in PDFs are harder to read on a phone and easy to let go out of date. Publish them as pages.
- Content that loads only when clicked. Tabs and accordions are fine when the text is in the page; some load their content with a script only when opened. See JavaScript sites and AI crawlers.
- Widgets for core facts. Hours, locations and providers shown only in third party widgets may not appear in the page itself.
If a patient needs a fact to decide or to arrive, it should be plain text on a page.
What Google says about structuring for AI
A popular piece of advice says to break pages into small chunks so AI systems can extract them. Google's 2026 guide to generative AI features addresses this directly: there is no requirement to break content into tiny pieces for AI to understand it, and Google's systems can understand the nuance of multiple topics on a page.
So do not restructure pages for a bot. Structure them for a patient, which means headings that match their questions, lists where content is a list, tables where facts compare, and an answer at the start of each section, as in answer first content. That structure is what accessibility guidance and plain language guidance already recommend, and it is what makes accessible forms and chat work too.
Checklist
- Each page has one main heading and section headings nested in order
- Headings are real heading elements, not large bold text
- Headings describe what each section answers and make sense alone
- Steps use numbered lists and options use bulleted lists
- Hours, locations and accepted plans appear in simple text tables or lists, not images
- Key facts are on web pages, not only in PDFs or widgets
Frequently asked
Do headings help my Google ranking?
Google does not describe headings as a ranking boost, and its SEO Starter Guide says the order of headings does not matter to Google Search. Headings help patients and screen reader users find what they need, and they make clear which text answers which question.
Should every heading be a question?
No. Question headings work well on FAQ sections and pages that answer common questions. Elsewhere, a clear descriptive heading such as "Parking and entrance" is easier to scan. Mix the two based on what the reader is looking for.
Are accordions bad for search or accessibility?
Not if the text is in the page and the accordion is built accessibly. Problems arise when content loads only after a click through a script, or when the accordion cannot be opened with a keyboard. Ask your developer to check both.
Sources
- Headings, W3C Web Accessibility Initiative
- SEO Starter Guide, Google Search Central
- Optimizing your website for generative AI features on Google Search, Google Search Central
- Plain Language Materials and Resources, Centers for Disease Control and Prevention
Book a strategy call with the team.
Twenty minutes. We'll walk through the specific opportunities in your market and what a MedPracticeGrowth engagement would look like for your practice.