# Author / E-E-A-T schema

_Source: https://seomatrix.ai/tools/author-schema/_

---

## What it does

Author schema is Person JSON-LD structured data that names who wrote a page and states their expertise, credentials, employer and verified profiles in a machine-readable form. It hands ChatGPT, Perplexity, Google AI Overviews and Search an explicit, parseable author identity to attach to your content — the E-E-A-T signals engines weigh when deciding whose answer to trust and cite. Without it, a byline is just text an engine cannot verify.

## What it checks

- **Person @type** — The root object that declares the byline is a real individual rather than free text, so engines can resolve the author as an entity and link them to the article they wrote.
- **knowsAbout topics** — An array of the subjects or entities the author is an authority on, telling AI engines which questions this person is a credible source for and reinforcing topical E-E-A-T.
- **sameAs identity links** — Links to the author's authoritative profiles such as LinkedIn, ORCID, Google Scholar or Wikipedia, letting engines cross-verify that the person is real and match them to their reputation across the web.
- **hasCredential** — Machine-readable degrees, licenses or certifications (EducationalOccupationalCredential) that back the 'Expertise' and 'Authoritativeness' of E-E-A-T with concrete proof.
- **worksFor / employer** — The Organization the author is affiliated with, tying their personal reputation to an established entity and adding institutional trust.
- **jobTitle** — The author's role or profession, giving engines a plain-language handle on why this person is qualified to speak on the topic.

## How to use it

1. Enter the author's name, job title, expertise topics (knowsAbout), credentials and profile URLs (sameAs).
2. Copy the generated Person JSON-LD block.
3. Paste it into the page's <head> — or reference it as the article's author — and validate it with the Schema Markup Validator (validator.schema.org); use Google's Rich Results Test once the Person is nested as an Article's author.

## FAQ

### What is Person JSON-LD and why do AI engines cite it?

Person JSON-LD is structured data that describes an author as a machine-readable entity — name, expertise, credentials and verified profiles. AI engines use it to confirm who stands behind a page and how qualified they are, which raises the odds your content is trusted and cited.

### Where do I put the generated author schema?

Paste the <script type="application/ld+json"> block into the <head> of the page the author wrote. For blog posts, link the Person as the author property of the Article schema so the byline resolves to the same entity.

### What should I put in sameAs?

List the author's authoritative, verifiable profiles — LinkedIn, ORCID, Google Scholar, Wikipedia, a personal site or an industry directory. These let engines cross-check that the person is real and match them to their reputation elsewhere on the web.

### Does author schema improve E-E-A-T and rankings?

Author schema doesn't directly boost rankings, but it makes your E-E-A-T signals explicit and machine-readable, helping Google and AI engines attribute expertise correctly. It matters most on YMYL topics where source credibility decides who gets cited.

