FAQ schema: basics you need to know

Practical guide to FAQ schema: what it is, how to add JSON-LD to your pages, testing steps, and common mistakes to avoid.

Michael

Published 17 Februari 2026

What this guide delivers

This post explains what FAQ schema (FAQPage structured data) does, shows a copy-paste JSON‑LD example, lists implementation steps and common mistakes, and gives practical testing and troubleshooting guidance you can use on your site today.

What is FAQ schema and why it matters

FAQ schema (the FAQPage type defined by schema.org) is structured data you add to a page that contains questions and their answers. It signals to search engines that a page includes Q&A content so they can consider showing that content as enhanced results — for example, an expanded question list directly in the SERP or in voice assistants. Structured data does not guarantee a rich result; it helps search engines understand page content and its intent so they can decide whether to surface it in special features.

Keep three technical distinctions in mind: crawling (discovery and fetching), indexing (what Google stores), and ranking (how results are ordered). FAQ schema affects how search engines understand and may display your content but it does not itself change how Google ranks pages.

How to implement FAQ schema (step-by-step)

Use JSON‑LD inside a script element in the page head or body. Only mark up content that is visible to users on that page (do not add markup for content that only appears to crawlers). Below is a minimal, valid JSON‑LD example you can adapt — replace the question and answer strings with your page content.

Implementation checklist

Only mark up content that appears on the page to real users.
Keep questions concise and answers clear — long-winded or irrelevant answers reduce usefulness.
Avoid repeating the same Q&A across many pages; prefer a single authoritative page or consolidate similar questions.
If a Q&A is paid/promotional, do not try to hide that fact — structured data must reflect visible page content and editorial context.

Common mistakes and best practices

Below are recurring issues seen in implementations and how to avoid them.

Marking up content not visible to users

Do not add FAQPage markup for content that appears only in structured data or is injected for crawlers. The marked-up Q&As must be present in the page HTML and visible when the page is rendered for users.

Overusing repetitive or low-value Q&As

Google's documentation and guidance discourage using structured data to markup large volumes of repetitive or thin Q&As solely to gain SERP real estate. Focus on useful, unique questions that help users.

Testing and troubleshooting

After adding markup, validate it with tools and understand how search engines see the page. Use these steps in order.

Step 1 — Quick validation

Run the page through Google's Rich Results Test: https://search.google.com/test/rich-results. This highlights detected schema types and common errors.
Also check the Schema Markup Validator at https://validator.schema.org to confirm schema.org compliance.

Step 2 — Verify the rendered page

Open the page in a browser, use View Source to confirm the JSON‑LD is present, and use DevTools > Elements to confirm the visible Q&As exist in the rendered DOM.
If your page uses client-side rendering, ensure the markup and content are available to crawlers that fetch the rendered HTML.

Step 3 — Use Search Console for owned pages

For pages you own, use the URL Inspection tool in Google Search Console to check crawl and index status and see how Google last rendered the page. URL Inspection is authoritative for your property; external 'site:' checks are only indicative.

If results don't appear in search: validate markup, confirm the content is indexable, and improve the editorial value of the Q&As. Remember that Google decides whether to show enhanced features based on its quality signals and the query context.

If you need a deeper check on how your page is crawled and rendered, start with the URL Inspection tool in Google Search Console; for broader technical guidance, Read the Technical SEO Guide.

When FAQ schema is not the right choice

FAQ schema is not appropriate when questions are generic, duplicated site-wide, or when the page's primary purpose is not to provide clear questions and answers. In those cases consider using other content structures (help center pages, dedicated knowledge base articles, or in-page anchors) and reserve FAQPage markup for focused pages where Q&A is the main content.

Also remember the broader search landscape in 2026: Google uses the mobile version as its primary basis for crawling and indexing; since July 2024 Googlebot Smartphone is the default crawler. Google also removed traditional cached pages in early 2024, and AI-driven search features such as Search Generative Experience / AI Overviews are now a common part of the SERP. Structured data remains a helpful signal for these features, but it is one of many signals search engines use.

Quick reference: do and don't

Do: Mark up only visible Q&As; use JSON‑LD; test with Rich Results Test and Schema Markup Validator.
Do: Keep answers useful and concise; prefer one authoritative location for similar questions.
Don't: Add FAQ markup for hidden content or for pages that exist only to display many thin Q&As.
Don't: Assume markup guarantees a rich result — search engines decide whether to use it.

FAQ: common questions about FAQ schema

Can I use FAQ schema on a category or product page?

Yes, if the primary purpose of that page is to present clear, user-visible questions and answers relevant to the page topic. Avoid adding Q&As that are unrelated to the page or duplicated across many similar pages.

Will adding FAQ schema improve rankings?

Structured data itself is a signal that helps search engines understand content and whether to show enhanced results. It does not directly change how pages are ranked, though better presentation in the SERP can improve click-through rates when search engines choose to use your markup.

How do I know if Google used my FAQ markup?

Use Rich Results Test to confirm markup detection and Search Console's URL Inspection for pages you own to see how Google rendered the page. Public 'site:' queries can indicate visibility but are not a definitive indexation check.

What if my FAQ markup used to show and now doesn't?

Re-validate your markup, confirm the content is still visible and indexable, and review whether the Q&As may be considered repetitive or low value. If the page changed or the site experienced indexing issues, investigate crawl and render status with URL Inspection.