Docket / Fix it / Placeholder text

Mentioning filler is not shipping filler

An audit reports that unfinished content is live and indexable on your site, and quotes the evidence. You open the page. It is finished, it has been finished for years, and the words it was flagged for are doing an ordinary job in an ordinary sentence.

Placeholder detection is a keyword search with a very high severity attached, and the two ways it goes wrong are both instructive — because the fix, twice, was to stop asking what the page was about and start asking what the text looked like.

Under construction, about buildings

A homelessness charity publishes a chapter of its housing-policy plan. Somewhere in it is a sentence about how many homes are under construction and how many have planning permission. The audit reported, at high severity, that unfinished content was live and indexable, and quoted that sentence back as its evidence.

The obvious guard fails here. A check can look at the words around a marker to see whether the page is discussing placeholder text rather than containing it — but this page is not discussing placeholder text. It is discussing buildings. There is no cue to find, because the phrase is being used for its ordinary meaning.

So the guard that worked was length. A holding page is short — that is what the marker is for, a stub somebody left behind. A long finished document that happens to contain the phrase keeps its finding only if something nearby says this page is the unfinished thing: check back soon, this section is coming, that shape of sentence.

The alternative was a list of nouns to exclude — buildings, roads, railways — and that list never ends. When the exclusions are open-ended, you are using the wrong property.

Lorem ipsum, named rather than used

A documentation wiki was flagged twice on one site, both times at high severity, both times citing the same famous two words.

Neither page was unfinished. One was a long discussion of internationalisation whose author used a namespaced filler-template name as a worked example of how namespaced template names look. The other was a help page listing that template among the templates the wiki has. Any wiki, CMS or design system that ships a filler template names it somewhere — usually in its own documentation, which is exactly the kind of page nobody wants flagged.

Again the discussion guard was useless: the words around those mentions are about namespaces and template inventories, not about filler.

The tell turned out to be something else entirely. The Latin never continues. Real leftover filler is a passage — it runs on into the rest of the sentence and the paragraph after it. A mention is two words and stops. Nobody's forgotten placeholder ends after the opening phrase, and nobody naming it in passing carries on into the rest of the Latin.

The pattern worth taking away

Both repairs replaced a question about meaning with a question about shape:

Shape is cheap to measure, hard to argue with, and does not need a list of every innocent context a phrase can appear in. Whenever you see a keyword-driven finding that keeps needing new exceptions, the useful question is not which word to remove from the list — it is what the real thing looks like that a mention of it does not.

Reading this on your own report

When the finding is real, and it is worth a lot

Keep the severity in view: this one deserves its rating, because live placeholder content is among the most damaging things a site can publish without noticing. It is usually:

The fixes that make it worse

How to trigger this on any site

Write an article about placeholder text. This one would have matched before the guards existed, which is a fair description of the whole category: a keyword check cannot distinguish writing about a thing from doing it, and only the shape of the text can.

Where this sits in an audit

The registered check is content.placeholder, which covers placeholder content in the content quality area. For the same failure in a different lane — a phrase that is a signal in one context and ordinary English in another — see why an audit finds reviews you do not have →. For why a finding that keeps needing exceptions should be gated rather than caveated, see a caveat is not a gate →.

Common questions

Why does my audit say a finished page is unfinished?

Because it matched a phrase such as lorem ipsum or under construction. Both appear in ordinary writing — one in documentation about templates, the other in anything about building work.

How can a tool tell filler from a mention of filler?

By shape rather than topic. Real filler sits on short pages and runs on as a passage; a mention is a phrase on a long page that stops after the opening words.

Should I rewrite a page to avoid the trigger phrase?

No. If the page is finished and the phrase is doing an ordinary job, the finding is wrong. Editing real prose around a keyword list is letting the list write your content.

Is placeholder content actually damaging?

Yes, when it is real. A stub still linked from a menu, or a template shipped with its example text intact, tells every visitor and every search engine that the page is not finished.

My design system documents a filler template. Will that be flagged?

It can be, and it should not be. Documenting a template that exists is correct; a check that flags it is matching the name rather than the content.