For local service businesses

Answer the question before they call.

People work out whether to trust a trade by reading about the job first. A blog on your own domain is where that happens — and it can keep happening without you writing a word on a Sunday.

Posts on your own domainNothing to installNo per-article quotes

What the posts answer.

Not company news nobody searches for. The questions a customer asks in the week before they pick up the phone — planned in advance, one per post.

The job, described properly
What the work involves, what it costs to get wrong, and how to tell when it is time to call somebody rather than watch another video about it.
The problem in plain words
The query someone types at the moment they realise they need help — written in the language they use, not the language of the trade.
The service, one page deeper
Posts link to the service pages and other pages you already publish, so the blog strengthens what you sell instead of competing with it.
The areas you cover
The plan is built around the pages your site already has, so the towns and services you list in your sitemap are respected rather than duplicated.
Images that do not look borrowed
A cover image and an in-article image are generated for every post, using your brand name and your colour — not a stock photo of a smiling stranger.
One post a week, on the date
An archive grows because something publishes every week, not because someone found a spare weekend in March.

The steady version of a blog.

Five steps, and only one of them is yours to repeat. The rest happens on the calendar, in the background, whether the week is busy or not.

  1. 01

    Scan the site

    The free scan reads your homepage, your headings and your sitemap, and shows the questions your site already answers plus the ones it misses.

  2. 02

    Connect the domain

    One DNS record and the blog answers on a domain you own — a subdomain or the address itself. Nothing to install on the site you already have.

  3. 03

    Drop the jobs you do not want

    Read the plan and discard any entry that would attract the work you would rather not take. That review is the only part of this that needs you.

  4. 04

    Posts publish themselves

    Written to the brief you kept, reviewed before publishing, then live with images, metadata and internal links on the date it was planned for.

  5. 05

    See the impressions

    Connect Search Console read-only and the site reports the clicks, impressions and average position its posts earn, per query.

What only you know.

A content plan cannot tell the difference between a job you want and one that eats a Saturday. You can, in about ten minutes — and that is exactly the review the plan is asking for.

The pieces that win estimates stay yours too: the job you are proud of, the mistake you learned from, the reason you charge what you charge. The pipeline handles the steady answering; the stories are still the owner’s job.

  1. What the work actually costs, and when a job is not worth taking
  2. Which services you want more of, and which you want fewer of
  3. The area you will travel to, and the one you will not
  4. The guarantees you can stand behind in writing
  5. The story behind an estimate that wins it

Six posts in the first month, or one every week.

Both start the same way. Only one of them still exists next year, and a reader can tell which is which.

The blog nobody keeps up

  • Six posts in the first month, then a year of nothing
  • An article about why customers should choose you, which nobody searches for
  • Photos taken on a phone on the way to the next job, or no photos at all
  • The same three sentences as every competitor in town
  • No numbers, because analytics were never set up

A blog with dates on it

  • One post a week, on the dates it was planned for
  • Queries taken from what people actually type when they need the service
  • A generated image for every post, in your colours
  • Internal links pointing at the services you want to sell more of
  • Clicks and impressions per site, read straight from Search Console

What a blog cannot do on its own

Reviews, the profile on the map, photos of real work, how quickly you answer the phone and what you charge still decide whether a customer gets in touch. A blog earns the visit — it does not replace the things people judge you on once they arrive.

And rankings, traffic and calls are not guaranteed — no honest supplier can promise them, and our terms say so. What you get is a growing set of pages on your own domain, publishing on a schedule, with honest reporting per query.

Costed per site, not per post.

€10 per website, per language, per month. The scan comes first and costs nothing — you see the queries your site is missing before you decide anything.

That is the whole invoice: no per-article rate, no minimum number of posts, no separate charge for images, metadata or hosting the blog. If your area is bilingual, each language is its own plan, its own calendar and its own line.

The blog itself sits on a domain you already own, so the archive belongs to the business — not to a directory or a platform you would have to leave behind if you stopped paying.

  1. The plan: queries, intents, outlines and dates
  2. Writing, with the review pass before publishing
  3. Cover and in-article images, in your brand colour
  4. Hosting the blog on your own domain
  5. Canonical URLs, sitemap and structured data
  6. Search Console reporting, per site

More on content

Questions local businesses ask.

Including whether a blog is worth it at all, and who writes the thing.

Do local service businesses actually need a blog?

If people search for what you do before they call, then the pages that answer those searches are how you get found. A blog is not the only way to publish such pages, but it is the cheapest recurring one: instead of a page written once and left alone, the site keeps adding answers to the questions your customers ask.

Do I have to write anything myself?

No. The plan and the articles are produced for you; your part is reading the plan and discarding entries that do not fit the business. It takes minutes a week, and it is the step that keeps a generic blog from turning into a generic business.

Will you publish to my Google Business Profile?

No — the posts live on your own domain, not on your profile. The profile is still where the map and the reviews live, and it is yours to run; the blog is what gives your website content to be found for, and the two do different jobs.

Can the posts mention my town?

The plan is built from what your site already publishes, including the URLs in your sitemap, so if you have a page per area, posts can link to those pages rather than invent their own geography. Where a post is aimed at a place, you will see it in the entry before anything is written — and you can discard it.

Is one post a week realistic for a business like mine?

That is the point of the dates: a weekly schedule is what a search engine reads as a business that is still trading and still publishing. If a week goes badly, move the date rather than skip it — the calendar holds the queue, and nothing is lost.

What does it cost?

€10 per website, per language, per month. No per-article quote, no minimum number of posts, no charge for the scan — which needs no account and gives you the queries your site is missing plus the first week of the plan. A second language, if you serve a market that searches in one, is a second line.

Will it bring more calls?

No ranking, traffic or call volume is guaranteed, and any supplier who promises one is guessing. What the blog does is give your own domain more pages answering more of the questions your customers ask, publishing on a schedule, with reporting that shows which queries the site is beginning to earn impressions for.

Start with your website

One post a week, without the Sunday.

Connect your domain and read the plan: the queries your site is missing, the first week of entries, and dates you can move before anything is written.

Free scan, no signupPosts on your own domain€10 / site / language / month