Newwebs Techs logo Newwebs TechsBuilding websites, explained for beginners
Web Design

How to Design a Blog Post Layout People Actually Read

A reader wrote to me in September with a problem that sounded like an SEO problem and was not one.

Blog article open on a phone and a laptop showing a narrow text column, large body type and clear subheadings

A reader wrote to me in September with a problem that sounded like an SEO problem and was not one. She had forty posts on a gardening blog, Search Console was showing about 11,000 impressions a month, and the click numbers were respectable. What she could not understand was why none of it turned into anything. No comments, no newsletter signups, nobody clicking through to a second post. Her average engagement time in Analytics was nineteen seconds on articles that take seven minutes to read.

I opened one of them on my phone. The text ran the full width of the screen with no margin to speak of, the paragraphs were six and seven sentences long, the body type was 15 pixels, and the line height was whatever the theme shipped with. The writing itself was good. She had grown the plants she was writing about. The layout was quietly throwing away every visitor that search had sent her, and no amount of keyword work would have fixed it.

Line length is the measurement that decides the rest

If you change one thing about a blog post layout, change how wide the text column is. Typesetters have worked with a target of 45 to 75 characters per line for a very long time, and the reason is mechanical rather than aesthetic. At the end of each line your eye has to travel back and find the start of the next one. The longer the journey, the more often you land on the wrong line, lose your place, and reread. Three or four of those in a row and a reader gives up without quite knowing why.

In practice that means a body column of roughly 620 to 700 pixels on a desktop screen, no matter how wide the monitor is. If you can set it in CSS units, 65ch is a clean way to express it, because it ties the column to the actual font rather than to a guess. Full width text on a 27 inch iMac produces lines of 150 characters, which is close to unreadable, and it is the default in more free themes than I would like.

On a phone the opposite risk applies. Narrow screens give you short lines automatically, so the thing to watch is the side margin. Sixteen pixels of padding on each edge is the minimum I accept; twenty is better. Text that touches the bezel feels cramped in a way readers register as cheapness. If your theme fights you on this, our notes on mobile friendly website design cover how to test the result on a real handset in about five minutes.

The habit of breaking up text with stock images

Almost every guide to blog layout repeats the same instruction: break up long text with images every few hundred words so the page does not look like a wall. I followed that advice for years and I now think it does more harm than good on most small sites.

The trouble is what the images usually are. A photograph of a smiling stranger at a laptop, or an abstract illustration of a lightbulb, carries no information. It interrupts a reader who was following an argument, costs 80 to 200 kilobytes, and pushes the next paragraph further down the page. I have watched people scroll past decorative images with no pause at all, then stop and actually read a plain two column table. The eye is not looking for pictures. It is looking for a reason to keep going.

What genuinely breaks up text is structure: a subheading, a short paragraph after three long ones, one table, a pulled sentence in bold. Images belong in a post when they are the evidence. A screenshot of the setting you are describing, a photograph of the thing you built, a before and after. If an image could be swapped for a different image without changing the meaning of the sentence next to it, delete it and the page gets both faster and easier to read.

The question is not whether the page looks broken up. It is whether a reader who skims the headings alone comes away with the answer.

The numbers I set before writing a single post

These are the values I put into a theme before I publish anything on it. They are not sacred, but they are a reasonable starting point and they take about twenty minutes to apply.

ElementValue I useWhy that number
Body text size18px mobile, 19 to 20px desktop16px is a minimum, not a target. Readers over forty notice the difference immediately
Line height1.6 to 1.7 for bodyBelow 1.5 the lines visually merge. Above 1.8 paragraphs stop reading as blocks
Text column width65ch, around 660pxKeeps lines inside the 45 to 75 character band on any font
Paragraph spacing1 to 1.3 times the line heightEnough gap to see where a paragraph ends without a visible gutter
Space above an H2Roughly twice the space below itGroups the heading with the text it introduces instead of floating between two blocks
Body text colourNear black, about #1a1a1a on whitePure black on pure white glares on bright screens. Grey lighter than #595959 fails contrast
Paragraph lengthTwo to four sentences, variedUniform three sentence blocks read as machine output even when they are not

One value deliberately missing from that list is the font. Almost any well made typeface will work at these settings, and almost none will rescue a layout with 15 pixel type on a 140 character line. If you do want to change it, the choice matters less than the loading cost, which is the subject of our guide on choosing fonts for a website.

Subheadings are navigation, not decoration

Something like two thirds of the people who open a long article will scan the headings first and decide from those alone whether to read the body. That makes your subheadings the most read text on the page after the title, and it changes how they should be written.

A heading like "Watering" tells a scanner nothing. "How often to water a fig in a clay pot" tells them whether their question is answered here. Write subheadings as half sentences that carry the finding, not as one word labels. They should also be distinguishable at a glance: an H2 noticeably larger than an H3, and an H3 that is clearly not just a bold paragraph.

Keep the hierarchy honest. One H1, which is the post title and is usually inserted by the theme, then H2 for each main section, and H3 only where an H2 genuinely has two or more parts. Skipping from H2 to H4 because the H4 looks the right size is the most common structural mistake I find in theme files, and it makes the page harder to understand for screen readers and for automatic table of contents scripts alike.

What the layout does for search, and what it does not

I want to be careful here, because layout gets oversold as a ranking factor. Font size is not a ranking signal. Line height is not a ranking signal. What is measurable is that two of the three Core Web Vitals are layout decisions in disguise. Largest Contentful Paint is usually decided by the biggest image near the top of the post, and Cumulative Layout Shift is almost always an image or an embed with no reserved height pushing the text down after the page has already started rendering.

The indirect effect is larger than the direct one. A reader who finishes the article and opens a second one is a reader who did not return to the results page looking for a better answer. I cannot prove a clean causal line from that to rankings, and anyone who tells you they can is guessing. I can say that every site I have worked on where engagement time went from twenty seconds to over two minutes also saw its impressions climb over the following quarter, and nothing else about those sites had changed.

One change worth making this week

Open your three most visited posts on your own phone, from a cold start, and read the first screen as if you had arrived from a search result. Do not look at the code. Just notice whether you want to continue. Then set the body size to 18 pixels and the line height to 1.65, and look again. Those two values cost nothing and fix more reading problems than any other pair of numbers available to you.

After that, go through the last ten posts and delete every image that is not evidence. The pages get lighter, the text gets closer together, and nobody writes in to ask where the lightbulbs went. More layout decisions of this kind sit in our web design section.

FAQ

Should a blog post have a sidebar?

On a post page, usually not. A sidebar narrows the text column on desktop and gets pushed below the article on mobile, where almost nobody reaches it. Keep sidebars for the blog index if you want them at all, and put the author box and related posts after the article body instead.

How long should paragraphs be in a blog post?

Two to four sentences most of the time, with deliberate variation. A single sentence paragraph after three longer ones acts like a stop sign and readers slow down there. Anything past six sentences on a phone becomes a solid grey rectangle.

Does a table of contents help?

On articles over about 1,200 words with five or more sections, yes. It gives scanners a map and it sometimes earns jump links in search results. On a 600 word post it adds a block of links between the reader and the answer they came for.

Is centred body text ever acceptable?

Not for body copy. Centred text gives every line a different starting position, so the return sweep has nowhere predictable to land. Use it for a short pull quote or a single caption and nothing longer.

RM
Ravi Menon

Ravi explains how the web works and how sites get found, aimed at people building their first website.

More posts by Ravi

More in Web Design

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto