Last month, a client of mine published 22 blog posts. Together they earned 20 clicks from Google. In the same four weeks, one single page on the same website earned 618 clicks and brought in almost half of the company's form leads.
That gap is the whole point of this post. If your content strategy (the plan for what you publish, and why) is "post a new article every week," you are probably working hard on the wrong thing. Here is what I would write instead, and how to start this month.
What 22 blog posts taught me about content strategy
The client is a concrete fence company in Serbia. I manage their website and their content.
Between late August and late September, we published 22 articles. Most followed a template: a town name, a type of fence, a few paragraphs about installation. They were fine. Google found and listed every one of them. And in their first weeks, all 22 together earned 20 clicks from 356 appearances in search results.
To be fair, some of those posts were only days old, and new pages take time to climb. But look at what happened on the page that did work.
It answers one blunt question: "How much does a concrete fence cost per meter in 2026?" In the same 28 days it earned 618 clicks. That is about half of every search click the whole site got. It also produced 6 of the 13 contact form leads that month.
Technically, that page lives on the blog. But it is not a "blog post" the way most business owners picture one. It is an answer. Someone is about to spend real money, they type the exact question into Google, and the page answers it straight.
One more number. When I had all the recent posts reviewed for quality, the two articles about real, finished jobs scored 9 and 8 out of 10. The template posts averaged 3.5. Google and the customers seem to agree.
The answer page: the one format I would build first
An answer page takes a question your customers ask on the phone and answers it better than anyone else online. Price, timing, "do I need a permit," "what happens if."
Here is a simple test. Think of the last ten calls or emails you got. Write down every question. Those questions, in your customer's own words, are your first pages.
A few examples from other industries:
Each one is a question people type into Google right before they pick up the phone. That is the moment you want to be the one answering.
What makes an answer page work:
This is the heart of good SEO (search engine optimization, meaning how you get found on Google) for a local business. No tricks. Answers.
If you are not sure which questions your customers are really asking, or your site makes answers hard to find, let's talk. I will tell you honestly which page I would build first.
Four more formats that beat another blog post
The answer page is the anchor. Around it, I build a small "content factory": a handful of formats where each one does a single job well. Not all of them need a writer.
A real FAQ page, built from real questions
Not the fluffy kind with "Why choose us?" as the first question. A proper FAQ page collects 10 to 20 short, honest answers in one place.
Add FAQ schema to it. Schema is a set of hidden labels in the page code that tell Google "this is a question, and this is its answer," so search engines understand the page without guessing.
A map of the jobs you have actually done
A page with a simple map of finished projects, where each pin opens a photo and two lines about the job. For a landscaping company in Atlanta, fifty pins across the metro area say "we work near you" faster than any paragraph can.
I covered town-by-town pages in an earlier post, Stop Writing Blog Posts. Write THIS Instead. The map is the visual proof that sits next to them.
A simple drawing that explains your process
A sketchnote is a hand-drawn style diagram: a few boxes, some arrows, a handful of words. "What happens from your first call to the finished kitchen," in one picture.
It is quick to understand and easy to share. Put the written version right below the drawing, because Google reads words, not pictures.
A field report from a finished job
Remember the 9 and 8 out of 10? Those were field reports. What the customer needed, what we found on site, what we did, and what it looked like after.
Add photos, one honest problem you solved, and one real number. Nobody else on the internet can write your field reports, and that is exactly why they stand out.
Here is how the formats compare, based on how I plan this for clients:
| What to publish | What it does for your customer | Rough time to make one | My recommendation |
|---|---|---|---|
| Answer page | Answers the question they ask right before they buy | 3 to 5 hours | Build this first, one per top question |
| FAQ page | Clears up small doubts in one place | 1 to 2 hours to start | Build once, add to it every month |
| Map of real jobs | Shows you work near them, with proof | Half a day to set up, minutes per new job | Great if you travel to your customers |
| Process drawing | Shows what happens and how long it takes | 1 to 2 hours with a simple template | Best for services with many steps |
| Field report | Shows real work and real results | About an hour after a job | At least one a month |
| Generic "tips" post | Competes with thousands of similar articles | 2 to 4 hours | Skip it |
How to start this month, step by step
You do not need a big budget or a content team for this. You need your inbox and a few focused hours a week.
Then check what works. Google Search Console (Google's free tool that shows which searches find your site) tells you how many clicks each page gets. Give new pages 6 to 8 weeks, keep building the formats that get clicked, and stop making the ones that do not.
If you want to see how I plan and build this for a client, my process page walks through it step by step, and the FAQ covers what people usually ask me first. And if adding a new page to your current site feels like a fight every time, that is a web development problem worth fixing before you write anything.
The Bottom Line
A good content strategy is not about publishing more. It is about publishing the few pages your buyers are already searching for: clear answers, real proof, and one obvious next step. One strong answer page can outwork twenty generic posts.
Want me to look at your site and tell you which page to build first? Get in touch here.