Your About page is doing more SEO work than your blog

A client called me last spring convinced her blog was broken. Eighteen months of posts, decent traffic on a handful of them, but nothing was converting and she couldn't get ChatGPT to mention her by name even for questions she'd written the definitive answer to. We spent the first call the way these calls always go — pulling up post after post, arguing over headlines. Then I asked her to open her own About page in a new tab.

It was four sentences long. No name attached to the business beyond a generic "our team," no year founded, no photo, a stock-photo hero image, and a mission statement that could have belonged to any of a thousand companies in her category. She'd spent eighteen months building the room and never put a name on the door.

That's not a rare mistake. It's the default. Website builders ship an About template that most people fill in once, during setup, and never touch again — while the blog gets a new post every week. The math of attention is backwards from the math of impact.

Google tells you this directly, if you read the rater guidelines

This isn't a theory I'm reverse-engineering from ranking movements. Google publishes it. The Search Quality Rater Guidelines — the document Google's human quality raters use to score pages, and the closest thing to ground truth Google gives the public about what "trustworthy" means to its systems — instructs raters to look for information about who is responsible for a website, and explicitly names the About page as the place to find it. Raters are told to check "Who is responsible for the website" and "Who created the content," and an About page with no names, no credentials, and no verifiable specifics scores as a low-trust signal.

Google's own helpful content guidance reinforces the same point from a different angle: content should demonstrate expertise and a clear sense of who is producing it. That signal doesn't live inside a single blog post — it lives on the page whose entire job is to answer "who made this."

So when your blog post ranks well but stalls at position six instead of climbing, or gets read but never quoted, the missing ingredient is sometimes sitting one click away, unbuilt.

Why AI engines care about this even more than Google does

A search engine ranks a page against a query. An AI engine has a harder problem: it has to decide, in the moment it's generating an answer, whether to attach your name to a claim it's about to state as fact. That decision runs through an identity check most people never think about.

Schema.org's Organization and Person types exist for exactly this — a structured, machine-readable way to state who you are, what you do, and how long you've done it, separate from the prose a human reads. When an About page carries that markup with real facts in it — founding date, named people, credentials, physical location — it becomes the anchor an AI system can check other pages against. When it doesn't, every blog post you publish is an orphan claim with no verified source behind it.

I'd put it this way after watching this pattern across the dozen-plus brands we run content for: a blog post answers one question. An About page answers the question sitting underneath every question — who is telling me this, and should I believe them. You can win the first without ever winning the second, and it caps what the first is worth.

What a genuinely built About page includes

Not a mission statement. Not stock photography. A page built for scrutiny looks like this:

• Real names, with credentials. Who founded this, who runs it now, what qualifies them. "Our team" answers nothing.
• A founding date and a track record. Specific years, specific milestones — the details a rater or a model can actually verify against other sources.
• A physical location, if you have one. Address, city, service area — consistent with your Google Business Profile and every directory listing, per our own guide on fixing inconsistent brand facts across the web.
• Organization and Person schema markup. The structured version of everything above, stated once in code so machines don't have to parse prose to find it. See schema markup: the language AI actually reads for the mechanics.
• What makes your approach different, stated as a claim, not a vibe. One clear point of view a competitor's About page couldn't copy word-for-word.
• Links out to proof — press mentions, review platforms, case studies — the same corroborating-source pattern covered in how AI uses Wikipedia and Wikidata to confirm facts about a brand.

None of this is expensive to build. It's expensive to have skipped, because the fix touches one page while the cost was spread thin across every blog post you'd already written.

The blog reaches; the About page confirms

Think of the two pages as doing genuinely different jobs, not competing ones. The blog's job is reach — it shows up for a hundred specific questions your buyers ask, one post at a time. The About page's job is confirmation — it's the page a skeptical reader, a Google rater, or an AI system checks when it's deciding whether the reach is worth trusting.

This is the same pattern we cover in entity SEO: making AI understand your brand — an AI engine isn't reading your blog post in isolation. It's building a model of your business as an entity, and every page either adds evidence to that model or leaves a gap in it. The About page is where the gaps get filled fastest, because it's the one page whose entire purpose is stating facts about who you are.

The structural pattern that makes a blog post citable in the first place — a liftable summary, self-contained sections, quotable specifics — is the same discipline covered in the content that gets quoted: structural patterns AI engines actually cite. Build your About page the same way and you get both benefits from the same page: a trust anchor for humans, and a citable entity summary for machines.

The mistake, and why it's invisible until you look

Nobody skips the About page on purpose. It gets built once, during the website-builder setup flow, filled with placeholder-adjacent language nobody meant to keep, and then forgotten because the analytics dashboard never flags it. Blog posts show up in Search Console with impressions and clicks. About pages rarely rank for anything competitive on their own, so they look inert — until you realize their job was never to rank, it was to vouch.

The tell is usually in the numbers, not the page itself. If your blog gets impressions but a disproportionately small share convert into clicks or citations relative to how specific and well-written the content is, check the About page before you rewrite another post. In our own tracking across the brands we run, pages that clearly state who's behind the answer consistently outperform equally good content sitting on a domain with a thin or generic identity page — a pattern that lines up directly with what Google's rater guidelines describe raters checking for.

How to fix yours this week

1. Add real names and one credential each. Founder, year started, one line on relevant experience. Delete "our team" language entirely.
2. Add Organization and Person schema. If you don't have a developer on hand, most CMS platforms support a JSON-LD script tag added directly to the page template — see the schema guide linked above for the exact fields Google and AI engines look for.
3. Cross-check every fact against your other listings. Address, founding year, and business name should match your Google Business Profile, directories, and social bios exactly. Mismatches read as low-trust to both raters and AI systems.
4. Replace the stock hero image. A real photo of real people at the real location does more entity-verification work than any line of copy.
5. Link your best blog posts back to it where authorship or expertise matters, so the connection between the claim and the anchor is explicit, not assumed.

None of these are big lifts. Most take an afternoon combined. The reason they get skipped is that they don't feel like "SEO work" the way a new blog post does — there's no publish-day dopamine hit, no fresh URL in the sitemap. But the return shows up on every page you've already written, not just the one you touch.

Italo Campilii

Founder, Acromatico · runs AI visibility & brand systems across 10+ live brands