What Is Article Schema?
Article schema is structured data from schema.org that describes a news story, blog post, or informational article to search engines, including its headline, author, publish date, and images. Added as JSON-LD, it helps Google understand editorial content and can enhance eligibility for features like Top Stories and rich presentation in search. Subtypes include NewsArticle and BlogPosting. It clarifies who wrote a piece, when, and what it covers, supporting trust and discovery.
- Vocabulary
- schema.org/Article, with NewsArticle and BlogPosting subtypes (schema.org)
- Key properties
- headline, image, author, datePublished, dateModified (Google Search Central)
- Headline limit
- Google recommends headlines under about 110 characters (Google Search Central)
- Author guidance
- author should be a Person or Organization with a name (Google Search Central)
What is Article schema and who needs it? #
Article schema describes editorial content, a blog post, a news story, a guide, so search engines understand it is an article and grasp its key metadata: the headline, the author, when it was published and last updated, and the images that represent it. It uses schema.org's Article type or its more specific subtypes, NewsArticle for journalism and BlogPosting for blog content. For a local business, Article schema belongs on your blog, resource, or news content, the how-to guides, seasonal tips, and company updates that support your SEO and demonstrate expertise. It is part of the schema.org vocabulary in /wiki/schema-markup-guide. While Article markup no longer guarantees a distinct visual rich result for most sites, it clarifies authorship, freshness, and topic for Google, which supports how your content is understood, grouped, and potentially surfaced in features like Top Stories for eligible publishers. It also feeds the trust signals, author and date, that both Google and AI systems weigh when deciding whether to cite editorial content.
Why does authorship and date matter for articles? #
Two properties do heavy lifting in Article schema: author and the date fields. author names who wrote the piece, ideally as a Person with a name, which contributes to Google's understanding of expertise and accountability, part of the E-E-A-T framework Google uses to assess content quality. For a dentist's blog, an article authored by a named dentist carries more implied authority than an anonymous post. datePublished and dateModified establish freshness, telling Google when the content appeared and when it was last updated. Freshness matters for time-sensitive topics; an article on 2026 tax deadlines or current pricing should show a recent dateModified so Google and readers know it is current. These signals also help AI systems decide whether to trust and cite a piece. On our own wiki, entries like /wiki/what-is-local-seo carry clear authorship and update dates for exactly this reason. When you publish business content, naming a real author and keeping dates honest is a small effort that meaningfully strengthens how machines evaluate your work.
What does Article JSON-LD look like? #
An Article block declares the type, headline, image, author, publisher, and dates. The example below shows a BlogPosting for a plumber's blog. Note headline should match the visible title and stay under about 110 characters, image should be a high-resolution URL (Google prefers 16x9, 4x3, and 1x1 versions), author is a Person with a name, and publisher is an Organization with a logo, connecting back to your Organization identity. datePublished and dateModified use ISO 8601 dates. Place the block on the article page itself, one per article. After deploying, validate with /tools/schema-validator and monitor Google Search Console. Keep dateModified accurate whenever you meaningfully update the content, but do not fake it, changing the date without changing the content is a manipulation Google can detect and dislikes. The markup should reflect the real editorial facts of the page: who wrote it, when, and what it looks like.
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "5 Signs Your Water Heater Is About to Fail",
"image": "https://rivertownplumbing.com/blog/water-heater.jpg",
"author": {
"@type": "Person",
"name": "Fay Whitmore"
},
"publisher": {
"@type": "Organization",
"name": "Rivertown Plumbing Co.",
"logo": {
"@type": "ImageObject",
"url": "https://rivertownplumbing.com/logo.png"
}
},
"datePublished": "2026-06-02",
"dateModified": "2026-07-01"
}What is the difference between Article, NewsArticle, and BlogPosting? #
schema.org offers a general Article type and two common subtypes, and choosing the right one adds precision. NewsArticle is for journalism, timely news reporting produced by a publisher, and it is the type associated with eligibility for the Top Stories carousel, which is generally reserved for recognized news publishers. BlogPosting is for blog content, the tips, guides, and updates most businesses publish, and it is the natural fit for a local business blog. The generic Article works when neither subtype clearly applies. For the plumbers, dentists, and law firms we serve, BlogPosting is almost always correct, because their content is helpful editorial material rather than breaking news. Using NewsArticle on a small-business blog will not magically qualify you for Top Stories, since that feature depends on being an established news source, so match the type honestly to what you actually publish. The distinction is small in code but meaningful in accuracy, and accuracy is what keeps your structured data trustworthy to both Google and AI systems.
How does Article schema connect to your brand identity? #
Article markup does not stand alone; it links to your Organization identity through the publisher property. The publisher is your Organization, complete with name and logo, tying every article back to the brand entity described in /wiki/what-is-organization-schema. This connection matters because it lets Google associate your editorial output with your brand, building a body of authored content under one identity, which supports authority over time. The author property, meanwhile, can connect to a Person entity, and for businesses building recognized expertise, developing consistent author identities across articles strengthens the expertise signal. Together, publisher and author answer the questions Google and readers ask of any article: what brand stands behind this, and who specifically wrote it. Keeping these consistent across your blog, the same publisher block, the same author entities, compounds the benefit. This is part of the coherent structured-data strategy we design in /services/web-design and maintain through /services/care-plans, where your Organization, Article, and other schema types reinforce one identity rather than scattering disconnected data.
Does Article schema still produce rich results? #
Expectations should be realistic. For most local businesses, Article schema does not produce a dramatic standalone rich result the way a product snippet shows stars. The Top Stories carousel, the most visible article feature, is largely reserved for established news publishers and requires more than markup. What Article schema does for ordinary business blogs is subtler but still worthwhile: it clarifies authorship, dates, and topic, which supports how Google understands and presents your content, can contribute to article thumbnails in some contexts, and feeds the trust signals that AI Overviews weigh when deciding whether to cite a source. As with FAQ schema covered in /wiki/what-is-faqpage-schema, the value has partly shifted from visible badges to machine comprehension and AI visibility, a theme in /wiki/ai-search-optimization. So add Article schema because it helps machines correctly attribute, date, and understand your editorial content, not because you expect a flashy result. For content that supports your SEO and expertise, that clarity is genuinely useful even without a badge.
Where does Article schema fit in a content strategy? #
Article schema is the markup layer of a broader content effort. A local business builds authority and captures search traffic by publishing genuinely helpful content: seasonal maintenance guides, cost explainers, how-to-choose comparisons, and answers to the questions customers actually ask. This content supports rankings for informational queries and feeds AI systems that increasingly answer those queries directly. Article schema then labels each piece so machines correctly identify the headline, author, date, and publisher. The schema is only as valuable as the content it describes, so the priority order is content first, markup second. For our clients, this content lives in a blog or resources section planned during /services/web-design and refined through /services/conversion-optimization, and the Article markup is wired into the post template so every new article is automatically described correctly. This automation matters because a business publishing regularly cannot hand-code schema for each post. Get the template right once, keep writing useful content, and the structured data takes care of itself, correctly attributing and dating everything you publish.
How do you implement and maintain Article schema? #
On WordPress, quality SEO plugins output Article or BlogPosting schema automatically from the post's title, author, featured image, and dates, and a developer can refine the author and publisher entities through /services/wordpress-development. On a custom or headless site, the post template generates the JSON-LD from the same content fields that render the visible article, so headline, author, and dates always match, which our /services/web-app-development team builds in. The single-source principle applies again: derive the schema from the real post data rather than maintaining it separately. Generate and check examples with /tools/schema-generator and /tools/schema-validator, and monitor Google Search Console for errors. Maintenance is mostly about honest dates: update dateModified when you genuinely revise a piece, and refresh time-sensitive content so it stays accurate, but never fake freshness. Retire or update outdated articles rather than leaving stale advice marked as current. This ongoing editorial and structured-data upkeep is part of /services/care-plans, keeping your content library accurate, trustworthy, and correctly described as it grows over the years.
FAQ
Should I use Article, NewsArticle, or BlogPosting?
For a typical local business blog, BlogPosting is the right choice, since your content is helpful editorial material rather than breaking news. NewsArticle is for journalism from recognized publishers and is tied to Top Stories eligibility, which markup alone will not grant. Use the generic Article only when neither subtype fits. Match the type honestly to what you actually publish.
Does Article schema get me into Top Stories?
Not by itself. The Top Stories carousel is largely reserved for established, recognized news publishers and depends on far more than markup. Adding NewsArticle schema to a small-business blog will not qualify you. For ordinary business content, Article schema instead clarifies authorship, dates, and topic to support comprehension and AI visibility.
Why does the author property matter?
Naming a real author, ideally as a Person, contributes to Google's assessment of expertise and accountability, part of the E-E-A-T framework for content quality. An article authored by a named professional carries more implied authority than an anonymous post, and it helps AI systems decide whether to trust and cite the piece. Consistent author identities strengthen this over time.
Should I update the dateModified when I edit an article?
Yes, when you genuinely revise the content in a meaningful way. An accurate dateModified signals freshness to Google and readers, which matters for time-sensitive topics. However, never change the date without changing the content to fake freshness; Google can detect this manipulation and it undermines trust rather than helping.
What is the publisher property for?
It ties the article to your brand entity, an Organization with a name and logo, connecting your editorial output to your overall identity. This lets Google associate a body of authored content with your brand, supporting authority over time. Keep the publisher block consistent across all your articles so they reinforce one coherent identity.
Do I need Article schema on every blog post?
It is worth having on all editorial content, and the practical way to achieve that is wiring the markup into your post template so every new article is described automatically. Hand-coding schema per post does not scale for a business that publishes regularly. Set the template up once, keep the fields honest, and the structured data handles itself.
Was this helpful?