When are custom thresholds worth it for No placeholder text left in?
When are custom thresholds warranted?
Override `prohibitedPhrases` when your own tooling has a house filler that the defaults do not know: a CMS that stamps `TK`, an agency that writes `TBD` or `[COPY HERE]`, an export pipeline that leaves `xxx` in unfilled fields. This is the highest-value override in the catalog, because your filler is the one most likely to actually reach production and the one least likely to be in a generic list. Add the strings your team really types, taken from a real unfinished page rather than from imagination.
When should you stay on Standard?
Stay on the defaults if you cannot name a house placeholder convention, because guessing produces false failures on ordinary words. Keep the Standard list on sites with heavy editorial copy, where short additions like `tbd` or `draft` appear inside legitimate sentences far more often than they appear as filler. If your problem is unmerged personalisation rather than filler prose, this is the wrong check to widen — that behaviour lives in the email placeholder check.
What do you trade away?
Every phrase you add trades quiet for coverage, and the loss is asymmetric: one false failure on a real article costs more trust than one caught placeholder buys. Short or common strings are the dangerous ones, because they match inside longer words and ordinary sentences. Note also that supplying your own list replaces the defaults rather than extending them, so include the original four alongside your additions unless you genuinely want them gone.
Community Standard vs org Custom
The Standard list is meant to be true for everyone, which is why it is limited to phrases that only ever appear in unfinished work. A Custom list encodes something only your organisation knows — the filler your own tools and agencies produce — and it should be maintained wherever your content conventions are documented, not rediscovered per audit. When you add a phrase, write down which pipeline produces it, so the entry can be retired when that pipeline is.
Worked override examples
An agency whose writers mark gaps with `TK` sets `prohibitedPhrases` to `["lorem", "ipsum", "fpo", "content goes here", "tk-copy", "[copy here]"]`, keeping the defaults and adding its own two. A product team whose CMS stamps `Untitled section` on new blocks adds that exact string, which catches an entire class of half-built pages the generic list misses. A design system site that publishes a typography specimen instead removes `lorem` and `ipsum` from its list for that one page's audit, keeping `fpo` and `content goes here` so the check still has teeth.
How does an agent call it with parameters?
{
"type": "url",
"url": "https://example.com",
"validations": [
{
"id": "no-lorem-ipsum",
"parameters": {
"prohibitedPhrases": [
"lorem",
"ipsum",
"fpo",
"content goes here"
]
}
}
]
}