Person Schema and Author Bios on a British Site: What the Documentation Says sameAs Is For, and the Entry a Register Already Holds

A byline is a claim. The markup around it is documented to do one job, which is to tie that claim to something somebody else maintains, and in Britain that is usually a public register entry.

Published by AI Knows Us · Updated 16 October 2026

Author markup is documented as an identity mechanism rather than a quality signal. Schema.org defines sameAs, read on 16 October 2026 at schema.org/sameAs, as the "URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website." That sentence tells a British firm which entries are worth putting in an author block: the ones a third party maintains and anybody can open. For a chartered accountant, a solicitor or an authorised adviser, those entries already exist on Companies House, on the Financial Services Register or in a chartered body's member directory. We have not measured what adding them does to a citation rate, and no figure of that kind appears on this page. What we have measured is which sources ChatGPT and Gemini reached for on British buying questions, and on 15 October 2026 two of the recurring ones were institutional: gov.uk appeared in 57 British readings and ico.org.uk in 28, neither of them anywhere in the United States set.

What the documentation actually says each property is for

Four primary sources, each read on 16 October 2026.

SourceWhat it states
schema.org/PersonDefined as "A person (alive, dead, undead, or fictional)." A type for an entity, with no claim about standing attached
schema.org/sameAs"URL of a reference Web page that unambiguously indicates the item's identity." The examples given are a Wikipedia page, a Wikidata entry or an official website
schema.org/author"The author of this content or rating." The page notes that HTML 5 provides a rel mechanism for authorship which "is equivalent to this and may be used interchangeably"
Google, Article structured data, page last updated 8 September 2026"To help Google better understand who the author is, we strongly recommend using the type and url (or sameAs) properties. Use valid URLs for the url or sameAs properties." It also asks you to "Make sure that all the authors that are presented as authors on the web page are also included in markup"

Google's same page, at developers.google.com/search/docs/appearance/structured-data/article, is specific about what does not belong in the name field: only the author's name goes in author.name, with the publisher, the job title and any honorific each having their own property. Google's profile page documentation, at developers.google.com/search/docs/appearance/structured-data/profile-page and also last updated 8 September 2026, describes ProfilePage markup as "designed for any site where creators (either people or organizations) share first-hand perspectives."

Put together, the documented job of an author block is disambiguation. It says that this byline, this profile elsewhere and this register entry are one person. That is a modest claim, and it is the one a British firm can substantiate.

The British entries worth naming, because somebody else maintains them

sameAs asks for a reference page that unambiguously indicates identity. A LinkedIn profile qualifies and so does a personal site, and both are maintained by the person they describe. The entries worth more in a sentence a reader can check are the ones an independent body keeps current.

  • Companies House. The register of companies and officers is free to search at find-and-update.company-information.service.gov.uk, and an officer appointment page is a stable public URL about a named person at a named firm.
  • The Financial Services Register. The Financial Conduct Authority publishes authorised firms and approved individuals at register.fca.org.uk, which is the entry a buyer checks before a first meeting.
  • Chartered and professional body directories. Member and firm directories run by the chartered institutes and the professional regulators are public, searchable and updated by the body rather than the member.

Our own British readings are the reason to take this seriously rather than a reason to claim a result. On 16 October 2026 we put 210 British buying questions to each engine, 420 British readings with none discarded, and our domain was cited in 3 of the 210 British ChatGPT readings and 0 of the 210 British Gemini readings. The pattern across both runs is that British questions reach for British institutions. A page that names the register, gives the registration and then answers the commercial question the register does not answer sits beside a source the engines already use, and the credential is a public register entry, so name the register works that positioning through for a firm rather than for a byline.

A copyable British author block

One Person node per real author, identifier entries in sameAs, joined to the firm by worksFor. Change every value, keep the shape, delete any property you will not keep current.

<script type="application/ld+json">
{ "@context": "https://schema.org", "@type": "Person", "@id": "https://example.co.uk/people/helen-marsh#person", "name": "Helen Marsh", "honorificSuffix": "FCA", "jobTitle": "Partner", "url": "https://example.co.uk/people/helen-marsh", "worksFor": { "@id": "https://example.co.uk/#organization" }, "knowsAbout": ["corporate reporting", "VAT on cross border services"], "sameAs": [ "https://find-and-update.company-information.service.gov.uk/officers/EXAMPLE/appointments", "https://www.linkedin.com/in/example-helen-marsh" ]
}
</script>

Then reference that same @id from the article itself, so the byline and the person are one node rather than two unconnected facts:

"author": [ { "@id": "https://example.co.uk/people/helen-marsh#person" } ]

Three checks that decide whether any of it is readable

  • Fetch the page without a browser. The block has to be in the HTML the server returns, because markup written by a tag manager after load is markup some agents never see. What a British site serves under each named agent is the subject of a technical GEO audit of a British site and what 220 dated fetches showed.
  • Open every sameAs URL in a private window. An entry behind a login or a search form is not a reference page anybody can reach, and a wrong entry points a matching step at the wrong person.
  • Match the markup to the visible page. Every value in the block belongs somewhere a reader can see it. A credential in JSON that the author page never mentions has no corroboration on its own site.

The question this page leaves open, and the figure that would close it

A citation rate before and after an author markup change, measured on a frozen British question set with both sample sizes printed, does not exist in our records and nothing on this page stands in for one. Closing it needs a British question set that never names the firm, a baseline with a date, a change log, a stated interval and an identical rerun, with a holdout half left untouched so the gap between the halves is readable. The round that produces it will carry its own denominators and date. Until then the defensible claim is the documented one: author markup resolves identity, and the entries worth putting in it are the ones an independent body keeps.

Questions about Person schema and author bios on a British site

Does Person schema make ChatGPT or Gemini cite an article?

Not on any evidence either operator has published, and not on ours, because we have run no test of it. The documented job of the markup is narrower: it states unambiguously that a byline, a profile elsewhere and a register entry describe one person.

Should an author bio sit on the article or on its own page?

Give each author a page with a stable URL and point the article's author property at that page's @id. Google's profile page documentation describes ProfilePage markup as designed for sites where creators share first hand perspectives.

Can a firm use one house byline for everything?

Google's Article guidance asks that all authors presented on the page also appear in the markup, each in their own author field rather than merged into one. If a piece has a named writer and a named reviewer, say so in both the visible page and the block.

Which British identifier should go in sameAs first?

The one an independent body maintains and a reader can open without an account. A Companies House officer appointment page or a Financial Services Register entry carries more than a profile the author writes themselves.

Do letters after a name belong in the author name?

No. Google's Article page asks for only the name in author.name, with any honorific going in honorificPrefix or honorificSuffix and a job title in jobTitle. The letters still belong in the visible byline.

What a British byline is actually buying

Not a score. It buys the ability for a reader, a journalist or a retrieval step to establish in one click that the person who wrote the page is a real, named, currently registered practitioner, and that the firm at the top of the page is the one on the register. In a field where 82.0% of the 20,143 citations we recorded on 16 October 2026 went to a vendor or agency own site, that single click is the cheapest separation available between a page written by somebody accountable and a page written by nobody in particular. If the page also quotes a fee, give it in pounds with the VAT position stated and the month it was true, which all 102 build spec conversations asked for in one form or another. Readers who want the underlying British numbers will find them in what AI assistants actually cite across 597 readings of ChatGPT and Gemini in three markets. AI Knows Us is paid to run that measurement and publish the pages that follow it, so read this as a supplier that would benefit from British firms caring about author identity, with the uplift figure left out because we have not measured it.

Read next

Or browse the whole archive.

See what AI says about you.

The first scan is free, it needs no account, and it asks the questions your buyers ask.

Free. No card. We ask 5 real buyer questions on 2 AI apps.

Already sure you want this? Join the waitlist. We open on 31 October 2026. It costs an email address. No card, and nothing is charged. Or talk to a person if you have a question first. Or read how we fix what it finds.