Article schema generator. JSON-LD ready to ship.
Fill 11 fields, get copy-ready Article JSON-LD aligned with Google's required-field list. Switch between Article, BlogPosting, and NewsArticle types. Inline validator runs on every keystroke.
Dedicated Article schema generator. Type into the 11-field form on the left; the right panel renders copy-ready JSON-LD for the chosen Article subtype (Article, BlogPosting, NewsArticle). Inline validator runs on every keystroke. No fetch, no log.
Required. ≤110 chars (Google truncates beyond).
Sources used by this generator
- schema.org/Article · /BlogPosting · /NewsArticle — type definitions
- Google Search Central — Article rich result required-field list
- ISO-8601 date format · W3C JSON-LD 1.1 syntax
Generation runs entirely in JavaScript on your device. No JSON is sent to any external service.
Privacy: form runs in-browser only. Your inputs never leave the device.
What goes in an Article schema.
Required (per Google Article rich-result spec): headline, image, datePublished, author, and publisher with logo. Missing any one and the rich result is ineligible. The validator surfaces a fail per missing field.
Recommended: dateModified (so Google knows freshness), mainEntityOfPage (canonical URL — disambiguates if the schema appears on multiple pages), description (first ~200 words or summary, used by AI consumers), articleSection (topic category), wordCount, keywords. None of these are required for the rich result, but each strengthens the entity for AI / archive / knowledge-graph consumers.
Type choice — Article vs BlogPosting vs NewsArticle: all three are valid; pick the most specific. BlogPosting for editorial blog posts, NewsArticle for journalism with dateline/reporter conventions, Article for everything else. Google honors all three for the rich result; the more specific type signals the genre cleanly to other consumers.
Author as Person vs Organization: Person whenever a human wrote the piece. Organization is appropriate for editorial team / wire service authorship. Avoid 'Editorial Team' or 'Staff' as Person.name — Google's September 2025 rater guidelines explicitly call out anonymous attribution as low-EEAT. Add author.url pointing to a team profile page with a 30+ word bio for the strongest E-E-A-T signal.
Image URL specs: minimum 1200 pixels wide; 16x9 / 4x3 / 1x1 aspect ratios all accepted. Provide multiple sizes via comma-separated URLs in the image field — Google picks the best fit per surface (square thumbnail, standard hero, AMP carousel). Logo image (publisher.logo.url) should be a transparent-background PNG, max 600x60 pixels.
Six questions users ask.
What's the difference between Article, BlogPosting, and NewsArticle?
All three are valid schema.org types. Article is the generic parent; BlogPosting is the subtype for editorial blog posts; NewsArticle is the subtype for journalism with the additional dateline + reporter conventions. Pick the most specific type that fits — Google honors all three for the Article rich result, and the more specific type signals the genre cleanly to other consumers (AI systems, archive crawlers). For a marketing-blog post, use BlogPosting; for a newsroom story, use NewsArticle; for everything else, use Article.
Are headline and image truly required?
Yes — Google's Article rich-result documentation lists headline, image, datePublished, author, and publisher (with logo) as the required field set. Missing any one of those and the rich result is ineligible. Our generator includes them as non-optional inputs and the inline validator surfaces a fail per missing field. The optional fields (dateModified, articleBody, keywords, articleSection, wordCount, mainEntityOfPage) are recommendations that strengthen the entity without being required.
What image specs does Google require?
Minimum 1200 pixels wide, 16x9 / 4x3 / 1x1 aspect ratios all accepted. Use a high-quality image that represents the article. Multiple image URLs are allowed in the image array; provide all the variants you have (1x1 for square thumbnail, 4x3 for standard, 16x9 for hero) so Google can pick the best fit per surface. Logo image (publisher.logo.url) should be a transparent-background PNG, max 600x60 pixels for AMP-style rendering.
Should author be Person or Organization?
Person whenever a human wrote the article. Person includes additional fields (jobTitle, sameAs for social profiles, knowsAbout for E-E-A-T signal) that strengthen author authority. Organization is appropriate when an editorial team or wire service is the canonical author. Avoid 'Editorial Team' or 'Staff' as Person.name — Google's September 2025 quality rater guidelines explicitly call out anonymous attribution as low-EEAT.
Why is the validator showing my mainEntityOfPage as a warning?
mainEntityOfPage is recommended (not required) but Google uses it to disambiguate when the same Article schema appears on multiple pages (e.g., a homepage feed plus the canonical article page). It should equal the canonical URL of the article. The validator warns when it's missing because the article will rank but won't claim canonical-entity ownership cleanly across syndicated copies.
Does this tool log my JSON?
No. The form runs entirely in JavaScript on your device. Nothing is sent to Digital Heroes servers. The 'recent generations' panel uses your browser's localStorage and stays on your device. No signup, no email, no analytics beacon includes the JSON content.
Schema cluster.
Product Schema Generator
Product JSON-LD with offers + reviews.
FAQ Schema Generator
Q+A pairs → FAQPage JSON-LD.
LocalBusiness Schema Generator
Address + geo + hours per day.
Structured Data Validator
Validate any JSON-LD against 8 types.
Schema Markup Generator
Multi-type — 6 schemas in one tool.
SEO service
Schema strategy + technical + content.