FAQ Rich Results Are Dead. Don't Delete the Q&A Markup
Google retired FAQ rich results on May 7, 2026. FAQPage JSON-LD still passes the schema validator but returns DEPRECATED. What to change in code and content.
Tags
6 posts
Google retired FAQ rich results on May 7, 2026. FAQPage JSON-LD still passes the schema validator but returns DEPRECATED. What to change in code and content.
I added Restaurant structured data to my restaurant-discovery PWA, then fed the same three defects to three validation layers to measure which one catches what.
A JSON-LD parser passes markup no search engine can read: schema.org sets @vocab, so typos and wrong casing expand into valid JSON-LD. A 60-line schema-aware validator catches them in CI, with real logs.
The same Product entity in three syntaxes, bytes and fragility measured. Google treats them equally, so the reason to choose JSON-LD is coupling, not ranking.
My JSON-LD validated as three disconnected islands. Here's how @id references stitch Organization, WebSite, and Article into one @graph, measured with jsonld.
Inject LocalBusiness JSON-LD with JavaScript and the raw HTML has zero ld+json blocks. I compare it with server-side output, Google's stance and ranking limits.