What Is FAQ Schema and How Does It Help SEO

If you have ever typed what is FAQ schema into Google, you have probably seen two very different answers. Older guides promise expandable questions under your search result, extra space on the results page, and a quick lift in clicks. Newer guides say the rich result is gone and the markup is worthless. Both versions are partly out of date, and neither one tells the full story. This guide gives you the current position, based on what Google and schema.org actually say in 2026, and it shows you how to use FAQ schema correctly, with a free tool that does the technical work for you.
FAQ schema is a small block of code that labels the questions and answers already on your page so that search engines can read them as structured data instead of guessing from the layout. It does not write your answers for you, it does not rank your page, and since 7 May 2026 it does not earn you an expandable FAQ display in Google Search. What it still does is make your question and answer content clear, consistent, and easy for machines to parse. That is a modest benefit, and this guide treats it as one. You will learn what FAQ schema is, how it differs from an ordinary FAQ section, how search engines read it, what changed in 2023 and 2026, how to add it by hand and with a generator, how to validate it, and which mistakes cause Google to ignore it.
Use the free FAQ Schema Generator while you read. It builds the exact JSON-LD block this guide describes, in your browser, with no signup and no cost. You can test it with the sample questions it loads in one click, then replace them with your own.
What is FAQ schema
FAQ schema is structured data that describes a list of questions and answers on a web page. Its technical name is FAQPage, a type defined by schema.org, the shared vocabulary that search engines use to understand page content. You add it to a page as a small JSON-LD script block, and it contains a machine readable copy of the questions and answers that visitors already see on the page.
Think of it this way. A human visitor reads a heading, then reads the paragraph under it, and understands that the paragraph answers the heading. A search engine crawler can read the same words, but it has to work out the relationship from headings, spacing, and page layout. FAQ schema removes that guesswork. It says, in a format built for machines, that this text is a question, and that text is the accepted answer to it. The schema.org definition of FAQPage describes exactly that: a web page presenting one or more frequently asked questions, where each question carries a name and an accepted answer.
Three parts make up the markup:
- FAQPage. The type of the whole block. It tells the parser that the page, or the section of the page, is a list of frequently asked questions.
- Question. One item in the list. Each question has a name, which is the question exactly as it appears on the page.
- Answer. The accepted answer to that question. In the code it sits inside acceptedAnswer, and its text holds the answer exactly as it appears on the page.
A minimal example with one question looks like this:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is FAQ schema?",
"acceptedAnswer": {
"@type": "Answer",
"text": "FAQ schema is FAQPage structured data in JSON-LD format. It labels the questions and answers on a page so search engines can read them as data."
}
}
]
}
That block is wrapped in a script tag with the type application/ld+json and placed in the page HTML. Visitors never see it. It sits in the code beside the visible FAQ section, and it mirrors that section word for word. That mirroring is not a suggestion. It is the central rule of FAQ schema, and breaking it is the most common reason the markup gets ignored.
FAQ schema is one type among many. Other types describe products, articles, reviews, events, local businesses, and breadcrumbs. Each type labels a different kind of content. FAQPage is the simplest of them, because a question and an answer need no prices, dates, ratings, or addresses. That simplicity is part of its appeal. It is also the reason so many sites added it without thinking, which is part of why Google later restricted it.
What is FAQ schema, and what is a plain FAQ section
People often use the two phrases as if they mean the same thing. They do not. A plain FAQ section is visible content. FAQ schema is invisible code. You can have one without the other, but only one combination is correct.
A plain FAQ section is a list of questions and answers written in normal page text, usually with each question as a heading and each answer as a paragraph below it. Visitors read it, find the answer they need, and move on. Search engines read it too, as ordinary text. A good FAQ section helps visitors and helps search engines understand the page, with or without any schema at all.
FAQ schema is the code layer on top of that section. It repeats the same questions and answers in JSON-LD so that a machine can extract them without parsing the layout. It adds no words for visitors, changes nothing on screen, and says nothing that the visible text does not already say.
- Visible FAQ section only. Readers see the questions and answers. Search engines read them as ordinary text. This is fine, and it is the foundation everything else depends on.
- FAQ schema only, with no visible FAQ section. The code claims the page answers questions that visitors cannot see. Google treats this as misleading markup, and the schema should not be used this way.
- Visible FAQ section plus matching FAQ schema. Readers see the questions and answers, and machines get a labelled copy of the same content. This is the correct combination.
- Visible FAQ section plus schema that says something different. The code and the page disagree. The markup is unreliable, and a search engine has no reason to trust it.
The practical lesson is simple. Write the FAQ section first, for real people, with real questions and complete answers. Add the schema second, as a faithful copy. If you ever have to choose where to spend your time, spend it on the visible answers. They are what visitors read, what search engines index, and what other sites link to. The schema is a label on that work, not a substitute for it.
There is one related type worth knowing about, because confusing it with FAQPage is a common error. QAPage is for pages where visitors ask the questions and other visitors answer them, such as a forum thread or a community support page. FAQPage is for pages where the site owner writes both the question and the answer. If your page is a help forum, use QAPage. If your page is a service page, a product page, or a blog article with a FAQ section you wrote yourself, use FAQPage.
How search engines read FAQ schema
When a search engine crawls a page, it reads the HTML, including any JSON-LD script blocks. For a FAQPage block, it checks the structure first and the content second. The structure check asks whether the JSON parses, whether the type is FAQPage, whether mainEntity holds a list of Question items, and whether each question has a name and an acceptedAnswer with text. If any of those parts are missing or broken, the block fails and the search engine moves on.
If the structure passes, the search engine compares the marked up questions and answers with the visible text of the page. This is the step most people skip when they think about schema. Google publishes general structured data guidelines that require marked up content to be visible to readers of the page. You can read the principles in Google’s introduction to structured data, and the search gallery shows which types of structured data can still produce a visible search feature. If the questions exist only in the code, or the answers in the code are longer, shorter, or different from the answers on the page, the markup does not match the page, and the search engine is entitled to ignore it.
Passing both checks makes a page eligible for whatever FAQ feature the search engine currently offers. Eligibility is not a promise. Google has always said that valid structured data does not guarantee a rich result, and that it decides whether and how to use the markup. That distinction matters more now than it ever did, because the FAQ rich result itself is gone from Google Search, as the next section explains.
Other search engines and tools read the same schema.org vocabulary. Bing, for example, uses schema.org types in its own understanding of pages, and independent validators parse FAQPage blocks without any connection to Google at all. That is why valid FAQPage markup is still parseable and still meaningful as data, even though Google no longer turns it into a visible result. The code speaks a shared language. Google is only one of the listeners, even if it is the largest one.
It also helps to understand what FAQ schema is not. It is not a ranking factor. Google has never listed structured data as a direct ranking signal, and no FAQPage block will lift a weak page above a strong one. It is not a shortcut to featured snippets, and it is not a way to appear in People Also Ask. Google picks People Also Ask questions and answers from pages across the web on its own, based on the visible content it has indexed. Clear, well written answers on the page are what earn those placements, not the schema block beneath them.
The honest position on FAQ schema in 2026
This is the section older guides get wrong, so read it carefully. FAQ schema has been through three distinct phases, and the current phase is very different from the one most guides still describe.
2019 to 2023: the open period
Google launched FAQ rich results on 8 May 2019, alongside HowTo markup. For several years, any site with valid FAQPage markup could see its questions appear as expandable rows under its search result. The rows took up extra space on the results page, pushed competitors further down, and gave searchers a reason to click. Site owners responded exactly as you would expect. FAQ sections appeared everywhere, including on pages with no genuine questions, and many of them were padded with promotional copy written to win space rather than to help readers.
August 2023: the restriction
In August 2023, Google restricted FAQ rich results almost entirely to well known, authoritative government and health websites. The reason was the misuse described above. Too many publishers had turned FAQ sections into a way to grab search results space, and the quality of the results suffered. For a normal business, a SaaS company, an agency, or an ecommerce store, the expandable FAQ display effectively disappeared at that point. The markup itself stayed valid, and Google said there was no need to remove it, but the visible reward was gone for almost everyone.
7 May 2026: the full removal
On 7 May 2026, Google went further and stopped showing FAQ rich results for every site, including the government and health sites that had kept them after 2023. Google added a deprecation notice on 8 May 2026, and on 15 June 2026 it removed the FAQ structured data documentation from Search Central altogether. Search Engine Journal reported the change in May 2026, and noted that Google planned to drop the FAQ search appearance, the rich result report in Search Console, and support in the Rich Results Test in June 2026, with Search Console API support removed in August 2026. Independent guides that checked the position in October 2026, including the reviews published by Morningstacks and Turksem, confirm the same timeline from Google’s own changelog.
That leaves the position plain. As of November 2026, Google does not show FAQ rich results for any site, and no amount of correct markup brings them back. The task brief for this guide originally described the August 2023 restriction to government and health sites as the current rule. That was accurate until May 2026, and it is no longer accurate. This guide follows the current sources instead, because publishing the old rule would mislead readers who act on it.
What Google says about structured data and AI search
There is a second honest point to make, because many guides now sell FAQ schema as a way into AI Overviews or AI Mode. Google’s own guidance on optimising for generative AI features, published in May 2026, says that structured data is not required for generative AI search, and that there is no special schema.org markup you need to add to appear in AI Overviews or AI Mode. The same guidance recommends the fundamentals that have always mattered: content that is indexed and crawlable, useful text, internal links, good page experience, and structured data that matches visible content. FAQPage markup is not listed as a lever for AI Overview selection, and it should not be sold as one.
None of this means FAQ schema is harmful. Google has said that structured data which is not being used does not cause problems for Search, and that there is no need to proactively remove valid markup from your pages. Existing FAQPage blocks can stay. They cost a few hundred bytes, they parse correctly, and they do no damage. The question is not whether to panic and delete them. The question is whether new FAQ schema is worth your time, and the honest answer is that it is a small, optional finishing step, not a growth tactic.
What FAQ schema can still do for SEO
With the rich result gone, it is fair to ask why anyone should still add FAQ schema. There are real, modest reasons, and they are worth stating without exaggeration.
It makes question and answer content unambiguous
The core value of FAQ schema never depended on the rich result. It labels a question and its answer as a pair, in a standard format, so that any system reading the page does not have to infer the relationship from layout. That clarity helps crawlers, validators, and other tools that consume structured data. It is a small gain, but it is a real one, and it costs almost nothing once the visible FAQ section exists.
It supports good content discipline
Writing schema forces you to write proper questions and answers. Each question needs one answer, each answer needs to be complete on its own, and the code must match the page. That discipline improves the visible FAQ section itself, and the visible section is what visitors read and what search engines index. Many sites find that the process of marking up their FAQs is what finally makes them write FAQs worth reading.
It keeps your pages machine readable for other systems
Google is not the only consumer of schema.org data. Other search engines, assistants, content tools, and research systems parse the same vocabulary. A valid FAQPage block is readable by all of them, even if Google no longer renders it. As AI assistants and answer engines read more of the web, a clearly labelled question and answer section is easier to extract correctly than an unlabelled one. That is not a promise of citations. It is a statement about readability, and readability is the whole point of structured data.
It costs almost nothing when the content already exists
If your page already has a genuine FAQ section, generating the schema takes a few minutes with a tool. The FAQ Schema Generator turns your questions and answers into valid JSON-LD without you writing a line of code. At that cost, keeping valid markup on pages that deserve it is a reasonable hygiene step, in the same way that keeping clean titles and descriptions is reasonable. The mistake is to treat it as a campaign on its own, or to pay an agency to add FAQ schema across a whole site in the hope of a ranking lift that will not come.
It pairs well with strong titles and descriptions
Schema does not replace the parts of a search result that still matter. Your title and meta description still decide whether a searcher clicks, and your content still decides whether they stay. If you are working on a page, check the title and description with the free Meta Tag Generator, and read our guide on how to write meta titles and descriptions before you touch the schema. A clear title, a useful description, and a genuine FAQ section will do more for that page than any markup alone.
What FAQ schema cannot do
Honest expectations matter more than enthusiasm here, so this section states the limits plainly. If a guide, a plugin, or a freelancer promises any of the following from FAQ schema alone, treat the promise with suspicion.
- It cannot improve your rankings. Structured data is not a ranking factor. A page ranks because its content answers the query well, because other trusted sites link to it, and because the site behind it is crawlable and fast. FAQ schema changes none of those things. Our link building services exist for the part that schema cannot do: earning real links from real sites that show Google your content is worth trusting.
- It cannot bring back FAQ rich results. Google stopped showing them for every site on 7 May 2026. Valid markup does not restore a feature Google has removed.
- It cannot guarantee an AI Overview citation. Google says no special schema is required for AI Overviews or AI Mode, and it does not promise that marked up content will be cited. Clear, answer first content on the page is what gets quoted, and even that is never guaranteed.
- It cannot fix thin or misleading content. If the answers on the page are vague, promotional, or copied from elsewhere, the schema only labels weak content more precisely. Fix the answers first.
- It cannot replace internal linking. A FAQ section answers questions, but it does not tell Google how your pages relate to each other. That job belongs to internal links, from the page to your service pages and to related guides, and from other pages back to this one. The free SEO tools hub shows how a hub page can connect a whole set of related tools and guides in one place.
- It cannot create questions nobody asks. Invented questions written only to target a keyword read as filler to visitors and to search engines. If nobody asks the question, do not mark it up.
There is also a subtle risk worth naming. Adding FAQ schema to every page on a site, including pages with no real questions, dilutes the signal. A crawler that keeps finding marked up FAQs on pages where the questions are forced or irrelevant learns to pay less attention to your markup in general. Use FAQPage where a genuine FAQ section exists, and leave it off pages where it does not. Selectivity is part of doing it properly.
How to write FAQs worth marking up
Good schema starts with good questions. Before you open any generator, spend your time on the content itself. The questions should come from real people, not from a keyword tool alone.
Find the questions people actually ask
Start with the sources closest to your customers. Support tickets and live chat logs show the exact words people use when they are stuck. Sales calls show the objections that stop a deal. Comments on your blog and social posts show what readers did not understand. Search Console shows the queries that already bring people to the page, including the question phrased queries that your page does not yet answer directly. Google’s People Also Ask box shows the follow on questions searchers ask around your topic, and it is a useful source of phrasing, though you should answer in your own words rather than copying the box.
Group the questions by theme. Pricing, delivery, suitability, comparisons, and problems are the usual groups for a service page. A product page adds compatibility, sizing, care, and returns. A blog article adds definitions, methods, and common mistakes. Aim for four to eight questions per page. Fewer than three looks thin, and more than ten usually means some of the questions are not real questions at all.
Write answers that stand alone
Each answer should make sense on its own, without the rest of the page. A reader who lands directly on that question should get a complete answer in two to four sentences, or about 40 to 70 words. Put the direct answer first, then add one sentence of useful context if it is needed. Avoid answers that only say yes or no, and avoid answers that tell the reader to contact you instead of answering. If the honest answer is that it depends, say what it depends on, and give the most common case.
Use plain language. Define any term a new reader would not know. Keep sentences short. If an answer needs a list, use one, but keep it tight. And never write an answer that is really an advert. A question such as “Why should I choose your company?” with an answer that is pure self promotion is not a frequently asked question. It is a sales pitch in disguise, and Google’s guidelines treat promotional FAQ content as a misuse of the format.
Keep the questions visible and honest
Every question you mark up must appear on the page, in text that a visitor can read without doing anything special. Do not hide questions in tabs that never load their content into the page HTML, do not put them in a section that only appears after a click that a crawler never makes, and do not write answers in the code that differ from the answers on the page. If your FAQ section uses an accordion, make sure the questions and answers are present in the rendered page, not loaded only when a visitor opens each item.
Check the wording once more before you generate the schema. Read each question aloud. If it sounds like something a real customer would ask, keep it. If it sounds like something a keyword tool suggested, rewrite it or remove it. The test is simple, and it is the same test Google applies: would a visitor find this question and this answer useful?
How to add FAQ schema by hand
You do not need a plugin or a tool to add FAQ schema. The block is short, and writing it once by hand teaches you what each part does. Follow these steps.
Step 1: Write the visible FAQ section first
Add the questions and answers to the page as normal text, with each question as a heading and each answer as a paragraph below it. Publish the section or save the draft, and read it as a visitor would. Fix anything that is unclear before you touch the code.
Step 2: Build the JSON-LD block
Create one FAQPage object. Set the context to https://schema.org and the type to FAQPage. Add a mainEntity array, and for each question add a Question object with a name and an acceptedAnswer object with text. Copy the question and the answer exactly as they appear on the page. The example in the first section of this guide shows the shape. Keep the block to one FAQPage per page. Adding two FAQPage blocks to the same URL creates a conflict, and a search engine may ignore both.
Step 3: Place the block in the page
Wrap the JSON in a script tag with the type application/ld+json, like this:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is FAQ schema?",
"acceptedAnswer": {
"@type": "Answer",
"text": "FAQ schema is FAQPage structured data in JSON-LD format. It labels the questions and answers on a page so search engines can read them as data."
}
}
]
}
</script>
You can place the script in the head of the page or in the body near the FAQ section. Both positions work in modern pages. The important point is that the block is present in the HTML the server sends, not added later by JavaScript after the page loads. Some crawlers do not run JavaScript, so schema that only appears after scripts run is invisible to them. If your site builds pages with JavaScript, check the raw page source to confirm the block is there.
Step 4: Escape characters carefully
JSON is strict about punctuation. A stray double quote inside an answer will break the whole block, and a trailing comma after the last item will do the same. If an answer contains a double quote, escape it. If it contains a line break, keep the text on one line or use the proper escape. If it contains HTML such as a link, keep it simple or remove the link from the marked up text. The most reliable way to avoid these errors is to generate the block with a tool rather than typing it by hand, which is the subject of the next section.
Step 5: Validate before you publish
Run the block through a validator before the page goes live, and again after it is published. The validation section later in this guide explains which tools still work for FAQPage in 2026 and what their results mean. Do not skip this step. A block with one broken character looks identical to a working block on the page, and only a parser will catch it.
How to add FAQ schema with the free FAQ Schema Generator
Hand writing JSON-LD is a useful skill, but it is slow and easy to get wrong. The free FAQ Schema Generator does the same job without the punctuation risk. It runs entirely in your browser, so nothing you type is uploaded or stored, and there is no signup, no account, and no limit on use. Here is how to use it, step by step, exactly as the live tool works. A full worked example on a real page walks through the same steps with real questions from a live article.
Step 1: Open the generator
Go to the FAQ Schema Generator page. You will see a Question field and an Answer field, with a live preview of the JSON-LD below them. The preview updates as you type, so you can watch the schema take shape in real time.
Step 2: Add your first question and answer
Type your first question in the Question field, exactly as it appears on your page, and type the answer in the Answer field, exactly as it appears on your page. Keep the answer short and complete, in the same words a visitor reads. Do not paste a different version of the answer into the tool. The code must match the page.
Step 3: Add more questions
Click the Add question button for each extra question. A new Question and Answer pair appears. If you add one by mistake, click the Remove button beside it to take it away. Work through your list one pair at a time, checking each answer against the page as you go.
Step 4: Try the sample if you want a quick test
Click Load sample to fill in three example questions and answers in one click. This is useful if you want to see the output format before you type your own content, or if you want to test the copy and download buttons. Replace the sample text with your own questions before you use the output on a real page.
Step 5: Copy or download your schema
When the preview shows all your questions, click Copy to copy the JSON-LD to your clipboard, or click Download to save it as a file called faq-schema.json. The download is handy if you keep schema files with your page templates or hand them to a developer. Either way, the output is a complete FAQPage block, ready to paste.
Step 6: Paste it into your page
Paste the copied block into your page HTML, inside a script tag with the type application/ld+json, in the head or near the FAQ section. If you downloaded the file, open it and copy the contents into the same kind of script tag. Publish the page, then view the page source in your browser and confirm the block is present in the HTML that the server sent.
Step 7: Test it
Run the published page through the Schema Markup Validator at validator.schema.org to confirm the JSON-LD parses and the FAQPage structure is correct. The validation section below explains this step in full, including what to do when a test reports nothing, which is now the expected result in some Google tools.
What the results mean
The generator output is a faithful copy of what you typed, formatted as valid JSON-LD. It does not check whether your questions are good, whether your answers are accurate, or whether Google will display anything. Those judgements belong to you and to the content on the page. What the tool guarantees is the structure: the context, the type, the question list, and the answer fields are all in the right places, with the punctuation correct. That is the part machines care about, and it is the part that hand written code most often gets wrong.
If you work with other schema types, the same approach applies. The free SEO tools hub lists the full set of LinkTrixx tools, including the Meta Tag Generator, the Keyword Density Checker, and the Robots.txt Generator. Each one runs in the browser in the same way, with no signup and no upload. Our guide on how to use the free Robots.txt Generator shows the same step by step pattern applied to a technical file, and our comparison of a free robots.txt generator vs paid SEO tools shows when the free tool is enough and when a paid tool earns its price, and our guide on how to use the free Keyword Density Checker shows how to check whether a page uses its target keyword at a sensible density before you publish. For the FAQ tool itself, our comparison of a free FAQ schema generator vs paid SEO tools makes the same check, with the paid prices checked when the post was written.
How to validate FAQ schema
Validation is the step that separates a page with schema from a page with broken code that looks like schema. It takes two minutes, and it catches the errors that are invisible on screen. Run these checks in order.
Check 1: The Schema Markup Validator
Open validator.schema.org, paste your JSON-LD block or your page URL, and run the test. This is now your primary tool for FAQPage, because it checks the markup against the schema.org specification itself, rather than against eligibility for a Google search feature. Look for a clean result with no errors. The validator will flag a missing name, a missing acceptedAnswer, a wrong type, or a JSON syntax error, and it will point at the line where the problem sits. If JSON itself is new to you, our guide to what JSON is explains the format, its six value types, and the ten errors that break a block, so the validation step makes sense before you run it. Fix the error in the generator or in your code, and run the test again until it passes.
Check 2: The Rich Results Test, with its limits understood
Google’s Rich Results Test accepts a URL or a block of code and reports the structured data it detects. For FAQPage, you need to know its current limit. Google dropped FAQPage support from this tool in June 2026, when the rich result was removed. A valid FAQPage block will now show as nothing detected in the Rich Results Test, and that result does not mean your markup is broken. It means the tool no longer reports on a feature that no longer exists. Use the Rich Results Test for other schema types that still produce rich results, such as Product, Recipe, and Article, and use the Schema Markup Validator as the authority for FAQPage.
Check 3: View the page source
Open the published page in your browser, view the page source, and search for FAQPage. Confirm three things. First, the script block is present in the source the server sent, not only in the rendered page after JavaScript runs. Second, there is only one FAQPage block on the page. Third, the questions and answers in the block match the visible FAQ section word for word. If the block is missing from the source, your site may be adding it with JavaScript after load, and some crawlers will never see it. Move the block into the server rendered HTML.
Check 4: Search Console URL Inspection
For pages you own, use the URL Inspection tool in Google Search Console to check crawl and index status and to see how Google last rendered the page. Search Console no longer carries an FAQ enhancement report, since the feature was removed, so do not look for one. Use the inspection tool to confirm the page is indexed and that Google can see the content. If the page is not indexed, the schema is irrelevant, because Google is not showing the page at all. Fix the indexing problem first, then worry about the markup.
Check 5: Preview the page as a visitor
Finally, read the FAQ section as a visitor. Click through any accordion, check the page on a phone, and confirm every question and answer is readable without extra steps. If a visitor cannot read an answer, the schema should not claim the page provides it. This check catches the visibility problems that validators cannot see.
Common FAQ schema mistakes
Most FAQ schema failures come from a short list of repeatable errors. Work through this list before you publish, and you will avoid nearly all of them.
Invalid JSON
The most common error is broken JSON. A trailing comma after the last question, a missing closing bracket, or an unescaped double quote inside an answer will break the entire block. The parser does not guess what you meant. It drops the block. Generate the code with the FAQ Schema Generator instead of typing it by hand, and validate every block before it goes live. If you edit the block by hand afterwards, validate it again.
Marked up content that visitors cannot see
Marking up questions and answers that do not appear on the page is the most serious policy error. Google’s general structured data guidelines require marked up content to be visible to readers. Hidden FAQs, code only FAQs, and answers that exist only in the JSON are all violations, even when the JSON itself is valid. If a question matters enough to mark up, it matters enough to show on the page.
Mismatched text between code and page
The questions and answers in the JSON-LD must match the visible text. If you shorten an answer in the code, expand it on the page, or update the page without updating the schema, the two versions disagree. Keep one source of truth, which is the visible page, and regenerate the schema whenever the page changes. This is easy to forget on service pages that get updated often, so add a schema check to your page update routine.
Markup on a page with no FAQ section
Some sites add FAQPage markup to every page template, including home pages, category pages, and landing pages with no questions at all. The markup then describes content that does not exist. Use FAQPage only on pages that carry a genuine FAQ section. If a page has no questions, leave the schema off it. The absence of schema is not an error.
Multiple FAQPage blocks on one page
One FAQPage block per page is the rule. Two blocks, for example one from a plugin and one pasted in by hand, can conflict, and a search engine may ignore both. Check the page source for duplicate blocks, especially if your site uses more than one SEO plugin or a theme that adds schema automatically. If you find a duplicate, remove one and keep the block that matches the page.
Promotional or misleading questions
Questions written to sell rather than to answer are a misuse of the format. “Why is our service the best?” and “Where can I buy the cheapest option?” are adverts, not frequently asked questions. So are questions stuffed with keywords that no customer would ever ask in those words. Write questions a real person would ask, and answer them directly. If a question exists only to carry a keyword, remove it.
Using FAQPage for user generated questions
If visitors ask the questions and other visitors answer them, the correct type is QAPage, not FAQPage. Marking a forum thread as FAQPage claims the site owner wrote both sides of the conversation, which is not true. Use the right type for the content you have. The same care applies to a single question with several answers from different people. FAQPage expects one accepted answer per question, written by the site owner.
Duplicating the same FAQs across many pages
Copying the same set of questions onto every page of a site, with only the page title changed, creates thin, repetitive content. Each page should answer the questions that belong to that page. A pricing page answers pricing questions. A service page answers questions about that service. A blog article answers questions about its topic. Shared questions about the company as a whole belong on one page, such as an About or Contact page, not on every page at once.
Forgetting to update the schema
Pages change. Prices change, policies change, and answers that were correct last year may be wrong now. When you update a visible answer, update the schema in the same edit. An outdated answer in the code is worse than no schema at all, because it tells a machine something the page no longer says. A quick check with the Word Counter can help you keep answers at a consistent length when you rewrite them, and the SERP Preview Tool shows how the page title and description will look in search results after an update.
FAQ schema and AI search
AI Overviews, AI Mode, and chat based assistants have changed how people find answers, and many guides now present FAQ schema as the way to appear in those answers. The honest position is narrower than the sales pitch.
Google has said plainly that no special schema is required to appear in AI Overviews or AI Mode. The systems that build those answers read the visible content of indexed pages, and they select passages that answer the query directly, completely, and in a form that is easy to quote. A clear FAQ section helps that process, because it gives the system a short, self contained answer to extract. The schema block underneath it does not add a separate signal that pushes the page into an answer. It is the visible answer that earns the citation, if any citation comes at all.
That does not make FAQ content useless for AI search. It makes the visible content the priority. Write answers that a system can quote without extra context. Put the direct answer in the first sentence. Keep the answer short enough to quote, and complete enough to satisfy the reader. Use the same words the searcher used in the question, where that is natural. And structure the page so that each question is easy to find, with a heading that states the question and a paragraph that answers it. That structure helps human readers, helps classic search, and helps AI systems, all for the same reason: it is easy to read.
There are also claims in circulation that FAQ schema makes a page several times more likely to appear in AI Overviews, or that only a small share of sites use structured data, so adding it puts you ahead of most competitors. Treat such figures with care. They come from vendor studies with methods that are rarely published in full, and they are not Google statements. This guide does not repeat them as facts, because they cannot be verified from the sources available. What can be verified is Google’s own guidance, and that guidance says the fundamentals matter: indexed content, crawlability, useful text, internal links, page experience, and structured data that matches visible content. Build on those fundamentals, and treat the schema as the last of them, not the first.
FAQ schema for link building and service pages
FAQ schema is a technical topic, but it sits inside a larger SEO job, and that job is what LinkTrixx does every day. A service page with a good FAQ section is easier to trust, easier to link to, and easier to convert. Here is how the pieces fit together.
Good FAQs make a page worth linking to
Other sites link to pages that answer questions their own readers ask. A service page that explains pricing, timelines, deliverables, and guarantees in plain language gives another site a reason to reference it. A page with no answers gives no reason at all. Write the FAQ section as if a peer in your industry might link to it, because that is often how links are earned. If you want to understand the wider process, read our comparison of the free Keyword Density Checker against paid SEO tools, which shows the same principle at work: a free tool that genuinely helps people earns attention that a thin page never will.
Match the FAQ section to the service
Each money page on this site answers different questions. A visitor to the link building services page wants to know how placements are sourced, how long they take, and what a link costs. A visitor to the SaaS link building page wants to know how the work fits a software product and its market. A visitor to the guest posting page wants to know which sites are available and how content is handled. An agency reading the white label link building page wants to know how the work stays under its own brand. Write each page’s questions for its own visitors, mark up only those questions, and keep the schema as faithful to each page as the page is to its readers.
Link the FAQ section into the site
A FAQ section should not sit in isolation. Link from the answers to the pages that go deeper, such as a service page, a pricing page, or a related guide. Link to the FAQ page from related articles, so that crawlers and readers can find it. And link from the FAQ section to the tool that built its schema, so that a reader who wants to do the same thing for their own site can follow the same steps. That is the internal linking pattern this guide follows throughout, and it is the pattern Google recommends in its AI guidance: useful text, connected by internal links, on pages that are easy to crawl.
Keep the content programme going
One FAQ section is not a content strategy. The pages that earn links over time are the ones that keep answering new questions, keep their answers current, and keep connecting to related guides. The LinkTrixx blog carries the full set of guides in this series, including the meta titles guide, the keyword density guides, and the robots.txt guide linked above. Each new guide answers a real question, links to the tool it describes, and links back to the service pages that the guide supports. That is the structure that makes a site easy for Google to understand, and it is the structure that makes a site worth linking to.
When to keep FAQ schema and when to skip it
Use this short decision list for any page you are considering. If the page passes all five checks, add the schema. If it fails any of them, fix the page first or skip the schema.
- The page has a genuine FAQ section. Real questions, written by you, with complete answers, visible to every visitor.
- Each question has one accepted answer. The answer is yours, it stands alone, and it matches the code exactly.
- The questions are useful, not promotional. A visitor would find them helpful, and none of them exists only to carry a keyword or a sales message.
- The page has one FAQPage block. No duplicates from a plugin, a theme, or a pasted block that was never removed.
- The block validates. The Schema Markup Validator reports no errors, and the block is present in the page source the server sends.
Skip the schema when the page has no FAQ section, when the questions are invented, when the answers are hidden, or when the page is a forum that needs QAPage instead. Skipping it is not a penalty. It is a correct decision, and it keeps your markup trustworthy on the pages where you do use it.
If you decide to add it, the whole job takes minutes. Write the visible questions, open the FAQ Schema Generator, type each pair, copy the output, paste it into the page, and validate it. Then move on to the work that actually moves rankings: better content, stronger internal links, and real links from trusted sites.
Frequently asked questions about FAQ schema
What is FAQ schema in simple terms?
FAQ schema is FAQPage structured data in JSON-LD format. It labels the questions and answers on a page so search engines can read them as data, with each question paired to its accepted answer. Visitors never see the code. They only see the visible FAQ section, and the schema is a machine readable copy of that same content.
Does FAQ schema help SEO in 2026?
FAQ schema helps search engines understand question and answer content clearly, and it keeps your pages machine readable for other systems that parse schema.org data. It is not a ranking factor, and it does not guarantee extra visibility, clicks, or AI citations. Treat it as a small hygiene step that supports good content, not as a tactic that moves rankings on its own.
Will Google show my FAQs as rich results?
No. Google stopped showing FAQ rich results for every site on 7 May 2026, including government and health sites, and it removed the FAQ documentation from Search Central on 15 June 2026. Valid FAQPage markup does not bring the expandable result back, and no tool or plugin can restore a feature Google has removed.
How do I add FAQ schema to a page?
Write the questions and answers as visible text on the page first. Then open the free FAQ Schema Generator, type each question with its answer, and copy or download the JSON-LD output. Paste the block into your page inside a script tag, publish the page, and validate the result with the Schema Markup Validator. Check the page source to confirm the block is present and matches the visible text.
What is the difference between FAQ schema and a plain FAQ section?
A plain FAQ section is visible text for readers, with each question as a heading and each answer as a paragraph below it. FAQ schema is invisible code that describes the same questions and answers in JSON-LD so machines can read them as data. You need the visible section first. The schema is an optional label on top of it, and it must never describe content that visitors cannot see.
Is the FAQ Schema Generator free?
Yes. The FAQ Schema Generator is completely free to use, with no signup, no account, and no limits. Your questions and answers are turned into JSON-LD in your browser, so nothing is uploaded or stored. You can copy the output or download it as a file, then paste it into any page that carries a matching visible FAQ section.
FAQ schema is a small, honest piece of technical SEO. It labels good questions and good answers so machines can read them clearly. It will not rank your page, it will not restore a rich result Google has removed, and it will not get you cited by an AI system on its own. What it will do is keep your pages clean, consistent, and machine readable, at almost no cost, on the pages where a genuine FAQ section already exists. Write the answers first, generate the schema second, validate it third, and then spend the rest of your time on the work that earns links and rankings.