richresults.ai is a specialist AEO agency providing AEO and GEO for experts: specialist lawyers, physicians, architects, consultants, winemakers, trainers, founders and other experts whose documented expertise is the reason a client chooses them. richresults.ai builds the expert as a distinct entity, separate from the firm, clinic, studio or company, and connects fields of expertise, publications, talks, cases and external sources to the expert who actually holds them.
The organization is usually well known to AI systems. The expert behind it is described through the organization, confused with a namesake or missing from the answer. richresults.ai builds the Entity Architecture that changes this: an expert profile as entity home, pages per field of expertise, the publication list as its own entity, Person JSON-LD with worksFor, sameAs and knowsAbout, Retrieval Answers and FAQs in the language of the field and the alignment with the external sources that confirm the expertise. Full technical implementation on the existing website is included, so ChatGPT, Perplexity, Claude, Gemini and Google AI Search identify, attribute and recommend the right expert.
01 The problem
The service belongs to the organization. The expertise belongs to the expert.
AI systems answer recommendation questions in a specialist field from what they can read about the expert. In most cases they read the organization: its services, locations, reviews and structured data. The expert appears as a name on a team page. richresults.ai builds the expert as a readable entity of its own, states the relationship to the organization explicitly and attributes fields, publications and cases to the expert, so the recommendation lands with the expert who holds the expertise.
The full analysis of expert and organization as two entities, roles over time, namesakes, fields of expertise and external sources is in the guide AI Visibility for Experts →
02 What richresults.ai builds for experts
The expert profile as entity home
richresults.ai builds one page that is the authoritative home of the expert's identity: name, current role with its period, former roles with their periods, the relationship to the organization, qualification and registration where applicable, stable identifiers and the external profiles that belong to the expert. Every other page about the expert, on the organization's website and in external sources, points back to this one. AI systems get one place where the expert is defined.
One page per field of expertise
Each field the expert holds gets its own page with its own statements, the publications and cases that belong to that field and the questions people actually ask in it. A lawyer in media law and commercial law gets two pages, not one description that stacks both. AI systems then answer a question in one field with the expertise that belongs to that field, and the expert is retrievable for each field separately.
Publications, talks and cases as their own entities
Books, articles, talks, court cases, projects and vintages are built as entities with the expert as author or responsible role, each with its date, publisher or venue and the field it belongs to. The publication list stops being a paragraph in a biography and becomes a structure AI systems can read and attribute. Where the work was done for a former organization, the period makes the attribution correct in both directions.
The relationship to the organization
richresults.ai states the relationship between expert and organization as a fact with a period: works for, founded, leads, is a partner in, left. The organization keeps its services, locations, team and reviews. The expert keeps fields, qualification, publications, talks, cases and awards. Internal links carry the relationship in both directions, from the team page to the expert's entity home and back, so AI systems read expert and organization as connected entities, never as one.
Person JSON-LD and Structured Data
richresults.ai implements the Person JSON-LD for the expert with worksFor, sameAs and knowsAbout, the Organization JSON-LD for the organization and the relationships between them, together with the Structured Data for fields, publications, talks and cases. The structure mirrors the visible content. It does not assert a role, a field or a publication the pages do not state. Every schema is validated against the Google Rich Results Test and Schema.org.
Retrieval Answers, FAQs and AEO Copywriting
Titles, meta descriptions, entity descriptions, FAQs and Retrieval Answers are written from the questions people actually ask in the expert's field, in the terms the field uses. Each statement names the expert as its subject and stands on its own as an extractable fact. The expert's pages then answer the recommendation question directly instead of leaving it to inference.
Alignment with external sources
Registries, publisher pages, conference programs, co-author listings, award pages and professional profiles confirm specific facts about the expert. richresults.ai identifies which external source confirms which statement, aligns name, role, field and organization across the expert's pages and those sources and connects each source to the statement it actually supports. Corroboration outside the expert's control is attributed, never invented.
03 The Expert Stage as the method behind the work
Documented expertise becomes the answer.
The Expert Stage is the method richresults.ai applies where an expert is a reason to be chosen. On an expert's website it takes the form described above: the entity home, the pages per field, the publications as entities, the Person JSON-LD and the external sources connected to the statements they confirm. The Expert Stage builds on expertise that actually exists and attributes it to the expert who holds it. It does not create expertise and does not invent authority.
04 Where AI gets experts wrong
Four errors with one cause.
AI systems describe the expert through the organization's offering, present a former role as current, merge two experts with the same name or credit a colleague with expertise that belongs to someone else. All four come from the same cause: the facts exist, and their attribution is left to inference. richresults.ai closes these gaps as part of the AEO and GEO work for the expert. The guide AI Visibility for Experts describes each of them in detail.
05 Result
A clear model of the expert for AI systems.
AI systems receive a clear model of who the expert is, which organization the expert works in and in which role, which fields the expert holds, which publications, talks and cases belong to the expert and which external sources confirm it. ChatGPT, Perplexity, Claude, Gemini and Google AI Search then name the expert for the questions in the field the expert actually has something to say about. How this works in practice is documented in the case studies.
How do ChatGPT, Perplexity, Claude, Gemini and Google AI Search currently describe you as an expert? richresults.ai analyzes which questions in your field surface you, whether you are described through your organization or through your own fields, which publications and cases are attributed to you and which sources shape those answers. Request an analysis.
