Article Schema: Make Your Blog Content Citable by AI

Article schema tells search engines and AI systems that your page is a piece of authored content with a publication date, an author, a publisher, and a topic. For ecommerce stores investing in content marketing -- blog posts, buying guides, comparison articles, industry analysis -- Article schema is the difference between content that AI systems can confidently cite and content they skip because they cannot verify its authorship, recency, or authority. Pages with dateModified schema receive 1.8x more AI citations than pages without it, and the highest-performing schema combination -- Article schema plus FAQ schema plus author markup -- delivers an 89% higher citation probability compared to pages with no structured data.

Why Article Schema Matters for Ecommerce Content

Most ecommerce stores produce content. Buying guides, ingredient explainers, styling tips, industry trends, product comparisons -- these pages drive organic traffic and build authority. But without Article schema, that content is structurally invisible to AI.

AI systems need attribution data to cite you. When an AI system generates an answer and includes a citation, it needs to attribute the information: who wrote this, when was it published, what organization published it. Article schema provides this data in a machine-readable format. Without it, the AI would need to parse your page layout, find an author byline (if one exists), locate a date (if visible), and guess the publisher. Most AI systems will not do that work when a competitor's page provides the same data in clean JSON-LD.

Freshness is a ranking signal for AI. The datePublished and dateModified properties in Article schema give AI systems explicit recency signals. For queries where current information matters -- "best sunscreens for 2026," "latest clean beauty trends," "current shipping delays" -- pages with recent modification dates get priority. A BrightEdge study found that sites implementing structured data and FAQ blocks saw a 44% increase in AI search citations.

Author authority compounds over time. When your Article schema consistently attributes content to the same author with proper Person schema, AI systems build an author entity profile. That author becomes associated with specific topics. Over time, articles by a recognized author on a topic they have established authority in receive higher citation priority.

Complete Article Schema Example

Here is a production-ready Article JSON-LD block for an ecommerce blog post:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Choose the Right Vitamin C Serum for Your Skin Type",
  "description": "A dermatologist-reviewed guide to selecting vitamin C serums based on skin type, concentration preferences, and ingredient compatibility.",
  "image": [
    "https://example.com/images/vitamin-c-guide-hero.jpg",
    "https://example.com/images/vitamin-c-guide-comparison.jpg"
  ],
  "datePublished": "2025-11-20T08:00:00+00:00",
  "dateModified": "2026-03-15T14:30:00+00:00",
  "author": {
    "@type": "Person",
    "name": "Dr. Sarah Chen",
    "url": "https://example.com/about/sarah-chen",
    "jobTitle": "Head of Product Development",
    "worksFor": {
      "@id": "https://example.com/#organization"
    },
    "sameAs": [
      "https://www.linkedin.com/in/sarahchenskincare",
      "https://www.instagram.com/drsarahchenskin"
    ]
  },
  "publisher": {
    "@id": "https://example.com/#organization"
  },
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://example.com/blog/choose-vitamin-c-serum"
  },
  "wordCount": "2400",
  "articleSection": "Skincare Guides",
  "keywords": ["vitamin C serum", "skincare routine", "L-ascorbic acid", "skin type guide"],
  "inLanguage": "en-US",
  "isAccessibleForFree": true,
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": [".article-summary", ".key-takeaways"]
  }
}

Understanding Each Property

Identity and Content Properties

@type -- Use Article for general blog posts and guides. Use NewsArticle for time-sensitive news content. Use BlogPosting (a subtype of Article) for blog-style content. For most ecommerce content, Article is the right choice.

headline -- The title of your article. Keep it under 110 characters. This is what AI systems display when citing your content.

description -- A summary of the article's content. Write this as if it were the answer to "What is this article about?" AI systems often use this description in citations.

image -- One or more images associated with the article. Include your hero image at minimum. Google recommends images that are at least 1200 pixels wide.

mainEntityOfPage -- The canonical URL of the page this article appears on. This helps search engines understand that the article is the primary content of the page, not a sidebar or widget.

Author Properties: The Citation Multiplier

Author markup is one of the most impactful properties for AI citation. Here is why and how to implement it correctly.

Use Person type with details. A name alone is the minimum. Adding url, jobTitle, worksFor, and sameAs transforms a name into a verifiable entity:

{
  "author": {
    "@type": "Person",
    "name": "Dr. Sarah Chen",
    "url": "https://example.com/about/sarah-chen",
    "jobTitle": "Head of Product Development",
    "description": "Board-certified dermatologist with 12 years of experience in cosmetic formulation.",
    "worksFor": {
      "@id": "https://example.com/#organization"
    },
    "sameAs": [
      "https://www.linkedin.com/in/sarahchenskincare"
    ]
  }
}

Why author details matter for AI: When ChatGPT or Perplexity cites an article, it evaluates source credibility. An article by "Dr. Sarah Chen, Head of Product Development at GlowLab Skincare" with a LinkedIn profile carries more weight than an article by "Admin" or with no author at all. The AI can cross-reference the author's credentials, employer, and topic expertise.

Multiple authors: If an article has multiple authors, use an array:

{
  "author": [
    {
      "@type": "Person",
      "name": "Dr. Sarah Chen",
      "url": "https://example.com/about/sarah-chen"
    },
    {
      "@type": "Person",
      "name": "James Park",
      "url": "https://example.com/about/james-park"
    }
  ]
}

Publisher Properties

publisher -- The organization that published the article. For ecommerce blog content, this is your company. Reference your Organization schema using @id:

{
  "publisher": {
    "@id": "https://example.com/#organization"
  }
}

If you do not have Organization schema elsewhere on the site, you can inline it:

{
  "publisher": {
    "@type": "Organization",
    "name": "GlowLab Skincare",
    "url": "https://example.com",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/images/logo.png"
    }
  }
}

Date Properties: The Freshness Signal

datePublished -- When the article was first published. Use ISO 8601 format with timezone: 2025-11-20T08:00:00+00:00.

dateModified -- When the article was last substantively updated. This is the single most important freshness signal for AI systems. Pages with dateModified schema receive 1.8x more AI citations than pages without it.

Critical best practice: Update dateModified only when you make substantive content changes. Fixing a typo or updating a CSS class does not warrant a dateModified update. Adding new information, updating statistics, revising recommendations, or expanding sections does. AI systems that see frequent dateModified changes without corresponding content updates may deprioritize the signal.

The biggest mistake merchants make: Implementing Article schema on a blog but never updating dateModified when content is refreshed. If your "Best Sunscreens for 2025" guide was updated in March 2026 with new products but the schema still says dateModified: "2025-06-15", AI engines treat the content as 9 months stale.

Article Schema for Different Content Types

Buying Guide

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "The Complete Guide to Choosing a Pour-Over Coffee Dripper",
  "description": "Compare ceramic, glass, and plastic pour-over drippers by heat retention, durability, price, and brew quality.",
  "datePublished": "2026-01-10T10:00:00+00:00",
  "dateModified": "2026-04-01T09:00:00+00:00",
  "articleSection": "Buying Guides",
  "author": {
    "@type": "Person",
    "name": "Marcus Rivera",
    "jobTitle": "Coffee Equipment Specialist"
  },
  "publisher": {
    "@id": "https://example.com/#organization"
  }
}

Product Comparison

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Ceramic vs Glass Pour-Over Drippers: Which Brews Better Coffee?",
  "description": "Head-to-head comparison of ceramic and glass pour-over drippers testing heat retention, brew time, and cup quality.",
  "datePublished": "2026-02-28T08:00:00+00:00",
  "dateModified": "2026-02-28T08:00:00+00:00",
  "articleSection": "Product Comparisons",
  "about": [
    {
      "@type": "Product",
      "name": "Ceramic Pour-Over Dripper",
      "url": "https://example.com/products/ceramic-dripper"
    },
    {
      "@type": "Product",
      "name": "Glass Pour-Over Dripper",
      "url": "https://example.com/products/glass-dripper"
    }
  ]
}

Industry Trend Article

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Clean Beauty Trends for 2026: What Consumers Actually Want",
  "description": "Analysis of 2026 clean beauty trends based on consumer survey data and ingredient trend reports.",
  "datePublished": "2026-01-05T08:00:00+00:00",
  "dateModified": "2026-03-20T11:00:00+00:00",
  "articleSection": "Industry Trends",
  "keywords": ["clean beauty", "2026 trends", "consumer preferences", "ingredient transparency"]
}

The Speakable Property

The speakable property identifies sections of your article that are especially suitable for text-to-speech playback and AI voice assistant citation. This is increasingly relevant as voice-based AI assistants grow:

{
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": [".article-summary", ".key-takeaways"]
  }
}

You can also use XPath instead of CSS selectors:

{
  "speakable": {
    "@type": "SpeakableSpecification",
    "xpath": [
      "/html/body/article/header/p",
      "/html/body/article/section[@class='key-takeaways']"
    ]
  }
}

The speakable property tells AI voice assistants which parts of your article to read aloud when users ask related questions. Write these sections as clear, self-contained summaries that make sense when spoken without visual context.

Combining Article Schema With Other Types

Article schema becomes most powerful when combined with complementary types on the same page:

Article + FAQPage

If your article includes a FAQ section, add FAQPage schema alongside Article schema. This combination delivers an 89% higher citation probability:

[
  {
    "@context": "https://schema.org",
    "@type": "Article",
    "headline": "How to Choose the Right Vitamin C Serum",
    "dateModified": "2026-03-15T14:30:00+00:00",
    "author": { "@type": "Person", "name": "Dr. Sarah Chen" },
    "publisher": { "@id": "https://example.com/#organization" }
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Can you use vitamin C serum with retinol?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes, but use them at different times. Apply vitamin C in the morning and retinol at night to avoid irritation."
        }
      }
    ]
  }
]

Article + BreadcrumbList

Always pair Article schema with BreadcrumbList to signal where this content sits in your site hierarchy:

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com" },
    { "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://example.com/blog" },
    { "@type": "ListItem", "position": 3, "name": "Skincare Guides", "item": "https://example.com/blog/skincare-guides" },
    { "@type": "ListItem", "position": 4, "name": "How to Choose the Right Vitamin C Serum" }
  ]
}

Common Article Schema Mistakes

Using "Admin" or generic author names. An author named "Admin," "Staff Writer," or "Team" provides no entity signal. Use real names with real credentials.

Never updating dateModified. If your content has been updated since publication but the schema still shows the original date, AI systems treat it as stale. Automate dateModified updates in your CMS.

Missing publisher information. Google requires a publisher for Article schema. Without it, your article may not qualify for rich results, and AI systems lose a trust signal.

Using Article schema on product pages. Product pages should use Product schema, not Article schema. Use Article schema only on content pages where the primary purpose is informational.

Headline mismatch. The headline in your schema must match the H1 on the page. A mismatch between schema headline and visible title is a policy violation.

Omitting wordCount. While optional, wordCount helps AI systems gauge content depth. A 2,400-word guide signals more comprehensive coverage than a 300-word post.

Article schema is the structured data equivalent of a byline, dateline, and masthead for your content. It tells AI systems: this was written by a real person, published by a real organization, on a specific date, and updated when the facts changed. That is exactly the information AI needs to cite you with confidence.

Up next

Testing Structured Data

Tools and methods for testing your structured data implementation.