usdigitalmarketingindex.com SEO
When should a publisher add Article structured data to a webpage?
Updated November 15, 2026
When the page is an article: a news story, a blog post, or a similar piece of written editorial content with a headline, an author, and a publication date. Article markup states those facts in a form search engines can read without inferring them from the layout. Google’s documentation says the markup helps it understand more about the page, such as “who the author is, or what the title of the article is” (Google’s Article structured data documentation). It is not a switch that turns on a special result. The same documentation lists no required properties, and Google’s general guidelines state that structured data “does not guarantee” a feature will be shown. Add it to describe articles accurately, and leave it off pages that are not articles.
Article page types
Google’s documentation covers three types under this heading: Article, NewsArticle, and BlogPosting.
| Page | Appropriate type |
|---|---|
| News report | NewsArticle |
| Blog post | BlogPosting |
| Feature, guide, analysis, opinion piece | Article |
| Product page | Not an article; Product |
| Category or listing page | Not an article |
| Service or landing page | Not an article |
| Home page | Not an article |
| Author profile page | Not an article; ProfilePage |
Choose by what the page is. Marking a sales page as an article misdescribes it.
Required and recommended fields
For this feature the documentation says: “There are no required properties; instead, add the properties that apply to your content”. The recommended properties it lists are author, with the author’s name and a URL identifying them, dateModified, datePublished, headline, and image.
A small example. The names and addresses are placeholders, and the author is a plain name with no titles or credentials added.
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "How to bleed a radiator",
"image": [
"https://www.example.com/images/radiator-16x9.jpg",
"https://www.example.com/images/radiator-4x3.jpg",
"https://www.example.com/images/radiator-1x1.jpg"
],
"datePublished": "2026-03-04T09:00:00+00:00",
"dateModified": "2026-10-12T14:30:00+00:00",
"author": [{
"@type": "Person",
"name": "Jordan Ellis",
"url": "https://www.example.com/authors/jordan-ellis"
}]
}
The block is placed in the page inside a script element of type application/ld+json.
Notes on the fields:
- headline is the article’s title as shown on the page.
- datePublished and dateModified use ISO 8601 format and reflect the real dates.
- author.name holds the name only. Job titles, honorifics, and affiliations belong in their own properties, not inside the name.
- author.url points to a page that identifies the author. The documentation adds that if this is a profile page on your own site, that page can carry profile page markup.
- Where an article has several authors, list each as a separate entry.
- If the author is an organization, use the Organization type.
Other types are stricter than Article. Recipe markup has properties that must be present, listed in the guide to which fields are required for eligible Recipe structured data.
Accurate visible correspondence
Markup must describe what the page shows. Google’s structured data guidelines say: “Don’t mark up content that is not visible to readers of the page” (Google’s structured data general guidelines).
| Property | Must match |
|---|---|
| headline | The visible title |
| author | The byline on the page |
| datePublished | The visible publication date |
| dateModified | The visible updated date, changed only when the article changes in substance |
| image | An image that appears in the article |
Do not add an author to markup that the page does not credit, and do not attach qualifications the person does not hold. The same guidelines list structured data that “is not representative of the main content of the page, or is potentially misleading” among the reasons markup may not be used, and warn that violations can lead to a manual action.
Testing and maintenance
- Run the page through Google’s Rich Results Test, which reports whether the markup can be read and flags problems.
- Check the Search Console enhancement reports, where they exist for your markup, for errors across the site.
- Compare the markup with the visible page on a sample of articles from each template.
- Recheck after template, theme, or plugin changes, because markup generated by a template changes on every article at once.
Maintenance points:
- Generate values from the same fields that render the page, so the two cannot drift apart.
- Update dateModified through the publishing workflow, not on every save.
- When an author leaves or a byline changes, the markup follows the visible byline.
- Remove article markup from page types that are not articles, if a plugin applied it to everything.
Set expectations plainly. Google’s guidelines state that it “does not guarantee that your structured data will show up in search results, even if your page is marked up correctly according to the Rich Results Test”. Valid Article markup makes the page’s facts explicit. Whether any enhanced display follows is Google’s decision.
Decision summary:
| Situation | Add Article markup? |
|---|---|
| Editorial article with a byline and date | Yes |
| Article published without a named author | Yes, with the publishing organization as author if that is what the page states |
| Page that is not an article | No |
| Thin page with an article template | The markup is not the issue; the page is |
The author’s own page is described with a different type. When that page qualifies, and what its markup requires, is covered in the guide to when an author profile page should use ProfilePage structured data.
The rule: mark up articles as articles, with the facts the page displays, and expect clarity, not a promised feature.
Add your comment to this answer