The Code Injection JSON-LD pattern
Every JSON-LD block on Squarespace follows the same shape: an HTML script tag with type='application/ld+json', a JSON object inside, and the entire block pasted into the Header field of the relevant Code Injection panel. The outer wrapper is always the script tag; the inner content is always valid JSON; the JSON's '@context' is always 'https://schema.org'; the '@type' is whatever schema you are installing. Get any of those four invariants wrong and the parser silently ignores the block.
Site-wide Organization injection (the homepage)
Organization schema identifies your brand as an entity to Google, ChatGPT, Perplexity, and the Knowledge Graph. The block belongs in Settings > Advanced > Code Injection > Header — site-wide, because the brand is the brand on every page. Required properties are name and url; recommended properties are logo, sameAs (your social profile URLs), and contactPoint. The pattern below is production-ready for a single-brand site.
Per-page Article injection (a blog post)
Article schema completes the structured data Squarespace's default Article emission omits: full author and publisher blocks, datePublished and dateModified ISO strings, and the image array. The block belongs in Page Settings > Advanced > Page Header Code Injection on the individual blog post (Business plan or above). Required properties are headline, author, publisher, datePublished; recommended are image and dateModified. The pattern below validates against Google's Rich Results Test for the Article rich result.
LocalBusiness on the service page
LocalBusiness schema identifies your business as a physical entity with an address, phone, and hours. For a single-location business, the block belongs site-wide in Settings > Advanced > Code Injection > Header. For multi-location businesses, ship per-location LocalBusiness blocks on each location page via Page Settings > Advanced > Page Header. Required properties are name, address, and either geo coordinates or telephone. The pattern below covers a single-location service business.
The Core-plan fallback when per-page injection is unavailable
The Core plan permits site-wide Code Injection but blocks the per-page panel. Per-page schema like Article therefore cannot use its native placement on Core. The workaround is a single site-wide Header block that contains a JavaScript snippet which conditionally injects the right schema based on the current URL. Functional, brittle, and an argument for upgrading to Business — but it works.
Validate every block before walking away
After every injection, open Google's Rich Results Test (https://search.google.com/test/rich-results) and paste the live URL the schema applies to. The tool fetches the rendered HTML, parses every structured data block, and reports validation errors plus rich-result eligibility. A clean validation shows no errors, no warnings (except 'recommended properties missing' which are non-blocking), and a 'Page is eligible for rich results' confirmation. Run Schema.org's validator in parallel for structural correctness independent of rich-result eligibility.
Freshness — when to update the injected schema
Schema is not set-and-forget. Update Organization sameAs when you add a social profile. Update LocalBusiness hours when you change hours. Update Article dateModified whenever you meaningfully edit the post (typo fixes do not count; new sections do). Update Product price and availability whenever they change. Stale schema is a passive ranking-and-AIO penalty: the engine reads the structured data, notices it contradicts the page content, and lowers its trust in the page as a citation candidate.