What FAQPage schema is
FAQPage is the Schema.org type for a page where the primary content is a list of frequently asked questions and their answers. The shape: a top-level FAQPage object with a mainEntity array of Question objects, each carrying a name (the question text) and an acceptedAnswer (an Answer object with text). The vocabulary is unchanged in 2026 — FAQPage remains a current, valid Schema.org type at version 30.0. What changed is Google's rich-result behaviour, not the schema itself.
When to use FAQ schema on a Squarespace site (and when not)
Use FAQPage schema on one page only: the dedicated FAQ hub where Q&A is the primary content. Do not use it on service pages with an FAQ section at the bottom, blog posts with a Q&A block, product pages with a FAQ accordion, or the homepage. The test is the page's primary purpose. A page whose primary purpose is to answer FAQs qualifies. A page that contains some FAQ content among other content does not.
Rich-results status post-May 2026
Google's canonical FAQ documentation now states the eligibility restriction directly: FAQ rich results are available only for well-known authoritative websites that are government-focused or health-focused. The retirement took effect 7 May 2026 for general Search. Rich Results Test FAQ support is scheduled to end June 2026; Search Console API FAQ report support ends August 2026. The underlying FAQPage Schema.org type is not deprecated — it remains a valid annotation — but no visible enrichment renders in general Search.
Required and recommended fields
Google's structured-data documentation defines four properties for valid FAQPage markup. Required: mainEntity (an array of Question objects). Per Question: name (the question text). Per Question: acceptedAnswer (an Answer object). Per Answer: text (the answer text). Optional: inLanguage (when the page is multilingual), dateCreated and dateModified (when questions evolve). The hard constraint is content fidelity — every question and answer in the schema must appear as visible text on the page, not hidden behind interaction.
Copy-paste JSON-LD example
The block below is a complete FAQPage schema for a dedicated /faq/ hub on a Squarespace business. Replace the question and answer text with your real visible Q&A. Keep the schema and the visible content in sync — diverging means the markup violates Google's content-fidelity policy.
Where to paste it on Squarespace
Open the FAQ hub in the Squarespace editor. Click the gear icon to open Page Settings. Open the Advanced tab. Find the Page Header Code Injection field. Paste the entire script block including the wrapping script tags. Save. Code Injection is available on Core and above. Personal-tier sites cannot install JSON-LD via Squarespace; the workaround is a plan upgrade. The page-level placement (not site-wide) is correct because FAQPage describes one specific page, not the whole site.
Validation steps in 2026
Until June 2026, Google's Rich Results Test still detects FAQPage. After June 2026 the FAQ-specific detection ends and validation moves to the Schema.org Markup Validator at validator.schema.org. Either way, confirm zero structural errors. The markup remains valid Schema.org regardless of whether the Rich Results Test still recognises it as a Google rich-result type.
Common gotchas on Squarespace
Four gotchas catch most Squarespace FAQ schema installs in 2026. First: schema/content mismatch. The visible Q&A must match the schema text exactly; Squarespace's accordion block sometimes wraps answer text in markup that diverges from the JSON. Second: smart quotes. The editor auto-corrects straight quotes to curly quotes, breaking JSON. Third: duplicate emission. A sitewide FAQPage Code Injection plus a per-page FAQPage Code Injection produces two blocks for the same page. Fourth: keeping FAQ schema on service pages out of habit — it adds maintenance burden and no longer produces a visible result for non-authoritative sites.
Related schema types
FAQPage typically ships alongside Article (when the FAQ hub is part of a broader editorial site) or LocalBusiness (when the FAQ hub answers questions about a local business). BreadcrumbList belongs alongside both. The Person and Organization entities that own the FAQ hub get their own schema blocks elsewhere — they don't duplicate inside the FAQPage block.