Structured data for a rich result Google no longer shows
structured_data_retired_typeShort answer
The page carries structured data for a rich result that Google has retired; the markup is still valid schema.org but no longer changes how the page appears in search. No change needed: the markup does no harm, but it no longer brings a rich result. Google stopped showing FAQ rich results in May 2026 and HowTo rich results in 2023. Don't add it to new pages for the sake of search results.
Why it matters
This is informational. Many sites still generate FAQPage and HowTo markup because plugins and templates were built when those rich results existed. Keeping it costs a few kilobytes; removing it costs an edit. The one thing to avoid is adding more of it expecting a visual benefit.
How Glimana detects it
Glimana checks the page's structured-data types against a list of retired rich-result types and fires when one is present. The evidence names the type.
How to fix it
- Find the affected pages in Glimana. Open Issues › Structured data for a rich result Google no longer shows. Every affected page is a row; open one to see the evidence Glimana recorded for it (the measured value, the offending element or the target URL). The same list sits on the task card under Tasks, and the page's own detail view under Pages shows its full signals.
-
Apply the fix on your platform.
Optional. If you want to remove it:
FAQ and HowTo blocks in Yoast / Rank Math emit the schema; the content block can stay while you disable the schema output in the plugin settings, or leave it as is.
FAQ apps often inject
FAQPageJSON-LD; disable it in the app settings if offered.Remove the JSON-LD block from the template. Keep the visible FAQ content; it is still useful to users and to AI answer engines that read the page text.
-
Publish and clear caches. Save and publish, then make sure the crawler will see the new version: WordPress — clear the page cache in your cache plugin and purge the CDN; Shopify — theme and content changes go live on save, but purge any CDN in front of the store; custom code — deploy and purge the edge cache. Check in a private window or with
curl -s https://your-domain/page | grep -i '<title\|canonical\|robots'that the live HTML has changed; Glimana reads what the server sends, not what your browser has cached. - Verify in Glimana. Open the task under Tasks and click Mark as done. The affected pages are queued for a verification crawl within a few hours, and the task closes when the retired type is gone. If the check still fails, the task returns to New with a note; when it passes, the task is listed under Resolved technical issues on Impact reports. To check sooner, use Re-crawl affected pages on the issue.
How the fix is verified
Re-crawl; the task closes when the retired type is gone. It is safe to dismiss the task instead.