The CMS is where your blog lives. Writing articles, publishing them, and keeping them findable.
What an article carries
A title, which is what appears everywhere and what people search for.
An excerpt, a short description used in listings and by search engines.
The body, written as text rather than dragged into place.
A category, so related articles group together.
An author.
An image, for listings and for anything shared.
Related products, which is the one people skip and the one that makes a blog commercially useful. An article about a problem, linked to the thing you sell that solves it, is the whole mechanism by which writing turns into revenue.
The excerpt matters more than it looks
It is the sentence somebody reads before deciding whether to read the article. It appears in listings, in previews, and often in search results.
Write it as a promise, not a summary. "How we cut invoice chasing from four hours a week to twenty minutes" earns a click. "An overview of accounts receivable improvements" does not.
One sentence. If it needs two, the article is about two things.
Categories
Keep them few. Four or five.
A blog with fourteen categories has one article in most of them, which makes the category navigation actively misleading: somebody clicks expecting a body of work and finds a single post from last year.
Name them for what a reader wants, not for your internal structure. "Getting paid faster" is browsed. "Finance module updates" is not.
Images
An article without one looks unfinished in every listing it appears in, and looks broken when somebody shares it.
One image, relevant, and the same shape as the others. Mixed aspect ratios in a listing look like a fault rather than a choice.
Publishing rhythm beats publishing volume
The single most useful thing to know about a business blog.
Two articles a month, indefinitely, beats twelve in one quarter and nothing after. A blog that stops is worse than one that never started, because the most recent post is dated and everybody can see it.
Decide the rhythm you can actually keep, then halve it. Whoever is writing has another job.
What to write about
Answer the questions you already get asked. Your inbox is the content plan. Anything explained more than three times to customers is an article, and writing it once saves the explanation forever.
Write what only you can write. Your data, your experience, your customers' actual problems. General advice is available everywhere and ranks nowhere.
Do not write about yourself. Nobody outside your organisation is looking for your company news, and a blog that is mostly announcements is one nobody subscribes to.
Categories, related products, and revenue
The link between an article and what you sell is the mechanism, and most business blogs never wire it up.
An article about a problem, with the relevant product attached, gives a reader who has just recognised their situation somewhere obvious to go. Without it, they finish, agree with you, and leave.
Attach one product, not four. A reader offered several options takes none.
Only where it genuinely applies. An article with an unrelated product bolted on reads as an advertisement, and readers stop trusting the next one.
Should you have a blog
Worth asking honestly, because the failure mode is expensive in a specific way: a stale blog signals a business that has run out of energy, and it signals it on your own website.
Yes, if somebody will own it and you have questions worth answering.
No, if it will be written by whoever has time this month. Put that effort into the knowledge base instead, where content that answers a real question keeps working forever and never looks stale.
That is not a lesser option. For most business software companies, the help centre does more commercial work than the blog, because people arrive at it with intent.
Writing one
The shape that works, and it is not the shape most business blogs use.
Open with the problem, in the reader's words. Not with context, not with your company, not with a definition. Somebody who recognises their own situation in the first two lines reads on.
Then what you actually did or found, with the specifics. Numbers, decisions, what went wrong. This is the part nobody else can copy and the only reason anybody stays.
Then what it means for them.
Then one next step. One. A post ending with four suggestions gets none of them taken.
The version to avoid is the one that opens by explaining what invoicing is. Anybody searching for it already knows.
Cadence beats everything
Worth repeating because it is the decision that determines whether a blog works.
The value compounds only if it continues. Two a month for two years is a body of work people find, subscribe to and cite. Twelve in one quarter and nothing after is an archive with a visible date on it.
Publish the second article before promoting the first. A visitor who arrives and finds one post leaves and does not come back.
Two habits
Update rather than republish. An article from two years ago that is still right should be edited and kept, not rewritten as a new post. It has accumulated whatever authority it has, and starting again throws that away.
Link to your own articles. A reader who finishes one and finds nothing else to read leaves. Two relevant links at the end of every article is the cheapest thing on this page and one of the most effective.
What it will not do
It will not schedule for you. Publishing is an action somebody takes.
It will not distribute it. Getting an article in front of people is Marketing.
It will not tell you what worked. Article performance depends on whatever analytics your site runs, not on this surface.
Did this answer your question?
No, ask a person