Wix Structured Data for SEO: A Guide to Implement Schema Markup in 2026

Structured data is the single biggest SEO lever most Wix site owners leave untouched. In 2026, schema markup is no longer a "nice to have" - it is the mechanism by which Google, Bing, ChatGPT, Perplexity, and Google AI Overviews determine what a Wix page actually is, who wrote it, what it is about, and whether it deserves to be cited. This is the definitive 2026 guide to Wix structured data: what Wix adds automatically, what it does not, how to add custom JSON-LD through the Advanced SEO panel and Velo, which schema types win rich results and AI citations, and exactly how to validate, monitor, and future-proof every change. Written by Michael Andrews, the UK's No.1 Wix SEO expert and consultant.

What is structured data and why does it matter for Wix SEO in 2026

Structured data is standardised, machine-readable vocabulary (defined at schema.org) that labels the content of a page so search engines can parse it reliably. On a Wix site, the markup lives inside a `<script type="application/ld+json">` tag in the page head. When Googlebot, Bingbot, GPTBot, ClaudeBot, or PerplexityBot crawls the page, it reads the structured data before it parses the visible HTML, giving it a trusted, unambiguous description of the page.

In 2026 three things have changed about how structured data affects Wix SEO. First, AI search engines (ChatGPT Search, Perplexity, Google AI Overviews, Microsoft Copilot) cite pages with strong, consistent schema far more often than pages without. Second, Google has tightened the link between visible content and structured data - mismatched schema is a spam signal. Third, the "entity @graph" pattern (multiple linked types in one JSON-LD) has replaced isolated single-type schemas as best practice.

What Wix adds automatically vs what you must add manually

Wix, Wix Studio, and Wix Harmony automatically generate schema for several content types. Knowing exactly which ones matters, because duplicating auto-generated schema causes validation errors and conflicting data in rich results.

Schema Wix generates automatically

Schema you must add manually

• **FAQPage** on service, landing, and blog pages (highest ROI in 2026)
• **HowTo** on tutorial and guide pages
• **Article** or **NewsArticle** on non-Wix-blog pages (static news/press pages)
• **LocalBusiness** (with geo, openingHours, priceRange, areaServed) - Wix's auto Organization is incomplete for local SEO
• **Service** with provider, areaServed, serviceType
• **Review** and **AggregateRating** outside of Wix Stores
• **Course** and **CourseInstance** for educational pages
• **VideoObject** for embedded or self-hosted video
• **Person** and **Organization** nested graphs for E-E-A-T
• **ProfilePage** for about / author pages
• **ImageObject** with author, license, creditText for rich image attribution
• **SpeakableSpecification** on news / blog content for voice search

The 2026 schema priority hierarchy for Wix sites

1. 1**Entity @graph** (Person + Organization + WebSite + WebPage) - foundation signal for every page
2. 2**BreadcrumbList** - already auto on most pages; verify it is present on custom pages
3. 3**FAQPage** - single highest-ROI additional schema in 2026
4. 4**Article / BlogPosting** - auto on Wix Blog; add manually on static article pages
5. 5**LocalBusiness** (full) - non-negotiable for local Wix sites
6. 6**Service** - essential for service businesses
7. 7**Product + Offer + Review** - auto on Wix Stores; extend with Review for authority
8. 8**HowTo** - still useful for AI citations even though Google de-emphasised the rich result
9. 9**Course** - for education / training Wix sites
10. 10**ImageObject** with creditText and license - drives image-search and AI attribution

How to add custom structured data to a Wix page (step by step)

1. 1Open your Wix dashboard and go to the page you want to edit.
2. 2Click the three-dot menu on the page and choose SEO Basics, or in Wix Studio open the Page Settings > SEO tab.
3. 3Scroll to Advanced SEO and expand Structured Data.
4. 4Click Add New Markup.
5. 5Paste your JSON-LD body - do not wrap it in a `<script>` tag, Wix adds that automatically.
6. 6Click Save.
7. 7Publish the site.
8. 8Open the live URL in an Incognito window, right-click > View Page Source, and confirm the JSON-LD appears inside `<script type="application/ld+json">` in the head.
9. 9Test the live URL with Google's Rich Results Test (rich-results.google.com) and the Schema.org Validator (validator.schema.org).
10. 10Submit the URL for reindexing in Search Console > URL Inspection > Request Indexing.

The entity @graph pattern (the 2026 gold standard)

In 2026, the single biggest schema upgrade for any Wix site is the entity @graph. Instead of pasting separate JSON-LD blocks for Organization, WebSite, and Article, put them all in one @graph array and link them by @id. AI search engines use this connected graph to build a trust profile of the site, the author, and the page.

"A connected @graph is the difference between an AI engine knowing "this is a page" and "this is a page by Michael Andrews, the UK's No.1 Wix SEO expert, published on wixseo.co.uk, part of the Wix SEO Expert UK knowledge base, about Wix structured data". The second gets cited. The first does not."

Tweet this quote

Minimal @graph template for a Wix page

Copy the JSON below, replace the domain and person fields with your own, and paste it into Wix > SEO Settings > Advanced SEO > Structured Data on your homepage. The @id values are what link the entities together - keep them consistent site-wide.

• `@graph[0]` - Person with name, jobTitle, url, sameAs (LinkedIn, Wix Marketplace, Amazon Author, Reddit), knowsAbout
• `@graph[1]` - Organization with name, url, logo, founder (links to Person by @id)
• `@graph[2]` - WebSite with url, name, publisher (links to Organization by @id), inLanguage
• `@graph[3]` - WebPage with url, name, isPartOf (links to WebSite), author (links to Person), about (array of Thing with sameAs to Wikipedia)
• `@graph[4]` - BreadcrumbList with itemListElement
• `@graph[5]` - FAQPage (or Article, Service, Product) for the page-specific content

FAQPage schema - the single highest-ROI schema in 2026

If you do nothing else in this guide, add FAQPage schema to your top 10 Wix pages. In our tracking across 750+ Wix engagements, FAQPage is cited by ChatGPT, Perplexity, and Google AI Overviews more often than every other schema type combined. It is also the easiest to implement correctly.

FAQPage rules that actually matter in 2026

• Every question and answer in the JSON-LD must appear in the visible page content. Hidden FAQs stopped getting rich results in August 2023.
• Answers should be 40-80 words each - long enough to be useful, short enough to be cited verbatim.
• Use 4-8 questions. Fewer looks thin; more causes Wix's renderer to truncate.
• Avoid promotional language in answers - AI engines demote and Google no longer shows promotional FAQ rich results.
• Each question should be a genuine user question, not a keyword-stuffed heading.
• Link each Answer to the Person entity (`author: { @id: "#person" }`) to reinforce authorship.

LocalBusiness schema on Wix (what Wix misses)

Wix's auto-generated Organization schema does not include `geo`, `openingHours`, `priceRange`, `areaServed`, or `hasMap` - all of which are required for Google's LocalBusiness rich results and for inclusion in Google's local pack and AI Overviews for local queries. If your Wix site serves a local market, a manual LocalBusiness JSON-LD is non-negotiable.

Product schema on Wix Stores (what to add on top of Wix's auto schema)

Wix Stores auto-generates Product with price, availability, and AggregateRating when reviews are enabled. What it does not generate, and what drives an extra 15-30% click-through rate on Shopping-tab impressions, is: shippingDetails (with shippingRate, deliveryTime, shippingDestination), hasMerchantReturnPolicy (with returnPolicyCategory, merchantReturnDays, returnMethod), GTIN/MPN/SKU identifiers, and pattern/color/material/size variants as ProductGroup.

Adding structured data to dynamic pages in Wix Studio (Velo)

The Advanced SEO panel only works for static pages. For dynamic collection item pages in Wix Studio (e.g. /team/{slug}, /portfolio/{slug}, /locations/{city}), structured data must be injected at runtime through Velo using the wix-seo-frontend API.

Velo pattern for dynamic structured data

1. 1Enable Dev Mode in Wix Studio.
2. 2Open the dynamic page file (e.g. `pages/Team (Item).xxx.js`).
3. 3In `$w.onReady`, get the current item: `const item = $w("#dynamicDataset").getCurrentItem();`
4. 4Build the JSON-LD object from the item fields (name, image, jobTitle, description, etc.).
5. 5Import `wixSeo` from `wix-seo-frontend` and call `await wixSeo.setStructuredData([{ type: "Person", ...payload }]);` passing the JSON-LD.
6. 6Test the live dynamic item URL in the Rich Results Test - the schema is injected after hydration, so use a desktop User-Agent test.

Validation: the two tools every Wix site needs

Common Wix structured data mistakes (and how to fix them)

1. Pasting JSON-LD wrapped in a `<script>` tag

Wix's Advanced SEO panel adds the script wrapper automatically. If you paste `<script type="application/ld+json">{...}</script>`, Wix outputs `<script type="application/ld+json"><script type="application/ld+json">{...}</script></script>` and every crawler ignores it. Paste only the JSON body.

2. Duplicating auto-generated schema

If you paste BlogPosting schema into a Wix Blog post, Wix renders both - its own auto schema and yours. Search Console flags this as a conflict. Always audit what Wix emits before adding custom markup on that page type.

3. Schema content not matching visible content

Every property in your JSON-LD must appear in the visible, crawlable HTML of the page. If your FAQPage has 6 questions but the page only shows 4, Google will demote the rich result. Fix: either render all 6 in the visible page content, or remove 2 from the JSON-LD.

4. Using deprecated or unsupported schema

Google deprecated rich results for: HowTo (mobile-only, 2023), FAQPage (general-domain, 2023 - still works for authoritative domains and AI citations), Q&A Page outside of forum contexts. Stop using TechArticle for non-technical content. Stop using NewsArticle unless the site is a registered news publisher.

5. Broken @id references

If your Person @id is `https://yourdomain.com/#person` on one page and `#person` on another, AI engines treat them as two different people. Always use absolute @id values and keep them identical site-wide.

6. Missing hreflang on multilingual Wix sites

Wix Multilingual emits hreflang automatically but only if each language version is published and the alternate pages exist. Schema inLanguage must match the page's hreflang value (en-GB, en-US, fr-FR, etc.) or AI engines cite the wrong locale.

Monitoring schema health in Google Search Console

Once schema is live, Search Console > Enhancements gives you a per-schema-type report showing Valid, Valid with warnings, and Error counts. Review weekly for high-traffic pages and monthly for the rest. The most common recurring issue on Wix sites is "Field datePublished is recommended" on Article/BlogPosting - fix by adding the field explicitly even when Wix has already populated it in the auto schema.

Structured data for AI search (GEO / AEO) - what actually moves citations

Across 750+ Wix engagements we have tracked which schema changes correlate with ChatGPT, Perplexity, and Google AI Overview citations. Four signals dominate:

1. 1**Connected entity @graph** - Person + Organization + WebSite + WebPage with matching @id values site-wide
2. 2**FAQPage with Person-linked Answers** - every Answer references `author: { @id: "#person" }`
3. 3**Author Person entity with knowsAbout, hasCredential, sameAs** - at least 4 external verification URLs (LinkedIn, Marketplace profile, Amazon Author, Reddit/community)
4. 4**Claim schema on short, quotable statements** - AI engines lift these into generated answers verbatim

A full Wix structured data implementation roadmap

1. 1Week 1 - Audit every page type with Rich Results Test. Document what Wix auto-emits.
2. 2Week 1 - Build the site-wide entity @graph (Person + Organization + WebSite) on the homepage.
3. 3Week 2 - Add FAQPage schema to the top 10 traffic pages.
4. 4Week 2 - Add LocalBusiness schema to the homepage (local sites only).
5. 5Week 3 - Add Service schema to every service page.
6. 6Week 3 - Extend Wix Stores Product schema with shippingDetails, returnPolicy, GTIN/MPN.
7. 7Week 4 - Add ImageObject with creditText and license to the top 20 hero images.
8. 8Week 4 - Validate every changed URL with Rich Results Test and Schema.org Validator.
9. 9Week 5 - Submit a sitemap refresh in Search Console and request indexing on top 50 URLs.
10. 10Ongoing - Review Search Console Enhancements weekly, re-audit schema every 90 days.

Frequently asked questions