Schema Markup·4 min read

Article Schema for Blogs and News: A Field Guide

Publish a story without structured data and Google has to work out who wrote it, when, and whether it's news or a blog post. A small JSON-LD block removes the guessing: it declares the headline, images, author, publisher and dates in a format crawlers read without ambiguity. This guide covers choosing between the three article types, a worked example you can adapt, the author fields worth getting right, and the mistakes that make markup less useful. The Article Schema Generator on this site builds the block from a post URL.

Open the free Article Schema Generator All insights

Why article schema still matters for news and blogs

The case for marking up every post.

Picture a ten-year-old blog moving to a new CMS. The templates change, the old plugin that added markup is gone, and Search Console soon shows posts with no structured data detected. Nothing breaks visibly, but the site has stopped telling Google which text is the headline, which name is the byline, and which date is the original publish date.

Article markup helps Google understand the headline, images and dates it can show for a post, and the dates you declare feed into the date shown next to your result. Just as important, the markup connects each post to an author and a publisher, which is the groundwork for everything else you do on credibility.

Article, BlogPosting or NewsArticle

Three labels, one family.

This choice matters less than people fear. BlogPosting and NewsArticle are both subtypes of Article, and Google covers all three in one set of Article documentation. Accuracy is the tiebreaker: a personal or company blog should use BlogPosting, a news operation should use NewsArticle, and anything that fits neither, such as a documentation page or a long evergreen guide, can use plain Article.

The generator defaults to Blog Posting and lets you switch in the Article type dropdown. When you auto-fill from a URL, the detected type only replaces the default if you haven't changed it yourself, so a deliberate choice always sticks.

A worked NewsArticle example, field by field

Real values, not placeholders.

Say a regional paper publishes a transit story. The heart of the generated block reads: { "@type": "NewsArticle", "headline": "City Approves Night Bus Network", "datePublished": "2026-05-12T00:00:00.000Z", "author": { "@type": "Person", "name": "Rhea Kapoor" } }. Four decisions live in those few lines: the type says journalism, the headline matches the on-page H1, the date is full ISO 8601, and the author is a Person object rather than a bare string.

The complete output adds images, a publisher Organization with its logo, dateModified, keywords, and mainEntityOfPage pointing at the canonical URL. Dates you pick in the form are written as midnight UTC. If auto-fill found a full timestamp on the page, that timestamp is kept instead, time zone and all.

Google recommends several large images in 16x9, 4x3 and 1x1 crops. Put one URL per line in the Image URLs box: one URL is written as a string, two or more as an array Google can choose from.

Author fields that matter in Article markup

Where E-E-A-T meets JSON.

Google's focus on experience and expertise made author data the most closely watched part of article markup. Two fields carry most of the weight: the author's name, spelled exactly as the visible byline, and the author profile URL, which should point at a real page listing credentials and other work by the same person. The markup does not create expertise on its own. It makes the connection explicit so the evidence on the page can be linked to a person.

Use a Person type for human writers; save Organization authors for genuinely institutional content like unsigned editorials.
Point the author URL at a profile page you control, and keep that page alive; a 404 behind every byline reads badly.
Add the publisher name and a reachable logo URL. Google lists no required Article properties, but a complete publisher block makes the source clear.
Match names across posts. Jane A. Smith on one article and Jane Smith on another splits the author in two.

Mistakes that make Article schema less useful

Silent failures, mostly.

Most weak article markup fails quietly: no error in Search Console, no visible change, no explanation. These are the usual culprits worth checking first.

A headline that doesn't match the visible title, often because the CMS appends the site name to one but not the other.
datePublished changing on every deploy because the template stamps build time instead of the real publish date.
A dateModified bumped for trivial edits, which makes the date shown in results less trustworthy.
Marking up category and tag pages as articles; only actual posts should carry the type.
A single small image, when Google recommends several high-resolution crops.

Working tips for the Article Schema Generator

Small habits, better output.

Press Auto-fill from URL before typing anything. The tool reads existing Article JSON-LD, OpenGraph article tags, author meta and date tags from the live post, and chips confirm what it found: type, author, publisher, word count and keywords. It only fills fields you've left empty, so fetching first costs nothing and saves most of the typing.

Watch the description counter, which turns amber past 160 characters, since longer text tends to be cut off in snippets. Let the reading time estimate stand unless you know better: it divides the word count by 220 and lands in timeRequired as an ISO duration like PT6M. The Validation panel lists headline, image, author and dates as recommended until they are filled, and flags dates that are not ISO 8601. When it clears, choose Pretty or Minified, then Copy script or Download, and use Test in Google Rich Results Test to check the result.

Article schema beside the other generators on this site

Right tool, right page.

Use this generator for individual posts where the details deserve care. For a quick first pass across many posts, the Whole site tab in the Schema Markup Generator drafts a basic Article block for each post it crawls. For a full site audit that compares new markup with what your pages already carry, use the Automatic Schema Markup Generator.

Round out the picture with the Person Schema Generator for standalone author pages and the Organization Schema Generator for the publisher itself. Before changing anything, run the post through the Schema Markup Extractor to see exactly what markup is already live.

Try it now

Open Article Schema Generator

The tool is one click away. No sign up, no upload, no payment.

Open Article Schema Generator

Write a review