In short. Check Wix’s JSON-LD requirements, edit the responsible markup settings, test the live URL and validate reported fixes in Search Console.
Definition: Structured data markup is a standardized format for describing a page to search engines. Troubleshooting it in Wix involves checking code in JSON-LD, a format for expressing structured data, correcting errors in the relevant SEO settings, and testing the live page for Google's supported rich results, such as product previews.
Key facts
- As of October 2026, Wix's markup troubleshooting guide requires JSON-LD with a single script element and one main markup type per block.
- Wix's adding-markup documentation sets a limit of fewer than 7,000 characters for an individual markup addition. Some pages, including Wix Stores product pages, already have preset markup.
- Google's Rich Results Test help describes testing either a URL or pasted code and expanding detected items to locate errors.
- The Schema.org Markup Validator accepts URLs or supplied markup and identifies syntax mistakes in Schema.org structured data.
Where is the faulty markup edited?
Wix's SEO Page Settings directory links to separate guides for markup errors and rich result eligibility. The distinction helps locate the next check: an error while adding code calls for Wix's format checks; a missing rich result calls for testing the live URL and Google's requirements.
For a manually added block, Wix's adding guide places the controls under the page's SEO basics, then Advanced SEO and Structured Data Markup. The block's action menu provides editing and testing controls. Preset markup for page types is managed through the site's SEO Settings, so the correction belongs in the settings responsible for that markup.
What makes Wix reject the code?
Wix's troubleshooting guide specifies an opening script tag with the application/ld+json type and a closing script tag. HTML inside the JSON-LD, such as a strong tag, fails its validation.
The same guide calls for straight quotation marks, commas between properties, and no trailing comma after the final property. A property fragment using the values in Wix's example looks like this:
"name": "Wix.com",
"alternateName": "Wix"
This is a fragment for checking punctuation. Each field stays on a single line; a literal line break within a field is another documented cause of rejection.
Which validation tool should be used?
Google's Rich Results Test documentation describes selecting Code to test a pasted snippet, changing it, and rerunning the test. Selecting URL checks the page available online. Expanding an error opens its location in the rendered source code, which is the code after page processing.
The same documentation warns that the test ignores JSON-LD comments even though the format's standard does not support them. Comments therefore need removal before publication.
The Schema.org validator documentation describes a broader vocabulary check: it extracts structured data and reports syntax mistakes. Google's tool checks supported search result features. Wix's eligibility guide also recommends checking whether the expected result type is supported and using URL Inspection to check indexing and live access.
How is a correction confirmed in Search Console?
Google's structured data repair guide recommends opening an issue in the rich result report to identify affected pages. A shared template error calls for correcting the template across the affected URLs.
After the site contains the corrections, the guide recommends Test live URL in URL Inspection. Once the fixes are confirmed, Validate fix on the issue details page starts Google's validation process, initially on a sample of pages.
Related terms
- Structured data
- JSON-LD
- How do I add custom JSON-LD to a Wix page?
- How does Schema.org validation differ from Google's Rich Results Test?
FAQ
Why does Google accept my code while Wix rejects it?
Wix's troubleshooting guide explicitly covers this situation. Check your script structure, punctuation and field line breaks against its requirements.
What if my live page is inaccessible to the test?
Google's test documentation requires page resources to be accessible anonymously. If your page is password protected, you can test its code separately while addressing access to the live page.
Sources
- Wix, "SEO Page Settings", undated
- Wix, "Troubleshooting Your Structured Data Markup", undated
- Wix, "Adding Structured Data Markup to Your Site's Pages", undated
- Google, "Rich Results Test", undated
- Schema.org, "Schema.org Markup Validator", undated
- Wix, "Troubleshooting Rich Results Eligibility Issues", undated
- Google, "Fix structured data issues in Search Console", undated
Check how a page reads to answer engines. Open the GEO score analyzer