Most business owners with a blog have the same experience: they write posts, they publish them, and then very little happens. No calls. No emails. No indication that anyone found it.
The usual advice is to post more. Write more often. Be consistent. And so they do — or they hire someone to do it — and the phone still doesn’t ring.
The content isn’t the problem. The approach is.
Why most business blog posts don’t produce anything
Here’s a test. Take your most recent blog post and ask: does any sentence in here contain something only you would know? Something that comes specifically from your experience doing this work, with your clients, in your market?
If the answer is no — if someone who had never done your work could have written it from a Google search — then the post is not doing the thing a blog post actually needs to do.
Content that ranks in search and converts readers into leads has two things that generic content doesn’t: it demonstrates real experience, and it says something that sticks.
Google calls this EEAT — Experience, Expertise, Authoritativeness, and Trustworthiness. The Helpful Content updates over the last few years have made their filter for this more aggressive. Content that covers a topic without demonstrating genuine expertise gets downgraded in favor of content that shows the author has actually done this work.
Readers have a version of this same filter. They can sense when something is a template. It reads smoothly, it covers the right topics, and they forget it immediately because there was no opinion in it. No story. Nothing that could only have come from someone who has sat in the room with real clients and worked through the real problem.
What happened when a mental health practice tried to rank with AI content
A mental health practice wanted to rank for their target keywords across a wide geographic area. They offer services online, so local visibility in multiple cities mattered. They decided to create the content themselves using AI — it looked easy enough, and they didn’t see a reason to pay someone to do it.
The first batch they sent me was generic descriptions of parks in different cities. The idea was to rank their mental health services with local content by connecting each location to a nearby park.
I pushed back. Generic descriptions of parks aren’t new content. Google has been filtering this out since the original EEAT signals were added to the algorithm, and Helpful Content updates have made it progressively harder to rank content that doesn’t demonstrate genuine expertise. A list of parks that anyone could find on a city website tells Google nothing about who wrote it or whether they know anything about mental health.
My recommendation: keep the list of parks, but come up with something about mental health that only they could say about those places. That unique angle — combined with their actual credentials and experience — would give those pages a real chance to rank.
They never completed that task. There’s more to this than asking an AI to write the content, and they ran into exactly that problem. The AI will write the words. It won’t tell you the words are wrong, because it’s a sycophant. It’ll say the content looks good and will rank, even when neither of those things is true. That’s one of the problems these skills were built to push back against.
What a blog post actually needs to do
A blog post has to do two things: earn its place in search results, and give the reader who finds it a reason to trust you.
It earns its place in search by targeting a specific question your ideal clients are actually typing into Google — not the broad category, but the specific question. And it answers that question in a way that demonstrates you have actually dealt with this before, not just researched it.
It earns trust by being specific. A story. A number. A detail that could only come from someone who has done this work. Something the reader can hold onto.
The wall-of-words post that covers everything broadly and concludes with nothing actionable doesn’t do either of these things. It exists because someone was told to post consistently, not because it was worth writing.
How the Blog Post Writer approaches this differently
The Blog Post Writer starts from a voice profile — a document that captures how you actually talk about your work, the specific stories you tell, and the things you believe that your competitors don’t. When a post is written from that foundation, it sounds like it came from a specific person because it did.
From there, the tool identifies the specific search intent the post should target — not the broad topic, but the actual question — and builds the post around a real example from your experience. Something that could only have come from you.
The result reads the way good content should: like a knowledgeable person explaining something they have actually done, to someone who is trying to decide whether to trust you.
That is what gets found in search. And it is what makes someone pick up the phone.
One post that earns its place is worth more than ten that don’t
If your blog isn’t producing leads, adding more posts in the same pattern won’t fix it. The first step is writing one post that does the actual job — that targets a real question and answers it in a way only you can.
The Blog Post Writer runs the process. Free, one session, and it produces a draft that starts from your actual experience rather than from a template.
If you want OptSus to run this as part of a broader content strategy for your business, email [email protected].
