Schema markup (structured data) is code—usually JSON-LD—that helps search engines interpret page content with more precision. Search engines can understand your site without it, but structured data clarifies meaning and can unlock rich results (enhanced search listings like stars, prices, event details, job boards, and recipe carousels).
This guide covers:
The markup Squarespace automatically generates
When to add additional schema
Known limitations in Squarespace’s implementation
Practical recommendations for staying compliant and future-ready
How to Add Schema Markup to Squarespace
Determine if custom schema is needed: Squarespace already generates structured data for several types of site content. Adding large, AI-generated schema graphs on top of it can create duplicate entities, conflicting business details, unnecessary properties, and markup that validators do not fully detect. Add only the specific markup a page actually needs.
Generate your schema: Once you have identified a specific reason for adding schema, use a schema generator or an AI tool to help create the JSON-LD. Verify every detail before publishing it—do not assume that valid-looking code is accurate or useful simply because an AI tool generated it.
Embed the markup: The majority of schema markup is specific to details on an individual page, so you’ll add it using a page’s advanced settings or a Code Block. Keep schema tightly aligned with the page’s visible content.
Alternatively, use sitewide code injection if the schema applies to every page.
Test your code: Use structured data testing tools to ensure your markup is error-free. Fix critical errors to be eligible for rich results. Complex schemas may require extra validation and fine-tuning. Refer to Schema.org guidelines to ensure accuracy.
💡 If you repeatedly add the same schema type (recipes, events, movie reviews), build a simple internal generator to standardize formatting and prevent inconsistencies.
Schema Basics
We offer a guide on structured data and schema markup, but here are some basics:
What is schema markup? Schema markup follows vocabulary defined by Schema.org. It provides structured signals about entities—people, organizations, products, articles, etc.
Why use schema? Adding schema can improve how search engines interpret and display your pages in their results. Schema can enable:
Star ratings
Pricing and availability
Recipe carousels
Event listings
Google’s job board
These enhancements may increase click-through rate (CTR). Important: Schema does not improve organic rankings. It affects display eligibility, not ranking position. Only certain structured data types enable rich results or specialized search results.
Do you need to add schema? Whether or not you should add schema markup to a Squarespace site depends on your specific needs and goals. Squarespace automatically generates default structured data for certain content types, which suffices for most sites. Additional markup is optional and depends on:
Whether your content qualifies for rich results
Whether your Squarespace pricing plan allows custom code
Whether enhanced visibility justifies the effort
Structured Data on Squarespace
Since 2016, Squarespace automatically injects structured data. It meets minimum requirements—but lacks flexibility and precision. You cannot remove their default schema.
To see the schema on any of your pages, use Schema.org’s validation tool.
Squarespace automatically adds these structured data types and properties:
-
WebSite markup includes:
URL
Site name (your Squarespace site title)
Logo
Description
Note: In Squarespace 7.0, the “Site Description” field populated the description property. In 7.1, the UI removed that field, but legacy values still output in schema with no edit control. If upgrading from 7.0 to 7.1, first remove the site description data (on the Basic Info panel) before upgrading.
Squarespace should offer user-editable schema, but until then they should pull description from the homepage’s meta description.
Ideally, Squarespace would also support alternateName.
-
For blog posts, article markup includes:
name (from the blog’s title tag)
URL
headline (blog post heading)
datePublished
dateModified
author
publisher (with the same Organization properties listed below)
image (blog thumbnail)
Improvements Squarespace could implement:
isAccessibleForFree
Expanded author fields
-
Squarespace’s Product markup currently includes:
name
image
description
brand
Offer (price, currency, availability, URL, and other properties based on product type)
Google Search Console often shows non-critical warnings due to missing optional properties—this is not an issue.
Squarespace could populate hasMerchantReturnPolicy by using the Return Policy set in the Selling/Checkout/Store Policies panel, but they do not.
-
Event markup includes:
name
startDate
endDate
image
location name
address
Missing but recommended properties that Squarespace should include:
organizer
offers
performer
eventStatus
description
-
Organization and LocalBusiness makeup is pulled from the Business Information panel.
For many online-only businesses, LocalBusiness schema is not appropriate. If desired, you can opt out of using Squarespace’s default Organization and LocalBusiness schemas by never filling in a site’s Business Information panel.
See the Critical Issues section below for more information.
Critical Issues with Google
If Google Search Console shows critical issues with your schema, this is often caused by removing information from the Squarespace Business Information panel. When information is saved on this panel, then removed, a site is (erroneously) left with empty schema markup. To prevent Google from showing “critical issues,” reenter the business name and at least one location field in the panel.
When to Add Schema to Squarespace
Schema markup is optional and not required for content to rank in standard search results or appear in AI answers.
Squarespace’s default schema meets the needs of most users, but it does not cover all schema types that can enable rich results. Notably, Google provides enriched search results for Recipes, Jobs, and Events.
Examples of schema you may want to manually add:
-
Use JobPosting schema if publishing job openings.
Proper markup enables eligibility for Google’s job board (shown above organic listings). This is especially valuable because aggregator sites dominate traditional rankings.
-
Use Recipe schema to qualify for Google’s recipe carousel.
Without it, recipe pages can rank and receive organic traffic—you just won’t appear in recipe grids.
-
Use Person schema when a specific individual is central to the site (e.g. consultant, author, founder, public-facing expert).
Markup can help:
Disambiguate common names
Connect the person to their organization
Align social profiles using sameAs
Clarify role, credentials, and expertise
Not required for AI visibility, but useful when personal authority and identity are core to the brand.
-
Use Review schema to enhance eligibility for review snippets.
-
Note that in 2023, Google reduced the visibility of FAQ rich results—meaning it no longer triggers expanded SERP listings.
It is not true that FAQ schema is necessary for inclusion in AI answers. Well-written HTML headings and clear formatting are readable by search engines and AI models.
-
If you have an issue with how your site name appears on Google, you can manually add AlternateName under Website schema.
Best practice is for only one WebSite schema block to be on a page, but duplication is fine until Squarespace supports this property natively.
Tips for Using Schema Markup
Keep it simple: Start with basic schema relevant to your site. Many sites do not need anything beyond what Squarespace already generates. Before tackling complex schema details, make sure you’ve completed a Squarespace SEO checklist.
Note that Google can accurately interpret structured data whether it is in separate blocks or a connected graph. However, using a connected graph can help ensure consistency and avoid potential conflicts.
Follow the applicable rules: Schema.org defines the vocabulary, while individual search engines and platforms determine which markup they support and how they may use it. Follow Google’s guidelines and updates when targeting Google search features, and check documentation because eligibility requirements can change.
Monitor supported features: When Google provides a rich result report in Search Console, use it to identify invalid items and changes in eligibility. Don’t assume every valid schema type will appear in Search Console.
Keep it accurate: Update the markup when the corresponding page content, business details, availability, dates, prices, or other marked-up information changes.
A Warning About AI-Generated Schema
Do not paste a Squarespace URL into an AI tool and assume the resulting schema markup is appropriate. AI tools are happy to generate schema whether a site needs it or not.
AI can help explore possible schema types and format verified information as JSON-LD, but it should not be treated as evidence that additional markup will improve SEO or AI visibility. For most Squarespace sites, start with what the platform already provides and add custom schema only when it supports a specific feature or clearly defined use.
Squarespace Schema Issues
Most readers can skip this section. This section is primarily intended for the Squarespace development team—they misunderstand and under-appreciate technical SEO details, such as robots.txt, hreflang, sitemaps, AMP, clean HTML, and schema.
While Squarespace’s schema implementation doesn’t follow best practices, it won’t impact your site’s organic search rankings. Google does not penalize sites for empty, redundant, or repetitive schema; however, the persistent issues remain frustrating:
-
Squarespace blogs still include legacy hentry microformat markup.
Modern structured data via Schema.org takes precedence, but this redundancy is unnecessary.
-
Squarespace outputs Organization and LocalBusiness schema on all pages—even when not contextually relevant.
Google recommends placing structured data only where applicable.
No ranking impact observed, but inefficient.
-
For many sites, the LocalBusiness schema is not appropriate. Squarespace has been aware of the issue since at least 2019, but it’s never been addressed.
The ability to select specific schema.org subtypes for some organizations would be preferred.
-
Squarespace’s LocalBusiness schema does not properly model multi-location businesses.
However, Google primarily relies on your Google business listings for location authority, mitigating most impact.
To avoid many of these issues, users should not fill out the Business Information section unless they have a single brick-and-mortar location. Squarespace moved this section to the Selling panel which helps prevent all users filling it out by default.
Takeaways
Schema does not improve rankings.
It may improve search result listings and CTRs.
Squarespace covers the basics.
Add markup if it unlocks meaningful features.
Validate, monitor, and keep it accurate.
Done correctly, structured data can strengthen how AI systems and search engines interpret your content—without requiring a full rewrite of your site.
Helpful Resources
Introduction to Structured Data Markup by Google
General structured data guidelines from Google
Troubleshooting tips from Google
Need help getting schema right?
We help small teams implement markup that matters.
Book a Zoom. Real guidance, fast.
