Creating a Good Blog Template

I write a lot of blog posts, between this site, work, and the companion posts I do for podcast episodes, and the single thing that keeps me from staring at a blank page is having a structure I trust. Not a rigid template I fill in like a form, but a shape I know works, so I can spend my energy on what I am actually saying instead of on how to arrange it. Let me walk through how I think about that shape.

Before I get to the writing, though, my actual template makes me deal with a bunch of decisions that have nothing to do with prose, and putting them first is the whole point. The top of my template is a metadata block I fill in before I write a word: the meta title capped at sixty characters, the H1, the focus keyword and any supporting SEO keywords, the meta description capped at about a hundred and fifty-five characters, the target persona I am writing for, the category, and the desired publish date. It looks like busywork. It is not. Forcing myself to name the focus keyword and the persona up front is what keeps the post from drifting, because now I know exactly who I am talking to and what one search this thing should answer. If I cannot fill in those fields cleanly, that is a sign the post does not actually have a point yet, and better to find that out before I have written eight hundred words.

The second block in my template is distribution, and it also comes before the writing. I draft the social copy right there in the same document, a version for email, one for LinkedIn, one for Twitter, plus a slot for the image. Writing the social hooks early does something sneaky and useful: if I cannot write a compelling one-line hook for the post, the post itself probably does not have a compelling hook either. The social copy is a canary. It tells me whether there is a there there before I have sunk an afternoon into the body.

Only after all of that does the template get to the part everyone thinks of as writing, the blog content itself. And that content has three parts that matter: the hook, the body, and the close. That is not a profound insight, but the difference between a post that lands and a post that meanders is almost always in how deliberately those three parts are doing their jobs.

The hook is the first two or three sentences, and it does one job: earn the next paragraph. That is the entire measure of a hook. Not to summarize the post, not to state the topic in a headline voice, just to make the reader want to keep going. The way I do this, almost every time, is by opening with a specific moment or a small true story instead of a general statement. Not “roadmaps are often misunderstood” but “the first time I watched a sales rep read a roadmap slide as a list of guaranteed dates, I understood why product managers get twitchy.” A specific scene pulls a reader in because it feels like something happened, and they want to know what. A general statement pushes them away because it feels like a lecture starting up. When I am stuck on a hook, I stop trying to be clever and just ask myself what actually happened that made me want to write this. The answer to that is usually the hook.

The body is where the real work lives, and the mistake people make is treating it as one undifferentiated blob of everything they know. The body needs its own internal structure or it turns into a ramble. The way I keep it honest is to figure out the two or three points I am actually making before I write, and then give each one room to breathe in its own stretch of paragraphs. Each point gets set up, explained, and grounded in a concrete example before I move to the next. The examples are not decoration. They are the load-bearing walls. A point stated abstractly slides right off the reader. The same point attached to a real number, a real tool, or a real thing that happened sticks. Whenever I catch myself writing three abstract sentences in a row, that is my signal that I owe the reader an example.

I also try to write the body so it flows as prose, not as a wall of headers and bullet points. Bullets have their place, a list of steps or tools, but when I see a post that is mostly bullets, it usually means the writer did not do the work of connecting the ideas. Prose forces you to show how one thought leads to the next. That connective tissue is where the thinking actually shows.

The close is the part most people fumble, usually by just stopping, or worse, by tacking on a summary that repeats what they already said. A close should not recap. It should land. The best closes take the reader up one level, from the specific thing you were explaining to the one idea you want them to carry out the door. For a post about roadmaps, that is “read them as intentions, not calendars.” One clean sentence that makes the whole thing worth remembering. I often write the close as a single short paragraph with a bit of a turn in it, something that feels like a period at the end of a thought rather than a door quietly clicking shut.

The last thing I will say is about length, because the template does not dictate it. If I have made my point in four hundred words, I stop. Padding a post to hit some imagined word count is the fastest way to bore a reader who was with you right up until you started stalling. A tight post that respects the reader’s time beats a bloated one every single time. Say the thing, ground it, land it, and get out.