By Samuel Anan | Generative AI Leader | London, UK

An About page should answer a practical question: who is responsible for this work, and what can a reader verify?

For a London startup, SaaS company, e-commerce brand or AI consultancy, that means more than publishing an ambitious founder story. The page should connect the business name, people, roles, offer, location and important claims to evidence that fits each statement.

This can make the business easier for customers, journalists, partners and researchers to assess. It can also support a clearer public identity across search and AI-assisted discovery. It does not guarantee that a search engine or AI system will rank, cite or recommend the business.

Google's current guidance for generative AI features treats GEO and AEO as extensions of established search practice rather than special shortcuts. A verifiable About page should follow the same principle: make the information useful and reliable first, then make its structure technically clear.

What makes an About page verifiable?

Verifiability does not mean publishing every personal detail or linking every sentence to an impressive domain. It means giving an appropriate verification route for the facts that matter.

A useful route proves the narrow claim beside it:

  • A credential link can confirm that a named qualification was awarded.
  • A project page can show the work performed and the role played.
  • A Companies House record can show registered company particulars.
  • A customer quotation can describe one genuine experience.
  • A publication can establish that a named article appeared there.

None of these proves everything. Company registration does not prove expertise. A certificate does not prove every performance claim. One testimonial does not establish a typical outcome. The page becomes more credible when it preserves those boundaries.

The About page verification matrix

Use this matrix to decide what the page should say, where a reader can check it and what the evidence does not establish.

Reader's questionWhat the page should stateSuitable verification routeWhat the route does not prove
Who is behind the work?Full public name, current role and responsibilityAuthor page, current professional profile or official organisational pageExpertise in every subject discussed
Which business or project is involved?Legal name, trading name and relationship between the namesOfficial business page or relevant public company recordService quality, endorsement or market leadership
What does the business do?Current services, products, audience and important exclusionsService pages, current product documentation or approved scopeResults not shown by those records
Why is this experience relevant?Specific roles, dates, responsibilities and areas of workProject credits, publications, credential pages or permissioned case materialUniversal suitability or guaranteed outcomes
Where does the business operate?Actual base, service area and remote or in-person availabilityContact page, current business information or location-specific service pageThat every service is available everywhere
Is a qualification or membership genuine?Exact name, issuer and status of the credentialIssuer-hosted credential or current membership directoryEndorsement beyond the credential's real scope
Is customer evidence genuine?The experience described, relevant service and relationshipOriginal record, permission and contact details held internallyThat every customer will receive the same result
How can someone make contact?Professional contact route and accepted enquiry typesWorking contact page, form or business emailA need to publish private personal details
Is the information current?Meaningful review or update dateInternal change log and current linked recordsThat changing a date alone makes the content accurate

The matrix is deliberately claim-specific. A page should not borrow the authority of one strong record to support unrelated statements elsewhere.

Make the identity and relationships explicit

Start with the name a customer, editor or partner should use. If the public brand, legal entity, founder name and project names differ, explain how they relate.

For example, Sparlab publicly identifies me as its founder and Yieldberg Studios as its builder. A clear account of those roles is more useful than presenting the three names without explanation.

The relationship should be accurate and proportionate. It is background about responsibility, not independent evidence of every product claim.

This matters especially for startup brands. A founder may be the strategist, spokesperson and service provider while a separate studio, product or trading name appears elsewhere. Leaving readers to infer those relationships creates avoidable uncertainty.

The page should answer:

  • Who is speaking?
  • Which organisation or project are they speaking for?
  • What work are they responsible for?
  • Which claims belong to the person, the company or a customer?

Google's people-first content guidance encourages accurate authorship information and bylines that lead to useful background about the author. It also warns against fabricated profiles and false credentials. The lesson is not to decorate every article with biography. It is to make responsibility inspectable where readers would reasonably expect it.

Separate identity, capability and outcome evidence

About pages often weaken when different kinds of evidence are treated as interchangeable.

Identity evidence establishes who a person or business is. It may include a public professional profile, a legal company record or an issuer-hosted credential.

Capability evidence shows the work someone can perform. It may include a detailed method, a relevant project role, a technical explanation or a portfolio item with clear scope.

Outcome evidence concerns what changed. It needs an appropriate baseline, period, measure, method and explanation of other factors that may have influenced the result.

Independent assessment comes from a party outside the business. It may include editorial coverage, an independently administered credential or a third-party review. The relationship and limits still matter.

A page can contain all four, but each should keep its proper meaning. A founder biography is identity evidence. It is not a substitute for a measured case study. A client quotation can describe one customer's experience. It does not prove a universal conversion or revenue claim.

Describe experience without manufacturing authority

Relevant experience should help the reader assess the current work. State the role, subject, period and responsibility clearly enough that the reader can understand why it belongs.

Instead of:

A recognised leader transforming brands through AI.

Use a more inspectable account:

Advises startup brands on AI-search visibility, content evidence and the relationship between SEO, GEO and AEO.

The second statement is narrower. It identifies the work without claiming independent recognition that has not been shown.

The same standard applies to first-person writing. A method article can explain how I approach a problem without inventing a client history. A clearly labelled illustration can demonstrate the reasoning without being presented as a customer result.

Treat "generative AI leader" as a claim, not a keyword

"Generative AI leader" is not made credible by repeating it in a heading, author biography and page description. It is a comparative or reputational claim, so a careful reader will reasonably ask what supports it.

Evidence might include:

  • original research with a transparent method;
  • a named framework that other people can inspect and apply;
  • relevant work with clearly explained responsibility;
  • current qualifications linked to the issuer;
  • independent citations, contributions or speaking engagements; and
  • case evidence whose conclusions match the underlying records.

If that evidence is still developing, use a precise description such as "generative AI strategist", "AI-search visibility specialist" or the exact service performed. Leadership is stronger when a body of useful work allows other people to reach the conclusion.

This is particularly important in automation and agentic AI, where a polished product description can obscure who reviews the output, handles exceptions or remains accountable when an automated action is wrong. If the work involves agents or automated publishing, identify the human responsibility as clearly as the technology.

Make London relevant rather than decorative

If the business is based in London, say what that fact means for the reader. It might affect in-person availability, service area, market experience, time zone or the communities served.

"London-based" should not be inserted simply because it is a target phrase. A useful description may say that the business is based in London and works with clients elsewhere, or that a particular service is available in London while consulting is delivered remotely.

For a UK limited company, GOV.UK lists company information that must appear on company websites, including the registered number, registered office address, place of registration and limited-company status. Those requirements apply to limited companies and do not mean every detail must sit in the main About-page narrative.

The Companies House public register can provide a route to registered particulars such as company status, officers, previous names and filings. Treat it as a public record, not as an endorsement or proof of service quality.

Handle credentials, badges and testimonials precisely

Name a credential exactly as the issuer names it. Link to the issuer's public verification page where one exists. Explain the subject or level only when the issuer's information supports that description.

A badge should not imply government approval, professional regulation or membership that does not exist. The same applies to logos from clients, publishers and technology providers. State the real relationship rather than allowing the visual mark to create a broader impression.

Testimonials require their own evidence. ASA and CAP guidance says marketers should hold documentary evidence that a testimonial is genuine, retain contact details for the person or organisation giving it and normally have permission to use it. Claims inside the testimonial must not mislead, and relevant commercial interests should not be hidden.

Keep the testimonial attached to the service and experience it actually describes. Do not edit a modest comment into a market-wide performance claim.

Provide a professional contact route without oversharing

Verifiability is not an instruction to publish a home address, private telephone number, date of birth or unrelated personal history.

The ICO's data-minimisation guidance says personal data should be adequate for the purpose, relevant to it and limited to what is necessary. For an About page, a professional email address, contact form or business telephone number may provide a suitable route without exposing unnecessary private information.

The page should also explain what kinds of enquiries the business accepts. A clear scope saves the reader from guessing whether the next step is a strategy session, product enquiry, media request, partnership proposal or support question.

Structure the page for people first

Good structure helps every reader find the evidence they need. The W3C Web Accessibility Initiative recommends informative page titles, headings that convey meaning and link text that describes its destination.

For an About page, that means:

  • use a specific page title rather than "Our Story" on its own;
  • make the main person or organisation clear near the beginning;
  • organise roles, services, evidence and contact details under descriptive headings;
  • label links with the credential, publication, project or record they open;
  • add meaningful alternative text to informative images; and
  • keep the next step understandable without relying on design alone.

"View Google AI Professional Certificate" gives a reader more information than "Verify here". "Read the AI-search measurement methodology" is more useful than "Learn more".

Add structured data only after the visible facts are correct

Structured data can express information that already appears on the page. It cannot make an unsupported biography true.

Google lists an author page, an "About Me" blog page and an employee page as valid uses for `ProfilePage` structured data. Where the page represents a business rather than one person, `Organization` structured data may be appropriate. The visible content and the markup should describe the same entity, relationships and current facts.

Use the technical layer to reduce ambiguity, not to manufacture authority. Google states that correctly implemented structured data does not guarantee a search feature, and its generative AI guidance does not require special AI markup.

Maintain the page as the business changes

An About page can become misleading without anyone adding a false statement. A project changes status, a qualification expires, a service closes or a contact route stops working while the page remains untouched.

Review the page whenever there is a material change to:

  • names, trading relationships or responsibilities;
  • services, products or service areas;
  • credentials, memberships or awards;
  • testimonials, case studies or permissions;
  • contact details and links; or
  • structured data that reflects those facts.

Record the substantive review date internally. Change the visible update date only when the page has genuinely been reviewed or improved.

A ten-question About page check

Before publication, ask:

  1. Can a first-time reader identify the person or organisation responsible for the work?
  2. Are trading names, products and project relationships explained?
  3. Does every credential use its correct name and verification route?
  4. Are experience claims specific about role and scope?
  5. Are performance claims supported by appropriate outcome evidence?
  6. Are testimonials genuine, permissioned and kept in context?
  7. Is the London or wider service area stated accurately?
  8. Can a reader contact the business without unnecessary personal information being exposed?
  9. Do titles, headings, links and structured data match the visible facts?
  10. Is there an owner responsible for reviewing the page when the business changes?

A good About page does not prove that a person or business is the best choice for everyone. It gives the reader a reliable account of who is responsible, what they do and how important claims can be checked.

That is useful for customers and publishers. It is also the right foundation for AI search, GEO and AEO: not a promise of visibility, but public information that is clearer, more accountable and easier to verify.

If your About page contains strong claims but weak verification routes, begin with the matrix above. The first improvement is often not a longer biography. It is a more precise connection between the statement and the evidence.

References

About Samuel Anan

Samuel Anan is a London-based generative AI leader working across AI search, generative engine optimisation (GEO), answer engine optimisation (AEO), workflow automation and agentic AI. He writes for startups, SaaS teams, and e-commerce businesses selling through Amazon and Shopify.