Kompozy sends your prohibited keywords to the model as a rule and does not scan output for them. How the rule works, what it misses, and how to build the list.
Published 2026-05-18 · Updated
Short answer
Kompozy does not run an output-time word filter. The Prohibited Keywords field in your prompting settings goes to the model with every text generation as words and phrases to avoid, next to built-in anti-AI-tell rules that ban words like delve and leverage. Nothing checks the finished post for those words, rejects it or regenerates it, so read outputs before they publish.
Key takeaways
Telling a model "never use the word leverage" works most of the time. The rest of the time is the whole brand-safety problem: the post that slips a banned phrase through is the one your audience reads, and on autopilot nobody reads it first.
An earlier version of this page described an output-time regex gate that rejected and regenerated any post containing a banned word. Kompozy does not have that gate. Your prohibited keywords reach the model as an instruction, and nothing scans the result. This page covers how the instruction works, why instructions slip, how to write a list the model follows more often, and where you still need to look yourself.
The intuitive fix for AI tells is to list your banned words in the generation prompt and trust the model to obey. It mostly works, which is exactly what makes it dangerous — "mostly" is not a standard you can ship autonomous content against. Three structural forces cause base models to violate prompt-level banned-word instructions, and none of them are fixable by writing the instruction more forcefully:
An output check gets around all three because it reads the finished text instead of trusting the model. Kompozy does not run one for prohibited keywords, so these forces apply to every post it writes. That is the reason to keep reading outputs, or to turn on Auto-Publish only in workspaces whose output you have watched for a while.
Prompting settings have a Prohibited Keywords field next to the Persona Brief. Here is what happens to it:
An admin compliance matrix decides whether each format gets the Voice Profile and anti-AI-tell blocks. Both are on for every format by default, for first generation and for regeneration.
Persona video scripts get one output-side check. Persona Short and Persona Frames run a critic pass that scores the script on AI tells, hook, pace and specificity, and swaps in a revision when any score is under 6 of 10. The critic looks for tells like stub sentences, meta-labels and anonymous-expert anchors. It does not look for your prohibited keywords.
The list lives in the Prohibited Keywords field and applies to every text format generated for that profile. The built-in anti-AI-tell rules already cover the most common AI vocabulary, so use your list for what those rules do not know about. Three kinds of phrase belong there:
| List category | Where it comes from | Example entries | How it changes over time |
|---|---|---|---|
| Extra AI tells | Phrases you keep cutting that the built-in rules do not name | game-changer, at the end of the day, here's the kicker | Grows as you spot new tics in your outputs |
| Industry cliches | Your field's overused jargon | motivated seller (RE), synergize (SaaS), mindset shift (coaching) | Revised most often, since field cliches age fastest |
| Brand-specific bans | Your workspace only | competitor names, regulated phrases, internal jargon, legal-flagged claims | Grows as legal and brand decisions pile up |
Because the list is an instruction and not a filter, the entries that matter most, like competitor names and claims you cannot legally make, also need a human check. A rule the model follows on most outputs is not enough for a claim that can get you in trouble once.
A starter list of your main industry cliches and brand bans is enough to begin with. It grows from the editing you do during the manual ramp, while you still approve every output.
Without a filter, nothing does word-boundary matching for you. The model reads your list as language, so plain, specific entries work best:
Kompozy does not regenerate a post because it found a banned word, so the steering has to live in the original prompt. Pair each kind of ban with a direction in the Persona Brief:
“Avoid abstract verbs like leverage, unlock and elevate. Say what the thing does in plain words, with a concrete example from the source.”
Stripping words with no direction is what makes output sound stilted. Give the model a target and the result reads cleaner instead of emptier. If a post still comes out wrong, regenerate it from the pipeline; the new version is written under the same rules.
The universal AI-tells library is the same for everyone, but the industry layer is where most workspaces win or lose on voice. The cliches that mark content as generic are field-specific, and a model trained on the internet will reach for your industry's most overused phrases unless you ban them explicitly. Starting points by vertical — extend each with the phrases you personally keep cutting:
Two cautions on the industry layer. First, some of these phrases are only bad when overused — "passive income" is a legitimate real-estate term and a cliche when it shows up in every post. Ban the ones you are tired of seeing, not the entire vocabulary of your field. Second, the industry list is the part you should expect to revise most often, because field cliches rotate; the phrase everyone overused last year reads as dated this year, and a fresh AI tell takes its place. The monthly tuning loop is where that revision happens.
What the current setup does:
What it cannot catch:
If a phrase must never appear, a word list in the prompt is not enough. Keep Auto-Publish Generated off for that workspace, or read scheduled posts before their slot comes up.
The list needs the most work early on, while you are still reviewing every output. Once you approve most posts untouched, it has done most of its job.
For the full map of what Kompozy checks and where, see quality gates. For building the list while you still approve every output, see the manual-vs-autopilot ramp. For how one source fans out across platforms, see content repurposing. Autopilot is included on Kompozy's Pro, Agency, and Enterprise plans; see pricing.
A Persona Tweet generated in the Kompozy workspace: short copy in a brand voice, the kind of output a banned-word list is checked against.

Best for:
Not ideal for:
No. Your prohibited keywords go to the model as an instruction on every text generation. Kompozy does not check the finished post for them, and a post that contains one is not rejected or regenerated.
In prompting settings, in the Prohibited Keywords field next to your Persona Brief. They reach the model in the Voice Profile section of the prompt.
Yes. A built-in anti-AI-tell block goes out with every text format by default and bans words like delve, leverage and unlock. Like your list, it is an instruction, not a filter.
Read posts before they publish. Leave auto-publish off for that workspace and approve rows in the pipeline, because a prompt rule alone cannot guarantee it.
It can, if you strip words without a direction. Pair bans with a Persona Brief line that says what to do instead, and keep the list to phrases you actually see.
Review recent outputs, add the phrases you keep cutting by hand, reword entries the model ignores, and drop entries that no longer appear.
We checked every product claim on this page against Kompozy's generation, autopilot and publishing code on 2026-10-23, and plan details against kompozy.io/pricing. The earlier description of a regex gate with rejection and regeneration was removed because the code has no such gate; the page now covers how prohibited keywords reach the model.
Sources
← Back to Autonomous Content Creation overview · Get started →