Service Pages or Blog Posts? A Local Guide

Most local businesses are writing the wrong pages in the wrong order.

The Common Failure

A local business decides to take SEO seriously and starts a blog. Six months later there are eighteen posts, traffic is up slightly, and inquiries have not moved.

Meanwhile the site still has one Services page listing nine services in a bulleted list, so there is no page that properly answers any of the searches that lead to work.

This is the most common structural mistake we see. Blogging is visible and feels like progress. Service pages are boring and are where the money is.

Match The Page To The Intent

Every search sits somewhere on a line from learning to hiring, and the page type has to match.

Someone searching boiler replacement cost Bristol is close to hiring. They want a page about that service, in that place, with a price, a timeframe and a way to book. That is a service page.

Someone searching why is my radiator cold at the bottom is not hiring yet. They want an explanation. That is a blog post, and its job is to answer well, establish that you know what you are doing, and offer the relevant service at the end.

Getting this backwards is the failure. A blog post cannot rank for a hiring search, because it does not answer the question the searcher is asking. And a service page will not rank for a diagnostic question, because it is trying to sell rather than explain.

Build The Service Pages First

One page per thing you get hired to do, named the way customers name it.

The page needs: what the job involves, what it costs or the range and what moves it, how long it takes, what happens on the day, who does it and what they are qualified in, the areas you do it in, proof in the form of reviews or completed jobs, answers to the four questions people always ask, and a clear way to book.

Prices are the sticking point. Most local businesses refuse to publish them and then wonder why inquiries are unqualified. A range with the variables named is enough. It ranks better, because people search cost, it converts better, because uncertainty is the main objection, and it saves you quoting jobs that were never going to happen.

Do this for every service before writing a single blog post. If you have eight services, that is eight pages, and it is more valuable than fifty articles.

Then Blog, But Narrowly

Once the service pages exist, blogging has a job. It captures people earlier, it answers the questions that come up on the phone, and it gives the AI answer layer something specific to cite.

The posts worth writing are the ones a customer would search before hiring. Diagnostic questions, cost questions, comparison questions, timing and regulation questions. Local specifics where they exist, since building rules, water hardness, housing stock and permit requirements all vary by area and generic national advice cannot cover them.

The posts not worth writing are the ones every business writes. Seasonal listicles, industry news, company updates, anything you would not read yourself. They do not rank, and they add pages that dilute the site.

One useful post a month beats four filler ones, and it is also achievable, which four is not.

Link Them Together Properly

A blog post that ends without a route to the relevant service page has done half its job.

Link from each post to the service it relates to, using the service name as the link text. Link from service pages to the posts that answer the detailed questions, so a page can stay focused without being incomplete.

This is also how the pages help each other rank. Internal links pass signal, and the link text tells search engines what the destination is about. A site where the blog and the services are two disconnected islands is wasting most of what it has published.

How To Tell What Is Working

In Search Console, filter by page and look at the queries each one attracts. A service page working properly picks up hiring queries. A blog post working properly picks up question queries and passes people onward.

In Analytics, look at which pages precede an inquiry rather than which get the most visits. These are usually different lists, and the second one is the one to act on.

The pattern to watch for is a page accumulating impressions with almost no clicks over several months. That usually means it half matches a lot of searches and satisfies none, which is what generic content produces. Improve it or remove it.

Deciding what to write next from that data, rather than from a content calendar someone made in January, is most of the difference between a blog that produces work and one that produces posts. That reading is what askotter does month to month once a site is live: it watches which pages earn inquiries and which are going stale, and proposes what to write or fix next with the numbers attached, for a person to approve.