A blog or a help centre: which one earns its keep
Decide whether your next content budget should go to a blog or a help centre by reading the evidence already sitting in your support inbox.
The choice behind the content budget
Two content projects usually compete for the same money. A blog goes after people who do not know the business yet. A help centre answers people who have already paid. Both get called content and both get costed the same way. They do completely different jobs.
Most Indian small businesses start a blog because it is the default suggestion from every agency and every website template. The help centre arrives later if at all. That order is often backwards. A business whose support queue is full of the same twelve questions is paying salary every month to answer them by hand.
What each one costs and what neither includes
Neither option includes the subject knowledge. A writer can structure and publish. A writer cannot know why your warranty excludes transit damage or how your Tally export is meant to behave. Somebody inside the business has to supply that and review it. Budget two to four hours a week of a knowledgeable person for as long as the project runs. Service fees also attract GST at 18% on top of any published rate.
A blog is a recurring cost because its value decays. Articles need refreshing and the pipeline needs feeding. A help centre is closer to a one-off build with maintenance. You write the forty answers once then revise them when the product changes. Over three years the help centre is usually the cheaper asset. It is also the duller line item to approve which is part of why it does not get approved.
Who should build which, and who should build neither
A help centre earns its keep when the same question arrives repeatedly through more than one channel. Software, consumer durables, insurance broking, education and anything with an onboarding step fit this. A blog earns its keep when buyers research for weeks before committing and when that research happens in public search. Industrial equipment, B2B services and financial products fit that.
Some businesses should build neither. If sales come from a small number of relationships won in meetings and tenders then content is not the constraint and no amount of publishing will become the constraint. A local business with one repeat product also gains little. A tiffin supplier or a salon or a plumbing outfit gets more from its Google Business Profile and its WhatsApp list than from either project. Buying content marketing in that position means buying the wrong thing well.
How to decide using evidence you already own
Export the last three months of support messages across email, WhatsApp and whatever your team logs after calls. Group them by the question asked rather than by the customer who asked it. Count the groups. Twenty questions that each recur more than five times is a help centre waiting to be written. If the support inbox is thin and most incoming messages are first contact from strangers then demand sits upstream and the blog is the better bet.
Then check whether those questions get typed into search at all. Use autocomplete and the People Also Ask box with the exact phrasing your customers use. Many internal questions have no search demand whatsoever. They still belong in a help centre because the value there is deflection and not acquisition.
Judging whether it worked
For a help centre the metric that matters is support contacts per hundred active customers measured month on month. If the articles are doing their job that number falls. Pair it with the share of visitors who read an article and then raise a ticket anyway.
For a blog the metric that matters is assisted conversions. Those are people who read an article, left, returned later and enquired. Set that measurement up before publishing rather than after. The metric that flatters is pageviews. Traffic can treble on articles that attract students and jobseekers and competitors. Nobody controls which queries a page gets shown for, so a rising traffic line is not evidence that buyers are reading.
The common mistake
The expensive error is running both at half strength. A blog needs consistency across quarters before it accumulates any standing in search. A help centre needs completeness before customers trust it enough to look there first. Half a blog and half a help centre produces two assets that neither rank nor deflect, at the full cost of both.
The same error has a second form. Help content gets buried inside the blog and written in marketing language. A troubleshooting answer dressed as an article helps nobody. The customer cannot find it and the prospect does not want it.
A note on sequencing
If both genuinely apply then build the help centre first. It is finite, it reduces a cost you are already carrying, and the material it produces feeds the blog later. The reverse does not hold.
Nobody can tell you how long either asset takes to pay back. That depends on your support volume, your competitors and how search engines choose to display answers in your category. None of those three sit under your control.
This guide explains how something works. It is not legal, tax or financial advice, and rules change. Confirm anything regulatory with a qualified professional before you act on it.