Wix · Website builder

Wix SEO audit: the issues built into Wix — and how to fix them

A Wix SEO audit checks your store across search, AI visibility, accessibility and security — with a fix for each issue we find.

A hosted website builder that has invested heavily in SEO since its rocky early reputation — but limited technical control and JavaScript-heavy rendering still shape what you can fix.

How does Wix's architecture shape your SEO?

Wix is a fully hosted builder where you work in a visual editor, not in code. It earned a poor SEO reputation years ago because pages were client-side rendered; Wix has since moved to server-side rendering and added a proper SEO toolset (Wix SEO Wiz, editable meta, robots, 301s). The constraints that remain are the real story: you can't fully control the server, the markup is JavaScript-heavy and component-generated, and Wix Stores imposes its own URL patterns. Most fixes happen through the Wix SEO dashboard and per-page settings rather than in files.

Reference: Wix SEO help center →

What issues show up most on Wix sites?

Why these happen on Wix

Specific to how Wix is built — not generic checklist advice.

SEO

JavaScript-heavy rendering and Core Web Vitals

Wix pages ship a lot of framework JavaScript. Even with server-side rendering, heavy pages and large images push LCP and INP into failing territory on mobile. You can't restructure the build, but you can compress images, limit animations and third-party widgets, and trim unused sections — which is where the wins are.

SEO

Limited technical SEO control

Wix gives you meta tags, canonicals, robots, and redirects through its dashboard, but not the file-level control of a self-hosted site. Audit what you actually can set — many Wix stores leave default titles, missing canonicals, or unconfigured 301s simply because the settings live in a dashboard they haven't opened.

AEO

Wix Stores product structured data

Wix Stores can output Product schema, but coverage depends on your settings and template. Verify that price, availability, and review markup are actually present in the rendered page so your products are eligible for rich results and AI shopping answers.

Full fix guide →

Fixes written for Wix

We catalog 173 Wix fixes — exact steps for Wix's admin and theme, each with a link to the official docs.

Catalog coverageSEO

Audit your XML sitemap and internal linking so that every product and category page is discoverable and crawlable by Google — not hidden behind JavaScript, pagination, or missing links.

On Wix
  1. 1Wix automatically generates and submits a sitemap for your store. Verify it at yoursite.com/sitemap.xml.
  2. 2Wix Dashboard › Marketing & SEO › Get Found on Google: follow the SEO Setup Checklist to connect Google Search Console and submit your sitemap.
  3. 3Wix Dashboard › Marketing & SEO › SEO Tools › SEO Patterns: ensure the Product Pages pattern is set to 'Indexed' (not noindex).
  4. 4For each product: Wix Editor › Product Page › SEO (Wix SEO Wiz or the Settings panel) — confirm 'Hide this page from search results' is NOT checked.
  5. 5Wix Dashboard › Store Products: confirm all products are set to 'Visible' — hidden products are excluded from the sitemap.
  6. 6Check internal links: ensure your store navigation menu (added via Editor › Menus & Pages) includes links to all main product collections/categories.
Code · Generic HTMLhtml
<!-- CORRECT: Standard crawlable link -->
<a href="/products/blue-running-shoes">Blue Running Shoes</a>

<!-- WRONG: JavaScript-only — Googlebot cannot follow this -->
<span onclick="navigate('/products/blue-running-shoes')">Blue Running Shoes</span>

Standard crawlable product link — use plain <a href> tags, never JavaScript-only click handlers, for navigation links that Google must follow.

Wix docs →
Cwv clsSEO

Eliminate unexpected layout shifts by reserving space for every image, video, embed, and dynamically injected element so nothing jumps when the page loads.

On Wix
  1. 1Images: In the Wix Editor, click any image → Settings → ensure 'Fit' or 'Fill' mode is set and the image container has a fixed height. Wix renders its own image component with reserved space, but if you've set container height to 'auto' it can collapse before the image loads — set an explicit pixel height on the container.
  2. 2Strips / sections: For each section strip, go to the strip settings and set a fixed minimum height rather than 'fit to content', especially for sections containing images or embeds.
  3. 3Cookie banner: In Settings → Cookie Banner, choose 'bottom' position so it appears as an overlay, not a top push-down that shifts content.
  4. 4Wix Chat / bookings widget: These are rendered by Wix natively with reserved space. If using a custom HTML embed (Add → Embed Code → HTML iframe), set an explicit height on the iframe element in the embed settings panel.
  5. 5Fonts: Wix manages font loading internally; you cannot add font-display descriptors directly. Use Wix's built-in font choices (available in the Text settings panel) rather than custom uploaded fonts to minimise FOUT-related shifts.
  6. 6Verify: Use Wix's built-in SEO tool (Marketing & SEO → SEO Tools → SEO Assistant) and cross-check with PageSpeed Insights; target CLS < 0.1.
Code · Generic HTMLhtml
<!-- CORRECT: explicit width and height prevent layout shift -->
<img
  src="/images/product-red-sneaker.jpg"
  alt="Red canvas sneaker, side view"
  width="800"
  height="800"
  loading="lazy"
>

Always declare width and height on every img element. The browser uses these to reserve space before the image file downloads.

Wix docs →
Cwv inpSEO

Reduce Interaction to Next Paint (INP) to under 200 ms by breaking up long JavaScript tasks, deferring non-critical third-party scripts, and lightening event handlers so the page feels fast and responsive after every tap or click.

On Wix
  1. 1Open the Wix Editor. In the left panel, go to Add Apps → Manage Apps and remove any app whose functionality you no longer actively use — every Wix app can add JavaScript weight.
  2. 2In the Wix Editor, select any embedded HTML/custom code widgets (via Settings → Custom Code or via Velo) and check whether their scripts can be moved to load 'After body start' or set to load on interaction rather than on page load.
  3. 3Go to Settings → Custom Code (in the Dashboard). For third-party scripts (chat, analytics, pixels), set the 'Load' timing to 'Load when page is ready' or 'Load after user interaction' if that option is available for your script.
  4. 4In Velo (Wix's dev environment), review any `$w.onReady()` code that runs large synchronous operations. Break heavy logic into smaller async steps using `async/await` and `setTimeout` to avoid blocking the main thread.
  5. 5Use PageSpeed Insights with your live Wix URL and the Chrome DevTools Performance panel to identify which specific interactions have the highest INP.
Wix docs →
Cwv lcpSEO

Reduce Largest Contentful Paint (LCP) to under 2.5 seconds by serving the hero image in a next-gen format (WebP/AVIF), preloading it, and eliminating render-blocking resources.

On Wix
  1. 1IDENTIFY LCP IMAGE: Run PageSpeed Insights on your Wix site URL. The LCP is usually the large image/strip at the top of your homepage.
  2. 2WEBP: Wix automatically serves images in WebP to supporting browsers — no conversion needed. Ensure your source image is high quality JPEG/PNG uploaded through the Wix Media Manager.
  3. 3OPTIMISE IMAGE SIZE: In the Wix Editor, click the hero image/strip › Settings › change the image to the smallest dimensions that still look sharp (e.g., 1500px wide for a full-width banner). Oversized source images slow delivery even after auto-conversion.
  4. 4PRELOAD (LIMITED): Wix does not allow direct <head> tag editing on standard plans. Upgrade to Wix Studio or use Wix's Velo (Dev Mode) to inject a preload link via the wix-seo API: import wixSeo from 'wix-seo'; wixSeo.setLinks([{rel: 'preload', href: 'YOUR_IMAGE_URL', as: 'image'}]);
  5. 5DEFER JS: Wix controls most JS loading internally. Minimise third-party apps (Wix App Market) that inject scripts — every unused app adds render-blocking weight. Remove apps you do not actively use.
  6. 6LAZY-LOAD: Wix applies lazy-loading automatically; for the hero image, position it as a 'strip background' or 'above-the-fold' element so Wix's engine prioritises it. Wix Studio users can set fetchpriority via custom properties.
  7. 7VERIFY: Re-run PageSpeed Insights after publishing changes.
Code · Generic HTMLhtml
<!-- Step 1: Preload the LCP hero image -->
<link
  rel="preload"
  as="image"
  href="/images/hero-banner.webp"
  imagesrcset="/images/hero-banner-400.webp 400w,
               /images/hero-banner-800.webp 800w,
               /images/hero-banner-1500.webp 1500w"
  imagesizes="100vw"
  fetchpriority="high"
>

<!-- Step 2: Hero <img> tag — eager, high priority, no lazy-load -->
<img
  src="/images/hero-banner-1500.webp"
  srcset="/images/hero-banner-400.webp 400w,
          /images/hero-banner-800.webp 800w,
          /images/hero-banner-1500.webp 1500w"
  sizes="100vw"
  alt="[Descriptive alt text for your hero image]"
  width="1500"
  height="600"
  loading="eager"
  fetchpriority="high"
>

Add inside <head>, immediately after <meta charset>. Replace the href with your actual hero image CDN URL.

Wix docs →

Browse all 173 Wix fixes →

Wix on the open web

1.8% of the crawled web runs Wix

281,945
live Wix sites
#3
of 6 ecommerce platforms
1.8%
share of all crawled sites

Losing share — -3.7% over the last 6 monthly crawls

Source: HTTP Archive — a real-Chrome crawl of 15.5M origins (2026-09-01). Share of all crawled sites, not just ecommerce.

How AI reads Wix sites · AEO

98% of Wix sites publish structured data

JSON-LD is the schema.org markup AI answer engines read to understand — and cite — a page. SEOLZ checks whether your structured data is present, valid, and visible to AI.

98%
publish JSON-LD
100%
have Open Graph
0%
JSON-LD only via JS

Source: HTTP Archive — structured-data probes on static + rendered HTML across 421,337 Wix sites.

The typical Wix site · HTTP Archive

How Wix sites measure up

Performance — median

2.7 MB
page weight
219
requests
6.2s
load time

Accessibility gaps — share of sites

77%
empty image alt
16%
unlabelled fields
79%
non-semantic controls

Source: HTTP Archive lab performance + accessibility probes across 421,337 Wix sites. SEOLZ measures your site against these.

Every scan checks all six pillars

You can't rank what AI can't read. SEO, AEO, and GEO tell you where you rank; WCAG, OWASP, and Lifecycle determine whether search and AI can read and trust you at all. SEOLZ scores all six as one system.

🔍
SEO

Your catalog pages may be invisible to Google right now and you'd have no way to know. Indexability gaps, canonical conflicts, and faceted navigation issues silently kill organic traffic — we surface every one and tell you which to fix first.

Learn how to fix SEO issues →
✨
Answer Engine (AEO)

When someone asks ChatGPT to recommend a product in your category, is your store in the answer? Often it isn't. We check the structured data, page structure, and brand signals that help search and AI understand your products and describe them accurately — and we measure whether they actually cite you, or a competitor.

Learn how to fix Answer Engine (AEO) issues →
🌐
AI Visibility (GEO)

AI search is eating traditional organic traffic. We track your actual brand mentions across ChatGPT, Perplexity, and other AI engines — and tell you what's pushing you down in the results.

Learn how to fix AI Visibility (GEO) issues →
♿
Accessibility (WCAG)

Ecommerce stores are among the most frequent recipients of ADA accessibility demand letters. We run WCAG 2.1 AA checks across your catalog, surface the barriers that most often appear in demand letters, and track each one through to a verified fix.

Learn how to fix Accessibility (WCAG) issues →
🛡️
Security (OWASP)

A missing security header exposes your customers, and a compromised or flagged site loses search visibility fast. We check the server configuration, HTTPS setup, and email authentication issues that erode trust — before they become an incident.

Learn how to fix Security (OWASP) issues →
⏳
Site Lifecycle

SSL expires. Plugin versions fall behind. GTM containers go unverified. These aren't hypothetical risks — they're the operational failures that cause outages, ranking drops, and security incidents. We catch them before they happen.

Learn how to fix Site Lifecycle issues →

Start free. Upgrade when ready.

Scout
Free
1 site · 50 pages/audit · monthly audits
6-pillar welcome scan
  • ✓Composite + pillar scores
  • ✓Issue counts
  • ✓Recurring five-pillar re-scan
  • ✓Free forever
Start free
Starter
$49/mo
1 site · 500 pages/audit · weekly audits
All 6 pillars
  • ✓Every finding across all 6 pillars, with step-by-step fixes for your platform
  • ✓Template fixes: fix it once, clear it on every page built from that template
  • ✓Fix tracking: mark it fixed and the next audit confirms it
  • ✓Email alerts for score drops, new security issues, and SSL / domain expiry
  • ✓Report builder with PDF, HTML and Markdown export
  • ✓GTM & tracking audit, plus Search Console topic gaps
Choose Starter

Questions about Wix audits

Does SEOLZ work with Wix?+

Yes — we crawl your live Wix site exactly as Google sees it, and our fixes point you to the specific Wix SEO dashboard and per-page settings to change.

Is Wix bad for SEO?+

Not anymore — Wix now renders server-side and has a full SEO toolset. The real limits are technical control and JavaScript weight. We focus on what you can actually change within Wix, so the recommendations are achievable.

How do I fix SEO issues on Wix without code?+

Almost everything on Wix is dashboard-driven: meta and canonicals in SEO settings, redirects in the URL redirect manager, performance via image and widget cleanup. We tell you which screen each fix lives in.

See what's holding back your Wix site

Free scan, no credit card, results in minutes. We've got you.

Scan My Wix Site Free