The About Page Is a Trust Document: What Engines Actually Evaluate

Reading time: 11 minutes

Why your About page is a trust document, not filler

Most advice about About pages treats them as a branding exercise: tell your story, share your values, add a nice photo. That framing misses what the page actually does in 2026. Google's Search Quality Rater Guidelines explicitly direct human raters to find out who is responsible for a website and who created its content, and the About page is where that investigation starts. When raters cannot identify the operator, the guidelines instruct them toward the lowest quality ratings regardless of how polished the rest of the site looks.

The same logic now runs at machine scale. AI answer engines assembling a response about your category have a short list of citation slots and a strong preference for sources they can attribute to an identifiable operator. A domain with no discoverable humans behind it is a domain the machine has no reason to trust. Your About page is the affidavit. Everything else on this page follows from taking that one reframe seriously.

This work sits squarely in Vector 2 of our methodology, Anchor: establishing the entity behind the domain so that every engine evaluating your content can confirm you exist. It pairs directly with the broader set of trust signals for your website, of which the About page is the load-bearing wall.

What search engines check: entity confirmation, identity, credentials

Strip away the copywriting and an About page answers four machine-readable questions. Who operates this site, as named humans and a named legal entity? What qualifies them, in credentials, licences, tenure, or documented work? Where do they operate, as a physical address or declared service area? And can any of it be confirmed somewhere else on the web?

That fourth question is the one owners underestimate. Engines do not take your About page at its word; they triangulate it. A founder named on the page who also appears on LinkedIn with a matching role, in a local news article, on an industry association member list, or in a podcast episode is a confirmed entity. A founder who exists nowhere except your own domain is an unverified claim. The page's job is to make the triangulation easy: full names, exact role titles, credential numbers where the profession issues them, and outbound links to the profiles that corroborate each claim.

For Ontario trades and professional services this is concrete, not abstract. A licence number from the governing body, a WSIB clearance mention, an association membership: each one is a fact an evaluator can check in seconds, and each one separates you from the competitor whose About page says only that they are passionate about excellence.

How AI engines use your About page for entity resolution

When ChatGPT, Perplexity, or Google's AI features encounter your brand, they have to solve a disambiguation problem before they can say anything about you: which real-world entity does this name refer to? That process, entity resolution, runs on exactly the data an About page provides. Founding date separates you from the similarly named company two provinces over. Address and service area pin you to a geography. Founder names connect the organization node to person nodes that carry their own trust history.

Google's own documentation on profile page structured data confirms the mechanism from the search side: pages about a specific person or organization, marked up properly, feed the systems that decide how an entity appears across search features. The generative engines behave the same way with less forgiveness, because a model that cannot resolve your entity does not rank you lower; it simply talks about someone else.

The practical instruction: write the About page as if a careful machine will quote it back to a prospect, because one will. Every sentence should be a fact you are content to hear an AI assistant repeat verbatim.

The structure that works: real people, real history, verifiable claims

A structure we return to on client builds, because each block maps to a question an evaluator is trying to close out:

Length follows from content. Industry guidance often quotes 300 to 500 words as a floor to avoid thinness, and that is a reasonable minimum, but the better rule is that the page should be exactly as long as your verifiable facts. Four hundred words of checkable specifics outperforms twelve hundred words of mission statement.

One person can carry the whole page. Google's rater guidance does not demand a big team; it demands an identifiable one. A sole operator with a name, a face, a licence number, and a decade of dated history is a stronger trust document than a corporate page listing eight anonymous departments.

NAP consistency: the About page as the canonical record

Name, address, and phone number appear across your site footer, your Google Business Profile, directories, and social accounts. Engines confirm your existence by matching these mentions against each other, and the About page functions as the canonical on-site record they are matched against. A former address lingering on the About page while the GBP shows the new one, or a page that says Smith & Sons Contracting while the GBP says Smith and Sons Contracting Ltd., introduces exactly the ambiguity entity resolution punishes.

The fix is administrative rather than creative. Pick the canonical form of the name, the address, and the phone number. Put that form on the About page, in the Organization schema, and in the footer, then propagate it outward. Audit annually; businesses move, numbers change, and the About page is reliably the page nobody remembers to update.

Person and AboutPage schema: telling machines what the page is

Prose tells humans who you are; structured data tells machines with no ambiguity. Three types do the work on an About page. AboutPage declares the page's function. Organization carries the business entity: name, address, telephone, founding date, sameAs profile links. Person carries each named human, with jobTitle, worksFor pointing at the organization, a knowsAbout array for expertise areas, and sameAs links to external profiles. Connected through stable @id values, the three form a small graph an engine can read in one pass. A minimal working example:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "AboutPage",
      "@id": "https://example.ca/about/#webpage",
      "url": "https://example.ca/about/",
      "name": "About Example Renovations",
      "about": {"@id": "https://example.ca/#organization"},
      "mainEntity": {"@id": "https://example.ca/#organization"}
    },
    {
      "@type": "Organization",
      "@id": "https://example.ca/#organization",
      "name": "Example Renovations",
      "url": "https://example.ca",
      "foundingDate": "2009",
      "telephone": "+15195550100",
      "address": {
        "@type": "PostalAddress",
        "addressLocality": "Brantford",
        "addressRegion": "ON",
        "addressCountry": "CA"
      },
      "founder": {"@id": "https://example.ca/#jane-doe"},
      "sameAs": ["https://www.linkedin.com/company/example-renovations"]
    },
    {
      "@type": "Person",
      "@id": "https://example.ca/#jane-doe",
      "name": "Jane Doe",
      "jobTitle": "Founder",
      "worksFor": {"@id": "https://example.ca/#organization"},
      "knowsAbout": ["kitchen renovation", "building code compliance"],
      "sameAs": ["https://www.linkedin.com/in/janedoe"]
    }
  ]
}
</script>

Two implementation notes. First, the @id values are the joints of the graph; keep them identical everywhere the entity appears on your site, so the Person referenced by an article byline is provably the same Person the About page describes. Second, every sameAs URL must resolve to a live profile that corroborates the claim, because a sameAs pointing at a dead or mismatched page is worse than none. For fuller field-by-field walkthroughs, see our Person schema example and Organization schema example.

What to cut: stock-photo teams, invented myths, empty values

Some About page conventions actively damage the trust evaluation, and cutting them is faster than any addition you could make.

Stock photography posing as your team. Reverse image search is trivial for evaluators and users alike, and a smiling stock model captioned as your project manager converts the whole page from evidence into fabrication. No photo at all beats a fake one.

Invented founding myths. The garage origin story, the epiphany narrative, the founding year rounded down to sound more established. Any embellishment an evaluator can contradict against a corporate registry or an archived version of your own site poisons the credibility of the true claims sitting next to it.

Values sections with no referent. Integrity, innovation, and customer focus, asserted without a single example, occupy space a checkable fact could hold. If a value matters, attach the practice that proves it: we photograph every stage of the job and send the album with the invoice.

Award badges without an awarding body. A trophy icon labelled Best of 2024 that links nowhere and names no organization reads as decoration to a human and as noise to a machine. Name the body and link the announcement, or drop the badge.

The common thread is symmetry: everything on the page should survive an adversarial reader. That is also the standard the May 2026 core update pushed evaluation toward, and it is covered in depth in our research piece on E-E-A-T explained for 2026.

Title tags, meta description, and the light-touch keyword question

The About page is not a keyword target in the way a service page is, and treating it like one is the most common optimization mistake we find on it. Its search job is narrow: win branded queries like your business name plus about, team, founder, or reviews, and support the site-wide geographic signal. A title tag of the form About [Brand] | [Core Service] in [City] covers all of it in under 60 characters.

The meta description should do the trust job in miniature: who you are, where you operate, since when, and one credential. Searchers clicking through to an About page are in evaluation mode, so the description that wins the click is the one that sounds like a specific, real company. Beyond that, resist the urge to weave service keywords through the body. The page reads worse, converts worse, and gains nothing, because the queries those keywords serve are already assigned to pages built for them.

What neglect costs: the asymmetry of a five-hundred-word page

Here is the argument for doing this work this month rather than eventually. The About page is typically one page among hundreds, rewritable in an afternoon, yet the signals it carries are evaluated site-wide. Quality raters assess the whole site's trustworthiness partly through it. Entity resolution for every AI citation your domain might earn routes through it. Industry analyses of AI answer engines through 2025 and 2026 consistently find citation share concentrating on sources with strong, verifiable E-E-A-T signals, which makes the operator-identity gap a visibility gap rather than a cosmetic one.

The honest qualifier belongs here too: rewriting an About page will not, by itself, move rankings next week. Results depend on your industry, competition, and existing digital presence. What the page does is remove a standing objection every evaluator, human or machine, currently holds against your domain, so that the rest of your content can be judged on its merits.

A working audit: ten checks for your own About page

Run these against your live page. Every no is a task.

Ten yes answers put your About page ahead of the large majority of small-business sites we review, where the typical score at first audit sits around three or four. The gap between those states is a few working days of honest writing and one schema block, which is about as favourable as effort-to-signal ratios get in this discipline.