How to Implement Article Schema for Blog Posts

Article schema is the foundation of blog post structured data. It tells search engines and AI models that your page is a published editorial article — not a product page, not a homepage, not a landing page. This distinction matters for AI citations because AI engines like ChatGPT and Perplexity prefer citing attributed, dated, published content over unattributed or undated content. Article schema is also a core E-E-A-T signal, declaring who wrote the content, when it was published, and who published it.

Step 1: Choose the correct Article type

schema.org offers several Article subtypes:

• BlogPosting — for blog posts (most common choice for blog content)
• NewsArticle — for news content
• TechArticle — for technical documentation
• Article — general fallback

Use BlogPosting for blog content. It is the most specific type and is fully supported by Google rich results. Using Article works but is less precise.

Step 2: Set the headline to match your H1

The headline property is the article title. It must match the visible H1 on the page exactly. Search engines and AI models use this to confirm that the schema describes the page they are reading.

"headline": "How to Implement Article Schema for Blog Posts"

If your H1 says "How to Implement Article Schema for Blog Posts" but your schema says "Article Schema Guide," that mismatch creates a trust gap. Use the Meta Title & Description Checker to verify your title tags match your headings.

Step 3: Add author as a Person type

The author property should be a Person type with a name that matches the byline on the page and a url pointing to the author's bio page:

"author": {
  "@type": "Person",
  "name": "Izajul Haque",
  "url": "https://example.com/about"
}

This is critical for E-E-A-T. Google and AI engines use author identity to assess content credibility. A named, linked author with a bio page is a strong expertise signal. An anonymous or missing author weakens it.

Step 4: Set datePublished and dateModified

Both dates use ISO 8601 format (YYYY-MM-DD):

"datePublished": "2026-09-15",
"dateModified": "2026-09-15"

• datePublished — the original publication date. Never changes.
• dateModified — the date of the last significant content update. Update this whenever you revise the article body.

If you publish on September 15 and significantly update on October 1:

"datePublished": "2026-09-15",
"dateModified": "2026-10-01"

AI engines use dateModified to assess content freshness. Outdated content is less likely to be cited for queries that benefit from current information.

Step 5: Add publisher as an Organization or Person type

The publisher property identifies the entity that published the article:

"publisher": {
  "@type": "Organization",
  "name": "Izajul Haque",
  "logo": {
    "@type": "ImageObject",
    "url": "https://example.com/logo.png",
    "width": 512,
    "height": 512
  }
}

For solo authors publishing under their own name, use Person as the publisher type. For organizations, use Organization with a logo. The logo must be a valid image URL with specified dimensions.

Step 6: Include image and mainEntityOfPage

"image": ["https://example.com/images/article-hero.jpg"],
"mainEntityOfPage": {
  "@type": "WebPage",
  "@id": "https://example.com/blog/how-to-implement-article-schema"
}

• image — at least one image URL. Use the article's hero image or OG image. Google requires this for Article rich results.
• mainEntityOfPage — the canonical URL of the article. This tells search engines what the page is primarily about and helps with deduplication.

Complete Article schema example

Here is a complete, valid BlogPosting JSON-LD block combining all the properties above:

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to Implement Article Schema for Blog Posts",
  "description": "Article schema tells search engines and AI models that your page is a published article. Here is a step-by-step guide to implementing valid Article schema.",
  "author": {
    "@type": "Person",
    "name": "Izajul Haque",
    "url": "https://example.com/about"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Izajul Haque",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png",
      "width": 512,
      "height": 512
    }
  },
  "datePublished": "2026-09-15",
  "dateModified": "2026-09-15",
  "image": ["https://example.com/images/article-hero.jpg"],
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://example.com/blog/how-to-implement-article-schema"
  },
  "articleSection": "How-To",
  "isPartOf": {
    "@type": "Blog",
    "name": "Izajul Haque Blog",
    "url": "https://example.com/blog"
  }
}

Step 7: Validate with Google Rich Results Test

Test the page URL in Google Rich Results Test. Article/BlogPosting is a supported rich result type. The tool will show:

• Whether the schema is detected and valid
• Any errors (must fix) or warnings (should fix)
• How the article rich result would appear in Google

Fix all errors before deployment. Common errors include missing author, missing datePublished, headline not matching the H1, and missing image. See schema markup for AI visibility for the broader strategy, and use the free SEO tools for related checks.

Common mistakes

• Using the wrong Article subtype — BlogPosting for blogs, NewsArticle for news. Using a generic Article when a more specific type exists loses precision.
• Headline not matching the H1 — The headline property must match the visible H1 exactly. Mismatches cause validation warnings and reduce trust signals.
• Missing author or using a generic author — "Admin" or "Staff Writer" as the author name weakens E-E-A-T. Use a real person's name linked to a bio page.
• Not updating dateModified after content revisions — If you significantly update an article but leave datePublished as both dates, AI engines may consider the content stale. See how AI Overviews are changing search for why freshness matters.
• Missing the image property — Google requires at least one image for Article rich results. Without it, the schema will show an error in validation. Explore SEO consulting and the glossary for more on structured data and E-E-A-T.