Spot AI slop

Is My Website AI Slop? A 20-Minute Self-Check for Builders

Not sure your site reads as AI slop? Run this 20-minute self-check, one question per area, then see how to write up your notes.

Is your website AI slop? It is if a first-time visitor can't tell what you do, can't tell your site apart from every other site, or can't finish the one thing you want them to do. The good news is you can test all 3 in 20 minutes with your live site and your phone, asking one question for each of the six areas our audit scores.

When you build with AI, the first draft often goes live before anyone has used it the way a visitor would. That includes you, and that's normal. You've seen it so many times inside the builder that your brain quietly fills in the gaps. This guide gives you a timed routine for looking at it fresh, plus a made-up example of what finished notes look like.

What are we checking for?

We're not checking whether AI touched your site. Whether you built in Lovable, Bolt, Replit, or something else, a visitor only cares about three things: is it clear, is it believable, and does it work? If you want the definition and history of the word first, start with what AI slop means.

So there's one question for each of the six areas our audit scores: Clarity and Promise, Craft and Design Integrity, Trust and Legitimacy, Flow and Usability, Mobile and Access, and Conversion and The Ask. You're doing the looking by hand, so write down what you actually see. What you meant to build doesn't count today.

This self-check is not a security review, a full accessibility audit, or proof that every part of your app works. A page that looks finished can still have problems behind a login or after payment. Keep anything outside the checks you actually completed under Not confirmed.

How do you set up the 20 minutes?

Give setup one minute.

  1. Open your live site at its public address. Skip the preview inside your builder.
  2. Use a private window, so you're logged out like a new visitor.
  3. Pull up the same address on your phone.
  4. Start a notes page with 3 headings: What works, Slop tells, Top fixes. Our report uses the same 3 for each area, and the example near the end shows them filled in.
  5. Set a timer for each check, and stop when it rings.

Does the first screen say what you do?

Give this one 3 minutes. It's Clarity and Promise. Look only at the first screen, then read your headline out loud and try to finish this sentence from it alone: "This is a _ for _ who want to ___." Then check that the rest of the page agrees with it.

Vague lines about unlocking possibilities fail because they'd fit any site on earth. A line passes when a visitor could repeat it back to you in one breath. If you can't finish the sentence, write the gap under Slop tells, and write the line you wish it said under Top fixes.

Does it look made for you, or made for everyone?

Give this one 4 minutes. It's Craft and Design Integrity. Scroll the whole page slowly and look for the spots where nobody made a choice:

  • Generic art or colored blocks where a real screenshot, product photo, or face should be.
  • The same style of icon parked beside every feature.
  • Rows of identical cards, with every section laid out the same way.
  • Buttons, corners, and fonts that change from one section to the next.
  • Text you could paste onto a competitor's site without changing a word.

Then ask yourself what on this page only you could say. If the honest answer is "nothing," that's the biggest item on your Slop tells list. One small extra while you're here: if an image carries meaning, like a chart or a product shot, it needs a text description, and a purely decorative one doesn't (W3C alt decision tree).

Does the site give a visitor a reason to trust it?

3 minutes, for Trust and Legitimacy. Sit in the seat of a cautious customer who's about to hand over money or personal details, and ask who's on the other side:

  • Is there a named person or business, and a way to reach them?
  • Does anything on the page suggest the site is still looked after, or does a date look frozen in time?
  • Do the privacy and terms pages open, and do they describe this product rather than a template?
  • Is there any leftover template text, like "Your Company Name" or "Lorem ipsum"?
  • Can you trace each testimonial to a real person and each number to a source?

Checking that your legal pages exist and match what you do is a good habit, but nothing here is legal advice. And a trust signal only counts when it's true. A counter or a testimonial belongs on the page only when the number or the person is real.

Does the main path work when something goes wrong?

4 minutes, for Flow and Usability. Pick the one thing a visitor is meant to do (sign up, book, buy, or send a message) and do it start to finish. Then break it on purpose.

  • Submit with a field left empty.
  • Type a bad email address.
  • Press back halfway through, then try again.
  • Click every menu and footer link.

Does each error tell you what to fix? Does the site confirm that it worked? Does the confirmation email actually arrive? If you submit a form, use a test email you control, label the entry "test," and stop before any real payment. Anything you couldn't check goes in your notes as unconfirmed. That's more honest than guessing. The full workflow is in our guide on how to test a vibe-coded app.

Can someone use it on a phone?

3 minutes, for Mobile and Access. Grab your phone and open the live site fresh, so any pop-ups or notices show up the way a new visitor would meet them. Check 4 things:

  1. On first load, can you spot the main button right away, with nothing sitting on top of it?
  2. Can you read the text without zooming?
  3. Does anything run off the side of the screen?
  4. Can you tap each menu item without hitting its neighbor?

Use a real phone for this, not a shrunken desktop window. Pop-ups, fixed bars, and chat widgets have a way of parking right on top of your button on a small screen.

Is it clear what you want visitors to do next?

2 minutes, for Conversion and The Ask. Find your main button and read only its label. Could someone who skipped the whole page tell you what happens when they click it? Is there one main action, or 5 competing for attention? Is the price, or the fact that it's free, visible before you ask for anything?

A label that names the action and the cost tells visitors what they're agreeing to. A vague one makes them guess, and guessing is a great reason to leave.

How do you tell if a website is AI generated, or just AI slop?

You can't reliably tell by eye. We can't either, and your visitors don't need to. Some AI-built sites are thoughtful, and some hand-built ones are as generic as a hotel lobby. A vague headline or a row of identical cards is a hint, not a verdict.

"AI generated" describes how a site was made. "Slop" describes whether anyone checked the result. So trade the big question for 3 smaller ones:

  1. Could the headline fit any site in your category?
  2. Can you name one choice on the page that someone made on purpose?
  3. Did anyone run the main path on a phone after the last change?

3 honest yeses is a good sign someone cared about the site, whatever tool built it. Any "no" goes on your Slop tells list.

If you want to see what these tells look like in the wild, read our AI slop examples guide first.

How do you write up your notes and decide what to fix first?

Mark each area Pass, Maybe, or Fail, with one line under each heading. Then pick your order. Start with whatever made you wince the most. A broken main path usually comes first, because nothing else matters if a visitor can't finish.

Say you built a resume-feedback app (another made-up one) and you've just finished your 20 minutes. Your notes might look like this.

Area (mark)What worksSlop tellsFix
Clarity and Promise (Maybe)Headline says "Feedback on your resume in minutes"Subheadline, "Unlock your career potential," fits any siteName who it is for
Craft and Design Integrity (Maybe)Real screenshot of a marked-up resumeSame rounded card and sparkle icon on all 3 featuresSwap icons for 3 real feedback snippets
Trust and Legitimacy (Maybe)Privacy page explains how long resumes are keptFooter year is old; "Join 10,000 job seekers" has no sourceRemove the count or source it
Flow and Usability (Fail)Upload to feedback works for a PDFA word-processor file shows only "Error"Say which file types are accepted
Mobile and Access (Pass)Text readable, nothing off screenNone noticedNone
Conversion and The Ask (Maybe)One main button, "Get my feedback"Price appears only after the uploadShow the price on the first screen

Under one last heading, Not confirmed, you'd add: "Feedback email: nothing arrived in 10 minutes, spam folder checked." You'd circle the upload error, since that's the one that made you wince, and put the fixes in order: file types first, then the price, then the subheadline. Aim for that shape, a short, ranked list. You're not rewriting the whole site today.

If you want to see how a finished report lays this out, the sample report uses fields like Verdict, What works, Slop tells, Top fixes, Where to start, Recorded evidence, and Not confirmed.

In the public sample report, the recorded main path ends at a Stripe checkout showing $27. The test stopped before entering payment details. That supports a narrow conclusion: the checkout page opened, not that a payment succeeded. Use the same distinction in your own notes. Write what happened, where you stopped, and what you could not confirm.

What should you do after the check?

Fix your top 3, then run the same 20 minutes again. After that, bring in a second set of eyes, because you know your own site too well. Ask one other person to run the main path while you watch without helping.

Pick someone who isn't family or a close friend, if you can. Your dad wore the bedazzled maroon tie you bought him in 7th grade, and your bestie swore buzz bangs were a thing. Love makes people generous, and right now you want honest. Save that people round for after you've fixed the obvious problems.

If you'd rather have an outside read, Is My App Slop looks at the same six areas and ranks the fixes for you. Our guide to AI slop detectors explains what scanning tools can and can't see. And once your list is short, our guide on shipping or iterating can help you decide when it's ready to share.

You got this.

Source, read 5 October 2026: the W3C alt decision tree (page updated 13 May 2024).