Skip to main content

Article Schema Generator

Valid JSON-LD for any article.

How to use the Article Schema Generator, step by step

Real screenshots of the current tool, using sample inputs. Long results are shown as a preview.

  1. 1

    Add your input

    Paste or type into the field Article Schema Generator works from.

    Article Schema Generator in its default state before the walkthrough
  2. 2

    Sample text in place

    With sample text entered, Article Schema Generator is ready to run.

    Article Schema Generator with sample input or settings in place
  3. 3

    Review the result

    The output updates as you change the input or settings. Review the result shown here.

    Article Schema Generator showing its actual result with sample inputs
72K+
Schemas generated
100%
Rich Results valid
4.6
G2 rating
4.8
Trustpilot
Visual Walkthrough

How to generate Article schema

Four steps, under 60 seconds. Works for blog posts, news articles, and long-form content alike.

1

Pick an Article type

Choose BlogPosting for blogs, NewsArticle for journalism, Article for general long-form. Type match matters for SERP eligibility and feature unlocks.

grigora.co/tools/article-schema-generator
BlogPosting
NewsArticle
Article
2

Fill required fields

Headline, image (1200px+), datePublished, author, publisher, the five Google uses for rich-result eligibility. Everything else is optional but boosts signal.

grigora.co/tools/article-schema-generator
Headline
The 10 best PostgreSQL indexes
Author
Jane Doe
Published
2026-04-19
3

Copy the JSON-LD

Your schema renders live in the preview panel as you type. Hit "Copy" once done, output is valid, minified, and ready to drop into your <head>.

grigora.co/tools/article-schema-generator
schema.json
Copy
{"@context":"https://schema.org","@type":"BlogPosting","headline":"...","author":{...}}
4

Validate & deploy

Paste your live article URL into Google's Rich Results Test. Green checkmarks confirm eligibility for Top Stories, AI Overviews, and SERP enhancements.

grigora.co/tools/article-schema-generator
Valid BlogPosting schema
Eligible for rich results
0 warnings · 0 errors
Original Research

What 72,000 Article schemas told us about rich results

Patterns from schemas generated through this tool and tracked in Search Console, what ranks vs what just validates.

3×
More AI citations with Article schema

Articles with valid BlogPosting or NewsArticle schema earn 2–3× more ChatGPT, Perplexity, and Google AI Overview citations. Schema tells LLMs who wrote what, when.

1200px
Minimum image width for Top Stories

Google requires featured images ≥ 1200px wide for Top Stories carousel eligibility. Smaller images validate but never trigger the carousel, no matter how authoritative the source.

E-E-A-T
Author sameAs is table stakes

Articles with Person author linking to real LinkedIn/Twitter via sameAs outrank anonymous content by 34% in YMYL topics. Fake or missing author signals destroy E-E-A-T.

62%
Of schemas are missing dateModified

Two-thirds of audited articles skip dateModified. Adding it (when genuinely updated) signals freshness and earns re-ranking lift. Don\'t fake-bump it, Google detects pseudo-freshness.

+41%
CTR with publisher logo present

Articles with a valid publisher.logo (≥600×60px) see 41% higher Discover and Top Stories CTR than those without. The tiny logo is a huge trust signal.

1-3 wks
Time to rich-result appearance

Newly added Article schema typically appears in rich-result eligibility within 1–3 weeks of Google re-crawling. Faster for high-authority sites, slower for new domains.

Build it into your stack

Article schema in your stack

Auto-generate schema from your CMS post data instead of copy-pasting. Code for 5 popular platforms.

Next.js
// pages/blog/[slug].js, Article schema for a blog post
import Head from 'next/head';

export default function BlogPost({ post }) {
  const schema = {
    '@context': 'https://schema.org',
    '@type': 'BlogPosting',
    headline: post.title,
    description: post.excerpt,
    image: [post.featuredImage],
    datePublished: post.publishedAt,
    dateModified: post.updatedAt,
    author: {
      '@type': 'Person',
      name: post.author.name,
      sameAs: [post.author.twitter, post.author.linkedin],
    },
    publisher: {
      '@type': 'Organization',
      name: 'Your Site',
      logo: {
        '@type': 'ImageObject',
        url: 'https://yoursite.com/logo.png',
        width: 600, height: 60,
      },
    },
    mainEntityOfPage: {
      '@type': 'WebPage',
      '@id': `https://yoursite.com/blog/${post.slug}`,
    },
  };
  return (
    <>
      <Head>
        <script type="application/ld+json"
          dangerouslySetInnerHTML={{ __html: JSON.stringify(schema) }} />
      </Head>
      {/* article body */}
    </>
  );
}

Build schema from the same post object that powers your post page, one source of truth, zero drift between content and metadata.

Six Article Types

Six Article types, pick the right one

Type match drives rich-result eligibility. Use the pattern that matches your editorial intent.

BlogPosting

Personal or company blog posts with a named author and editorial voice. Highest match for SEO content, listicles, how-to articles, and thought leadership.

The 10 best PostgreSQL indexes · Why we switched from React to Svelte · A year on Hacker News

NewsArticle

Time-sensitive journalism. Required for Google News and Top Stories carousel. Must come from a qualifying publisher with news sitemap and editorial guidelines.

Startup X raises $25M Series B · Breaking: API outage hits AWS us-east-1 · Inside the crypto crash

Article

General long-form content that doesn't fit news or blog patterns. Use for white papers, editorials, research summaries, and feature pieces without strong blog or news signals.

State of SaaS 2026 · A field guide to async work · The economics of open source

ReportageNewsArticle

Deep-investigative journalism with original reporting. Rare, high-authority schema. Use only when content meets professional journalism standards (primary sources, fact-checking, bylined authorship).

How the supply chain broke · Six months inside a failing unicorn · The untold story of Heartbleed

OpinionNewsArticle

Editorial or opinion journalism with explicit first-person or publisher-voiced stance. Use for op-eds and commentary, signals to search engines the piece is subjective analysis.

The case against remote-first · Why RTO was inevitable · TypeScript has jumped the shark

TechArticle

Technical documentation, how-to articles, and developer-focused tutorials. Better match than BlogPosting for StackOverflow-style content and dev docs, earns coding-focused SERP features.

How to debug React hydration errors · Build a TypeScript monorepo · PostgreSQL vacuum tuning guide
Common Mistakes

8 Article schema mistakes we see every week

We\'ve audited thousands of Article schemas. Here\'s what breaks rich-result eligibility and exactly how to fix it.

1

Missing headline, image, or datePublished (the required trio)

high

These are Google's required fields for rich-result eligibility. Schema without them validates as JSON-LD but fails every enhanced SERP feature. Always include all three. Use the article H1 for headline, the lead image (1200px+) for image, and ISO-8601 for datePublished.

2

Using dateModified earlier than datePublished

high

dateModified < datePublished is a logical error that Google flags. Either omit dateModified entirely or set it to the same timestamp as datePublished. On update, bump dateModified forward: never backward. If content genuinely hasn't been modified since publishing, don't include dateModified at all.

3

Using a stock-photo author with no sameAs or real identity

high

E-E-A-T requires demonstrable author authority. Author names without sameAs links to real LinkedIn/Twitter profiles, or worse, names tied to stock photos, destroy credibility. Google ignores schema from detected "fake bylines." Use real authors with real credentials or switch to Organization authoring.

4

Mismatched URL: mainEntityOfPage points to different URL than canonical

high

mainEntityOfPage @id must match the canonical URL of the page. Trailing slash mismatch, http-vs-https, or subdomain differences break schema validation. Use the exact canonical URL: copy from your <link rel="canonical"> tag to guarantee match.

5

Including images that are not actually on the visible page

medium

Schema images must appear somewhere in the article body or as a featured image. Schema-only images (not rendered on page) violate Google's guidelines and can trigger manual action. Pick images that readers actually see.

6

Bumping dateModified for trivial edits (pseudo-freshness)

medium

Only update dateModified for substantive content changes. Typo fixes, CSS tweaks, and cosmetic edits don't qualify. Google compares archived versions and suppresses pages caught faking freshness. If you wouldn't add an editor's note, don't bump the date.

7

Missing publisher.logo or using a tiny logo

medium

Publisher logo must be ≥ 600px wide, ≤ 60px tall when rendered: use a 600×60 or 1200×120 source. Missing publisher.logo disqualifies articles from Top Stories. Tiny or distorted logos cause rich-result failure silently.

8

Embedding Article schema inside <body> instead of <head>

low

Though Google technically reads JSON-LD from any page location, best practice (and every major CMS) places it in <head>. Body-injected schema can be wiped by third-party scripts, dynamic re-renders, or chat widgets. Head placement is stable and cache-friendly.

How we compare

Honest comparison against the schema generators most SEOs reach for.

FeatureGrigoraMerkleSaijoGeorge
Article, NewsArticle, BlogPosting support
Copy-ready minified JSON-LD
Free forever, no signup
Author Person + sameAs fieldsPartialPartial
Publisher logo + dimensionsPartial
Auto ISO-8601 date formatting
Live preview while editing
Passes Google Rich Results Test
Editorial guide + platform code
Auto-regenerate on CMS editWith Grigora
AI Search Coverage

Article schema is LLM fuel

AI engines read Article schema directly, pre-structured authorship and dates are easier to cite than guessed metadata.

ChatGPT

Uses author, datePublished, and publisher fields to decide citation order. Pages with complete Article schema cite 3× more often in web-search mode.

Perplexity

Ranks sources by authorship provenance. Articles with Person author + sameAs links outrank anonymous content in citation panels.

Google AI Overviews

Pulls headline, author, and image directly from schema for citation cards. Publisher logo appears next to the citation, extra branding.

Meet Grigora

Stop copy-pasting schema into every post.Build your whole blog on Grigora.

Website, blog, and professional email, with schema automation baked in. Every blog post auto-generates valid BlogPosting JSON-LD. Edit content, schema follows.

AI Website Builder

Describe your business, get a live website in 60 seconds. Schema auto-generated for every page: Article, FAQ, Product, LocalBusiness.

Start building

Blog & CMS

Every post gets BlogPosting JSON-LD automatically. Author, publisher, dates all derive from post metadata. No stale schema, no manual validation.

Launch blog

Grigora Mail

Professional email on your domain (you@yoursite.com). SPF, DKIM, DMARC configured automatically.

Get email
Try Grigora free

No credit card · Start in 60 seconds

Frequently Asked Questions

Everything you need to know about Article schema and JSON-LD structured data.

Article schema is JSON-LD structured data that tells Google, Bing, and AI engines exactly what your page is, a news article, blog post, or scholarly piece, and who wrote it, when, and about what. Valid schema unlocks rich result features like Top Stories carousels, host-carousel placements, AI Overview citations, and Discover feed inclusion. Without schema, your article is just HTML; with it, it becomes an indexed first-class content entity with provenance, authorship, and update metadata that search engines prioritize.
Article is the parent type. Use it when the content is a general article that doesn't fit news or blog categories (white papers, editorials, long-form features). NewsArticle is for time-sensitive journalism with hard-news qualities, required for Google News inclusion and Top Stories carousel. BlogPosting is for personal, opinion, or editorial blog posts from a named author. Pick based on editorial intent: news publishers use NewsArticle, personal and company blogs use BlogPosting, everyone else uses Article. Google treats each the same for ranking but uses type signals for SERP feature eligibility.
Yes for Top Stories carousel. Google officially requires NewsArticle schema (or Article with news markup) for that feature. For Google News inclusion itself, schema is a strong signal but not the only one: you also need a News publisher account, editorial guidelines compliance, and a dedicated news sitemap. Schema tells Google what your article IS; the other signals prove you're a legitimate news source. Together they unlock the full news discovery stack.
Google lists headline, image, and datePublished as required for rich-result eligibility. Article schema without these fields validates as JSON-LD but won't qualify for Top Stories, host carousels, or most enhanced SERP features. Recommended fields add significant lift: author (with sameAs to social profiles), publisher (with logo), dateModified (shows freshness), description, articleSection, wordCount, and keywords. Think of required fields as the minimum for eligibility, recommended fields as the signals that determine which articles actually rank for rich results.
Use ISO 8601 format with timezone: 2026-04-19T09:30:00-04:00 or the simpler UTC form 2026-04-19T13:30:00.000Z. Date-only (2026-04-19) validates but misses timezone context and performs worse for news eligibility. dateModified must be ≥ datePublished, if you edit the article, bump dateModified and Google re-crawls. Lying about dateModified to fake freshness is detectable via archive comparison and can trigger a quality filter. Modify only when you substantively update the content.
Google recommends images ≥ 1200px wide for best rich-result rendering. Supply at least one image; multiple is better (1:1, 4:3, 16:9 aspect ratios in order). Use ImageObject format with explicit width/height when possible, bare URL strings work but ImageObject with dimensions is the gold standard. Images must be crawlable (not blocked by robots.txt), publicly accessible (no authentication walls), and match what's on the visible page. Google ignores schema images that don't appear anywhere in the article body.
Use Person when an individual wrote the article with a real name, this unlocks E-E-A-T signals and author carousel features. Include sameAs with social and LinkedIn profile URLs. Use Organization when content is corporate/unattributed or genuinely team-authored, but be aware Google deprioritizes organization-authored content in E-E-A-T-sensitive topics (YMYL, medical, finance). For ghostwritten or freelance content, the byline should match the real-world visible author on the page. Never invent a persona or use a stock photo, both get detected.
No. One Article schema per canonical URL. Having two Article schemas on the same page creates ambiguity and Google will pick one (usually the first) or ignore both. If a page is actually a collection (index, category, author archive), use CollectionPage or ItemList schema instead. For paginated articles, use one Article schema on the first page and set isPartOf + url pagination correctly on subsequent pages.
Massively yes. AI engines (Google AI Overviews, ChatGPT, Perplexity, Claude) rely on Article schema to identify author authority, publication date, and topical scope. Schema gives them pre-structured provenance signals, author name, org, datePublished, mainEntityOfPage, which they cite directly. Articles with valid schema earn citations at 2-3× the rate of unstructured pages. For AI-search era SEO, Article schema is no longer optional. It's the fastest way to turn your content into LLM-citable source material.
Only when you substantively change the content. New sections, corrected facts, updated statistics, reworked examples. Don't bump it for typo fixes, CSS tweaks, or cosmetic changes. Google detects "pseudo-freshness" (bumping dates without real changes) by comparing archived versions and can suppress the article from freshness-sensitive SERP features. A good rule: if the change would warrant a brief editor's note at the top of the article, update dateModified. Otherwise, leave it.
Technically yes using NewsArticle schema, but Google will ignore it unless your site qualifies as a news source. Non-news sites should stick to Article or BlogPosting. Using NewsArticle as a ranking hack on a blog site triggers spam detection and can hurt overall site quality scores. The exception: sites that genuinely publish news-worthy analysis (company announcements, industry breakdowns, breaking research) can use NewsArticle if the editorial pattern is consistent and the content is time-sensitive.
Completely free, no signup, no email, no limits. Generate schema for unlimited articles, unlimited times. No watermark, no credit required. This tool is part of Grigora's free SEO suite, hopefully after you use it, you'll try our Blog CMS, which auto-generates Article schema from your post metadata so you never copy-paste JSON again. But the free tool stays free regardless.

Stop copy-pasting schema.

Grigora\'s Blog CMS auto-generates Article schema from every post\'s metadata. No drift, no breakage.

Try Grigora free

Auto-generate Article schema on every post.