How to Add Schema Markup to Wix (2026 Guide)

Schema markup is one of the most underutilised SEO opportunities on Wix websites. When implemented correctly, structured data can unlock rich results, star ratings, breadcrumbs, product details, how-to steps, that meaningfully increase your click-through rates from Google without needing to rank any higher. It also feeds the AI systems that are increasingly deciding which businesses get cited in conversational search results. This guide walks through the actual process of adding JSON-LD schema to a Wix site, step by step, with worked examples you can adapt and the validation steps to confirm it works.

What Is Schema Markup and Why Does It Matter?

Schema markup is code in JSON-LD format that you add to your web pages to help search engines understand your content. It does not change how your page looks to visitors. It tells Google what your content means, not just what it says.

When Google understands the meaning behind your content, it can display it as a rich result: a search listing with extra visual elements like star ratings, FAQ expandables, business hours or breadcrumb trails. These enhanced listings take up more space on the results page and attract more clicks than plain blue links.

JSON-LD (JavaScript Object Notation for Linked Data) is Google's preferred format for structured data. It sits in a script block in your page's HTML head and is invisible to visitors. You do not need to be a developer to use it. You need to understand what each property means, paste the right block into the right place, and validate it.

What Wix Generates Automatically, and What It Does Not

Before you add any custom schema, you need to know what Wix already puts on your pages. Adding markup that duplicates what the platform generates is the most common schema mistake on Wix sites, and it causes real problems. Here is the complete picture as of 2026.

Wix auto-generates structured data for the following page types when you use the corresponding Wix feature:

• Wix Blog posts: Article or BlogPosting schema, populated from your post title, author, publish date, featured image and body content.
• Wix Stores product pages: Product schema including name, price, availability, images and review data where present.
• Wix Events pages: Event schema with event name, date, location and description.
• Wix Forum posts: DiscussionForumPosting schema based on thread title and content.
• Wix Portfolio projects: CreativeWork schema with project details.
• Online Programs list pages: structured data for course listings.
• Wix Video: VideoObject schema when you embed video through the Wix Video feature.

Two additional types are triggered by specific features rather than page types:

• LocalBusiness markup is added to your homepage automatically when you populate your business name and address in Settings > Business Information.
• Sitelinks Search Box markup is added when you install the Wix Site Search app.

Now here is the critical part: what Wix does not generate. There is no automatic markup for:

• FAQPage: even if your page has a visible FAQ section, Wix will not generate FAQ schema for it. You must add this yourself.
• HowTo: step-by-step tutorial content gets no schema unless you add it manually.
• BreadcrumbList: Wix does not auto-generate breadcrumb schema, even though it shows breadcrumb navigation in the editor.
• Review or AggregateRating: customer reviews on non-product pages receive no schema.
• Service: if you offer services rather than products, there is no auto-generated Service schema.
• Person: author or personal brand pages receive no Person schema beyond what is nested inside BlogPosting.

This means if your Wix site is a service business with FAQ content, how-to guides, or testimonials, the schema types that would be most valuable to you are precisely the ones Wix does not provide. That is where manual implementation comes in.

The AI Structured Data Generator for Blog Posts

In 2026, Wix introduced the AI Structured Data Generator, which uses AI to analyse your published blog posts and automatically generate relevant Schema.org markup for them. If you are a new Wix user, it is enabled by default. If you have an existing site, you need to opt in through SEO Settings in your dashboard.

Once active, every new or updated blog post will automatically receive structured data based on the post's actual content. The AI can generate Article, BlogPosting, FAQPage, Recipe and other types depending on what it detects in the text.

This is a genuinely useful feature for blog content, but it has clear limits. It applies only to blog posts, not to static pages, service pages, landing pages, or any other page type. If your homepage, contact page, or service pages need schema (and they almost certainly do) you still need to add it yourself using one of the two manual methods below.

The 7 Most Important Schema Types for Wix Websites

1. LocalBusiness: for any business serving local customers. Triggers business panels with address, phone, hours, and map pins.
2. Article / BlogPosting: for blog posts and news content. Helps Google surface articles in Top Stories and news carousels.
3. FAQPage: for FAQ sections. Feeds AI systems (Google AI Overviews, ChatGPT, Perplexity) with structured Q&A pairs for citation. Note: Google discontinued the visible FAQ rich result in May 2026, but the schema remains valuable for AI discoverability.
4. BreadcrumbList: for site navigation. Shows the page hierarchy path in search results instead of the raw URL.
5. Product: for eCommerce product pages. Can display price, availability, and review stars in search.
6. Review / AggregateRating: for businesses with customer reviews. Shows star ratings alongside your search listing.
7. Person: for author profiles and personal brand sites. Helps Google connect content to a known individual.

How to Add Schema Markup to Wix: Custom Code Method

The Custom Code method injects JSON-LD directly into the page's HTML head, exactly where Google expects to find it. This is the method I use for most client implementations because it gives you full control over what goes where. Here is the process:

1. Open your Wix site dashboard (not the editor). Navigate to Settings, then Custom Code.
2. Click to add a new custom code snippet.
3. Paste your JSON-LD block wrapped in script tags with type="application/ld+json".
4. Set the placement to Head. Wix offers Head, Body - start and Body - end. Always choose Head so crawlers parse it before the page body loads.
5. Choose which pages the code applies to. Select All Pages or specific pages. LocalBusiness schema belongs on your homepage and contact page, not every blog post. FAQ schema belongs only on pages with FAQ content.
6. Set the code to load on each page load, not triggered by a user action.
7. Give the snippet a clear name (for example "LocalBusiness Schema - Homepage") and save.
8. Publish your site. Custom Code only takes effect on the published live site, not in the editor preview.

The Alternative Route: Adding Schema via SEO Settings

Wix also offers a second method through the built-in SEO Settings panel, and for certain use cases it is simpler than Custom Code. This method is available for blog posts, store products, store categories, booking services, events, forum posts, portfolio projects and online programmes.

To add schema to a specific page, navigate to that item in your dashboard, open its SEO Settings (usually found under Marketing & SEO or via an Edit SEO Settings button), click Advanced, then Structured Data Markup, then Add New Markup. Give it a name, paste your JSON-LD code, and click Apply.

The SEO Settings method has two advantages over Custom Code. First, you can set default structured data templates per page type, so every new product page or blog post automatically receives your custom markup with dynamic variables that pull in the page's own title, URL, images and dates. Second, Wix validates your JSON-LD syntax before saving. If your code has a formatting error, it will reject it with an error message rather than silently publishing broken markup.

The limitation is scope. SEO Settings only applies to Wix app pages (blog, store, bookings, events, etc.). If you need to add schema to a static page, your homepage, a custom landing page, or any page that is not tied to a Wix app, you need the Custom Code method described above.

Worked Example: LocalBusiness Schema

LocalBusiness is the most broadly useful schema type and a good starting point. Below is a complete, valid JSON-LD block you can adapt for your own business. Replace every value with your real details: name, address, phone number, opening hours, and coordinates.

The script block to paste into Wix Custom Code:

<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "LocalBusiness", "name": "Your Business Name", "description": "A one-sentence description of what your business does.", "url": "https://www.yourdomain.com", "telephone": "+44-1234-567890", "email": "[email protected]", "address": { "@type": "PostalAddress", "streetAddress": "123 High Street", "addressLocality": "Your Town", "addressRegion": "Your County", "postalCode": "AB1 2CD", "addressCountry": "GB" }, "geo": { "@type": "GeoCoordinates", "latitude": 51.5074, "longitude": -0.1278 }, "openingHoursSpecification": [ { "@type": "OpeningHoursSpecification", "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"], "opens": "09:00", "closes": "17:30" } ], "image": "https://www.yourdomain.com/your-logo.png", "priceRange": "££" } </script>

Required fields for a rich result: name, address (with streetAddress, addressLocality, postalCode and addressCountry). Strongly recommended: telephone, geo coordinates, openingHoursSpecification, image and priceRange.

Worked Example: FAQPage Schema

FAQPage schema structures your question-and-answer content for AI citation systems like Google AI Overviews, ChatGPT, and Perplexity. Note: Google discontinued the visible FAQ rich result (expandable dropdowns in SERPs) in May 2026, but the schema remains one of the fastest wins for most Wix sites because nearly every business site has an FAQ section and AI systems actively consume this structured data. Here is a complete JSON-LD block with two questions. Add as many as you need, following the same pattern:

<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "How long does delivery take?", "acceptedAnswer": { "@type": "Answer", "text": "Standard delivery takes 3 to 5 working days. Express delivery is available for next-day arrival if ordered before 2pm." } }, { "@type": "Question", "name": "Do you offer a money-back guarantee?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. If you are not satisfied, contact us within 30 days of purchase for a full refund. The item must be returned in its original condition." } } ] } </script>

Each question must have exactly one acceptedAnswer, and the answer text must match what is visibly written on the page. Google's guidelines require that FAQ schema reflects content users can actually see. Marking up questions that are not visible on the page violates their policies and can result in a manual action.

Worked Example: Article Schema for Blog Posts

If you are using the Wix Blog feature, Wix already generates Article schema for your posts automatically. In that case, you do not need to add this manually. Check your page source first. But if you are publishing content on static pages rather than through the Wix Blog app, or if you need to override Wix's auto-generated markup with more detailed data, here is the Article schema format:

<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Article", "headline": "Your Article Title Here", "description": "A concise summary of what this article covers.", "image": "https://www.yourdomain.com/images/article-hero.jpg", "author": { "@type": "Person", "name": "Your Name", "url": "https://www.yourdomain.com/about" }, "publisher": { "@type": "Organization", "name": "Your Business Name", "logo": { "@type": "ImageObject", "url": "https://www.yourdomain.com/logo.png" } }, "datePublished": "2026-01-15", "dateModified": "2026-08-20", "mainEntityOfPage": { "@type": "WebPage", "@id": "https://www.yourdomain.com/your-article-url" } } </script>

The headline should match your H1 tag. Dates must use ISO 8601 format (YYYY-MM-DD). The author should be a Person with a name and a URL pointing to a real author page. Google uses these fields to determine eligibility for Top Stories and article carousels.

How to Check It Worked

Adding the code is only half the job. You need to verify that Google can actually parse it. There are three checks to run, and all must be done on the published live site, never the editor preview.

1. Google Rich Results Test (search.google.com/test/rich-results): paste your published URL. Green ticks mean your schema is valid and eligible for rich results. Red errors list missing fields or invalid types. Fix every one before moving on.
2. Schema Markup Validator (validator.schema.org): checks technical correctness against the full schema.org specification, catching issues the Rich Results Test may miss such as deprecated properties.
3. View Page Source: on your published site, right-click and select View Page Source (Ctrl+U / Cmd+U). Search for application/ld+json. If your block is not there, the snippet is either not saved, not set to the right pages, or the site has not been republished.

What Goes Wrong: Common Schema Mistakes on Wix

These are genuine faults that break schema implementations on Wix sites. Each one has caused real problems on sites that came through for audits.

• Duplicate Organization blocks. Wix auto-generates Organization and WebSite schema. Adding your own via Custom Code creates competing blocks that Google may ignore. Always check your page source for existing schema before adding your own.
• Schema applied sitewide when it should be page-specific. LocalBusiness on every page (including blog posts) creates invalid markup. Apply each type only where the content matches.
• Placement in Body instead of Head. Body - end placement risks the schema not being parsed by crawlers that stop before the body finishes loading.
• Invalid property types. Quoting latitude as "51.5074" instead of the number 51.5074, or using a bare ID reference where Google expects a full object. The Rich Results Test catches these.
• Testing in the editor instead of the live site. Custom Code does not run in preview mode. You must publish and test the live URL.
• Forgetting to republish after changes. Edits to Custom Code snippets do not take effect until you republish.

FAQ Schema: The Easiest Win in Wix SEO

FAQ schema remains one of the easiest and most impactful schema types to implement. While Google discontinued the visible FAQ rich result (expandable dropdowns) in May 2026, FAQPage schema now serves a critical role: it feeds AI systems like Google AI Overviews, ChatGPT, and Perplexity with structured Q&A pairs, improving your citation visibility in conversational search without needing a higher ranking.

The worked example above gives you the exact JSON-LD format. The process for implementation is identical to the LocalBusiness example: create the JSON-LD block, paste it into Custom Code with Head placement, and apply it only to the specific page that contains those FAQs. Alternatively, if the FAQ is on a blog post or product page, you can add it through SEO Settings under Advanced > Structured Data Markup. Do not apply FAQ schema sitewide unless every page genuinely has FAQ content.

Why Schema Markup Now Matters for AI Search and GEO

Structured data was originally built for rich results: star ratings, FAQ dropdowns, product cards. That is still important, but it is no longer the full picture. AI systems like Google AI Overviews, ChatGPT, Perplexity and Microsoft Copilot are now consuming structured data as part of how they understand, evaluate and cite web content. This is where schema goes from a nice-to-have to a genuine competitive advantage, and it is why I spend more time on structured data strategy now than at any point in the past decade.

Google has stated publicly that structured data is a "computationally cheap" way for systems, including large language models, to process information at scale. That means it is specifically efficient for the AI systems powering features like AI Overviews. When an AI system needs to determine whether your business offers a particular service, what your hours are, or who your founder is, structured data provides that answer in a format it can parse instantly rather than inferring it from unstructured page text.

The concept that makes this work at a deeper level is the entity graph. An entity graph is a network of connected schema blocks where each entity (your business, your founder, your services, your location, your content) has a unique @id and references the other entities by their @id values. Instead of isolated JSON-LD blocks that describe individual things in a vacuum, a connected graph tells the AI system that this Person is the author of this Article, which is published by this Organization, which offers this Service at this Location.

That connection is what separates schema that merely qualifies for rich results from schema that actively shapes how AI systems understand your brand. When Perplexity or ChatGPT is generating an answer about services in your industry, the site with a connected entity graph provides a structured, unambiguous data source. The site with disconnected fragments forces the AI to guess, and guessing means it is just as likely to cite a competitor.

For most Wix site owners, the practical starting point is adding LocalBusiness, Article and FAQ schema as described in this guide. That gets you into the game. But if you want to build a genuinely connected entity graph, linking your business entity to your founder, your services, your reviews, your content and your geographic coverage in a way that AI systems can traverse, that is specialist work. It is exactly what the dual-layer schema service is built for, and it is the difference between having structured data and having structured data that actually performs across both traditional and AI search.

Where to Go from Here

Schema markup is not a magic switch. Adding it does not guarantee rich results. Google decides which results to enhance and when. What schema does is make your content eligible for those enhancements and give AI systems a structured data source they can work with confidently. Without it, you are not even in the running.

Start with the single most relevant schema type for your business. For most Wix sites, that is LocalBusiness for the homepage and FAQPage for any page with genuine questions and answers. Add one, validate it, confirm it appears in Google Search Console's Rich Results report (this can take days to weeks after publishing), and then move on to the next type.

For a hands-on walkthrough of the Custom Code method specifically, the course lesson on how to add JSON-LD schema markup via Wix Custom Code covers the exact same process with screen-by-screen detail.

If you are unsure which schema types your site needs, or you want to check whether your existing schema is valid, get in touch for a structured data audit. No guesswork, just a clear report of what is working, what is broken, and what is missing.