The draft that's been open since spring
We run into this with customers all the time — let's call this one Dana. She runs a small bookkeeping practice for local tradespeople. Her last blog post went up in April. A half-finished draft about year-end tax tips has sat in a browser tab ever since.
Dana isn't lazy, and she isn't short on things to say. She answers client questions every single day. When a competitor shows up in search and she doesn't, she feels a pang, adds "blog post" to next week's list, and then next week happens: a client deadline, a quarterly filing, a newsletter. The blog slides down again.
What stopped her wasn't the writing. A blog post looks like one task and behaves like ten. Find a phrase people really type into a search box. Write a title that doesn't get cut off. Write the line that appears under it. Set a clean URL. Build headings. Answer follow-up questions. End with a next step. Do all of it in a voice that sounds like her and not like a template.
None of that is hard. Together it's a small project, and small projects lose to urgent work every time.
Then there's the reward problem. A social post gets a reaction the same afternoon. A blog post gets silence, because search traffic builds over weeks. Whatever gives feedback today wins.
And the gap compounds. By month four, Dana had quietly decided her next post had to make up for the missing ones. That's the trap.
The post that restarts your blog doesn't have to be great. It has to exist.
Turn ten jobs into one checklist
The way out isn't more willpower. It's fewer decisions per post. A post that can be found follows a checklist, and a checklist is something you can write once and reuse. (We walk through why blogs stall in the first place in this piece on restarting a blog that's gone quiet.)
The parts worth locking in, using the guidelines from that post:
- One target keyword, the phrase a real person would type. Use it in the title, the first paragraph and one heading, naturally. Repeating it in every paragraph reads badly and doesn't help.
- A title of about 60 characters or fewer. Longer titles get trimmed in search results, and the cut part is often the part that explained the post.
- A meta description of about 155 characters or fewer. It won't rank the post by itself, but it decides whether someone clicks.
- A short, clean slug made of the words that matter.
- Sections that stand alone, so someone landing on any heading gets an answer.
- One next step at the end, so the reader doesn't bounce back to the results page.
Once those are settled, the only real work left is the part only you can do: the example, the detail, the opinion.
Decide the structure once. Spend your energy on the substance.
Try this week
Think of the last question a customer asked you, by email, on a call or in a message. Write it down exactly as they said it. That sentence is a search phrase, a real person's words for a real problem.
Now spend 30 minutes on the skeleton: a title of 60 characters or fewer with the phrase in it, a meta description of 155 or fewer, a short slug, and three headings that each answer part of the question. Then write the first section while it's fresh.
One phrase, one post. Then repeat next week.
Or skip the routine: this is the step Zolt does for you, drafting the post in your Brand Voice with the title, meta description, slug, FAQs and call to action already in place, ready for you to read and approve.
From the Zolt blog
- Stop re-explaining your business to every AI tool — why AI drafts come back generic, and what changes when the tool already knows you.
- Blank page every Monday? You need a content system — a way to stop starting from zero each week.
- You can't trust an AI draft without reading every line — how to review a draft quickly and still stand behind it.
That's it for this week. If the draft in your tab is still open, close it and start with one customer question instead. It's a lighter place to begin.
If you'd like help making that routine easier to keep, you can Get Started.
— Your friends at Zolt
P.S. Hit reply and tell us the customer question you picked. We like reading them.