How to format a blog post: answer-first structure, H2 and H3 headings, short paragraphs, lists, tables, bold, images and alt text, plus a template to copy.

In short
to format a blog post, put the answer in the first paragraph, split the body into H2 sections phrased as questions with H3 sub-steps, keep paragraphs to 2 to 4 sentences, use lists for steps and tables for comparisons, bold a few key phrases, add images with descriptive alt text near the related text, and end with a clear next step. This format helps readers who scan, helps Google understand the page and gives AI assistants self-contained passages to quote.
Want to go further? Ask
Formatting decides whether a good article gets read. Readers rarely start at the top and read every word: Nielsen Norman Group's eye-tracking research on the F-shaped reading pattern (2017) found that people scan in an F shape when a page gives no strong cues, and recommends visible subheadings, bold key terms, bullet lists and front-loaded headings. Knowing how to format a blog post is giving readers those cues. This guide covers writing format only; for the writing process itself, see our guide on how to write a blog post.
Most effective posts follow the same skeleton, whatever the topic:
Length follows the topic, not a target: our article on how long an article should be explains how to set it from the search results.
Headings are the outline readers see. Use one H1 (the title, usually set by your CMS), H2 for main sections and H3 for steps or items inside a section. The W3C tutorial on headings explains that headings communicate the organization of the page and that skipping ranks, such as an H2 followed by an H4, should be avoided where possible, because screen reader users navigate by heading level.
Google's SEO Starter Guide notes that heading order does not matter for Google Search and that there is no ideal number of headings; a logical order is for readers and accessibility. The free heading structure analyzer shows the hierarchy of any published page, and our guide to semantic HTML explains the tags behind it.
Aim for 2 to 4 sentences per paragraph and one idea per paragraph. On a phone, a 6-line paragraph on a laptop becomes a wall of 15 lines. Start each paragraph with its main point so a reader skimming first lines still gets the argument. Vary sentence length, but keep most sentences under about 25 words, and cut the ones that only announce what comes next.
| Element | Use it for | Rule |
|---|---|---|
| Numbered list | Steps in order, rankings | One action per item, starting with a verb |
| Bullet list | Items without order: features, criteria, examples | 3 to 7 items, parallel wording |
| Table | Comparisons on several criteria, prices, specs | Header row, short cells, no merged cells |
| Blockquote | A quotation from an expert or a source | Name the person and the source |
| Bold | Key phrases: definitions, figures, conclusions | 1 to 3 per section, never full paragraphs |
| Italics | Titles of works, foreign terms, light emphasis | Rarely, harder to read on screens |
Tables are especially useful because readers, Google and AI assistants can all read a row as a fact: "Option A, $49, 20 articles". Bold works only when it is rare: if a third of the text is bold, nothing stands out.
Add an image where it explains something the text cannot: a screenshot of a setting, a chart, a before and after. Google's image SEO best practices describe alt text as the most important attribute for image metadata, advise against filling it with keywords and recommend placing images near the relevant text. A good alt text describes the image in a short phrase: "Dalmatian puppy playing fetch" rather than "puppy dog dogs puppies".
Use descriptive anchors ("our guide to keyword research" rather than "click here"), link to related posts and pages where they help, and link to sources for every figure. Our guide to blogging for SEO explains how to plan internal links across a blog.
For long posts, a table of contents at the top lets readers jump to the section they need. Each entry points to a heading through an anchor link, which also lets you share a link to one section.
Google states in its featured snippets documentation that its systems decide which page to show and that you cannot mark up a page to request one. What you control is how easy your answers are to extract:
| Element | Rule | Why |
|---|---|---|
| Title | Keyword near the start, specific promise | Click from search results |
| First paragraph | Complete answer in 2 to 4 sentences | Readers, snippets and AI quotes |
| Headings | H2 per question, H3 per step, no skipped levels | Scanning and accessibility |
| Paragraphs | 2 to 4 sentences, one idea | Mobile reading |
| Lists | Numbered for order, bullets otherwise | Fast reading of steps and items |
| Tables | For comparisons on several criteria | Clear facts, easy to quote |
| Bold | 1 to 3 key phrases per section | Cues for scanners |
| Images | Useful visuals, descriptive alt text | Understanding and image search |
| Links | Descriptive anchors, sources for figures | Navigation and trust |
| Conclusion | Key sentence in bold, one call to action | Next step for the reader |
| FAQ | 3 to 5 real questions, short answers | Extra queries, AI answers |
Before publishing, check the length with the word counter and add an estimate with the reading time calculator. The free Sorank Chrome extension then shows the SEO fixes of the published page.
A well-formatted blog post answers first, uses descriptive headings, short paragraphs, lists and tables, and makes every section readable on its own. Sorank's blog article generator applies this format to every article it writes, with sources, internal links and images, then publishes in autopilot or as drafts for review.
Two to four sentences, with one idea per paragraph, works well for most blogs because it stays readable on a phone screen. Start each paragraph with its main point. Occasional one-sentence paragraphs can emphasize a key idea, but a whole post of single sentences reads as choppy.
A table of contents is useful for long posts, roughly above 1,500 words, or for guides that readers consult section by section. Short posts do not need one. Each entry should link to a heading with an anchor, which also lets readers share a link to a specific section.
Indirectly, yes. Clear headings, short paragraphs and lists help readers find answers, and a well-structured answer under a question heading is easier for Google to show as a snippet and for AI assistants to quote. Google says heading order itself does not affect rankings, so structure for readers first.
THEY TRIED SORANK BEFORE YOU
