Schema Markup·4 min read

Article Schema for News and Blogs: A Field Guide

Publish a story without structured data and Google has to guess who wrote it, when, and whether it's news or opinion. Getting article schema for news and blogs right removes the guessing: a small JSON-LD block declares the headline, author, publisher, and dates in a format crawlers parse without ambiguity. This guide walks through choosing between the three article types, a real example you can adapt, the author fields worth sweating over, and the mistakes that quietly get markup discarded. The Article Schema Generator on this site builds all of it from a URL.

Open the tool All insights

Why article schema for news and blogs still matters

The case for marking up every post.

Picture a ten-year-old blog migrating to a new CMS. The templates change, the old plugin that injected markup is gone, and within a week Search Console starts logging pages with no detected structured data. 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.

Marked-up articles are eligible for richer presentation in Google, headline and image treatments in Top Stories and Discover among them, and the dates you declare influence the timestamp shown next to your result. Just as important, the markup connects each post to an author entity and a publisher, which is the groundwork for everything else you do on credibility.

Article vs BlogPosting type, and where NewsArticle fits

Three labels, one family.

The article vs blogposting type question comes up constantly and matters less than people fear. BlogPosting and NewsArticle are both subtypes of Article, and Google's documentation treats the whole family as one rich result category. Accuracy is the tiebreaker: a personal or company blog should send BlogPosting, a journalism operation should send NewsArticle, and anything that fits neither, a documentation page or a long evergreen guide, can use plain Article.

The Article Schema Generator defaults to BlogPosting and lets you switch in the Article type dropdown. When you auto-fill from a URL, the detected type only wins if you haven't changed that default, 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 the featured image, a publisher Organization with its logo, dateModified, keywords, and mainEntityOfPage pointing at the canonical URL. Enter plain dates in the form and they're expanded to ISO datetimes automatically, so you never hand-format a timestamp.

Author fields that matter in Article markup

Where E-E-A-T meets JSON.

Google's push on experience and expertise made author data the most scrutinized corner 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.

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.
Keep the publisher logo URL valid and reachable, since the publisher block is required for the article rich result.
Match names across posts. Jane A. Smith on one article and Jane Smith on another splits the author entity in two.

Mistakes that get Article schema ignored

Silent failures, mostly.

Most broken article markup fails quietly: no error in Search Console, no rich treatment, 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.
A missing publisher logo, which invalidates the block for the article rich result even when every other field is perfect.
datePublished changing on every deploy because the template stamps build time instead of the real publish date.
Marking up category and tag pages as articles; only actual posts should carry the type.
Featured images below Google's recommended resolution, which keeps the post out of image-led placements.

Working tips for the Article Schema Generator

Small habits, better output.

Run auto-fill before typing anything. The tool reads existing JSON-LD, OpenGraph article tags, author meta, and date tags from the live URL, and it only fills fields you've left empty, so fetching first costs nothing and saves most of the typing.

Watch the description counter and stop near 160 characters, since longer text gets truncated in snippets. And let the reading time estimate stand: it's derived from the real word count at roughly 220 words per minute and lands in timeRequired as a tidy ISO duration like PT6M.

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 coverage across an entire site in one pass, the Schema Markup Generator crawls every URL and assigns types automatically, articles included, though at lower depth per page.

Round out the entity picture with the Person Schema Generator for standalone author pages and the Organization Schema Generator for the publisher itself. And before changing anything, run your post through the Schema 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