Unit 2: Local & Content · Lesson 9 of 15

Article and BlogPosting

Every blog post you publish can tell machines its headline, its author, and when it was written. It's one of the easiest wins in schema, because your CMS already knows all of it.

8 min readIntermediateArticle, BlogPosting, NewsArticle, TechArticle

Pick your type

Schema.org has a family of article types. They all share the same properties, so the choice is mostly about being accurate. Pick the most specific one that's true.

TypeUse it for
ArticleThe general-purpose parent. Safe for any editorial content if nothing more specific fits.
BlogPostingA post on a blog. Fern & Ink's "Journal" posts are BlogPostings.
NewsArticleActual news reporting, usually from a news publisher. A studio announcing a new hire isn't really news journalism; BlogPosting is fine.
TechArticleHow-to and technical documentation. This course uses it for every lesson (View Source on this page to see it).

Don't overthink it. Google's article docs cover Article, BlogPosting, and NewsArticle with the same guidance, and TechArticle is still an Article underneath. Picking BlogPosting vs. Article won't make or break anything.

The code

Here's a Fern & Ink journal post, "How to Choose Paper for Letterpress Printing," written by founder Maya Lund.

JSON-LD · BlogPosting
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "@id": "https://fernandink.example/journal/choosing-letterpress-paper/#article",
  "headline": "How to Choose Paper for Letterpress Printing",
  "description": "Cotton, bamboo, or recycled? A printer's guide to picking paper that takes a deep impression and feels great in the hand.",
  "image": [
    "https://fernandink.example/images/paper-guide-16x9.jpg",
    "https://fernandink.example/images/paper-guide-4x3.jpg",
    "https://fernandink.example/images/paper-guide-1x1.jpg"
  ],
  "datePublished": "2026-09-03T09:00:00-05:00",
  "dateModified": "2026-10-12T14:30:00-05:00",
  "author": {
    "@type": "Person",
    "@id": "https://fernandink.example/about/#maya",
    "name": "Maya Lund",
    "url": "https://fernandink.example/about/"
  },
  "publisher": { "@id": "https://fernandink.example/#organization" },
  "mainEntityOfPage": { "@id": "https://fernandink.example/journal/choosing-letterpress-paper/#webpage" },
  "isPartOf": { "@id": "https://fernandink.example/#website" }
}

Line by line

Google's own docs say Article markup has no required properties. Instead, it recommends a short list. Those are tagged Recommended below; the rest are our advice for connecting the post to the rest of your site.

PropertyStatusWhat it does
headlineRecommendedThe post's title. Keep it the same as the visible H1.
imageRecommendedThe post's main image. One URL is fine; several crops are better (see below).
datePublishedRecommendedWhen the post first went live.
dateModifiedRecommendedWhen the post was last meaningfully changed.
authorRecommendedWho wrote it, as a Person (or Organization) with a name and a url.
descriptionOptionalA one-sentence summary. Your meta description or excerpt works well.
publisherOptionalThe business or site behind the post. Point it at your #organization @id.
mainEntityOfPageOptionalSays "this article is the main thing on this web page," linking it to the page's WebPage block.
isPartOfOptionalSays which site the article belongs to. Here, Fern & Ink's #website.

Images: three crops if you can

Google suggests giving several high-resolution versions of the image in 16:9, 4:3, and 1:1 ratios, each at least 50,000 pixels (width times height, so 300×200 is too small; 1200×675 is plenty). That way, whatever shape a search feature needs, it has a good crop. If your CMS only makes one size, one good image is still fine. The image should be the real one from the post, not your logo.

Dates: keep them honest

Use full ISO 8601 dates with a time and timezone offset, like 2026-09-03T09:00:00-05:00. Without a timezone, Google has to guess.

More important: only change dateModified when you actually change the post. Fixing a typo isn't an update. Bumping every post's date to "today" so they all look fresh is a well-known trick, and it erodes trust in your dates. If the page shows "Updated October 12," the markup should say October 12 too.

Authors: a real person with a real page

Google's guidelines ask for the author as a Person (or Organization) with two things:

  • name: just the name. "Maya Lund," not "Maya Lund, Founder" or "By Maya Lund." Job titles belong in jobTitle.
  • url: a page about that person, like an author or about page.

If a post has two authors, give author an array with two separate Person objects. Don't jam both names into one string.

Notice the @id on Maya, too: https://fernandink.example/about/#maya. Her full profile lives on the about page, and every post she writes can point to the same @id. We'll build that profile in the Person lesson.

Common mistakes

  • Author as plain text. "author": "Maya" is technically allowed by Schema.org but gives machines very little. Use a Person with a name and url.
  • Headline doesn't match the H1. If you rewrite the title for SEO, update the markup too.
  • Fake freshness. Auto-updating dateModified on every page load or every deploy.
  • Logo as the article image. Use an image that's actually in the post.

CMS tip: let your post fields do the work

You should almost never hand-write Article markup. Every CMS already stores everything you need. Map the fields once in your post template, and every post gets correct schema forever.

Post field in your CMSSchema property
Titleheadline
Excerpt or meta descriptiondescription
Featured image (and its crops)image
Publish datedatePublished
Last updated datedateModified
Author (linked to an author profile)author → name, url, @id
Post URL@id, mainEntityOfPage

WordPress SEO plugins like Yoast and Rank Math already do this mapping for you, so check what they output before adding your own (see the Yoast SEO guide). In Webflow, Craft, or a headless setup, you'll build the template yourself: output the JSON in the <head>, fill each value from the field, and run every string through a JSON encoder so a quote mark in a title can't break the block.

Try it

Take a real post from a site you work on. Using the field table above, write down where each value comes from in your CMS. Then check: does the publish date in the CMS match the date shown on the page? Does the author have a page you could use for url? If not, that's your first fix.

Check yourself

  • I can pick between Article, BlogPosting, NewsArticle, and TechArticle.
  • I know Google lists no required Article properties, only recommended ones.
  • My dates include a timezone, and dateModified only changes when the content does.
  • My author is a Person with a name and a url.
  • My markup is generated from post fields, not typed by hand.
Go deeper on Double Atari

Article markup alongside LocalBusiness and Service: Schema Markup Explained, Part 2: LocalBusiness, Service, Article, and Local Search.