Every week I audit websites for clients across Kerala — IT companies in Technopark, ayurveda centres in Thrissur, law firms in Ernakulam — and the single most consistent structured data mistake I find is misapplied schema. Either they have FAQPage markup on a page with no actual questions, or they have a 12-step cooking process tagged as an Article, or they have no schema at all on a page that Google would happily render as a rich result. The choice between FAQPage, HowTo, and Article schema is not arbitrary. Each type sends a specific signal about what your content does and how Google should display it — and in 2026, that signal also influences whether AI Overviews pull from your page or skip it.
This guide gives you a clear decision framework. By the end, you will know exactly which schema type to reach for, what it does under the hood, and what mistakes to avoid with each implementation.
What Schema Markup Actually Does
Schema markup in JSON-LD format is structured metadata — a machine-readable layer that sits in your page's <head> and tells Google's crawlers what your content means, not just what it says. Google does not need schema to understand your content; its natural language processing is capable enough without it. What schema does is confirm Google's interpretation and unlock specific display formats that would otherwise be unavailable.
Think of it as a formal declaration. When you add "@type": "FAQPage", you are telling Google: "This page's primary value is a list of questions with definitive answers." Google responds by potentially surfacing those questions in an expandable rich result below your blue link, or by flagging your answers as candidate sources for AI Overviews. Without the schema, Google might still infer this — but with the schema, you remove ambiguity.
In 2026, the stakes are higher because Google's AI Overviews use structured data as one of several eligibility signals. A page with well-formed FAQPage schema on genuinely question-answering content is more likely to be extracted into an AI Overview than an identical page without it. This is not a guarantee — content quality, domain authority, and topical relevance still matter more — but schema is a meaningful accelerant.
FAQPage Schema: What It Signals and When to Use It
FAQPage schema signals that a page's primary purpose is answering a set of discrete questions. Each question must have one definitive answer — not a discussion, not a redirect to another page, but an answer that could stand alone if Google extracted it.
What Google does with FAQPage
When FAQPage validates correctly and the content meets Google's quality bar, you become eligible for FAQ rich results: expandable question-answer pairs displayed directly below your search result. This doubles or triples your vertical space in the SERP, which increases click-through rate even if your ranking position stays the same. For AI Overviews, FAQPage-tagged content is treated as pre-segmented answer units — Google's extraction pipeline can pull individual Q&A pairs without needing to parse narrative prose.
When to use FAQPage
- Service pages where customers have predictable, specific questions ("How long does a website audit take?", "Do you serve clients outside Kerala?")
- Dedicated FAQ sections at the bottom of blog posts, where you answer follow-on questions that the main article does not address
- Product pages where users ask about compatibility, shipping, or warranty before purchasing
When NOT to use FAQPage
- Never mark up questions that are answered with "Contact us for details" — the answer must be substantive in the markup itself
- Do not apply FAQPage to a page where questions are rhetorical section headers with essay-length discussion underneath, rather than actual question-answer pairs
- Avoid using FAQPage on multiple pages with the same questions and answers — Google's March 2026 spam update explicitly targets duplicate FAQPage schema across a site
FAQPage JSON-LD example
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How long does an SEO audit take?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A full technical and content SEO audit for a 50-page website typically takes 5-7 business days. This includes crawl analysis using Screaming Frog, manual review of top-20 pages, Core Web Vitals assessment, and a written report with prioritised recommendations."
}
}
]
}HowTo Schema: What It Signals and When to Use It
HowTo schema signals that your content describes a process — a sequence of steps that, when followed in order, produces a specific outcome. It is the most semantically precise of the three schema types, and it is also the most frequently misapplied.
What Google does with HowTo
On mobile devices, validated HowTo schema can trigger step-by-step rich results where each step expands with its image and description. Google restricted HowTo rich results to mobile only in September 2023, reasoning that the format serves users who are physically following instructions on a small screen. However, HowTo schema still influences AI Overview eligibility for how-to queries, even without the visual rich result. Google's systems understand that a page tagged HowTo contains a process, which makes it easier to extract as an answer to "how do I…" queries.
When to use HowTo
- Tutorial posts with numbered steps where each step has a clear action ("Click Settings", "Enter your API key", "Save changes")
- Recipe pages (though Recipe schema is more specific and preferred for food content)
- Technical guides for developers, IT administrators, or tradespeople — any domain where steps must be done in sequence to achieve a result
When NOT to use HowTo
- Do not apply HowTo to content that is really just a list of tips or best practices with no defined sequence — use Article instead
- Avoid HowTo on pages where the "steps" are actually sections of analysis or opinion
- Never mark up a process you cannot complete in under 30 steps — Google's rich result renderer handles brevity better than exhaustive processes
HowTo JSON-LD example
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to Verify Your Google Business Profile in Kochi",
"step": [
{
"@type": "HowToStep",
"position": 1,
"name": "Sign in to Google Business Profile Manager",
"text": "Go to business.google.com and sign in with the Google account associated with your business listing."
},
{
"@type": "HowToStep",
"position": 2,
"name": "Select your business location",
"text": "From the dashboard, click on the business you want to verify. If it does not appear, search by name."
},
{
"@type": "HowToStep",
"position": 3,
"name": "Choose a verification method",
"text": "Select from postcard, phone, email, or video verification. Postcard takes 5-14 days to arrive at your registered Kochi address."
}
]
}Article Schema: What It Signals and When to Use It
Article schema is the most broadly applicable of the three. It signals that your page is an editorial piece of content — written by a human author, published at a specific point in time, and representing a reasoned point of view or analysis on a topic. Unlike FAQPage and HowTo, Article schema does not describe the format of your content; it describes the nature of it.
What Google does with Article
Article schema makes pages eligible for the Top Stories carousel (critical for news publishers), enhances how your content appears in Google Discover, and gives Google's AI systems high-confidence signals that your content is a credible, attributed editorial piece. The datePublished, dateModified, and author fields are particularly important — they help Google assess freshness and E-E-A-T signals. An Article page with a named author who has a verifiable web presence is treated more favourably for AI Overview citations than an anonymous or authorless piece.
Google supports three Article subtypes: Article (general), NewsArticle (time-sensitive news), and BlogPosting (blog entries). For most consultancy and service business blogs in Kerala, BlogPosting is the most accurate subtype, though Article works fine.
When to use Article
- Long-form blog posts, guides, opinion pieces, and analysis content
- Any page where the content is primarily narrative prose rather than Q&A or step sequences
- News and announcements from your organisation
When NOT to use Article
- Do not apply Article schema to service or product pages — these are not editorial content and may confuse Google's classification
- Avoid Article on homepage content, which serves multiple purposes rather than one editorial topic
Article JSON-LD example
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "How Kerala IT Companies Can Rank for AI Overview Queries",
"datePublished": "2026-01-17T09:00:00+05:30",
"dateModified": "2026-01-24T09:00:00+05:30",
"author": {
"@type": "Person",
"name": "Rajesh R Nair",
"url": "https://rajeshrnair.com"
},
"publisher": {
"@type": "Organization",
"name": "Rajesh R Nair",
"logo": {
"@type": "ImageObject",
"url": "https://rajeshrnair.com/rajesh-512.png"
}
},
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://rajeshrnair.com/blog/aeo/aeo-strategy/example.html"
}
}The Decision Flowchart: Which Schema Type to Choose
Walk through these questions in order for any page you are considering marking up:
Question 1: Does your page describe a sequence of steps that users must follow to achieve a specific outcome?
Yes → Use HowTo schema. If it also has a FAQ section, add FAQPage as a second schema block.
No → Continue to Question 2.
Question 2: Does your page primarily consist of questions with definitive answers?
Yes → Use FAQPage schema. If the page is also a blog post, layer in Article schema for the overall content.
No → Continue to Question 3.
Question 3: Is your page an editorial piece — a blog post, analysis, guide, or opinion piece — with a named author?
Yes → Use Article (or BlogPosting) schema.
No → Your page may be better served by other schema types: LocalBusiness, Product, Service, or WebPage.
The key insight is that these types are not mutually exclusive. A blog post explaining how to set up Google Search Console can carry both Article schema (describing the overall piece) and HowTo schema (describing the setup process). A service page with a FAQ section at the bottom can carry both Service schema and FAQPage schema. Google handles multiple schema types on a single page without issue, as long as each schema accurately reflects content that exists on the page.
How Each Schema Type Affects AI Overview Eligibility
Google's AI Overviews pull from pages that answer queries clearly and credibly. Each schema type influences this in a slightly different way.
FAQPage schema pre-segments your content into extraction-ready units. AI systems do not have to parse paragraphs to find the answer — the schema points directly to it. This gives FAQPage-tagged content an extraction efficiency advantage, particularly for question queries that begin with "what is", "how much", "is [X] worth it", and similar forms.
HowTo schema helps AI Overviews identify instructional content reliably. When a user asks "how do I [task]", Google's AI prioritises sources with clear step-by-step structure. HowTo schema is a strong signal that your content has this structure, even if the AI Overview does not reproduce your steps verbatim.
Article schema contributes to AI Overview eligibility more indirectly. The author and datePublished fields support E-E-A-T assessment. A page from a named, attributable author on a real publication date is more trustworthy than anonymous content. For AI Overviews involving contested or nuanced topics — legal questions, health topics, financial decisions — author credibility signals from Article schema become particularly important.
Common Implementation Errors and How to Avoid Them
After reviewing structured data for several dozen Kerala businesses over the past two years, these are the errors I encounter most often:
Schema-content mismatch: The most common and most penalisable error. FAQPage markup on a page where the "questions" are actually section headers with no corresponding answers in the markup. Google's spam detection since the March 2026 update specifically targets schema that does not match visible page content. Every property in your JSON-LD must correspond to something a user can actually read on the page.
Identical FAQPage schemas across pages: An ayurveda clinic in Thrissur had the same seven FAQ questions and verbatim answers on all 14 of their service pages. After the March 2026 update, all 14 pages lost their FAQ rich results within two weeks. Unique FAQ content per page is not optional — it is a spam policy requirement.
Missing required properties: HowTo schema without step elements, or Article schema without datePublished. Use Google's Rich Results Test to validate — it surfaces missing required properties explicitly.
JavaScript-rendered schema: If your JSON-LD is injected by a JavaScript framework after page load, Googlebot may not see it during the first crawl pass. Place JSON-LD directly in the <head> of your HTML, not in dynamically loaded components. This is a common problem with React and Vue-based sites where schema is added through a helmet or meta library without server-side rendering.
Validation Tools You Should Actually Use
Three tools cover everything you need for schema validation:
Google Rich Results Test (search.google.com/test/rich-results): The authoritative source for whether your schema makes you eligible for rich results. Paste a URL or raw HTML. It shows detected schema types, eligible rich features, and any errors or warnings. Run this after every schema implementation.
Schema.org Validator (validator.schema.org): Validates your JSON-LD against the full schema.org specification, not just Google's subset. Useful for catching property-name typos and unsupported values that the Rich Results Test might not flag.
Screaming Frog SEO Spider with the structured data report enabled: For site-wide audits across hundreds of pages. Configure it to extract JSON-LD and flag pages with schema errors, duplicate schemas, or schema-content mismatches at scale. Indispensable for agencies managing multiple client sites.
Frequently Asked Questions
Can I use FAQPage schema and Article schema on the same page?
Yes, you can combine FAQPage schema with Article schema on the same page, and this is often a good practice. The Article schema describes the content as a whole — its headline, author, and publication date — while FAQPage describes specific question-and-answer pairs within that content. Google treats these as complementary, not conflicting. Just ensure every question in your FAQPage schema actually appears as visible text on the page. Google's spam guidelines require that schema markup accurately represents what users can read.
Why did Google remove HowTo rich results from most desktop searches?
In September 2023, Google narrowed HowTo rich results to show primarily on mobile devices, citing a shift in how users consume instructional content. On mobile, step-by-step expansions improve the experience because users are often following instructions physically. On desktop, users generally prefer to read the full page. However, HowTo schema still has value beyond the visual rich result — it helps Google's AI understand your content's instructional structure, which influences AI Overview citations for how-to queries. Keep implementing it for content that genuinely describes a process with discrete steps.
What validation tool should I use to check my JSON-LD schema?
Use Google's Rich Results Test (search.google.com/test/rich-results) as your primary validation tool — it shows exactly which schema types Google detected and whether they qualify for rich results. For deeper structural validation against schema.org specifications, use Schema.org's own validator at validator.schema.org. A third option is Merkle's Schema Markup Validator, which provides a more readable property breakdown. Run all three for important pages. Note that the Rich Results Test reflects what Googlebot sees, not just what your browser renders, so it catches render-dependent JavaScript issues that browser DevTools miss.
Does adding Article schema improve rankings directly?
Article schema does not directly improve rankings in the way backlinks or content quality do. Its primary benefit is eligibility for rich features — Top Stories carousel, article sightlinks, and enhanced display in Google Discover. For AI Overview eligibility, Article schema helps Google's systems confidently classify your content as a credible editorial piece. Indian news publications and content-heavy consultancy websites that implemented Article schema with proper author and datePublished fields have seen measurably higher Discover impressions in Google Search Console, even without ranking position changes.