Automated blog posts provide a reliable rhythm at predictable cost and answer customer questions that no one in the business otherwise has time for. They work under four conditions: topics from real search queries, a briefing with the business's facts, approval by a human, and a connection that publishes without copy and paste. They cause harm when they are produced in bulk without any benefit to readers, which Google has classified as Scaled Content Abuse since March 2024.
Automated blog posts are texts that a system generates from search queries and the business's specifications, submits for approval, and publishes on the website once approved. The question every business owner asks is not "Can this be done?" but "Is it worth it, and where's the limit?". This page weighs up the benefits and risks, works out the costs and names the cases where automated posts do more harm than good.
What automated blog posts deliver
- Rhythm. The most common reason company blogs go quiet isn't a lack of knowledge, it's a lack of time. A system delivers a draft every Monday, whether the week is hectic or not.
- Topics from the market. Instead of guessing what interests customers, topics are based on what people in the region actually search for.
- Structure that Google can read. Subheadings, answer up front, FAQ section, internal links. These belong in every post and are easily forgotten when writing by hand.
- Predictable costs. A monthly amount instead of quotes per text.
What they don't deliver
They don't know your business. Every statement about services, prices, projects and region comes from your briefing or is guesswork. They don't replace a case study, an interview with the owner or photos from the job site. And they won't bring in enquiries if the website itself offers no way to get in touch.
Automated or manual: the comparison
| Criterion | Automated with approval | Written yourself |
|---|---|---|
| Time per post in the business | A few minutes for review and approval | Several hours including research and publishing |
| Rhythm | Fixed, regardless of workload | Fluctuates with order volume |
| Topic selection | From search queries | Out of thin air, often topics no one searches for |
| Technical depth | Only as good as the briefing | Only as good as the person writing |
| Source of error | Incomplete briefing | Lack of time, abandoned drafts |
| Personal touch | Needs to be added | Present from the start |
| Costs | Monthly amount | Working time that's then missing elsewhere |
The table shows why the decision is rarely a straight either or. The best approach is an automated draft that someone from the business enriches with a couple of sentences. For how this compares financially to an agency, see Blog system or content agency.
What automated posts cost
Example calculation, all assumptions marked: an owner writes a post themselves and needs three to four hours for it (assumption), at an internal hourly rate of CHF 80 (assumption) that's CHF 240 to 320 per post, or around CHF 1,000 to 1,400 per month on a weekly rhythm. A blog system like BlogPilot costs CHF 199 per month on the Starter plan for one post per week, and CHF 269 on the Business plan for three posts per week (excl. VAT, as of October 2026, details under Prices). On top of that there are the few minutes per week needed for approval. For an overview of the price ranges typically seen for software, agencies and in-house options, see What does an AI blog cost?
The sums tip the other way if approval is skipped. The posts may be cheap, but the damage from an incorrect price shown on the website costs more than a year's subscription.
Four quality conditions
- Topics from real search queries. Not from a keyword list, but from what people in the region actually type in.
- A briefing with the facts of the business. Form of address, region, services, non-services, taboo words. Without this briefing, the system produces correct but generic content.
- Approval by a human. Every post is read before it goes live. At least for the first few months.
- A connection without copy and paste. Posts appear directly in WordPress, Wix, Shopify or a hosted blog under your own domain. What can be automated here is shown on the Automate your blog page.
What Google says about it
In March 2024, Google added to its spam policies. Since then, mass-produced content that is mainly designed to influence rankings and offers readers little or no value counts as a violation, regardless of whether it comes from humans, machines or both. At the same time, Google has stated since February 2023 that using AI is not in itself a rule violation. So the line isn't drawn between human and machine, but between value and volume. Exactly where that line lies is explained on the Scaled Content Abuse page.
When automated blog posts do harm
- When they're published without approval and mention services or prices that aren't correct.
- When the volume exceeds the value: twenty posts a week for a business with five services.
- When every post has the same structure, the same stock phrases and not a single piece of information from the business.
- When the website has no way to make contact, no service pages and no up-to-date legal notice. Then even the best blog won't bring in enquiries.
- When the topic is legally or medically sensitive and no one with expert knowledge checks it.
What to do with this
Automated blog posts make sense for an SME when no one in the business has time to write, but someone has a few minutes a week to check. They don't make sense if the blog is meant to run without any checking, or if the website itself isn't yet ready to handle enquiries. Anyone who meets these four conditions gets a blog that answers a customer question week after week, at a cost below what their own time would be worth.
Frequently asked questions
Does Google detect automated blog posts and downrank them?
Google has publicly stated that it assesses content based on quality and usefulness, not on how it was produced. What gets penalised is mass-produced content with no value for readers, whether from a human or a machine. A weekly post with a genuine answer to a customer question doesn't fall into that category.
How many automated posts a week makes sense?
For most SMEs, one. For businesses with many services or several locations, two to three. What matters isn't the quantity, but whether each post answers its own distinct question. Seven posts a week only make sense if there are seven distinct questions that customers actually ask.
What happens to the posts if I cancel the service?
That depends on the connection. Posts written via an interface into WordPress, Wix or Shopify sit in your own system and stay there. For a hosted blog, you should clarify before signing the contract whether and how you can export the content.
Do I still need someone to write?
Not to write, but to check and add to the content. Someone in the business needs to invest a few minutes each week to confirm facts and contribute a project example. Without that person, you end up with correct but interchangeable text.