birthdaywebsite.app
scanned 2026-10-18 03:09 UTC · defs 2026.09 · uncalibrated beta
category overview
the breakdown
8 of 27 patterns flaggedAI-default font stack (Inter / Geist / Space Grotesk)
Slop fonts
Inter, Geist, Space Grotesk, and Instrument Serif (italic) are the four fonts LLMs default to because Stripe/Linear/Vercel standardized them and training data is saturated with them.
All-caps section labels (text-transform:uppercase)
All-caps
UPPERCASE section labels with positive letter-spacing ('DESIGNED FOR DEVELOPERS', 'MORE FEATURES', 'WHY US') are AI's idea of editorial chic.
Gradient-heavy backgrounds (5+ elements)
Gradient bgs
5+ gradient-background elements means decorative blobs, glows, conic rainbow swirls, or 'aurora' panels everywhere.
Cards nested inside cards
Nested cards
Cards inside cards (a bordered/shadowed/rounded container holding more bordered/shadowed/rounded containers) create visual noise and excessive depth — a reflexive AI layout move where every group gets wrapped in its own panel.
Numbered "1 · 2 · 3" step sequences
Numbered steps
Numbered 1·2·3 'How it works' sections are AI's go-to filler.
Big-number stat banner ("10k+", "99.9%", "$2M+")
Stat banner
'10k+ users', '99.9% uptime', '$2M+ saved' — when these aren't backed by named customers, dated sources, or third-party verification, they read as fabricated.
FAQ accordion in the lower half
FAQ
A `<details>` accordion with 5-10 generic FAQs at the bottom of every page is AI filler.
✓ clean, no tells in this category.
AI-sparkle badges (✨ / Sparkles "magic" tells)
AI sparkles
The ✨ sparkle emoji (or a lucide 'Sparkles' icon) used to label a feature as 'AI-powered'.
the four axes
Slop score · lower is better · system & AEO · higher is better · uncalibrated beta
design slop · Slop score · lower is better
withheld
opt-in required (uncalibrated beta)
copy slop · Slop score · lower is better
not run
system · DESIGN.md · higher is better
none
no DESIGN.md
AEO · agent-readable · higher is better
not run
probe live below
system & aeo detail
system · DESIGN.md drift
No DESIGN.md declared. Add a design system file to track drift between redesigns.
AEO · agent-readable
Page is reachable over HTTP (HTML 2xx)+10
Edge/WAF allows automated retrieval without challenge or block+20
robots.txt permits AI search & citation crawlers (RFC 9309)+20
Page is indexable (no global noindex directive)+12
Snippet & preview controls permit quoting across Google, Bing, and Apple+8
Server-rendered HTML contains primary page prose without JS+15
Validated Markdown twin served via negotiation or .md route+6
HTML advertises a valid Markdown twin (Link rel=alternate)+3
Valid /llms.txt published at site root (H1 + links, non-HTML)+2
Negotiated responses send Vary: Accept+4
No prompt injection, hidden instructions, or AI manipulation links+0
Interactive controls have accessible names and no blocking overlays+0
Agent discovery endpoints (ARD, Agentmap, A2A agent-card, WebMCP)+0
Machine-readable AI usage preferences (AIPREF Content-Usage, Content-Signal, TDMRep)+0
Publication and modification dates are valid and consistent across signals+0
JSON-LD structured data parses cleanly and matches visible text+0
Eight checks, weighted to 100. Evaluated live per scan. Run a fresh scan to see pass/fail.
competitive analytics
cleanliness radar
— you--- rank avg
slop distribution
7,910 scans across 10 bands
You've seen the score. Now fix it.
8 tells, heaviest first.
AI-default font stack (Inter / Geist / Space Grotesk)+8
whyInter, Geist, Space Grotesk, and Instrument Serif (italic) are the four fonts LLMs default to because Stripe/Linear/Vercel standardized them and training data is saturated with them. Using any of these signals 'AI-built' to anyone who's looked at more than 10 landing pages in 2026.fixReplace the body and heading typefaces with something that actually reflects your brand. Pick from foundry sans (Söhne, Aeonik, GT America, Untitled Sans, Suisse Int'l, Pangea, Telegraf, Object Sans) OR a system-font stack (`-apple-system, BlinkMacSystemFont, Segoe UI`) for body + a single distinctive display face for H1.ruleIf you can't name the foundry, don't ship the font. Inter/Geist/Space Grotesk are banned for this site.
Gradient-heavy backgrounds (5+ elements)+4
why5+ gradient-background elements means decorative blobs, glows, conic rainbow swirls, or 'aurora' panels everywhere. This is the AI template equivalent of a 2008 MySpace page.fixAim for zero decorative gradients. At most ONE subtle gradient if it has structural purpose (a section background that aids hierarchy). Replace decorative gradients with: solid color blocks, a single tasteful photograph, real product UI screenshots, or negative space.rule≤1 gradient element total on the page.
Cards nested inside cards+4
whyCards inside cards (a bordered/shadowed/rounded container holding more bordered/shadowed/rounded containers) create visual noise and excessive depth — a reflexive AI layout move where every group gets wrapped in its own panel.fixFlatten the hierarchy. Pick ONE level to be the card and use spacing, typography, and dividers for the inner structure instead of nesting more containers. A card holding three sub-cards should usually be a card holding three text blocks separated by space or a hairline.ruleNo card-like container inside another card-like container. One level of elevation, max.
All-caps section labels (text-transform:uppercase)+3
whyUPPERCASE section labels with positive letter-spacing ('DESIGNED FOR DEVELOPERS', 'MORE FEATURES', 'WHY US') are AI's idea of editorial chic. They appear above every section in v0/Cursor output and add zero information.fixUse sentence-case section titles, or skip section labels entirely. The H2 should do the work. If a label is genuinely useful, write it as a normal sentence in a smaller, dimmed sans.ruleNo `text-transform: uppercase` with `letter-spacing` > 0 on section labels.
Numbered "1 · 2 · 3" step sequences+3
whyNumbered 1·2·3 'How it works' sections are AI's go-to filler. They almost never describe an actual product flow — they describe a generic 'sign up / use it / love it' loop.fixReplace the numbered steps with the actual product flow shown in real UI. A single annotated screenshot or 15-second video tells the user more than 1-2-3 generic verbs. If steps are essential (e.g. an actual checkout flow), make them visual — show the screen at each step.ruleNo numbered steps section with generic verbs like 'Sign up / Connect / Get started'. If you keep numbered steps, each must include a real product screenshot.
Big-number stat banner ("10k+", "99.9%", "$2M+")+3
why'10k+ users', '99.9% uptime', '$2M+ saved' — when these aren't backed by named customers, dated sources, or third-party verification, they read as fabricated. AI templates love them because they make the page feel substantive without effort.fixReplace vanity stats with one specific, verifiable, named claim. 'Used by Stripe, Linear, and Vercel' (with real logos and links) beats '10,000+ companies'. If you don't have named customers yet, REMOVE the stat banner entirely — empty space is more honest than fake numbers.ruleNo big-number stat banner unless every stat is backed by a verifiable source on the page or one click away.
AI-sparkle badges (✨ / Sparkles "magic" tells)+3
whyThe ✨ sparkle emoji (or a lucide 'Sparkles' icon) used to label a feature as 'AI-powered'. It's the single most overused generative-UI tell of 2026 — it says 'AI' without saying what the AI does.fixDelete the sparkle glyph. Describe the actual capability in plain words ('drafts replies in your voice', not '✨ AI magic'). If you need an icon, pick one that depicts the specific action, and let the verb carry the meaning.ruleNo ✨/Sparkles glyph as an 'AI magic' label. Name the capability instead.
FAQ accordion in the lower half+2
whyA `<details>` accordion with 5-10 generic FAQs at the bottom of every page is AI filler. The questions are usually invented to look comprehensive, not because real users asked them.fixEither remove the FAQ section entirely (link to docs or a help center instead), or rewrite it as 3-5 real questions you actually get from users. Better: weave the answers into the main page copy where the question would naturally arise.ruleFAQ section may exist only if every question is one a real user has actually asked, and the section has ≤5 entries.
npx slop-detect birthdaywebsite.app --fix
embed the live badge · uncalibrated beta
[](https://slop-detect.com/score/birthdaywebsite.app)live · re-scans periodically
Claim this page
Own birthdaywebsite.app? Verify by email to list it in the directory and get an alert if it ever drifts back into slop.
monitoring
Keep birthdaywebsite.app on-system between redesigns.
Join the waitlist: the baseline is recorded now, and daily re-scans with regression and design-drift emails switch on at launch. Scanning stays free; this remembers a domain over time.
double opt-in · free during validation · engine stays MIT & free forever · pricing · privacy