Prompt & template leaks: find unfinished content
Find unfilled placeholders like [insert keyword] and leftover prompt text published by mistake. Free scan for scaffolding across your pages.
What it means
The page contains unfilled template placeholders or prompt-echo text — for example [insert keyword], {{topic}}, or an opener like "Certainly, here's the rewritten version." These are scaffolding that was meant to be replaced or removed before publishing.
Why it matters
Published placeholders are a visible sign that content was generated from a template or prompt and shipped without being finished. Google's guidelines call out auto-generated pages with visible template fields as a Lowest-quality trait, and readers who see "[insert city]" immediately lose trust in the page.
How to fix it
- Search the page for bracketed slots ([insert …], {{ … }}) and fill them with the real value or delete them.
- Remove prompt-echo openers such as "Sure, here's the improved article" — start with the actual content.
- If you generate pages from a template, add a build check that fails when an unfilled placeholder reaches production.
Example
<p>Here is a 500-word blog post about [INSERT PRODUCT NAME] targeting the keyword [KEYWORD]:</p>
<p>Certainly! Below is the article you requested.</p><p>The Acme Trail 200 is a lightweight trail shoe built for technical terrain...</p>Unfilled placeholders and echoed prompt text are published-by-mistake scaffolding. Fill the template or remove the leftover text before publishing.
When it's not a problem
If the brackets or braces are intentional documentation of a template syntax (e.g. an article teaching Handlebars or Jinja), the tokens are the subject matter and are fine.
How Crawlinx detects it
During text analysis we match deterministic tells — unfilled placeholders like [insert ...] and echoed prompt phrases. When found, we report a representative snippet so you can locate it fast.
How common is it?
325 audited sites in our corpus currently show this issue. The breakdowns below show which platforms, gatekeepers, verticals and countries are most exposed.
FAQ
- Why is prompt-leak text a problem?
- It's an unambiguous sign the page shipped without human review. Readers see the scaffolding, and Google's quality raters treat leftover generation artifacts as a low-quality signal.
Audit your own site — free
157 checks, internal PageRank, render-diff. No signup, results in ~30s.