Google Removed FAQ Rich Results. How Should Small Businesses Re-Evaluate FAQ Schema?

Google has removed one of the most familiar structured data wins from the small business SEO playbook: FAQ rich results. As of May 7, 2026, FAQ rich results are no longer appearing in Google Search. Google also says it will remove the FAQ search appearance, the FAQ rich result report, and FAQ support in the Rich Results Test in June 2026, with Search Console API support ending in August 2026.

That sounds dramatic, but the practical decision is more precise. This is not a reason to delete every FAQ from your website. It is a reason to stop treating FAQPage schema as a shortcut to extra space in Google results. For a Canadian small business, FAQs still matter when they answer real buyer questions, clarify service scope, reduce friction, and make the page easier for search and AI systems to understand.

What Changed, Exactly?

Google had already reduced FAQ rich result visibility in August 2023. At that point, Google said FAQ rich results would generally be limited to well-known, authoritative government and health websites. The May 2026 update goes further: FAQ rich results are no longer appearing in Google Search, and the supporting reporting/testing surfaces are being phased out.

The key dates are simple:

• May 7, 2026: FAQ rich results stopped appearing in Google Search.
• June 2026: Google plans to drop the FAQ search appearance, FAQ rich result report, and FAQ support in the Rich Results Test.
• August 2026: FAQ rich result support in the Search Console API is scheduled to be removed.

For most SMBs, this changes the business case. The old pitch was often: add FAQ schema and win more SERP real estate. That pitch is no longer a responsible reason to invest. The new question is: does the FAQ content help customers, clarify the page, and support search visibility in ways that are not dependent on a special Google display feature?

This Does Not Mean FAQ Content Is Dead

A visible FAQ block can still be useful. It can answer objections before a visitor contacts you. It can explain pricing ranges, service areas, timelines, eligibility, warranties, booking steps, or what a customer should prepare. It can also make a service page less vague by giving search systems extractable question-and-answer content.

What changed is the reward model. FAQ content should not be written for a collapsed Google rich result. It should be written for the person who is trying to decide whether to call, book, request an audit, or compare your business with a competitor. If the question would never help a real customer, it probably does not deserve space on the page or markup in the HTML.

A Practical Re-Evaluation Matrix

Use this decision table when reviewing existing FAQ sections and FAQPage schema:

Current state	Decision	Why
The FAQ answers real buyer questions and is visible on the page.	Keep the FAQ and keep valid FAQPage markup.	The content still supports clarity, user experience, and machine understanding.
The FAQ is visible but vague, generic, or copied across many pages.	Rewrite it before keeping the markup.	Repetitive boilerplate can weaken page usefulness and does not help customers decide.
The schema exists but the FAQ is not visible to users.	Remove or fix the markup.	Structured data should describe visible page content, not hidden SEO-only content.
The FAQ was added only to chase Google rich results.	Stop adding it as a default tactic.	The Google display feature is gone, so the investment needs a better reason.
The page has no FAQ, but customers repeatedly ask the same questions.	Add visible FAQ content first, then consider FAQPage markup.	The user problem justifies the content; schema comes second.

What to Measure Now

FAQ rich result impressions are no longer the right success metric. If a page loses a FAQ search appearance report, that does not automatically mean the page lost rankings or value. Reporting needs to move back to URL-level business signals.

Track these instead:

• URL-level impressions and clicks in Google Search Console.
• CTR changes on pages that previously relied on FAQ rich results.
• Form submissions, phone clicks, bookings, and qualified enquiries from pages with FAQ sections.
• Query coverage for long-tail questions that FAQs answer.
• AI search visibility by checking whether AI tools mention or cite the page for practical buyer questions.
• On-page behaviour such as scroll depth, time on page, and whether visitors reach the contact path.

The most important change is interpretation. A drop in FAQ rich result reporting is expected because Google is removing the feature. A drop in enquiries, clicks, or qualified traffic is a different problem and should be investigated at the page level.

How Canadian SMBs Should Use FAQs Now

For a local or regional business, the strongest FAQ sections are not generic. They answer questions tied to service scope, geography, constraints, and buying risk. A Halifax service business might answer which areas it serves, how soon an audit or appointment can happen, what affects the quote, what information the customer should prepare, and when a smaller fix is enough.

For Canadian businesses, useful FAQ prompts often include:

• Do you serve my city, province, or region?
• What affects the price range?
• How long does the first project usually take?
• What should I fix before paying for monthly support?
• Do you work with bilingual, multi-location, or seasonal businesses?
• What information do you need before giving a recommendation?

These questions are valuable even without a Google FAQ rich result because they reduce sales friction. They also give search systems clearer text about what the business does, who it serves, and what the next step looks like.

Where FAQPage Schema Still Fits

FAQPage schema is not a ranking guarantee and it is no longer a Google FAQ rich-result strategy for normal small business sites. But structured data can still help describe page content when it is accurate, visible, and maintained. Google also says structured data should match the visible text on the page, and its AI features documentation still points site owners back to the same SEO fundamentals: indexable pages, useful textual content, internal links, page experience, and structured data that matches visible content.

The practical rule is straightforward: keep FAQPage markup when the page has a visible FAQ with one clear answer per question. Do not use FAQPage for user-generated Q&A, hidden content, advertising claims, fake questions, or boilerplate repeated across dozens of pages. If a page has no visible FAQ, it should not have FAQPage schema.

What to Do in the Next 30 Days

1. Inventory pages using FAQPage schema. List the URL, page type, visible FAQ status, and whether the questions are unique to that page.
2. Separate reporting changes from performance changes. Expect FAQ rich result reporting to disappear; investigate only URL-level traffic, CTR, and conversion movement.
3. Rewrite weak FAQ blocks. Replace generic questions with service, location, pricing, timeline, risk, and next-step questions customers actually ask.
4. Remove hidden or misleading markup. If the FAQ is not visible, either show useful FAQ content or remove the schema.
5. Update SEO dashboards. Remove dependencies on FAQ search appearance filters and API fields before the August 2026 API removal.
6. Measure the page as a decision asset. Watch clicks, conversions, query coverage, and AI/search citations instead of rich-result eligibility.

The Decision for Small Businesses

The right response is not panic. It is reallocation. Stop budgeting time for FAQ schema as a Google rich-result tactic. Keep budgeting time for useful FAQ content on pages where customers need answers before they contact you.

For most Canadian SMBs, the best version of this update is simple: remove fake SEO-only questions, improve real buyer answers, keep schema only where it reflects visible content, and measure outcomes at the URL and enquiry level. FAQ rich results are gone, but clear answers are still part of a strong SEO and GEO foundation.