Article Schema

Article schema is a type of structured data — code, usually in the schema.org vocabulary, added to a web page — that tells search engines the page is an article, such as a news story or a blog post, and describes its key details in a machine-readable way. Instead of leaving a search engine to infer what a page is from its text alone, Article schema states it explicitly and supplies structured fields: the headline, the author, the publication and modified dates, the publisher, and a representative image. The markup, most often written in JSON-LD and placed in the page's code, does not change what a human sees; it adds a labeled description underneath for machines. In the schema.org vocabulary, the Article type has more specific subtypes, including NewsArticle for journalism and BlogPosting for blog entries, which sharpen the signal further.

Article schema matters because it helps search engines understand and present editorial content with confidence. When a page clearly declares itself an article and hands over its headline, author, date, and image in structured form, a search engine can treat it as news or blog content and is more likely to feature it in enhanced ways — the rich results, carousels, and detailed listings that plain pages do not earn. It also feeds the growing set of systems that read structured data to summarize and cite content, from search features to AI answers. The markup is not a ranking trick and does not guarantee any placement, but it removes ambiguity about what the page is, which is the groundwork for eligibility for richer, more visible search presentations.

Article schema is one type within the broad schema.org vocabulary, and choosing the right type matters. Schema.org defines many types for different content: Product for a product page, Recipe for a recipe, FAQPage for a list of questions and answers, Event for an event, Organization for a company, and so on. Article — with its NewsArticle and BlogPosting subtypes — is specifically for editorial, written content: the news stories and blog posts that make up much of the web's reading. Marking a blog post with Article schema tells search engines it is an article; marking a product with Product schema tells them it is something for sale. Using the type that actually matches the page is the whole point, because the type determines which structured fields apply and which rich results the page can qualify for.

The distinction from other types is not just labeling; it decides eligibility. A recipe page marked with Recipe schema can qualify for recipe rich results with cook times and ratings; an article marked with Article schema can qualify for article and top-stories treatments instead. Applying the wrong type, or forcing Article schema onto a page that is really a product or a category, sends a misleading signal and forfeits the right rich result. Article schema also pairs naturally with other markup on the same page — an Organization or Person for the author and publisher, breadcrumb markup for the site path — which together give search engines a fuller, more connected picture. The craft is matching each page to its true type and supplying accurate, complete fields rather than stretching one type to cover everything.

Using Article schema well means adding accurate, complete markup that mirrors the visible page. Include the required and recommended fields — a clear headline that matches the on-page title, the author (linked to a Person or Organization), the publish and modified dates, the publisher, and a high-quality image — and choose the most specific type that fits, NewsArticle for journalism or BlogPosting for a blog post rather than the generic Article where a subtype applies. Write the markup in JSON-LD, keep it in sync with the content whenever the article changes, and validate it with a structured-data testing tool before and after publishing. The gain is eligibility for richer search presentations and clearer machine understanding, which supports both traditional rich results and newer systems that read structured data to summarize and cite.

The failures are marking up content that contradicts the page (a headline in the schema that differs from the visible one, or dates that do not match), using Article schema on pages that are not articles, leaving out recommended fields so the page misses rich-result eligibility, and letting the markup drift out of date as the article is edited. Search engines penalize or ignore structured data that misrepresents the page, so accuracy is not optional. The discipline is to use Article schema honestly and completely — the right subtype, fields that match the visible content, valid JSON-LD kept current — so search engines can trust the page is what it claims to be and reward it with the richer, more visible treatment that accurate structured data makes possible.

Schema, from the Greek skhema (form or shape), names the structured vocabulary that gives a page's content a machine-readable form, here for articles.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where article schema is a core concern: