Small business blogging by business type

Small business blogging follows one method for every business, and each type adds a short list of rules of its own. A store's posts hand readers to products, a local business's posts hand them to a call, a software company's posts hand them to a trial, and a publisher's posts are the product.

The variant lines in chapters 1 to 13 mark where a rule differs. This chapter gathers what only each type needs.

Online store

A store's collection and product pages catch people ready to buy; the blog catches everyone still deciding and hands them to the right product.

What a store blog is for

  • Buying guides: "How to choose a [product] for [use]", with a comparison table of the types and the one to pick for each use.
  • Comparisons: "[Product A] or [product B]?", "[material] vs [material]", and the store's range against the alternatives, verdict first.
  • List posts: "best [product] for [use]", with the selection method up front.
  • How-to and care content: how to use, fit, clean, store and repair what the store sells. It earns repeat visits and leads to accessories and refills.
  • Every post leads to a collection or a product. A post that ends with nothing to look at is a cost.

Product card embeds and tested calls to action

  • Embed a product card wherever the text recommends a product: the image, the name, the live price and stock from the catalogue, and one button. Prices are never typed into the post.
  • Place cards at the point of decision, next to the sentence that recommends the product, not in a carousel at the end.
  • Test the card's call to action on high-traffic posts ("See the [product]", "Add to cart", "Compare sizes"), one change at a time, and keep the winner.
  • Cards render on the server with sized images and no layout shift.

Linking posts, collections and products

  • Posts link to the collection and the products they discuss; each collection links back to its two or three best guides, and each product page links to its care and how-to guides.
  • Never let a post cannibalise a collection page. The collection owns the commercial term ("buy [product]", "[product] price", "[product] shop"); the post takes the informational and comparison terms next to it. A post that starts ranking for the collection's term gets its title and H1 re-pointed to its own question, and a link to the collection with the collection's term as the anchor.
  • The collection page carries its own short buying text, so it never needs a post to rank for its term.

Seasonal and launch content

  • Plan posts by the store's selling calendar: seasons, holidays, gifting dates, the weather and product launch dates.
  • Publish seasonal posts at least 8 weeks before the peak, so they are indexed and linked when demand arrives. Keep their URLs evergreen and refresh the same post each year instead of writing a new one (chapter 4).
  • Each significant launch gets a post: what is new, who it is for, how it compares with what came before, and a link to the product. Update it with real buyers' questions after the launch.

Questions from reviews and support

  • Mine product reviews, support tickets, chat logs and return reasons for the questions buyers ask and the words they use. Each recurring question becomes a section, an FAQ answer or a post of its own.
  • A return reason tells you what to write: "too small" calls for a sizing guide; "not what I expected" calls for a better comparison.

Clean canonicals and no crawl traps

  • Every product and collection has one clean, self-referencing canonical. Variant, filter, sort and tracking URLs point their canonical at the clean URL.
  • Faceted navigation never spawns endless crawlable URLs: filter combinations aren't linked as crawlable pages, stay out of the sitemap, and are blocked or kept out of the index where they multiply.
  • A discontinued product gets a 301 to its closest replacement or its collection; a product that is out of stock for now stays live.
  • The sitemap lists only canonical product, collection, post and category URLs, and hreflang covers every language and region version.
  • Where the platform fixes the blog folder, keep it, and keep posts directly under it.

Moving the store to its own domain

  • Every SEO setting moves with the store: one-to-one 301s from every old product, collection, post and category URL to its new address, plus canonicals, hreflang, sitemaps, structured data and internal links, all updated the same day.
  • Verify the new domain in Search Console, submit its sitemap, and use the change-of-address tool where the old domain is verified.
  • Check a sample of old URLs for a single 301 hop to a 200 page after the move, and watch the indexing reports for a month.

Store rules elsewhere in the series

  • Product prices come from the catalogue, live, never typed (chapters 3 and 10).
  • Product facts come from the product data and the supplier's documents (chapter 6).
  • Product images come from the catalogue, plus photos in use (chapter 7).
  • Product and Offer markup stays on product pages (chapter 8).
  • Reviews, ratings, sales counts and purchase notices show only real buyers' data, under the platform's rules.
  • Success is orders and revenue from sessions that included a post (chapter 13).

Cadence

  • One post a week for a store. That is 4 posts a month. Start with five posts, then the weekly rhythm, with seasonal and launch dates setting the order.
Grid of four business types and the next step their blog posts lead to: a product card, a call, a trial or demo, and a subscription.
The method is the same for every business; the next step at the end of the post changes with what you sell.
Embed this image
<a href="https://rend.ee/en/blog/seo-blog-guide/small-business-blogging#fig-business-types"><img src="https://rend.ee/images/guides/seo-blog/en/blog-next-step-by-business-type.webp" alt="Grid of four business types and the next step their blog posts lead to: a product card, a call, a trial or demo, and a subscription." width="1600" height="873" style="max-width:100%;height:auto"></a>

Local service business

A local service business sells a job in a place, so its posts prove local knowledge and end in a call.

  • The topic is your trade in your area (chapter 2), with area pages only for areas you really serve, and no doorway pages (chapter 6).
  • Describe your own area from what you know and can source: the housing, the heating, the water, the weather (chapter 3).
  • Prices are your own, from your price list; a market average appears only in a post about market prices, labelled as one (chapter 3).
  • Every service topic carries a cost breakdown, a cost per unit, the response time, and a "how long does it take" section with the real time breakdown for that job (chapters 3 and 4).
  • Demand for hyper-local terms: trust the live results and the map pack, and Search Console once the page is live. Don't bolt the city name onto the keyphrase by default (chapter 3).
  • One canonical name, address and phone across the site, the Google Business Profile and directories, with an email address on your own domain (chapter 3).
  • The homepage carries Organization plus the trade type, and every service page one Service node (chapter 8).
  • Discovery stories every 3 months show what you found inside a real job, and how the local housing stock or climate contributed (chapter 2).
  • How-to guides for jobs that need a professional end with "Want us to take care of that for you? Call [phone]." (chapter 1).
  • On phones, a large click-to-call button and a sticky call or quote bar (chapter 1).
  • Claims fit the trade: a non-emergency service never says "24/7" (chapter 3).
  • Seasonal demand seeds the calendar: frost weeks, the start of the heating season, spring roofing (chapter 13).

Software or B2B company

A software or B2B company sells to a buyer who researches for weeks with colleagues, so its posts answer each question in that research and end in a trial or a sales conversation.

  • The pillar is the page for the job your product does; posts cover the problems behind that job, comparisons, integrations and how-tos (chapter 2).
  • Comparison dimensions are the buyer's: price per seat or per month, setup time, integrations, who owns the data, support and contract length (chapter 2).
  • "[Tool] alternatives" and "[tool A] vs [tool B]" searches belong to posts; "[product] pricing" belongs to the product site (chapter 3).
  • Competitor prices come from their public pricing pages, normalised to the same billing period and seat count, and dated (chapter 3).
  • Product capabilities come from the product and its documentation, and security or compliance certifications are stated only when the report or certificate exists (chapter 6).
  • Images are real interface screenshots, cropped to what the text discusses, with customer data replaced (chapter 7).
  • Describe the product fully, by what it does for the buyer (chapter 1).
  • The soft call to action is a trial, a template or a short demo; the direct one is a sales call (chapter 1).
  • Success is trials, demo requests and pipeline from sessions that included a post (chapter 13).

Publisher

A publisher's posts are the product, so the measure is readers who return and subscribe.

  • Each subject hub is a pillar, and every article on the subject links to it (chapter 2).
  • Bylines carry the weight. Authors, editors and fact-checkers have bio pages with Person markup, and author pages list each person's articles (chapters 4 and 8).
  • The statistics page and original research are the linkable assets other sites cite (chapter 6).
  • The update window matters most here: every article is refreshed between its 5th and 12th month (chapter 13).
  • The call to action is a newsletter or subscription sign-up, with the email entry on its own page (chapter 1).
  • Success is returning readers, sign-ups and subscriptions (chapter 13).

Get Free SEO AuditFree audit

  • Andres Lepik, co-founder and head of growth at REND, with a short beard, smiling in a black REND cap and T-shirt against a light grey backgroundEdited by Andres LepikCo-founder & Head of Growth
  • Siim Saar, head of SEO at REND, with stubble, in a black REND cap and T-shirt against a light grey backgroundFact-checked by Siim SaarHead of SEO
Rasmus Kivi, co-founder and CEO of REND, smiling in a black REND cap and T-shirt against a light grey background

Post by Rasmus Kivi

Co-founder & CEO

Co-founded REND and still reads every client's monthly report himself before it goes out.