June 22, 2026·15 min read·schema

Article schema with author E-E-A-T: the complete 2026 implementation guide

Article schema with proper Person author sub-schema is the foundational structured data for any content site. Google's E-E-A-T framework — Experience, Expertise, Authoritativeness, Trust — depends heavily on verifiable author signals, and Article schema is where those signals get declared formally. Here's the implementation guide: required fields, the Person sub-schema structure, common mistakes that break E-E-A-T signal eligibility, and the validation workflow that confirms it works.

Article schema with proper Person author sub-schema is the foundational structured data for any content site optimizing for E-E-A-T (Experience, Expertise, Authoritativeness, Trust). The implementation requires several specific fields: headline, description, datePublished, dateModified, image, and most critically author as a full Person sub-schema (not just a name string), with name, url pointing to a substantive bio page, sameAs array linking to verifiable professional profiles, and jobTitle describing relevant expertise. Done correctly, this single schema implementation creates verifiable identity signals that Google's E-E-A-T framework and AI engine quality filters cross-reference before citing or ranking content. Done incorrectly (or with author as a string instead of Person sub-schema), the schema is technically valid but provides minimal E-E-A-T benefit.

E-E-A-T became a stated Google ranking factor when "Experience" was added in late 2022, expanding the older E-A-T framework. The shift increased emphasis on demonstrable first-hand experience of content creators, particularly for YMYL (Your Money or Your Life) topics. AI engines adopted similar quality assessments, weighting named author signals heavily when filtering source candidates for citation. Article schema is the structured data layer that declares these signals to both Google and AI engines simultaneously.

This guide covers the complete Article schema structure with Person author, the specific fields that matter for E-E-A-T signal strength, the bio page infrastructure required to support the schema, common implementation mistakes that break the signal chain, and the validation workflow that confirms everything is connected.

What Article schema declares and why E-E-A-T depends on it

Article schema is a Schema.org entity type that marks up the metadata for a piece of content: who wrote it, when it was published, what it's about, who published it. The schema lives in a <script type="application/ld+json"> block in the page head.

For E-E-A-T purposes, three fields matter most:

author — declares who wrote the content. This is where E-E-A-T signal infrastructure attaches. A bare string (e.g., "author": "Jane Smith") provides minimal signal. A full Person sub-schema with linked bio page and sameAs array to professional profiles provides verifiable identity.

publisher — declares the organization publishing the content. Connects to Organization schema covering the site itself. Important for E-E-A-T at the site level rather than article level.

datePublished and dateModified — declare content recency. Important for both E-E-A-T (fresh content signals active maintenance) and AI engine recency weighting.

Google's E-E-A-T framework doesn't directly read schema markup as ranking input — Google's algorithms evaluate E-E-A-T through many signals. But Article schema with Person author provides the structured handle that makes those signals verifiable. A page declaring a real named author with linked bio and professional profiles gives Google's quality assessment confidence; a page with anonymous "Editorial Team" attribution provides no comparable confidence.

AI engines (ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews) explicitly use Article schema in source filtering. Pages with proper author Person sub-schema get cited measurably more often than equivalent content without it, particularly for YMYL topics where trust signals matter most.

The complete Article schema with Person author

A production-quality Article schema looks like this:

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to validate JSON-LD schema markup",
  "description": "Step-by-step process to validate schema using Google's Rich Results Test and Schema.org validator.",
  "datePublished": "2026-05-11T10:00:00-03:00",
  "dateModified": "2026-05-11T10:00:00-03:00",
  "image": "https://yourdomain.com/images/validate-schema-cover.jpg",
  "url": "https://yourdomain.com/blog/validate-schema",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://yourdomain.com/blog/validate-schema"
  },
  "author": {
    "@type": "Person",
    "name": "Ed Grows",
    "url": "https://yourdomain.com/about",
    "image": "https://yourdomain.com/images/author.jpg",
    "jobTitle": "Founder of citelity",
    "description": "Building citelity — the AEO stack for indie founders and content sites.",
    "sameAs": [
      "https://x.com/edgrows",
      "https://github.com/edgrows"
    ]
  },
  "publisher": {
    "@type": "Organization",
    "name": "citelity",
    "url": "https://citelity.com",
    "logo": {
      "@type": "ImageObject",
      "url": "https://citelity.com/logo.png"
    }
  }
}

Each field plays a specific role. Let me walk through what matters and what doesn't.

Required vs optional fields

Schema.org and Google have different concepts of "required" — Schema.org's spec is more permissive than what Google's Rich Results Test treats as best practice. Here's the practical breakdown:

Strictly required (validation fails without them):

@context — always https://schema.org
@type — Article, BlogPosting, NewsArticle, or TechArticle depending on content
headline — the article title
author — even bare string passes; Person sub-schema strongly preferred
datePublished — ISO 8601 format

Strongly recommended (Google warns without them):

description — short summary
image — primary article image (URL or ImageObject)
dateModified — distinct from datePublished when content has been updated
publisher — Organization sub-schema
mainEntityOfPage — declares the canonical page URL for this article

Useful but optional:

url — explicit URL (helps when mainEntityOfPage isn't set)
articleBody — full text (rarely included due to size)
articleSection — category/section
keywords — comma-separated tags
wordCount — integer word count

For E-E-A-T specifically, the author field is where almost all the signal value concentrates. Make sure it's a full Person sub-schema, not a string.

The Person sub-schema in depth

The author Person sub-schema is where E-E-A-T verification happens. Required fields:

{
  "@type": "Person",
  "name": "Author Name",
  "url": "https://yourdomain.com/authors/author-name",
  "image": "https://yourdomain.com/images/author.jpg",
  "jobTitle": "Founder of [Company] / Senior Engineer / etc.",
  "description": "Brief bio describing relevant expertise.",
  "sameAs": [
    "https://x.com/handle",
    "https://linkedin.com/in/profile",
    "https://github.com/username"
  ]
}

name — real name (or consistent named pseudonym with public profile). Generic names like "Editor" or "Admin" provide no verification.

url — points to the author's bio page on your domain. Critical: the bio page must actually exist and contain substantive content demonstrating expertise. Empty bio pages or placeholder content provide no signal.

image — actual photo of the person, not a stock photo or illustration. Image fakery is detectable and damages E-E-A-T more than no image does.

jobTitle — relevant role for the content topic. "Software Engineer" for technical content, "Practicing Attorney" for legal content, "Registered Dietitian" for nutrition content. The title should genuinely describe the author's qualification for the topic.

description — 1-3 sentences summarizing the author's relevant expertise. Avoid marketing language; describe verifiable qualifications.

sameAs — array of URLs to verifiable professional profiles on platforms outside your domain. This is where cross-platform identity verification happens. The more verifiable profiles, the stronger the signal — but they must actually exist and contain content that supports the bio claim.

The most valuable sameAs profiles vary by content topic:

LinkedIn — universal credibility signal
Twitter/X — for tech, marketing, journalism, public personas
GitHub — for software engineering content
ResearchGate / Google Scholar — for academic content
Industry-specific platforms (e.g., GoodReads for book reviewers, Strava for fitness)

The bio page infrastructure

The url field in Person schema points to a bio page. That bio page is part of the E-E-A-T signal chain — if it doesn't actually demonstrate expertise, the schema provides no benefit.

A proper bio page contains:

Substantive bio content (300-500 words minimum) describing the author's background, expertise, and qualifications for the topics they write about
Real photo matching the photo in author.image
List of credentials relevant to the content topics (degrees, certifications, years of experience, prior work)
Links to all profiles in the sameAs array (so the cross-references are bidirectional)
List of articles the author has written on your site (often automated based on author field in articles)
Person schema on the bio page itself — declaring the bio page as the canonical entity for the person

The Person schema on the bio page connects everything: articles reference the bio page URL via author.url, the bio page declares the person formally, the bio page's sameAs array confirms the same external profiles, the external profiles (when visited) describe a person consistent with the bio page.

This bidirectional verification is what makes E-E-A-T signals strong. Anonymous or inconsistent identity claims break the chain.

Free tool · No signup

Free Schema Validator

Paste any URL → full AEO audit across 12 factors with ready-to-paste JSON-LD fixes.

Check your schema →

The 6 rules for Article schema E-E-A-T strength

The implementation choices that distinguish strong E-E-A-T from weak:

Rule 1: Author must be Person sub-schema, not a string

Bare string author ("author": "Jane Smith") is technically valid Article schema but provides minimal E-E-A-T value. Full Person sub-schema with url, sameAs, jobTitle is the strong version.

Rule 2: Bio page must actually exist and be substantive

Person schema's url field must point to a real bio page. Empty placeholder pages or 404 pages break the verification chain. Bio pages need real content demonstrating expertise.

Rule 3: `sameAs` profiles must actually exist and be consistent

Profile URLs in sameAs are checked. If LinkedIn URL doesn't lead to a profile, or if the profile contradicts the bio page (different name, different role, different photo), the verification fails.

Rule 4: Real author photo, not stock or illustration

Stock photos and illustrations are detectable and provide no identity signal. If you don't have a real photo, omit the image field rather than using fake imagery.

Rule 5: jobTitle should be specific to the content topic

Generic jobTitle ("Writer," "Editor") provides less E-E-A-T signal than topic-specific role ("Software Engineer specializing in distributed systems," "Practicing Attorney with 12 years in immigration law").

Rule 6: Publisher Organization schema should also be properly structured

Article-level E-E-A-T depends partly on site-level E-E-A-T. The publisher Organization schema should be configured sitewide and consistent across all articles. Generic or missing publisher schema weakens overall trust signals.

Common mistakes that break E-E-A-T signal eligibility

Author as a string instead of Person sub-schema. Technically valid but minimal E-E-A-T benefit.
Bio page that doesn't exist. Person schema URL pointing to 404 or empty placeholder. Breaks the verification chain.
Inconsistent identity across platforms. LinkedIn says one thing, bio page says another, X profile says a third. Verification fails.
Stock photos as author images. Detectable; reduces trust signal below "no image" baseline.
Generic publisher Organization schema. Missing or boilerplate publisher info weakens article-level signal.
Multiple authors declared as single Person. When multiple people genuinely contributed, use array of Person entities. Don't merge them into "John and Jane Smith" as a single name.
datePublished in the future or wrong format. Validation fails or trust signal damaged.
Missing dateModified when content was updated. Article shows stale date despite recent updates; affects recency assessment.
Schema declaring expertise that's not visible in body content. If schema says author is a "Senior Engineer" but article reads like generic content with no technical depth, the mismatch is detected.
Generic Editorial Team authorship as default. Better to have no schema author than fake collective authorship that breaks E-E-A-T expectations.

Validation workflow

Three steps before publishing or after updates:

1. Google's Rich Results Test

search.google.com/test/rich-results — paste URL or raw JSON-LD. Required: zero errors. Article schema typically generates warnings about "valid for some Search features" — these are usually fine for AEO purposes.

2. Schema.org Validator

validator.schema.org — catches spec-level violations. Green checkmarks across all entities required.

3. Manual verification of the identity chain

This is the step automated validators miss. Do it manually:

Click the author bio page URL — does it load with substantive content?
Click each sameAs profile URL — does it lead to a real profile with consistent information?
Verify the author photo on the article matches the photo on bio page and external profiles
Check that jobTitle on bio page matches jobTitle in schema
Confirm publisher Organization schema is also configured sitewide

If any link in the chain breaks, the E-E-A-T signal weakens regardless of schema validation passing.

For broader schema validation guidance, see our schema markup guide and FAQ schema implementation guide.

Free tool · No signup

Free Schema Validator

Paste any URL → full AEO audit across 12 factors with ready-to-paste JSON-LD fixes.

Check your schema →

How Article schema combines with other schema types

Most content benefits from Article schema combined with other types:

Article + FAQPage — for articles with FAQ sections. Article covers article-level metadata; FAQPage covers Q&A pairs.
Article + HowTo — for tutorial articles. Article for metadata; HowTo for step structure. See our HowTo schema guide for details.
Article + Review — for product review articles. Article for the article framing; Review schema for the verdict structure.
Article + BreadcrumbList — sitewide breadcrumb structure. Belongs on every article.

One Article schema block per page. Don't declare two Article entities on one URL.

What Article schema doesn't do

Honest framing about limits:

It doesn't guarantee ranking improvements. Article schema is a structural signal that enables E-E-A-T verification. The verification still has to confirm real expertise, which depends on content substance and author qualifications. Schema can't substitute for either.

It doesn't compensate for thin content. A 600-word article with perfect Article schema underperforms a 2,500-word article with basic Article schema. Schema is a multiplier on content quality, not a replacement.

It doesn't bypass E-E-A-T evaluation for YMYL topics. For Your Money or Your Life topics (finance, health, legal, safety), Google applies stricter E-E-A-T standards regardless of schema. The schema needs to point to an author with actual credentials in that YMYL area, not just any named author.

It doesn't make AI-generated content cite-worthy. AI engines apply pattern detection for AI-generated content independent of schema. Adding Article schema to AI-generated content doesn't bypass that detection — and the schema declaring named human authorship while content shows AI-generation patterns triggers schema misuse signals.

Free tool · No signup

Free AEO Content Score

Paste content or URL → 0-100 score across 10 AEO factors + 3 prioritized quick wins.

Score your content →

FAQ

What's the difference between Article and BlogPosting schema?

BlogPosting is a specific subtype of Article designed for blog content. The fields and structure are similar; BlogPosting just adds blog-specific implicit context. For most content sites publishing blog posts, BlogPosting is the more accurate type to declare. For news articles, NewsArticle is the right subtype. For technical tutorials with extensive code, TechArticle works. The exact subtype matters less than getting the fields right — Article works as a generic fallback when subtypes are uncertain.

Do I need separate Article schema for each article, or can I template it?

Each article needs its own Article schema with article-specific values (headline, datePublished, image, URL, etc.) — these cannot be shared across articles. Templating is appropriate for: the structure of the schema itself, the publisher Organization sub-schema (same across all articles), and the Person author sub-schema (when one author writes many articles). Most CMS systems template the structure automatically once configured. The key is verifying that the per-article values get populated correctly, not just the template structure.

Can I use the same Person sub-schema for multiple authors at my site?

No — each author needs distinct Person schema with their own bio page URL, photo, jobTitle, and sameAs profiles. Generic shared author schema doesn't work because each Person represents a distinct individual. If you have multiple authors, each gets their own bio page and Person schema. Articles by each author reference that author's specific Person sub-schema in their Article schema's author field.

What if my site doesn't have named authors? Can I still get E-E-A-T benefits?

Limited E-E-A-T benefits without named authors. Anonymous or 'Editorial Team' attribution provides minimal verification value to Google or AI engines. Two paths: either bring on real named authors (1-3 for a small site can be enough) and build proper bio infrastructure, or accept reduced E-E-A-T signal strength and compete on other factors (content depth, original research, technical accuracy). For YMYL topics specifically, the named author path is essentially required for serious traffic; for non-YMYL informational content, anonymous publishing is viable but at a competitive disadvantage versus sites with named authors.

How often should I update dateModified on Article schema?

Update dateModified whenever you make material changes to the article content — not for typo fixes, but for any update that genuinely affects the article's information value. Examples that warrant updating: adding new sections, updating factual claims, replacing outdated examples, refreshing statistics, adding new internal links pointing to recently published related content. Don't update dateModified for cosmetic changes (CSS edits, image optimization, ad placement changes) because that signals content freshness that isn't really there. Google and AI engines cross-check claimed freshness against actual content changes; misuse damages credibility signals.

Closing

Article schema with proper Person author sub-schema is the foundational structured data for any content site optimizing for E-E-A-T in 2026. The implementation is straightforward technically; the discipline is in the supporting infrastructure: real bio pages with substantive content, real photos, verified external profiles, consistent identity across platforms, and content body that actually demonstrates the expertise the schema declares.

The compounding benefit: once configured correctly, Article schema with Person author works across Google ranking signals, AI engine citation eligibility, voice assistant inclusion, and future surfaces that increasingly weight verifiable identity. The investment is one-time setup; the return persists as long as the supporting infrastructure (bio pages, profiles) stays maintained.

If you're starting today: audit your top 20 pages for Article schema implementation. Pages with bare string authors should be updated to full Person sub-schema. Pages with Person schema but broken bio page links should be fixed. Pages with consistent named authorship across multiple articles should consolidate around 1-3 author Person schemas with strong bio infrastructure, rather than diluting across many weakly-supported author identities. The cleanup typically improves citation eligibility within 4-6 weeks once AI engines re-evaluate the strengthened signals.

← Back to all posts

What Article schema declares and why E-E-A-T depends on it

The complete Article schema with Person author

Required vs optional fields

The Person sub-schema in depth

The bio page infrastructure

The 6 rules for Article schema E-E-A-T strength

Rule 1: Author must be Person sub-schema, not a string

Rule 2: Bio page must actually exist and be substantive

Rule 3: sameAs profiles must actually exist and be consistent

Rule 4: Real author photo, not stock or illustration

Rule 5: jobTitle should be specific to the content topic

Rule 6: Publisher Organization schema should also be properly structured

Common mistakes that break E-E-A-T signal eligibility

Validation workflow

1. Google's Rich Results Test

2. Schema.org Validator

3. Manual verification of the identity chain

How Article schema combines with other schema types

What Article schema doesn't do

FAQ

Closing

Rule 3: `sameAs` profiles must actually exist and be consistent