Why You Are Here
Structured data is how you tell a search engine what a page IS rather than making it infer that from the HTML. Article schema states plainly that this page is an article, that a specific person wrote it, when it was published, when it was last updated, and which image represents it.
Writing that JSON by hand is tedious and easy to get subtly wrong. A missing comma breaks the whole block. An author written as a plain string rather than a structured object parses but conveys much less. A date in the wrong format is silently ignored.
The first situation is a blog or publication where no SEO plugin is handling structured data, or where the plugin's output is generic and you want control over what it says.
The second is a custom or headless site with no plugin ecosystem, where the markup has to be written and maintained deliberately.
The third is fixing errors. Search Console is reporting warnings on your article pages and you need a clean, valid block to compare against or replace what is there.
What This Tool Does
The Article Schema Generator builds valid JSON-LD structured data from a simple form.
Choose your article type, enter the headline, author, publication date, modification date, image URL, and publisher details, and the tool assembles correctly structured JSON-LD with the script wrapper included. Copy it and paste it into your page.
Everything runs in your browser. Nothing is uploaded or stored.
What Article Schema Actually Does in Search
Most pages about Article schema promise rich snippets with images and author bylines. That is not accurate, and it is worth being clear about what you should actually expect.
Article structured data does not produce a distinctive rich result in ordinary web search
Adding it to a standard blog post will not visibly change how your listing looks. There is no star rating, no price, no expandable panel.
What it genuinely does
| Benefit | Applies to |
|
Top Stories carousel eligibility |
News publishers meeting Google News criteria |
|
Google Discover eligibility |
Publishers with qualifying content and imagery |
|
Author and entity understanding |
All sites, feeds E-E-A-T signals |
|
Publication and update dates |
Helps Google assess freshness |
|
AI and LLM comprehension |
Increasingly relevant for AI-generated answers |
The honest summary: for a news publisher, Article schema is close to essential because Top Stories and Discover placement depend on it alongside other criteria. For a typical blog or business site, it is worthwhile infrastructure that helps machines understand your content correctly, but it will not transform your search appearance overnight. Anyone promising otherwise is overselling it. That understanding value is rising rather than falling, since AI search systems lean heavily on structured data to identify authorship, dates, and topical focus.
Article, NewsArticle, or BlogPosting
The generator offers three types. They share the same properties and differ in what they signal.
| Type | Use For | Notes |
|
Article |
Generic editorial content |
The safe default when unsure |
|
NewsArticle |
Journalism and news reporting |
Relevant to Top Stories eligibility |
|
BlogPosting |
Blog posts |
A subtype of Article, widely used |
NewsArticle and BlogPosting are both subtypes of Article, so anything valid for Article is valid for them. Use NewsArticle only for genuine news reporting. Applying it to marketing content misrepresents the page, and Google's guidelines are explicit that structured data must accurately describe the content.
Property Reference
Google no longer lists any required properties for Article
This changed and most published guidance has not caught up. Competitor pages still say required fields like headline and publication date. What remains are recommended properties, and the more of them you supply accurately, the better the page is understood.
| Property | Recommended | Notes |
|
headline |
Strongly |
Keep under 110 characters |
|
image |
Strongly |
Multiple aspect ratios preferred, 1200px wide or more |
|
datePublished |
Strongly |
ISO 8601 format with timezone |
|
dateModified |
Yes |
Only if genuinely updated |
|
author |
Strongly |
Use a Person or Organization object, never a plain string |
|
author.url |
Yes |
Link to an author page, supports E-E-A-T |
|
publisher |
Yes |
Organization with name and logo |
|
description |
Optional |
Brief summary |
|
mainEntityOfPage |
Optional |
Canonical URL of the page |
headline must stay under 110 characters. Google truncates or ignores longer headlines. It does not have to match your H1 exactly, but it must describe the same content.
author should be an object, not a string. Writing author: Jane Smith is valid JSON-LD but tells Google almost nothing. A Person object with a url pointing at an author bio page connects the article to an identifiable author, which matters for how Google assesses expertise and authority.
Example Output
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "How to Make Sourdough Starter From Scratch",
"description": "A step-by-step guide to creating and maintaining a starter.",
"image": [
"https://example.com/images/sourdough-1x1.jpg",
"https://example.com/images/sourdough-4x3.jpg",
"https://example.com/images/sourdough-16x9.jpg"
],
"datePublished": "2026-03-14T09:00:00+05:00",
"dateModified": "2026-06-02T11:30:00+05:00",
"author": {
"@type": "Person",
"name": "Jane Smith",
"url": "https://example.com/authors/jane-smith"
},
"publisher": {
"@type": "Organization",
"name": "Example Bakery Blog",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/logo.png"
}
},
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://example.com/blog/sourdough-starter"
}
}
Supplying three image aspect ratios (1x1, 4x3, 16x9) lets Google pick whichever fits the surface it is displaying on. It is optional, but it is what Google's own documentation recommends.
Where to Put the Code
Wrap the JSON in a script tag and place it in the page:
<script type="application/ld+json">
{
... your JSON-LD here ...
}
</script>
| Placement | Works |
|
Inside <head> |
Yes, cleanest and most common |
|
Before </body> |
Yes |
|
Injected via Google Tag Manager |
Yes, though direct HTML is more reliable |
|
Inside the visible page body |
Yes, Google finds it regardless |
Multiple schema blocks are normal and encouraged. A well-marked-up article page often carries Article schema for the content, BreadcrumbList for navigation, and Organization for the publisher. Put each in its own script tag rather than trying to combine them.
Validating Your Markup
| Tool | What it Checks |
|
Google Rich Results Test |
Whether Google can parse it and what features it qualifies for |
|
Schema Markup Validator |
Whether the markup is valid Schema.org, independent of Google |
|
Search Console structured data reports |
Errors across your whole site over time |
Use the Rich Results Test before publishing and Search Console afterwards. The Rich Results Test only reports on Google-supported features, so valid markup that Google does not use for a rich result may show no issues and no eligibility, which is expected rather than a failure.
Common Mistakes to Avoid
WARNING: Marking Up Content That Is Not on the Page
Structured data must describe what a visitor actually sees. Listing an author who is not credited on the page, a publication date that appears nowhere, or an image not present in the article breaches Google's structured data guidelines and can trigger a manual action against the site. The markup describes the page; it does not add to it.
WARNING: Using dateModified as a Freshness Tactic
Updating dateModified without genuinely changing the content is a common tactic and a poor one. Google compares the claimed date against what it sees when it crawls, and repeatedly claiming updates that did not happen erodes trust in your dates generally. Only set dateModified when the article has meaningfully changed, and leave it out entirely if it has not.
WARNING: Writing the Author as a Plain Text String
author: Jane Smith validates without error, so nothing warns you it is weak. But a bare string is just text, while a Person object with a url connects the article to an identifiable author entity with a bio page and a track record. Given how much weight Google places on demonstrable expertise, this is one of the most valuable properties to structure properly rather than the afterthought it usually becomes.
Quick Reference
| Item | Detail |
|
Types |
Article, NewsArticle, BlogPosting |
|
Format |
JSON-LD, Google's preferred format |
|
Required properties |
None, per Google |
|
Recommended |
headline, image, dates, author, publisher |
|
Headline |
Under 110 characters |
|
Images |
1200px wide, three aspect ratios |
|
Dates |
ISO 8601 with timezone |
|
Author |
Object, never a plain string |
|
Placement |
Anywhere, head preferred |
|
Multiple blocks |
Fine, use separate script tags |
|
Rich result |
No, in normal web search |
|
Real value |
Top Stories, Discover, entity understanding |
