Article Schema Generator

Is Article markup eligible for a Google rich result?

Article markup has no required properties. It helps Google understand the headline, images, dates and author of a news, sports or blog article, and can influence the title, image and date shown for it in results.

Status verified on 24 September 2026. Google’s documentation: https://developers.google.com/search/docs/appearance/structured-data/article

About Article structured data

Article markup is the most widely used structured data type, but it is also the one with the least visible effect. Google describes it as helping the search engine understand the page and display better title text, images and date information; it does not usually produce a distinct rich result of its own.

The properties that matter most are the ones about identity and freshness: who wrote it, when it was first published and when it last changed. Consistent, honest values for those help Google connect authors across your site and show accurate dates.

Common Article schema mistakes

• A headline that is too long. Google may truncate long titles, and the headline property is meant to be concise; keep it under about 110 characters.
• Putting more than the name in the author field — for example “Dr Amina Rahman, Senior Editor at Example News”. Use only the name, and put a separate author for each person.
• Dates without a time zone. ISO 8601 dates with a UTC offset, such as 2026-03-18T09:00:00+05:00, remove any ambiguity about when the article was published.
• Setting dateModified to today on every visit. It should change only when the content actually changes.
• Choosing NewsArticle for content that is not news. Use BlogPosting for blog posts and Article as a general fallback.
• Images that are not crawlable or are smaller than the recommended size. An image should represent the article and be indexable.

Article schema example

A blog post with three image ratios, both dates with time zones, an author and a publisher, as generated on this page, is shown below.

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How we cut our page load time by 40%",
  "description": "A step-by-step account of the changes that made our site faster.",
  "image": [
    "https://example.com/img/page-speed-16x9.jpg",
    "https://example.com/img/page-speed-4x3.jpg",
    "https://example.com/img/page-speed-1x1.jpg"
  ],
  "datePublished": "2026-03-18T09:00:00+05:00",
  "dateModified": "2026-04-02T14:30:00+05:00",
  "author": [
    {
      "@type": "Person",
      "name": "Amina Rahman",
      "url": "https://example.com/authors/amina-rahman"
    }
  ],
  "publisher": {
    "@type": "Organization",
    "name": "Example Engineering",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/img/logo-600x60.png"
    }
  },
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://example.com/blog/page-load-40-percent"
  }
}