FAQ schema in 2026 and what to keep after rich results end

Keep FAQ content that helps customers. Keep accurate FAQ schema if it has a clear use and takes little work. Remove paid features bought only to earn Google FAQ rich results. Google stopped showing those results on 7 May 2026, so new markup will not bring them back. Google records the end date in its Search updates.

For a small business, the best next step is a short audit. Review the answers, the code, the bill and the reports as four separate items.

What changed for FAQ schema in 2026?

FAQ schema is code that labels questions and answers for machines. It often uses JSON-LD, a data format placed in a page. Visitors read the page text; tools can read the markup.

Three things need separate checks:

- FAQ content: The questions and answers people can read.

- FAQPage markup: The code that describes that content.

- Google FAQ rich results: The extra questions once shown below a search listing.

Google ended the third item. It did not remove the FAQPage type from Schema.org. The Schema.org FAQPage definition still describes a page with one or more common questions.

Google had already limited FAQ rich results to well-known, trusted government and health sites in 2023. Most business sites had lost regular access long before May 2026. Advice that still lists those sectors as an exception is now out of date. Google's 2023 notice explains the earlier limits.

That notice also says unused structured data does not cause problems for Search. There is no need for a rushed purge of accurate markup. A paid promise of Google FAQ dropdowns, though, no longer has value.

FAQ schema decisions at a glance

Use this table before you change a template or cancel a plan.

Treat repeated markup as a control issue. Two sources can drift apart when staff edit only one. Do not claim that every duplicate block causes a penalty.

Keep answers that help people act

Start with support emails, sales calls and site search terms. Choose questions that reveal a real gap.

For example, a furniture shop might need to explain whether delivery includes assembly. A software service might need to state how users export their data. A web design firm might need to explain who owns the finished site.

Place essential facts in the main page copy. Delivery limits belong near delivery details. Fees belong near prices. Use a short FAQ for extra cases that would make the main text hard to scan.

For each answer, check four things:

1. Does it state a useful fact or step?

2. Does it match the current service, product or policy?

3. Can readers find it where the question comes up?

4. Is someone responsible for keeping it current?

Avoid vague replies such as “Contact us for more details” when you can give the rule first. If the answer varies, state what it depends on and offer a clear next step.

Make these checks part of routine website maintenance. A small content task is easier to manage when it has an owner and a review date.

Audit WordPress without losing useful content

Start with a backup and a test copy of the site. Pick one FAQ page, one blog post and one product or service page that use the same FAQ setup.

Find the source of the markup

Open each page while logged out. Use View Page Source and search for FAQPage. Check the browser's Elements panel too if scripts add content after the page loads.

List the likely sources: an SEO plugin, an FAQ block, a page builder, the theme or custom code. Check each tool's settings and notes. Change one source at a time on the test copy, then compare the page and markup.

For example, Yoast's FAQ block adds FAQ schema. The block can have value as a way to edit answers even after the Google display has ended.

Change the narrowest setting

If your tool offers a switch for FAQ markup alone, test that first. Do not turn off every schema type to remove one type.

Yoast's main schema switch controls its connected schema output. It is broader than an FAQ setting. Yoast explains that scope in its schema settings guide.

If there is no separate switch, compare the work of a custom change with the cost of leaving accurate markup in place. Paying a developer just to remove harmless code may solve no business problem.

Before you remove an FAQ plugin, check whether the page needs its blocks, styles or shortcodes. If it does, rebuild the visible answers first. WordPress provides separate Deactivate and Delete actions; test deactivation before deletion.

Clear the relevant caches after each change. Recheck the live page on a phone and a desktop, including all answer panels and links.

Audit Shopify before cancelling an app

Check the app's roles before you judge its price. Does it only add JSON-LD, or does it also display FAQs, manage shared answers or supply product data?

Check app blocks, embeds and theme code

Shopify apps can work through page blocks, app embeds or code added to a theme. Shopify's theme guide describes all three routes.

Use a copy of your theme for tests, and check whether app settings also affect the live store.

1. Open Online Store and edit the test theme.

2. Inspect the FAQ blocks on each relevant page template.

3. Open App embeds and check for the FAQ or schema app.

4. Check its settings for separate content and markup controls.

5. Preview the changed pages and inspect their FAQPage output.

Do not assume that disabling an embed cancels its subscription. Theme controls and billing are separate checks.

Export, replace, then uninstall

Save your questions and answers before removing the app. Replace any visible FAQ blocks you still need. Ask the app maker whether removal needs extra theme cleanup.

Shopify warns that some apps leave theme code behind. Its guide also says that uninstalling stops future recurring Shopify app charges, but a current cycle charge may remain. Charges paid outside Shopify need separate cancellation.

After removal, check a product page and the FAQ page again. Confirm that useful answers still appear and that other needed markup remains.

Decide what is worth paying for

Many store owners ask whether an FAQ schema app still earns its fee. Judge it by the features you actually use:

- Markup alone: Do not pay for a promise to restore Google FAQ rich results.

- Content tools: Keep a plan if it saves enough time on editing, shared answers or language versions.

- A wider SEO suite: Review the full feature list before a downgrade.

- AI claims: Request evidence tied to the exact feature and outcome being sold.

Use your own costs. Multiply the monthly fee by 12, then compare it with the cost of moving content and running a simpler setup. Include staff time, updates and support.

Google says no special Schema.org markup is needed for AI Overviews or AI Mode. That does not prove FAQ schema has no use in any AI system. It does rule out treating it as a required Google AI feature.

Replace old checks and reports

Use the Schema.org Markup Validator to check retained FAQPage data. This checks structured data, not whether Google offers a rich result for it. Google rich-result support and valid Schema.org code are separate tests.

Do not use Google's Rich Results Test as the pass or fail test for FAQPage. Check the current list of supported Google search features when you review other markup.

Retire report tiles and alerts that treat missing FAQ rich results as a site fault. Ask whoever runs your reporting to review old FAQ filters and API requests too. Remove obsolete FAQ-only requests from scheduled reports and check that totals still load.

Expect FAQ impressions in Search Console to fall after 7 May, because the feature ended. That drop alone does not show that the pages lost all search traffic.

Instead, track page clicks, search terms, leads, purchases and repeat support questions. Use Google Analytics to track website performance alongside Search Console.

Record when you change content, markup or tools. Compare similar periods and account for sales or seasonal demand. Avoid changing the text, title, URL and schema at once if you want a useful before-and-after check.

Frequently Asked Questions

Should I replace FAQPage with QAPage?

Only if the page fits that type. Schema.org defines QAPage around a single question and its answers. It is not a route to restore FAQ dropdowns. Choose markup that describes the actual page.

Can I keep answers in expandable panels?

Yes. Keep the controls clear and test them with a keyboard and on a phone. Readers must be able to reach the answers. An expandable panel is different from text placed only in markup.

Does removing FAQ markup require a new URL?

No. Edit the markup at its source while keeping the page at its current address. A code cleanup does not call for a URL change or a redirect.

Can a validator confirm that my answers are correct?

No. A valid structure can still contain an old fee or a false delivery promise. Compare the marked-up answers with the visible page and the current business rules. Google's structured data rules call for current, relevant content that readers can see.