the ai-design-slop fingerprint · definitions 2026.09
Does your landing page look generated?
deterministic · real Chromium · a scan takes ~8s
The cleanest pages, by category
view full leaderboard →A reproducible scan of well-known landing pages, cleanest first. Every name links to its score page, where the current run, history and live badge live.
a signal, not a verdict · premium sites score Mild too
The board fills from the public leaderboard. view it →
What the score measures
Four axes, two polarities. Design and copy measure slop, so lower is better. System and AEO measure fit and reach, so higher is better.
27 weighted CSS patterns: the fonts, gradient hero text, glassmorphism and convention stack generated pages converge on. Run on real Chromium, scored deterministically. lower is better
An optional second axis on the words: the hedge-y, em-dash-heavy register LLMs default to, and the "not just X, it's Y" antithesis. lower is better
Drift from a page's own declared design tokens. A bespoke site checked against its own DESIGN.md can never false-positive as slop. higher is better
Whether ChatGPT, Claude and Perplexity can fetch, read and cite the page: crawler access, robots.txt, a markdown twin, llms.txt. higher is better
continuity
Slop is the hook. Staying on-system is the product.
Sites do not become slop in one commit. A teammate ships a section, an agent "improves" a hero, and six weeks later the page reads like everyone else's.
Monitoring re-scans your domain daily and emails you when it slips. Publish a DESIGN.md and it also checks every scan against your own declared tokens, then names exactly what drifted.
Re-scans every monitored domain each day and emails you the moment the slop score regresses.
Checks each scan against your declared tokens and names the drift: a font nobody approved, a CTA off the palette.
Every monitored domain gets a print-ready report at /report/<domain> to hand a client or a team.
Nothing is emailed until you confirm. Your address is stored only to send the alerts you asked for; one request deletes it.
Every domain on your email in one dashboard; opt in to the public directory for a live badge and a dofollow backlink.
Monitor a domain
A daily re-scan and a drift alert the moment a redesign slips back into slop. Scanning stays free; this remembers a domain over time.
Double opt-in: nothing is emailed until you confirm. Stored only to send the alerts you asked for, never shared, and one request deletes it (privacy). Every monitored domain gets a print-ready client report at /report/<domain>. The engine stays MIT and free forever; monitoring is the continuity layer.
Not where you want to be?
Run a scan, read the flagged patterns, and copy a fix prompt straight into the agent that built the page.
Empty is better than fake. Show the product, don't decorate around it.