DEV Community

Cover image for Google deprecated FAQ rich results. Should you remove the JSON-LD?
SmartMetrics Support
SmartMetrics Support

Posted on

Google deprecated FAQ rich results. Should you remove the JSON-LD?

Google killed FAQ rich results in Search yesterday. Next month, the Search Console report will go away, and API support will drop in August. None of this affects ranking. If you have FAQPage JSON-LD shipping on pages today, you can pull it or leave it without consequence either way.
If you want to grep your codebase, here's the markup example:

<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "How long does shipping take?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Standard shipping takes 3-5 business days."
}
}]
}
</script>

The reason there's no ranking impact is that the FAQ schema never affected ranking in the first place. It only ever made you eligible for the rich snippet, the expandable Q&A block under the listing. Google narrowed that snippet to government and authoritative health sites back in 2023. Almost nothing else has triggered it since. This week's news is the formal end of a feature that already stopped firing three years ago.

For new Q&A content, drop the schema entirely and use semantic HTML - simple h2/p.

This is what feeds People Also Ask. Google extracts question-answer pairs from the rendered DOM, not from structured data. Same with LLMs. ChatGPT, Perplexity, and AI Overviews tokenize and read the visible text. JSON-LD lives in the page source but doesn't add anything that a parser of clean HTML doesn't already get.

So here's the shipping advice for new pages. Skip FAQPage, write the question in an H2, put the answer in the very next sentence, and stop there. That's the format that gets pulled into PAA and quoted by AI engines.

Read the full breakdown for SEOs - link

Top comments (0)