Skip to content
50% OFF $299 $599
Lock in
§ 3.2 ARTICLE
Published VerifiedEvery 6 weeks Sources5 named Authored bySquareRank Team

Schema · § 3.2 · How-to

FAQ schema on Squarespace, post-May-2026

Google retired the FAQ rich result across general Search on 7 May 20261, restricting visible rich-result eligibility to government and health authorities. The FAQPage Schema.org type3 is still valid and still parseable — AI engines (Perplexity, ChatGPT, Claude) continue to extract Q&A from marked-up pages even though the Google accordion result is gone. The 2026 Squarespace rule: keep FAQPage on the dedicated /faq/ hub only, remove it from service pages and blog posts.

This leaf focuses on the Squarespace install for the one page where FAQ schema still belongs — the FAQ hub. The AI Overviews policy angle (what changed, why it matters, what Google did not say) is covered in detail at the AIO sibling leaf. This page is the install reference.

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.

The distinction worth keeping in mind: FAQPage as a Schema.org type (active, parseable by every consumer of structured data including AI engines) and FAQ as a Google rich-result feature (retired for non-government/health sites on 7 May 2026). Confusing the two produces bad advice in both directions — some designer blogs now say “remove FAQPage schema entirely,” which is wrong; some say “FAQPage schema still triggers Google rich results,” which is also wrong. The honest position: FAQPage is still valid, still useful for AI engine Q&A extraction, and no longer triggers the visible Google accordion result for most sites.

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.

Pre-2026, FAQ schema on service pages was a low-effort way to claim more SERP real estate — the FAQ accordion could double a result card's visible footprint. That benefit is gone. The remaining benefit (possible AI engine extraction lift) is real but unverified by any canonical Google source. Until a Google or AI-engine announcement confirms continued FAQ-schema weighting on non-FAQ-primary pages, treat the markup as having zero upside on service pages and blog posts. Removing it costs nothing; keeping it adds maintenance burden with no offsetting return.

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.

Google did not publish a blog post explaining the change. The deprecation appeared in the canonical FAQ documentation1 and was picked up by Search Engine Journal2 and other secondary coverage. The shift completes a narrowing that began in August 2023, when Google sharply reduced FAQ rich-result visibility for non-authoritative sites. The 2023 change reserved the feature for government and health; the 2026 change removed the visible result entirely for everyone else.

The 2026 FAQ deprecation in numbers

May 7, 2026

the date Google retired FAQ rich results in general Search for non-government, non-health sites.

Google Search Central · 2026-05-07
June 2026

FAQ rich-result support is scheduled for removal from Google's Rich Results Test.

Google Search Central · 2026
August 2026

FAQ rich-result report is scheduled for removal from the Search Console API.

Search Engine Journal · 2026-05

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.

  • @type: FAQPage — the top-level wrapper.
  • mainEntity — an array. Each element is a Question.
  • Question.@type — literal string “Question”.
  • Question.name — the question text as displayed on the page.
  • Question.acceptedAnswer — an Answer object.
  • Answer.@type — literal string “Answer”.
  • Answer.text — the answer text as displayed on the page. Plain text is preferred; basic HTML (<a>, <br>) is permitted but not recommended for AI engine extraction.

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.

JSON-LD FAQPage schema for a Squarespace /faq/ hub — replace questions with your real Q&A 
 <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "Do you take same-week appointments?", "acceptedAnswer": { "@type": "Answer", "text": "Yes when slots open. Book through the calendar on the home page; new clients usually find an opening within 7 to 10 days." } }, { "@type": "Question", "name": "Which insurance carriers do you accept?", "acceptedAnswer": { "@type": "Answer", "text": "BlueCross BlueShield, Aetna, Cigna, and United. Out-of-network superbills available on request." } } ] } </script>

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.

A second valid placement is the Code Block in the Squarespace editor — available on Business and above — which lets you drop a custom HTML block directly into the page body. Both work; the Code Injection approach is slightly cleaner because it keeps the markup separate from the visible content layout and survives template changes.

After saving, verify by viewing source on the live page (Ctrl+U on Windows, Cmd+Option+U on Mac) and searching for application/ld+json. The FAQPage block should appear exactly once. If two FAQPage blocks appear, you have either pasted the block twice or a sitewide Code Injection is also emitting an FAQPage — audit and remove one.

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.

The expected output of a clean validation in 2026: the Schema.org validator reports zero errors and (ideally) zero warnings; the Rich Results Test detects FAQPage and reports either “not eligible for FAQ rich result” (for non-government/health sites) or “eligible for FAQ rich result” (for government/health sites). Both outcomes mean the markup is well-formed; only the visible enhancement differs. Errors — missing mainEntity, malformed Question objects, smart-quote breakage — need fixing before the install counts as complete.

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.

A Squarespace-specific note on accordion blocks: when an FAQ section is rendered inside Squarespace's accordion block, the answer text is typically present in the DOM but visually collapsed. That keeps the markup compliant with Google's “all FAQ content must be visible to users” rule because the content is rendered to the page even if interaction is required to expand it. Verify by viewing source — if the answer text is in the HTML, you're compliant; if the accordion lazy-loads the content via JavaScript after expansion, you may not be.

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.

Keep reading · § 3.2