Content Error Detector

Catches embarrassing content mistakes on key pages before customers see them

  1. agent ›1/2 — 'Merino base layer' shows its intro paragraph twice since this morning's deploy. The repeat starts right after 'Machine washable at 30°'. It's your best-selling base layer: 2,300 sessions last week.
  2. agent ›2/2 — The 'Returns' page says 'You can return items within [X] days'.
  3. you ›The returns page barely gets traffic. Do we really need a ticket for that one?
  4. agent ›That's why it's second, not first. But it still had 410 sessions last week, and an unfilled return window is exactly what a hesitant buyer checks. It's a one-word fix — do both in the same ticket.

What it does

After each crawl, reads the AI descriptions of the pages that changed and of what changed on them, looking for the kind of mistake a deploy or a hurried edit leaves behind: placeholder text, spelling mistakes, broken sentences, missing content, text blocks repeated twice, or copy that makes no sense. These errors rarely show up in the numbers until a customer complains, so the agent looks at the text itself. Each alert names the page, quotes the error and says what kind it is, and the alerts are ordered by the page's revenue and traffic — the mistake on your best-selling product comes before the one on a page nobody visits.

Category
Action & Recommendation
Data sources
AI descriptions of what changed · Recent page changes · Page analytics · AI page descriptions
Schedule
Daily, after each crawl

An example insight.

What a result from Content Error Detector looks like. The numbers are an illustration, not a customer's.

Content Error Detector · Content Error · Example

Placeholder text 'Lorem ipsum' live on category page

The Women > New Arrivals category page contains placeholder text in the header description area. This was likely left from a staging deploy and is visible to all users.

Stop guessing why revenue dropped.

Book a demo and we'll show you what Historian finds on your own store.