SchemaForAI
Ad

Free Article Schema Generator for AI Search

Generate JSON-LD schema markup for articles, news stories, blog posts, and tech guides. Optimized for ChatGPT, Google AI Overviews, and Perplexity. No sign-up required.

Article Details

Article / NewsArticle / BlogPosting / TechArticle

Choose the schema.org type that best fits your content.

Use NewsArticle for time-sensitive journalism, BlogPosting for opinion pieces, TechArticle for technical docs, and plain Article for everything else.

The article title. Keep it under 110 characters for Google rich results.

AI engines weight the headline heavily when deciding whether to cite. Lead with the entity or topic — not clickbait.

Name of the person who wrote this article.

Named authors with a real Person entity get cited by AI significantly more often than anonymous or 'Staff' bylines.

Name of the organization or website publishing the article.

The publisher should match the Organization entity you control. Consistency across pages builds AI trust.

The date this article was first published.

Recency matters — AI engines prefer fresh articles for time-sensitive topics. Always provide this.

The most recent date the article was meaningfully updated. Optional but recommended.

Updating this when you refresh content signals freshness to AI engines without republishing.

Minimum 50 characters. This is what AI engines read first — make it complete and self-contained.

0 / 300

Treat the description as an elevator pitch for your article. Include the primary entity and the unique insight.

Full URL to the article's featured image. Minimum 1200px wide recommended.

AI visual search (Gemini, GPT-4V) indexes images via schema. Use a high-resolution, descriptive image.

The canonical URL where this article lives.

The canonical URL anchors your article as an entity in AI knowledge graphs. Keep it stable.

JSON-LD
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your article headline here",
  "description": "A 1–2 sentence summary of the article…",
  "image": "https://example.com/cover.jpg",
  "datePublished": "2026-01-15",
  "author": {
    "@type": "Person",
    "name": "Author Name"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Publisher Name"
  },
  "url": "https://example.com/article"
}

AI Readiness Score

Get a 0–100 score showing how likely AI search engines are to parse and cite content from your page.

How to use this code:

  1. Copy the JSON-LD code above
  2. Paste inside <script type="application/ld+json">
  3. Add the <script> tag to your page <head>
  4. Validate with Google Rich Results Test ↗
AI Simulator

See how ChatGPT answers — with and without your schema

Side-by-side comparison of what an AI assistant would return for a typical article query, with vs. without the structured data you generated above.

3 of 3 remaining today

Sample user query

What does this article cover?

Without Schema
Generic answer

Click Simulate to see the AI response without schema.

With Schema
Detailed citation

Click Simulate to see the AI response with schema.

Install Guide

How to install this schema on your site

Pick your platform. Every step includes a copy-paste-ready code block where it applies.

  1. 1

    Install and activate a schema plugin: "Rank Math SEO", "Yoast SEO Premium", or "Schema Pro". For straight JSON-LD injection without a full SEO plugin, "WPCode" (formerly Insert Headers and Footers) is the simplest option.

  2. 2

    In Rank Math: go to the post edit screen → Rank Math sidebar → Schema tab → Schema Builder → paste your JSON-LD. In Yoast Premium: the Schema tab auto-generates standard types; use the Custom Schema plugin add-on to inject custom types.

  3. 3

    For WPCode: Code Snippets → Add Snippet → Custom Code (HTML/PHP) → paste the full <script type='application/ld+json'> tag. Set Location to 'Site Wide Header' or 'Specific Post/Page' depending on scope.

    html
    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "FAQPage",
      "mainEntity": [ /* your Q&A pairs */ ]
    }
    </script>
  4. 4

    Publish the post. Open the live URL, view source, confirm the <script type="application/ld+json"> tag appears in the <head>.

  5. 5

    Validate at search.google.com/test/rich-results.

What is Article Schema Markup?

Article schema markup is a family of Schema.org types that describe written content — news stories, blog posts, tutorials, investigations, opinion pieces — in a format that search engines and AI systems can parse and trust. Instead of inferring the author, publication date, or topic of your article from page text, crawlers read the structured data and know definitively who wrote the piece, when it was published, who published it, and what it is about.

The schema.org vocabulary exposes four practical subtypes you will use in day-to-day publishing: Article (the generic, safe default), NewsArticle (for time-sensitive journalism from a news organization), BlogPosting (for blog posts, personal essays, and company blog content), and TechArticle(for technical documentation and developer-oriented guides). Each subtype inherits from Article, so any property available on Article is available on the others, but search engines and AI systems use the subtype itself as a soft signal about the content's intent and authority.

The markup lives inside a JSON-LD script tag in your page head:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How Article Schema Boosts AI Citations",
  "author": {
    "@type": "Person",
    "name": "Jane Doe"
  },
  "datePublished": "2026-01-15",
  "image": "https://example.com/cover.jpg",
  "publisher": {
    "@type": "Organization",
    "name": "Example Media"
  }
}
</script>

Every well-formed Article schema connects three entities: a Person (the author), an Organization (the publisher), and the article itself. This triangle — person wrote it, organization stood behind it, here is the canonical URL — is what makes Article schema so valuable to AI engines building knowledge graphs.

Ad

Why Article Schema Matters for AI Search Engines

AI search engines don't just read pages — they build knowledge graphs. When Perplexity decides whether to cite your piece, or when Google AI Overviews picks a source to synthesize, the engine is reasoning about entities (people, organizations, articles) and how they relate to each other. Article schema is the most efficient way to insert your content into that graph correctly.

Consider what AI engines weight most heavily when ranking sources for a generative answer:

  • Named-author E-E-A-T signals: Articles attributed to a real, named Person — especially one linked to external credentials via sameAs — consistently outperform anonymous or "Staff" bylines in AI citations. The author field in Article schema is the cleanest way to establish this connection.
  • Freshness via datePublished / dateModified: AI engines heavily discount stale content on time-sensitive topics. A properly maintained dateModified field preserves link equity while resetting the freshness signal when you substantively update a piece.
  • Publisher-as-entity reinforcement: Linking the publisher Organization in every article on your site reinforces your brand as a coherent entity in the AI knowledge graph. Over time, this accumulated signal makes all your content more citable.
  • Canonical URL anchoring: The url field locks the article to a stable identity. AI engines deduplicate citations by URL — without it, two copies of your article (with and without tracking parameters, on AMP and non-AMP paths) can fragment your authority across multiple weaker entities.
  • Subtype specificity: Using NewsArticle for breaking news signals time-sensitivity and nudges engines toward recency-ranked surfaces. TechArticle signals a developer audience and can qualify your content for code-oriented AI Overviews. BlogPosting signals opinion, which AI engines treat differently than hard reporting.
  • Image-aware AI retrieval: Modern AI engines including Gemini and GPT-4V index article images through schema. A high-resolution, descriptively named image linked via the image field can show up as the hero in an AI Overview card.

The practical result: two articles with identical body content can receive radically different AI citation rates based purely on the quality and completeness of their Article schema. A well-marked-up article on a mid-authority domain regularly outperforms an unmarked article on a top-tier domain in generative answers — AI engines prefer the clean, machine-verifiable signal to the ambiguous one.

Article Schema Best Practices for AI Visibility

Adding Article schema is trivial. Adding Article schema that actually moves AI citation rates takes attention to detail. Here's what separates the implementations that work from the ones that just exist:

Pick the most specific subtype

Don't default to Article when NewsArticle or TechArticle genuinely fits. The subtype is a soft authority signal — using the right one earns placement on AI surfaces that filter by content type.

Keep headline under 110 characters

Google truncates longer headlines in rich results, and AI engines often display the headline verbatim in citation cards. Write for that constraint: lead with the entity, not with clickbait.

Always include a named author

An anonymous article forfeits the single strongest AI citation signal available to it. If real-name bylines aren't available, use a pseudonymous Person entity with a bio page — still better than nothing.

Link author to sameAs profiles

On the author's bio page, add a Person schema with sameAs links to their LinkedIn, GitHub, ORCID, or other verifiable profile. This turns your author into a cross-platform entity AI engines can trust.

Match image URL to the visible image

Google penalizes schema whose image field doesn't match a visible, dominant image on the page. Use the same URL in your og:image and Article.image — it also simplifies asset management.

Never fake dateModified

Bumping dateModified without meaningful content change is the most common schema manipulation AI engines detect and discount. Update it when you revise arguments, numbers, or claims — not on typo fixes.

Keep publisher consistent sitewide

The publisher field should be identical across every article on your domain, pointing to the same Organization entity. Variations dilute the authority signal and can read as multiple sub-brands to AI engines.

Add articleSection for large sites

If you publish across multiple verticals (tech, business, lifestyle), populate articleSection so AI engines can route readers based on topical authority. It's optional but high-leverage for media sites.

How to Install Article Schema on Your Website

WordPress

  1. 1Generate your Article JSON-LD above and click Copy.
  2. 2Install a code-injection plugin such as WPCode, or use a theme that supports per-post custom code.
  3. 3On the post edit screen, paste the JSON-LD into the post-specific header snippet — this scopes the schema to this article only.
  4. 4Ensure your theme isn't already outputting conflicting Article schema. If it is, disable the theme's version first.
  5. 5Publish and validate with Google Rich Results Test.

Next.js / React

  1. 1Import the JSON-LD as a constant at the top of your article page component.
  2. 2Render it in a <script type="application/ld+json"> tag inside the page, using dangerouslySetInnerHTML.
  3. 3Replace any </script> substrings inside string fields with <\/script> to prevent HTML parsing issues.
  4. 4For dynamic articles, build the object from CMS data rather than hand-writing JSON.
  5. 5Verify with the Rich Results Test after deploy.

Shopify / Ghost / Substack

  1. 1Copy the generated JSON-LD.
  2. 2In Shopify, edit your blog article template (article.liquid or your theme's equivalent) and paste inside the <head> block.
  3. 3In Ghost, use the Code Injection section of the post settings.
  4. 4In Substack, use a manual script insertion via custom code (available on paid plans).
  5. 5Preview the post and validate the live URL with Google Rich Results Test.

Frequently Asked Questions

Which Article subtype should I use — Article, NewsArticle, BlogPosting, or TechArticle?+
Use the subtype that most accurately describes your content. NewsArticle is for time-sensitive journalism produced by a news organization — think original reporting, press releases, breaking news. BlogPosting is for opinion pieces, personal essays, or company blog posts that aren't strictly journalistic. TechArticle is for technical documentation, developer guides, and engineering write-ups — Google gives this subtype slightly different treatment in rich results. Plain Article is the safe default when your content doesn't fit neatly into the others. AI engines use the subtype as a soft signal about the content's intent and authority, so picking the most honest match improves citation quality.
How long should the description field be?+
Aim for a range of 100 to 160 characters, which is long enough to capture the article's unique claim or finding but short enough to render cleanly in AI search snippets and social cards. Treat it like a one-sentence elevator pitch: lead with the primary entity (product, person, concept), state what the article concludes or explains, and avoid generic marketing language. AI engines including Perplexity and ChatGPT read this field before the body, so a vague description like "Learn everything about SEO" will lose every time to a sharper one like "A 2026 analysis of how Article schema markup affects Perplexity citation rates."
Do I need both datePublished and dateModified?+
datePublished is required for any Article — it anchors the piece in time and lets AI engines judge freshness. dateModified is optional but highly recommended: when you substantively update an article, bumping this date without changing the URL signals to AI engines that the content has been refreshed. This preserves backlinks and accumulated authority while restoring the freshness signal. A common mistake is updating dateModified on cosmetic edits (typo fixes, image swaps) — reserve it for meaningful updates to facts, arguments, or numbers. Over-incrementing this field without real content change can be detected and discounted.
Why is the author field so important for AI citation?+
Large language models and AI search engines are increasingly weighting E-E-A-T signals (Experience, Expertise, Authoritativeness, Trust), and the named author is the primary anchor for all of them. A page attributed to "Staff" or left anonymous gets cited far less often than one attributed to a named Person entity. Even better: link the author to a Person schema elsewhere on your site with sameAs references to their LinkedIn, GitHub, or scholarly profiles. This connects the article to a verifiable human with a verifiable track record, which is exactly what AI engines are trained to trust.
What image size and format should I use?+
Use a featured image at least 1200 pixels wide for Google rich results eligibility. Google's guidance allows any aspect ratio, but 16:9 and 4:3 are most universally compatible across AI surfaces (including ChatGPT's inline image rendering and Perplexity's card layout). Prefer modern formats like WebP or AVIF for smaller file sizes, but keep a JPEG fallback for older crawlers. Host the image on the same domain as your article or a well-known CDN — images hosted on short-lived URLs or image-proxy services are sometimes ignored by stricter AI parsers. File names and alt text matter too: descriptive file names like author-jane-doe-interview.jpg outperform IMG_4521.jpg.
Can I include multiple authors?+
Yes. The author field accepts a single Person or an array of Person objects. For a co-authored article, pass an array so both authors receive citation credit in AI responses. Each Person entry should include at minimum a name, and ideally a url pointing to a bio page and sameAs links to external profiles. AI engines correctly attribute quotes and claims to the right author when the schema is structured clearly. If there's a primary author and contributors, use the author field for the primary and the contributor field for others — this preserves the hierarchical credit structure.
Should the URL in schema match the page's canonical tag?+
Always. The url field in your Article schema must exactly match the URL in your <link rel="canonical"> tag. Mismatches cause AI engines (and Google) to distrust one or both signals. If your article is accessible at multiple URLs (with and without www, with UTM parameters, through an AMP variant), pick one canonical form and use it consistently across schema, canonical tags, sitemaps, and internal links. Inconsistency is the single most common cause of an article with perfect content underperforming in AI citations.
Is Article schema still worth adding if I already have Open Graph tags?+
Yes — they serve different audiences. Open Graph is primarily for social previews (Facebook, LinkedIn, Slack), while Article JSON-LD is for search crawlers and AI systems. The two overlap in what they describe but don't substitute for each other. Open Graph gives you a social card; Article schema gives you an entity in the AI knowledge graph. Modern sites include both. They should of course agree on the facts (same title, same image, same author), but you should not omit Article schema just because og:title exists on the page.

Related Schema Generators

Ad