The Page That Explains Everything and Communicates Nothing

The worst homepage I ever audited was also the most thorough. It mentioned every feature, every integration, every industry the product served, every award the company had won. Nothing important was missing. And after reading all of it, I could not have told you what the product was. I remember sitting there thinking: this page has answered every question except mine.

This failure mode has a shape, and once you see it you’ll recognize it everywhere. The page grows by accretion. Sales says enterprise buyers ask about compliance, so a compliance section appears. A big customer uses an obscure integration, so it joins the logo wall. Marketing wants to rank for eleven phrases, so all eleven get worked into the headline area. Each addition was rational. Someone, somewhere, once needed that information. The page becomes a union of every question anyone has ever asked, and a union of answers is not an explanation. It’s a filing cabinet with the drawers open.

The mistake underneath is treating the homepage as a document instead of a conversation. A document should be complete; you file it and consult it. A conversation has a sequence, and the sequence matters enormously, because a stranger arriving at your site has exactly one question at first: what is this? Not “is it SOC 2 compliant,” not “does it integrate with my warehouse,” not “which industries.” Just: what is this thing, in words I already know? Until that question is answered, every other answer on the page is noise, because the visitor has no frame to hang it on. Telling me about your integrations before I know what you do is like listing a stranger’s medical history before telling me they’re a person or a horse.

What makes this hard to fix is that completeness feels safe and omission feels risky. If you cut the compliance section, you can imagine the specific deal you’ll lose. If you keep it, the cost is invisible: a thousand strangers each slightly more confused, none of whom will ever email you to say so. Confusion doesn’t file complaints. It just leaves. So the incentives all point toward adding, and the page ratchets in one direction, and everyone involved can defend every piece of it while the whole slowly stops working.

There’s also a psychological trap for the writer, which is that explaining everything feels like clarity. You’ve been transparent! It’s all right there! But comprehension doesn’t work by exposure. A visitor doesn’t absorb a page; they sample it. Eyes land on the headline, a subhead, maybe a button, maybe one image caption. If those four samples cohere into “oh, it’s X for Y,” the page communicated. If the four samples come from four different sections aimed at four different audiences, the visitor gets a word salad, even though every individual sentence on the page is true and well-written. The unit of communication is not the sentence. It’s the impression formed from a few random sentences, and you don’t control which ones.

When I run scans with GazeSite, the clarity check is deliberately crude: given only what’s visible, can a stranger say what this site offers within a few seconds? Crude is the point. The sophisticated reading — the one where you scroll everything and synthesize — is the reading nobody does. And the pages that fail this crude test are rarely sparse pages. They’re almost always the exhaustive ones. Sparse pages fail differently, by being vague. Exhaustive pages fail by being loud in twelve directions at once, which arrives as silence.

The fix is not to delete information but to demote it. Everything on the old homepage can live somewhere; it just can’t all live at the top, at equal volume. The top of the page gets one job: answer “what is this” so plainly that the visitor could repeat it to a colleague. One sentence, one audience, one claim. Below that, information can appear in the order a persuaded person would want it — what it looks like, what it costs, how to start — and the long tail of compliance and integrations and industries moves to pages for the people who ask those questions. This is what structure is for. Not decoration, but sequencing: an argument for reading the page in a particular order, made by someone who decided what that order should be.

Which points at the real difficulty. Demotion requires deciding what matters most, and that decision has an owner, and the owner has to say no to colleagues whose favorite section just moved below the fold or off the page entirely. The exhaustive homepage is often not a writing failure at all. It’s an unresolved argument about what the company is, settled by including everything, which is to say not settled. The page communicates nothing because the company hasn’t agreed on the one thing to communicate.

So if your homepage explains everything, don’t start by rewriting it. Start by answering, in one spoken sentence, what you’d say to a stranger who asked what you do. If that sentence comes easily, your page just needs editing. If it doesn’t, you’ve found the actual problem, and no amount of copy will fix it for you.