Free News Article Schema Generator

Why many news stories underperform

How SwiftSchema helps

How it works

What is NewsArticle structured data?

NewsArticle structured data clarifies your news story’s headline, hero images, publish/update dates, authorship, and publisher identity. It is intended for news publishers and helps search engines understand and present your content accurately across Google News, Discover, and other surfaces.

Eligibility & Status

NewsArticle is “limited”: news experiences (such as Top stories) depend on publisher eligibility, policy compliance, and manual reviews. Markup improves clarity but does not guarantee placement. Use NewsArticle only for timely news stories; choose Article or BlogPosting for evergreen or marketing content.

Why news markup matters

• Trust and transparency: Accurate publisher.logo, author names, and timestamps build credibility with readers and search engines.
• Distribution readiness: Consistent schema keeps AMP, canonical, and feed versions aligned, reducing validation errors during syndication.
• Update signaling: Proper dateModified values tell search engines when you’ve updated a story.
• Workflow efficiency: Templates ensure every story ships with compliant metadata, even during breaking news cycles.

Essential properties to include

• headline: Concise, descriptive, and matching the on-page H1/title.
• image[]: Array of high-resolution URLs (≥1200 px). Include multiple sizes for resilience.
• datePublished / dateModified: ISO 8601 timestamps with timezone offsets; update whenever you edit the story.
• author: Person entries with name and optional profile URLs.
• publisher: Organization name plus logo ImageObject (publicly accessible, high resolution).
• mainEntityOfPage: Reference the canonical URL to avoid duplication.
• articleSection, keywords, inLanguage: Clarify beat, tags, and locale.
• Optional: description, wordCount, speakable, embedded VideoObject for multimedia stories.

Preparing newsroom content before generating schema

1. Finalize editorial metadata: Headline, dek, section, tags, embargo times.
2. Select hero imagery: Use licensed, high-quality photos and prepare fallbacks.
3. Verify author bios: Ensure author pages exist (ideally with Person schema).
4. Store publisher assets: Host official logos on a stable CDN with accessible URLs.
5. Document update policy: Decide how to display corrections/updates so dateModified aligns with visible notes.
6. Plan localization: Prep translated headlines and copy for international editions; manage hreflang/canonical settings.
7. QA checklist: Integrate schema validation into your CMS or CI pipeline prior to publication.

Implementation workflow inside SwiftSchema

1. Select NewsArticle in the generator.
2. Enter headline, image[] (≥1200px), datePublished, dateModified, articleSection, keywords, inLanguage, and canonical url.
3. Add author Person entries and publisher Organization with a crawlable logo (include width/height).
4. Include mainEntityOfPage, description, and optional speakable or video objects.
5. Export JSON-LD and embed it in your article template (canonical + AMP); keep content identical across versions.
6. Validate via Rich Results Test or Search Console’s Article tool before shipping; revalidate after edits.

Troubleshooting & QA

• Headline mismatch: Align schema headline with H1 and <title>.
• Low-quality logos/images: Use retina-ready, crawlable assets; avoid blocking with robots.txt.
• Out-of-sync dates: Update dateModified whenever content changes and show update notes on the page.
• Wrong content type: Don’t mark evergreen or promotional pieces as NewsArticle.
• Missing mainEntityOfPage: Reference the canonical URL to reinforce ownership.
• AMP discrepancies: Mirror schema across AMP and canonical pages to avoid validation errors.

Automate QA by running schema validation during staging builds. Fail builds if required fields are missing, images are too small, or dates fall outside expected ranges.

Maintenance and governance

• Maintain a newsroom schema policy explaining when to use NewsArticle, how to document corrections, and how to handle multi-author stories.
• Audit older stories periodically to ensure logos, author bios, and canonical URLs remain valid.
• Update publisher branding in schema immediately after rebrands.
• Keep lastReviewed metadata current for this guide and for internal documentation.

Common Errors & Fixes

• Using NewsArticle for non-news: switch to Article/BlogPosting when appropriate.
• Missing publisher logo: include a crawlable ImageObject with sufficient resolution.
• Overlong headline: shorten to fit snippet limits.
• Stale dateModified: update whenever you edit the story and annotate updates on page.
• Missing mainEntityOfPage: add the canonical URL reference.

On-page parity checklist

• H1/title matches headline; dek/summary aligns with description if used.
• Hero image on-page matches the URLs in image; images are at least 1200px wide and publicly accessible.
• Visible publish/update times match datePublished/dateModified; corrections are noted on-page when dates change.
• Author names on-page match author.name; link to author bios where possible.
• Publisher name/logo on-page (e.g., header/footer) matches publisher and logo in schema.
• Canonical URL is self-referential and matches mainEntityOfPage.@id.
• AMP/alternate versions mirror the same structured data values.

Common mistakes to avoid

• Using NewsArticle for evergreen/marketing content. Use Article or BlogPosting instead.
• Tiny or blocked images. Provide ≥1200px hero images on public URLs; avoid CDN tokens that expire.
• Incomplete publisher logo. Include width/height on the logo ImageObject; host on a stable URL.
• Date drift. Update dateModified and show an on-page update note; don’t backdate to game freshness.
• Canonical confusion. Ensure canonical, mainEntityOfPage, and structured data URLs all point to the same article.
• AMP/canonical mismatch. Keep headline, dates, author, publisher, and images identical across versions.

Troubleshooting and validation

• Rich Results Test errors: Check required fields, image accessibility, and logo dimensions. Verify headline length (<110 chars is safer).
• Search Console Article issues: Confirm the page is indexable, not blocked by robots, and uses consistent canonical tags.
• Missing images in detection: Ensure images are absolute URLs, ≥1200px, and not lazy-loaded without placeholders.
• Publisher/logo not recognized: Host logo at a stable, crawlable URL with width/height; avoid SVG if unsupported in your surface.

Maintenance routine

• Revalidate templates after CMS/theme changes.
• Refresh logos if branding changes; keep the URL stable when possible.
• Rotate hero images only when the story meaning changes; keep metadata in sync.
• Revisit older high-traffic stories quarterly to ensure schema, canonicals, and images are intact.