CiteRanger CiteRanger
E-E-A-TAuthor PagesStructured Data

Author Pages That Build Trust: Bio, Credentials, Schema and sameAs

What a good author page contains, how Google connects authors across the web with Person and ProfilePage markup, and which mistakes make a bio worthless.

Richard Roth

Richard Roth

Founder & SEO Strategist

September 22, 2026

14 min read

Light interface illustration: an author profile card with an avatar, credential rows and a row of profile chips

An article without an author is a claim without a witness. Readers notice it. Google’s quality raters are told to look for it. And AI systems deciding which sources to cite have nothing to connect the text to. The author page is where that connection is made, and on most sites it is a name, a stock photo and two sentences.

Key Takeaways
  • Google's raters are explicitly told to find out who created the content. A missing or vague author is a quality problem, not a design detail
  • A useful author page answers three questions: who is this, why should I trust them on this topic, and where else can I verify that
  • Person markup with sameAs links lets Google and AI systems connect the author to their profiles elsewhere on the web
  • Fake or inflated bios do the opposite of what they promise. Only claim what a reader could check
Keep the facts in your articles as trustworthy as your author page Claim 15 Free Credits

Why does the author page matter for trust?

Because trust needs someone to attach itself to. Google’s Search Quality Rater Guidelines dedicate a whole section to this question, and the instruction to raters is direct:

Google Search Quality Rater Guidelines, September 2025, section 2.5.2

Every page belongs to a website, and it should be clear: who is responsible for the website, and who created the content on the page you are evaluating.

Source

The raters then do something most site owners never think about: they research the author. Section 3.3 of the guidelines covers the reputation of the website and its content creators. Raters are told to search for what others say about the person, not only what the site says about itself.

Google’s helpful-content guidance makes the same point from the creator’s side. One of its self-assessment questions asks whether the content presents information in a way that makes you want to trust it. Google names three examples: clear sourcing, evidence of the expertise involved, and background about the author, for instance through a link to an author page.

Three things follow from this:

  1. Anonymous content starts with a handicap. Not a penalty, but nothing to build trust on.
  2. The author page is a research target, not a formality. Raters, journalists, potential customers and AI systems land on it to decide whether the byline means anything.
  3. What is on the page has to survive a search. If the bio says “award-winning” and a search finds nothing, the bio has hurt more than it helped.

In E-E-A-T explained we looked at why trust is the element that outweighs the other three. The author page is one of the few places where you can show all four at once. Experience through what the person has done. Expertise through credentials. Authority through mentions. Trust through verifiability.

What does a good author page contain?

A good author page answers three questions, in this order. Who is this person? Why should I trust them on this topic? And where can I check that? Everything on the page serves one of these questions.

1. Identity: name, photo, role

A real name, a real photo (not a stock image, not an AI portrait) and a role that describes what the person actually does. “Founder & SEO Strategist” says more than “Content Creator”, and “Head of Content at a 40-person SaaS” says more than “Marketing Expert”.

If the author writes under an alias, the guidelines accept that for platforms like forums, but for a company blog it weakens the signal. The whole point is that a reader can connect the name to a person.

2. Relevance: what qualifies this person for this topic

This is the part most bios skip. A bio that lists ten years of experience is weaker than one that names the actual work. The projects, the type of clients, the tools built. Google’s definition of Experience is about first-hand or life experience with the topic. The bio should show that the person has done the thing they write about.

Concrete beats general:

  • Weak: “Experienced SEO professional passionate about content.”
  • Strong: “Over 160 SEO projects since 2021, first at an agency, then self-employed. Builds CiteRanger, a tool that scans articles for outdated facts, because that was the problem he kept running into.”

The second version is checkable, specific and explains why this author writes about content freshness rather than, say, link building.

3. Verifiability: credentials, mentions, external profiles

Credentials are only useful if they are real and, ideally, checkable. Guest articles in named publications, talks at named events, certifications with a verifiable issuer, a LinkedIn profile that matches the bio. Every item you list should be something a rater, a reader or a journalist could confirm in a minute.

A LinkedIn link is the minimum. It is the profile most people will check. It is also the one Google can most easily use to connect the author across the web.

4. Body of work

The list of articles by this author is not decoration. It shows topical focus. Fifteen articles on content quality are a different signal from fifteen articles on fifteen unrelated subjects. It also gives raters and readers a way to judge consistency.

5. Context: who the author works for

The author page should link to the About page and the organisation, and the organisation should link back. This closes the loop that the rater guidelines describe: who is responsible for the site, and who wrote this page.

Quick Tip

Write the bio for a sceptical reader, not for yourself. After every sentence ask: could someone check this? If the answer is no, either add the evidence (a link, a name, a number) or cut the sentence. A short bio where everything is verifiable beats a long one with three claims nobody can confirm.

How does Google connect an author across the web?

Through structured data and consistent identity signals. Google’s documentation on Article structured data describes exactly what it needs.

For every article, the author property should carry the name and a URL. Google describes it as a link to a page that uniquely identifies the author, for example a social media profile or an about page. It adds that sameAs works as an alternative, and that it understands both when disambiguating authors.

That word, disambiguating, is the key. There are many people called Richard Roth. Google needs to know which one wrote this article. And whether it is the same one behind the other twenty on the site. The signals it uses:

  • author.url on every article, pointing to the same author page
  • Person markup on the author page with a stable @id, so the entity is the same on every page that references it
  • sameAs links to external profiles (LinkedIn and others) that confirm the identity
  • ProfilePage markup on the author page itself, which Google introduced for pages where “creators (either people or organizations) share first-hand perspectives”
  • The same name, photo and role everywhere, on the site and off it

The ProfilePage documentation shows the intended structure: the page is a ProfilePage, its mainEntity is the Person, and the Person carries name, description, image and sameAs.

A minimal, correct setup

On the author page:

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "mainEntity": {
    "@type": "Person",
    "@id": "https://example.com/author/jane-doe/#person",
    "name": "Jane Doe",
    "jobTitle": "Head of Content",
    "url": "https://example.com/author/jane-doe/",
    "image": "https://example.com/images/jane-doe.jpg",
    "sameAs": ["https://www.linkedin.com/in/jane-doe/"],
    "knowsAbout": ["Content strategy", "E-E-A-T", "Content audits"],
    "worksFor": { "@id": "https://example.com/#organization" }
  }
}

On every article:

"author": {
  "@type": "Person",
  "@id": "https://example.com/author/jane-doe/#person",
  "name": "Jane Doe",
  "url": "https://example.com/author/jane-doe/"
}

The @id is what ties them together. Without it, every article describes a new, unconnected Person object with the same name. With it, Google sees one entity referenced from many pages.

Two details from Google’s documentation are easy to get wrong. First, author.name should hold only the name, with no title or company attached. Second, sameAs should point to pages that unambiguously identify the person, which is how schema.org defines the property. A Wikipedia page, a Wikidata entry, an official profile.

Good to Know

Multilingual sites need one Person entity, not one per language. If the author page exists as /author/jane-doe/, /de/autor/jane-doe/ and /es/autor/jane-doe/, all three should use the same @id, pointing to one canonical form. Otherwise you create three authors with the same name and undo the disambiguation you were trying to achieve.

Which author page mistakes hurt more than they help?

The ones that turn out to be false when someone checks. An author page is a set of claims, and every unverifiable claim is a trust leak.

  • Stock photos or AI-generated portraits. A reverse image search reveals a stock photo in seconds. An AI portrait reads as “there is no real person here”. Both undo everything the bio says.
  • Inflated credentials. “Award-winning”, “renowned”, “industry-leading” without a named award, a named publication or a checkable fact. Raters are told to research reputation; empty superlatives are what they find nothing for.
  • Bios generated by AI. They tend to be generic, they repeat the same phrases across the web, and they contain no first-hand detail. Google’s guidance asks for first-hand expertise; a bio that could describe anyone demonstrates none.
  • Dead or mismatched profile links. A LinkedIn link that 404s, or a profile that shows a different job title, a different company or a different photo.
  • Fake authors. Invented people with invented bios. This is the most damaging version, because it is deception. The rater guidelines name deceptive information about who is responsible for the content as a reason for the lowest rating.
  • One author for everything. If a single “editorial team” byline covers medical, legal and technical articles, the byline carries no expertise signal for any of them.
  • No link between article and author page. A byline that is plain text, with no link and no author.url, gives Google nothing to connect.
Richard Roth Founder CiteRanger, SEO Strategist

The most common problem I see is not a missing author page. It is an author page that was written for the site’s own ego rather than for a reader who is trying to decide whether to believe the article. Cut every adjective, keep every fact, add a link for every claim. We rebuilt our own author page this week with exactly that rule, and it lost half its words and gained everything that matters.

AI answer engines work with entities. When a system decides whether to cite a page, part of that decision is whether the source is identifiable. And whether it matches what the system knows from elsewhere. An author recognisable as the same person across a site, a profile and a few external mentions is a source the system can place. An anonymous byline is not.

Google’s own AI features draw on the same signals as classic search. The company’s documentation on AI features says the same foundational SEO practices apply, and no special markup is needed. So the Person and ProfilePage markup you add for Google Search is the markup that helps in AI Overviews and AI Mode, too. We covered the mechanics of source selection in how AI search engines choose which sources to cite.

How do you build or fix an author page in one afternoon?

Most sites can go from “name and two sentences” to a page that actually builds trust in a few hours. In order:

Step 1: Collect the verifiable facts

Real work history with dates, named projects or clients where allowed, publications, talks, certifications, profile URLs. Discard everything that cannot be checked.

Step 2: Write the bio around the topic

Two to four short paragraphs. What the person does. What qualifies them for these topics. And why they write about them. First person or third person both work; consistency across the site matters more.

Step 3: Add the visible structure

Photo, name, role and a one-line tagline. Then the bio, a short list of areas of expertise, credentials and mentions, a profile link and the list of articles. A career timeline helps if the history is relevant to the topic.

Step 4: Add the markup

ProfilePage with a Person mainEntity, a stable @id, sameAs links and knowsAbout. Reference the same @id from every article’s author property and from the organisation’s founder or employee property where applicable.

Byline on every article links to the author page. The author page links to the About page. The About page names the author. External profiles link back to the site.

Step 6: Check it like a rater would

Search the author’s name plus the topic. Reverse-image-search the photo. Open every link on the page. Whatever a stranger would find in five minutes is what raters and AI systems find too.

Quick Tip

Keep a “proof file” for each author: a simple document listing every claim on the author page and where it can be verified. When someone updates the bio, they update the proof file. It takes ten minutes to set up and prevents the slow drift from facts to marketing copy that happens to most bios over the years.

Conclusion

An author page is where trust gets a face. Raters are told to find out who wrote the page, readers do it instinctively, and AI systems need an entity to attach a citation to. The page that works is short on adjectives and long on checkable facts. Through Person markup and sameAs links it points at the places where those facts can be confirmed.

Build the page for a sceptic, keep it as current as the articles it stands behind, and let the body of work do the rest.

A strong author page is the frame; the evidence inside the articles is what fills it, which is what showing experience covers. The E-E-A-T checklist has both as checkable points.

Frequently asked questions about author pages

Does every blog need an author page?
Every site that wants its content to be trusted benefits from one. Google's rater guidelines instruct raters to find out who created the content, and the helpful-content guidance recommends linking to an author page. For anonymous or team bylines, the trust signal is much weaker.
What structured data should an author page have?
ProfilePage markup with a Person as mainEntity, including name, jobTitle, image, url, sameAs links to external profiles and knowsAbout topics. Every article should reference the same Person via a stable @id in its author property.
Which sameAs links should I include?
Profiles that unambiguously identify the person and that a reader could check: LinkedIn at minimum, plus other official profiles if they exist and are maintained. Never link to empty, outdated or unrelated profiles.
Can I use an AI-generated author photo or bio?
You can, but it works against you. A reverse image search exposes generated photos, and generic AI bios contain no first-hand detail. Both signal that there is no real person behind the content, which is the opposite of what an author page is for.
How long should an author bio be?
Long enough to answer who the person is, why they are qualified for the topic and where that can be verified, usually two to four short paragraphs. Every sentence should be checkable; length without verifiable facts adds nothing.
Do author pages help with AI search and ChatGPT citations?
Yes, indirectly. AI systems prefer identifiable, consistent sources. A connected author entity across the site, LinkedIn and external mentions makes a page easier to place and cite. Google's AI features use the same signals as classic search, so the same markup helps there.
Find outdated facts first15 free credits, no cardStart free