Author Entity Building
Session 9.2 · ~5 min read
Google does not just evaluate content. It evaluates who created the content. The concept of E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) makes individual authors relevant to how Google assesses content quality. An article about tax law written by a certified accountant carries more weight than the same article written by an anonymous contributor. The difference is not the content itself. It is the author entity behind it.
Author entity building is the process of establishing individual contributors as recognized, disambiguated entities with verifiable credentials. When Google can identify an author as a real person with real expertise, the content that person produces benefits from their entity reputation.
E-E-A-T and Author Entities
Google's Search Quality Evaluator Guidelines describe E-E-A-T as a framework for assessing content quality. Experience means the author has first-hand experience with the topic. Expertise means the author has formal qualifications or deep knowledge. Authoritativeness means the author is recognized as a go-to source. Trustworthiness means the content and its source are reliable.
(Person)"] --> B["Experience
(first-hand practice)"] A --> C["Expertise
(credentials, knowledge)"] A --> D["Authoritativeness
(recognition, citations)"] A --> E["Trustworthiness
(reliability, accuracy)"] B --> F["Content Quality
Assessment"] C --> F D --> F E --> F F --> G["Search Rankings
+ Knowledge Graph"] A -->|"worksFor"| H["Organization Entity"] H -->|"publishes"| F style A fill:#222221,stroke:#c8a882,color:#ede9e3 style B fill:#222221,stroke:#6b8f71,color:#ede9e3 style C fill:#222221,stroke:#6b8f71,color:#ede9e3 style D fill:#222221,stroke:#6b8f71,color:#ede9e3 style E fill:#222221,stroke:#6b8f71,color:#ede9e3 style F fill:#222221,stroke:#8a8478,color:#ede9e3 style G fill:#222221,stroke:#c47a5a,color:#ede9e3 style H fill:#222221,stroke:#c8a882,color:#ede9e3
The diagram shows how an author entity feeds into content quality assessment through the four E-E-A-T dimensions. The author entity also connects to the organization entity through the worksFor relationship, creating a chain: person creates content, organization publishes content, content quality reflects on both entities.
Author Page Requirements
Every author who publishes content on your site should have a dedicated author page. This page serves as the identity document for the author entity, similar to how the about page serves the organization entity. It should contain verifiable facts about the person, structured data, and links to external profiles.
| Element | Priority | Purpose | Schema Property |
|---|---|---|---|
| Full name | Critical | Identity anchor | name |
| Professional photo | Critical | Visual identity, matches social profiles | image |
| Job title and organization | Critical | Person-organization link | jobTitle, worksFor |
| Professional bio (2-4 sentences) | Critical | Entity description, Wikipedia-style opener | description |
| Credentials and certifications | Critical | Expertise verification | hasCredential |
| Social profile links | Recommended | Cross-platform entity linking | sameAs |
| List of authored content | Recommended | Demonstrates topical coverage | (HTML links to articles) |
| External publications | Recommended | Third-party authority signals | (prose, links to external work) |
| Education | Optional | Credential context | alumniOf |
| Awards | Optional | Recognition signals | award |
| Speaking engagements | Optional | Authoritativeness in field | (prose or Event schema) |
Person Schema for Authors
Each author page should carry a complete Person schema. This is the author's machine-readable identity document. It must include the same @id that will be referenced in Article schema on the content pages they author.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Person",
"@id": "https://example.com/team/jane-smith/#person",
"name": "Jane Smith",
"jobTitle": "Senior SEO Strategist",
"worksFor": {
"@type": "Organization",
"@id": "https://example.com/#organization"
},
"description": "Jane Smith is a senior SEO strategist with 12 years of experience in technical SEO and entity optimization.",
"image": "https://example.com/images/jane-smith.jpg",
"url": "https://example.com/team/jane-smith/",
"sameAs": [
"https://www.linkedin.com/in/janesmith/",
"https://twitter.com/janesmith"
],
"alumniOf": {
"@type": "CollegeOrUniversity",
"name": "University of Texas at Austin"
},
"knowsAbout": ["SEO", "structured data", "Knowledge Graph optimization"]
}
</script>
The worksFor property is essential. It connects the Person entity to the Organization entity. When Google processes Article schema that references this Person as the author, and that Person works for the Organization that is the publisher, the full attribution chain is complete.
Key concept: An author entity is not a byline. A byline is a name on a page. An author entity is a recognized, disambiguated person in Google's Knowledge Graph with verifiable credentials, cross-platform presence, and explicit connections to the content they create and the organization they work for.
Connecting Author Entities to Content
The author page is the identity document. The connection to content happens in two places: the visible byline on each article, and the Article schema on each content page. The byline should link to the author page. The Article schema should reference the author's Person @id. Both must be present for the full entity signal.
A visible byline without schema tells humans who wrote the content but makes Google infer the connection. Schema without a visible byline provides the machine-readable signal but raises a consistency concern (Google expects schema to reflect visible content). Both together provide the strongest signal.
Building Author Authority Externally
Author entities do not exist only on your website. Guest posts on industry publications, podcast appearances, conference talks, and social media activity all contribute to the author's entity profile. Each external appearance should use the author's consistent name, link back to their author page when possible, and use the same professional photo.
LinkedIn is particularly important for author entities. Google frequently uses LinkedIn profiles as a reference point for Person entities. Ensure the author's LinkedIn profile matches the information on their author page: same name, same job title, same organization, same photo.
Further Reading
- Google: Article Structured Data
- Google: Search Quality Evaluator Guidelines (E-E-A-T sections)
- Schema.org: Person Type
- Search Engine Journal: Demonstrating E-E-A-T
Assignment
Build or improve author entities for your site's content creators.
- List every person who has authored content on your site. For each, check whether a dedicated author page exists.
- Create or update author pages for your top 2 content creators. Include all "Critical" elements from the requirements table.
- Add Person schema to each author page with at least: name, jobTitle, worksFor (referencing your Organization @id), description, image, and sameAs.
- Verify that the author's LinkedIn profile matches the information on their author page. Fix any inconsistencies in name, title, or organization.