How to Add JSON-LD Code to Wix

To add JSON-LD to a Wix page, open its SEO settings, find Structured Data Markup, and add markup that matches the page's visible content. Publish the page, then test its URL with Google's Rich Results Test. For pages that pull changing data from a CMS collection, use Wix's page-type SEO settings or Velo to keep the markup up to date.

JSON-LD helps search engines understand details such as products, prices, and events. Wix already adds some structured data automatically, so check what's there before adding more. Extra markup can conflict with Wix's existing markup, and valid code does not guarantee a rich result.

I'm Athena Kavis, a Wix Partner since 2019 who has designed more than 1,000 websites. When setting up structured data and custom JSON-LD code, Wix provides several straightforward options to help you build on what the platform already includes and add only what your site needs.

Understanding Structured Data and Native Wix Schema Automation

Structured data is a standardized format that provides search engines with explicit clues about the meaning of a web page. Rather than forcing search engine bots to guess whether a string of text represents a price, an author name, or a customer review score, JSON-LD (JavaScript Object Notation for Linked Data) organizes that information into clear machine-readable code.

Across the web, over 2.6 million websites run on Wix. To simplify technical optimization for this large user base, Wix automatically creates Rich Result-optimized JSON-LD structured data for several vertical applications. When you publish a blog post, host an event, or launch an online store, Wix injects standard schema into the page source behind the scenes.

However, relying entirely on automated presets can leave noticeable gaps in your search appearance. For instance, Wix Stores automatically generates Product schema containing the product name, description, image, and base price. Yet, out-of-the-box automation frequently omits commercially vital attributes such as aggregateRating, gtin (Global Trade Item Number), mpn (Manufacturer Part Number), and detailed brand properties.

Search engines look for these specific properties to award enhanced rich snippets in organic search results. Omitting them means missing out on prominent search enhancements like star ratings, in-stock badges, and detailed price drop indicators. If you want to capture higher click-through rates, pairing your site with dedicated SEO services helps identify where automated markup falls short and where custom data structures are required.

How Out-of-the-Box Markup Works on Wix Verticals

Wix handles structured data across distinct vertical pages by injecting markup directly into the server-rendered HTML. This server-side delivery ensures that crawlers read the data immediately upon the initial HTTP request without waiting for client-side scripts to execute.

Here is how Wix automatically handles different vertical page types:

• Wix Stores: Injects Product schema, BreadcrumbList markup, and basic organization details for every active catalog item.
• Wix Blog: Produces Article or BlogPosting schema that pulls the headline, featured cover image, publish date, and author name directly from your post editor.
• Wix Events: Automatically generates Event markup including event name, start and end times, location, and ticket availability status.
• Wix Online Programs/Courses: Generates Course schema detailing program titles, descriptions, and learning structures.
• Local Business Automation: When you enter a verified physical business address in your dashboard business info settings, Wix automatically generates LocalBusiness schema site-wide.

The technical team behind Wix continuously updates these out-of-the-box presets whenever Google adjusts its rich result guidelines, saving merchants from manually rewriting basic structures.

When to Override or Extend Native Wix Structured Data

While automatic presets are convenient, they are intentionally generic. When your store sells branded goods or collects third-party product reviews, you will need to extend or override Wix's native schema.

Common scenarios where default schema should be modified include:

1. Adding Merchant Identifiers: Providing valid gtin8, gtin13, or mpn identifiers so Google can match your products against global shopping catalogs.
2. Injecting Review Aggregates: Adding third-party rating data via aggregateRating to qualify for review star snippets in search results.
3. Preventing Schema Duplication: If you add custom markup through an external script or app without turning off the default preset, search engines may detect conflicting @type definitions. Wix allows you to open your dashboard SEO tools, preview the preset, and convert it into custom markup that you can safely modify.

Core Methods to Implement JSON LD Code Wix Sites Require

Adding custom structured data to a Wix website generally follows two main paths: the visual SEO settings interface inside the dashboard or custom code scripts. Whether you need a simple FAQ block or a full product graph, the right JSON LD code Wix implementation depends on how static or dynamic your page content is.

Adding Custom JSON LD Code Wix Static Pages Need via SEO Settings

For static landing pages, about pages, and contact forms, the most straightforward approach is using Wix's built-in SEO panel.

To add schema to an individual static page:

1. Open your site inside the Wix Editor or Wix Studio.
2. Select the page you want to edit from the Pages menu and open its SEO Settings.
3. Navigate to the Advanced SEO tab.
4. Locate the Structured Data Markup section and click Add New Markup.
5. Paste your formatted JSON-LD code into the text field.
6. Click Apply and publish your site.

For dynamic item pages connected to CMS collections, Wix Studio and the standard dashboard SEO Tools allow you to define structured data at the page-type level. As outlined in the Wix dynamic schema forum guide, you can paste a JSON-LD template and use variable tokens to dynamically map CMS dataset fields (such as item title, price, or description) directly into your schema properties.

Programmatic JSON LD Code Wix Dynamic Pages Require via Velo API

When your website requires complex conditional logic—such as appending review ratings only when reviews exist, or formatting variants with custom inventory rules—visual settings may not provide enough flexibility. In these instances, you can use Velo, Wix's full-stack development environment to write custom JSON LD code Wix pages can render dynamically.

With Velo, you can read records from Velo database collections and use the setStructuredData() API to build your JSON-LD object dynamically. This method injects structured data into the server-rendered page head, ensuring search engine bots capture the dynamic markup in the initial HTML response.

When working with Wix APIs integration, setStructuredData() accepts an array of schema objects and replaces any pre-existing structured data object of the same @type rather than merging with it.

If you are new to developer tools on Wix, reviewing Velo 101 development will help you understand page lifecycle hooks, such as running your code within the dataset's onReady handler to prevent missing data errors.

Structuring Complex Schema: Multiple Types and Entity Optimization

Modern search engines do not look at web pages in isolation; they analyze how different concepts connect. Rather than adding isolated blocks of schema, structuring your code as a connected entity graph helps search engines understand your brand, locations, products, and authors.

There are two primary ways to handle multiple schema types on a single Wix page:

• Separate Script Blocks: You can add multiple independent JSON-LD blocks using the "Add New Markup" button in the Advanced SEO panel. This works well when adding an independent FAQPage schema alongside an existing service page.
• The @graph Array: By grouping multiple nodes within a single @graph array, you can establish explicit relationships between entities using persistent @id references.

Connecting Related Entities with Persistent Identifiers

An @id URI acts as a unique, persistent identifier for a specific entity. By establishing consistent @id strings across your website, search engines can connect different mentions of your brand into a single node within Google's Knowledge Graph.

For example, your homepage can define your core organization entity:

• Organization @id: https://www.quixsites.com/#organization

When you create product pages, blog posts, or local landing pages, you can reference that exact @id inside the publisher, brand, or provider fields without re-declaring your entire company history on every single URL.

For multi-location businesses, maintaining consistent Name, Address, and Phone (NAP) details within your LocalBusiness schema is critical for local search visibility. Discrepancies between your schema, on-page text, and external business citations can confuse search engines and dilute local search authority.

Leveraging Structured Data for Google AI Overviews and Brand Authority

As generative engines and AI Overviews summarize the web, machine-readable structured data plays an increasingly vital role in how your business is understood. Generative models prioritize sources that present structured, disambiguated facts that directly align with visible on-page content.

Following proven methods for optimizing JSON-LD for AI search perception allows search algorithms to parse facts—such as pricing, return policies, organizational leadership, and service specialties—without misinterpretation.

Ensure that all data contained within your JSON-LD matches the text visible to human visitors. Discrepancies between hidden schema attributes and visible page text can lead to rich snippet suppression or inaccurate AI summaries.

Troubleshooting and Validating JSON-LD Structured Data on Wix

Even minor syntax mistakes can cause search engines to ignore an entire structured data block. Testing your code before and after publishing is an essential part of schema management.

When working with advanced Wix coding techniques or manual script injection, use the following validation process:

1. Pre-Deployment Syntax Check: Validate raw code using a JSON syntax checker to ensure all commas, braces, and quotes are properly placed.
2. Schema Markup Validator (Schema.org): Test your code against official Schema.org standards to verify that all properties belong to the selected @type.
3. Google Rich Results Test: Run your live, published URL through Google's Rich Results Test to confirm eligibility for rich snippets.
4. Google Search Console: Monitor the Enhancements tab in Google Search Console over a period of 2 to 4 weeks to identify any site-wide warnings or crawling errors.

Diagnosing Common Schema Validation Errors and Warnings

Understanding the difference between validation errors and warnings will help prioritize your technical fixes:

• Critical Errors: Issues that prevent search engines from parsing your data and completely disqualify the page from rich snippets (e.g., missing @context, missing @type, or missing required fields like name or offers).
• Non-Critical Warnings: Suggestions for optional properties that provide extra context (e.g., missing priceValidUntil or sku) but do not disqualify the page from showing rich results.

Common Wix-specific implementation pitfalls include:

• Internal Media URLs: Wix stores media using internal paths (such as wix:image://). Always replace internal tokens with the public, fully resolved https:// image URL when manually writing JSON-LD.
• Incorrect Date Formatting: Dates for events or blog postings must follow the ISO-8601 standard (for example, 2026-10-15T09:00:00Z).
• Duplicate Identifiers: Reusing the same @id for two different entity types on the same page will cause validation parsers to reject both nodes.
• CDN Caching Delays: After updating structured data on a Wix page, clear your browser cache and purge external CDN caches before re-testing in Google's Rich Results tool.

Frequently Asked Questions About Wix Structured Data

Does Wix automatically add JSON-LD to every page?

Wix automatically adds structured data to major vertical pages, including Wix Stores products, Wix Blog posts, Wix Events, and Wix Bookings. For blank, standard static pages, Wix provides basic WebSite and WebPage metadata, but custom schema such as FAQPage, Service, or detailed LocalBusiness markup must be added manually through the SEO Settings panel or via Velo.

Can I use multiple JSON-LD script blocks on a single Wix page?

Yes. Wix supports multiple JSON-LD script blocks on a single page. You can add multiple separate blocks using the "Add New Markup" feature in the page's Advanced SEO settings, or group related entities together within a single script using a @graph array. Ensure the entities in each block complement one another and do not contain contradictory information.

Will adding custom JSON-LD schema guarantee Google rich results?

No. Valid JSON-LD markup makes a page eligible for rich results, but it does not guarantee inclusion. Google's algorithms determine whether to display rich snippets based on search intent, overall domain quality, user location, and whether the structured markup accurately matches visible on-page content.

Conclusion

Structured data is a powerful tool for clarifying your website's content, qualifying for rich search snippets, and establishing your brand's presence across AI search systems. By understanding the balance between native Wix automation, visual SEO settings, and programmatic Velo code, you can build an error-free structured data setup that elevates your search performance.

At Quix Sites, we build high-performance websites tailored to modern search requirements. If you are looking to enhance your digital presence with custom structured data or bespoke website functionality, schedule a consultation for expert Wix development and SEO with our team.