Slop*Detector

CERTIFIED SLOP — slop score 85/100

The evidence on loomscape.space points one direction, and the score of 85 reflects that. The copy leans on em dashes in back-to-back sections, pairs rhetorical questions with their own answers ('Tired of finding out what happened after it already blew up? Loomscape is the answer.'), and closes on a line dressed up past what it actually says ('Wherever your market speaks, you're never watching alone.'). The product screenshot doesn't help the case either; a sidebar literally labeled 'Something Workspace' sits next to a metric claiming a 1,275% jump, the kind of placeholder data a generator drops in rather than something pulled from a real account. Layered on top of that are the usual structural tells, pill tags, a gradient hero, an eight-card feature grid, and no Terms of Service or Privacy Policy anywhere on a page that's asking people to start a trial. Taken together, the writing patterns and the unfinished legal basics agree with each other closely enough that this reads as generated end to end rather than lightly assisted.

Findings

• Feature-tile grid — Equal-width card grids of 3–4 identical tiles (icon, subheader, blurb) are the signature layout block of generated landing pages.
• Pill tags — Little fully-rounded pill badges sprinkled across the page ("New", "Beta", category chips) are a default garnish of vibe-coded UI.
• Gradient backgrounds / gradient text — Large gradient washes and gradient-clipped headline text (usually blue→purple) are the default decoration of generated UI.
• Rhetorical question as hero machinery — The hero copy opens with a rhetorical question before pivoting to the answer, a pattern flagged as AI hero machinery rather than direct product description.
• Stock CTA pair — The hero uses a filled primary button next to an outlined secondary button with generic action labels, the canonical AI-generated CTA pairing.
• Mocked dashboard screenshot with implausible/placeholder data — The embedded product screenshot shows a workspace literally named 'Something Workspace' and metrics with suspiciously large percentage jumps, suggesting placeholder data slotted in by a generator rather than a real product capture.
• Feature-tile grid — An 8-card grid with icon-free but uniformly structured bold-number + header + blurb cells describing capabilities, matching the classic repeated-card feature grid structure.
• Numbered/icon list used as filler — A vertical list of four icon+bold-header+blurb rows (Campaigns & activity, Compare your whole competitive set, Messaging & angles, Sentiment shifts) mirrors the generated feature-list rhythm even without full card wrapping.
• Copy/layout symmetry — Multiple sections repeat the same kicker-less but mechanically balanced bold-stat + header + blurb cadence across many cards, and channel cards (TikTok/Instagram/Threads) each get exactly three identical pill tags underneath, showing mechanically balanced content rather than organic variation.
• Pill tags — Numerous fully rounded pill-shaped tags are scattered across the lower sections, both as feature labels and as a channel/platform strip, consistent with the AI pill-tag pattern.
• Indigo/green accent and gradient text — The page uses an emerald-green and lime-green palette as its accent system throughout, including a gradient/highlighted headline word, consistent with the 'safe' green-accent drift noted as a current AI-default fallback.
• Faux data visualization with suspicious precision — Small inline chart/stat cards floating over the hero area show oddly specific but unverifiable numbers typical of fabricated product demo data.
• Redundant restating sections — The 'Wherever your market speaks, you're never watching alone' section and the final 'Understand your market. Act with confidence.' section both restate the same core pitch (cross-channel monitoring, confident decisions) already covered in the hero and stats section, adding little new information.
• Em dashes — Em dashes are the single most reliable punctuation tell of LLM copy. Human marketing copy almost never uses them; models reach for them constantly.
• "It’s not X. It’s Y." reframe — The contrast-reframe construction ("It’s not X. It’s Y.", "X isn’t just Y, it’s Z") is the classic LLM rhetorical move. A dead giveaway.
• Stacked short-sentence drumbeat — Three or more clipped sentences in a row ("Important emails buried. Drafts that sound wrong. Labels everywhere.") is the manufactured-rhythm tell.
• "That’s where/why/the…" payoffs — Short demonstrative payoff sentences glued onto paragraph ends ("That’s the flywheel.") are choppy LLM theater.
• Compulsive rule-of-three — "Fast, reliable, and secure." Triads everywhere read as machine rhythm — humans vary list length; models default to three.
• Em dash usage — The copy uses em dashes multiple times, including the double-space-free kind the guide explicitly bans ('No em dashes. Ever.'). This is a classic LLM punctuation tell.
• Rhetorical-question pivot — Two separate instances pose a question and immediately answer it, a structural tic the guide flags as paragraph machinery rather than real explanation.
• 'X, not Y' reframe — The hero subhead uses the banned appositive contrast device to manufacture sharpness instead of just stating the benefit.
• Compulsive rule-of-three — Several feature descriptions and CTAs use triadic parallel structure back-to-back, a rhythmic tell the guide calls out as machine cadence.
• 'From X to Y' sweep — A generic range construction is used to describe the product flow instead of naming the actual steps.
• Manufactured profundity — This closer dresses up a simple multi-channel monitoring claim in vague, slightly mystical phrasing rather than stating the concrete capability.
• Short declarative stacking — Back-to-back clipped imperative sentences create the drumbeat rhythm the guide warns against, even if only briefly.
• No Terms of Service — No Terms of Service link anywhere on the page. Shipped products taking signups or payment have one; weekend vibe-code projects usually don't.
• No Privacy Policy — No Privacy Policy link anywhere on the page. Shipped products taking signups or payment have one; weekend vibe-code projects usually don't.