Lorem ipsum in production: find and fix it

What it means

The page body contains placeholder text — "lorem ipsum", "dolor sit amet", or a recognisable variant — that was never replaced before the page was published. Template content reached a live, indexable URL: a QA failure. The page has no real informational value and no search intent it can satisfy.

Why it matters

Google evaluates pages on whether they serve users well, and placeholder text is the clearest possible failure on that measure. A page containing lorem ipsum is classified as thin content, and thin content can drag down the perceived quality of the whole domain, not just the individual URL. It also signals that your publication process has no content-verification step. If the page carries a default index directive and sits in your sitemap, you are actively submitting thin content to Google's index.

How to fix it

1. Add <meta name="robots" content="noindex, follow"> immediately and remove the URL from your XML sitemap to stop it being indexed while incomplete.
2. Then either complete the page with real content and restore the index directive, or delete the page and redirect its URL to the nearest relevant parent.
3. Do not leave pages permanently noindexed as a workaround — noindex is a corrective measure, not a content strategy.
4. Add a CI check that scans for lorem-ipsum strings before deployment to prevent recurrence.

When it's not a problem

Pages whose subject is placeholder text itself — typography tutorials, dummy-text generators, design-system documentation showing sample content — are legitimate exceptions. A style-guide page that shows lorem ipsum inside a UI mockup is expected, not a defect.

How common is it?

934 audited sites in our corpus currently show this issue. The breakdowns below show which platforms, gatekeepers, verticals and countries are most exposed.