What this property was
RockClash is a rock band comparison game: bands face off, you pick winners, arguments ensue, the internet does what the internet does with music opinions. The site is Next.js with Tailwind, a PostgreSQL database of bands and matchups, plus the standard content shell — game modes, comparisons, a blog, about and FAQ pages. Simple, fast, no auth, no payments in the codebase. That last detail matters, because for an embarrassing stretch of time, the website's copy was writing checks the codebase couldn't cash.
Evidence recorded in the manuscript
Revenue: zero confirmed. The monetization was ads and affiliate at most, and at this traffic level that means nothing meaningful; there was never a working purchase to make, which in hindsight was the only thing protecting me from the copy problem becoming a refund problem. Traffic: modest organic search and the occasional curiosity click. Costs: domain, a slice of shared server, and the audit time to make it honest. I genuinely don't know how many visitors hit the overpromising version of the site before the fix.…
The lesson recorded after launch
Audit your copy against your code, especially when machines wrote the copy. AI agents will cheerfully produce confident, polished marketing for any feature you mention in a prompt, and the failure mode isn't a dramatic lie — it's drift, where pages quietly describe your ambitions instead of your product. The fix is a discipline, not a one-time edit: every claim on every page must be verifiable by a stranger using the live site today. Across fifty properties, that means scheduled integrity sweeps where you read your own sites like a skeptical visitor.…