Use AI for writing, keep your readers' trust. How to avoid AI slop

You avoid AI slop by keeping real material and real people in charge of the writing, and letting AI help only with the drafting. That comes down to a handful of habits, in the order you'd use them: where the facts come from, how they're checked and credited, how the piece sounds, what you cut, and who signs it off. Each one closes a gap that generic, untrustworthy writing gets through.

The habits come from "Avoiding AI slop: how to use AI for writing without losing trust", which Hynca Media Desk published on 4 October 2026. It doesn't announce a change or a new policy. It sets out the practice the Desk is built on, and we've written it up here so you can apply it to your own site, whether you run one site or manage dozens for clients.

What AI slop looks like on a business site

The guidance defines slop as generic, padded writing that could be about anyone, often with invented facts and stock phrases. You've probably read some already. A news post opens with a sentence about how quickly things are changing and promises to explain what you need to know. Then it says very little, at length.

On a small business site, slop is the article that could sit on any competitor's site with the name swapped. On a member organisation's site, it's the update that mentions your sector but says nothing about the problems your members actually have. For an agency, it's the same post on several clients' sites with only the logo changed.

It has a recognisable shape. Phrases arrive ready-made. Claims are so broad that nobody can check them. The worst kind contains a fact that isn't true: a figure, a date or a detail the writing tool supplied because there was a gap to fill.

Why it costs more than it saves

Readers notice it.

A made-up fact is worse. Once it's published under your business's or organisation's name, it's your claim. If a customer acts on it, or a member repeats it, the mistake leads back to you. That's the damage to trust the guidance warns about.

For agencies, the damage lands on the client. The client's name is on the page, and the client's readers are the ones misled. The agency then has to explain how it happened, and every other piece it has written for that client starts to look doubtful too.

The guidance doesn't put a number on any of this, and we won't either. You don't need one to see the trade-off: time saved by skipping the facts gets spent later on corrections, apologies and lost readers.

Start from sources or a brief, never a bare topic

Every later step depends on this one.

If you ask a writing tool for "a post about changes affecting small firms", it has nothing to work from. It will produce something that sounds like an article. Where it doesn't know a detail, it may supply one. Invented facts come from that gap.

Give it something real instead. That can be a source, such as an official announcement or a published report, or your own brief setting out what you know and what you want to say. Then hold to the rule the guidance sets: facts come only from those. If a detail isn't in the source or the brief, it doesn't go in the piece.

A few habits make the rule easier to keep:

• Keep the source material and the brief with the draft, in the same folder or document, so whoever checks it can see both at once.
• Write the brief before you open the tool. Note the facts you have and the ones you don't. Knowing what's missing tells you where a guess might creep in.
• If you're an agency, keep a separate brief for each client. A shared brief is how the same article ends up on five sites.
• When the source leaves something out, leave it out too. A shorter piece with true facts serves your readers better than a longer one with guesses.

The guidance this article is based on is a fair example. It names no author, cites no studies and doesn't say which AI tools or detectors it has in mind. So this piece doesn't either.

Check every claim, then credit the source

Before anything is published, check the draft claim by claim against the facts you started from. Every figure, date and name should match the source or the brief, and so should every statement of what happened.

When a claim isn't supported, you have two options. You can narrow it to what the facts do say, or you can cut it. Never fill it in. Suppose the source says a scheme opens in spring and the draft gives a specific date. The draft is wrong, however plausible the date looks. Narrow it back to "in spring", and the piece is accurate again.

The simplest method is to read the draft with the source open beside it. Underline each factual claim, then find it in the source. If you can't find it, take it out. A short news piece is quick to check this way; a long guide takes more time. Either way, it's less work than a correction.

Then name the organisation the facts came from, and link to the original wherever there is one. Readers can see where each fact came from and check it for themselves. Credit also helps you later: when someone asks where a figure came from months after publication, the answer is already on the page.

Sound like you, and cut the tells

A piece can be accurate and still read like slop if it doesn't sound like anyone. So write in a real voice: yours, your organisation's or your client's.

Learn that voice from the person's or organisation's own writing. Past articles, newsletters and member updates show how they actually sound. You can see the words they use, how long their sentences run and how formal they are. A trade body writing to members might use "we" and refer to its own events; a local tradesperson might write short, direct sentences and never use jargon. Then keep learning from their edits. Each time someone changes a phrase, shortens an opening or removes a word they'd never use, you learn something about the voice.

Next, cut the tells. Once you know them, you'll spot them in your own drafts:

• Padding. Sentences that repeat the one before, or say something everyone already knows. If you delete a sentence and nothing is lost, it was padding.
• Throat-clearing openers. An opening paragraph that talks about the topic in general before getting to it. Start with what the reader came for.
• Hollow signposts. Phrases that announce a point instead of making it, or call something important without saying why.
• Paragraphs that are all the same length. Real writing varies. Some paragraphs need one sentence; some need five.

Cutting these makes a piece shorter. That's usually an improvement, and the reader gets to the facts sooner.

Why a person approves, and why humanizer tools miss the point

The guidance asks for a person to read and approve everything before it goes out. That person knows the business, the members or the client. They'll catch a claim the source supports but that would mislead your readers, or a sentence that's accurate but wrong in tone. A site that publishes without that judgement is relying on luck.

For an agency, it helps to agree in advance who that approver is for each client, and what they're expected to look at. Without a named person, approval becomes a quick glance from whoever happens to be free.

Some people tackle the problem from the other direction. They try to fool AI detectors, or run copy through "humanizer" tools that rewrite it until a detector stops flagging it. The guidance says you shouldn't do either. A piece can pass a detector and still contain an invented fact. It can pass and still sound like nobody. Your reader was never the detector.

Write for people instead, and be honest about how the work is done. If AI helps you draft, say so plainly when someone asks. Your readers need the facts to be real and the voice to be yours, with a named business or organisation standing behind every piece. Disguising the process does nothing for any of that.

How the Desk is built around this

Hynca Media Desk describes itself as built on four things: facts first, a claims check, your voice, and nothing published without a person's approval. Each piece starts from the source or your brief. It's checked against those facts before it reaches you, and it's written for your readers in the way you'd write to them. You read it, edit it and approve it; what goes on your site is your decision.

See what the Desk can write for your site in the features overview, or contact the Desk with a question about your own site.