Blog post structure and on-page SEO
A blog post's structure puts the answer where readers, Google and AI assistants look first: the title, the headings and the first sentence under each heading. Many of them read only those, so each one has to carry the point on its own.
Title, meta description and H1
- Title tag: the keyphrase first, at most 60 characters, the brand after a pipe where it fits ("[Post title] | Brand"), and a price or a time in minutes where it is real.
- Once a title ranks, change it only to update a figure it states.
- Meta description: 140 to 150 characters, keyphrase first. Sentence one carries the keyphrase plus a concrete price or time. Sentence two names the brand plus one detail only you have (chapter 6), with a figure first where one fits. Never "fast", "24/7", dashes, hedges, ranges or an inflected brand name. It reads as keyword, benefit, action: write it like an ad that earns the click, because the matching words show in bold in the results.
- Keep a list of every page's title and meta description, so no two pages share one.
- Exactly one H1, keyword-led, at most two lines at 375 px wide: 45 characters, never over 60.
Headings and openings
- Keep a clean H2 and H3 hierarchy with no skipped levels, with H4s where a section needs them. Every heading has text under it. Section H2s carry the topic words.
- Headings ask the reader's question (guides, FAQs) or state a claim (essays, product and service pages). Read only the headings and you should get the summary. Never "Our approach" or "Benefits".
- Answer each heading in its first sentence. Google and AI assistants pull that sentence as the snippet.
- The first sentence answers the main point. The lead under the H1 says what the topic is and what it means for the reader in 1 or 2 sentences, at most 240 characters. A quick-answer box that sums up the answer follows the first sentence, and a direct answer block whose H2 is the searcher's question follows the intro.
- Win featured snippets with the right element. For a definition, a question, a comparison or a set of steps, give a short standalone answer in the format that fits (a short paragraph, numbered steps, a list or a table) before expanding. Lists, tables and accordions also keep readers on the page longer.
- Disclaimers go once, at the end of the section, so fine print never interrupts.
Paragraphs and rhythm
- One idea per paragraph, 2 to 4 sentences. A one-sentence paragraph marks the turn.
- Mostly 15 to 25-word sentences, with short ones that land the point. No run of three sentences of the same length.
- Lists only for parallel items: 3 to 7 of them, in parallel grammar, one line each where possible. Argue in prose.
- End each section by setting up the next with a signpost ("The good news:", "Why 10?").
Sections a job or purchase topic needs
When the post's topic is a job someone pays for, or a product someone buys, these sections are required. A purely informational post uses them where they help.
- A cost breakdown and a cost per unit, in a real table. The price heading states the rule, never "The price depends on…". A "what affects the price" list follows the table.
- A buyer guide ("How to choose …") with three H3s, where the topic involves a product choice.
- A proven how-to pattern: "when it's needed" with 3 measurable triggers; a "why" box with the mechanism; "how it's done" in 3 steps naming the tools, materials and tests; the local or use-case angle; then price and time matching the parent page exactly.
The job sections change with the business.
- For a local service business: add "How long does it take", with the real time breakdown for that job, plus the response time.
- For an online store: swap the job sections for the buyer's: a comparison table of the products or types, which one suits which use, sizing or fit, care and lifespan, and the cost per use where it helps (chapter 14).
- For a software or B2B company: swap them for setup time, the steps to the first result, what it costs per seat or per month, and what it replaces.
FAQ
- Write each answer to a template. The question goes in the customer's words, as typed into Google or asked of an assistant. Sentence 1 answers it: yes, no, a number or a time. Sentence 2 gives the deciding factor or the mechanism. An optional sentence 3 says what to do or links on. 30 to 80 words. Never open with "It depends" or "Yes, if…".
- Counts: 8 questions on a product or service page and 4 on posts and other pages. Real objections beat softballs.
- Answers stay in the HTML even when collapsed.
- Write "Frequently asked questions" in full as the heading; don't abbreviate it.
Length
Word counts are targets, not quotas. Length reflects the complexity of the topic: stop when the reader has what they need. Every post has a floor of 700 words, raised to match the competition and the specificity of the query.
| Page type | Minimum words |
|---|---|
| Any blog post | 700 |
| Listicle, list post or long guide | 1,500 |
| Home page | 800 |
| Product or service page | 600 |
| Case study | 500 |

URLs and slugs
- Evergreen slugs only: descriptive topic words. Never dates, years, months, seasons, campaign names, versions, prices, counts or staff names, even when the title carries a figure.
- Lower case, hyphens, local letters transliterated (õ and ö to o, ä to a, ü to u, š to s, ž to z), one trailing-slash policy per site, and a hierarchy that mirrors the site.
- Each language gets its own natural slug under its own blog path.
- Posts sit directly under the blog folder (/blog/post-title, with the folder named in the site's language). Categories are pages of their own and never part of the post URL, so a post can change category without changing its address. No duplicate page structures.
- A statistics page names the topic and the year in its title, never in its URL. The title year changes each January.
- Never change an established URL. A page that must move gets a single server-side 301 redirect to the closest relevant live page (the same topic first, then the parent, the homepage last), with the query string kept, forever. A deleted page throws away every backlink it ever earned. With no relevant page, return 410, never a soft 404 or a blanket redirect to the homepage. Update internal links, the sitemap, the canonical, the structured-data URL and menus at the same time.
Layout
- Article body text at 18 px on 30 px line height on desktop and 17 px on 28 px on phones, with a measure of 62 to 70 characters (680 px) in the reading column.
- Figures go in tables inside the articles.
- Visible breadcrumbs on inner pages, matching the URL path, marked up as navigation with the current page flagged.
- Tabular data goes in real HTML tables with header cells scoped to their rows or columns.
- Every internal link has a descriptive anchor. Never "here", "read more" or "click here".
- All content is visible without JavaScript. Reveal animations run only when scripts run.
The article page
Every post carries these elements, in this order:
- A reading progress bar across the top that shows how far through the article the reader is.
- Breadcrumbs, then the H1.
- The author row: the author's photo, name and job title, the published date, the updated date, the read time in minutes (the word count divided by 200, rounded up) and the category.
- The opening: the first sentence answers the main point, the quick-answer box follows it, then the rest of the intro.
- The linked table of contents, with jump links to every H2: sticky in a left column on desktop, placed after the intro and the quick-answer box on phones. Google indexes jump links and can show them as links to sections in the results.
- The body, with original images and infographics, tables, lists and accordions where they help, and a companion video where one exists.
- The closing block and one call to action (chapter 1).
- "Edited by" and "fact-checked by": each with name, job title and photo.
- "Post by": the author's photo, name and title again, with a paragraph of background on who wrote the post.
- Related posts: links to more posts on the same topic.
- A social sharing image in the page head: the post's own 1200 × 630 image with its title on it, so a shared link always shows a preview (chapters 7 and 8).
- Every post has one category and a few tags. Categories are browsable pages of their own; tags group posts across categories.
- A companion video helps a post rank on both Google and YouTube. Pair a post with one where it adds something, embedded as a lightweight facade (chapter 8).
- Check that your blog engine renders every part before the first post ships: H3s, tables, images, inline links, an FAQ block, the closing call-to-action block, breadcrumbs, the table of contents, the progress bar, the author row with photo, the read time, categories and tags, the quick-answer box, the "edited by", "fact-checked by" and "Post by" blocks, related posts, and BreadcrumbList and FAQPage structured data, in every language you publish in.

The blog index
- Readers browse by topic, not by scrolling. Model the index on Shopify's blog: it leads with topics and categories, each with its own page, and lists posts under them. Go one step further and list the categories and topics themselves too.
- Never a wall of identical cards. A blog that shows hundreds of identical cards on one page fails, because a human can't naturally find what they're looking for.
- Each category page opens with a short introduction and lists its strongest posts first.
- The index stays "noindex, follow" until it has posts (chapter 8).
Dates
- Show a published date and an updated date, and change the updated date only when the content really changes. The refresh in chapter 13 is a real change.
- Write dates in prose in the language's natural long form ("14 March 2024"). Use numeric dates only where a template can't supply the right grammatical form.
Edited by Andres LepikCo-founder & Head of Growth
Fact-checked by Siim SaarHead of SEO
Post by Rasmus Kivi
Co-founder & CEO
Co-founded REND and still reads every client's monthly report himself before it goes out.