Does a small business website need a blog

What a blog is actually for on a small business site

A designer added a blog to the site map without asking, and the tab has sat empty since the site went live. Nobody on staff volunteered to write anything, and the owner isn't sure anyone should have to.

A blog earns its place when it answers a real question in public, in the business's own words, tied to something customers actually ask. That's it. It isn't a requirement, a ranking trick, or proof the site is being taken seriously.

The wider picture a blog is supposed to feed is worth understanding before adding one. A blog gives search and AI assistants more pages that name what the business does and where. Without that foundation, extra posts don't have much to attach to.

Treating a blog as a box to check does the opposite of that. A post written to satisfy a checklist rather than to answer anything reads as filler the moment a stranger opens it, and a stranger who lands on filler once rarely comes back to check twice.

Questions customers already ask as the only reliable source of subjects

Skip the keyword tool. The questions worth answering are the ones already asked out loud, on the phone, at the counter, in the same email over and over. Those are proof a real person searched for that exact answer and didn't easily find it.

Keep a running note near the register or the inbox. Every time the same question comes up twice, that's a post. Nothing invented, nothing guessed at from a competitor's site.

A question that only ever comes up once probably isn't worth a whole post. Save it for a reply, a text, or a line added to an existing page instead. The list only grows into something worth writing from once a pattern shows up on its own.

The pages a site needs before any of this works matters more at the start than a blog does. A blog with no service pages behind it is answering questions with nowhere solid to send the reader next.

A blog against simply having better service pages

A service page should already say what the business does, for whom, and where. If that page is thin, a blog won't fix it. It just adds more thin pages next to the first one.

Where a blog earns real space is the material a service page can't hold without turning into clutter: a longer answer, a specific edge case, a question that doesn't belong on the main page but comes up often enough to matter.

For short, recurring questions that don't need a full page each, an FAQ section built to cut down repeat questions does the job with less ongoing writing than a blog asks for. A blog and a good FAQ aren't the same tool, and a business can run one without the other.

A landscaper deciding between the two might put "do you work through winter" on the FAQ, since it's short and settled, and save a longer post for something like choosing plants for a specific soil type, which needs room to actually explain itself.

The abandoned blog with an old post sitting at the top

A blog with one post from three years ago sitting at the top does more damage than no blog at all. It reads as a business that started something and walked away, which is not the impression anyone wants a stranger to form in the first ten seconds.

That dated post doesn't fade quietly. It sits there, timestamped, telling every visitor exactly how long it's been since anyone touched the site. A visitor doesn't know whether the business closed, changed hands, or simply stopped bothering. They rarely stay to find out which.

If a blog exists already and nothing's been added in a long while, there are only two honest moves: write again, or take the section down until there's a real plan to keep it going. A visible gap left standing is worse than a blank tab.

Neither move takes long. Writing one current post resets the clock. Removing the section entirely takes minutes and stops a three-year-old date from doing quiet damage every day it stays up.

Who is realistically going to write it

Before adding a blog, name the actual person who will write the first post, and the fifth. Not "the team." Not "someone will handle it." A specific person, with time set aside for it, or the blog stays a tab nobody opens.

An owner who genuinely enjoys explaining the work is well placed to write it, even in short, plain paragraphs with no polish attempted. A hired writer can produce cleaner prose, but only if someone still supplies the real questions and the real answers behind them. Handing a writer nothing but a topic and a deadline tends to produce exactly the kind of generic filler the first section warned about.

Whatever gets published still needs a proper title and description once it's live, the same as any other page. Writing titles and descriptions that get clicked applies to a blog post exactly as it applies to a service page, and skipping that step wastes the writing that came before it.

Publishing occasionally and well against a schedule nobody keeps

A weekly posting schedule sounds disciplined on the day it gets written down. Whether that pace holds depends entirely on how much spare time exists once the actual job of the business gets done, and a schedule that quietly stops partway through the year is more visible than no schedule ever was.

A handful of solid posts, spaced out and each one answering a real question properly, beats a weekly calendar that collapses partway through the year. Nobody reading a post checks whether it arrived on time. They check whether it actually answers what they came to ask.

Set a loose target instead of a fixed one. One post whenever a genuinely new question surfaces holds up better over time than a calendar full of dates picked in advance and abandoned a few months in.

A blog isn't the only way to keep a site looking current, either. How a site is supposed to grow after the launch date covers the other ways a business keeps a site from going stale without committing to a publishing habit it can't sustain.

If there's no honest answer to who writes it and how often, the right call is to leave the blog out for now. A site with no blog tab is a more honest site than one with a tab that hasn't moved in years.

More from the blog

All posts