LLM Best Practices

Author entity SEO

5 min read

View markdown source

Overview

Author entity SEO is the work of teaching Google that the human in the byline is a real, identifiable person with a track record. Google maintains an entity graph that links bylines to people, and pages authored by recognized entities receive an E-E-A-T boost on every article they touch. The work is largely structural: one canonical identity per author, one profile URL, one Person JSON-LD record reused across every article.

Byline every editorial page with a real human name

Use the author’s full legal or professional name. No “Staff,” no “Admin,” no “Editorial Team.” Aliases work if they are consistent across every property the author publishes on; pseudonym inconsistency breaks entity resolution.

  • One name across the byline, the author profile URL slug, the Person JSON-LD, and every linked social profile.
  • If the author writes under a pen name, use the pen name everywhere. Do not mix legal name and pen name across properties.
  • Show the byline at the top of the article, linked to the author profile page. Footer bylines reduce the chance Google associates the article with the author entity.

Host a dedicated author profile page at /authors/

Every byline links to a profile page on the same domain. The profile is the canonical entity record on this site.

The page contains:

  • A real photo of the author.
  • A bio paragraph naming the projects, years, and topics the author has hands-on experience with. See the experience pillar in e-e-a-t.
  • Formal credentials if any (MD, CPA, JD, PhD) on YMYL topics.
  • A list of every article the author has written on this site, with publish dates.
  • Outbound links to the author’s GitHub, LinkedIn, ORCID, X/Twitter, Wikipedia, and any other public profile.

The profile URL is what gets cited from the article JSON-LD as the author.url. Treat it as permanent; never change the slug after the page goes live.

Populate sameAs with three to seven public profiles

sameAs is the schema.org property that resolves an entity to its other web presences. Populate it with stable URLs only; deleted accounts break the resolution chain.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Jane Doe",
  "url": "https://example.com/authors/jane-doe",
  "jobTitle": "Staff Engineer",
  "sameAs": [
    "https://github.com/janedoe",
    "https://linkedin.com/in/janedoe",
    "https://orcid.org/0000-0002-1825-0097",
    "https://x.com/janedoe",
    "https://www.wikidata.org/wiki/Q12345678",
    "https://en.wikipedia.org/wiki/Jane_Doe"
  ]
}
</script>

GitHub, LinkedIn, ORCID, and X are the high-confidence anchors. A Wikipedia article or Wikidata Q-ID is the strongest signal Google accepts; an author who qualifies for a Wikidata entry should claim it.

Mark up Person JSON-LD on the profile page, not just articles

The author profile page carries the full Person JSON-LD record. Article pages reference the same person by URL, so the entity definition lives in one place.

<!-- on /authors/jane-doe -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "mainEntity": {
    "@type": "Person",
    "name": "Jane Doe",
    "url": "https://example.com/authors/jane-doe",
    "image": "https://example.com/authors/jane-doe.jpg",
    "sameAs": [ "..." ]
  }
}
</script>

Article pages link to the author by URL only:

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

This is the canonical pattern Google’s structured-data parser expects. Duplicating the full record on every article works, but the profile-page-as-source-of-truth pattern is easier to maintain. See schema-markup-deep for the broader schema catalog.

Include an authorBio component on every article

Below the byline (or at the end of the article body), render a compact author bio:

  • Author photo, name, one-sentence summary of expertise.
  • A “Written by” link to the author profile page.
  • Two or three of the same sameAs links surfaced as visible icons (GitHub, LinkedIn).

This is the human-readable mirror of the JSON-LD. Quality raters see it, the entity resolver corroborates it, and inbound link equity to the profile page accumulates from every article.

Maintain a single canonical author identity

The hardest part of author entity SEO is operational, not technical: keeping the identity consistent over years. One person, one canonical name, one profile URL per property, one set of sameAs links.

  • When an author changes employers, update the profile bio. Do not move the profile URL.
  • When an author leaves the publication, keep the profile page indexable. Removing it breaks every article they wrote.
  • When a publication acquires another, migrate author profiles with 301s to preserve the entity history. See redirects.

Common errors

  • Pseudonym inconsistency. The same person publishing as “J. Doe,” “Jane Doe,” and “janedoe” across three sites looks like three entities to Google.
  • Missing sameAs array. Without external anchors, the JSON-LD is unresolvable; Google has no way to connect the byline to a known entity.
  • Multiple author URLs for the same person on one site. A profile at /authors/jane-doe and another at /team/jane splits the entity record.
  • Faking credentials. Listing “MD” without an ORCID, PubMed, or licensing-board record is detectable through cross-reference, and triggers a YMYL downweight under the helpful-content-update system.
  • Deleting author profiles when staff leaves. Every article the author wrote loses its E-E-A-T anchor.

Graph View

Backlinks