Scannable content: headings and short blocks that keep readers
Short answer Most visitors skim a page before deciding to read it. Put the answer in the first two lines, write headings as the questions customers ask, keep paragraphs to one idea, and use lists and tables for steps and prices. Google says to break long content into sections with headings, and sets no ideal number of headings.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callHow do you make a page easy to skim?
Give the skimmer what they came for without making them read everything. Seven changes do most of the work:
| Change | Why |
|---|---|
| Answer in the first two lines | Readers decide fast whether to stay |
| Headings written as customer questions | Skimmers read headings and skip the rest |
| Start each heading with the words that matter | "Price of a furnace tune-up", not "Let's talk about pricing" |
| One idea per paragraph, 1–3 sentences | On a phone, five lines of text is already a wall |
| Lists for steps, tables for prices and options | The eye finds a row faster than a sentence |
| Bold a few key facts, not whole sentences | Bold everywhere means bold nowhere |
| Plain words, link text that says where it goes | "See our drain cleaning prices", not "click here" |
The research behind this list is old and still holds. Nielsen Norman Group, a usability research firm, found in 1997 that 79% of test users scanned any new page and only 16% read word by word (Nielsen Norman Group: How users read on the web). A version of a page that was concise, scannable and plainly worded tested 124% more usable than the promotional original.
Why don't visitors read the whole page?
They are checking whether the page answers their question before they invest time. In a 2011 summary of Microsoft research that timed more than 2 billion page visits, Nielsen Norman Group reported that the average page visit lasts "a little less than a minute" and that "the first 10 seconds of the page visit are critical" (Nielsen Norman Group: How long do users stay on web pages?).
Eye-tracking shows how they skim. The best-known shape is the F-pattern: people read across the top, then a shorter line lower down, then run their eyes down the left edge (Nielsen Norman Group: F-shaped pattern). The same study calls this pattern bad for businesses, because whatever sits on the right of a dense paragraph gets missed. Good headings change the shape: readers jump from heading to heading and skip the text under the ones that don't matter to them. Nielsen Norman Group calls that the layer-cake pattern, and it's the one you want.
How should I write headings?
Write each heading as the next question a customer would ask, in their words. A roofer's page might run: "How much does a roof replacement cost?", "How long does it take?", "Do you handle the insurance claim?", "What warranty do I get?". A reader who only scans the headings should still learn what the page covers.
Nielsen Norman Group's advice is to "start headings and subheadings with the words carrying most information" (Nielsen Norman Group: F-shaped pattern), so a skimmer who reads only the first two words still gets the gist. Skip clever headings like "Raising the roof". The W3C's accessibility guidance says the same: "Use short headings to group related paragraphs and clearly describe the sections." (W3C WAI: Writing tips)
On heading tags (H1 is the page's main headline, H2 and H3 are sections under it), Google is relaxed:
"Having your headings in semantic order is fantastic for screen readers, but from Google Search perspective, it doesn't matter if you're using them out of order." (Google Search Central: SEO Starter Guide)
So keep headings in order for people using screen readers, but don't panic over a plugin warning about heading levels.
How long should paragraphs be?
One idea each, usually one to three sentences. Test it on your phone: if a paragraph fills the screen, split it. The W3C puts it simply: "Write in short, clear sentences and paragraphs." (W3C WAI: Writing tips)
Pick the format by what the content is:
| Content | Format |
|---|---|
| Steps the customer follows | Numbered list |
| Things included in a service | Bulleted list |
| Prices, packages, options | Table |
| A reason, a story, a promise | Short paragraph |
| An official rule or a review | Quote block |
Cut before you format. Nielsen Norman Group's 1997 tips include using half the words of conventional print writing, or fewer (Nielsen Norman Group: How users read on the web). Sentences like "We are passionate about delivering quality" add length a skimmer has to wade through.
What should go at the top of the page?
The answer, then the details. Writers call this the inverted pyramid: conclusion first, supporting facts after. Nielsen Norman Group recommends putting "the most important points in the first two paragraphs on the page" (Nielsen Norman Group: F-shaped pattern).
For a service page, the first screen on a phone should say what you do, where, roughly what it costs, and how to book. A long welcome, a mission statement or a slider of stock photos pushes all four out of view. For more on what that first screen needs, see landing page best practices.
Does scannable content help SEO?
Indirectly, and Google says the basics plainly. Its starter guide says: "Break up long content into paragraphs and sections, and provide headings to help users navigate your pages." It adds: "There's also no magical, ideal amount of headings a given page should have." (Google Search Central: SEO Starter Guide)
Google also says its ranking looks at how usable content is:
"When all other signals are relatively equal, content that people will find more accessible may perform better." (Google Search: How Search works, ranking results)
The same page says Google uses "aggregated and anonymized interaction data to assess whether search results are relevant to queries." Google doesn't say it uses your bounce rate. Treat formatting as a way to serve the reader, not a ranking trick: content still comes first. For the rest of what a service page needs to rank, see on-page SEO for service pages.
How do I know if the new format worked?
Compare the page's engagement before and after in Google Analytics 4 (GA4), over the same number of weeks. GA4 counts a visit as engaged if it "lasted longer than 10 seconds, or had a key event, or had 2 or more screen views" (Google Analytics Data API). Bounce rate in GA4 is simply the share of visits that were not engaged.
- Note the page's engagement rate and its calls or form fills for the last four weeks.
- Change the format only. Leave the offer, price and photos alone so you know what moved the number.
- Check the same figures after four more weeks.
To see where people stop, a heatmap or session-recording tool shows how far visitors scroll before they leave.
Engagement is a clue; booked jobs are the score. To count calls and forms as key events, see GA4 key events for a small business.
Example
Illustrative cases with invented numbers.
A house cleaner's pricing page (US dollars)
The page opens with 300 words about the owner's story, and prices sit in a paragraph near the bottom. Rewrite: first line "Standard cleaning from $140 for a 2-bedroom home, booked online", then a three-row table for standard, deep and move-out cleaning, then the story further down.
An accountant's tax services page (Canadian dollars)
Five long paragraphs cover personal returns, small business returns and bookkeeping. Rewrite: one H2 per service, phrased as the question ("What does a personal tax return cost?"), each opening with the fee from C$150 and a bulleted list of what's included.
A plumber's water heater page
The headings read "Our commitment" and "Why us". Rename them "Repair or replace your water heater?", "How much does a new water heater cost?" and "Can you install it today?". A skimmer now sees the page answers all three.
FAQ
How many headings should a page have?
Google says there is no ideal number. Add one wherever the reader's question changes, roughly every few short paragraphs.
Do skimmers ignore everything on the right side?
Often, on dense pages. The F-pattern research found people miss what sits at the end of long lines, so put key facts at the start of a line or in a heading.
Is a long page bad for skimmers?
No, if it's well organized. A long page with clear question headings scans faster than a short page written as one block.
Should I put a table of contents at the top?
On long guides, it helps readers jump to their question. On a short service page it pushes the phone number and booking button down, so skip it.
Different for you?
- Visitors land and leave without calling: website not getting leads.
- The page was written years ago and is losing traffic: update old website pages.
- The page is for a paid ad: landing page best practices.
- You want pages written and structured for you: SEO & GEO Agent.