Article Schema Markup Generator

Help Google show your author, publication date and image in News and Discover — generate valid Article schema markup instantly.

Product Article FAQ Organization Local Business Breadcrumb

Blog posts and news articles — enables author, date, and image in Google News and Discover.

Headline0/110

Max 110 chars recommended

Description

A summary of the article.

Image URL

Min 50K px, multiple ratios

Article URL

Canonical URL of the article page.

Date published

ISO 8601, include timezone

Date modified

Must be ≥ datePublished

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article"
}
</script>

Google Rich Results eligible

Test in Google

How to use the Article Schema Markup Generator

Enter the article headline exactly as it appears in the visible H1 on your page — Google compares schema content against what users see.
Set datePublished to the original publication date. Set dateModified every time you make a significant update — this is a key freshness signal for Google News and Discover.
Fill in the Author section: add the author's name and a URL to their bio page. This is the most impactful E-E-A-T signal in Article schema.
Fill in the Publisher section: add your organization name and a crawlable logo URL (recommended size: up to 600×60 px).
Add an image URL — Google requires at least one image for Article Rich Results in News and Discover. Use a high-resolution image (minimum 50,000 total pixels).
Copy the generated JSON-LD block from the output panel and paste it inside the <head> of your article page.
Validate with the Google Rich Results Test and monitor coverage in Google Search Console → Enhancements → Articles.

How the Article Schema Markup Generator works

Article schema markup is a JSON-LD script block placed in your page's <head> that tells Google exactly what kind of content your page contains — its headline, author, publication date, publisher, and featured image. The generator builds this block locally in your browser with no server calls and no data storage. You fill in the fields, the JSON-LD output updates in real time, and you copy the result into your HTML or CMS.

Once the markup is on your page, Google reads it during the next crawl and uses it to evaluate whether your article qualifies for enhanced visibility in Google Search, Google News, and Google Discover. The schema is completely invisible to readers — it adds machine-readable metadata without changing a single word or image on the page.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Add Structured Data to Any Website",
  "author": {
    "@type": "Person",
    "name": "Maria Koval",
    "url": "https://example.com/about/maria"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Abect",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png"
    }
  },
  "datePublished": "2025-01-15T09:00:00+02:00",
  "dateModified": "2025-05-01T14:00:00+02:00",
  "image": "https://example.com/img/article-cover.jpg"
}
</script>

What Article Schema unlocks in Google Search, News, and Discover

Without Article schema, Google infers the author, date, and publisher from page content — often incorrectly or inconsistently. With correctly filled markup, you give Google a definitive, machine-readable source of truth that unlocks additional visibility surfaces beyond the standard blue-link SERP result.

Google News inclusion — Article schema is a prerequisite for appearing in Google News. Without it, even a site with journalistic-quality content may be excluded from News surfaces entirely.
Google Discover cards — Discover shows large-image content cards to mobile users. Articles with schema and high-quality images get richer card treatment and more prominent placement.
Author byline in SERP — some search result formats display the author's name and publication date beneath the page title, directly visible without a click.
Freshness signals — Google uses dateModified to assess content recency. Updated articles with a current dateModified rank better on freshness-sensitive queries.
AMP integration — Article schema is technically required for AMP pages appearing in Google News carousels. Publisher logo dimensions are strictly enforced in AMP contexts.
E-E-A-T signals — a verified author with a linked bio page and a named publisher organization strengthen Google's assessment of Experience, Expertise, Authoritativeness, and Trustworthiness for your entire site.
Top Stories carousel — eligibility for the Top Stories rich result in mobile search requires Article (or NewsArticle) schema with a valid headline, image, and datePublished.

Article, NewsArticle, or BlogPosting — which type to use

Schema.org defines a hierarchy: Article is the base type, while NewsArticle and BlogPosting are subtypes that inherit all Article fields and add additional meaning. Google supports all three, but the correct choice depends on what your content actually is — using a more specific type gives Google a cleaner signal.

Type	When to use	Google News eligible	Discover eligible	Key difference
Article	General articles, guides, long-form content	Yes (baseline)	Yes	Most universal — safe default when content type is mixed
NewsArticle	Breaking news, press releases, reports	Yes (prioritized)	Yes	Signals time-sensitivity — datePublished is treated as critical
BlogPosting	Personal blog posts, opinion pieces	Limited	Yes	Lower authority signal for News — fine for personal or brand blogs
TechArticle	Technical documentation, tutorials, API references	No	Yes	Signals developer-facing content — no specific rich result format
Review	Product or service reviews with a rating	No	Yes	Can combine with Product or LocalBusiness schema on the same page

For most content marketing and editorial sites, Article is the safest and most flexible choice. Use NewsArticle only if your content is genuinely time-sensitive news — Google scrutinizes datePublished more strictly for NewsArticle than for the base Article type.

When Article Schema delivers results — and when it does not

Pages where Article Schema is the right choice

Blog posts and editorial articles with a named author and a clear publication date — the most common and effective use case for Article schema.
News and press releases on publisher sites — use NewsArticle for time-sensitive content that competes in the Top Stories carousel.
Long-form guides and pillar pages — Article schema signals depth and authoritativeness, supporting E-E-A-T evaluation for competitive informational queries.
Content marketing articles on brand sites — even without a dedicated newsroom, Article schema helps Google identify the author and publisher behind branded content.
AMP pages — Article schema is a technical requirement for AMP articles appearing in the Google News carousel and Top Stories on mobile.

Pages where Article Schema will not help or may be incorrect

Product pages and landing pages — these are not articles. Use Product schema or WebPage schema instead. Applying Article markup to a product page sends a confusing signal to Google.
Category and archive pages — listing pages that aggregate multiple articles do not qualify as Article. Leave them without Article schema or use CollectionPage.
Pages without a clear publication date — if the page has no visible date and you cannot honestly fill in datePublished, the schema will have limited effectiveness.
Evergreen pages updated continuously — if the page has no meaningful "published on" date (like a live documentation wiki), Article schema is a poor fit. Use WebPage instead.
Pages without a named author — Article schema without an author is valid but provides minimal E-E-A-T benefit. The author field is what makes Article schema most valuable for trust signals.

Technical deep dive: author URL, dateModified, and publisher logo

author.url is the single most underutilized field in Article schema. When you link the author to a URL — ideally a bio page on your own site that describes the author's credentials, experience, and published work — Google can build an entity connection between the author and the content. This is the core mechanism behind E-E-A-T author signals. The URL does not have to be Wikipedia (though that is ideal); a well-structured author page at `example.com/about/your-name` works. For the strongest signal, the author bio page itself should also reference the author's social profiles via `sameAs` in its own markup.

dateModified is frequently set once at publication and never updated — this is a missed opportunity. Google News and Discover actively use dateModified as a freshness signal. When you update an article with new information, corrected data, or additional sections, updating dateModified tells Google the content is current. However, avoid updating dateModified for trivial edits like fixing typos — Google may penalize sites that constantly update timestamps on unchanged content to artificially appear fresh.

publisher.logo has strict size constraints that are enforced in AMP contexts: the logo must fit within a 600×60 px bounding box (width ≤ 600 px, height ≤ 60 px). A square logo at 60×60 px works best. The logo URL must be directly crawlable by Google — no redirects through login pages, no lazy-loaded images. If your logo fails the logo size check, your AMP pages may be excluded from the Google News carousel even if all other fields are correct.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "NewsArticle",
  "headline": "Google Updates Product Schema Requirements for 2025",
  "description": "Google has revised the required fields for Product rich results, adding shipping as a recommended field.",
  "image": {
    "@type": "ImageObject",
    "url": "https://example.com/img/article.jpg",
    "width": 1200,
    "height": 630
  },
  "author": {
    "@type": "Person",
    "name": "Maria Koval",
    "url": "https://example.com/about/maria-koval",
    "sameAs": [
      "https://linkedin.com/in/mariakoval",
      "https://twitter.com/mariakoval"
    ]
  },
  "publisher": {
    "@type": "Organization",
    "name": "Abect",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png",
      "width": 300,
      "height": 60
    }
  },
  "datePublished": "2025-01-15T09:00:00+02:00",
  "dateModified": "2025-05-01T14:30:00+02:00",
  "url": "https://example.com/blog/google-product-schema-2025",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://example.com/blog/google-product-schema-2025"
  }
}
</script>

Frequently Asked Questions

What is the difference between Article, NewsArticle, and BlogPosting?

All three are valid Article schema types that Google supports. Article is the base type and the safest default for most content. NewsArticle is a subtype intended for time-sensitive journalism — Google treats its datePublished more strictly and it gets priority consideration for the Top Stories carousel. BlogPosting is for personal or brand blog content and carries a lower authority signal for News surfaces. Use the most specific type that honestly describes your content.

Is Article schema required to appear in Google News?

Article schema is not the only requirement for Google News inclusion, but it is a strong signal that Google expects. Without it, your content may still appear in News if Google's crawler identifies it as news-like content, but schema significantly improves consistency and eligibility. For AMP articles in the News carousel, Article schema is technically required.

Does Article schema help with regular Google Search rankings?

Not directly — structured data is not a ranking factor in standard search. However, Article schema enables Rich Results (author byline, image, date) that increase click-through rates in the SERP. Higher CTR is an indirect positive signal. More importantly, the E-E-A-T signals from author URL and publisher data influence Google's quality assessment of your entire site, which does affect long-term ranking potential.

Is the author URL field required?

No — author.url is not required for the schema to be technically valid. However, it is the most impactful field for E-E-A-T signals. Without it, Google knows the author's name but cannot verify their identity or expertise. With a linked bio page, Google can build an entity connection between the author and the content. Always include author.url when possible — point it to an author bio page on your site, a LinkedIn profile, or a Twitter profile.

Can an article have multiple authors?

Yes — the author field can be an array of Person or Organization objects. For example: "author": [{"@type": "Person", "name": "Maria Koval"}, {"@type": "Person", "name": "Ivan Petrenko"}]. Google supports multiple authors in Article schema and may display co-author information in supported rich result formats.

Should I update dateModified every time I edit the article?

Update dateModified only when you make substantive changes — new sections, corrected facts, updated statistics, or significantly revised content. Do not update it for minor typo fixes or formatting changes. Google has issued guidance against artificially refreshing timestamps on unchanged content — sites that do this consistently may see their freshness signal discounted.

What image should I use in Article schema — the OG image or a separate one?

You can use the same image as your OG image if it meets the requirements: minimum 50,000 total pixels (e.g., 696×696 px or larger), crawlable without login, and in a supported format (JPEG, PNG, WebP). Google recommends providing images in multiple aspect ratios (16:9, 4:3, 1:1) so it can select the best crop for different surfaces (Discover, News, Search). Use the ImageObject type with explicit width and height for the strongest signal.

What are the publisher logo size requirements?

For AMP and Google News, the publisher logo must fit within 600×60 pixels — width no more than 600 px, height no more than 60 px. A 60×60 px square logo is the safest option. The logo must be a simple, text-based or symbolic logo — not a marketing image or hero banner. It must be directly accessible by Google without authentication.

Can I combine Article schema with FAQ schema on the same page?

Yes — this is a recommended combination for long-form articles that include a Q&A section. Add Article schema for the overall article metadata and a separate FAQPage schema block for the Q&A content. Google reads both independently. Keep them in separate <script type="application/ld+json"> blocks. The FAQ accordion can appear in the SERP alongside the article snippet.

What happens if datePublished is wrong or missing?

If datePublished is missing, Google infers the date from page content or crawl history — often incorrectly. An incorrect inferred date can hurt your visibility on time-sensitive queries. If datePublished is set to a future date, Google may delay indexing the rich result. Always use the actual original publication date and never backdate or frontdate it — Google cross-references the crawl timestamp.

Does Article schema work on single-page React or Next.js apps?

Yes, but the JSON-LD must be present in the server-rendered HTML — not added via useEffect after page load. In React with Vite, use react-helmet-async to inject the script into the <head> during SSR or prerendering. In Next.js App Router, use the built-in metadata API or a <script> tag with dangerouslySetInnerHTML in a Server Component. If Google's crawler sees the page before JavaScript runs and the schema is not in the initial HTML, it will not be indexed.

How do I verify that Google picked up my Article schema?

First, test the page URL in the Google Rich Results Test immediately after publishing — it shows whether the schema is valid and what rich results it qualifies for. After Google re-crawls the page (request re-indexing via URL Inspection in Search Console), check Search Console → Enhancements → Articles. This report shows the number of valid, invalid, and warning-state Article pages across your site and details any field-level issues.