FAQ schema markup is a specific type of structured data that identifies a list of questions and answers on a webpage. While Google restricted the display of FAQ rich results to government and health-related websites in late 2023, this markup still helps search engines understand the semantic structure of your content. Using it correctly ensures that your data is machine-readable, which aids in accurate indexing and potentially improves how your site appears for specialized queries.
Why did Google reduce FAQ rich result visibility?
In August 2023, Google announced a significant change to how FAQ and How-To rich results are displayed. The goal was to provide a cleaner and more consistent search experience. For most site owners, this meant that the expandable question-and-answer boxes previously visible under their search listings disappeared. This was not a penalty but a change in the assessment of what best answers a query.
This shift aligns with broader core updates where Google prioritizes helpful, reliable, and people-first content over technical tweaks designed solely to gain more screen space. When a site loses visibility during these transitions, it often reflects a change in Google’s ranking systems rather than a specific error on the website. Understanding this distinction is key for marketers who want to stay focused on long-term growth.
A site can lose visibility without doing anything wrong, the assessment of what best answers a query changed.
Google Search Central
Which websites still show FAQ rich results?
Currently, FAQ rich results are primarily reserved for well-known, authoritative health and government websites. This selective display ensures that users get trustworthy information directly on the results page for sensitive topics. For a typical e-commerce store or a software-as-a-service provider, the rich result will likely not appear, even if the markup is technically perfect.
Despite this, the schema remains useful. It serves as a clear signal to crawlers about the relationship between specific questions and their answers. If your page provides a direct answer to a long-tail query, Google might still use the information within your FAQ schema to generate a featured snippet or a specialized result, even if it does not use the traditional FAQ rich result format.
Technical requirements for FAQ structured data
To implement FAQ schema, you must use the JSON-LD format, which is the recommended method for Google Search. The code should be placed in the head or body of the HTML. Every FAQPage type must include a mainEntity property that contains a list of Question objects. Each Question must have a name (the text of the question) and an acceptedAnswer (the text of the answer).
- Use the FAQPage type at the top level of your JSON-LD block.
- Ensure each Question and Answer pair is visible to users on the actual page.
- Avoid using FAQ schema for advertising purposes or inappropriate content.
- Validate the code using the Rich Results Test tool to identify syntax errors.
- Check the URL Inspection tool in Search Console to see how Google crawls the page.
Common validation errors to avoid
Many sites fail validation because they include markup for content that is not present on the page. If your JSON-LD includes five questions but the user can only see three, this creates a mismatch. Additionally, using the same FAQ markup across multiple pages of a site can lead to indexing issues. Each page should have unique questions that are specific to its topic.
How Alien Road applies FAQ schema optimization
At Alien Road, we treat structured data as a foundation for AI-driven search understanding rather than a shortcut for visibility. Our process starts with a thorough audit of the client’s current search footprint. For a typical engagement, such as a Shopify store selling home goods, we identify pages that are already ranking in the top 10 for question-based queries.
Our team follows a specific workflow to implement and monitor these changes:
- Discovery Phase: We identify high-intent questions using search data and customer support logs.
- Implementation: We write custom JSON-LD for each page, ensuring the text matches the on-page copy exactly.
- Testing: We run every implementation through the Rich Results Test to fix non-critical issues.
- Monitoring: We track the ‘Enhancements’ report in Google Search Console to confirm the data is indexed.
- Iterative Review: We wait for the rollout of any core updates to complete before making further adjustments.
In a typical account, we might see that adding structured data helps the search engine categorize the page faster. For example, on a product category page, clarifying common questions about shipping or sizing through schema helps the AI understand the service level of the brand. We resist making a dozen changes at once during a rollout, as this allows us to learn which specific action had the most impact.
Wait for the rollout to complete before analysing anything. Compare like with like, the same period a year earlier, not the week before.
Google Search Central
Should you remove existing FAQ schema from your site?
There is no technical reason to remove FAQ schema just because the rich results are no longer visible. The markup still provides a detailed map of your content. Removing it could potentially lead to a loss of clarity for the search engine’s understanding of your page’s purpose. However, if your schema is outdated or contains errors, it is better to update it or remove the broken parts rather than leaving incorrect code in place.
If you are short on time, focus your efforts on pages that are most likely to benefit from semantic clarity. This includes detailed product descriptions, service pages, and comprehensive blog posts. For a site with thousands of pages, prioritize the top 20% of pages that drive 80% of your organic traffic.
How to monitor the impact of your schema?
Since rich results are limited, you cannot rely solely on the ‘impressions’ metric in the Search Console FAQ report. Instead, look at the overall ranking trends for question-based keywords. If your page starts appearing for more ‘how-to’ or ‘what is’ queries, your structured data is likely helping Google connect your content to those specific user needs.
You can also use the URL Inspection tool to see the last time Google crawled the structured data. If you see errors flagged in the Enhancements section, fix them immediately. While non-critical issues won’t prevent your page from ranking, a clean report is a sign of a healthy, well-maintained website.
Where to start this week
Start by auditing your top ten most important pages. Check if they have FAQ schema and use the Rich Results Test to ensure the code is valid. If the markup exists but the questions are outdated, update the text to reflect your current services or products. This simple step ensures that search engines have the most accurate information about your business.
Next, review your Search Console reports. Identify any pages that lost visibility during recent core updates and check if those pages contain thin content. Instead of adding more technical schema to a weak page, focus on improving the actual text. A strong, detailed answer on the page is always more valuable than a complex piece of code that lacks substance.