How to build a content calendar for a small business blog you can actually keep

By Thomas Lovas Lokoy · Published 16 October 2026 · 6 min read

A paper calendar with a pen marking a date — Photo: Untitled · CC0

A content calendar for a small business blog does not need software, a team or a year of ideas. It needs to answer four questions: what are we publishing, for whom, by when, and who is doing it. A small business blog rarely needs more ideas; it needs someone to decide which idea comes next. This guide builds a calendar you can keep up with, starting from your customers rather than from a blank grid of dates.

Start with a publishing rhythm you can sustain

Before you plan topics, decide how often you can publish without the calendar becoming a source of guilt. Count honestly: how many hours a month can someone in the business spend on the blog, and how long does one post take you from outline to published, including checking and images? Divide one by the other and round down.

A slower rhythm you keep beats an ambitious one you abandon. Google's guidance on helpful content is about whether pages are useful, original and made for people, not how often they appear. Its self-assessment explicitly asks whether content is "primarily made to attract visits from search engines", which is a fair warning against publishing simply to fill a slot.

Pick a cadence, such as one post a fortnight or two a month, and a fixed publishing day. A fixed day turns the calendar from a wish list into a set of deadlines.

Collect topics from the people you serve

The GOV.UK content design guidance says that "every piece of published content should meet a valid user need", and its user-need format works well for a small business blog:

As a… (who is the reader?)
I need to… (what are they trying to do?)
So that… (why?)

Good places to find those needs, roughly in order of usefulness:

Questions customers ask you. Emails, calls, the counter, sales meetings. Keep a shared note and add to it every time someone asks something you have answered before. These are the best blog topics a small business has, because you know the answer and you know people want it.
Your own search data. If your site is verified in Google Search Console, the Performance report shows the search queries that led to your pages, with clicks, impressions, click-through rate and average position. By default it shows the past three months. Queries where you appear but rarely get clicked can point to a topic that deserves its own post.
Seasonal and operational events. Opening hours over holidays, seasonal products, deadlines your customers face, annual changes in your industry.
Keyword research. Useful for wording and for checking demand, but a weak source of ideas on its own. The keyword research guide covers doing it without relying on volume figures.

Write each idea as a working title plus one line of user need. An idea you cannot write a user need for is probably not a post.

Balance the calendar across the funnel

A blog that only publishes "how to choose a supplier" posts speaks to buyers and ignores everyone earlier. One that only publishes broad tips never helps anyone decide. Tag each idea by stage: learning about a problem, comparing options, or ready to act. The content funnel stages guide explains how each stage changes what a post should contain. When you fill the calendar, mix stages across each month rather than clustering them.

Build the content calendar itself

A spreadsheet is enough. Use one row per post and these columns:

Publish date. The fixed day you chose.
Working title.
User need. The one line from the topic list.
Primary keyword. Optional, but useful later.
Funnel stage.
Owner. One name. A post owned by "the team" is owned by nobody.
Status. Idea, outlined, drafted, checked, scheduled, published.
Draft due date. Set it well before the publish date so there is time to check facts and fix problems.
URL. Filled in once published.
Review date. When you will next look at the post.

Fill the next eight to twelve weeks with specific posts, and leave the period after that as a list of candidate ideas. Planning further ahead in detail tends to produce posts that are out of date before they are written.

Leave the occasional slot empty. Something will come up: a customer question worth answering quickly, a change in your sector, a post that takes longer than expected. A slack slot absorbs it without breaking the rhythm.

Work backwards from each publish date

For each post, the publish date is the end of a short process, not the day you start. A workable sequence:

Outline. Decide the reader, the sections and the evidence. The guide on how to outline a blog post covers this.
Draft.
Check. Sources, figures, names, dates. The fact-checking routine is a fixed-order checklist for this step.
Prepare. Title, meta description, images, internal links.
Publish and share.

Put the outline and draft deadlines in the calendar, not only the publish date. The status column makes it obvious when a post is slipping while there is still time to swap it for another.

Plan updates as well as new posts

A calendar that only schedules new posts slowly fills your site with old ones. Google's SEO starter guide recommends that you "check in on previously published content and update it as needed, or even delete it if it's not relevant anymore." GOV.UK's guidance on managing existing content makes the same point for government pages: monitor content to check it is useful and findable, then update or retire it.

Practical ways to build this in:

Set a review date on every post when you publish it. Posts with prices, rules or dates in them need shorter review intervals than evergreen explanations.
Reserve a slot each month for maintenance, treated as seriously as a new post.
Use the Search Console Pages view to see which posts get impressions; those are usually the ones most worth keeping accurate.

When you do update a post, be honest about it. Google's documentation on publication dates says a page can show a publication date, a last-updated date, or both, and that the dates "must describe the publication or update date of the page". Its helpful-content guidance asks whether you are "changing the date of pages to make them seem fresh when the content has not substantially changed". Change the date when the content changes, and not otherwise.

GOV.UK's guidance on change notes is a useful model for substantial updates: it says not to "say the page has been updated without saying what has changed". A line at the top or bottom of the post noting what changed helps returning readers.

Review the content calendar once a month

Set a monthly half hour to look back and forward:

What shipped, and what slipped? If the same kind of post always slips, it may be too ambitious for your rhythm.
What did readers respond to? Comments, enquiries that mention a post, Search Console clicks.
What is coming up? Seasonal events, product changes, questions customers have started asking.
Reorder the next eight to twelve weeks accordingly.

Keep the review short. The calendar exists to make publishing easier, not to become a project of its own.

Common mistakes

Planning dates before topics. You end up writing to fill slots.
No owner per post. Everything is somebody else's job.
No draft deadlines. Every post is written the night before.
No maintenance slots. The archive goes stale while the calendar looks busy.
Over-planning. A year of titles is a year of guesses.

If you draft posts with a writing tool, the calendar row is most of a brief already: reader, need, keyword, stage. Add your outline and sources, and the tool has what it needs to follow your plan rather than invent one.