Article Schema for Publishers (JSON-LD Templates) Topical Map

Article schema (type: Article, NewsArticle, or Reportage-specific types like LiveBlogPosting) in JSON-LD is a machine-readable block that describes an article's key metadata (headline, author, datePublished, image, publisher, mainEntityOfPage). Publishers need it to enable rich search features, ensure correct indexing of article metadata, and increase the chance of enhanced SERP treatments like article carousels, Top Stories placement, and rich cards.

At minimum include @context, @type (Article/NewsArticle), headline, datePublished, author (Person or Organization), and mainEntityOfPage/@id pointing to the canonical URL; include publisher with logo to qualify for many article rich features. Omitting these commonly used fields often prevents eligibility for rich SERP features even if markup is technically present.

Use the paywalledContent property inside the creativeWork/Article JSON-LD to indicate restricted content and implement the 'structured data for paywalled content' pattern (provide preview text that is indexable while guarding full content). Also use the visibility and robots meta patterns Google documents and test in Search Console to confirm thumbnails and snippets behave as expected.

Use the LiveBlogPosting type with liveBlogUpdate elements that include url, datePublished, and author for each update; the overall LiveBlogPosting should include mainEntityOfPage, headline, and publisher. Structure updates as separate structured data nodes (or an array) so search engines can surface the live timeline and individual updates accurately.

Always include both datePublished and dateModified when an article is updated, and ensure dateModified is only updated when substantive content changes occur (not for minor typo fixes). Keep the displayed visible dates on the page consistent with the JSON-LD values and use canonical tags to prevent index fragmentation between versions.

Use high-quality, crawlable image URLs and include an image array with at least one image that is 1200px wide (or follows Google’s minimum large-image guidance) and specify URL, width, and height when possible. Proper images increase eligibility for large-image rich results and improve CTR from SERP features.

Combine automated unit tests (schema JSON-LD linting), scheduled crawls with validation (using Schema.org/structured-data validators and Rich Results Test APIs), and Search Console’s Enhancements reports to detect errors; surface failures into a dashboard (BI or issue tracker) for prioritized fixes. Integrate tests into CI/CD so new templates or CMS changes are validated before deployment.

Server-rendered JSON-LD is the most reliable for search engines and ensures markup is present at crawl time; client-rendered is acceptable if you confirm rendering with Google’s live test tools but carries higher risk. Tag managers can work for prototypes but introduce maintainability and validation challenges at scale—prefer template-driven server-side generation for enterprise publishers.

Use canonical link elements pointing to the primary article URL and ensure mainEntityOfPage/@id in JSON-LD references the canonical URL; avoid duplicating full structured data across canonical and non-canonical variants unless they explicitly represent different content. For AMP, include consistent JSON-LD on the AMP page and connect via rel=canonical/amphtml links.

Common errors include missing publisher.logo, using author as plain text instead of Person/Organization objects, mismatched canonical URLs between HTML and JSON-LD, incorrect date formats, and stale or non-crawlable image URLs. These mistakes either disqualify articles from rich features or cause inconsistent displays in Search Console and SERPs.