Overview
Introduction
A well-formed Article schema is what tells Google a page is news or blog content worth showing with a headline image, byline, and publish date in search results, rather than as a bare blue link. Writing it by hand means remembering the exact nesting - author and publisher are objects, image should be an array - and it's easy to get subtly wrong.
This generator takes the handful of fields that actually matter (headline, image, author, dates, publisher) and outputs a complete, correctly-nested JSON-LD block ready to paste straight into a page's <head>.
What Is Article Schema Generator?
A form-driven generator for Article, NewsArticle, and BlogPosting JSON-LD, the three schema.org types used to mark up written content so search engines can identify its headline, author, and publish date.
All three share an identical property shape; the generator just swaps the @type value, so switching between them after filling in the form requires no other changes.
How Article Schema Generator Works
Each field maps directly to its JSON-LD property: headline to headline, the image URL to a single-item image array (the array form is what Google's documentation shows, even for one image), author name to a nested Person object, and so on.
The output updates live as you type, wrapped by default in a full <script type="application/ld+json"> tag; a toggle switches to bare JSON for cases where you're embedding it inside your own script wrapper.
When To Use Article Schema Generator
Publishing a new blog post or news article and wanting search engines to show it as a rich result with a headline image and byline.
Retrofitting structured data onto an existing content site that was built without it, one article template at a time.
Often used alongside Structured Data Validator, Organization Schema Generator and FAQ Schema Generator.
Features
Advantages
- Handles the correct nested shape for author, publisher, and image automatically, avoiding the most common hand-written JSON-LD mistakes.
- Switches between Article, NewsArticle, and BlogPosting without re-entering any field, since all three share the same underlying shape.
- Outputs a ready-to-paste <script> tag by default, so there's no manual wrapping step before it goes into a page.
Limitations
- Doesn't validate that the image URL actually resolves or meets Google's minimum resolution/aspect-ratio requirements for Article rich results.
- Covers the commonly-used Article fields only; it doesn't expose every optional schema.org property (like articleSection or wordCount).
- Generates markup for one article at a time; a site with hundreds of articles will want this pattern automated in its own templating rather than pasted by hand per page.
Examples
Best Practices & Notes
Best Practices
- Use the real publish date, not the date you generated the markup, and update dateModified whenever the article's content meaningfully changes.
- Fill in the publisher and its logo even though they're optional here, since Google's own guidelines recommend both for full rich-result eligibility.
- Keep the headline in the schema identical to the visible <h1> on the page; mismatched headlines between markup and visible content violate Google's structured data policies.
- Use an image at least 1200px wide, since Google's Article guidelines specify a minimum resolution for the image to be eligible for a large rich-result image.
Developer Notes
image is emitted as a single-element array rather than a bare string because Google's Article documentation explicitly recommends the array form even for one image, and some crawlers are stricter about accepting only the array shape.
Article Schema Generator Use Cases
- Adding Article schema to a new blog post before publishing
- Retrofitting NewsArticle schema onto an existing news site's article template
- Generating a quick BlogPosting snippet to paste into a static site generator's frontmatter-driven <head>
Common Mistakes
- Writing image as a plain string instead of an array, which is technically tolerated by some parsers but not what Google's documentation recommends.
- Leaving datePublished as the date the schema was added rather than the article's actual original publish date.
Tips
- Run the generated output through the Structured Data Validator tool in this category before shipping, to double-check nothing required is missing.
- If your CMS already injects a publish date into the page, copy that exact value into datePublished rather than retyping it, to avoid a mismatch.