Article Schema Generator

All three are schema.org subtypes that share the same core properties (headline, author, dates, publisher) but signal a more specific content category to search engines. Article is the general-purpose parent type, suitable for anything that doesn't fit the other two more specific categories. BlogPosting explicitly marks the content as a blog post, which is the most common choice for typical website blog content. NewsArticle specifically marks genuinely newsworthy, timely journalism, and is required (not just recommended) for eligibility in certain Google News surfaces and the Top Stories carousel — using it for non-news content like an evergreen blog post or tutorial is a common misuse worth avoiding.

datePublished tells search engines exactly when content first went live, which factors into freshness signals and can appear directly in search result snippets. dateModified signals that content has been meaningfully updated since — search engines can use this to recognize that older content has been kept current and accurate rather than left stale, which matters for topics where recency and correctness genuinely change over time (a 2019 article about 'current' best practices reads very differently with an honest 2024 dateModified than without one).

A publisher logo isn't strictly required for the schema to be valid, but Google's own structured data guidelines specifically recommend one for Article-type schema, since it can be used in rich result displays. When you do include one, Google's guidance recommends a rectangular, non-square image at least 112x112px — a simple square logo can still work but is more likely to be cropped or displayed awkwardly in surfaces that expect a rectangular format.

mainEntityOfPage tells search engines that the specific page at this URL is 'about' the article described in this exact schema block — effectively confirming this page is the canonical, definitive home for this piece of content, rather than a syndicated copy, an excerpt, or a listing page that merely links to it elsewhere. This becomes especially important if the same article content is ever republished or syndicated to another site, since it helps search engines correctly attribute the original.

Schema.org models an author as a distinct entity (typically the Person type, as this tool uses) rather than a bare text string, because a structured entity can in principle carry additional detail beyond just a name — a URL to an author bio page, credentials, or social profiles — and because explicitly typing the author as a Person (versus an Organization, for cases with no individual byline) gives search engines an unambiguous signal about who specifically wrote the content, which matters for topics where author expertise and credibility (E-E-A-T, in Google's own terminology) is a meaningful quality signal.

This tool's form supports a single author name to keep the interface simple for the most common case, but schema.org's author property does technically accept an array of multiple Person entries for genuinely co-authored content. If you need multiple authors, you can generate the schema here for the primary author and then manually edit the copied JSON-LD to add additional author objects to the array before publishing it.

No — structured data is necessary but not sufficient for any rich result treatment; it tells search engines what your content is and gives them the option to display it in an enhanced format, but the actual decision to show a rich result depends on many additional factors (overall site quality, content relevance to the specific search query, and search engine-specific eligibility requirements) that are entirely outside any schema generator's control. Think of correct, valid Article schema as removing a barrier to eligibility rather than as a guarantee of a specific search appearance.

Article-type schema is generally worth adding to every genuine article, blog post, or news piece on a site, since it's specifically designed to describe exactly that kind of content and carries essentially no downside when accurate. It would be inappropriate, however, to add it to pages that aren't actually individual articles — a category listing page, a homepage, or a product page should use a different, more accurate schema type instead (or none at all) rather than Article schema applied where it doesn't genuinely fit.