The 2026 copy-paste JSON-LD library for Squarespace
Schema & Structured Data for Squarespace
Copy-paste schema markup for Squarespace: 12 JSON-LD blocks, where each one goes in Code Injection, and which still earn rich results in Google in 2026. FAQ rich results ended on 7 May 2026 and HowTo in 2023, but that structured data still helps AI engines.
Two reasons schema deserves an entire pillar of its own in 2026. First, AI engines use structured data as a citation shortcut — Search Engine Land's GEO research15 finds JSON-LD collapses days of crawl-and-infer work into a single read, materially increasing the odds a page becomes the cited source. Second, Squarespace generates some schema automatically (Website, Organization, LocalBusiness, Product, Event and blog posts) but leaves the rest, such as the founder Person and BreadcrumbList, to the owner, and most owners never install any of it — making schema the single highest-leverage technical task on a typical Squarespace site.
JSON-LD is the JSON-shaped, script-tag-wrapped format Google recommends for telling search engines what a page is about. A block of JSON, placed inside a script tag with type application/ld+json, names the entities on the page (Article, Person, Organization, Product) and declares their properties (headline, author, price, address). Google's canonical guidance, last updated December 2025, names JSON-LD as the preferred structured data format for Search — over Microdata and RDFa, both of which are still parsed but no longer the recommended pattern.
The mental model: schema is the metadata layer of your page, written in a vocabulary every major search and AI engine understands. The HTML you write describes what a human sees. The JSON-LD you inject describes what a machine reads. The same page can be a well-written essay to a reader and a clearly-typed Article entity to Google's understanding layer at the same time — and the two layers do not interfere.
The vocabulary lives at schema.org11, a collaborative project originally launched by Google, Bing, Yahoo, and Yandex. The current version (30.0, March 2026) defines several hundred types and several thousand properties; in practice, a typical Squarespace site uses a dozen of them. The library on this pillar covers those twelve.
§02Why it matters now
Why schema matters more for AI engines than for Google in 2026
Schema started as a search-rich-results play. In 2026 the bigger payoff is AI engine citation. ChatGPT, Perplexity, Claude, and Gemini use structured data the same way they use bylines and inline sources: as a shortcut to confident attribution. A page with clean Article + Person + Organization schema gives an AI engine a one-read path to the entities behind the page; a page without it forces the engine to infer those entities from prose, which it does worse and trusts less. The practical consequence: schema lifts AI citation odds materially more than it lifts Google rich-result odds for most page types on a typical Squarespace site.
The reason is structural. Google has been parsing pages for two decades and inferring entities from clean HTML reasonably well; structured data was a nice-to-have unless you were chasing a specific rich result. AI engines, by contrast, are newer and rely on retrieval-time parsing rather than years of accumulated entity graphs. When ChatGPT-User or Perplexity-User fetches a page to cite, it has seconds to decide who wrote it, what business it represents, and whether the claim is supported — and JSON-LD answers all three questions on a single read.
The 2026 schema landscape in numbers
12
schema types cover the workload of a typical Squarespace site — the library on this pillar.
The 2026 rich-results landscape for Squarespace sites
The honest map of where Squarespace schema still triggers visible enhancements in Google Search in 2026: Article (recommended, no rich-result guarantee), LocalBusiness (knowledge panel surfaces), Product (rich snippets if Merchant Center aligned), Event (dated-event carousel), Review and AggregateRating (review snippets, with the self-serving disqualifier), Breadcrumb (URL-trail in results). What no longer triggers rich results in general Search: FAQ (retired 2026-05-07 for non-government, non-health sites), HowTo (retired September 2023, desktop and mobile).
The map matters because it changes the install priority. Pre-2023, the high-value schema types were Article + FAQ + HowTo. Today the high-value types are LocalBusiness + Product + Event for SERP visibility, and Article + Person + Organization for AI-engine citation. FAQ and HowTo schema still belong on the right pages — the FAQ hub, a genuine how-to article — but they no longer deliver the SERP enhancement they used to.
Squarespace schema at a glance
The 12 guides in install order: what Squarespace writes for you, what Google shows in 2026, and where each block goes.
Schema type
Squarespace auto-generates it?
Google rich result in 2026
Where to paste
Guide
Person
No, blog posts carry a bare author name
AI + validators onlyNo Google rich result; AI engines use it to attribute authors
“Site-wide Header” is the Header field of the site-wide Code Injection panel; “Page Header” is Page Header Code Injection under the page’s gear icon > Advanced. Squarespace’s automatic blocks can’t be edited or removed16, so the “Yes” rows get a supplemental block, never a second copy.
§04The install pattern
The Code Injection placement pattern on Squarespace
JSON-LD on Squarespace lives in Code Injection. Site-wide schema (Organization, sitewide breadcrumb rules) goes in the Header field of the site-wide Code Injection panel. Per-page schema (this Article, this Event, this Product when you're layering on Squarespace Commerce's auto-generated block) goes in Page Header Code Injection, under the page's gear icon > Advanced. Code Injection needs a Core, Plus or Advanced plan, or a legacy Business or Commerce plan that includes it. On Personal, JSON-LD is not installable inside Squarespace.
The split matters because of cardinality. An Organization entity describes the brand — it should fire once per page, defined once. An Article entity describes one specific page — it has to be defined per page. Putting an Article schema block in the site-wide header injects it onto every page, including the homepage and contact page, which is wrong and trips the Rich Results Test validator. Putting an Organization schema block in Page Settings only injects it on that one page, which is wasteful and means most of the site has no Organization signal.
§05The auto-emitted layer
What Squarespace already emits, and where it conflicts
Squarespace generates structured data automatically: Website, Organization, LocalBusiness, Product, Event and blog post blocks, built from your settings and content fields, and you can't edit or remove them. The auto-emitted layer is incomplete — it does not include author Person entities with sameAs, AggregateRating from reviews, openingHoursSpecification on locations, or any of the entity-level signals AI engines weight heavily. The 2026 install rule is: layer on top of the auto-emitted block, do not duplicate it. View source on a representative page and find-on-page for application/ld+json before authoring your manual block.
The hidden conflict is duplicate type emission. If Squarespace already emits a BlogPosting block on a blog post and you inject a second Article block at the page level, the page now has two JSON-LD blocks describing the same Article entity. Google's validator handles this by parsing both, which usually works but occasionally produces “duplicate entity” warnings. The cleaner pattern is to inspect what Squarespace emits, then extend it: since the automatic blocks can't be removed, add an @graph with only the missing entities and ship one manual block per page.
Three Squarespace-specific gotchas worth naming. First: the auto-emitted Product block on Commerce pages uses "@type": "Product" at the top level — if you wrap your additions in a second top-level Product block, the validator sees two Products on one page. Use @graph instead. Second: the auto-emitted BlogPosting block does not include the author's sameAs links — the Person entity it ships is a bare name with no entity wiring. Third: Squarespace does not auto-emit BreadcrumbList on any template I've audited, which means a 60-second install captures a meaningful AI-engine and SERP signal that the platform leaves on the table.
§06No-code route
How to add schema to Squarespace without writing code
You can get most of the way without writing any JSON-LD. Squarespace already generates Website, Organization, LocalBusiness, Product, Event and blog post structured data, and you can't edit or remove those blocks. Your job is to feed them: fill in Business Information so the Organization and LocalBusiness blocks carry a real phone number, address and opening hours, and complete the product, event and blog fields. Then test a live page in Google's Rich Results Test. For whatever is still missing, usually a founder Person and BreadcrumbList, copy a finished block from the library on this page, swap in your own details and paste it into Code Injection. That is editing, not coding.
Fill in Business Information. Open Settings, click Selling, then Business Information17, and add your contact phone, email, physical location and hours. On a client site we checked on 6 October 2026, the homepage carried Organization and LocalBusiness blocks built from those fields. A second Squarespace site with the panel left empty carried only a WebSite block.
Complete the fields Squarespace turns into schema. Squarespace lists blog post, event, local business, organization, product and website as the schemas it generates for you16. Empty fields produce thin blocks, so give every product a name, price, description and image, every event a date and location, and every blog post an author.
Test one live page of each type. Paste the URL into Google's Rich Results Test12 and read the detected items list. For types Google no longer shows as rich results, the Schema Markup Validator13 confirms the markup is still valid.
Fill the gaps with a copy-paste block. Open the matching leaf, such as Person schema for the founder, BreadcrumbList or a corrected LocalBusiness block, change the names, URLs and address to yours, and paste it in. Site-wide blocks go in the Code Injection panel; single-page blocks go in Page Header Code Injection, which you reach from the page’s gear icon under Advanced18. Code Injection needs a Core, Plus or Advanced plan, or a legacy plan that includes it18.
Third-party schema apps and widgets can also generate markup for you. If you use one, run the Rich Results Test again afterwards and check that it hasn’t added a second Organization or Product block on top of the one Squarespace already writes.
Free schema generator: Organization, LocalBusiness or Person
Fill in what applies; the JSON-LD block updates as you type, empty fields are left out, and nothing you type leaves this page. Keep the name, phone and address identical to Business Information, which Squarespace already turns into schema.
The validation workflow: Rich Results Test plus Schema.org validator
Two validators handle 2026 schema work. Google's Rich Results Test (search.google.com/test/rich-results) tells you whether Google sees the markup, parses the entities, and considers the page rich-result eligible — but only for the rich-result types Google still supports. The Schema.org Markup Validator (validator.schema.org) tells you whether the JSON-LD is structurally valid against the Schema.org vocabulary regardless of Google's rich-result decisions. Use both. Rich Results Test first for the types Google still surfaces; Schema.org validator for FAQ, HowTo, and any custom @graph composition that Google's tool no longer specifically tests.
The validators answer different questions. Rich Results Test answers “will Google show this as an enhancement?” (a Google-product question). Schema.org validator answers “is the markup structurally valid?” (a vocabulary question). A page can pass the Schema.org validator and fail to trigger a Google rich result — that's the FAQ scenario today, and that's fine if your goal is AI engine extraction rather than SERP visibility. Conversely, a page that fails the Schema.org validator probably won't be reliably extracted by anyone, AI engine or Google.
§08The library
The 12-type library, organised by install priority
Twelve schema types cover the work of a typical Squarespace site. The install order, in priority sequence: Person (the founder entity, anchors everything else) → Organization (the brand entity) → Article (every editorial page points its author at Person and its publisher at Organization) → BreadcrumbList (60-second sitewide install, lifts SERP appearance) → LocalBusiness or Service depending on business model → Product if you sell on Commerce → Event if you run dated events → Review and AggregateRating if you have independent reviews → FAQ on the FAQ hub only → HowTo on genuine how-to articles only. Skip the ones that don't apply. Author the rest in priority order.
Each leaf below covers one type. The structure is the same on every page: what the schema describes, when to use it, the current 2026 rich-results status from Google Search Central, the required and recommended fields, a full copy-paste JSON-LD example for a realistic Squarespace business (not an abstract one), where to paste it on Squarespace, validation steps, and the common gotchas that catch first-time installs.
Start with the leaf that matches the page you're working on right now. If you're not sure where to start, work top-down through the twelve guides below — the order is the install order.
Five mistakes account for most failed Squarespace schema installs in 2026: smart quotes in the JSON (the editor auto-corrects), duplicate type emission (Squarespace already emits blog post, Product, Organization and other blocks, so your block duplicates the auto-emitted one), site-wide injection of per-page schema (every page gets the same Article, all wrong), missing the application/ld+json mime type on the script tag (the block is then ignored by the validator), and claiming entities the page doesn't visibly support (FAQ schema on a page with no visible Q&A, Review schema on the business's own site).
The fixes are quick once you know what to look for. Author the JSON in a plain text editor (VS Code, TextEdit set to plain text), not in Squarespace's rich editor or Microsoft Word. View source on the live page after pasting and confirm the JSON renders as JSON, not as escaped HTML. Run the Rich Results Test on every page you've touched. The full diagnostic list lives on the JSON-LD Injection leaf.