Safeguard
Industry Analysis•

FAQ rich results were retired: what to do with your FAQ markup

Google's documentation says FAQ rich results stopped showing on 7 May 2026. What that means for existing FAQ markup and for your FAQ content.

Safeguard Security Team
3 min read

Google's documentation says FAQ rich results no longer appear in Search, starting 7 May 2026, and that the feature documentation was later removed. Existing FAQPage markup will not produce those results, so you can stop adding it, but the FAQ content itself still earns its place on the page.

What Google's page says

The FAQ documentation carries a changelog with three relevant entries. In September 2023 it was updated to say the feature was only shown for well known, authoritative government and health sites. On 8 May 2026 a deprecation notice was added stating the feature would no longer appear in Search starting 7 May 2026. On 15 June 2026 the documentation was removed because the rich result is no longer shown.

I could not read the original guidelines on that page, so I will not restate them.

What to do with existing markup

Three options, in order of effort.

  1. Leave it. The markup is harmless if it matches visible content. Google's general rule still holds: structured data should describe what readers can see.
  2. Stop generating it for new pages. This saves template complexity.
  3. Remove it in a planned cleanup, not an emergency one. Check Search Console afterward for any new errors.

Do not rush to delete it from a hundred pages tonight. The risk of breaking a template is larger than the cost of keeping valid markup.

Keep the questions

Real questions, answered in plain text, remain useful to readers and to anyone summarizing your page. Google's AI features documentation says to keep important content in text form. A visible Quick check or FAQ section does that.

Write each answer to stand alone in one to three sentences. Put the same question wording a user would type. See technical writing for answer engines.

Do not hide answers

If you collapse answers in expandable sections, check that they are still in the rendered HTML. Google's snippet guidance notes that content immediately visible, rather than hidden behind expandable sections or tabs, is more likely to get deep links. Collapsing is fine for readers. Just do not make the answer depend on a script that may not run.

Quick check

Is FAQPage still a valid schema.org type?

I did not verify the current schema.org status. What I confirmed is that Google no longer shows the FAQ rich result.

Could leftover FAQ markup hurt me?

Google's documentation I read does not say valid markup that matches visible content is penalized. Spammy or non compliant markup is a different matter.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.