The blog still needs an owner. It no longer needs a writer.

Every company that buys an automated blog asks the same question somewhere around week three: who is actually responsible for this thing now? The honest answer is that automation deletes one job and exposes another. The writing disappears. The accountability does not, and it lands on a different person than most companies expect.

The job that disappears is production, not judgment

Strip a company blog down and you find two separate jobs wearing one title. The first is production: research, outline, draft, edit, format, schedule, post. The second is judgment — deciding what the company is willing to say in public with its name attached.

Production is what everyone means by "blogging", and it is the part an engine takes over completely. Judgment is the part nobody bothers to name, because while one person did both, the second job hid inside the first. The moment production leaves, judgment stands alone and looks, for the first time, like a job.

That is why an automation project can stall in month two while posts keep appearing on schedule. Nothing broke in the pipeline. The company simply discovered it had never assigned the second job to anyone.

An owner needs standing, not craft

The instinct is to hand the blog to whoever wrote it before, or to whoever has the most spare capacity this quarter. Both are wrong, and wrong for the same reason.

The scarce input was never writing hours. It was the authority to commit the company to a claim. When a draft says onboarding takes two weeks, someone has to be able to approve that sentence without asking three colleagues first. When a post takes a position on a competitor's pricing model, someone has to own the consequence of being wrong about it in public.

A capable junior marketer can write beautifully and still be unable to answer either question. They will do the sensible thing and escalate, and the escalation is where the week goes. The cost of approval was never the reading time; it is the latency between a finished draft and a decision. Give the blog to someone whose yes is final inside their remit, even if they have not written anything since university.

Google makes you answer "who" in public. The internal answer is harder.

Google's guidance on creating helpful, reliable, people-first content asks you to evaluate a page in terms of Who, How and Why, and it is direct about the first: it asks whether it is self-evident to visitors who authored your content, and strongly encourages accurate authorship information where readers would expect it. When Google set out its position on AI-generated content in February 2023, it pointed creators at that same framework rather than at a prohibition.

So the public answer is a byline, and your posts should carry one. But a byline is a name on a page. It is not the same thing as knowing internally whose judgment the page represents, and the gap between those two is where an automated blog quietly goes wrong.

This is the same distinction we keep coming back to: machine authorship is not what Google penalises. Pages nobody needed and nobody stood behind are.

The engine will restate a claim that stopped being true

Here is the part we would rather not advertise. An engine that has learned your voice and your subject matter has no way of knowing that your pricing changed on Tuesday, that the integration it keeps citing was deprecated in the spring, or that the customer in your best case study has since churned. It will write the outdated fact fluently and with complete confidence, because fluency is not knowledge of your business.

Nothing in the pipeline catches this. The draft reads well, the structure is right, the register is yours, and the sentence is false. Only a person holding a current picture of the company can see it, and they can see it in the two seconds it takes to read the line.

That is the strongest argument for seniority in the owner's seat, and it is an argument against us as much as for us. If the person approving posts does not know what the company currently claims, sells and promises, the archive drifts away from the truth at exactly the rate it publishes.

What this changes

Name the owner in the brief, not on the calendar. The calendar is the engine's problem now. The brief is where the company's positions live, and the person who holds those positions is the one who should be approving what gets said in public.

In practice that means one person with commercial standing rather than a rota, a fixed short window each day rather than a queue they visit when free, and a byline that reflects a real human relationship to the words. If you cannot name that person today, you do not have a staffing gap. You have an unassigned job that stayed invisible for years because somebody was too busy writing to notice it.