DEV Community: JSON Schema App

JSON vs JSON-LD in SEO: Why the Difference Matters for Squarespace Users

JSON Schema App — Tue, 19 May 2026 10:12:45 +0000

Most Squarespace site owners figure the platform handles structured data for them. It injects the schema automatically, so what's the problem? The issue is that there's a real difference between JSON and JSON-LD, and Squarespace's built-in output doesn't go far enough. This piece explains what that difference is, where the platform falls short, and why it matters for how a site shows up in search.

JSON vs JSON-LD: What’s the Difference?

JSON (JavaScript Object Notation) is a general-purpose data format used in APIs, config files, and app communication. It's clean and readable, but it carries no meaning on its own. If a file contains "name": "Harlow Studio", a machine sees two strings. It doesn't know if that's a business name, a product name, or someone's first name.

JSON-LD uses the same syntax but adds two fields that change everything: @context and @type. The @context links the data to Schema.org, a shared vocabulary built by Google, Microsoft, Yahoo, and Yandex together. The @type tells crawlers exactly what kind of entity the page is about, a local business, a product, a blog post, a FAQ page. That combination is what turns raw data into something a search engine can actually interpret and act on.

JSON-LD also lives in a < script type="application/ld+json" > tag in the page head, separate from the HTML. On Squarespace, where page templates are locked, schema can be updated without touching any visible content on the page.

Limitations of Squarespace’s Default Schema Markup

Squarespace has been auto-injecting structured data since 2016. Blog posts get basic Article markup, headline, author, and publish date. Product pages get Product schema. Events get Event markup. It's all server-side rendered, so it's clean and crawlable without any JavaScript dependency. That's genuinely useful as a starting point.

The trouble is what Squarespace doesn't generate. There's no FAQPage schema, even on pages built entirely around questions and answers. No HowTo markup on step-by-step guides. No AggregateRating on review content. The detailed LocalBusiness fields that power Knowledge Panels and Maps listings, hours, service area, and coordinates are also absent. So are nested Person details for author credentials, which carry real weight for E-E-A-T.

Google doesn't hand out rich results just because schema is present somewhere on the page. The markup has to match the exact structure tied to each feature. A generic Article block will never earn FAQ dropdowns in search results, which requires a properly nested FAQPage block, which Squarespace simply doesn't create. A good Squarespace schema markup tool is designed specifically to fill in those missing pieces.

What Schema Squarespace Generates Automatically

Squarespace does generate some structured data automatically, but it’s fairly limited in scope. Basic Article schema is usually added for blog posts, covering simple fields like the headline and publish date. That’s helpful as a starting point, but most of the schema types that actually improve rich results and AI visibility still need to be added manually.

For example, the FAQPage schema is not automatically created by Squarespace, even if a page contains FAQ-style content. The same goes for detailed LocalBusiness schema, AggregateRating or review markup, HowTo schema, and Person schema for author credentials or expertise signals. These all require manual implementation if the goal is to give search engines a clearer context and improve how pages appear in search results.

How JSON-LD Improves Rich Results and CTR

Pages with rich result features consistently outperform plain blue links. Rotten Tomatoes found a 25% higher click-through rate on pages with structured metadata versus unstructured ones. At scale, that difference adds up quickly.

It's not complicated, why? A rich result takes up more space on the page, shows ratings or pricing or expandable FAQs before anyone clicks, and reads as more credible than a plain listing next to it.

Three near-identical pages were tested with structured data as the only variable. Only the page with proper JSON-LD appeared in a Google AI Overview, the no-schema page wasn't even indexed. With AI Overviews now appearing on 50-60% of searches, and tools like Gemini and Perplexity using structured context to build answers, that's a result worth paying attention to.

A Real Example of JSON-LD on a Squarespace Site
Here's a LocalBusiness block that a Squarespace service site would need to add on its own; the platform won't produce this level of detail automatically:

{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Harlow Studio",
"url": "domain name",
"telephone": "+1-512-555-0174",
"address": {
"@type": "PostalAddress",
"streetAddress": "318 South Congress Ave",
"addressLocality": "Austin",
"addressRegion": "TX",
"postalCode": "78704",
"addressCountry": "US"
},
"openingHours": "Mo-Fr 09:00-18:00",
"priceRange": "$$"
}

Take out @context and @type, and this becomes plain JSON. Google's structured data parser won't touch it, and no rich result becomes possible.

Getting it onto a Squarespace page takes two routes. For schema that applies everywhere, Organization, WebSite, go to Settings → Advanced → Code Injection → Header and paste it there. For page-specific types like FAQPage or Product, use a Code Block inside the page editor instead. Paste the JSON-LD, turn off "Display Source Code," and it stays invisible to visitors but fully readable to crawlers.

Before calling it done, run everything through Google's Rich Results Test or schema.org/validator. Missing required fields are the single most common reason technically correct markup still fails to show rich results in search.

Why Manual JSON-LD Management Becomes Difficult

Hand-coding JSON-LD for one or two pages is manageable. On a site with dozens of service pages, blog posts, and product listings, it becomes a real maintenance problem. The schema needs to stay current, wrong business hours or outdated pricing generate Search Console warnings and quietly cost rich result eligibility.

A good Squarespace schema markup tool scans pages, generates valid JSON-LD, and deploys via script injection without requiring any coding. The critical feature is that it checks Squarespace's existing auto-generated schema before adding anything new. Custom markup that overlaps with the platform's output causes Google to discard both, and that's easy to miss. Understanding how to add schema in Squarespace correctly includes knowing that an overlap issue exists.

Frequently Asked Questions

Is JSON same as JSON-LD for SEO?
No. JSON is just a data format with no semantic meaning, search engines don't interpret it as structured data. JSON-LD adds @context and @type that link the content to Schema.org, which is what makes rich result eligibility possible.

Does Squarespace automatically add structured data?
It adds the basics, articles, products, events. But FAQPage, HowTo, detailed LocalBusiness, and AggregateRating markup all need to be added separately, either manually or through a schema tool.

Does JSON-LD help with appearing in Google AI Overviews?
Based on current evidence, yes. The 2025 Search Engine Land experiment found that the page with proper JSON-LD appeared in AI Overview citations while the no-schema page went unindexed entirely.

Wix Schema Markup Guide 2026: How to Get Rich Results (Step-by-Step)

JSON Schema App — Thu, 16 Apr 2026 12:36:27 +0000

You can build a clean, fast, and well-designed Wix website and still feel like it’s not getting the attention it should on Google. It’s more common than you’d think. The content may be solid and the pages optimized, yet something still feels off when your search listings don’t look as detailed or engaging as others.

A lot of that comes down to how clearly your content is structured for search engines. With Wix schema, you’re helping Google better understand what your pages are about instead of relying only on basic text. It works in the background, but it can shape how your content shows up in search results.

Understanding How Schema Works on a Wix Website

Schema markup is structured data that helps search engines understand your content more clearly. Instead of relying only on context, Google reads defined labels that explain what each part of your page represents.

There’s also a performance angle to it. Industry studies suggest rich results can improve click-through rates by around 20-30%, mainly because listings look more detailed and visually appealing. It doesn’t directly boost rankings, but it often brings in more clicks.

On Wix, some schema is added automatically for blogs, products, and basic pages. The problem is, it’s usually generic and doesn’t always match your actual content. For instance, a blog may include Article schema but miss out on FAQ or How To markup, even when it’s relevant.

When you start adding schema manually, you get more control over how your content is defined. This reduces confusion for search engines and helps them process your pages more accurately, increasing your chances of appearing in richer search results.

Why Structured Data Impacts Rich Results Visibility

Google treats structured data as a supporting signal rather than a direct ranking factor, and that distinction is important. Schema won’t push your page higher on its own, but it can significantly influence how your listing appears in search results.

When implemented correctly, schema helps your page become eligible for enhanced search features like FAQ dropdowns, breadcrumbs, and product details. Technically speaking, these features are triggered when Google’s systems can confidently match your structured data with what’s actually visible on the page.

If your schema communicates something different from your on-page content, there’s a good chance it will be ignored altogether. Keeping both aligned is what makes the markup effective.

Schema Types That Work Well with Wix SEO

For most Wix websites, a handful of schema types consistently deliver better visibility. When the structure aligns with the content, Google can process it more confidently and display richer results.
Here are the schema types that tend to work best:

Article Schema

Best suited for blog content. It helps define key elements like the headline, author, publish date, and article type. This gives Google better context about your content and can improve how quickly and accurately it gets indexed.

FAQ Schema

Works well when your page directly answers common questions. If your content is structured in a Q&A format, this schema can help your listing appear with expandable questions in search results, which often improves visibility and clicks.

Local Business Schema

Important for service-based or location-specific websites. It reinforces details like your business name, address, contact info, and operating hours, helping Google connect your site with local search queries.

Product Schema

Essential for Wix eCommerce stores. It allows search engines to display pricing, availability, and sometimes reviews directly in search results, making your listing more informative before users even click.

Instead of stacking multiple schema types on a single page, it’s more effective to focus on the one that best represents your content.

Also, there are other schema types like Webpage, Breadcrumb, Video, Person, and Event schema that can be useful in specific situations. These aren’t required for every Wix site, but they can add value when they naturally fit the content.

Implementing JSON-LD Schema on Wix

Wix allows you to insert custom structured data through its SEO settings. The recommended format is JSON-LD, as it is easier to manage and preferred by Google.

To implement it, open your page settings >> navigate to advanced SEO options, and locate the structured data field. This is where your code goes.

Paste your code here:

Here’s a clean example of FAQ schema:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is Wix schema markup?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Structured data that helps search engines understand Wix pages."
      }
    }
  ]
}

Once added, publish the page and test it using Google’s Rich Results Test. Validation is important because even minor syntax errors can prevent your schema from being processed.

What to Expect After Adding Schema Markup

Schema implementation doesn’t produce instant changes, but it improves how your pages are processed over time. Once Google re-crawls your site, your pages may begin to qualify for enhanced search features.

Using a JSON schema app makes this process much easier and more efficient. Instead of manually handling structured data, it helps automate how your pages communicate key information, allowing search engines to interpret your content more accurately with less effort.

FAQs

What is Wix schema markup in simple terms?

It’s structured data added to your Wix site that helps search engines understand your content more clearly. This improves how your pages appear in search results.

Does Wix automatically add schema?

Yes, but only basic schema. For better results, adding custom structured data manually is usually necessary.

How do I check if my schema is working?

You can use Google’s Rich Results Test tool. It shows whether your markup is valid and eligible for enhancements.

Can schema improve my rankings directly?

Not directly. It improves how your listing appears, which can lead to higher click-through rates over time.