AI Slop Website Examples: 12 Tells of a Generated Site

Twelve signs that a website was generated and published without review. One proves little; several together usually mean nobody edited the output.

New to the term? Start with what AI slop means. Here for code? See 20 AI slop code examples.

Copy: generic, padded or unfinished

1. The hero that could sell anything

Unlock the power of seamless collaboration.
Elevate your workflow with our cutting-edge, AI-powered platform.
Revolutionize the way you work, today.

Swap the product name and this headline still fits a CRM, a todo app or a dog-walking service. Say what your product does and for whom: “Scores the code your agent wrote, before it merges” is more convincing than “Elevate your code quality.”

2. The fast-paced digital landscape

Openers like “In today’s fast-paced digital landscape…” or “Whether you’re a startup or an enterprise…” delay the point, and sections often end with “In conclusion” and a restatement. Delete the first sentence of each section and check whether anything was lost.

3. Placeholder text that shipped

<h2>[Your Compelling Headline Here]</h2>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit.</p>
<footer>© 2024 Your Company Name. All rights reserved.</footer>

The strongest tell: nobody read the page before it went live. Treat these like a TODO left in production code.

Design: defaults nobody chose

4. The purple-to-blue gradient

<section class="bg-gradient-to-r from-purple-600 to-blue-500">
<h1 class="bg-clip-text text-transparent bg-gradient-to-r from-pink-500 to-violet-500">

The default in popular component kits and in the examples models learned from. Use a gradient only if you actually chose it.

5. Three emoji feature cards

🚀 Lightning Fast    ⚡ Powerful Integrations    🔒 Enterprise-Grade Security
Experience blazing   Connect with the tools     Your data is safe
fast performance.    you already love.          with us.

Each card has an emoji, a two-word title and a sentence that repeats the title, and none of the claims can be checked. Show the feature instead: a screenshot, a command, or a number with a source.

6. Every surface is the same card

When every block is rounded-2xl shadow-xl with a glass background, centered text and the same padding, pricing, testimonials, features and the FAQ all look alike and nothing stands out. Decide what matters most on the page and make only that prominent.

7. Generated imagery that falls apart up close

Generated hero images often have warped hands, garbled text, a laptop with two keyboards, or a team whose members share one face. They pass at thumbnail size, so check images at full size and read any text in them.

Proof: claims nobody can check

8. Testimonials from nobody

"This tool completely transformed our workflow!"
- Sarah J., CEO at TechCorp

A first name, an initial and a company that does not exist. Use real testimonials from people readers can find, or none: fake ones make every true claim on the page harder to believe.

9. Numbers without a source

“10x faster”, “Trusted by 10,000+ teams”, “99.9% uptime” and “Save 40 hours a month” appear because landing pages have stats, not because anyone measured them. Publish one real number with its method, or leave the section out until you have one.

Markup: links, forms and code that do not work

10. Links and buttons that go nowhere

<a href="#">Privacy Policy</a>
<a href="#">Terms of Service</a>
<button>Get Started</button>  <!-- no handler, no link -->

Footer links point to #, social icons point at the platform’s home page, and the “Get Started” button has nothing attached. Click every link and button before launch.

11. The form that pretends to submit

function handleSubmit(e) {
e.preventDefault();
console.log("Form submitted:", email);
setSuccess(true); // shows "Thanks! We'll be in touch."
}

The visitor sees a success message while the email only reaches the browser console: a swallowed failure, the same bug as in code.

12. Div soup, no alt text, dead code

<div class="flex flex-col flex-col items-center items-center">
<div onClick={go}>Learn more</div>
<img src="/hero.png" />
</div>
// const oldHero = () => { ... }  // unused, left from the first attempt

Clickable divs instead of buttons, images without alt, duplicated utility classes, commented-out components and unused imports. Together they make the site slower, less accessible and harder to change, which is what AI slop in code does to any codebase.

A one-minute AI slop website check

1. Read the hero aloud. If it could describe a different product, rewrite it.
2. Search the page for unlock, elevate, seamless, lorem, Your Company, and brackets.
3. For every number and testimonial, ask where it came from. If nobody knows, remove it.
4. Click every link and button and submit every form. Watch the network tab, not the success message.
5. Run an accessibility check for missing alt text and non-button click targets.
6. Scan the code behind it. Problems in the markup usually point to problems in the logic.

The same defaults show up in code

Every tell above is a default: models and templates produce the most common landing page unless someone asks for something specific and checks the result. Code has the same defaults, but they are harder to see: the swallowed exception, the narrative comment, the unsafe cast, the helper left from a first attempt. aislop flags those patterns with fixed rules, so the code gets the review the page never did.

Run npx aislop scan in the repo behind your site, browse the AI slop patterns, or scan a public repo in the browser.