Ready to grow?To write a blog post that brings in customers, pick a question your buyers already ask, answer it plainly, and end with a clear way to reach you. You do not need to become a writer. You need a process you can run in one afternoon and repeat whenever you have an hour to spare.
We will follow one example the whole way through. Brightline Plumbing is a two-van local plumber. They want one post that answers "why is my water heater leaking?" because customers call about it every week. Each step below is judged on one thing: will this bring Brightline a phone call.
Pick a topic your customers actually search for
Start with the question you already get asked, not the topic you find interesting. Brightline's owner hears "why is my water heater leaking?" on calls all the time, so that is the post. A topic only works if real people search for it, and most pages fail this test. Ahrefs studied around 14 billion webpages and found that 96.55% of all pages get zero traffic from Google. A post about something nobody searches for joins that pile.
The payoff for getting this right is real. Demand Metric, cited by HubSpot, found that companies that blog generate about 67% more leads per month than those that do not. That lift comes from posts tied to actual demand, not posts written to impress other plumbers.
Make a short list of the questions you answer by phone every week. Pick the one that, once solved, leads naturally to a job you can quote. A leaking water heater leads to a repair or replacement. That is the kind of question worth a post.
Skip the topics that feel impressive but go nowhere. "The history of modern plumbing" might interest Brightline's owner, but nobody searching it is about to book a job. A good test: would the person reading this post plausibly need to hire you within the week? If the honest answer is no, set the topic aside and pick the one tied to a real problem with a real cost attached.
Research what's already ranking and what to add
Type your question into Google and read the first five results. You are looking for two things: what they all cover, and what they all miss. Brightline's owner sees that every top post explains the common causes of a leak, but none tell the reader which leaks are an emergency and which can wait until morning. That gap is Brightline's edge, because it is the exact thing a worried customer wants to know at 9pm.
Do not assume you need to write the longest post on the page. Backlinko, in an analysis of 11.8 million search results, found the average first-page result runs about 1,447 words, but the study found no direct relationship between word count and rankings. Quality and relevance matter more than length. Aim to answer the question fully, then stop.
While you read those five results, keep a running note of two columns: "everyone covers this" and "nobody covers this." Brightline's owner ends up with a short note that says every post lists the causes of a leak and shows a generic diagram, but none give a real cost range for a replacement, and none explain how to shut off the water heater safely while you wait. Those two missing pieces are the most useful things on the page, and they come straight from the experience of doing the job. That is the part a hobby blogger writing the same topic could never add.
Build a simple outline before writing
Write your subheads as plain questions before you write a single sentence of the post. This is how working writers keep a draft on track. ProBlogger's Darren Rowse documents his own process for writing a single post, and he outlines as a list of bullet points first, then drafts against them. He is one practitioner showing a repeatable workflow rather than a theory, and the outline step is the part worth copying.
For Brightline, the outline is five questions a worried customer would ask in order:
- Is a leaking water heater dangerous right now?
- What are the common causes?
- Can I fix it myself, or do I need a plumber?
- What will it cost to repair or replace?
- How do I stop it leaking again?
That list is the spine of the post. Each bullet becomes a subhead. Now the writing is just filling in answers you already know from the job.
Write a headline that earns the click
Your headline has one job: make the right person click instead of scrolling past. Match the words your customer actually types. "Why Is My Water Heater Leaking? A Plumber Explains What to Do" beats "Water Heater Maintenance Tips" because it mirrors the search and promises a clear answer from someone who fixes these for a living.
Keep it specific and honest. If you can name the payoff, do. "Leaking Water Heater? How to Tell If It's an Emergency" works because it speaks straight to the fear that sent the person to Google. Write three or four versions, read them aloud, and keep the one that sounds like a real answer to a real worry.
Avoid headlines that promise more than the post delivers. If the title says "the only guide you'll ever need" and the post answers one narrow question, the reader feels misled and leaves. A reader who feels misled does not call. Brightline's owner keeps the headline matched to exactly what the post does: explain a leak, say whether it is urgent, and offer to come look. The click and the answer line up, and trust holds.
Write the draft like you're talking to one customer
Picture the last person who called you with this exact problem and write to them. Use "you." Use the words they use, not trade jargon. Brightline's owner writes "the puddle under your tank is usually one of three things" instead of "water heater leakage presents in several common failure modes." One reads like a helpful neighbor. The other reads like a manual.
Do not pad to hit a length. Semrush research, cited by Red Search, found that top-performing content averages just 1,152 words while low-performing posts average 668 words, so efficiency beats both extremes. Say the true thing, give the specific cost range or the real warning sign, and move on. A reader who feels you respect their time is a reader who keeps your number.
Format for skimming
Most readers scan before they read, so build the post for a fast eye. Keep paragraphs to two or three sentences. Break the answer into the subheads from your outline. Turn any "here are the causes" section into a list:
- A leaking drain valve at the bottom of the tank
- A failing temperature and pressure relief valve
- Corrosion inside the tank itself, which usually means replacement
A customer who lands on Brightline's post should be able to find "is this an emergency" in three seconds without reading the whole thing. White space and clear subheads do that work. A wall of text sends them back to the search results.
Add a clear call to action that turns readers into leads
A post without a next step is a missed call. After you have answered the question, tell the reader exactly what to do. Brightline closes with one line: "If the leak is coming from the tank itself, or you're not sure, call us at [number] and we'll take a look today." Specific, low pressure, easy to act on.
Put the call to action where the reader is most relieved, right after you have solved their problem. Offer the thing they actually want next: a quote, a same-day visit, a quick question by phone. If you want to give readers a sense of cost before they call, point them to a simple estimate tool rather than burying it in text. This is also the moment to connect the post to your wider work of turning visitors into buyers, which is the whole point of the page in the first place. For more on that, see how to get more customers.
Edit, then publish and update over time
Read the draft out loud once before you publish. Anywhere you stumble, the reader will too. Cut the sentences that could sit on any plumber's website unchanged, and replace them with the specific number, cause, or warning only you would know. That is the difference between a generic post and one a customer trusts.
After it goes live, treat it as a living page. When a customer asks a question the post did not answer, add it. When your prices change, update the figures. A post you revisit twice a year keeps earning calls long after the afternoon you wrote it. Brightline's water heater post becomes the answer they send to every caller, which frees the phone for the jobs that need it.
Frequently asked questions
How long should a blog post be?
Long enough to fully answer the question, and no longer. Backlinko found the average first-page result runs about 1,447 words with no direct link between length and rankings, while Semrush data shows top posts average around 1,152 words. Answer the question well, then stop.
How do I know if anyone will search for my topic?
Type your topic into Google as a plain question and see if real results appear that match it. If the page is full of pages answering that exact question, people are searching for it. Ahrefs found 96.55% of all webpages get zero traffic from Google, so writing for a real search is what separates a post that earns customers from one nobody finds.
Do I need to be a good writer to do this?
No. You need to answer a question clearly in the words your customers use. Writing to one real customer, using short sentences and a clear next step, matters far more than polished prose.
How often should I publish?
Quality beats frequency. One well-targeted post that answers a real customer question will out-earn a stack of vague posts. Publish when you have a genuine question worth answering, and update your best posts as your business changes.
The reason this process works is that it points every step at a real customer instead of at a writing standard. You pick the question they ask, answer it the way you would on the phone, and make the next step easy. That is also the thinking behind Fonzy, which finds the questions your customers are searching and helps you answer them, so the posts keep bringing in work without you having to learn SEO.
