Article schema is the foundational layer of structured data for any content-driven SEO strategy targeting AI citations. While FAQPage and HowTo schema provide specific content format signals, Article schema provides the authority and provenance context that AI systems require before they will cite any document: who wrote this, when was it published, who published it, and what is the canonical URL. Without Article schema, an AI system retrieving your content must infer all of these fields from unstructured signals—byline text, footer dates, domain names—a process that introduces errors and reduces citation confidence. With Article schema, you are handing AI systems a complete, authoritative record of your document's identity. This guide covers the Article schema specification in full, the subtype strategy (Article vs. TechArticle vs. NewsArticle), implementation best practices, and the author entity optimization that is increasingly important for AI trust scoring.
Article Schema Subtypes and When to Use Each
Schema.org defines Article as the parent type and several subtypes for more specific document categories. The three most relevant for AI SEO are Article (general informational content), TechArticle (technical documentation, tutorials, and reference material), and NewsArticle (time-sensitive news and press coverage). Choosing the right subtype matters because AI systems trained to answer different query types weight these subtypes differently. For a query like 'how does structured data affect AI citations', an AI system will preference TechArticle sources over generic Article sources when the TechArticle has matching technical authority signals. NewsArticle schema triggers freshness weighting—AI systems treat NewsArticle-marked content as time-sensitive and weight it higher in the days immediately after publication, then de-weight it as the publication date recedes. For most B2B and SaaS content teams, TechArticle is the correct subtype for product guides, tutorials, and analysis; Article is correct for opinion pieces, case studies, and general informational content. AdvertorialArticle and SatiricalArticle exist as subtypes but should be avoided: they reduce AI citation probability because AI systems apply credibility discounts to declared advertising and satirical content. A key implementation nuance: do not use NewsArticle for content that is not genuinely time-sensitive news, even if your domain publishes news. Mismatched schema types signal inconsistency to AI parsers and can reduce authority scores.
- TechArticle is the correct subtype for technical guides, tutorials, and product documentation
- NewsArticle triggers freshness weighting—use only for genuine time-sensitive news content
- Article is the safe default for opinion, analysis, case study, and general informational content
- Avoid AdvertorialArticle and SatiricalArticle subtypes—they trigger credibility discounts
- Consistent subtype usage across your domain builds schema type authority signals
Complete Article Schema Implementation with All Authority Fields
Here is production-ready Article JSON-LD with all authority-signaling fields: {"@context": "https://schema.org", "@type": "TechArticle", "headline": "Article Schema for AI SEO: Signal Authority to ChatGPT and Google", "description": "Learn how Article schema markup establishes the authorship and provenance context AI systems require before citing your content.", "keywords": "Article schema, AI SEO, structured data, JSON-LD", "wordCount": 2100, "author": {"@type": "Person", "name": "Author Name", "url": "https://yoursite.com/authors/name", "sameAs": ["https://www.linkedin.com/in/authorname", "https://orcid.org/0000-0000-0000-0000"], "jobTitle": "Head of SEO", "affiliation": {"@type": "Organization", "name": "Your Company", "url": "https://yoursite.com"}}, "publisher": {"@type": "Organization", "name": "Your Company", "url": "https://yoursite.com", "logo": {"@type": "ImageObject", "url": "https://yoursite.com/logo.png", "width": 600, "height": 60}}, "datePublished": "2026-05-01T09:00:00+00:00", "dateModified": "2026-05-20T14:00:00+00:00", "mainEntityOfPage": {"@type": "WebPage", "@id": "https://yoursite.com/article-slug"}, "image": {"@type": "ImageObject", "url": "https://yoursite.com/images/article-og.jpg", "width": 1200, "height": 630}, "articleSection": "AI SEO", "inLanguage": "en-US"}. Fields most implementations omit: wordCount (signals content depth to AI systems), keywords (explicit topic signals), articleSection (maps to site taxonomy), inLanguage (important for multilingual AI systems), and the ISO 8601 timestamp format for datePublished and dateModified (the time component enables more precise recency scoring).
- Use ISO 8601 datetime format with timezone for datePublished and dateModified
- Include wordCount to signal content depth—AI systems weight longer authoritative documents higher
- keywords field provides explicit topic signals independent of body text analysis
- articleSection maps your content to site taxonomy, strengthening topical authority
- The image field is required for Google rich results and boosts visual AI systems' confidence
Author Entity Optimization: The Critical Authority Signal
The author field in Article schema is one of the most underoptimized elements in most implementations. Most sites set author to a plain string ('John Smith') or a minimal Person node with only a name. This is a missed authority signal. AI systems increasingly implement E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) evaluations at the author-entity level, not just the domain level. A complete Person node for the author creates a resolvable entity that AI systems can cross-reference across documents. When John Smith has a Person schema node on your site with sameAs links to his LinkedIn profile, his ORCID identifier, his Twitter/X profile, and his Wikipedia page (if applicable), AI systems can build a knowledge graph node for John Smith as a named expert. When that expert's name appears on multiple authoritative documents about the same topic, the AI's confidence in citing those documents increases. The affiliation field within the Person node is equally important: it creates a machine-readable link between the author and the publishing organization, strengthening the organization's topical authority in that domain. For sites with multiple authors, create a dedicated author profile page for each author with Organization schema linking back from each author page. This author-organization graph structure is one of the clearest E-E-A-T signals available in structured data.
- Use a complete Person node for author—never a plain text string
- Include sameAs links to LinkedIn, ORCID, Twitter, and Wikipedia for named experts
- Add jobTitle and affiliation fields to create the author-organization authority graph
- Create dedicated author profile pages with consistent Person schema across all author pages
- Cross-link author pages to their articles via the author property for entity graph coherence
Monitoring Article Schema Performance in AI Systems
Tracking Article schema's impact on AI citations requires a multi-platform monitoring approach. Google Search Console now includes an AI Overviews report that shows which queries triggered AI Overview impressions for your pages—cross-reference this with pages that have Article schema versus those that do not. For third-party AI systems, use Semrush's AI Toolkit, BrightEdge's Share of Voice for AI, or Authoritas's AI visibility tracking to monitor branded and non-branded query appearances. Establish a baseline before making schema changes, then measure at 30, 60, and 90 days post-implementation. Key metrics to track: AI Overview impression share (GSC), AI citation frequency by query cluster, the specific phrasing AI systems use when citing your content (indicates which schema fields are being parsed), and backlinks from AI-adjacent content (pages that aggregate AI answers often link to cited sources). For Article schema specifically, monitor the author entity performance: search for your authors' names in AI systems and observe whether their affiliation and expertise are correctly attributed. Incorrect attribution indicates schema parsing errors that should be corrected. The feedback loop between schema implementation, AI citation monitoring, and iterative schema improvement is the operational core of an AI-first SEO program.
- Use Google Search Console's AI Overviews report to baseline Article schema impact
- Track AI citation frequency with Semrush AI Toolkit or BrightEdge AI Share of Voice
- Monitor author entity attribution in AI responses to verify Person schema is being parsed
- Measure at 30, 60, and 90 days post-implementation for statistical confidence
- Create a schema performance dashboard tracking AI impression share by content cluster
Article schema is not glamorous—it lacks the visible SERP rich results of FAQPage or HowTo schema—but it is the most foundational structured data investment you can make for AI citation authority. By declaring authorship, publication dates, organizational affiliation, and topical context in machine-readable format, you are building the provenance record that AI systems use to decide which sources are worth citing. The author entity optimization layer—complete Person nodes with sameAs links and affiliation graphs—is a particularly high-leverage tactic that most SEOs have not yet implemented. Do it now, before it becomes table stakes.
Frequently Asked Questions
Is Article schema required for Google AI Overview citations?
Article schema is not a strict requirement, but it is one of the strongest available signals for AI Overview citation probability. Google's AI systems can infer authorship and publication dates from unstructured content, but explicit Article schema with complete author, publisher, and date fields significantly reduces inference errors and increases citation confidence. Aleyda Solis's 2025 analysis found Article schema on cited pages at significantly higher rates than on non-cited equivalent pages.
Should I use Article or WebPage schema for my homepage and landing pages?
Use WebPage (or its subtype WebSite) for your homepage and landing pages, not Article schema. Article schema is appropriate for editorial content—blog posts, guides, research, news. Using Article schema on non-editorial pages creates a schema mismatch that can confuse AI parsers and reduce citation quality. For the homepage, combine WebSite schema (for sitelinks search box) with Organization schema. For landing pages, use WebPage with appropriate BreadcrumbList markup.
How often should I update dateModified in Article schema?
Update dateModified every time you make a substantive change to the article's content—adding new sections, updating statistics, revising recommendations, or correcting information. Do not update dateModified for trivial changes like typo fixes or formatting adjustments, as this can signal to AI systems that you are artificially refreshing content without genuine updates. Substantive updates with accurate dateModified timestamps are a legitimate and effective freshness signal for AI recency scoring.