Article Schema: 2026 Guide to Article Markup

Administrator in Search Engine Optimization Oct 19 / 1 week ago

Article schema helps Google understand what a page is, who wrote it and when it appeared, and a common mistake is marking up authors or dates that do not match what the page shows. Another is stamping a new datePublished on every edit. This guide covers the types, the properties, the testing steps and the fixes. The examples are fictional and come from Portland, Munich and Seoul.

What is article schema and why does it matter?

Article schema is structured data that describes a news, blog or sports article page. Google says it can help Google understand more about the page and show better title text, images and date information in search results. It also reaches other Google properties, such as Google News and the Google Assistant.

Think of article schema as a label on the page. The visible article tells readers the story, while article markup tells a crawler the headline, the author, the image and the dates in a standard form. Google's wording is careful, so ours will be too. Article schema helps Google understand the page, and the documentation does not promise a ranking boost or a click lift. The official Google article documentation is short, so read it before you build anything. For the wider basics of the format, see our JSON-LD schema markup guide, which this post does not repeat.

Which article types does Google support?

Google accepts three schema.org types for article markup, which are Article, NewsArticle and BlogPosting. The page must be based on one of them. All three share the same recommended properties in the Google documentation, so the choice mostly tells Google what kind of page it is reading.

Our take: match the type to the page. Use NewsArticle for reported news, BlogPosting for a blog entry and plain Article when neither label fits, such as a long guide or a sports report. Google does not say that one type beats another, so do not lose sleep over the choice. Consider a fictional food blog in Portland, Oregon. Its recipe posts use BlogPosting while its weekly market report uses NewsArticle. Both pages carry the same recommended properties, and only the label changes. The formal definitions live at schema.org Article, which lists NewsArticle among its subtypes.

Which properties does Google recommend for article markup?

No property is strictly required. Google says to add the recommended properties that apply to your content. The list is author, author.name, author.url, dateModified, datePublished, headline and image. Fill in as many as you can truthfully, because each one gives Google a clearer picture of the page.

The table below follows the Google documentation.

The status column is copied from the Google article documentation. Because no property is required, a clean test result says little about quality, so fill in the fields on purpose. Because the date fields are recommended and not required, a clean test says nothing about whether your dates are right. Check them against the visible page by hand.

Do you need markup to appear in Top stories?

No. Google says there is no markup requirement to be eligible for Google News features like Top stories. You can still add Article markup to tell Google more explicitly what the content is about, such as that it is a news article, who the author is and what the title of the article is.

So treat the markup as clarity and not as an entry ticket. A fictional news site in Munich already publishes clear pages, bylines and dates. Article schema gives it a tidy description of each story, and it does not buy a place in any feature. For the editorial side of those features, read our Google News and Top stories guide. If your stories also reach readers through feeds and suggestions, our Google Discover guide covers that route.

How should you mark up authors?

Include every author that the page shows, and give each one its own author entry. Put only the person's name in author.name, and add a type and a url, or sameAs, so Google can tell who they are. Use Person for people and Organization for organizations, and never use Thing.

Google gives a short list of author markup best practices, and they are easy to follow. Do not merge two writers into one field, such as one name string with a comma. Do not add a job title, an honorific, the publisher name or words like posted by to author.name. Use the proper properties for those details instead, and use the publisher property for the publisher. If the author URL is an internal profile page, Google recommends marking up that author with profile page structured data. The sameAs property is an accepted alternative to url. Our guide to author pages and bylines covers the page itself, and our E-E-A-T and helpful content guide covers trust more broadly, so this section sticks to author markup inside article schema.

How do datePublished and dateModified work?

The datePublished property is when the article was first published, and dateModified is when it was most recently changed. Both use ISO 8601 format, and Google recommends adding timezone information. Without it, Google uses the timezone of Googlebot. Add them when you want to give Google more accurate date information.

A common mistake is to stamp a fresh datePublished each time an editor fixes a typo. Our take: keep datePublished fixed and move dateModified only for real changes, and keep the dates in your article schema in line with the dates a reader sees on the page. The Google article documentation does not spell out either rule, so treat both as good practice. The documentation links these properties to date information in search results, but it does not say how Google picks a date, so we make no promise about what will show. If you update old stories on a schedule, our content refresh and decay guide explains which pages deserve the work and which deserve a quiet retirement.

What should the headline and image hold?

The headline is the title of the article, and Google suggests a concise one because long titles may be truncated on some devices. The image should represent the article, not a logo or a caption. Image URLs must be crawlable and indexable, and the image must match the marked up content.

These two fields are easy to get wrong in article markup. Google also says images must be in a format that Google Images supports. For best results it suggests several high-resolution images in wide, classic and square shapes, so the same story can fit more than one layout. The headline is a separate field from the page title, and how Google picks title text is a wider topic that our guide to Google title links explains. Image files deserve care too, and our image alt text guide shows how to describe them for readers who cannot see them.

How do you add article markup step by step?

Add the recommended properties that apply, follow the guidelines, then validate with the Rich Results Test and fix critical errors. Deploy a few pages and check them with URL Inspection, making sure robots.txt, noindex or a login does not block them. Then submit a sitemap so Google learns about later changes.

At that same Munich site, the developer builds the byline and date on the page first and then generates the article markup from the same data, so the two cannot drift apart. A short checklist keeps the rollout honest.

• Choose Article, NewsArticle or BlogPosting for each template.
• Build the article markup from the same data as the visible byline and date.
• List every visible author as its own author entry.
• Keep datePublished fixed and update dateModified on real edits.
• Validate the markup in the Rich Results Test before you deploy.
• Inspect a few live pages and submit an updated sitemap.

If you use a CMS, a plugin may be easier than hand coding. If your pages are built with JavaScript, Google has a separate guide on generating structured data with scripts. Remember that it can take several days after publishing for Google to find and crawl a page. Our XML sitemaps guide covers the sitemap step, and our technical SEO audit guide shows where markup checks fit in a wider routine.

How do you test your markup with Search Console and Google tools?

Paste the URL into the Rich Results Test and fix any critical errors. Then use the URL Inspection tool to see how Google reads the live page. If someone else runs your site, forward any Search Console message about the issue to them.

Google adds that you may also fix the non-critical issues the tool flags, since they can raise the quality of your data, although that is not needed to be eligible for rich results. When something breaks, check the list of structured data errors and the unparsable structured data report in Search Console. Our take: a jump in article schema errors right after a release is worth checking against your template changes first. If the tool is new to you, start with our Search Console guide, and use the structured data debugging guide when errors pile up.

Why is Google not showing my article features?

Google does not guarantee that features built from structured data will appear. Check that the page is crawlable, that the article markup has no errors and that it follows the guidelines. A clean test does not rule out spammy content or spammy markup, because the Rich Results Test cannot catch problems that are not syntax issues.

Work through the causes in order. First, confirm that the page is open to Google, since a robots.txt rule, a noindex tag or a login wall will hide it. Our robots.txt and noindex guide shows how to check. Next, review the guidelines again, including Search Essentials and the general structured data rules. A structured data manual action means Google ignores the article markup, although the page can still appear in results. Fix the problem, use the Manual Actions report, and allow time for recrawling and reindexing before you judge the outcome. Google also offers a step-by-step guide for missing rich results, and the Search Central forum is open if you are stuck.

How should a Korean publisher think about Naver?

A publisher in Seoul, South Korea should still add valid article markup for Google, but it should not treat Google as the only audience. Our take: Naver is a major engine in Korea and has its own tools and habits. Build the article markup once, then plan separate work for Naver and for Korean language fields.

A fictional news blog in Seoul, South Korea, writes every headline and author name in Korean so that the visible byline and the markup show the same words. The team then reads our Naver SEO guide for Korea to decide what else matters on that engine. We do not claim that Naver reads Google markup in any particular way, and the Google documentation says nothing about it, so test where your readers search.

How do you keep article markup healthy over time?

Treat the markup as part of the template. Recheck it after each redesign, keep it in step with the visible byline and dates, and watch Search Console for new errors. Fix canonical tags on multi-part articles so they point at each page or a view-all page, not at page one.

That canonical rule comes straight from the Google guidelines, and our canonical tags guide explains the idea in full. Google also says that if readers must pay or register, you should consider structured data for subscription and paywalled content. Markup drifts when a team renames an author, the page updates, and the old name stays in the data. Trails of links matter as well, so see our breadcrumbs guide for the hierarchy markup that often sits beside article markup. Star ratings follow separate rules, which we cover in our review snippet guide. Keep the routine boring and repeatable, and you avoid the mistake of markup that no longer matches the page.

Frequently asked questions about article schema

Does article schema improve my rankings?

Google's documentation does not say that article markup changes where a page ranks. It says the markup can help Google understand the page and show better title text, images and date information in search results. Treat the markup as a clarity feature. Focus on a useful article, honest labels and a page that answers the search. Those habits help readers whether or not Google shows an enhanced result for a given page.

Which type fits a normal blog post?

Google accepts Article, NewsArticle and BlogPosting, and it lists the same recommended properties for all three. Our take: BlogPosting is the natural label for a blog entry, NewsArticle suits reported news, and Article is a safe general choice. The documentation does not say that one type ranks or displays better than another, so pick the one that describes the page most honestly and keep it consistent across the template.

Can a page list more than one author?

Yes. When a page shows several authors, list each one in its own author field, and make sure everyone presented as an author on the page also appears in the article markup. Google says not to merge two names into one field. Each entry should carry a name, a type and a url or sameAs, so that Google can tell the people apart and understand who they are.

Should I put a job title in the author name?

No. Google says author.name should hold only the name of the author. Do not add the publisher name, a job title, an honorific or introductory words such as posted by. If you want to share a job title, use the jobTitle property, and use the publisher property for the publisher. Keeping the name clean helps Google match the author across pages and features without guessing which words belong to the person.

Do I need to add dateModified?

No, it is recommended and not required. Google says to add dateModified if you want to provide more accurate date information. Leaving it out is allowed, because the documentation lists no required property. If you do add it, use ISO 8601 format with timezone information, and change it only when the article truly changes. Our take: a date that moves on every minor edit makes the markup less honest.

Can I use my logo as the article image?

Google says to use images that are relevant to the article, rather than logos or captions. The image must represent the marked up content, must be crawlable and indexable, and must be in a format that Google Images supports. Test the image URL with the URL Inspection tool to see whether Google can reach it. A real photo or chart from the story is almost always the better choice than a brand mark.

What happens after a structured data manual action?

If you receive a structured data manual action against a page, Google ignores the structured data on it, although the page can still appear in search results. Open the Manual Actions report in Search Console, fix the markup and review the guidelines again. Spammy content or spammy markup can cause the problem, and a syntax test will not catch those issues, so review the article markup on your pages with care.

Does the markup work for paywalled or multi-part articles?

Yes, with extra care. For multi-part articles, make the canonical tag point at each individual page or at a view-all page, and not at page one of the series. If readers must pay or register for access, Google suggests that you consider structured data for subscription and paywalled content. Both points come from the technical guidelines in the article documentation, so check them against your templates.

Which markup formats do the Google article examples use?

The article documentation gives examples in JSON-LD and Microdata. Pick the format your team can maintain and keep it identical across templates. Our take: JSON-LD is the easiest to generate from the same data as the visible byline and date. Whichever format you choose, validate it before release and again after template changes, so the article markup stays correct as your site grows.