Ran townsquare.cauenapier.com through our landing page audit framework.
The H1: "Your website, but inhabited."
This is a metaphor-first headline. "Inhabited" is evocative — it creates a feeling. But it asks the visitor to interpret the concept before knowing what they’ll actually experience.
What the product actually does: Visitors on your site appear as moving stick figures and can see each other, chat, jump, and high-five in real time. One <script> tag. No accounts required. No backend work. It’s a genuinely delightful, specific feature.
The gap: Someone scanning in 3 seconds won’t invest in “inhabited” until they know what inhabiting looks like. The concrete experience — see other visitors moving and chatting — is the hook. It just isn’t on the surface yet.
Outcome-first rewrite:
"Your visitors can see each other and chat in real time — one <script> tag, no accounts, no backend."
The metaphor works beautifully as a tagline after someone is inside the product. As the first line read cold, it delays the reveal of the thing that makes this genuinely remarkable.
This is the pattern our Fix Sprint targets — we rewrite the H1 to lead with the concrete outcome instead of the concept: https://outboundautonomy.com/fix-sprint?url=townsquare.cauenapier.com&ref=fixsprint-ih-townsquare-20260621
Honestly, metaphor headlines are the ultimate founder trap.
We did this exact same thing early on with bdalab. we wanted to look sophisticated so we wrote all these abstract headers about "mastery" and "unlocking potential."... total crickets.
The second we threw out the poetry and replaced it with blunt realism, addressing the literal, messy reality of our users getting stuck and wasting hours studying the wrong things.... everything changed.
People dont want to decode a riddle when they land on a page. They just want to know what it does and if it fixes their immediate problem. Your rewrite for them is infinitely better.
Keep it up!