What should an About page say so that AI recognises you?
Write it as a passage that makes sense without context: who made it, when it started, where, what the product is, who it is for, and what it is not. When AI answers "what is X", it first has to decide which entity you mean, and the About page is where you can settle that yourself.
One limit first: we found no official documentation from OpenAI, Anthropic or Perplexity saying they read Organization structured data, so this is unverified. Google's documentation only says this markup helps it understand an organization. The advice below rests on this reasoning: the About page is among the first pages retrieved when your name is searched, and the clearer it is, the less likely the wrong thing is lifted. That is inference.
| Fact to state | How to write it in the body | Matching Organization property |
|---|---|---|
| Name and alternate names | The full product name, the short name people use, and common misspellings | name, alternateName |
| What it does | The first sentence is the definition: what it is, who it is for, the one thing it does | description |
| Who made it | The company or team name; for a solo developer, a name or handle and a way to reach them | legalName, email |
| When | The year and month it started and when it launched | foundingDate |
| Where | The city and country, even if it is only a mailing address | address |
| Official profiles elsewhere | URLs of the code repository, company page and social accounts | sameAs |
| What it is not | One explicit sentence: not X, not affiliated with X | description（正文里更重要） |
The property names on the left are all listed as recommended properties in Google's Organization documentation (checked 2026-11-06). The documentation also states that Organization markup is not required and has no required properties.
Where does the Organization markup go, and what goes in sameAs?
On the home page or a page that describes the organization, such as About; not on every page. That is what Google's documentation recommends. sameAs holds pages on other sites with more information about you, such as social and code-hosting profiles, and you can list several; name should match your site name.
List only pages you really own and that really exist. A Wikipedia entry that has not been created is worth nothing here. The URLs in this example are placeholders; replace them with your own:
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.com/#org",
"name": "ExampleApp",
"alternateName": "ExampleApp AI",
"legalName": "Example Studio Ltd.",
"url": "https://example.com/",
"logo": "https://example.com/logo-512.png",
"description": "ExampleApp is an AI tool that does one specific thing for one kind of user. Not affiliated with Example Inc.",
"foundingDate": "2026-03",
"address": { "@type": "PostalAddress", "addressLocality": "Singapore", "addressCountry": "SG" },
"email": "hello@example.com",
"sameAs": [
"https://github.com/example-studio",
"https://www.linkedin.com/company/example-studio",
"https://x.com/exampleapp"
]
}
Everything stated in the structured data must also be said in the body. If the name, founding date or place do not match, whoever reads it becomes less sure who you are.
How do you tell yourself apart from a bigger brand on the About page?
Say it in one explicit sentence: what this site is, what it is not, and who it has no relationship with. When names collide, this sentence does more than any markup, because it is plain text that people and machines can both read. The full method is in What to do when your product name collides with a bigger brand.
Gamma AI Slide (gammaslide.com) and gamma.app are two different products with very similar names. Its disambiguation page, gammaslide.com/gamma-slide-vs-gamma-app (read 2026-11-06, page dated as updated 2026-11-05), handles it like this:
| What the page does | Why it helps AI |
|---|---|
| The second sentence says this site is not made by the makers of gamma.app and has no affiliation or endorsement with them | When asked "what is the difference between gamma slide and gamma", there is a ready sentence to quote |
| It states that it does one thing: presentations, paid by credits, not a subscription | Keeping its scope narrow means the other things the other product does are not attributed to you |
| The other product's prices and features were not copied: the page says that on 2026-11-05 its attempt to read their pricing page was refused (403), so that column says "check their site" | It does not state facts it could not check; the source and date are on the page |
The page also exposes a gap. On 2026-11-06 we found that the Organization data on the gammaslide.com home page has only four fields (name, url, logo and @id), with no description, sameAs or foundingDate, and gammaslide.com/about returns 404, so there is not yet a page dedicated to "who we are". This is a known to-do, not a recommended practice.
How do you write an About page step by step?
1. Write the definition as the first sentence
Format: "Name is a product for whom that does what, made by whom in where." Every later paragraph just fills in this sentence.
2. List the facts, one per line
Founding date, location, contact email, team size (if you have it) and launch date. Leave out what you do not have; do not invent it.
3. Write one sentence that tells you apart
Only products whose names collide need this step. Write "not X" and "no relationship with X"; do not say bad things about the other party.
4. Add the Organization markup and check it against the body
Put it on this page (the home page also works). Adapt the example above and check that every field has a matching sentence in the body.
5. Put only real official profiles in sameAs
The code repository, company page and social accounts. Third-party coverage of you does not go here; put it in the body with a link.
6. Link to this page from the home page navigation or footer, and make sure it is in the sitemap
Use the crawler check in AI visibility audit checklist to confirm AI crawlers can read it, then see How to write structured data to check how the markup is written.
Once the About page is done, if you want other sites to describe you the same way, see Does a small product need Wikipedia and Wikidata and How to write content AI will quote.
FAQ
Do I have to add Organization structured data?
Google's documentation says it is not required and has no required properties. Whether to add it depends on whether you need to make the name, logo and official profiles clear; what matters is that the body says the same things first.
Which URLs should go in sameAs?
Google's documentation describes pages on other sites with more information about you, such as social accounts and review-site profiles. Include only pages you really own and that really exist.
Does Organization markup go on every page?
Google's documentation recommends the home page or a page that describes the organization, such as About; it does not need to be on every page.
Do AI search products read Organization data?
We found no official documentation from OpenAI, Anthropic or Perplexity saying so; unverified. Google's documentation only says it uses it to understand organizations.
How do I write the About page if it is just one person?
Give your name or handle, country, when you started, a contact email, and links to your code repository or social accounts. A real small-team description is easier to get right than a vague company blurb.
Sources
- Google Search Central · Organization structured data （Viewed 2026-11-06; the page shows no update date）
- Gamma AI Slide · Gamma AI Slide vs gamma.app: what is the difference? （Read 2026-11-06; the page is dated as updated 2026-11-05）
- Gamma AI Slide · gammaslide.com 首页的 Organization 数据 （Read 2026-11-06）
- kagentx evaluations: the data on the case study pages; each example gives its date.