The content do-no-harm gate

Before I publish anything, I ask one question: will this help the site, or could it hurt it? The content do-no-harm gate answers that with a clear verdict and the cheapest ways to make the page stronger.

It works on anything, a live page or a draft before it goes out. And it does not grade from scratch. It composes the scorers I already trust, so the verdict is consistent with how the rest of the platform measures quality.

The gate exists to stop self-inflicted damage. Most SEO harm is not from competitors. It is from publishing a page that drags the site down.

Every piece of content gets one of three verdicts. The gate is not a score out of a hundred. It is a decision.

The gate is a composer, not a new scorer. It pulls the signals that already exist and turns them into one verdict. Building a fresh grader would just add another thing to keep in sync.

• The SEO composite, including generative-engine visibility, for how the page performs in search.
• The answer-engine readiness audit, for whether answer engines can extract and cite it.
• The mechanical quality score, for structure, depth, and originality.
• A semantic verdict, for whether the writing actually reads as useful.

Compose the scorers you already trust. Do not re-model quality in a new place, or you will maintain two definitions of good.

Block is not a low score. It fires on a specific, nameable harm signal, so it is never noise.

• A quality-floor breach that would send the page to noindex anyway.
• A semantic verdict of unpublish or rewrite, not just a weak grade.
• A page that is SEO-harmful and carries critical issues at the same time.

Block is operator-waivable. The gate gives an honest, grounded reason, and a human can override it with eyes open. It informs the decision. It does not take it away.

A pass-with-upgrades verdict is only useful if it tells you what to fix first. The gate ranks upgrades by leverage, cheapest and highest-impact at the top, so you spend effort where it moves the needle.

1. Open with the answer. Lead with the thing the reader came for, not a throat-clearing intro.
2. Turn headings into questions, so answer engines can match them to real queries.
3. Add scannable structure: lists and tables where prose is doing a list's job.
4. Raise concrete density: real numbers, real specifics, not vague claims.
5. Add the structured data the page is missing, like an FAQ block where it fits.

The temptation with any quality gate is to make it generous, so it stops blocking your own work. That is how a gate becomes theater.

The generative-visibility signal honestly excludes data that is stale or too thin to judge, rather than inventing a number to fill the slot. A gate that fakes a pass is worse than no gate. It gives you confidence in a page that will quietly hurt you.

1. Take the next thing you are about to publish and grade it before it goes out.
2. Fix the top one or two cheapest-first upgrades, not all of them.
3. If it blocks, read the reason. Fix the harm, or waive it with eyes open.
4. Wire the gate into the publish path, so nothing ships without clearing it.