Roshanak Kavian
Co-Founder and CEO of Indigo Mars, a Los Angeles marketing agency.
Writing an author's name as a plain text string in your Article schema — "author": "Jane Doe" — is technically valid, but it provides essentially no real authority signal on its own. Person schema authors are meant to be a genuine, structured entity, not just a label, with properties that connect a real name to real credentials, a real organization, and real external profiles. This is the direct technical implementation of the "E" and the "A" in E-E-A-T, not a separate consideration from it.
Why a Plain Text Name Isn't Enough
A bare name string tells a search engine or AI system almost nothing beyond who to attribute the words to. A proper Person object, by contrast, is a structured entity carrying real information: what this person's role is, what organization they're connected to, what they're actually knowledgeable about, and where else their identity can be independently verified. This is the difference between simply naming an author and actually establishing one as a credible, checkable entity.
The Properties That Actually Matter
name — the author's real, consistently used name, matching what's visibly displayed on the page.
jobTitle — their actual current role, not something aspirational or outdated.
worksFor — a direct link to the Organization entity for the business, connecting the author to the company in a structured, machine-readable way.
sameAs — links to the author's real external profiles: LinkedIn, other verified professional presences. This is what allows a system to cross-reference and confirm this is a real, findable person, not a name invented for the byline.
knowsAbout — the specific topic areas this person is genuinely positioned to write about, giving a system a structured signal of relevant expertise.
Connecting Person to Organization
The Person entity's worksFor property should point to the same Organization schema already established for the business elsewhere on the site. This creates a real, linked relationship — this specific author, connected to this specific organization — rather than two disconnected pieces of structured data that happen to appear on the same page. That connection is part of what makes the whole setup read as credible rather than assembled from disconnected parts.
The Same Consistency Rule Applies Here Too
Just as with every other type of schema covered in this guide, accuracy matters more than presence. If the schema states a job title, an organization, or a set of credentials that doesn't match what's visibly written in the author's actual bio on the page, that mismatch undermines trust rather than adding to it. The schema should be a structured, machine-readable version of exactly what a human reader would see in the byline — not an enhanced or aspirational version of it.
Where to Go From Here
This is the direct technical implementation of the principles covered in What Is E-E-A-T and Why AI Search Depends on It.
Not sure whether your own author bylines are backed by real, structured Person schema? Get in touch and we'll check it.
