To add schema markup to a Wix page, open the SEO settings for that page type and select Edit next to Structured data markup. Choose Add New Markup, name it, paste valid JSON-LD, select Apply and publish the site. Check first whether Wix already supplies markup for the page, because a second description of the same item can contradict the first.
Wix says it accepts JSON-LD only, allows up to five markups per page and limits each markup to fewer than 7,000 characters. Work on one page at a time, whether it is an article, a product, an event, a business page or a breadcrumb trail, and keep every fact in the code visible on that page.
After publishing, test the live URL with Google's Rich Results Test, the Markup card in Bing's URL Inspection and, where Yandex matters to you, the Yandex structured data validator.
Find out what Wix already adds to the page
Wix creates SEO settings automatically according to page type, and Wix says preset structured data is available for several of them, including Wix Stores products, Wix Blog posts, Wix Events pages and dynamic item pages. If your page belongs to one of those types, some markup may already exist before you write a line of code.
Preview the preset in the Wix SEO settings, then open the published page and inspect it. Run the live URL through Google's Rich Results Test, or paste the page's JSON-LD into the Schema Nova validator, and read which types come back. That tells you whether you are adding a missing description or replacing an existing one.
The page type decides how much work is left. A product on Wix Stores may only need a corrected field, while a plain business page with no preset has nothing to correct and may simply need one accurate block. Decide which case you are in before you open the editor, because the answer changes whether you add, convert or leave the preset alone.
Know the three kinds of Wix markup
Wix describes three situations. Preset markup is what Wix supplies for certain page types. Custom markup is JSON-LD you add or edit yourself. For Wix Blog posts there is also AI-generated markup, which Wix says currently works only for Wix Blog posts and which can be refreshed when the post changes.
Manual and AI-generated markup on a Blog post can coexist, so adding your own block does not automatically switch the generated one off. That is useful when you want to add one extra type, such as a breadcrumb trail, without touching what Wix produces for the post itself.
If you want to change the generated markup rather than add to it, you can convert it. Wix explains that converting AI-generated markup to custom markup moves upkeep to you. Future edits to the post may then leave your custom code out of date, so converting is a decision to keep updating that block whenever the post changes.
For other page types, Wix also lets you exclude or convert a preset before you replace it. Doing that first keeps the page from carrying two competing descriptions of the same product, event or post.
Add custom JSON-LD from the SEO settings
Have the JSON-LD ready before you open Wix, because the editor expects finished code. You can write it by hand, adapt the example below, or build it with the article schema generator or the breadcrumb schema generator. Either way, read the result against the visible page before you paste it.
Wix's labels change from time to time, so follow the current SEO and GEO area if a name differs from the ones here. The dashboard route Wix documents runs in this order:
- Open SEO and GEO in the Wix dashboard.
- Select Tools and settings, then SEO Settings.
- Choose the page type.
- Select Edit next to Structured data markup.
- Choose Add New Markup.
- Enter a name for the markup.
- Paste the JSON-LD.
- Select Apply.
- Publish the site.
The name is only a label for you, so pick one that says what the block describes, such as "Article details" or "Breadcrumb trail". Nothing reaches the live page until you publish, which is why the last step matters as much as the first.

Use the page-level route for a single page
For a single main page, Wix documents a second route. Open Pages and Menu, open the menu for the page, choose SEO basics, then Advanced SEO, then Structured Data Markup. The Add New Markup step and the paste, Apply and publish steps are the same as above.
Use this route when the markup belongs to one page only, such as an About page or a landing page that describes one real business or event. Use the dashboard route when the markup should follow a page type, such as every blog post or every event.
If you build in Wix Studio, remember one limit for dynamic pages: Wix says page variants inherit SEO settings from the original dynamic page, and the SEO settings cannot be configured separately for each variant. Make the change on the original page.
Use Wix variables on dynamic pages
A Wix CMS dynamic item page is one page design and URL pattern that displays many collection items. A single template serves every item, so a block you write once appears on all of them. Wix describes dynamic pages as collection-driven, with a unique URL for each item.
That changes how you write the values. The item name, description, image, URL, price and date must come from Wix variables, not from one item's text. Wix provides variables for dynamic SEO settings and structured data, and the SEO settings screen for the dynamic page is where you insert them.
If you type one product's name or price into the template, every other item in the collection will describe that product, and the markup will contradict the visible page. Write the block so it stays accurate for every item, and test a few different item URLs after publishing, not only the first one.
Prices, dates and images deserve the most attention. They change in the collection, so a variable that points at the right field keeps the markup in step with the page. A hard-coded value does not.
A BlogPosting and BreadcrumbList example to adapt
The example below is two separate markups, which suits Wix because each markup is its own entry and the page may hold up to five. The first describes an article, the second its breadcrumb trail. Every value is fictional. Replace each example.com URL, the name, the headline, the image files and the dates with the real information shown on your page.
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"@id": "https://example.com/example-article#article",
"url": "https://example.com/example-article",
"headline": "How to Care for a Fictional Indoor Herb Garden",
"description": "A fictional guide to caring for an indoor herb garden.",
"image": [
"https://example.com/images/herb-garden-1x1.jpg",
"https://example.com/images/herb-garden-4x3.jpg",
"https://example.com/images/herb-garden-16x9.jpg"
],
"author": {
"@type": "Organization",
"name": "Example Editorial Team",
"url": "https://example.com/about"
},
"publisher": {
"@type": "Organization",
"name": "Example Publishing",
"url": "https://example.com",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/images/logo.png"
}
},
"datePublished": "2026-01-15",
"dateModified": "2026-01-20",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://example.com/example-article"
}
}Paste the JSON-LD itself into the Wix field, since Wix accepts JSON-LD only. The author and publisher here are an organization. If a named person wrote the post and the page shows that name, describe a Person instead, as in the article schema guide.
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"@id": "https://example.com/example-article#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://example.com"
},
{
"@type": "ListItem",
"position": 2,
"name": "Guides",
"item": "https://example.com/guides"
},
{
"@type": "ListItem",
"position": 3,
"name": "How to Care for a Fictional Indoor Herb Garden"
}
]
}The breadcrumb names and links should match the trail visitors can see on the page. The last item has no item URL because it is the current page. If your page has no visible breadcrumb trail, leave this second markup out. For more on trails, read the breadcrumb schema guide.
Each markup must stay under Wix's 7,000-character limit, and these two sit well inside it. If you would rather join the two into one block, a single @graph works; the JSON-LD graph guide shows how, and more patterns are in the JSON-LD schema examples. The general guide to adding schema markup covers the same idea outside Wix.
A property can exist in Schema.org, be listed by Google's Article or Breadcrumb feature, and be required there, and those are three separate facts. The table applies to those two Google features, not to every search engine.
Avoid duplicate or inaccurate markup
Before pasting, decide whether the page already has a preset for the same thing. If Wix already describes the article, adding a second BlogPosting creates two descriptions that may disagree on the headline, image or date. Edit, convert or exclude the preset first, then add yours.
Describe only what visitors can see. Google says structured data must represent visible page content, and Wix gives the same instruction. Do not add ratings, reviews, prices, availability or dates that the page does not show, and do not add a business or person the page does not mention.
Pick the type that matches the page. A blog post is a BlogPosting, a product page describes a product, and an event page describes an event. A type that fits the content better than a generic one is easier to keep accurate. The guides for article schema and rich results explain how types relate to search features.
Test the published page in Google, Bing and Yandex
Testing happens on the live URL after you publish, so publishing comes before every test. Start by checking the JSON syntax and the Schema.org vocabulary, which the Schema Nova validator can do before you paste the code into Wix, then publish and move on to the search engine tools.
Google offers the Rich Results Test, and Google Search Console's URL Inspection reports on a page after it is indexed. Bing's Webmaster Tools URL Inspection has a Markup card that recognizes JSON-LD. When Yandex visibility matters, Yandex Webmaster provides a Structured Data Validator that checks Schema.org and Yandex's own service requirements.
Each tool answers a different question. Syntax and vocabulary come first, then a specific search feature's requirements, then whether the page is indexed and shown. Passing one does not mean passing the next, a point the structured data testing tool guide walks through in more detail.
Recheck after you change page content, collection fields, prices, dates or images, because the markup and the visible page need to keep agreeing.

Make the markup readable for Bing and AI search
Bing reads JSON-LD, so the block you add in Wix serves Bing as well as Google. Bing says annotations can help it understand content, though rich-result availability varies by market and is not guaranteed. Wix takes JSON-LD only, so Microdata is not an option inside its markup field.
For ChatGPT search and Perplexity, check your robots.txt and any CDN rules so OAI-SearchBot, PerplexityBot and Perplexity-User are not blocked. OpenAI says a site can be eligible for ChatGPT search when it allows OAI-SearchBot to crawl it, and placement is not guaranteed. Google says AI Overviews and AI Mode need no special markup. See whether AI systems use schema markup.
Keep the markup accurate after you publish
A markup block is a commitment to maintain it. Whenever you edit the article, change a price, swap an image or move a page, open the markup and update it too. Wix says converted Blog markup becomes your responsibility to maintain, so add a markup check to your editing routine.
Keep the Wix limits in mind as pages grow: five markups per page and fewer than 7,000 characters each. If a page needs more, merge related blocks into one @graph or drop anything the page does not actually show.
Schema.org is a shared vocabulary, and Google's supported features are a smaller, changing set. Google's documentation updates say FAQ rich results are no longer shown in Google Search from May 7, 2026, yet FAQPage remains valid Schema.org vocabulary. Do not add FAQ markup as a way to get a Google FAQ result. For other platforms, the same process applies in the guides for WordPress, Shopify, Squarespace and Webflow.
Questions people ask
Can I add custom JSON-LD to Wix?
Yes. Wix documents a Structured Data Markup control in its SEO settings where you choose Add New Markup, paste JSON-LD, apply and publish. Wix accepts JSON-LD only, so Microdata is not an option in that field.
Does Wix already add schema markup?
Wix supplies preset structured data for several page types, including Wix Stores products, Wix Blog posts, Wix Events pages and dynamic item pages. Wix Blog posts can also use AI-generated markup. Preview the preset in your SEO settings and inspect the published page before you edit or duplicate it.
How many markups can one Wix page have?
Wix says up to five markups per page, and each markup must be fewer than 7,000 characters. Split large blocks into separate markups or trim fields the page does not show.
Does Wix AI-generated markup replace my manual markup?
No. Wix says manual and AI-generated markup can coexist on a Wix Blog post. If you convert the generated markup to custom markup, you take over its upkeep and must update it when the post changes.
Does valid markup guarantee a Google rich result?
No. Google says a supported feature is not guaranteed to appear, and Wix and Bing say the same about rich results. Valid JSON-LD shows the code parses and may describe the page correctly. Eligibility, indexing and display are separate steps.
