Skip to content

fix(citations): the FAQ rich result doc is gone; cite the changelog and schema.org #156

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
jdevalk wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

fix(citations): the FAQ rich result doc is gone; cite the changelog and schema.org #156

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions src/content/spec/seo/structured-data.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down Expand Up @@ -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:

Expand Down
Loading