Aizii Learn · AI Search

[← Back to Learn](https://aizii.ai/learn)

# How to add product schema on Squarespace

On Squarespace, the platform adds basic structured data to product pages automatically, but that built-in markup is locked: you cannot edit it, extend it, or complete its missing fields from inside Squarespace. The only way to add real Product markup is to inject your own JSON-LD, and code injection is gated behind a paid plan that includes it. Squarespace has renamed its plans over time, so check your current plan details, but the rule is stable: the entry-level plans do not include code injection, the mid-tier plans and up do. The one constraint shaping everything on Squarespace is that injected markup is static text on a page. It does not update when you change the price in the product editor, so it goes stale unless you maintain it.

## Why Squarespace is different

Squarespace is the most limited platform in this series for structured data, and that limitation is structural. There is no template access, no plugin system for schema, and no settings panel for markup like Wix has. The built-in product schema stays thin no matter what you do, and filling in more product fields in the editor does not complete it. Your options are per-page injection (a header code field on each product's page settings, manual for every product) or site-wide injection (one shared header field under Settings and then Advanced and then Code Injection, which cannot carry per-product data). Neither is dynamic. A Squarespace store with real product schema is a store whose owner pastes and maintains JSON-LD by hand.

## Steps

**1\. Check what already exists.** Open a live product page, view the page source, and search for `application/ld+json`. You will find the built-in block. Read it and accept what it is: a starting point you cannot improve in place.

**2\. Confirm your plan supports code injection.** If your plan does not include it, the per-page and site-wide injection fields will not be available, and the decision is whether the upgrade is worth it for your catalog size. Do not buy an upgrade for schema alone on a three-product store; do the math on a fifty-product one.

**3\. For a small catalog, inject per product.** Open the product page, go to its Settings, then the Advanced tab, and paste a complete Product JSON-LD block into the Page Header Code Injection field, with that product's actual name, price, currency, availability, and image URL. Save, publish, and confirm in the page source that both the built-in block and your block are present and do not contradict each other on price or availability. Repeat for each product.

**4\. Maintain it like inventory.** This is the step people skip. When you change a price, run a sale, or sell out, the injected block does not know. Update the JSON-LD in the page's code injection field at the same time you update the product, or the markup becomes the stale-facts problem the pillar warns about: engines catch the mismatch between markup and page and trust neither number.

**5\. For a large catalog, be realistic about the ceiling.** Per-page injection does not scale to hundreds of products with changing prices. Your practical options are keeping the built-in markup and making sure every product field it reads is filled in, maintaining injection on your top sellers only, or accepting that Squarespace is the wrong platform for a catalog whose facts change daily.

**6\. Validate.** Test a URL such as https://\[yourdomain.com\]/shop/your-product, replacing yourdomain.com with your actual domain, in Google's Rich Results Test and the Schema Markup Validator. Test an out-of-stock product and confirm the injected availability value matches the page.

### The fundamentals

-   •The complete JSON-LD reference this article builds on, see our [product schema guide](https://aizii.ai/learn/ai-search/how-to-add-product-schema-markup-for-ai-search)
-   •Whether AI crawlers can reach your pages at all, see our [robots.txt guide](https://aizii.ai/learn/ai-search/how-to-write-robots-txt-for-ai-search)
-   •A readable catalog summary for AI engines, see our [llms.txt guide](https://aizii.ai/learn/ai-search/how-to-write-a-good-llms-txt-file)

### A hypothetical example

Say you run a ceramics studio on Squarespace with twelve products and prices that change twice a year. You check the page source, find the thin built-in block, and confirm your plan includes code injection. You paste a complete JSON-LD block into each product page's header injection field with the real price and availability, validate one page, and add "update the schema block" to your price-change checklist. Twelve pages, twenty minutes, done. If that studio grew to two hundred products with weekly price changes, this method would stop being viable, and that is the point at which the platform becomes the constraint.

## What this guide does not cover

This covers getting valid product markup onto your Squarespace product pages within the platform's real limits. It does not cover keeping that markup accurate as inventory changes beyond the manual maintenance described above, getting AI crawlers to your pages, or letting an agent complete the checkout, which is the transaction layer and a separate job.

## Frequently Asked Questions

Does Squarespace automatically include JSON-LD on product pages?

Yes. Squarespace outputs standard Product and Offer schema for all store items by default.

Can I add custom JSON-LD to Squarespace product pages?

Yes. On business and commerce plans, you can paste custom schema into Page Settings under Advanced Code Injection.

How do I prevent duplicate schema when adding custom code in Squarespace?

Do not duplicate the core Product node. Instead, use code injection to append specific missing nodes like MerchantReturnPolicy.

## Check your own brand now

Run the free scan. It takes seconds, no signup, and shows whether AI crawlers can read your product pages today: aizii.ai/aeo-scan

[Run the free scan](https://aizii.ai/aeo-audit)