Schema · Free

Free Article Schema Generator

Generate Article, NewsArticle, BlogPosting, or TechArticle JSON-LD schema with author, publisher, image, and date fields. Smart date parsing, schema.org-compliant output, ready to paste into your page head.

  • No signup, no email required
  • Works entirely in your browser
  • Output you can copy and paste directly
  • Built by a working SEO team, not gated by upsells

Article details

Output

JSON-LD
// Add at least a headline to generate JSON-LD.
Validate
Open Rich Results Test

What it does

Article schema is the structured-data type for editorial content on the web — blog posts, news stories, tutorials, opinion pieces, long-form essays. This generator produces valid JSON-LD across the four most-used Article subtypes:

  • Article — generic catch-all for any editorial content that does not fit a more specific type.
  • BlogPosting — for blog posts. The most common type for company blogs and content marketing.
  • NewsArticle — for news content with time-sensitive reporting. Required for inclusion in Google News.
  • TechArticle — for technical or how-to content with a primarily instructional purpose.

Pick the subtype that best matches your content. The schema fields are largely the same across all four; the type signal helps Google and other search engines categorize the content correctly.

Why Article schema matters in 2026

Article schema is one of the few structured-data types that remains broadly useful in 2026 even as Google has deprecated rich-result eligibility for several others. The reasons:

  • Google News & Discover eligibility. NewsArticle schema is effectively required for inclusion in Google News. Discover increasingly favors content with explicit author and publisher metadata.
  • AI Overview citation. Pages with valid Article schema are cited at noticeably higher rates in AI Overview answers than comparable unstructured pages.
  • Author entity recognition. Adding a Person entity for the author with a URL helps Google build an entity for the author across the web — a meaningful signal for trustworthiness on YMYL topics.
  • Publisher entity recognition. Publisher data with a logo helps Google associate articles with your brand entity, improving knowledge-panel and brand-search performance.

How to use this generator

  1. Pick the schema type. Most company blog content is BlogPosting. Reach for Article only if BlogPosting does not fit (e.g., academic-style content). NewsArticle is for time-sensitive journalism.
  2. Fill the headline. The only strictly required field. Keep it under ~110 characters; longer headlines get truncated in some Google features.
  3. Add the author. Always include a real person as author when possible. The Person entity helps Google build author authority over time. URL is optional but strongly recommended — link to a real author bio page.
  4. Add the publisher with logo. Required by Google for News and several rich-result types. The logo should be a fully-qualified URL pointing to a 600×60 px (or larger) image.
  5. Set the dates. datePublished is required; dateModified should be updated whenever you materially change the article. Fresh dateModified often improves rankings on time-sensitive queries.
  6. Copy the output and paste into the <head> of the article page. Validate with the Rich Results Test.

Article schema best practices

  • Real author, real bio. Use a real person, not a brand name, for the author field. Anonymous or company-attributed articles can use Article-type without author, but Google rewards named authors with trustworthy bios.
  • Update dateModified when you actually update. Padding dateModified to game freshness is a documented anti-pattern. If you do not change the content, do not change the date.
  • Use ISO 8601 dates. 2026-05-08T10:00:00Z or 2026-05-08. Free-text dates fail validation. This tool converts plain YYYY-MM-DD dates automatically.
  • Image must be fully-qualified. https://yoursite.com/image.png, not /image.png. Relative URLs fail validation.
  • Match schema content to visible content. The headline in your schema should match the H1 (or be very close). Author shown in schema should match the byline on the page. Mismatches risk a manual action.
  • Use mainEntityOfPage. Pointing this at the canonical URL of the article tells Google which URL is the authoritative one — useful when the same content appears on multiple URLs (AMP, syndication).
  • Don't over-stuff the keywords field. Three to seven topical keywords is the sweet spot. Beyond that, the field is ignored.

Common Article schema mistakes

  • Using BlogPosting on landing pages. Landing pages, product pages, and category pages are not articles. Use the appropriate schema (Service, Product, ItemList) for those.
  • Generic publisher logo. Using a placeholder image URL or a logo that does not match what visitors see on the page itself fails Google's content-match check.
  • Missing dateModified on update. Forgetting to update dateModified after a substantial article rewrite means Google still treats the content as stale.
  • Author as a brand. author: { "@type": "Organization", "name": "Brand" } is technically valid but signals lower trustworthiness than a Person author. Use Person whenever you have a real author.
  • Skipping the schema entirely on short posts. Even a 400-word blog post benefits from Article schema. The cost is zero; the upside is real.

Frequently asked questions

What's the difference between Article, BlogPosting, and NewsArticle?

Article is the generic parent type. BlogPosting is for blog posts (the most common case for content marketing). NewsArticle is for time-sensitive journalism and is required for Google News inclusion. TechArticle is for technical/how-to content. Pick BlogPosting for most company blog content.

Do I need both datePublished and dateModified?

datePublished is required; dateModified is optional but strongly recommended. Initially set dateModified equal to datePublished. Update dateModified whenever you make substantial edits — Google rewards fresh content on time-sensitive queries.

Can the author be an Organization instead of a Person?

Technically yes, but Person is preferred. Google's author authority signals work best on real human authors with verifiable bios. Anonymous content or content attributed to a brand handles fine in schema but earns less trust signal long-term.

What size should the publisher logo be?

Minimum 600×60 px for Google News eligibility. Aspect ratio should be wider than tall. Use a fully-qualified URL (https://yoursite.com/logo.png), not a relative path.

Will Article schema get me into Google News?

It's a prerequisite for Google News, but not sufficient on its own. Google News also requires editorial standards, regular publishing cadence, named authors, and adherence to content policies. Article schema gets you in the door; the rest of your editorial setup keeps you there.

Should the headline match the H1?

Yes, ideally. Substantial mismatches between the schema headline and the page's H1 can be flagged as content-mismatch. Small variations (subtitle differences) are fine; completely different headlines are not.

Will this tool log my data?

No. Everything runs in your browser. The fields you fill never leave your device — there is no server endpoint and nothing to log.