Your About Page Is an Entity Signal: Brand Story Pages That Teach AI Who You Are

The About page has spent twenty years as marketing's junk drawer: the founder photo, the "our journey" timeline, the values wall, updated whenever someone remembers it exists — which is roughly never. That neglect made sense when the page's only readers were the occasional diligent customer and a bored recruiter. It stopped making sense the moment AI systems started composing answers about your brand — because when ChatGPT, Perplexity, or Google's AI is asked "who is [your company] and are they legit?", your About page is one of the first primary sources it reads, and often the only place on the internet where you get to state, in structured and unstructured form together, exactly who you are. In 2026, the About page isn't brand fluff. It's an entity declaration — and most businesses are declaring almost nothing.

The concept doing the work here: search and AI systems moved "from strings to things." They no longer just match keywords; they resolve entities — uniquely identifiable things (a company, a person, a product) with properties and relationships — inside knowledge graphs, and generate answers by pulling verified entities and their relationships rather than scanning blog posts word by word. The chain that makes this commercially urgent is now explicit: entity establishment → Knowledge Graph inclusion → the training and grounding data of AI systems → whether and how you appear in AI answers. Google has stated the link directly — Gemini is trained on the Knowledge Graph, so brands with high-quality entity representations carry a structural advantage in AI-generated answers. If your brand isn't a clearly resolved entity, your content can rank traditionally and still be invisible to the answer layer — because the machine composing the answer isn't sure who you are.

Why the About page specifically (and not just "the website")

Three properties make this one page the natural home of your entity layer:

It's the canonical self-description. Every other page describes what you sell or know; the About page describes what you are — and that's precisely the question an AI system is trying to resolve when a user asks about your brand. It's where name, founding, location, leadership, offerings, and proof naturally co-exist, which makes it the page where Organization schema and visible content can match perfectly — a requirement, since Google's structured-data policies insist markup reflect visible, accurate on-page content. Your content explains; schema translates; knowledge graphs connect — and the About page is where all three can point at the same facts.

It's the disambiguation battlefield. Unless your brand name is globally unique, machines must decide which "Alian" or "Apex" or "Nova" you are. The About page is where you hand them the differentiators: full legal and brand names, location, industry, founding date, the founders as linked Person entities, and the sameAs trail to your verified profiles. The five entity problems that appear repeatedly in the wild all get solved (or created) here — the biggest being inconsistent naming: "Acme Software" on the website, "Acme Software, Inc." on LinkedIn, "Acme" on Crunchbase, "AcmeSoft" on X — variants a disambiguator may treat as different entities, splitting your identity and its accumulated trust into fragments. One canonical name, everywhere, starting from this page.

It's where E-E-A-T becomes machine-readable. AI systems use your brand SERP and entity signals as a proxy for authority and trustworthiness. The About page is where experience and expertise stop being claims and become linked facts: named people with credentials (Person schema connected to the Organization via founder/employee relationships), verifiable history, real addresses, memberships, awards — each one a graph edge the machine can check against third-party sources.

The rebuild: what a 2026 About page contains

The entity paragraph — the first 60 words. Open with a direct, extraction-ready self-definition that a machine could lift verbatim as the answer to "what is [brand]?": "[Brand] is a [category] company founded in [year] in [city], serving [who] with [what]." No "we believe journeys begin with a single step." The poetic version can live below; the declarative version must come first, because the first paragraph is the highest-probability extraction zone — the same answer-first discipline from our AEO playbook, applied to your identity.

The facts block, visible and structured. Founding year, headquarters, team size range, markets served, key services/products, leadership — as scannable on-page content that mirrors the schema exactly. Machines cross-check; a mismatch between what the page says and what the markup claims reads as a trust problem.

The people, as entities. Founders and key leaders with names, roles, one-line credentials, and links to their profiles — each carrying Person schema tied to the Organization. Authorship and leadership are entity relationships now, not bios; a founder who exists as a resolved entity (consistent name, LinkedIn, publications, talks) lends that resolution to the company.

The proof, linkable. Client logos are pixels; named case studies, press mentions, platform profiles (Clutch, G2, GBP), and review counts are verifiable edges. Every claim on the page should be one click from its evidence — because the review-corpus and third-party-consensus mechanics from our earlier posts are exactly what AI systems check your self-description against.

The story, last and human. The founder's journey, the why, the culture — genuinely valuable for the humans deciding whether to trust you, placed after the machine-legible layer rather than instead of it. This isn't "write for robots"; it's sequencing: facts first, feelings second, so both audiences get served.

The schema layer (the 30 minutes that do half the work)

On the About page (and homepage), Organization schema in JSON-LD with: a stable `@id` (your entity's permanent address in graph-space — pick the URL form once and never change it), legalName and the canonical brand name, logo, foundingDate, founder (as Person objects), address, contact, description matching the entity paragraph, and — the property practitioners consistently rank most important — a complete `sameAs` array linking every authoritative profile: LinkedIn, GBP, Crunchbase, GitHub, industry directories, social handles. The sameAs array is you telling every machine reading the page: these scattered profiles are all the same entity — me. Beyond your own site, the standard playbook adds a Wikidata entry (Wikipedia is one strong signal but not the only path — a solid Wikidata entry plus aligned profiles is often enough to seed entity recognition) and a profile-standardization pass so name, description, founding date, and location match everywhere machines look. Realistic expectations from the practitioner data: knowledge-panel appearances within 60–180 days, AI-citation lift within 90–120 days — entity work is compounding infrastructure, not a growth hack.

The audit: what AI currently believes about you

Before rebuilding, measure the gap. Ask ChatGPT, Perplexity, and Gemini, in clean sessions: "What is [brand]? Who founded it? What does it do? Where is it based? Is it trustworthy?" Then Google your brand name and study the SERP — the knowledge panel (or its absence), which profiles surface, what description gets pulled. Wrong facts, outdated descriptions, confusion with a similarly-named company, or a shrug ("I don't have information about...") are all entity problems — and the About page rebuild plus profile standardization is the treatment for every one of them. Re-run the same prompts quarterly; watching the machines' description of you converge on your own is the most satisfying metric in this whole discipline.

The reframe to leave with: for two decades, the About page answered a question almost nobody asked. Now a growing share of your prospects never visit it at all — they ask a machine about you instead, and the machine does read it, carefully, as evidence. Rewriting one page and thirty minutes of schema so that every AI describing your brand describes it accurately, confidently, and in your own words is close to the cheapest visibility work available in 2026. Entity architecture — the About-page rebuild, Organization/Person schema, Wikidata, profile standardization, and the quarterly what-does-AI-say audit — is part of every AEO engagement we run, and it's usually the piece with the most embarrassing before screenshots.