Blogging for Small Businesses: Is It Worth the Effort?

A blog does not pay off through the number of posts but through the questions it answers before anyone picks up the phone. 99.3 percent (Federal Statistical Office of Germany) of all companies in Germany are small and medium-sized businesses, and across the European Union the figure is around 99 percent (European Commission) — businesses, in other words, where nobody writes text for a living. At the same time, roughly 89 percent (Federal Statistical Office of Germany) of companies with internet access run their own website. The difference between a website that merely exists and one that produces enquiries rarely lies in the design. It lies in whether visitors find what they need before making a decision: how does this work, what does it cost roughly, which documents are required, how long does it take? A service page can answer questions like these only up to a point without becoming overloaded. The blog is the place for depth. It pays off when it does three things: it answers questions that arise before the first contact, it takes work out of the initial consultation because prospects arrive prepared, and it gives your site reasons to appear for specific wordings that would not fit on a service page. To see how this connects with the rest of the build, take a look at our services around building and running a website.

The most workable topics are already sitting in your inbox. Around 92 percent (Federal Statistical Office of Germany) of people aged 16 to 74 in Germany use the internet, and a considerable share of that use is research before a decision. People rarely search using industry vocabulary; they search in everyday language, asking about cost, deadlines, prerequisites and comparisons. Those exact phrasings reach you every day free of charge — through the contact form, on the phone, in consultations. Collect them unsorted in a single list for four weeks without judging them. Then rank them by frequency: anything asked three times or more becomes a post, everything else stays a note. This approach has two advantages. First, you write about things you master professionally, which shortens the review time. Second, you match your customers' vocabulary instead of using terminology nobody types into a search field. If your enquiry form is already being evaluated, it delivers the topic list almost by itself — the post on turning visits into enquiries with contact forms describes which fields make that possible. A useful side effect: you quickly spot which questions belong on the service page and need no separate post at all.

The craft standard for a specialist post is modest, yet it is frequently missed. Around 71 percent (HTTP Archive Web Almanac) of the pages examined serve a meta description at all; for the rest, chance decides which snippet of text appears in search results. On accessibility the picture is starker: roughly 95 percent (WebAIM Million) of the home pages examined show automatically detectable failures against common success criteria of the Web Content Accessibility Guidelines (W3C). For blog posts these are usually the same three issues: missing alt text, skipped heading levels and links without a meaningful anchor. Fixing them costs a few minutes per post and decides whether a text stays usable with a screen reader or in poor lighting. On content, one simple rule applies: one question per post, visible in the title, answered in the opening paragraph, evidenced in the rest. Anything else that seems interesting belongs in its own text. For images it is worth reading about formats and alt text for website images — in blog posts, images are often the heaviest payload and at the same time the least well described element on the page.

A post without a follow-on is a dead end. Answering a question and then leaving the reader alone wastes the moment when interest is at its peak. Every post therefore needs at least one link to the service page it belongs to, and each service page in turn needs links to the two or three posts that go deeper on typical follow-up questions. This mutual linking has two effects: it moves people forward, and it makes the thematic relationship obvious to search engines. Machine-readable markup is worth adding as well: only about 41 percent (HTTP Archive Web Almanac) of pages requested on mobile contain structured data at all, even though posts benefit from it directly through author, publication date and modification date. The article on structured data and standing out in search results explains which markup suits which page type. At the end of each text there should then be a single clear next step instead of four competing calls to action. Which service page fits usually follows from the question itself — an overview of the possible destinations is given in the detailed description of our services.

The most common measurement mistake in a company blog is staring at page views. For a business with a regional catchment area, a post with 120 views a month that produces three qualified enquiries is worth more than one with 4000 views and no contact at all. What helps is a short list of metrics that traces the path to the enquiry, plus a fixed review date — quarterly is enough, monthly only produces noise at small volumes. Patience matters too: a new post typically needs three to six months before its position settles. Deciding after four weeks whether the blog is worthwhile means deciding too early. One decidedly unstatistical question in the first conversation helps as well: where did you read that already? When prospects refer to a post unprompted, that is a more reliable signal than any curve. Record the actual time spent per post as well; it is the basis for planning next year's rhythm realistically. To see how editorial work maps onto the feature set, look at the overview of what is included and what it costs.