Article schema markup: example, recommended fields and WordPress setup

JSON-LD example

Copy this into a <script type="application/ld+json"> tag and replace the values with your own.

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to Repot a Fiddle Leaf Fig Without Shocking It",
  "image": [
    "https://example.com/images/fiddle-leaf-16x9.jpg",
    "https://example.com/images/fiddle-leaf-4x3.jpg",
    "https://example.com/images/fiddle-leaf-1x1.jpg"
  ],
  "datePublished": "2026-03-04T08:00:00-05:00",
  "dateModified": "2026-08-19T14:30:00-04:00",
  "author": [
    {
      "@type": "Person",
      "name": "Maya Lindqvist",
      "url": "https://example.com/authors/maya-lindqvist"
    }
  ],
  "publisher": {
    "@type": "Organization",
    "name": "Greenroom Journal",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png"
    }
  },
  "mainEntityOfPage": "https://example.com/repot-fiddle-leaf-fig"
}

Properties

Article, BlogPosting or NewsArticle?

All three are valid for Google's Article feature and take the same properties. Pick the most specific one that is true:

• BlogPosting for posts on a blog.
• NewsArticle for news reporting on a news site.
• Article for everything else editorial: guides, essays, long-form reference pages.

The choice matters less than the accuracy of the fields inside it. Do not use Article on product pages, category archives or your homepage; those have better-fitting types such as Product or WebSite.

Add it in WordPress

By hand. Print a <script type="application/ld+json"> block from your theme's wp_head hook, filling headline, dates and author from the post. It works, but you have to maintain it and keep it from duplicating markup from your SEO plugin.

With Hydrogen SEO. Set Article as the site-wide type for posts on the Schema screen, then use smart tags (type @ in a field) such as the post title, author and publish and modified dates so every post gets correct, page-specific values with no per-post editing. Individual posts can switch to a more specific type in the SEO Settings sheet. The JSON-LD is rendered server-side, so crawlers see it without running JavaScript. Developers can adjust the output, for example to add a publisher logo, with the hydrogen_seo_schema_markup filter.

One-off markup. To hand-write a block for a static page, the free schema generator in the Hydrogen SEO app at /seo/schema-generator builds Article JSON-LD from a short form, instantly and without credits.

Common mistakes

• Author as a plain string with extra text. Use "name": "Maya Lindqvist", not "By Maya Lindqvist, Editor". Put only the name in name, and use a separate object for each author.
• Organization as author when a person wrote it. Use Person for people; use Organization only when the article genuinely has no individual author.
• Faking freshness. Bumping dateModified without changing the content is misleading. Update it when you make a real edit.
• Dates without time zones. A bare date works, but a full timestamp with an offset removes ambiguity.
• Tiny or missing images. Use large, crawlable images that actually appear on the page.
• Two plugins printing Article. Duplicate blocks with different values confuse parsers. Keep one source of schema. More in invalid structured data.

Test it

Paste your draft Article markup into the JSON-LD validator to catch missing properties early; the published page still needs a pass through Google's Rich Results Test. Since Article has no required fields, the Rich Results Test mostly reports warnings for missing recommended properties. Fix the ones you have real data for. After rollout, watch Search Console for structured data issues across all posts, and run a free SEO audit to spot posts with no structured data.