# Assistants Read Your About Page Before They Trust You

**Author:** John Morabito (Founder, /winston)
**Published:** September 20, 2026
**Reading time:** 11 minutes
**Canonical:** https://www.winstondigitalmarketing.com/playbooks/about-page-as-entity-source-for-ai/

Before anything decides whether to recommend you, it has to work out what you are. That question gets resolved from whatever page states it plainly, and on almost every site that page is the about page, which is also the page most sites treat as decoration.

## The short answer

When something needs to know what your company is, it goes looking for the page that says so. Not the homepage, which is written to sell. Not a service page, which is about one thing you do. The about page is the page a site is conventionally expected to state plainly what the business is, and that convention is why it gets read.

On most sites it is a founder story. It opens in a garage or at a kitchen table, moves through a paragraph about passion and a paragraph about commitment to quality, and closes on a promise. There may be a city name in there somewhere. A model reading that page for a sentence of the form "this company is a X in Y that does Z for W" comes away with nothing, because no such sentence exists on it.

This is a narrow problem with a cheap fix, and it sits next to two larger ones. Building your brand's identity across the whole web is entity SEO: https://www.winstondigitalmarketing.com/playbooks/entity-seo-build-your-brand-entity/ . Building the credibility of the people who sign the work is author authority: https://www.winstondigitalmarketing.com/playbooks/how-to-build-author-eeat/ . This page is about the single page both of those lean on, because the about page is the source they point back to. Corroboration only helps when there is a claim to corroborate. If the page states nothing, everything downstream is confirming a blank.

## The six facts, stated as sentences

There are six things an about page has to state. Write them as sentences, near the top, before the story. Here is the shape, using a made-up roofing company so that nothing in this table reads as a claim about a real one.

| The fact | The sentence that states it | What the page usually says instead |
| --- | --- | --- |
| What it is, and what it does | "Harlow Roofing is a residential roofing contractor. We do full replacements, repairs, gutters and skylight installation on pitched asphalt and slate roofs." | "Harlow Roofing is your partner in protecting what matters most." |
| Who it is for, and who it is not for | "We work with homeowners and small landlords. We do not do commercial flat roofs or new construction." | "We serve clients of all sizes." |
| Where it is | "The shop is in Yonkers, New York, and we work within about forty minutes of it." | A map widget, a contact form, and no city in the text anywhere. |
| Since when, and under what names | "The business has been running since 2004, and has been Harlow Roofing since 2011, when it was Harlow and Vance." | "Years of experience you can trust." |
| Who runs it | "Dana Harlow owns the business and does every estimate herself. Miguel Ortiz has been the lead installer since 2009." | A grid of nine headshots with first names. |
| How to reach a person | "Phone and email, answered between 7am and 5pm on weekdays, with the phone number written as text on the page." | "Get in touch!" above a form. |

Notice what the middle column has in common. Every one of those sentences could be wrong. That is the property that makes them worth reading. A claim that can be checked can also be confirmed somewhere else, and confirmation from more than one place is the entire mechanism by which a model gets confident enough about a company to name it.

The second row is the one people resist and the one that pays off fastest. Saying what you do not do feels like turning down work. What it actually prevents is the failure worse than not being recommended, which is being recommended for the job you do not want. A model that knows Harlow does not touch commercial flat roofs will stop putting Harlow in front of people who need commercial flat roofs, and will have a sharper idea of what to put Harlow in front of instead.

## Why a paragraph of adjectives resolves nothing

Dedicated. Passionate. Innovative. Customer-focused. These are not assertions about a company. They are the same words on every page in the category, which means they cannot distinguish one company from another, which is the only job that matters when something is trying to work out which company you are.

There is a quick test for this, and it is unkind.

> The paste test: take any sentence off your about page and ask whether your closest competitor could paste it onto theirs without it becoming false. If they could, that sentence carries no information about you. Run it down the whole page. Most about pages survive almost intact, which is the problem stated as an exercise rather than an opinion.

The second reason adjectives fail is that nothing can confirm them. "Based in Yonkers since 2004" can be checked against a business registry, a Google Business Profile, a local news mention, an old permit record. "Passionate about quality" can be checked against nothing, so it accumulates no confidence no matter how many of your own pages repeat it. Your own site is one witness making one statement. The claims that can gather other witnesses are the ones worth writing, which is why the about page and third-party corroboration are really one project seen from two ends: https://www.winstondigitalmarketing.com/playbooks/trusted-domains-seo-citation-reciprocity/

The third reason is mechanical. What gets retrieved is a passage, not a page, and the passage that extracts cleanly is a heading followed directly by an answer. An about page that hides its one real fact in the fourth paragraph of a narrative has no clean chunk to lift, even if the fact is in there. The same structural rules that apply to any page you want quoted apply here, and they are in how to write content AI actually cites: https://www.winstondigitalmarketing.com/playbooks/how-to-write-content-ai-cites/

None of this is an argument against narrative. A founder story with the year, the city, the first customer and what the business did before it did this is full of checkable facts and reads better than a table. The problem is not that the page tells a story. It is that most stories on most about pages contain no claim that could be wrong.

## The machine-readable twin

Everything in that six-row table should also exist as `Organization` schema on the same page. Not a different set of facts written for machines. The same claims, rendered twice, once for a person and once for a parser. When the two versions disagree, you have manufactured the exact ambiguity the page was supposed to remove.

```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://harlowroofing.example/#org",
  "name": "Harlow Roofing",
  "legalName": "Harlow Roofing LLC",
  "alternateName": "Harlow and Vance Roofing",
  "url": "https://harlowroofing.example/",
  "description": "Residential roofing contractor in Yonkers, New York. Full replacements, repairs, gutters and skylight installation on pitched asphalt and slate roofs.",
  "foundingDate": "2004",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "118 Example Avenue",
    "addressLocality": "Yonkers",
    "addressRegion": "NY",
    "postalCode": "10701",
    "addressCountry": "US"
  },
  "telephone": "+1-914-555-0142",
  "email": "dana@harlowroofing.example",
  "founder": { "@id": "https://harlowroofing.example/about/#dana" },
  "areaServed": [
    { "@type": "City", "name": "Yonkers" },
    { "@type": "AdministrativeArea", "name": "Westchester County" }
  ],
  "sameAs": [
    "https://www.linkedin.com/company/harlow-roofing/",
    "https://www.bbb.org/us/ny/yonkers/profile/roofing-contractors/harlow-roofing"
  ]
}
```

Four things about that block are worth saying out loud.

- **One stable identifier, reused everywhere.** The `@id` is a permanent name for the company inside your own markup. Every other node that needs to refer to the company points at that string rather than describing the company again. Two descriptions of one company in one document is a parsing problem you created yourself. The full connected-graph pattern is in schema markup for AI engines: https://www.winstondigitalmarketing.com/playbooks/schema-markup-for-ai-engines-2026/
- **The `alternateName` field is doing real work here.** It is where the old trading name goes, which is how a parser reconciles the decade of records out there that still say Harlow and Vance. Most sites leave it empty and then wonder why their old name keeps surfacing as a separate business.
- **Every `sameAs` entry should be a live profile you control or that demonstrably describes you.** Each one is a witness you are inviting somebody to go check. A dead link or a profile that says something different is not a neutral entry, it is a failed confirmation. The reasoning behind the whole array is in the entity SEO playbook: https://www.winstondigitalmarketing.com/playbooks/entity-seo-build-your-brand-entity/
- **Use `LocalBusiness` instead if customers come to you.** A place with a door, hours and a service radius wants the local type with the hours specified properly, field by field, matching the Google Business Profile exactly. That pattern is in the LocalBusiness schema guide: https://www.winstondigitalmarketing.com/playbooks/local-business-schema-guide/

The question people ask here is whether to use `AboutPage`. You can, and it is fine, and it is not the part that matters. `AboutPage` tells a parser what kind of page it is looking at. `Organization` tells it what the company is. The second one is the claim you care about, so if you are only going to get one of them right, get that one right.

## When your four descriptions disagree

Your about page is not the only place your company describes itself. There are at least four, and they drift apart in predictable ways.

| Surface | What usually drifts | Why it matters |
| --- | --- | --- |
| The about page | Nothing, because nobody edits it, which becomes its own problem the moment a fact changes | It is the page everything else gets compared against |
| The site footer | Legal name, suite number, phone, hours | It appears on every page, so by volume it outvotes the about page |
| The Google Business Profile | Category, hours, service area, and a name with a keyword appended to it | It is the most independently verified of the four, so it tends to win a disagreement |
| Directory and association profiles | The old address, the old phone, the name from before the rename, a service list from two pivots ago | You cannot see them from your own site, so they rot with nobody watching |

Here is what a disagreement actually costs. A model has several statements about one company, made at different times, at different levels of authority, with no reliable way to tell which is current. Its options are all worse for you than agreement: hold the fact with low confidence and leave it out of the answer entirely, or pick the best-corroborated version, which is frequently the oldest one, because an old record has had more years in which to be copied. Neither of those looks like a penalty from where you sit. They look like being left out of answers you should be in.

The keyword-stuffed profile name deserves its own sentence. A Google Business Profile called "Harlow Roofing | Best Roofer in Westchester" against an about page that says "Harlow Roofing" is two names for one company, introduced at the surface where a name conflict is most expensive. It is also against Google's own guidelines, which is a separate risk with the same fix.

The fix is unglamorous. Pick the canonical form of every fact once. Keep it written down in one place, a file rather than somebody's memory. Update all four surfaces from that file, and treat the file as the thing you edit when a fact changes. For the profile itself, the field-by-field version is in Google Business Profile optimization: https://www.winstondigitalmarketing.com/playbooks/google-business-profile-optimization/

> Finding the records you forgot about: search your phone number in quotes. Then your old phone number. Then your old address, and your former business name if you have one. What comes back is the set of records describing your company that you did not write and mostly cannot edit. Fix the ones that have a claim form. For the rest, the only lever you have is your own page stating the change plainly, which is a good reason for that sentence to exist.

## Name real people, with real roles

The stock team grid is nine circular headshots, first names, one-word titles, and in the worse cases the names are baked into the image files, so there is no text on the page at all. A human skims it and learns nothing. A parser reads it and finds nothing, because there is nothing there to read. If your team section is images, the fastest improvement available to you is turning it into sentences, and the second fastest is in image SEO and alt text: https://www.winstondigitalmarketing.com/playbooks/image-seo-and-alt-text-for-ai/

What works is boring: who runs the business, what they actually do day to day, how long they have done it, and the one or two things they are specifically known for. "Dana Harlow owns the business and does every estimate herself" is a checkable claim about a named person with a role. "Dana, Operations" is a caption.

Then keep the person consistent. One name string, spelled the same way on the about page, in bylines, in the footer, and on LinkedIn. One `Person` node with a stable identifier that the `Organization` node points at, rather than a fresh description of the same human on every page they appear. The full version of that work, including what belongs on a bio page, is author authority: https://www.winstondigitalmarketing.com/playbooks/how-to-build-author-eeat/ , and when the business is essentially one person, the identity work merges into GEO for personal brands: https://www.winstondigitalmarketing.com/playbooks/geo-for-personal-brands/

You do not need nine people for this. One named person with a real role beats a grid of nine faces with nothing attached to them. Add people when there is something true and specific to say about each one, not to look larger than you are.

## A page that reads as a record

The difference between an about page that helps and one that does not is not tone, and it is not length. It is whether the page can be wrong. A record makes claims and takes on the obligation to keep them current. Marketing copy makes no claims and therefore has nothing to maintain, which is exactly why it is so comfortable to write.

The test is a reconstruction. Hand your about page to somebody who has never heard of your company and ask them to write down what it does, who for, where, since when, who runs it, and how to reach a person. If they cannot fill in all six from the page alone, without inference, it is not a record yet. Most people find they can fill in two.

Two habits keep it working after you have fixed it. Date the page, because almost all of the conflicting information about your company is old information, and a date is how a reader and a parser tell recent from stale. And state your changes explicitly rather than quietly swapping the facts: the rename, the move, the merger, the service you no longer offer. One sentence saying Harlow Roofing was Harlow and Vance until 2011 reconciles a decade of records you cannot edit. Silently updating the name leaves those records looking like a different company.

This is also the form the reference sources want. A Wikidata statement needs a source, and a stable, dated page that states plain facts about a company is the source an editor reaches for, which is the mechanism behind Wikipedia, Wikidata and the knowledge sources AI trusts: https://www.winstondigitalmarketing.com/playbooks/wikipedia-and-knowledge-sources-for-ai/ . You do not need a Wikipedia article for this to pay off, and you probably do not qualify for one. You need one page that is worth citing as the origin of a fact.

An honest note, since you can go read ours. Our about page (https://www.winstondigitalmarketing.com/about/) opens with an argument rather than a definition. The six facts are on it, further down and in the schema graph, and I would write it that way again, because the page has a job besides being a record. The trade is worth naming rather than pretending it does not exist: if your about page has to sell, put the record above the argument, or give it its own heading so it can be found. A page can do both jobs. What most about pages do is neither.

## What to do first

This is a half-day of work and it does not need a project plan. In order:

1. Run the reconstruction test on your own about page and note which of the six facts are missing. Most of the work is deciding that.
2. Write the missing sentences and put all six near the top, under a heading, before the story. Twenty minutes, and it is the highest-value twenty minutes on this list.
3. Make the `Organization` schema state the same six things, with one stable `@id`, a filled-in `alternateName` if you have ever traded under another name, and a `sameAs` array of profiles that are live today.
4. Compare the page against your footer and your Google Business Profile field by field. Where they differ, decide which version is canonical and fix it in one place that the others are updated from.
5. Search your old phone number, old address and former name in quotes. Claim what you can, and add the reconciling sentence to the about page for everything you cannot.

## Hiring someone for this

Nobody sells an about page rewrite on its own, so this normally arrives inside an entity or GEO engagement, which is fine as long as the person doing it has thought about it. Three questions sort that out quickly. Ask what an about page should contain, and count how many of the six facts come up before the word "story" does. Ask what they would do about a directory listing carrying your 2017 address that you cannot edit, and listen for whether your own page stating the change is part of the answer. Ask whether `AboutPage` or `Organization` does the work, which is a small question that separates people who have written this markup from people who have read about it.

On our side the pricing is published rather than quoted after a call, and every engagement is a written scope with the number attached before you pay anything. It is on the pricing page: https://www.winstondigitalmarketing.com/pricing/ . The done-for-you version of this sits inside our generative engine optimization service: https://www.winstondigitalmarketing.com/services/generative-engine-optimization/ , and if you want to see how your about page reads to a machine before you talk to anybody, put it through the free audit: https://www.winstondigitalmarketing.com/audit/

## Frequently asked questions

### Does my about page actually matter for AI search?

It matters more than its traffic suggests, because it is not competing for a query. It is the page that gets consulted when something needs to establish what your company is before it decides whether to recommend you. A model assembling an answer about your category has to resolve you to an entity first, and the about page is the conventional place a site states that plainly. If it does not, the resolution happens from whatever else is available, which is usually a directory record you have never read. The page gets very little traffic and does a lot of work, which is why it is so often the least maintained page on the site.

### What should an about page say?

Six things, in plain sentences, near the top. What the business is and what it actually does, stated in the category a customer would use. Who it is for, including who it is not for. Where it is. How long it has been running, and under what names. Who runs it, by name and role. How to reach a person, with hours during which someone answers. Everything else on the page is optional. If the story, the mission and the values come first, put a short section above them that states the facts under its own heading, so the record is not buried in the narrative.

### Should I use AboutPage or Organization schema on my about page?

Both, doing different jobs, and if you only do one, do Organization. AboutPage tells a parser what kind of page this is. Organization tells it what the company is, which is the claim you actually care about. Give the Organization node a stable identifier on your domain, state the same facts the visible page states, and add a sameAs array pointing at the profiles you control. Then have the page reference that node rather than declaring the company again in different words. Two descriptions of one company in one document is the ambiguity you were trying to remove.

### What is wrong with a founder story on the about page?

Nothing, as long as it is not the only thing there. The problem is not narrative, it is that most founder stories contain no claim that could be wrong. Take a sentence off your about page and ask whether a competitor could paste it onto theirs without it becoming false. If they could, that sentence carries no information about you, and most about pages survive that test almost intact. A story that includes the year, the city, the first customer and what the business did before it did this is full of checkable facts. A story about passion and commitment is not.

### What happens when my about page and my Google Business Profile disagree?

You have given a model several statements about one company with no way to tell which is current. The resolutions available to it are all worse for you than agreement: hold the fact with lower confidence and leave it out of the answer, or pick the version with the most corroboration, which is frequently the oldest version because old records have had longer to be copied. The Google Business Profile tends to carry weight because it is independently verified, so a name there with a keyword appended, against a clean name on your site, creates a conflict at the surface you least want one on. Pick the canonical form of every fact once, keep it in one place, and update all four surfaces from it.

### Do I need a team page with photos of everyone?

No, and the photo grid is usually the weakest version of this. Nine circular headshots with first names and one-word titles give a reader nothing to check, and when the names are baked into the images there is nothing there to read at all. One named person with a real role, a tenure and a sentence about what they actually do is worth more than a grid of nine faces. Add people because there is something true and specific to say about each one, not to look bigger than you are.

### How is this different from entity SEO and author authority?

Scope. Entity SEO is the whole identity of your brand across the web, including the profiles, the reference sources and the third-party mentions that corroborate it. Author authority is about the credibility of the people who sign the work. This is one page, and it is the page both of those depend on, because it is the source they point back to. Fixing the about page is the smallest piece of that work and the one to do first, since corroboration only helps once there is a clear claim to corroborate.