Structured data on a Wix site: a floor, not a lever

Structured data is the least interesting item on our fix list, and it is the one we are most comfortable recommending. Those two facts are connected.

We sell a paid AI visibility monitor for Wix sites, and two of the five fixes it applies for you are structured data blocks. So read this knowing we benefit if you believe schema markup matters. What follows is mostly the case against overselling it, because the evidence anyone can point at, including Wix’s own research, does not support the version of this pitch the market usually makes.

The short version: on a Wix site, structured data is a cheap and reversible quality floor. It is not a lever with a promised return. If you have not measured whether assistants name you at all yet, that comes first, and the manual check for whether AI assistants recommend your business costs nothing but half an hour.

What Wix already adds, before you touch anything

Start here, because on a lot of sites the work is already done, and paying somebody to redo it would be a waste.

Wix’s Help Center states it plainly:

“Wix adds preset markups to some of your site’s pages by default when you create them. These are Wix Stores product pages, Wix Bookings services pages, Wix Blog posts, and Wix Events pages.”

The home page has its own rule, with a limit worth knowing if you run more than one branch: “Wix creates Local Business markup for your primary location only.” And, stated just as plainly, “If you have multiple business locations, we don’t create markups for each additional location.” Locations two and three are yours to add or to leave.

There is also an AI assisted option, with two documented boundaries: it “currently works only for Wix Blog posts”, and what it produces “is read-only”. One page type, and you do not get to edit the output.

That is a reasonable amount of ground covered for free, which is the first honest thing to say about a fix a paid tool wants to sell you.

What a Wix Stores site actually serves

Documentation says what is supposed to happen. We wanted the bytes, so we went and read them.

We keep a small published Wix Stores site for testing. It was built through the ordinary Wix setup flow and never hand tuned for search, which is the point: it shows what a stock Wix store serves, not what a specialist can coax out of one. It has no customers, which is what makes it safe to poke at. Today we fetched two of its pages and looked at the HTML the server returned.

Three things are worth taking from that.

• Nobody did anything to get it. The product page describes itself as a Product with an offer attached, from the preset markup, without a settings panel ever being opened.
• It was in the HTML the server sent. Not added afterwards by something that has to run first. Hold on to that distinction, because it comes back at the end of this post when we get to what our own product adds.
• One block, not five. Whatever you add through the panel in the next section, you are adding it beside something rather than onto a blank page.

One site, two pages, one day. That is a measurement, not a survey, and yours may differ, particularly with Bookings or Events in the mix. Checking takes about thirty seconds: open the page, view source, and search it for ld+json.

Three ways JSON-LD reaches a Wix page

This is the genuinely confusing part, because the three routes are documented in different places, they carry different limits, and they can interact without telling you.

1. Wix’s preset markup.

   Automatic, per page type, as above. You do not switch it on, and it is why most Wix stores already have Product markup on every product.

2. The per-page SEO panel.

   The route Wix documents for site owners. You add a markup to one specific page, and the limits in the next section apply to it. This is where a service business puts the FAQ or Service markup that no preset covers.

3. A script in the head.

   Wix’s Embedded Script API documentation says: “You can use the Embedded Script API to inject custom script tags to the head tag of a site.” That route belongs to an installed app rather than to you in the editor, and it is the one our own product uses. What that does and does not prove is the last section of this post.

One trap if you or a developer writes site code. The documentation for Velo’s setStructuredData states that “The structured data you set overwrites any structured data information set earlier”. So the programmatic route can replace the preset markup you never touched, and nothing on screen announces it.

The limits, and one pair that does not add up

Four rules govern what the panel will take, all from Wix’s own pages:

• “Wix only accepts structured data using JSON-LD markups.” Microdata and RDFa are not routes here.
• “Structured Data must be less than 7,000 characters to be added.”
• “You can add up to five markups per page.”
• “Important: Google guidelines require the information in the markup to be part of your page.”

The last of those is the rule that actually bites, and it is the one broken by everybody who treats markup as a shortcut. If you want structured data to say you open on Sundays, the page has to say you open on Sundays. Markup is a machine readable copy of what is on the page, not a second channel for claims the page does not make.

Now the arithmetic that does not work. Five markups at fewer than 7,000 characters each comes to something near 35,000 characters. Wix’s troubleshooting page for structured data says: “A total of 8,000 characters of markup can be added in total to a page.”

Both allowances are published, and they cannot both be the whole story. Neither page explains how the two interact and we have not found a page that does, so we do not know which one governs your page. We are reporting the contradiction rather than settling it, because settling it would mean handing you our guess dressed as a fact, and you would have no way to check it.

The practical consequence is small and identical either way: keep your markups few and small, and when one is refused, look at its length before anything else.

What the evidence says about AI answers

This is the section that costs us something.

Wix published research on the on-page factors behind AI visibility. It examined 13 on-page factors: blog post count, list count, images with alt text, character count, page size, internal links, total links, response time, paragraph count, total images, meta description length, heading count, and word count. Structured data was not one of them.

Its headline finding, in their words:

“Organic search traffic was the strongest predictor of AI visibility: sites with 50+ organic search visits per month were 8.2x more likely to be discovered than sites with minimal or no organic search traffic.”

Read that carefully in both directions, because it is easy to overread in either. It is an association in their data rather than a controlled test, so it does not show that buying organic traffic buys AI visibility. And structured data being missing from the list is not evidence that markup does nothing: it is evidence that the question was not asked. An unmeasured factor and a measured non-factor look identical in a summary and are not the same thing at all.

Wix’s own advice for its free AI visibility tool points elsewhere too. The help article for the AI Visibility Overview in Wix Analytics says: “To improve your site’s visibility on AI platforms, focus on enhancing your SEO. Strong SEO helps ensure that your site appears in relevant answers generated by AI platforms.” That article does not mention structured data or schema anywhere. We put that tool side by side with weekly monitoring in a separate note, including the cases where the free one is the whole answer.

And the strongest case for schema on Wix’s own property concedes the point. Writing there that argues schema markup matters for AI search still says: “There’s less research on how schema markup plays into LLM visibility, given how new GEO is.” That is a fair statement of where this stands, and it sits inside a piece arguing that schema does matter, which is exactly why it is worth quoting.

So here is the conclusion we hold to, on a page we would rather be able to write differently. Structured data is well documented as helping search engines parse a page. It is cheap and it is reversible. Whether it lifts how often an assistant names you is plausible and not established, and we cannot show you a number for it. Anybody who can is ahead of the evidence, and the reasonable thing to ask them for is the study.

Why we still apply it

The honest reading of that section is not “skip it”. It is “do it, cheaply, and stop waiting for a receipt”.

• The cost is minutes and the downside is close to nothing, as long as the markup matches the page.
• It removes ambiguity that something else would have to guess at. A price, an address, opening hours and a product name, stated in a form with no interpretation left in it.
• It comes back off. Remove the markup and the page is exactly what it was. Very little else in this category is reversible.
• The strongest association in Wix’s own research runs through search. Structured data is a documented search input, so if organic search traffic is what predicts AI visibility in their data, the things that help search are the things worth doing. That is our reasoning rather than their finding, and we flag it as reasoning: it is an inference across two steps, and inferences are where this category goes wrong.

And the other half, which fix lists tend not to print:

• It does not force a citation. There is no property in any markup that makes an assistant name you.
• It cannot make a claim true. Marking up a rating you do not have is a risk you have chosen to take, not a tactic.
• More markup is not more visibility. Five markups on a page that answers no buyer question are five markups about nothing.
• It does not replace writing the page. When a competitor is named and you are not, the ordinary cause is that they answered the question in words and you never wrote it down. That is the subject of the note on what being named second costs.

The nearest thing to this fix is the other cheap, reversible file with an uncertain return: llms.txt on a Wix site, which is a proposal nobody has promised to read. Same posture, same reason to do it anyway, same reason to keep your expectations at floor height.

What our product adds, and what we will not claim about it

Of the eight fixes our checklist raises, five are applied for you from the dashboard with a preview first and a one click undo: llms.txt, crawler access in robots.txt, LocalBusiness structured data, Product structured data, and empty product SEO fields. We guide the other three and deliberately do not make them for you: FAQ content that answers a buyer question, Bing IndexNow registration, and page titles and descriptions.

Mechanically, the two structured data fixes do one thing each. We add a single script tag of type application/ld+json through the Wix Embedded Scripts API, placed in the head, and we record the script that was created. Reverting deletes exactly that script by its id. Nothing else on your site is touched, and nothing visible changes in either direction.

Now the part that belongs on this page more than any other. Wix’s own documentation notes that a script added this way may not run until after the DOM has fully loaded, and we have not confirmed that our block appears in the HTML a given crawler receives. So we do not tell you that any particular assistant, or any particular search crawler, reads any particular block we add. We can tell you what we add, where we add it, and that one click takes it away again.

That is an awkward paragraph to publish under a price, and it is the whole thesis of the post. A floor is worth having. Nobody can price one. The integration page is the full record of what we read from a Wix site, what we write back, and what we will not touch.

What Patesco is actually for is the measurement around all of this: it reads your published Wix site, writes the buyer questions, asks ChatGPT, Gemini and Perplexity on a weekly schedule, names the competitors that keep appearing beside you, and emails you what moved. The free plan runs 5 questions across the three assistants and shows the real result. Premium runs 25 questions at $19 a month, which is the plan whose sample is wide enough to read small movements. If a fix of yours looks like it moved the number, the arithmetic for deciding whether it really did is in the note on being named second: on a five question scan, a four point rise is inside the ordinary week to week noise.

FAQ

Patesco is an independent tool for Wix site owners. ChatGPT, Perplexity and Gemini are trademarks of their respective owners and are referenced here only to describe which assistants are checked. Patesco is not affiliated with, endorsed by, or partnered with any AI provider or with Wix.