The about page nobody reads, and the one people do

Pull up the analytics for almost any B2B site and the about page sits in the top three or four URLs by traffic, usually just behind the homepage and the page that ranks for the company's main service. Ask the person who owns the site what that page is for and the answer is nearly always a shrug dressed up as strategy: it rounds out the navigation, it's where the founding story goes. Nobody treats it as a page with a job, which is strange, because the traffic numbers say it has one, and that it's currently guessing at the job rather than doing it.

The instinct to fill that page with the founding story is not unreasonable. Somebody built this company, there was a reason, and telling people that reason feels like the honest thing to do on the one page reserved for talking about yourself. The problem isn't dishonesty. It's that the story answers a question almost nobody visiting that page is asking.

Who actually lands there, and what they already decided before they clicked

The about page does not pull in strangers doing the first pass of a search. Those people land on the homepage or a service page, because that's what ranks for the problem they typed in. The about page pulls people already several steps into a relationship with the company, with a specific, narrow question that only that page — by convention — is expected to answer.

A prospect mid-evaluation clicks About once the open question has shifted from "does this do what I need" to "should I trust this particular company with it." A job candidate clicks About after reading the listing, to check who they'd actually be working for before writing a cover letter. A journalist or an analyst clicks About because it's the fastest place to confirm a company is a real, ongoing entity before quoting or citing it. Someone in procurement clicks About as one stop on a checklist that also includes the security page, looking for the legal entity name they'll need to put a contract in front of. None of these four arrived confused about what the company sells. All four arrived with a specific doubt, and the founding story — however well written — resolves none of them.

That's the mismatch. A page getting genuinely high-intent, late-stage traffic is staffed with content aimed at a reader who isn't there: someone discovering the company for the first time and needing to be charmed into interest. The people who actually click About already have interest. What they need is confirmation — size, real people, and a couple of pieces of paperwork most companies bury or skip.

Size, and why vagueness reads as smaller than it is

The first thing most of those four visitors are checking, whether they'd phrase it this way or not, is scale: is this company big enough that dealing with them carries acceptable risk. A candidate wants to know if they're joining three people or three hundred. A procurement officer wants to know if the vendor will still exist in three years. A prospect wants to know whether the team behind the product is one overworked founder or a functioning organization.

Companies that have a good number tend to state it. Companies that don't tend to reach for language that sounds like it answers the question without committing to a figure — "a growing team," "a passionate group of experts." A reader checking for size treats that vagueness as evidence of a small or shrinking number, on the assumption that a flattering figure would already be on the page. The reader can't tell intentional discretion from an unflattering truth, and defaults to assuming the worse of the two.

The fix costs nothing: state the actual headcount, or the founding year if headcount would be embarrassingly small, or years in business — whichever real number reads best, stated as a number rather than dressed as an adjective. "Founded in 2019, eleven people, offices in two cities" tells a reader more in nine words than "passionate about what we do" tells them in three hundred.

Real names and real faces do work that stock photography actively undoes

The second check is whether the people behind the company are real, and this is the one place an about page can lose ground it never needed to give up. A stock photograph of a smiling person in a blazer, captioned "Our Team" or captioned nothing at all, does not read as neutral filler to a visitor running this check. It reads as evidence — the visitor knows what a stock photo looks like, and its presence on the page where they came to confirm the company is staffed by real humans tells them the opposite.

The substitution costs more than it saves. A short list of actual names and actual titles with no photos at all reads as more trustworthy than a page of four photogenic strangers, because the first is honest about what it has and the second is caught pretending. If real photography isn't available yet, name the people plainly and skip the imagery. A journalist checking legitimacy and a candidate checking who they'd report to are both, in that moment, looking for a name they can put next to a role, not an aesthetic. Titles matter too: "Founder & CEO" tells a visitor something, and "Chief Vibes Officer" tells them the page was written for internal amusement rather than for the person standing in front of it.

The founding story belongs in one sentence, or on its own page

None of this means the founding story is worthless — it means it's misplaced. A visitor checking size, checking whether the people are real, and checking the legal registration is not, in that moment, in the mood for four paragraphs about a garage and a late night that changed everything. That narrative has genuine value as blog content or podcast color. It is not what someone clicking "About" fifteen minutes before deciding whether to sign a contract needs from that click.

The workable version is one sentence, near the top, compressed to the point of being almost a fact rather than a story: "Started in 2019 by two engineers who'd spent a decade fixing the same problem at three different companies." That does the humanizing work the founding story was supposed to do without asking a verifying reader to sit through a narrative they didn't ask for. If the fuller story is worth telling, link out to it and let the reader choose to go looking for it.

This is a special case of the broader discipline what a company website is actually for argues for the whole site: know the job before deciding what goes on the page. The about page's job, for the traffic it actually gets, is verification. Verification pages should read like verification, not like a pitch.

The legal and registration details nobody notices until they're missing

The quietest trust signal on the page — invisible to a casual scan, load-bearing anyway — is the boring administrative detail: the full legal entity name, a real registered address rather than a P.O. box, and, where relevant, a registration number, VAT number, or the professional license that lets the company legally do what it claims to do.

Nobody reads that information for pleasure. But its absence is checked, specifically, by the two visitors with the most at stake in whether a deal closes: procurement, needing a legal entity name for a purchase order, and a journalist confirming the company is a registered thing rather than a landing page with a stock photo and a contact form. Both checks fail silently — nobody emails to say "I couldn't find your registration number, so I moved on." The deal just doesn't happen, and the company never learns why. Companies whose site does sales-enablement work, sent as one specific link between the first call and the second — the pattern the pillar piece above walks through — feel this hardest, since that page is often the only unattended moment in an otherwise human sales process.

Putting that detail on the page is a five-minute task with no design implications: a line in the footer with the legal name, the registered address, and the registration number if one applies. It will never be the reason someone praises the site. It will occasionally be the reason a deal that was going to stall quietly, doesn't.

What the page is actually for

An about page with high traffic and no defined job ends up optimized for the writer rather than the reader — it tells the story the company most wants to tell, in the order that story makes narrative sense, rather than answering the questions the people who click it actually have. Reordered around the real audience, the page gets shorter, not longer: a real number near the top, real names with real titles, one compressed sentence about why the company exists, and the unglamorous legal details a reader can find without hunting.

Companies that get this right tend to have thought about the whole contact chain the same way — not just what the about page confirms, but what happens once someone acts on it, a decision the case for and against a contact form covers on its own terms. Companies that treat every page as an argument for something specific tend to produce pages like the one taken apart in the Basecamp positioning teardown — pages that read like they know exactly who is standing in front of them.