Writing guide
How to write a blog post
A blog post has one job that most writers never name: it must answer a question someone typed into a search box, fully enough that the reader stops searching. Rankings, subscribers and AI citations are all downstream of that single transaction. The reader arrives with a question, skims for evidence you can answer it, and gives you about ten seconds before hitting the back button.
Most business blog posts fail before the second paragraph. They open with three sentences of throat-clearing about how important the topic is, hide the answer somewhere below the fold, and pad the word count because someone once said long posts rank better. The result reads like it was written to fill a content calendar rather than to answer a person — and both readers and search engines have learned to recognize the difference.
The guide below is the process a working editor would use: pick one question, study what already ranks, structure the post around sub-questions, and put proof under every claim. Follow it and the writing gets faster, because most of the work happens before the first sentence.
What it is
A blog post is a standalone article, usually 800 to 2,000 words, published on a site’s blog to answer one specific question or make one argument for a defined reader. It is built to be found — through search, AI answers, email or social — and to be skimmed before it is read.
When to use it
Write a blog post when your audience already searches for a question you can answer with real experience, data or examples. Skip the format when the news is about you (that is an announcement), when the topic needs original research at report depth, or when a documentation page would answer the question in fewer words.
The structure that works
The answer-first opening
The first 100 words either confirm the reader is in the right place or send them back to the results page. Answering immediately is what earns the right to go deep afterwards.
- State the direct answer to the title’s question within the first two or three sentences, including a number if one exists.
- Cut every sentence that would work equally well at the top of a different post — “in today’s digital landscape” is filler by definition.
- Preview the structure in one line so a skimmer knows what the rest of the page holds.
H2 subheadings written as searcher questions
Readers scan a post by its H2s the way they scan a results page, and search engines lift question-shaped sections into featured snippets and AI answers.
- Phrase each H2 as a question a reader would actually type, or as its direct answer — “How often should you publish?” or “Publish twice a month, every month”.
- Open each section by answering its own H2 in the first sentence, then expand.
- Keep 4 to 7 H2s for a 1,500-word post; more than that usually means two posts are fighting over one URL.
Evidence under every claim
Advice without proof is interchangeable with every other post on the topic. Evidence is the one part a competitor cannot paste.
- Pair every recommendation with one proof: a number, a named example, a screenshot, or a short account of what happened when you did it.
- Prefer your own data — even a small sample — over a recycled statistic from a 2019 roundup.
- Link to primary sources, not to other blog posts citing them.
A short FAQ for the long tail
Sub-questions that don’t deserve a full section still deserve an answer, and question-plus-short-answer blocks are the exact shape snippets and AI answers quote.
- Pull 3 to 5 questions from Google’s “People also ask” box and from what customers actually ask you.
- Answer each in 40 to 60 words — direct statement first, qualifier second.
- Don’t restate questions the body already answered; the FAQ exists for what didn’t fit.
The recap and one next step
A reader at the bottom of a post is the warmest visitor a site gets. Ending with a limp summary wastes them.
- Compress the post into 3 to 5 takeaways a reader could act on this week.
- Offer exactly one next step — a related guide, a template, a signup — chosen to match why they searched.
- Skip the “in conclusion” paragraph that restates the intro; a recap is a tool, not a ritual.
Step by step
- 01
Pick the one question the post answers
Every durable post maps to one question with one intent. “Content marketing” is a topic; “how often should a small business publish blog posts” is a question. If you cannot state the question in a single sentence, you are looking at two posts — split them, because a page that half-answers two questions ranks for neither.
Check that people actually ask it. Type the question into Google and look at autocomplete, the “People also ask” box, and what kind of pages currently rank. Forum threads at the top are good news: demand exists and the current answers are weak.
- 02
Read the top five results and write down what they miss
Spend 20 minutes reading what already ranks, with a document open. For each result, note the angle, what it covers, the last update date, and the one thing it fails to answer. You are not doing this to imitate the winners — you are hunting the gap: the missing number, the untested claim, the scenario none of them address.
Write the gap down as a sentence: “None of the top five say what to do when X.” That sentence is your angle, and it is the reason a reader — or an AI answer engine — would cite you instead of the incumbent. If the exercise turns up no gap, choose a different question; an eleventh identical post moves nothing.
- 03
Outline the H2s before writing a sentence
List the sub-questions a reader must get through before the title’s question feels settled, in the order they would naturally ask them. Those are your H2s. For a 1,500-word post, 4 to 7 is the working range — each section lands at 150 to 300 words, enough to answer and prove one point.
Test the outline before drafting: read only the H2s aloud. If they form a coherent path from question to resolution, the post will hold together. If two H2s answer the same thing, merge them now — a two-minute fix in the outline is an hour’s rewrite later.
- 04
Write the body first and the opening last
Draft the sections in any order, fastest first. Momentum matters more than sequence, and the opening is the hardest part to write before you know what the post actually says.
Then write the opening as a direct answer: the response to the title’s question in two or three sentences, with a number or a firm position. A useful test — if a reader saw only your first 100 words quoted in an AI answer with your name on it, would they have gotten value? That is increasingly how first paragraphs are consumed.
- 05
Put one proof under every claim
Go through the draft and mark every sentence that tells the reader to do something. Each one needs a support beam in the same section: a number, an example with a name, a screenshot, a quote from a primary source, or a short story of what happened when you followed the advice yourself.
Where you have no proof, either do the small work to get some — test the tactic, pull a number from your own analytics, ask a customer — or cut the claim. An 1,100-word post where everything is backed beats a 2,000-word post held up by “studies show”.
- 06
Add the FAQ from real questions
Collect the questions the body did not cover: Google’s “People also ask” box, autocomplete variations, and the things prospects ask on sales calls. Choose 3 to 5.
Answer each in 40 to 60 words with the direct answer in the first sentence. These blocks do double duty — they catch long-tail searches, and they are the passage shape most often lifted into featured snippets and AI answers.
- 07
Write ten headlines and pick one
Write the headline last, once you know what the post delivers, and write at least ten variants before choosing. Vary the mechanism: a number (“Publish twice a month: the math for small teams”), a specific outcome, a named mistake, a question. The keyword should appear naturally, near the front, in the version you keep.
Hold the winner to two constraints: about 60 characters so it survives truncation in search results, and no promise the post does not keep. A curiosity gap the first paragraph fills is a technique; one the post never fills is a refund the reader takes out of your credibility.
- 08
Edit for the skimmer, then read it aloud
Skimmers are the majority, so edit for them first: paragraphs of 4 lines or fewer with one idea each, bold reserved for the sentences that carry the argument, and any list hiding inside a paragraph converted into an actual list. Then delete the first paragraph if the post still works without it — surprisingly often it does.
Finally, read the post aloud once. Every place you stumble, the reader stumbles harder. This pass catches the sentence knots and padding that silent re-reading never finds, and it typically trims 5 to 10 percent of the word count.
Before and after: what good looks like
Before
In today’s fast-paced digital world, content is more important than ever before. Every business, big or small, knows that blogging can be a great way to build an audience and drive traffic to your website. But one question many business owners find themselves asking is how often they should be posting new content. Unfortunately, there is no one-size-fits-all answer to this question, as it depends on a variety of factors. In this article, we will explore some of the key considerations to help you decide what posting frequency might be best for your unique business needs.
After
Two posts a month is enough for most small businesses — if both target questions you can realistically rank for. Consistency beats volume: a site that publishes twice a month for a year will generally outperform one that publishes daily for six weeks and goes quiet, because search engines reward accumulating, current coverage of a topic. Three factors set your number: how competitive your keywords are, how fast your site earns links, and how many hours you can protect every single month. Here is how to work out each one, and what to do when you fall behind.
The before spends 97 words saying nothing a reader can act on — every sentence would fit any post on any topic, and the actual question is deferred to “a variety of factors”. The after answers in the first sentence with a number, takes a defensible position, names the three deciding factors, and promises a structure. A searcher gets value in ten seconds and a reason to keep reading, and an AI answer engine gets a quotable claim to cite.
Mistakes that sink a blog post
| Mistake | The fix |
|---|---|
| Warming up on the page — three paragraphs of context before the answer | Write the body first, then write the opening as the direct answer. If the post still works with the first paragraph deleted, delete it. |
| Targeting a topic instead of a question | Rewrite the working title until it is a question one person would type. “Email marketing” is a category; “how many emails before a sale” is a post. |
| Advice with no proof attached | Audit every “should” in the draft. Attach a number, example or screenshot to each one, or cut the claim — unsupported advice is what AI answers skip and readers distrust. |
| A headline that promises what the post doesn’t deliver | Match the headline’s promise to the strongest section you actually wrote. Clickbait debt gets collected as pogo-sticking, and rankings follow it down. |
| Publishing into a vacuum with no internal links | Link 2 to 5 related posts from the body, and add a link from at least one older post back to the new one. Orphan pages take months longer to rank. |
| One post trying to serve two intents | Check the results page: if your phrase surfaces a mix of buying guides and tutorials, the intent is split. Pick one intent per URL and write the other separately. |
Pre-publish checklist
- The title’s question is answered, with a number or a firm position, inside the first 100 words.
- Headline is under 60 characters, contains the keyword, and promises only what the post delivers.
- Every H2 is a question a reader would ask, or a direct answer to one.
- Each section opens with its answer, then expands — no section saves its point for the end.
- Every recommendation has a proof in the same section: number, example, screenshot or source.
- No paragraph runs past 4 lines, and any hidden list is formatted as a list.
- The FAQ has 3 to 5 questions with 40-to-60-word direct answers.
- 2 to 5 internal links sit in the body, and one older post now links here.
- The meta description is hand-written, 120 to 160 characters, and states the post’s promise.
- The post was read aloud once and every stumble fixed.
- One next step closes the post, matched to why the reader searched.
Free tools for this work
Check your blog post before it ships.
Frequently asked questions
- How long should a blog post be?
- As long as the answer needs and no longer. For most how-to questions that is 1,000 to 1,800 words; a definition-style question can be settled well under 800. Check the depth of the top five results for your specific question — matching what already satisfies searchers beats hitting an arbitrary count, and padding gets punished by readers before it gets punished by rankings.
- How long does it take to write a good blog post?
- Budget 3 to 6 hours for a 1,500-word post: roughly an hour of research and outlining, two to three hours of drafting, and an hour of editing and formatting. A post finished in 45 minutes almost always reads like one. The research and outline are the hours that show up in the final quality.
- How often should I publish blog posts?
- Pick the frequency you can hold for a year — for most small teams that is 2 to 4 posts a month. A steady two per month compounds; a burst of daily posts followed by silence does not. Frequency only helps when each post targets a distinct question you can win, so cadence is capped by your supply of real answers.
- Do blog posts still matter now that AI answers questions directly?
- Yes, but the bar moved. AI answer engines cite sources, and they favor pages that answer directly, show first-hand evidence and carry clean question-shaped structure — the traits this guide builds in. What stopped working is the generic summary of other posts; what gets cited is the post with original numbers and experience in it.
Free download
The Pre-Publish Checklist
This guide covers one format. The checklist covers every article. 47 checks WriteZu runs before an article ships — as a checklist you can run by hand.
No spam. The checklist, then only what's worth knowing.
Or let WriteZu handle the writing for you
It follows this exact structure — researched, drafted, scored against quality gates, and published to your CMS — while you approve from your inbox.
Start free