Loading…
Generate Article JSON-LD for blog posts and editorial pages: headline, author, publisher, image, and the publish and modified dates. The output validates live, so a malformed date shows up before you ship it.
{
"@context": "https://schema.org",
"@type": "Article"
}headline Article is missing required property "headline".image Article is missing recommended property "image". Adding it improves rich result eligibility.author Article is missing recommended property "author". Adding it improves rich result eligibility.publisher Article is missing recommended property "publisher". Adding it improves rich result eligibility.datePublished Article is missing recommended property "datePublished". Adding it improves rich result eligibility.dateModified Article is missing recommended property "dateModified". Adding it improves rich result eligibility.description Article is missing recommended property "description". Adding it improves rich result eligibility.Copy the snippet first, then paste it into either tool's code tab.
Paste this inside your page's <head> (or anywhere in the HTML). Then check it with the JSON-LD validator.
Article schema tells search engines the page is editorial content with a byline and a timeline, rather than a product page or a category listing. Google uses it to pick better headlines and images for article results, to understand authorship across your site, and to date content accurately in results where freshness matters. The only required property is headline. Image, author, publisher, dates, and description are recommended, and each one you skip narrows how the article can be displayed.
For a typical blog, the highest-value combination is headline, a wide image (Google prefers at least 1200px), an author with a name, and truthful dates. Publisher matters more for multi-author publications where the brand, rather than the writer, is the trust anchor.
Nearly every broken Article snippet we have debugged came down to dates. The classics: a US-format date string like 03/15/2026 that parses as ambiguous, a dateModified earlier than datePublished after a CMS migration, and a build pipeline that stamps dateModified with the deploy time so every page claims it changed today. That last one is the most damaging because it quietly burns Google's trust in all your freshness signals. Set dateModified from your content store, never from the build clock.
The generator emits dates exactly as you type them and the validator warns when they are not ISO 8601. After deploying, give the page a once-over in Google's Rich Results Test, or paste the JSON into our JSON-LD validator alongside the rest of the page's markup. If the article also carries FAQ or breadcrumb blocks, the visualizer shows how the entities relate.
They share the same rules, so the practical difference is small. BlogPosting fits blog content, NewsArticle is for actual news reporting (and matters if you appear in Google News), and Article is the safe generic parent. This generator emits Article, which every parser accepts; you can change the @type string to BlogPosting in the output without breaking anything.
Google's old 110-character guidance was dropped, but the headline should still match the visible title of the page. A headline in markup that differs from the on-page H1 is a mismatch signal, and truncation in display is handled by Google regardless of what you put in the markup.
ISO 8601. A plain date like 2026-03-15 works; a full timestamp with timezone like 2026-03-15T09:30:00+05:30 is better because it removes ambiguity about which day it was in which timezone. The inline validator flags anything that does not look ISO-shaped.
Only for substantive updates: corrected facts, new sections, refreshed figures. Bumping dateModified on every typo fix or template deploy teaches Google your freshness signals are noise, and it stops trusting them. Keep it honest and it stays useful.
Not directly in any confirmed way, but author information feeds how Google understands expertise on a topic, and it appears in some result treatments. Use a real person with a real name where possible, and an Organization author for genuinely institutional content.
TWR adds AggregateRating schema to your public review page automatically — free. Collect verified reviews inside your app and let us handle the structured data.