Session 8.4: Author Entities and E-E-A-T

Course → Module 8: Entity-First Content Strategy

Session 4 of 7

E-E-A-T and Why Authors Matter

E-E-A-T stands for Experience, Expertise, Authoritativeness, and Trustworthiness. It is the framework Google's quality raters use to evaluate content. While E-E-A-T is not a direct ranking algorithm, it informs the signals that ranking algorithms are designed to detect.

The first "E" (Experience) was added in December 2022. It explicitly asks whether the content creator has first-hand experience with the subject. This makes author identity a central element of content quality evaluation. Anonymous content has no author to evaluate for experience or expertise.

Content without a named, verifiable author is content without E-E-A-T signals. Google cannot evaluate expertise for an entity it cannot identify.

The Author Entity Stack

An author entity is not just a byline. It is a structured identity that connects a named person to their credentials, their organization, and their content. Building an author entity requires four components working together.

Component	What It Is	What It Signals
Author byline	Name visible on the article, linked to bio page	Content has a named, accountable creator
Author bio page	Dedicated page on your site with photo, credentials, and article list	The person is a real, verifiable entity
Person schema	JSON-LD markup on the bio page with name, jobTitle, worksFor, sameAs	Machine-readable identity for Knowledge Graph
Article schema with author	Each article's schema includes author property linking to the Person	This content was created by this verified entity

Person Schema for Authors

The Person schema on an author's bio page should include as many verifiable properties as possible:

{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://yourcompany.com/about/john-smith/#person",
  "name": "John Smith",
  "jobTitle": "Chief Engineer",
  "worksFor": {
    "@type": "Organization",
    "@id": "https://yourcompany.com/#organization"
  },
  "image": "https://yourcompany.com/images/john-smith.jpg",
  "url": "https://yourcompany.com/about/john-smith/",
  "sameAs": [
    "https://www.linkedin.com/in/johnsmith",
    "https://twitter.com/johnsmith"
  ],
  "knowsAbout": ["industrial pumps", "fluid dynamics", "pump maintenance"]
}

The @id creates a reusable reference. Other schema blocks on the site (Article schema, for example) can reference this Person by @id instead of repeating all the properties.

Google's Entity Resolution for Authors

Google uses entity resolution to connect author identities across platforms. The September 2025 update to Google's Search Quality Rater Guidelines reinforces that content creator information is a primary evaluation factor.

Google's AI systems determine whether "John Smith on LinkedIn" is the same person as "John Smith who wrote this article" and "John Smith speaking at this conference." This cross-platform author recognition works through the same reconciliation principles covered in Module 7: consistent naming, sameAs links, and bidirectional verification.

graph LR A["Article by John Smith"] --> P["Bio Page with Person Schema"] P --> L["LinkedIn: John Smith, Chief Engineer"] P --> T["Twitter: @johnsmith"] P --> O["Organization Schema: worksFor"] L -.->|profile links to| P style P fill:#222221,stroke:#c8a882,color:#ede9e3

Multiple Authors on One Site

If your organization has multiple content creators, each needs their own author entity. This does not dilute authority. It strengthens it, provided each author writes within their area of expertise.

The organization entity is the parent. Author entities are connected through the worksFor property. When Google sees three recognized experts all producing content for the same organization, the organization's entity authority compounds.

Author Setup	E-E-A-T Signal	Practical Impact
No author (anonymous content)	None	Google cannot evaluate experience or expertise
Name only (no bio page, no schema)	Weak	Author exists but is not verifiable
Name + bio page (no schema)	Moderate	Human-readable but not machine-readable
Name + bio page + Person schema + sameAs	Strong	Full author entity with Knowledge Graph potential

An author entity is not a vanity feature. It is a structural requirement for content that Google evaluates as expert, experienced, and trustworthy.

Assignment

For every content creator on your site, check: (1) Is their name on each article they wrote? (2) Do they have a dedicated bio page? (3) Does that bio page have Person schema with name, jobTitle, worksFor, sameAs, and knowsAbout? (4) Does the Article schema on their content reference their Person entity? Fix every gap you find, starting with your highest-traffic author.

Author Entities and E-E-A-T