AI Search Quotes Your Page. You Can't Walk It Back on the Call.
We did a "promise-to-proof" pass on our /ai page this week. The goal was simple: find every claim on the page and ask whether we could actually back it up if a prospect asked directly. We changed three things. None of them were major. All of them were worth fixing.
The old logic doesn't hold
The traditional approach to marketing copy is aspirational. You write to the top of the range. "We've worked with businesses doing up to $20M in revenue" sounds better than "$5M," even if most of your clients are closer to $500k. The reasoning is that it signals capability, and you can always calibrate on the call.
That logic breaks when AI search is involved. When a prospect types "does Twenty1 Media work with larger businesses" into Perplexity, Perplexity reads your page and quotes it back. The $20M figure becomes the answer. The prospect arrives at the call with a number in their head you never actually meant.
Your page is no longer a first impression. It's a quoted source.
Three things we changed
Track record range. The page said Isaac had "built workflows for businesses doing $500k to $20M a year." The $20M figure didn't reflect actual clients. Changed to $500k to $5M. That's the real range. A prospect who cares about the number can verify it. A prospect who doesn't is unaffected by the change.
Support response language. The "Run" phase of our engagement described "SLA-backed support response." We don't have a formal SLA. We respond fast and we prioritize our retainer clients, but there's no document with penalties for missing a response window. Changed to "Priority support response." Same practical commitment, no unenforceable contract implied.
The activity ticker. The hero section had a list of sample automations the "Operations Engine" handles: quote drafts sent, job sheets built, follow-ups logged. It looked like a real-time log. The label read "today · [dynamic date]" with the actual current date rendered in. It wasn't real. Changed the label to "sample activity." The list is illustrative. Calling it "today's activity" implied live data we weren't providing.
What we were looking for
The pattern in all three: copy that makes an implied assertion you'd struggle to defend if a prospect repeated it back. Not vague or aspirational in a harmless way. Specific enough to be checkable, wrong enough to create a problem.
The $20M claim is the clearest case. If a prospect says "I saw you've worked with $20M businesses, here's our situation," you've started the conversation with a misrepresentation. The SLA language is subtler: most prospects won't ask for the SLA document, but the ones who do are the clients most likely to hold you to it. The ticker is the one most people would overlook, but it's the kind of detail that erodes trust when someone notices.
The audit process
We went through the page section by section and asked one question for each factual-sounding claim: if a prospect repeated this back to us on a call, could we confirm it without qualifying? If the answer was "sort of" or "it depends," we rewrote it.
This isn't about being conservative with marketing. The page is still direct about what we charge, who we serve, and what we build. It just doesn't assert things we can't stand behind.
Do the same pass on your own site. AI search engines are reading it as a source document. Write it like one.