Generate Article, NewsArticle, or BlogPosting schema with author, publisher, date, and image data. AMP-compatible output.
You fill in fields like headline, author, publisher name and logo, publish/modified dates, and a lead image, and the tool assembles them into a schema.org JSON-LD block with the @type you pick (Article, NewsArticle, or BlogPosting). The field most often left wrong: publisher is required to be an Organization object with a logo ImageObject, not a plain string, and author needs an explicit @type of Person or Organization - typing a bare name into either field produces markup Google's rich result test will flag.
A concrete input and expected output from the current implementation.
Input
Type: BlogPosting | Headline: How to Brew Pour-Over Coffee | Author: Jane Doe (Person) | Publisher: Daily Grind Blog, logo https://dailygrind.example/logo.png | Date published: 2026-08-10 | Image: https://dailygrind.example/images/pour-over.jpg
Expected output
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "How to Brew Pour-Over Coffee",
"image": ["https://dailygrind.example/images/pour-over.jpg"],
"datePublished": "2026-08-10",
"author": {
"@type": "Person",
"name": "Jane Doe"
},
"publisher": {
"@type": "Organization",
"name": "Daily Grind Blog",
"logo": {
"@type": "ImageObject",
"url": "https://dailygrind.example/logo.png"
}
}
} Each form field maps to its schema.org property, with author and publisher expanded into typed sub-objects rather than left as plain strings, which is what the JSON-LD spec requires for those properties.
The form only asks for plain values (a name, a URL, a date), but the tool expands them into the nested object shapes schema.org expects: author becomes a Person or Organization node, publisher becomes an Organization with a logo ImageObject, and the image field becomes an ImageObject or array depending on how many images you supply.
Google's older AMP article guidance recommended supplying the lead image in multiple aspect ratios (1x1, 4x3, 16x9) at 1200px+ width so the image qualifies across placements. When you provide more than one image URL, the tool lists them all under the image array in that order rather than picking just one, leaving eligibility checks on width/ratio to you.
No. Valid markup is necessary but not sufficient - Google still evaluates page content, site quality, and its own eligibility criteria before showing an article rich result. Test the output in Google's Rich Results Test, then treat inclusion as Google's decision, not this tool's.
Use NewsArticle for timely reported news content, BlogPosting for blog-style posts and opinion pieces, and Article as the generic fallback when neither fits cleanly. All three share the same required properties, so switching types later is a one-field change in the output.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Shorten URLs with local redirect tracking via localStorage. See click counts and generate a QR code for each link.
Build UTM-tagged URLs for campaign tracking with source, medium, campaign, term, and content parameters.
Enter 2+ headlines and see simulated previews in Google results, email subject lines, and social posts side-by-side.
Count characters for Twitter/X, LinkedIn, Facebook, and Instagram with platform-specific limits and warnings.
Calculate click-through rates from impressions and clicks with industry benchmarks and trend analysis.
Check email subject line length against best practices for desktop and mobile with preview text optimization.