Rudra Kasturi Inc.

Article · AEO

Article schema that matches the page: author, dates and headline, with a checklist

SUMMARY

Google says Article markup helps it understand a page and show better title text, images and dates, and that markup must represent the visible content. Its documentation recommends author, datePublished, dateModified, headline and image. This post gives a checklist and mistakes list for each, drawn from the documentation; the checklist wording is our own.

Google’s Article documentation (updated 8 September 2026 as we read it) says Article markup on news, blog and sports pages can help it understand the page and show better title text, images and date information. It lists author, dateModified, datePublished, headline and image as recommended properties. It also notes there is no markup requirement for Google News features such as Top stories. The principle that runs through the guidelines: markup must be a true representation of the page.

Four Article schema fields that must match the visible page: headline, author, datePublished and dateModified

Checklist, property by property

PropertyWhat Google’s documentation saysOur check
headlineThe article title; concise, as long titles may be truncatedMatches the visible title or a clear short form
authorPerson or Organization; include every author shown on the pageNames on the page equal names in markup
author.nameOnly the name; no job title, honorific or publisherNo “Dr.” or “CEO” in the name field
author.urlA page that uniquely identifies the author, or use sameAsLink resolves and describes that person
datePublishedWhen first published, ISO 8601, with time zone recommendedEquals the date readers see
dateModifiedWhen last modified, ISO 8601, with time zone recommendedChanges only with real edits
imageRelevant to the article, not a logoSame image readers can see

Multiple authors

List each author as its own object. Google says not to merge names into one field.

An example

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Article schema that matches the page",
  "datePublished": "2026-11-05T15:00:00+05:30",
  "dateModified": "2026-11-05T15:00:00+05:30",
  "author": [{
    "@type": "Person",
    "name": "Jane Doe",
    "url": "https://example.com/authors/jane-doe/"
  }]
}

The author and URL are placeholders. Use real ones, and keep them matching the byline.

Common mistakes

  • Fake freshness. Setting dateModified to today on every deploy. Google’s helpful content page warns against changing dates to make pages look fresh when content has not changed.
  • Invented authors. Google’s guidelines say not to mislead users or impersonate any person or organization. See our post on fake authorship.
  • Markup for hidden content. Authors or dates that readers cannot see.
  • Missing time zone. Google says that without one it defaults to Googlebot’s time zone.
  • Wrong type. Use the most specific applicable type, such as BlogPosting for a blog post.

Google also says markup is not a guarantee of rich results. For AI search, it says no special schema is required; Article markup is good SEO hygiene, not an AI shortcut. See our schema decision table.

What to do

  1. Open a recent post and compare each visible field with its markup.
  2. Fix any mismatch in the template, not page by page.
  3. Link author names to real profile pages.
  4. Test with the Rich Results Test and the URL Inspection tool.
  5. Add breadcrumbs too, using our breadcrumb guide.

Sources