# Editorial metadata

Author, dates and provenance behind the content.

**[Trust](/docs/trust)** · checked on every URL · 4 checks that can fail it

Provenance is what lets an agent decide whether to trust and cite a page, and JSON-LD is the only unambiguous place to state it. This is Lumar's editorial-trust profile, not Google rich-result validity: Google states Article has no required properties.

## Adoption

**Web baseline** (L4) — the JSON-LD syntax is everywhere; the article types that carry provenance are niche

Standard equipment on the web. Its absence is the exception rather than its presence. Direction of travel: ► flat, as of 2026-07-28.

JSON-LD is on 41% of pages but Article-type markup on roughly 0.18% (Web Almanac 2024), and no vendor has confirmed that author markup feeds AI citations.

## What we check

Absence is never a finding: every check below runs only once `editorialMetadataPresent` is true, so a site that has not
adopted this is not assessed on it and appears in no report.

| Check | Kind | Raises | On whose authority |
|---|---|---|---|
| `editorialMissingAuthor` | medium severity | usability | Lumar readiness profile |
| `editorialMissingPublisher` | medium severity | usability | Lumar readiness profile |
| `editorialMissingDatePublished` | medium severity | usability | Lumar readiness profile |
| `editorialInvalidDate` | medium severity | usability | Schema.org profile |

## Examples

These are the fixtures the test suite runs through the real collector, not snippets written for a document.

- Correct: `test/e2e/test-pages/trust/correct.html`
- Present but wrong: `test/e2e/test-pages/trust/issues.html`

## Specifications

| Document | Revision | Kind |
|---|---|---|
| [Schema.org author](https://schema.org/author) | v30.0 | specification |
| [Google Search: Article structured data (states no required properties)](https://developers.google.com/search/docs/appearance/structured-data/article) | living document | vendor profile |

Last re-read against the published documents: 2026-08-12.