Structured Data & Machine Readability Layer 2 · Understanding Established

Article Schema (JSON-LD)

Article schema in JSON-LD is structured data placed in the page head that explicitly labels a page as an article and attaches the provenance metadata AI systems rely on — headline, author, datePublished, dateModified, publisher, and canonical URL — so a machine knows what the page is and who is accountable for it, not just what words it contains.

Why it matters

Why this signal affects whether AI cites you.

Structured data is how a machine knows what a page is, not just what words it contains. Article schema in JSON-LD explicitly labels a page as an article and attaches the metadata AI systems lean on when deciding whether to trust and attribute it: headline, author, publish and modified dates, publisher, and the canonical URL. Without it, an AI has to infer all of that from raw HTML — and inference is where attribution gets lost, dates get guessed wrong, and the wrong entity gets credit. With clean Article schema, the page hands the model an unambiguous, machine-readable summary of its own provenance. This matters for citation in two ways. First, freshness: AI systems increasingly prefer recently updated sources, and an explicit dateModified is the clearest freshness signal you can send. Second, authorship and E-E-A-T: a named author linked to a real Person entity is one of the strongest trust signals a page can carry, and Article schema is where that link lives. JSON-LD is the format every major AI platform and search engine reads most reliably, and it sits in the page head without touching your visible design — making Article schema one of the highest-leverage, lowest-risk Understanding-layer factors. Because the markup is invisible to readers and cheap to template once, it is one of the few factors you can roll out across an entire site in an afternoon and then benefit from indefinitely.

What good looks like

How to get this right.

  • A JSON-LD Article block in the page head with headline, author, datePublished, dateModified, and publisher fields populated.
  • An author property linked by sameAs to the writer's real Person entity, LinkedIn, and other authoritative profiles.
  • A dateModified value kept genuinely current so AI systems reading freshness signals treat the page as up to date.
What to avoid

Common mistakes.

  • Hardcoding dateModified to the original publish date so the freshness signal never actually updates.
  • Authoring as the Organization with no named Person, forfeiting the strongest E-E-A-T attribution signal.

You now know the signal. See your score.

This page covers what Article Schema (JSON-LD) is and how to get it right. AIVZ measures it on your actual pages — across six AI platforms, weighted and prioritized against all 93 factors — and hands you the exact fixes in priority order.

Scan your site against all 93 factors
Common questions

Frequently asked.

Does Article schema change how my page looks?

No. JSON-LD lives in the page head and is invisible to human visitors; it only adds a machine-readable description of the page for AI systems and search engines.

Which matters more, datePublished or dateModified?

Both help, but dateModified is the clearest freshness signal — AI systems increasingly prefer recently updated sources, so keep it genuinely accurate rather than hardcoded.

Sources

Related factors

Signals that work together.

Last updated · See changelog

See What AI Sees

The fastest way to evaluate fit.

The free scan is the canonical demo of what AIVZ does. Run a scan on your own site, your competitor's, or a prospect's.

Factor · Article Schema (JSON-LD)