For Schema Studio 0.9.5. Reviewed October 10, 2026. Review tested versions, exclusions and limitations.
Build an article graph
Goal: describe a real article, connect its page, author and publisher, and avoid duplicate entities.
- Inspect the full graph. Retain a correct existing WebPage and its ID.
- Add/select Article or BlogPosting. Bind headline to post.title unless a different visible headline is intentional.
- Bind datePublished and dateModified to WordPress dates.
- Use a relevant featured image when available. Confirm it loads publicly and represents the article.
- Connect author to the real Person and publisher to the correct Organization. Reuse existing IDs.
- Connect mainEntityOfPage to the actual WebPage ID and inspect the full preview.
- Explicitly bind every reusable entity needed. A Person’s Organization relationship does not guarantee the Organization is emitted.
- Save, reload and test the published URL.
This simplified output uses fictitious example.com values. Replace them with verified facts and existing IDs; do not add another graph when one already exists.
{
"@context": "https://schema.org",
"@graph": [
{"@type": "WebPage", "@id": "https://example.com/guide/#webpage",
"url": "https://example.com/guide/", "name": "A practical guide"},
{"@type": "Person", "@id": "https://example.com/authors/alex/#person",
"name": "Alex Example", "url": "https://example.com/authors/alex/"},
{"@type": "Organization", "@id": "https://example.com/#organization",
"name": "Example Company", "url": "https://example.com/"},
{"@type": "Article", "@id": "https://example.com/guide/#article",
"headline": "A practical guide",
"mainEntityOfPage": {"@id": "https://example.com/guide/#webpage"},
"author": {"@id": "https://example.com/authors/alex/#person"},
"publisher": {"@id": "https://example.com/#organization"}}
]
}
This teaches relationships, not a complete Google eligibility checklist. Consult current Article guidance.
Links will be automatically removed from comments.