A business blog that generates leads instead of company news

A business blog produces results when it answers the questions customers ask before buying. It produces nothing when it reports company news. The difference between those two explains why some blogs bring dozens of leads a month and others bring zero.

In this guide I go through how to build a blog that produces: where the topics come from, how to structure an article, how often to publish and how to measure results.

What a blog does when it is done right

It brings search traffic. You might have ten service pages, but there are hundreds of questions customers look for answers to. Every article is a new chance to be found.

It builds trust before contact. A customer reads three of your articles and calls already convinced. The sales conversation starts from a completely different point.

It gives sales tools. When the same question recurs in quote negotiations, the article can be sent as a link in reply.

It produces visibility in AI search. Content that answers questions is exactly what language models cite in their answers. More on this on our GEO page.

Where the topics come from

A shortage of topics is an apparent problem, not a real one. Four sources produce more topics than you have time to write:

• Questions from sales and customer service. The best source. If the same question comes up three times, it is an article. The question already comes in the customer’s words.
• Search term data. Search Console shows which searches already find your site. Searches you have no proper page for are ready-made topics.
• Competitors’ gaps. Look at what competitors write about and what they do not. The difficult subjects (prices, risks, failures) are often left entirely untouched.
• Your own experience. Projects, mistakes and lessons learned. Nobody else can write this content, and it is exactly what separates you from the generic mass.

An article structure that works

Use the same frame every time; it speeds up writing and helps the reader:

1. A headline containing the search term and a promise. “What a roof repair costs” is better than “Thoughts on roof repairs”.
2. A direct answer in the first paragraph. Do not save the point for the end. The reader and the search engine want the answer immediately.
3. Subheadings in question form. They structure the text and hit searches at the same time.
4. Specifics: numbers, examples, prices. This is what separates your article from all the others.
5. A frequently asked questions section at the end. Short answers to five genuine questions.
6. A call to action. What the reader should do next.

How often and how long

Two proper articles a month produce more than eight rushed ones. Regularity matters more than frequency: a pace you can sustain for a year beats a month-long push.

On length: write as long as covering the subject properly requires, typically 800–1,500 words. Length is not an end in itself, but a thin 300-word article goes nowhere in search results, because it does not answer the question all the way through.

After publishing: half the work is here

An article does not find readers by itself. Do these for every one:

• Internal links. Link the new article from the related service page and add a link to it in three old articles. This is the single most effective action, and it is almost always forgotten.
• Distribution. Social media, the newsletter, sales use. One article is many social posts.
• Updating. Put a check in the calendar six months out: do the prices, numbers and recommendations still hold?

What to measure

Blog results show slowly, so measure the right things. Organic traffic to the articles tells you whether they are being found. Search Console impressions and positions show the direction before traffic grows. The most important metric, though, is how many article readers end up making contact or on a service page: that separates useful content from entertainment.

A realistic timeline: the first signs appear in 2–3 months, the real effect in 6–12 months. A blog is a compound-interest investment where articles from a year ago are still bringing traffic.

Four mistakes that make a blog pointless

Company news. “We attended the trade fair” interests nobody but you. Write about what you learned, not about where you went.

Topics with no demand. If nobody searches for the subject and nobody asks about it, the article has no readers. Check the demand before writing.

Dodging the answer. An article that skirts the price question and ends with an invitation to get in touch lets the reader down. Answer directly, then sell.

Publish and forget. Without internal links, distribution and updates an article stays buried in the archive.

How one article gets written in an hour

Slow writing is usually the result of doing everything at once: thinking what to say, how to say it and whether it is right. Separate the stages and the speed multiplies.

Stage 1 (10 min): write down five questions the article answers. These are your subheadings.

Stage 2 (25 min): answer every question in a few sentences. Do not fix anything, just write.

Stage 3 (15 min): add a direct answer to the whole subject at the start and the frequently asked questions at the end.

Stage 4 (10 min): read it through, cut the repetition, check the main term is in the headline and the first paragraph.

Dictation is the fastest route to stage 2 for many people. Speak the answers into your phone and tidy the text afterwards. Dictation also produces more natural language than text hammered out on a keyboard.

Updating old articles produces more than new ones

Once a blog has twenty or so articles, updating starts producing more than writing new ones. The reason is simple: an old article already has a ranking and a history, so lifting it from position 8 to position 3 is easier than lifting a new one from nothing.

Find the articles sitting at positions 5–15 in Search Console. Look at what the current top offers that you are missing, add it, update the outdated numbers and add internal links. That is an hour of work per article and usually produces faster than a new piece.

Who writes: you, an employee or bought in

The best text comes from combining expertise and writing skill. In practice there are three options.

Writing it yourself produces the most authentic content but often does not get done because of time pressure. Written by an employee, the text stays in house, but quality varies. Bought in, the text definitely gets finished, but it requires an interview with you: without your own view the result is generic.

The model that works best for many is a combination: you give your view in a 20-minute call, the writer produces the text and you check the facts. That produces content a competitor cannot copy, without it taking a day per article.

Frequently asked questions

Is a business blog worth keeping?

It is, if customers look for information before the buying decision. A blog brings search traffic, builds trust and supports sales. If the buying decision is made with no background work at all, the benefit is smaller.

How often should you write for a blog?

Two good articles a month is a solid pace for most small businesses. Regularity decides more than volume: the pace you can sustain for a year produces best.

How long should a blog article be?

Typically 800–1,500 words, meaning long enough that the subject is covered fully. Articles under 400 words rarely end up ranking, because they do not answer the question comprehensively enough.

How long do you have to wait for blog results?

The first signs appear in Search Console in 2–3 months and the real traffic effect in 6–12 months. Old articles keep bringing traffic for years, which makes a blog a cumulative investment.

Can blog posts be produced with AI?

AI speeds up drafting, but text produced with nothing else is the same as everybody else’s. Standing out requires your own experience, concrete numbers and a point of view the model cannot invent for you.