Lorem ipsum detection

Lorem ipsum never reaches your client.

Frank reads every block of visible text on every page in your sitemap, including CMS templates and pages nobody clicks through to, and flags Latin filler before launch.

Get startedSee pricing
  • Set up in 30 seconds
  • Unlimited scans
  • No code required

Updated

Why it slips through

Filler text hides where nobody looks.

Lorem ipsum rarely survives on the homepage. It survives on the pages nobody opens during review.

  1. 01

    CMS templates

    A blog or case study template with one forgotten field shows filler on every item that leaves it empty.

  2. 02

    Pages outside the nav

    Thank-you pages, legal pages and campaign landers rarely get clicked through before launch.

  3. 03

    Late additions

    A section added after the last review goes live with whatever was in it when the deadline hit.

How it works

It reads the words, not a phrase.

  1. 01Any word order

    Generated filler, caught in any order

    Frank doesn't search for the phrase “lorem ipsum”. It checks each block of text and flags it when at least 35% of the words come from a list of around 190 lorem ipsum words. Shuffled filler is caught, and real copy with the odd Latin word isn't.

    • Headings and paragraphs
    • Buttons, list items and other body text
    • Every page selected from your sitemap
  2. 02Highlighted on the page

    Straight to the problem

    Every finding is a major issue, shown with the text Frank found and highlighted on a screenshot of the page, so you can go straight to it.

    How scoring works

Frequently asked questions about lorem ipsum detection

  • No. Frank detects Latin dummy text only. English placeholders such as “TBC”, “Name Surname”, “Heading goes here” or “Coming soon” aren't flagged. When you spot one while reviewing a page, pin a marker on it so the right person fixes it.

  • Text under five words is skipped, so a two-word “Lorem ipsum” heading won't be flagged. Text is also judged piece by piece wherever the formatting changes, so a short bold or linked bit of filler inside a sentence can be missed.

  • No. Frank checks visible page text: headings, paragraphs, buttons, list items and other body text. It doesn't check alt text, page titles, meta descriptions, code blocks, or hidden text such as a closed menu or tab.

  • Every page you select from the project's sitemap, including CMS template pages and pages that aren't in the navigation.

  • Not at the moment. The word list is fixed.

Explore Frank

See what else Frank does for you.

  1. 01

    Accessibility checks

    Frank flags missing alt text and common accessibility issues on every page, from skipped heading levels to unlabelled form fields.

    Feature
  2. 02

    Broken link checking

    Frank tests every internal and external link on every page, follows redirects, and flags 404s, server errors and dead development links.

    Feature
  3. 03

    Figma design QA

    Map your Figma pages to your live site once, then review every page side by side with its approved design.

    Feature
  4. 04

    For Framer

    Automated QA for Framer sites: check every page and CMS page on your staging or preview URL before you publish to your domain.

    Solution
  5. 05

    For Webflow

    Automated QA for Webflow sites: check every page and CMS template on your webflow.io staging site before you connect the domain.

    Solution
  6. 06

    For WordPress

    Automated QA for WordPress sites: check every page on your staging site for lorem ipsum, broken links and accessibility before launch.

    Solution
  7. 07

    For agencies

    Consistent, automated QA across every project and every team member, with a scored record of every scan.

    Solution
  8. 08

    For freelancers

    A second pair of eyes for solo designers and developers: automated checks on every page, so you can hand over with confidence.

    Solution
  9. 09

    Frank vs BugHerd

    BugHerd collects visual feedback from clients and teams. Frank runs automated QA checks on every page. Here's how they compare.

    Comparison
  10. 10

    Frank vs Pixelay

    Pixelay overlays a Figma design on a live page inside Figma. Frank reviews every page against its design and runs automated QA checks too.

    Comparison
  11. 11

    Frank vs Sitepager

    Sitepager tracks what changes on a site between updates. Frank checks a build before launch and lines it up with the Figma design. Here's how they compare.

    Comparison
  12. 12

    Frank vs manual QA

    Manual QA is slow, inconsistent and easy to skip. Frank automates the repetitive half, so your team keeps the judgement calls.

    Comparison
  13. 13

    QA reports & scores

    Every page gets a score out of 100 and a red, amber or green status, with issues highlighted on a screenshot, every scan kept, and reports you can share with clients by link.

    Feature
  14. 14

    Team markers

    Pin issues straight onto a scanned page, comment, @mention a teammate and filter by priority, so nothing gets lost between review and fix.

    Feature

More on pre-launch QA

All articles

Find the filler before your client does.

Run your first scan in minutes. Every plan includes unlimited projects and unlimited scans.

Get startedSee pricing
  • Set up in 30 seconds
  • Unlimited scans
  • No code required