How to write a blog outline that makes drafting twice as fast

To write a blog outline, pick a working title, check the top-ranking posts for your keyword and plan to cover what they cover plus one gap, order sections by what readers need first, write H2s as searchable phrases, put 2-3 bullet talking points under each, and cut weak sections before drafting — about one H2 per 250-400 words.

Most writers who stare at a blank page aren't blocked on words. They're blocked on decisions: what goes in, what order, what's the point of this section. An outline makes all of those decisions in advance, in a form cheap enough to change. Here's the six-step process, the math for how many sections you need, and a complete example outline to copy.

Why outlining first doubles your drafting speed

Drafting without an outline means making two kinds of decisions at once. Structure decisions: what does the reader need next? Wording decisions: how do I phrase it? They're different mental jobs, and switching between them every few sentences is what makes a 1,500-word draft eat an entire afternoon.

An outline splits the work. You make every structure decision up front — 20 or 30 minutes during which moving things costs nothing, because reordering two bullets takes three seconds. Reordering two finished sections means rewriting the transitions around both, and usually a paragraph inside each. Once the map is drawn, drafting turns into a fill-in job: look at the bullet, say the thing, move on.

There's a second effect. Outlines kill mid-draft scope drift — that moment on paragraph nine where you start wondering whether the post should really be about something else. With an outline, you had that argument with yourself yesterday, and it took two minutes instead of costing 800 words.

Step 1: pick a working title

The working title's job is to fix the scope, not to be clever. "How to name a podcast" and "How to launch a podcast" are different posts that share maybe one section; deciding which one you're writing is the biggest structural choice you'll make, so make it first and make it on purpose.

Don't polish yet. Write something plain that names the topic and the reader's goal, then move on. After drafting, when you know exactly what the post delivers, come back and make the title earn clicks — a blog title generator is useful at that stage for producing variants fast, and these blog title formulas give you proven shapes to pour them into.

Step 2: check what ranks, then find the gap

Search your target keyword and open the top five results. In a scratch doc, list every H2 they use. Ten minutes of copying, and you now know two things.

First, the table stakes. Any subtopic that shows up in three or more of the ranking posts is a subtopic searchers expect. Skip it and your post reads incomplete — to readers, and to a search engine comparing your coverage against pages it already trusts.

Second, the gap. Somewhere in that pile of H2s there's a question nobody answers well: a missing worked example, a comparison everyone dances around, a step everyone compresses into one vague sentence. That gap is your reason to exist on page one. One genuine gap beats five recycled sections.

Your outline is the union of the table stakes plus your gap — their coverage, reorganized your way, with the missing piece added.

Step 3: order sections by reader priority

The default instinct is chronological, or "background first, payoff later." Resist it. Someone who searched your keyword wants the answer and the steps; the history, the theory, and the edge cases come after — if they survive step 6 at all.

A reliable order: the direct answer, then the how, then the why, then the exceptions. News writers call this the inverted pyramid, and it works for the same reason in blog posts — every reader gets the most valuable thing available at the moment they stop reading, whether that's after one section or seven.

Step 4: write H2s as searchable phrases

"Length" as a heading tells Google nothing and tells a scanning reader barely more. "How many sections does a blog post need?" does both jobs at once: it matches something people actually type, and it lets a skimmer decide in half a second whether the section is for them.

Question-shaped H2s carry one more advantage: featured snippets. When a heading matches a query and the paragraph directly beneath it answers in 40-60 words, Google can lift the pair straight into the snippet box or a People Also Ask result. Not every heading should be a question — steps read better as imperatives — but any section that answers a distinct question should be phrased as that question or a close variant of it.

Step 5: add two or three talking points per section

Under each H2, write 2-3 bullets. Fragments are fine — "pixel width, not character count" is a perfectly good bullet. Each one is a point the section must land.

The bullets double as a diagnostic. Can't come up with a second one? The section is thin; merge it into a neighbor. Need a sixth? That's two sections wearing one heading; split it. This is also the place to park the evidence you'll need — the example, the number, the screenshot idea — so you're not hunting for it mid-draft with your momentum bleeding out.

Step 6: cut sections before drafting, not after

Every outline has a weakest section — usually one you added because it felt expected. Kill it now. Deleting a bullet costs three seconds and zero ego. Deleting 400 drafted words is a negotiation with sunk cost, and the words usually win.

The test is simple: as a reader, would you actually read this section or skim past it? Skim sections get cut or merged. There's a bonus, too — the sections you cut become a ready-made list of future posts that can link back to this one.

How many sections does your post need?

Plan one H2 for every 250-400 words of target length. Under 250 words per section, the post feels choppy, headings interrupting instead of organizing. Over 400, readers get lost inside sections, and you probably need H3s or a second post.

In practice: an 800-word post carries two or three H2s. A 1,500-word post carries four to six. A 2,500-word guide carries seven to ten. If your outline shows nine H2s against a 1,200-word target, something has to give — cut sections or raise the target, but decide now, not at 11pm on draft night.

An example outline you can copy

Say the target is 1,500 words on "how to choose a domain name." That budget buys five sections at roughly 300 words each, question-shaped where a real query exists:

Working title: How to choose a domain name you won't regret

1. What makes a good domain name? — passes the radio test (spellable after hearing it once); short beats clever; skip hyphens and numbers
2. How to brainstorm domain name ideas — list 20 candidates before judging any; say each out loud; check how it reads in other languages
3. How do you check if a domain is available? — registrar search; trademark database; matching social handles
4. What if the .com is taken? — the three options ranked: tweak the name, switch the ending, buy from the owner — and when each makes sense
5. How much should a domain cost? — first-year pricing vs renewal pricing; premium domains; when paying more is rational

Notice what's already decided before a single sentence exists: the scope (choosing, not hosting), the order (criteria before process before money), and the gap (most competing posts skip the "what if it's taken" decision entirely). Drafting this post is now mostly typing.

If you want the first pass done for you, the blog outline generator builds a structure like this from a topic and a target length. Then you apply steps 2 and 6 yourself — the gap-finding and the cutting are the parts only you can do.