Article Schema Generator — Clarify Headline, Images, and Dates

Generate valid Article JSON‑LD in minutes. Improve article understanding and eligibility for rich displays by nailing headline, image, and publish/updated dates.

Try the Article Generator

Why many articles underperform

Pain points we solve

• Your snippet doesn’t reflect the real headline or updated date.
• Missing or low‑quality images limit how your article appears in surfaces.
• Hand‑written JSON‑LD leads to validator warnings and inconsistent results.
• Using NewsArticle without meeting publisher criteria causes confusion.

How SwiftSchema helps

Solution

The Article generator guides you to provide the fields that matter most: headline, high‑quality image(s), datePublished, and dateModified.

It outputs clean, copy‑ready JSON‑LD you can paste once per article. Optional author and publisher details help reinforce credibility and context.

Use BlogPosting for blog content, Article for general articles, and reserve NewsArticle only if you meet news publisher criteria.

How it works

How it works

1. Choose Article in the generator below.
2. Enter headline, at least one high‑quality image URL, and datePublished.
3. Add dateModified, author, and publisher when relevant.
4. Copy JSON or Script, paste into your article page, and validate in the Rich Results Test.
5. Publish with confidence knowing your metadata is consistent and crawlable.

Generate Article JSON‑LD

Paste once per page. Validate. Ship.

What is Article structured data?

Article structured data is the baseline schema for long-form content. It codifies your headline, hero imagery, publish/updated dates, and authorship so search engines can interpret your story correctly. When done well, this markup aligns the snippet that appears in Google, Discover, and other surfaces with the real content users see. When done poorly—missing images or mismatched dates—you risk misleading snippets, “Unknown author” labels, or ineligible placements.

The Article type is flexible: use it for evergreen guides, editorial think pieces, research summaries, or white papers. If the piece is unmistakably a blog entry, use BlogPosting (a subtype of Article). Reserve NewsArticle only for organizations that meet Google News Publisher policies; using NewsArticle without accreditation can trigger manual actions for misrepresentation. The Schema.org hierarchy makes it easy to extend Article with specialized subtypes (e.g., TechArticle) while keeping the foundational properties consistent.

Required and high-impact properties

1. headline
   — Keep it under ~110 characters (per Google guidance) so it doesn’t truncate. Ensure it matches the on-page H1.
2. image
   — Provide 1–3 URLs to 16:9 images at least 1,200px wide. Use absolute URLs and host them on your domain.
3. datePublished
   — ISO 8601 date (e.g.,
   2025-11-08
   ). Make sure it matches the visible timestamp.
4. dateModified
   — Update it whenever you materially edit the piece; don’t refresh it for typo fixes.
5. author
   — Person or Organization. Include
   @type
   ,
   name
   , and optionally
   url
   or
   image
   .
6. publisher
   — If you’re an organization with a recognizable brand, include publisher with logo to reinforce trust.
7. mainEntityOfPage
   — Reference the canonical URL for disambiguation when syndicating.
8. articleSection
   — Label the content category (“Guides”, “Opinion”, “Case Study”) to help search engines cluster similar pieces.

Optional enhancements include

, (for voice assistants), (VideoObject), and if you want to expose the full text.

Content prep before generating schema

Structured data should mirror reality, so confirm the following before copying JSON‑LD:

• The headline, deck, and hero image are finalized.
• The byline identifies the correct author (including guest contributors).
• The canonical URL is published and accessible (no 404 or staging paths).
• The article includes at least one high-res, crawlable image within the HTML.
• Publish and update timestamps are expressed in ISO format and visible to readers.

If you plan to update the article periodically (e.g., “2024 Tax Guide”), add a “Last updated” paragraph near the top. That reminder helps editors remember to update

in the schema without guesswork.

Implementation checklist

1. Choose the right type:
   Article
   for general content,
   BlogPosting
   for blog entries,
   NewsArticle
   only if you meet news standards,
   TechArticle
   for developer docs with code snippets.
2. Gather assets: headline, canonical URL, hero image URLs (minimum 1,200px wide), publish/updated dates, author bios, publisher logo (112x112 or larger, square).
3. Generate JSON‑LD: Use the form below to capture fields. Include optional
   articleSection
   ,
   keywords
   , or
   speakable
   if relevant.
4. Embed once per page: Place JSON‑LD in the
   <head>
   or just before closing
   </body>
   . Avoid duplicating Article schema across multiple script tags.
5. Validate: Run Google’s Rich Results Test and pay attention to warnings (e.g., missing
   publisher.logo
   ). Fix them before shipping.
6. Monitor: After publishing, use Search Console’s URL inspection to request indexing. Track impressions/clicks under “Discover” or “Search Appearance > Articles.”

Image best practices

Google requires large, high-quality imagery for surfaces like Discover. Follow these tips:

• Minimum width 1,200px, ideally 1,600px for cross-device consistency.
• Use JPG/WebP with minimal compression artifacts.
• Don’t overlay text or logos that cover more than 20% of the image.
• Host images on the same domain and avoid blocking them via robots.txt.
• Provide multiple aspect ratios if your CMS supports it: 16:9, 4:3, 1:1.

When featuring multiple images, list them in the

array in order of relevance. If the article uses a hero video, include both VideoObject and image references to maximize eligibility.

Date hygiene

Nothing erodes trust faster than a snippet that says “Updated today” when the content hasn’t changed. Follow these rules:

• Only update
  dateModified
  when you add or revise substantive content (new data, new sections, major corrections).
• Store
  dateModified
  in your CMS so editors don’t forget to change it when republishing.
• Display the updated timestamp near the top of the article so readers and crawlers see the same information.
• Use consistent time zones (prefer UTC) in schema and meta tags.
• When migrating content, keep the original publish date if the URL remains the same; note the migration in the body copy if needed.

Common implementation pitfalls

• Headline mismatch: The title tag, H1, and
  headline
  should align. If marketing rewrites any of them, update the others.
• Image fetch errors: If the image URL returns 403 or 302, crawlers can’t fetch it. Double-check CDN permissions.
• Multiple Article blocks: Some CMS plugins inject duplicate schema. Use browser devtools to confirm only one Article script appears.
• Using NewsArticle without credentials: Unless you’re enrolled in Google News or have E-E-A-T proof, stick to Article/BlogPosting to avoid policy violations.
• Forgetting
  mainEntityOfPage
  : This property helps when articles syndicate to partner sites; it points back to the canonical source.

Troubleshooting checklist

• Run the Rich Results Test and copy any warnings into your issue tracker.
• Use Search Console’s “Enhancements > Articles” (if available) to monitor coverage.
• Check the URL in Google’s Structured Data Testing Tool to ensure the schema parses even when JS is disabled.
• Inspect the live page’s HTML to verify
  datePublished
  and
  dateModified
  values match the schema and meta tags.

Editorial workflow tips

Create a content brief template that includes a schema checklist: headline length, image specs, author bio link, canonical URL, and reference links. Share it with writers and editors so structured data becomes part of the editorial process, not an afterthought.

For sites with multiple author personas, maintain an

file or CMS table storing each author’s schema-friendly details (name, URL, image). When an author publishes, pull their data automatically into the Article JSON‑LD to reduce manual errors. If you host both English and localized versions of articles, add and link alternate versions via tags and hreflang annotations so crawlers know which article serves which market.

Common Errors & Fixes

• Headline too long: Keep under ~110 characters, mirroring the H1. Truncate or create a shorter headline for schema if needed.
• Missing images: Provide high-quality, crawlable image URLs with sufficient width.
• Incorrect type: Use Article/BlogPosting subtypes unless you meet news criteria.
• Stale timestamps: Update
  dateModified
  only when making substantive edits, and sync it with the visible “Updated on” label.
• Broken canonical links: Ensure
  mainEntityOfPage
  references the live canonical URL, not staging or UTM-laden links.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Add Product Structured Data",
  "image": [
    "https://example.com/images/article-cover.webp"
  ],
  "datePublished": "2025-04-16",
  "dateModified": "2025-04-20",
  "author": {
    "@type": "Person",
    "name": "A. Writer"
  }
}