Schema MarkupPublished: January 17, 2025• 10 min read

FAQ Schema Markup Guide 2026: JSON-LD Examples

Learn how to create, validate, and maintain FAQPage JSON-LD in 2026, after Google retired FAQ rich results. Includes working examples and common fixes.

Written by Chris Drinkard

14 years in hospitality management

5 years helping independent hotels grow their online presence. Passionate about AI, search, and digital strategy.

2026 update: Google stopped showing FAQ rich results on May 7, 2026. Keep FAQPage markup only when it accurately describes useful Q&A that readers can see; do not expect an expanded search result or a direct CTR lift from the markup.

What Is FAQ Schema Markup?

FAQ schema (FAQPage structured data) identifies a list of publisher-authored questions and answers on a webpage. It gives Schema.org-aware systems an explicit description of the Q&A, but it no longer creates an FAQ rich result in Google Search.

What changed in 2026:

Google no longer adds expandable FAQ questions below a result
FAQPage is no longer reported as a Google Search appearance
The markup does not improve rankings by itself
The visible questions and answers can still be useful search content
Schema.org-aware tools can still parse valid FAQPage markup

How FAQ Schema Works

You add JSON-LD structured data to your HTML that tells search engines:

@type: "FAQPage" (identifies the page type)
mainEntity: Array of Question objects
Each Question contains:
- name – The question text
- acceptedAnswer – The answer text (with HTML allowed)

A parser can use those properties to distinguish the question text from its accepted answer without inferring the structure from page layout alone.

Benefits of FAQ Schema

1. Machine-Readable Q&A

FAQPage gives tools that understand Schema.org a predictable map of each question and its official answer. This is clearer than relying on headings, accordions, and surrounding prose alone.

2. Easier Content Maintenance

A consistent question-and-answer model makes it easier to audit missing answers, duplicated questions, and markup that no longer matches the visible page.

3. Better Scannability for Readers

The useful part is still the content. Clear questions and direct answers help visitors find details quickly, whether or not any machine reads the markup.

4. Reusable Structured Content

The same well-maintained Q&A can support help centers, product education, internal search, and other systems that consume structured content.

5. Better User Experience

Structuring content as FAQs improves readability and helps visitors find information quickly. Users prefer scannable content with clear questions and concise answers.

Set the right expectation: measure whether the FAQ content earns impressions, clicks, engagement, or citations. Do not attribute a traffic change to FAQPage markup without a controlled test—the markup has no dedicated Google search treatment now.

When to Use FAQ Schema

FAQ schema works best on pages that genuinely answer common questions. Use it strategically, not on every page.

✅ Good Use Cases

Blog posts: Add 3-5 FAQs at the end of educational content
Product pages: Answer common questions about features, shipping, returns
Service pages: Address pricing, process, and qualification questions
Support/Help articles: Official documentation with Q&A format
Dedicated FAQ pages: Comprehensive question lists
Location/Contact pages: Hours, parking, appointment questions

❌ Avoid FAQ Schema On:

Forum/Community Pages: Use QAPage schema instead when multiple users provide answers (e.g., Stack Overflow, Reddit threads).

Advertising/Marketing Content: Google prohibits FAQ schema for promotional content, ads, or offensive material.

Hidden FAQs: Questions and answers must be visible on the page. Do not mark up content hidden behind tabs or modals (though accordions are OK).

Duplicate Questions: Each question must be unique on the page. Do not repeat questions with slight variations.

How to Implement FAQ Schema

Follow these steps to add FAQ schema to your pages:

Step 1: Create Your FAQ Content

Write 3-10 questions your target audience actually searches for. Use these sources:

Google "People Also Ask" boxes for your target keywords
Google Search Console – Search queries that bring traffic
Customer support tickets – Questions customers frequently ask
Competitor FAQ pages – See what others cover
Reddit, Quora, forums – Real user questions

Step 2: Add FAQ HTML to Your Page

Structure your FAQs semantically in HTML:

<section id="faqs">
  <h2>Frequently Asked Questions</h2>
  
  <div itemscope itemprop="mainEntity" itemtype="https://schema.org/Question">
    <h3 itemprop="name">What is FAQ schema markup?</h3>
    <div itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer">
      <p itemprop="text">FAQ schema is structured data that tells search engines which content represents frequently asked questions...</p>
    </div>
  </div>

  <!-- Repeat for each question -->
</section>

Step 3: Add JSON-LD Schema Markup

Insert this JSON-LD code in your <head> or before </body>:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is FAQ schema markup?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>FAQ schema is structured data that identifies publisher-authored questions and answers in a machine-readable format.</p>"
      }
    },
    {
      "@type": "Question",
      "name": "Does FAQ schema help SEO rankings?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>FAQ schema is not a ranking factor and Google no longer shows FAQ rich results. Its value is making visible Q&amp;A machine-readable.</p>"
      }
    },
    {
      "@type": "Question",
      "name": "How many FAQs should I add to a page?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Add only the FAQs needed to answer genuine user questions. There is no rich-result minimum.</p>"
      }
    }
  ]
}
</script>

Important: The text in your JSON-LD must match the visible content on your page. Misleading or hidden structured data can violate Google's general structured data guidelines even when the JSON is technically valid.

Step 4: Escape HTML in Answer Text

You can include HTML formatting in answers, but must escape it:

"text": "<p>FAQ schema uses <strong>JSON-LD</strong> format. You can include <a href='https://example.com'>links</a>, <ul><li>bullet lists</li></ul>, and <br> line breaks.</p>"

Allowed HTML tags: <h1>-<h6>, <p>, <br>, <ul>, <ol>, <li>, <a>, <strong>, <em>, <div>

Real FAQ Schema Examples

Example 1: Blog Post FAQ

For a blog post about Core Web Vitals:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What are the three Core Web Vitals metrics?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>The three Core Web Vitals are: <strong>Largest Contentful Paint (LCP)</strong> measuring loading performance (target: under 2.5s), <strong>First Input Delay (FID)</strong> measuring interactivity (target: under 100ms), and <strong>Cumulative Layout Shift (CLS)</strong> measuring visual stability (target: under 0.1).</p>"
      }
    },
    {
      "@type": "Question",
      "name": "Are Core Web Vitals a ranking factor?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes, Google announced in June 2021 that Core Web Vitals are official ranking factors as part of the Page Experience update. Sites meeting all three thresholds have a competitive advantage, though content relevance remains the primary ranking factor.</p>"
      }
    }
  ]
}
</script>

Example 2: Product Page FAQ

For an SEO audit tool product page:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Is Rankture's SEO audit tool free?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes, we offer a free SEO audit that analyzes 10+ pages of your website. You can run audits without creating an account. Paid plans start at $29/month and include deeper analysis, competitor comparisons, and priority support.</p>"
      }
    },
    {
      "@type": "Question",
      "name": "How long does an SEO audit take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Most audits complete in 60-90 seconds. We analyze your site's technical SEO, on-page optimization, Core Web Vitals, and content quality. Larger sites (100+ pages) may take 2-3 minutes.</p>"
      }
    },
    {
      "@type": "Question",
      "name": "What does the SEO audit check?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Our audit performs 20+ checks including: <ul><li>Page speed and Core Web Vitals</li><li>Mobile responsiveness</li><li>Meta tags and title optimization</li><li>Schema markup validation</li><li>Broken links and redirects</li><li>HTTPS security</li><li>Image optimization</li></ul></p>"
      }
    }
  ]
}
</script>

Example 3: Service Page FAQ

For a local SEO service page:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is local SEO?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Local SEO optimizes your online presence to attract customers in specific geographic areas. It includes optimizing Google Business Profile, building local citations, earning reviews, and creating location-specific content to rank in Google's Map Pack and local search results.</p>"
      }
    },
    {
      "@type": "Question",
      "name": "How much does local SEO cost?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Local SEO services typically range from $500-$2,000/month depending on competition and scope. Our local SEO audit tool is free and identifies opportunities. For businesses serving one city, expect $500-$1,000/month. Multi-location businesses may need $1,500-$3,000/month.</p>"
      }
    }
  ]
}
</script>

Testing & Validating FAQ Schema

Always test your FAQ schema before publishing to catch errors early.

1. A FAQPage-aware validator

Google's Rich Results Test no longer helps here. Google retired FAQ rich results in May 2026 and removed FAQPage documentation that June, so the test will not report on your markup at all — a valid FAQPage simply shows as nothing detected. You need a validator that checks the markup itself rather than eligibility for a search feature that no longer exists.

Our FAQ schema checkervalidates FAQPage JSON-LD directly in your browser. Paste your markup and it will:

Confirm the root @type is FAQPage
Verify mainEntity is a valid array of Question items
Check each question has acceptedAnswer with @type: Answer
Flag missing name or text properties
Catch JSON-LD syntax errors and unescaped characters

✅ Success Indicators:

Root type resolves as FAQPage
Every question has a non-empty accepted answer
No JSON-LD parse errors
Answers contain the same text a reader sees on the page

2. Schema Markup Validator

Use validator.schema.org for detailed technical validation:

Paste your JSON-LD code
Click "Run Test"
Check for errors, warnings, or notices
Verify all required properties are present

3. Google Search Console

After publishing, use URL Inspection to confirm Google can access the page. FAQPage no longer has a dedicated enhancement report:

Inspect the published URL
Confirm the page is indexable and the live test can fetch it
Use your FAQPage-aware validator to test the markup itself
Request re-indexing after meaningful content changes when appropriate

Note: Valid FAQPage markup will not trigger a Google FAQ rich result. Treat validation as a data-quality check, not a search-feature eligibility check.

FAQ Schema Best Practices

1. Write for Humans First

Your FAQs should genuinely help users, not just manipulate search results. Write natural questions people actually ask and provide complete, helpful answers.

2. Keep Answers Concise

Aim for 40-300 words per answer. Too short (1 sentence) looks thin; too long (500+ words) is overwhelming. Focus on directly answering the question.

3. Use Target Keywords Naturally

Include your target keywords in questions and answers, but don't force it. Questions should mirror how real people search (e.g., "How do I optimize for Core Web Vitals?" not "Core Web Vitals optimization methodology").

4. Match Content to Search Intent

Answer questions relevant to your page's main topic. On a product page, answer product-related questions. On a how-to guide, answer implementation questions.

5. Update FAQs Regularly

Review your FAQs quarterly and update answers as:

Your product/service changes
Industry best practices evolve
New common questions emerge
Search Console shows new relevant queries

6. Cross-Link Related Content

Link from FAQ answers to related blog posts or service pages for more details. This improves internal linking and helps users find more valuable content.

7. Maintain Consistent Schema

If you use FAQ schema on one page, consider adding it to similar pages. Consistency signals to Google that your site provides comprehensive information.

Pro Tip: Run your page through the FAQ schema checker to confirm your FAQPage markup parses cleanly, or the full schema validator if you want every structured data type on the page checked at once.

Common FAQ Schema Mistakes to Avoid

❌ Marking Up Non-FAQ Content

Mistake: Using FAQ schema for testimonials, product features, or blog sections that aren't questions.

Fix: Only mark up actual question-answer pairs. For testimonials, use Review schema. For features, use ItemList or HowTo schema.

❌ Hiding FAQ Content

Mistake: Marking up FAQs that are hidden behind tabs, modals, or requiring login.

Fix: FAQs must be visible on page load. Accordions that expand on click are OK, but content must be in the DOM (not lazy-loaded).

❌ Duplicate Questions Across Pages

Mistake: Using identical FAQ schema on multiple pages (e.g., copying same 5 FAQs to every blog post).

Fix: Tailor FAQs to each page. Use unique questions relevant to that specific content. Duplication may cause Google to ignore some instances.

❌ Schema Doesn't Match Visible Content

Mistake: JSON-LD questions/answers differ from what's visible on the page.

Fix: Schema must accurately represent visible content. Google compares markup to HTML and may penalize mismatches.

❌ JSON Syntax Errors

Mistake: Missing commas, brackets, or quotes breaking JSON parsing.

Fix: Validate JSON in a linter (jsonlint.com) before publishing. One syntax error breaks all schema on the page.

❌ Using FAQ Schema for QA Forums

Mistake: Applying FAQPage schema to community discussions where multiple users answer questions.

Fix: Use QAPage schema for forums. FAQPage is only for content authored by your organization with a single accepted answer.

❌ Too Few or Too Many FAQs

Mistake: Adding just 1 FAQ or stuffing 50+ FAQs on a page.

Fix: Use only genuine, useful questions. Three to ten is often readable, but there is no schema or rich-result minimum.

Monitoring FAQ Schema Performance

Track these metrics to measure FAQ schema success:

1. Query Visibility

Measure whether the visible FAQ content matches useful searches:

Review queries and impressions for the page in Search Console
Look for question-form searches that match an on-page answer
Improve weak answers instead of adding repetitive markup

2. Click-Through Rate (CTR)

Compare CTR after improving the visible Q&A, while accounting for ranking changes:

Google Search Console → Performance → Compare date ranges
Filter by specific pages with FAQ schema
Compare pages and periods at similar average positions

3. Impressions & Clicks

Useful question-and-answer content can earn visibility for related queries:

Track impression growth for pages with FAQ schema
Monitor clicks and average position together
Identify new long-tail queries ranking due to FAQ content

4. Schema Errors

Regularly check for schema issues:

Run the FAQ schema checker after content or template changes
Review syntax errors and missing required properties
Confirm the markup still matches the visible answers

5. User Engagement

FAQ-driven traffic may have different engagement patterns:

Track whether readers expand or navigate from FAQ sections
Monitor engaged time and exits around the Q&A content
Track conversions without assuming the schema caused them

Monitoring Schedule: Check FAQ schema performance weekly for the first month, then monthly ongoing. Use Google Search Console and analytics to track CTR, impressions, and engagement. Run free SEO audits monthly to catch schema errors early.

FAQs About FAQ Schema

What is FAQ schema markup?

FAQ schema is Schema.org FAQPage structured data that labels questions and their publisher-authored answers in a machine-readable format. Google stopped showing FAQ rich results on May 7, 2026, but valid FAQPage markup can still describe your content to systems that process Schema.org data.

Does FAQ schema help SEO rankings?

FAQ schema is not a Google ranking factor and no longer produces FAQ rich results. Its practical value is semantic clarity: it identifies questions and official answers for systems that use Schema.org data. The visible FAQ content itself can still rank when it is useful and relevant.

How many FAQs should I add to a page?

Use only the number of FAQs needed to answer real user questions. Three to ten is often readable, but there is no rich-result minimum. Avoid padding a page with repetitive questions just to increase the amount of markup.

Can I use FAQ schema on every page?

Use FAQPage only when the page visibly contains a list of questions with answers authored by the publisher. Do not mark up hidden, irrelevant, or promotional content. Use QAPage instead when users can submit multiple answers to one question.

What is the difference between FAQ schema and QAPage schema?

FAQ schema is for pages authored by your organization with official answers (e.g., product pages, help centers). QAPage schema is for community-driven Q&A pages where multiple users provide answers (e.g., Stack Overflow, Reddit). Use FAQ schema for controlled, authoritative content and QAPage schema for user-generated discussions.

How do I test if my FAQ schema works?

Use an FAQPage-aware Schema.org validator. Google removed FAQPage support from the Rich Results Test after retiring the FAQ search feature, so a clean Rich Results Test does not validate FAQPage markup. Check JSON syntax, @type, mainEntity, Question.name, and acceptedAnswer.text.

Validate Your FAQ Schema Now

Check your FAQPage markup against the Schema.org specification in seconds — no sign-up. Or run a full audit to validate every structured data type across your site and see how AI answer engines read your content.

Check Your FAQ Schema Validate All Schema Types