From the Forge Publishing because the calendar says Tuesday is not a content strategy.

From the Forge

Does Your Small Business Actually Need a Blog, or Are We All Just Pretending?

A blog can be useful. A blog can also become a digital attic where "5 Tips for Choosing the Right Solution" goes to die.

CONTENT MANAGER
POSTS 12 published · 9 drafts · 1 survivor
LIVE
Why Your Water Heater Keeps Making That Sound Updated 2 weeks ago · 413 organic visits · 11 service clicks
2022
5 Plumbing Tips for Homeowners Last updated 4 years ago · 14 visits · nobody remembers writing it
2021
Why Quality Service Matters 812 words · says "quality" 17 times · answers nothing
DRAFT
Top 10 Reasons to Choose a Professional Created from a content calendar nobody admits approving
THE CONTENT STRATEGY Publish when there is something useful to publish.
One useful article can do more work than twenty posts written to keep the calendar happy. Template Forge

Every small-business website seems to have one.

Blog.

You click it.

The newest post is from March 2022.

The headline is something like: "5 Reasons Why Quality Matters When Choosing a Professional."

Nobody has touched it since.

The page has the emotional energy of a mall fountain after closing.

This is usually the result of a familiar strategy: somebody said the business "needed a blog for SEO." Nobody decided what the blog was actually for.

So the business published three safe little articles, ran out of things it wanted to say, and quietly backed away from the entire section.

Which raises the question: did the business need a blog? Or did it need useful answers somewhere on the website?

A blog is useful when the business has something repeatable to explain.

Good business content usually starts somewhere boring: the phone, the inbox, the estimate appointment, or the same customer question being answered for the forty-third time.

That is content.

A plumber keeps explaining why a water heater is popping. A bakery keeps answering how far ahead custom cakes need to be ordered. A process server keeps explaining what information is needed before service. A contractor keeps answering whether a permit is usually required for a certain type of project.

Those are not "blog ideas." They are business knowledge customers already ask for.

Publishing that knowledge can save sales conversations, help people make decisions, give search engines useful pages to understand, and create something worth linking to from service pages.

Echo's filter

If nobody has ever asked the question, needed the answer, or benefited from the explanation, I am suspicious of the assignment.

"We need to post every week for SEO" is not a law of nature.

Google is unusually direct about this.

Its people-first content guidance warns against producing lots of content across many topics mainly because you hope some of it performs in Search.

It also says Google does not have a preferred word count.

And Google explicitly says that adding lots of new content or removing older content just to make a site seem "fresh" will not improve rankings overall.

Which means the sacred ritual of publishing 837 words every Tuesday at 9:00 AM because an SEO checklist told you to is not sacred.

It is a calendar event.

Search optimization still matters. Google Search Essentials recommends helpful, reliable, people-first content and using words people actually use when looking for that content.

That is very different from saying: "Please generate another article because we have not fed the algorithm this week."

Your customers are already writing the editorial calendar.

You just have to notice.

Before buying "How much does this usually cost?"

Pricing context, ranges, variables, and what changes the estimate.

Before calling "Do you handle my situation?"

Service fit, edge cases, exclusions, areas served, and timing.

After comparing "What is the difference?"

Materials, service levels, methods, options, and tradeoffs.

After something breaks "Is this normal?"

Troubleshooting, warning signs, maintenance, and when to call somebody.

That is enough material for years in some industries.

And unlike generic "industry trends" filler, it is attached to actual customer uncertainty.

The article does not even have to live under a section called Blog. It can be a guide, resource, FAQ article, field note, knowledge base entry, or explanation.

The label is less important than whether the page earns its URL.

Do not publish commodity sludge just because AI made it cheap.

Content got easier to produce. That did not automatically make it more worth reading.

Google's current guidance for generative AI search tells publishers to focus on valuable, non-commodity content, unique viewpoints, first-hand experience, and information that is not merely recycled from what everybody else already said.

That is a useful standard even if you do not care about AI search.

Ask what the business knows that the generic article does not. What actually goes wrong? What do customers misunderstand? What does the owner disagree with? What has the team learned from doing the work?

If the article could be published by 4,000 unrelated businesses after replacing the logo, it may not be content yet.

Automation can help with research organization, outlines, cleanup, formatting, and production.

But if the only reason the page exists is "we asked a machine for 25 HVAC topics," I would like to file a complaint on behalf of HVAC.

You do not owe Tuesday a blog post.

Consistency is useful when consistency supports a real audience. A local publication may need a schedule. A newsletter may need a rhythm. A store with frequent releases may have regular updates.

But a small landscaping company does not become irresponsible because it did not publish "Fall Lawn Trends You Need to Know" before lunch.

Publish because:

  • the answer is useful,
  • the topic supports a service or product,
  • customers repeatedly need the information,
  • you have something original to contribute,
  • or the page deserves to exist as a durable resource.

That cadence may be weekly. It may be twice a month. It may be six genuinely useful articles in a year.

The internet will survive.

The useful article should have a job after Publish.

What is the article supposed to do?

Rank for a useful question? Support a service page? Reduce repetitive sales explanations? Earn links? Give social media something worth sharing? Help a visitor choose between two options?

Measure that.

Do not declare victory because the CMS says Published.

Publishing is an action you took. Usefulness is what happened afterward.

So, does your small business actually need a blog?

Maybe.

If customers repeatedly ask questions, your team has real expertise, searchers need explanations, and useful content can support the business, then yes, publishing can be extremely valuable.

But you do not need a blog because the navigation would look empty without one.

You do not need one because somebody sold you "four SEO posts per month."

And you definitely do not need a weekly graveyard of "Top 7 Benefits of Choosing a Trusted Professional."

Start with the questions. Publish the answers that deserve permanence. Call the section whatever makes sense afterward.

Sources behind the non-sarcastic part

The blog is optional. Having something worth saying is not.

Publish less filler.

Keep the pages that actually help somebody.

The comment section has entered the chat

Join the discussion

0 approved comments

Does a small business still need a blog, or is useful content better published only when there is actually something worth saying?

No approved comments yet. You could be first, which is either exciting or suspiciously responsible.

Add your two cents

Keep it useful, keep it human, and disagree without flipping the table. Comments are reviewed before they appear.

Your email stays private. It is used for moderation and abuse prevention, not public display.

0 / 3,000

All articles