From f2d6d29df97a5f1ab12aeba26e5a3f434a97717b Mon Sep 17 00:00:00 2001 From: Joost de Valk Date: Mon, 3 Aug 2026 08:08:53 +0200 Subject: [PATCH] fix(citations): the FAQ rich result doc is gone; cite the changelog and schema.org Google stopped showing the FAQ rich result on 7 May 2026 and deleted /search/docs/appearance/structured-data/faqpage on 15 June 2026. The page's prose was already correct about the retirement, but both the frontmatter source and the inline link pointed at the deleted doc. Swap the frontmatter source for the Search Central changelog, which carries both entries, and split the inline link: the changelog evidences the retirement, schema.org/FAQPage evidences that the vocabulary is still valid. Dates are now stated in the prose so the claim survives the changelog entry scrolling off. Co-Authored-By: Claude Opus 5 (1M context) --- src/content/spec/seo/structured-data.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/content/spec/seo/structured-data.md b/src/content/spec/seo/structured-data.md index b6d67e93..e957f1de 100644 --- a/src/content/spec/seo/structured-data.md +++ b/src/content/spec/seo/structured-data.md @@ -7,13 +7,13 @@ status: recommended order: 100 appliesTo: [all] relatedSlugs: [breadcrumbs, heading-hierarchy, xml-sitemaps, canonical-url, schemamap, server-side-rendering] -updated: "2026-07-09T00:00:00.000Z" +updated: "2026-08-03T00:00:00.000Z" sources: - title: "Schema.org" url: "https://schema.org/" publisher: "schema.org" - - title: "FAQPage (FAQ) structured data" - url: "https://developers.google.com/search/docs/appearance/structured-data/faqpage" + - title: "Latest Google Search documentation updates" + url: "https://developers.google.com/search/updates" publisher: "Google Search Central" - title: "Introduction to structured data markup in Google Search" url: "https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data" @@ -69,7 +69,7 @@ Stick to a small set of well-supported types: - **`BreadcrumbList`** — on every page that has a breadcrumb trail. - **`Article`** or **`BlogPosting`** — for articles, with `headline`, `datePublished`, `dateModified`, `author`, `image`. - **`Product`**, **`Offer`**, **`AggregateRating`** — for e-commerce, where eligibility is strict. -- **`FAQPage`** — only when the page genuinely has a Q-and-A list visible to users. Note that Google [retired the FAQ rich result in 2026](https://developers.google.com/search/docs/appearance/structured-data/faqpage): `FAQPage` is still valid schema.org vocabulary, but it no longer produces a Google search feature, and no answer engine has confirmed it favours the markup over rendered HTML — so add it for genuine visible content, not for SERP or "GEO" gain. Never stuff fake FAQs. ([Further reading](https://joost.blog/faq-schema-cycle/) on why the format was abused into deprecation, and the proposed `FAQSection` type for Q-and-A that is a *section* of a page rather than its main entity.) +- **`FAQPage`** — only when the page genuinely has a Q-and-A list visible to users. Google [stopped showing the FAQ rich result on 7 May 2026 and deleted its documentation on 15 June 2026](https://developers.google.com/search/updates): [`FAQPage`](https://schema.org/FAQPage) is still valid schema.org vocabulary, but it no longer produces a Google search feature, and no answer engine has confirmed it favours the markup over rendered HTML — so add it for genuine visible content, not for SERP or "GEO" gain. Never stuff fake FAQs. ([Further reading](https://joost.blog/faq-schema-cycle/) on why the format was abused into deprecation, and the proposed `FAQSection` type for Q-and-A that is a *section* of a page rather than its main entity.) Rules: