The "So What?" Test for Every Line on Your Homepage
Read every line of your homepage as a bored stranger asking 'so what?' and delete or rewrite whatever can't answer.
There’s an editing procedure I use on homepages that requires no taste, no design sense, and no copywriting skill. You read the page one line at a time, and after each line you say, out loud, in the voice of a bored stranger: so what? If the line has an answer, it stays. If it doesn’t, it gets rewritten until it does, or deleted. That’s the whole procedure. It’s crude, and it works better than most sophisticated advice, because it converts a vague goal, “make the copy compelling,” into a mechanical test you can actually run.
Watch it work on a typical line. “Built on a modern cloud-native architecture.” So what? Well, the founder explains, it means we scale automatically. So what? It means the app stays fast even when your whole company uses it at once. So what? It means you won’t be the person who bought a tool that fell over during the busy season. Now look at what happened: three so-whats in, we finally hit something a buyer feels. The published line should have been the last one, or near it. The architecture is the founder’s answer; the busy season is the customer’s question. Every “so what” is a step along the chain from what you built toward why anyone cares, and most homepage copy stops walking two or three steps too early.
Why do writers stop early? Because the early steps are the ones they’re proud of. The cloud-native architecture was hard to build. The founder wants credit for it, and putting it on the homepage feels like claiming that credit. But the homepage isn’t a trophy case. The visitor doesn’t award points for difficulty; they can’t even perceive difficulty. They perceive only consequences for themselves. This is the uncomfortable core of the test: it keeps ejecting the sentences you’re most attached to, because attachment usually signals that a sentence is about you.
The test is also a fog detector. Some lines fail not because they stop too early on the chain but because they were never on a chain at all. “We’re passionate about empowering teams.” So what? There’s no answer, not even a bad one, because the line contains no claim. You can’t follow a consequence from it because it doesn’t assert anything that could have consequences. Lines like this are verbal upholstery. They exist because a section of the page looked empty, and something had to go there. The test finds them instantly, because a line with no content produces a distinctive silence when you interrogate it.
You have to be careful not to overcorrect into the opposite vice. If you chase “so what” far enough, everything terminates in the same few ultimates: make more money, save time, avoid fear. A homepage where every line has been boiled all the way down reads like a hostage note: Save time. Make money. Buy now. The skill is knowing where on the chain to stop, and the answer is: at the last step the visitor can verify or vividly imagine. “Close your books in three days instead of three weeks” is far along the chain but still concrete, still checkable, still about accounting. “Transform your finance function” has gone past the end of the chain into abstraction from the other side. Concrete consequence, not cosmic consequence.
There’s a variant of the test for the skeptical reader, and it’s the same words with different emphasis: so what? As in, prove it. Every line that survives the first test should face the second. “Close your books in three days,” says the page. So what, says the skeptic, meaning: why should I believe you? This is where evidence attaches to claims: the screenshot, the customer quote, the free trial that lets them verify it themselves. A claim without support survives the first test and fails the second. The best homepage lines pass both, which is why they tend to be specific: specificity simultaneously delivers a consequence and hints at proof, since only someone who has really done a thing can afford to describe it precisely.
I ended up encoding a version of this into GazeSite, where the clarity checks essentially ask of a page’s headline copy: could a stranger say what this means and why it matters? But the automated version exists because the manual version, though free, is rarely performed. It’s unpleasant. Running “so what” on your own writing means playing a person who doesn’t care about your work, and founders spend all day trying not to imagine that person. Yet that person is the market. Almost everyone who lands on your homepage doesn’t care yet. Caring is the output of the page, not the input.
So take the page you have, today, and read it aloud line by line with the question after each. You’ll find lines you can’t defend and would never write again, sitting there because they’ve been there since launch. The test doesn’t tell you what to write. But it tells you, with very little mercy, what to cut, and on most homepages that’s the majority of the work.
More articles
Your homepage should be written for someone doing three other things at once, because that's who's reading it.
Read →A web page is a journey through a stranger's doubts, and you can map that journey the way you'd map any route.
Read →Good navigation is less about helping people go somewhere and more about telling them where they already are.
Read →