Spot AI slop

AI Slop Detector: What It Can and Can't See on Your Site

What an AI slop detector can see in text, images, and pages, why its score can be wrong both ways, and how to read one before you fix anything.

An AI slop detector is a tool that scans text, an image, or a whole page for patterns that look machine-made or generic, then hands you a score. It's quick at spotting tells. What it can't tell you is whether your product is clear, true, and trusted, and its score can be wrong in both directions.

You built something with AI, and you'd like a quick, honest signal on how it looks. A detector can give you one, as long as you know what it actually looked at. This guide covers the kinds of detector, where each one goes wrong, and how to read a score. For the definition of the word itself, see what AI slop means.

What does an AI slop detector look at?

Say you paste your homepage copy into one tool, upload your hero image to another, and point a third at your URL. You may get three different answers, because there are 3 kinds of detector, and the difference is what you feed them.

  • Text detectors read words and estimate how likely it is that a machine wrote them.
  • Image detectors look at one picture and estimate whether a machine made it.
  • Page scanners load a page and judge the look and the wording together: the headline, the layout, the icons, the photos, and the footer.

Each one judges a single slice. A text detector never sees your layout. An image detector never sees your headline. A page scanner sees the page, but reading a page and using the product behind it are two different things. Tools also differ in how they arrive at a number, so read what a tool says its score means before you act on it.

What can a page scan see quickly?

Page scans are good at the tells that sit on the surface and look the same every time. They're fast, and they're consistent.

Anything you could spot by holding two pages side by side is fair game: the same photo style over and over, one icon pattern used for every feature, corners rounded differently from card to card, or a footer nobody updated. A scan can also check that the basics exist, like a way to contact you and the usual legal pages. Whether those pages exist is something a scan can see. Whether they're right for your business is something it can't, and none of this is legal advice.

What does a page scan miss?

There are 3 things any pattern check struggles with, whatever it's built on.

The first is who made the page and why. A scan sees a page, never the person behind it. A founder who chose a plain layout on purpose and a founder who never touched the defaults can end up with pages that look a lot alike.

The second is what your audience expects. A dense, plain page can be exactly right for a niche, and a polished one can be all wrong for it. Patterns don't know your buyers.

The third is change over time. A scan is one snapshot. It has no idea that last week's version was better, or that you fixed the headline an hour ago.

Why can a score be wrong in both directions?

Two terms help here. A false positive is when a check flags something that's actually fine. A false negative is when a check passes something that's actually poor.

Text detectors show both clearly. A 2023 research paper on arXiv tested several widely used GPT detectors on writing from native and non-native English speakers. In that paper, the detectors consistently labeled the non-native samples as AI-generated, while the native samples were identified accurately. The authors also report that simple prompting strategies could slip past the detectors, and they caution against using them in evaluative or educational settings.

Pages behave the same way. A scan can flag a clean template that a founder customized with real care (a false positive). It can also pass a polished page with a muddled offer (a false negative), because polish leaves marks a tool can count, and clarity has to be understood.

The W3C, the web standards body, makes a related point about accessibility tools in its evaluation tools overview. It says some checks can't be automated, that tools can give inaccurate results, and that what tools say shouldn't outrank the real experience of the people using a site. That page is about accessibility, but the habit travels well. Treat a score as a clue.

What is an AI generator fingerprint check?

Our homepage lists an "AI generator fingerprint check" among the things the $27 report includes, and its FAQ says the audit "checks for the fingerprints AI builders leave behind." You can see how a report words that finding in the sample report. This is what we do and don't claim for it.

  • What it does. It's one check inside the audit of your live public pages, looking for the marks AI builders leave behind. It's a read of how the page looks.
  • What it doesn't claim. It isn't proof of origin. The audit reads what a customer sees at your link, "not your code or which tool you used," so it can't tell you which tool made a site, or that AI made it at all.
  • Who it's for. The audit works on any public site, however it was made, including ones built with Lovable, Bolt, or Replit, and ones started from a template and edited with AI. We aren't affiliated with any of them.

A template edited by hand and a template edited with AI can look alike, so treat a fingerprint note as a hint, not proof. A hint is still useful, though. It points at the part of the page where a visitor may feel a sense of sameness, and you get to decide whether that's true.

What does our audit read that a text or image detector can't?

No person reads your app here. Is My App Slop uses AI to score what a customer sees against a fixed rubric, which is why your report comes back in minutes. Instead of one AI-or-not number, it scores six areas of what a customer sees, and the report lists anything it couldn't confirm under Not confirmed.

What does a pattern check flag on a language-tutor marketplace?

Take a marketplace where learners book 1-on-1 lessons with tutors (this one's made up). The founder runs a pattern scan, and then a real learner shows up.

What a pattern check flagsWhat a visitor notices
A generic photo of a smiling person with a laptop in the heroTutor cards show no teaching language or price until you open each profile
The same icon repeated on all 3 feature cardsThe Book a lesson button sits below the fold on a phone
A headline that could fit any app: "Unlock your language potential"Nothing says whether tutors are certified, or what a trial lesson costs
Card corners rounded differently from one card to the nextTime slots appear in the tutor's time zone with no label, so a learner books the wrong hour

The left column is worth fixing, and a scan can find it. The right column is where a learner decides to book or leave. Fix only the left column and you might end up with a better score and a page that still loses people.

How should you read a score?

As a summary of what the tool could observe, and nothing more. I'd ask 3 questions of any score:

  1. What did it look at? Words, a picture, a page, or a path through the product.
  2. What could it not see? A tool that doesn't say hasn't told you its limits.
  3. What do I do next? A single number with no reasons gives you nothing to fix.

Look at the parts, not the total. Our report gives each of the six areas its own score, a What works note, a Slop tells note, and ranked fixes, plus an overall Verdict. Work from the ranked fixes.

A good score means fewer obvious problems. A weak one means there's work to do, and it says nothing about whether the idea is bad. A score is a clue about the page, so treat the tells it finds as hints. Our guide on reading an audit report shows how to turn findings into a working list.

When is a detector enough?

Early on. When you've got a draft and a few first users on the way, a detector or a scan is a fair place to start. I wrote a line in Build the Damn Thing that fits here: as builders, don't fall into the trap of not trusting the easy. A napkin sketch or a simple landing page can get you real feedback, and a quick scan can be useful at this stage too. If you'd rather look at your own site first, our 20-minute self-check walks you through it by hand.

Go further when more is at stake. If real money moves, people create accounts, or you store personal details, bring in a specialist who can review those parts directly. A score tells you how the front door looks. It can't vouch for the locks.

Sources, both read 5 October 2026: the arXiv paper on GPT detectors and non-native English writers (first submitted 6 April 2023, last revised 10 July 2023) and the W3C's evaluation tools overview (updated 28 April 2020).