Wix SEO Explained: What the Platform Controls, and Where You're Responsible
Wix jumped from 55% to 71% Core Web Vitals pass rate in a single year (source) -- with no action from site owners. What separates fast from slow Wix sites now is almost entirely source image weight and App Market footprint.
No account needed · Results in ~3 minutes
What Wix handles vs. what you control
Understanding this split explains most audit results and which recommendations are actually actionable for a Wix site owner.
- Multi-CDN delivery: Google Cloud CDN, AWS CloudFront, and Fastly -- not configurable
- WebP and AVIF image conversion + responsive breakpoints -- automatic on all plans
- SSL/HTTPS, cache headers, and gzip/brotli compression -- not configurable
- Security headers on standard plans -- Enterprise-only for custom headers
- Sitemap generation (2-level sitemap index) and robots.txt base -- platform-managed
- PetalBot blocked in robots.txt by default -- platform decision, not yours
- Source image quality before uploading -- the CDN cannot compress what you upload at 8MB
- App Market app selection -- each app you install adds a script to every page
- Above-fold layout: hero image size, animations, and video backgrounds
- Velo custom JavaScript -- adds to platform JS overhead when used
- Third-party embeds via HTML code blocks (Calendly, HubSpot chat, etc.)
- Page meta tags, URL slugs, and per-page SEO settings
- Schema via Wix SEO panel > Structured Data Markup tool
The key insight: Security headers, CDN configuration, image format, and caching are platform decisions on Wix -- not gaps the site owner can close on a standard plan. Stackra distinguishes these from owner-addressable gaps when generating recommendations.
Why Wix sites are sometimes slow
Wix's infrastructure is not the variable. These are, in order of how often each is the root cause.
Heavy source images before upload
Wix's CDN automatically converts images to WebP and AVIF, generates responsive breakpoints, and serves each image at the right size for each device. The format and delivery are handled. But a 6MB hero image uploaded at full resolution will still produce a slow LCP -- the CDN converts the format, not the file weight.
Compress images before uploading. Target under 500KB for above-fold images before Wix's resizing applies. Tools like Squoosh or TinyPNG work at the upload stage. Wix handles format and delivery after that -- source file weight is the owner's lever.
Wix App Market scripts on every page
Every Wix App Market app that loads a script adds it to every page -- there is no way to conditionally load App Market scripts on specific pages only. Unlike WordPress plugins, Wix apps cannot be selectively dequeued. Installing five apps means five scripts loading site-wide.
Audit your installed apps via Settings > Manage Apps. For each: is it actively used today? Remove any that are installed but not in active use. Reducing app count is the primary performance lever available on Wix after compressing source images.
Complex above-fold content
Wix's platform JS payload creates some render-blocking overhead on every page. When the above-fold area adds large hero images, video backgrounds, or heavy entrance animations on top of that, the time before the main content paints (LCP) compounds quickly.
Keep above-fold content simple: one image, minimal animation, no auto-playing video backgrounds. Aim for your hero image to be under 100KB. These are layout decisions -- the platform handles delivery, but you choose what goes in the frame.
Velo custom JavaScript
Wix Velo lets owners add custom JavaScript via a sandboxed environment. Velo code runs in addition to Wix's own platform JavaScript. A simple Velo script adds little overhead. Complex Velo pages with API calls, data queries, or many interactions add meaningfully to load time.
Audit Velo-powered pages for unused code, unnecessary API calls on load, and blocking patterns. If a Velo feature is no longer used, removing it entirely is better than disabling it -- inactive code still loads if it is in the file.
Third-party embeds outside the App Market
Chat widgets, booking tools, and marketing embeds added via HTML code blocks (Calendly, HubSpot chat, Tidio, etc.) load their own scripts entirely outside Wix's optimization layer. Unlike Wix's native apps, these run no infrastructure-level optimizations.
Wix Chat is native and adds no extra script. Wix Bookings is native and adds no extra script. Where a Wix native feature covers the same need as a third-party embed, use the native option -- it carries no additional script cost.
Schema and structured data on Wix
Wix has the strongest native schema capability of any fully managed platform. What your site generates automatically depends on which Wix native apps are active.
Auto: native app schema
Schema is automatically generated by each active Wix native app: Product schema by Wix Stores, BlogPosting by Wix Blog, Event by Wix Events, Service and Booking by Wix Bookings, Organization and LocalBusiness at the site level. If you use Calendly instead of Wix Bookings, you have no Booking schema -- the native app must be active.
Custom schema via Structured Data Markup tool
Wix's SEO panel includes a Structured Data Markup tool that lets you add custom JSON-LD with preset types and dynamic variable injection. This is a UI-based editor -- no code required. You can add FAQ, HowTo, Review, or any Schema.org type through the panel.
Custom JSON-LD via head code injection
You can also inject raw JSON-LD via Settings > Advanced > Custom Code or via per-page Head Code injection. This is more flexible than the Structured Data Markup tool but requires writing the JSON-LD markup directly. Useful for schema types not yet covered by the preset editor.
What you cannot do: server-side schema
Wix does not support server-side rendering of dynamic schema from your own database or external API. All schema is either platform-generated (native apps) or statically injected (custom code). If your use case requires dynamic schema from a custom data source, Wix Velo can supply data to injected markup, but with added complexity.
Native apps vs. App Market
Wix includes many features natively that WordPress requires plugins for. Native Wix apps run on the same infrastructure as the site with no external script overhead. App Market apps add third-party scripts.
Platform quirks Stackra checks for
Wix-specific signals that affect your score -- and the reasoning behind how we handle each one.
Wix improves your site over time
Wix deploys infrastructure improvements to all sites simultaneously -- the 2024-2025 CWV jump (from 55% to 71%) happened with no owner action. A Wix site built in 2022 performs measurably better today than on the day it launched. Stackra accounts for this when interpreting scores.
Security headers are a platform ceiling, not a gap
Custom security headers are Enterprise-only on Wix. Standard plan owners -- including Business and Business Elite -- cannot add or modify response headers. Stackra flags the security grade as a platform ceiling and does not recommend adding headers that cannot be added on standard plans.
WebP and AVIF are automatic
Wix's CDN serves WebP and AVIF to supported browsers automatically on all plans. Stackra does not flag image format as an action item on Wix sites. The right guidance is compressing source files before upload -- format conversion and responsive sizing are handled by the platform.
Wix Ecommerce sometimes fires on service businesses
Wix Bookings and Wix Payments infrastructure triggers 'Wix Ecommerce' detection on service businesses with no actual product store. When Wix Ecommerce is detected alongside zero product schema and no cart signals, Stackra interprets this as service-commerce (bookings, subscriptions) and adjusts recommendations accordingly -- no product page or catalog guidance.
PetalBot block in robots.txt is platform behavior
Wix blocks PetalBot in robots.txt on all sites by default -- this is a platform decision, not something the owner configured. PetalBot powers Huawei's search engine and is blocked because it is resource-intensive. Stackra does not flag this as an SEO issue.
Schema presence depends on which native apps are active
Wix auto-generates schema only for active native apps. A site not using Wix Stores has no Product schema; a site not using Wix Events has no Event schema. Stackra evaluates schema relative to what apps are active -- missing schema is only flagged if the corresponding native app is present and schema is absent.
Score context: how Wix compares
Real-user Core Web Vitals pass rate by platform, mobile. Source: HTTP Archive / CrUX, June 2025 (Wix and Squarespace), February 2026 (Shopify), Web Almanac 2025 (WordPress).
See how your Wix site scores
Stackra detects Wix automatically and adjusts every recommendation to what you can actually change as a site owner. Free, no account required.
~3 minutes · No signup required.