TL;DR: automate the brief, the first draft, the formatting and the publishing. Never automate the approval. A basic pipeline is $2,000-3,500 and five to seven days. The failure mode is not bad writing, it is publishing at a volume nobody is editing.
Content automation earned its reputation honestly, because most implementations are press generate and publish. The output is recognisably machine-made, readers notice, and the brand pays for it in a currency that is slow to earn back.
The version that works divides the labour differently: automation does the repetitive parts, people keep strategy, editing and the decision to publish. Done that way you get several times the output at the same quality bar, which is a real business result rather than a volume metric.
What Google's policy actually targets
Worth being precise, because the fear here is usually aimed at the wrong thing. The rule is about scaled content abuse: producing many pages primarily to manipulate rankings rather than to help anyone. Automation is not the trigger; purpose is. The October 2025 spam update went specifically after thin machine-written pages made to carry links.
Which means an automated pipeline producing genuinely useful pieces that someone edits and stands behind is not what is being penalised. A pipeline producing forty pages a month that nobody reads before publishing is, whoever wrote them. The line is editorial responsibility, and it is a line you can actually hold.
The pipeline, and which stages are machine work
Five stages: brief, draft, edit, format, publish. Automate the first, second, fourth and fifth. The third is the product.
The brief decides everything downstream
Weak output almost always traces to a weak brief, not to the model. Anybody who has handed a vague brief to a junior writer knows this already; nothing changed except the speed of the disappointment.
What a brief has to carry:
The query and what the person searching actually wants
What the top competing pieces already cover, so you can stop repeating it
Your angle: the thing you know that they do not, which is usually the whole reason to publish
Specific facts, numbers and examples to use, supplied rather than invented
Voice constraints, and the list of things you never say
An explicit instruction: where the brief provides no fact, say so rather than filling the gap
That last line is the single highest-value sentence in the whole system. A model asked to write about something it has not been given will produce something plausible, and plausible-and-wrong is the failure that costs you a reader permanently.
Voice is calibrated, not described
Telling a model to write in a friendly professional tone produces exactly what everyone else gets from that instruction. Feeding it five to ten of your genuinely good pieces and having it extract the actual patterns - sentence length, vocabulary, constructions you avoid, what you always do - produces something recognisable.
Then keep a banned list and grow it every time something slips through. Every generation failure you catch should become a permanent rule in the prompt and a check in the validator, not a note in somebody's head. That is the difference between a pipeline that improves and one that produces the same three tics forever.
The gate that cannot be removed
A draft lands wherever the editor already works, flagged with a checklist generated from the brief: these are the five things to verify in this piece. The editor spends twenty or thirty minutes refining rather than two hours writing. Approval is one action, and it triggers publishing.
The temptation, always, is to remove this step once the drafts get good. Do not. It is the only thing separating your pipeline from the thing search engines are actively filtering, and it is the only point where a person is accountable for what goes out under your name. When someone proposes dropping it, they are proposing you publish unread.
A useful signal: track how much each draft gets edited. If edits trend to zero, the briefs are good. If edits stay heavy on a category, the brief for that category is wrong, and fixing it is cheaper than editing forever.
What we automated for a fashion client
Persij needed product descriptions for 200+ items a season plus ongoing social. The pipeline takes product attributes, generates a description, bullets and three social variants, and puts them in front of a human in batch, where the review is seconds per item rather than minutes. Approved content publishes and schedules itself. A week of copywriting became about two days of review.
Note the shape of that win. The volume was already required and already being produced; what changed is what a person spends their attention on. That is the honest version of content automation, and it is a much easier case to make internally than pretending you now need ten times the content.
What to keep human, permanently
Some categories do not belong in the pipeline at all.
Anything where being wrong has consequences: legal, medical, financial, compliance
Original opinion and anything that stakes out a position, because it has to be someone's actual position
Customer stories and case studies, which depend on facts only the client can confirm
Crisis and apology, which should never be drafted by a system
Anything making a claim about your own results
Cost and what it replaces
A basic pipeline from topic to draft to review to publish: five to seven days, $2,000-3,500. A fuller version with multi-channel formatting, search research and performance tracking runs to around $4,500. Against $3,000-6,000 a month in freelance or agency production, it pays back quickly, and the more durable gain is that output stops depending on whether one person had a good week.
Want to see the shape of this for your content? The audit at 2pizza.team/audit takes two minutes, no call. If your volume is low enough that a freelancer is the better answer, it will say so.
Originally published at 2pizza.team. We build AI and automation systems for small teams - fixed price, two to six weeks. See the work.
Top comments (0)