Content and Blogging · Guide

How to Use AI to Help Write Blog Content Without Losing Quality

The position held across this site is that these tools support a writer rather than replace one. This is the page that argues it rather than asserting it, which means being specific about what they do well before being specific about where they fail.

Updated: August 2026
Written by: Andrew Odgers, Managing Director
Reading time: 10 minutes
The framing, stated precisely

The Objection Is Not That A Machine Was Involved

Published search policy does not distinguish between content written by a person and content produced by a machine. What it distinguishes is content made to serve a reader from content made to occupy a search result.

Why that framing is correct. It targets the actual problem.

The thing that fails is content produced without judgement or anything to add. That charge applies identically to a human writer producing the same empty page, which is a useful check on whether an objection is principled.

What follows from it. The tool is not the question.

Asking whether you may use these tools is the wrong question. The question is whether what gets published contains anything a reader could not have found elsewhere.

What this page will not do. Claim anything about detection.

Whether generated text can be identified is disputed and nothing supports a confident answer. Building a strategy on either assumption would be unwise.

The position, plainly

They Support A Writer Rather Than Replace One

This is the position held across our blogging, risky practices and advanced material. It is a judgement about where the value sits rather than a moral objection.

What the value in a post actually is. What only you know.

The specifics, the examples from work you have done, the figures, the exceptions and the position you have come to. Those are the reasons somebody stays on a page.

What these tools supply. Everything around that.

Structure, fluency, phrasing and pace. Genuinely useful and genuinely time-saving. None of it is the reason anybody reads.

Why replacement fails. The valuable part is missing.

A post produced entirely without input from the business contains only what was already publicly available, reassembled. It reads acceptably and gives nobody a reason to prefer it.

Why support works. Each side does what it can.

Your knowledge, shaped by something that is good at shaping. That is the same division the strategy page describes between a business and a writer.

Fair and specific

What They Are Genuinely Good At

Six things these tools do well. These are real and worth using. A page that pretended otherwise would deserve to be ignored.

Structuring an argument. Shape from material.

Given what you want to say, producing a sensible order to say it in. That is a mechanical task people find disproportionately hard.

Getting past a blank page. The commonest blocker.

Producing something to react to. Editing a bad draft is far easier than starting. Reacting is where most people work best.

Tidying something clumsy. Your words, better arranged.

Where you have written the substance roughly, smoothing it costs you nothing that mattered. This is the safest use there is.

Drafting variations. Titles and openings.

Producing several versions of a short piece of text so you can choose. Fast and genuinely useful, since the judgement stays yours.

Summarising research. Reading faster.

Condensing material you have gathered, provided you check it against the source rather than trusting the summary.

Generating the questions worth answering. Prompting you.

Producing candidate questions on a subject, which is useful as a memory aid alongside the real source, being questions your customers actually ask.

The limits that decide the outcome

What They Are Bad At, Which Matters Here

They do not know your business, your customers, your prices or what you actually think. A post about a trade written without any of that is exactly the generic content that fails.

Your business. How you work.

What you do and do not take on, the way you approach a job, what you have decided over years of doing it. None of that exists anywhere to be drawn on.

Your customers. Who actually asks.

The pattern of enquiries you receive, what people are worried about and the questions that come up repeatedly. This is the material that makes a post feel written for somebody.

Your prices. The most searched question.

What things cost in your area, at your standard, this year. Generated figures on this are guesses presented confidently, which is the worst combination.

What you actually think. The position.

Where you disagree with the common view, what you would advise against, which options you consider poor value. That is frequently the most useful thing in a post and it cannot be inferred.

Why the result is recognisable. Nothing to disagree with.

Content built without those is smooth, comprehensive and takes no position. Readers recognise it immediately, which is why it fails despite being competent.

Where the consequences are real

The Specific Risk In This Sector

Generated content about a regulated subject, a technical process or anything with a safety dimension can be fluent and wrong. The business publishing it carries the consequence.

Why fluent is the dangerous part. Errors that read well survive.

A clumsy mistake gets noticed. A confident, well phrased, incorrect statement passes review because nothing about it signals doubt. That is the specific hazard rather than inaccuracy in general.

Where it matters most. Several trades we work with.

Electrical and gas work, anything structural, medical and health subjects, legal and financial questions. In each, a wrong answer published under your name can reach somebody who acts on it.

What the business carries. All of it.

The consequence sits with whoever published, regardless of what produced the text. No tool shares the responsibility and none was ever going to.

What this requires. Review by somebody who knows.

Not proofreading. Somebody qualified in the subject reading for correctness. On these subjects that is not optional and it is the step most often skipped, because the text reads well.

The simplest safeguard. Do not generate what you can state.

Where the answer is something you know, supply it. The risk arrives when the tool is filling gaps in your knowledge rather than expressing it.

The central warning

Volume Is The Failure Mode

The temptation is to produce forty posts instead of eight. That is the mistake, being the one these tools make easy for the first time.

Why the temptation is strong. The constraint moved.

Producing content used to be limited by writing time, which kept plans small. Remove that limit and the obvious response is to make more, since nothing now prevents it.

What forty posts produce. An accumulation problem.

A large quantity of pages nobody needed, each adequate, none distinctive. Our risky practices material covers what accumulating that kind of content does to a site.

Why more is worse rather than neutral. Dilution.

Weak pages do not sit harmlessly beside good ones. They compete with them, spread the site's attention across subjects it cannot cover well and make the whole thing look thinner.

The correct use of the same capability. Eight better posts.

Use the time saved to research more thoroughly, add the specifics, check the facts and edit properly. The output is the same number of posts and each is worth more.

How this connects to the strategy. The list does not grow.

A finite list of questions worth answering does not become longer because production got cheaper. The questions are set by your customers rather than by your capacity.

The block that makes the page usable

What Should Always Be Yours

Five things that must come from the business regardless of what helped write the rest. These are what make a post worth reading and no tool supplies them.

The argument. What the post concludes.

The point you are making and why you hold it. A piece with no argument is a summary of a subject, which is what everybody else has published.

The examples. Things that happened.

Situations from actual work, described specifically. These are unavailable to anybody else and they are the most persuasive material a business owns.

The specifics. Numbers and details.

What things cost, how long they take, what usually goes wrong. Where a page is vague on these, readers assume the writer did not know.

The position. Including the unpopular parts.

What you would advise against and where you disagree with the standard advice. Taking a position is what distinguishes a page from every other page on the subject.

Anything a customer could check. Verifiable claims.

Statements somebody could test against reality. These have to be right, which means they have to come from somebody who knows.

The test. Remove them and see what remains.

If a post still stands with all five taken out, it did not contain anything and was not worth publishing.

Adding rather than tidying

Editing Generated Text Properly

Light editing leaves the flatness intact. The useful edit is adding what only the business knows, which is a different activity from improving the prose.

What light editing achieves. Very little.

Changing some phrasing, breaking up a paragraph, replacing a few words. The text reads slightly differently and contains exactly what it contained before.

What the useful edit looks like. Insertion.

Reading each section and asking what you know that is not there. Then adding it, in your own words, which is where a generic piece becomes yours.

The paragraph-level habit. One question.

Ask whether the paragraph contains anything a reader could not have found on any other page. If not, either add something or remove it.

The conclusion nobody likes. Some posts should not exist.

If there is nothing to add on a subject, that is a finding rather than an obstacle. The post should not be published, because the same page already exists elsewhere.

Where the structural work sits. Separately.

Structuring a post covers the editing that applies to anything, however it was drafted.

A judgement rather than a requirement

Disclose Or Not

This comes up constantly and the answer is a judgement about your audience rather than an obligation. What matters is whether the content is accurate and useful.

Why it is not a search question. Policy does not ask.

No published requirement obliges a business to state how its content was drafted. Whoever tells you otherwise is describing a preference as a rule.

Where disclosure helps. Audiences who care.

Some readers, particularly in creative or professional fields, treat this as relevant. Where your audience is one of those, saying so costs nothing and pre-empts a question.

The test that settles it. Would you be comfortable answering.

If asked directly how a post was produced, would the answer trouble you. If yes, the problem is the process rather than the disclosure.

What matters more than either. Whether it is any good.

A useful, accurate, specific post serves a reader whatever helped produce it. An empty one fails whether or not it is labelled. The full series is on the content and blogging guide.

Website migrations

Eight better
posts, not forty
more.

The time these tools save should go into research, specifics and editing rather than into producing more pages. Your list of questions worth answering is set by your customers rather than by how cheaply content can be made.

How we approach content:

Question gathering Topic selection Recorded interviews Writing and structure Subject review Internal linking Post maintenance Performance review

If there is nothing you can add to a subject, we will tell you the post should not exist.

The full guide series

Every guide.
One practice.

What a blog is for, how to choose subjects worth writing about, how to structure a post, how to promote it, how to measure it and how to keep it current.

Questions people ask

Using These Tools, Briefly

Will using AI hurt our rankings?
Published policy does not distinguish between content written by a person and content produced by a machine. What it distinguishes is content made to serve a reader from content made to occupy a search result. The thing that fails is content produced without judgement or anything to add. That charge applies identically to a human writer producing the same empty page.
What are these tools actually good for?
Structuring an argument once you know what you want to say, getting past a blank page, tidying something you wrote roughly, drafting variations of titles so you can choose, summarising research you gathered, then prompting questions worth answering. All real and worth using. The safest is smoothing your own rough writing, since nothing that mattered is lost.
Why does generated content read as generic?
Because it cannot know your business, your customers, your prices or what you think. It cannot know what you decline to take on, what people repeatedly worry about, what things cost at your standard in your area, else where you disagree with the common view. The result is smooth, comprehensive and takes no position, which readers recognise immediately.
Is there a particular risk in our trade?
If your subject is regulated, technical or has a safety dimension, yes. Generated content can be fluent and wrong. Fluent is the dangerous part: a clumsy mistake gets noticed while a confident, well phrased, incorrect statement passes review. The consequence sits with whoever published it. Review by somebody qualified in the subject is not optional there.
Can we now produce far more posts?
You can, which is the failure mode. Weak pages do not sit harmlessly beside good ones: they compete with them and make the site look thinner. Use the time saved to research more thoroughly, add specifics and edit properly. A finite list of questions worth answering does not get longer because production became cheaper.
Should we tell readers we used it?
That is a judgement about your audience rather than an obligation, since no published requirement obliges it. Some readers in creative or professional fields treat it as relevant. Most people wanting to know what a repair costs do not. The useful test is whether you would be comfortable answering if asked. If not, the problem is the process rather than the disclosure.