Do you need a blog on your company website? An honest answer

You need a blog if your buyers search for answers before they hire, and someone at your company can write those answers from experience at least twice a month. If either is missing, leave the blog out. A page of three posts from two years ago makes a company look inactive, which is worse than having no blog at all.

That is the short version. The longer one covers what a blog does for a business site, what to build instead when a blog is the wrong tool, and what keeping one alive involves.

What does a blog do for a business website?

A blog does one job well: it answers questions that your buyers type into Google weeks before they are ready to contact anyone. A plumbing contractor's service page ranks for "plumbing contractor in Pune". It does not rank for "why does my water heater trip the breaker", and the person asking that today is the person hiring next month.

It does three smaller jobs on the side.

• It gives your sales conversations something to link to. "Here is the guide we wrote on that" is more convincing than a paragraph in an email.
• It shows that you have done the work. A post that explains a problem from the inside is proof that no About page can match.
• It gives your service pages internal links from relevant content, which helps those pages rank.

What a blog does not do is bring traffic by existing. A post on a topic nobody searches for, or one that repeats what the top ten results already say, gets nothing. Google's own guidance on creating helpful, reliable, people-first content is the standard: would someone who read this leave feeling they learned enough to achieve their goal?

When is a blog worth having?

Three conditions, and you need all three.

Your buyers research before they buy. Anyone choosing a web developer, an accountant, a clinic, a school or a B2B supplier reads first. Anyone who needs a locksmith at 11pm does not.

Someone can write from experience. The person who answers client questions all day has thirty posts in their head already. A junior marketer or an agency writer has none, and the gap shows. This is the condition that fails most often.

You can keep it up for a year. Posts take three to six months to rank, and a blog with four posts has not given Google much reason to index it. Plan for at least two posts a month for twelve months before judging the result.

When we build a company site as part of a website design and development project, we include a blog only when the client can name who will write it. If the answer is "we will find someone", we leave it out and add a FAQ page and a case study section instead. A blog can be added later; an abandoned one is harder to remove because its URLs may have picked up links.

When is a blog a waste of money?

• A local trade with no research phase. Electricians, movers and car repair shops win on Google Business Profile reviews and a fast site with a phone number. A blog comes a long way behind both.
• A company where nobody will write. Outsourced generic content ("5 reasons to hire a professional") does not rank and does not convince anyone.
• A business with under ten questions worth answering. Put them on a FAQ page. It is one page to maintain, not a publishing schedule.
• A new company that has not finished its core pages. Finish the service pages, the About page and the contact page first. A blog on a site whose service pages are thin sends readers to a dead end.

We build blogs; we do not write them. Our services stop at design, development and the technical setup that lets a blog rank, so there is no commission in this advice.

What should you build instead of a blog?

Three alternatives cover most of what a blog is asked to do.

A FAQ page with real answers, marked up with FAQ schema, often does more for a small company than a blog would, because it is finished the week it is written. See what pages a business website needs for where it sits in the site.

Case studies are the second most useful page type and the most neglected. One case study with a real number ("quote-to-order time went from four days to one") outweighs ten posts. Our guide on collecting testimonials and case studies covers how to get them.

What does keeping a blog alive involve?

A blog fails for one of two reasons: nobody owns it, or nobody knows what to write next. Both are fixed before the first post.

1. Name an owner. One person, with publishing in their job description, not "the marketing team".
2. Write the question list first. Thirty questions clients actually ask, with the words they use. Sales email and WhatsApp threads are the source. If you cannot get to thirty, that is a sign the FAQ page is the better tool.
3. Set the format. The first paragraph answers the question. Headings are questions. One first-hand detail per post. No post under 800 words, none over 2,000.
4. Decide the cadence and halve it. If two a week sounds possible, commit to one. A schedule you keep beats one you abandon.
5. Review every post at six months. Prices, versions and screenshots date. Update the post, and the "updated" date, only when the content changes.

This blog runs on exactly that plan: a question list drawn from enquiries, posts written by the person who does the work, and a six-month review cycle.

How should a blog be built into the site?

If you decide to go ahead, the build matters as much as the writing. Ask your developer for these; they are the difference between a blog that can rank and one that cannot.

• Posts at /blog/post-name on the main domain, with short hyphenated slugs.
• Categories, not tags. Tag pages are thin and compete with the posts.
• A visible author with a bio, and published and updated dates.
• A title and meta description you write by hand for every post. Check them against Google's display limits with the meta length checker.
• Article structured data, an RSS feed and the posts in the XML sitemap.
• Each post linking to a service page in context, and each service page listing its best posts.

Decide on the blog at the planning stage, with the rest of the page list, so it fits the site structure instead of being bolted on. The pillar guide on how to plan a company website covers where that decision sits in the process.