Wix SEO: What the Platform Handles and What You Still Have to Set Up
Table of contents
Wix SEO is decided by what your site hands to Google, not by the builder's logo. The platform already handles canonicals, sitemaps and hreflang; the loose ends are the blog, redirects and structured data.
Wix SEO: the 2014 myth and the criterion that actually matters
The line "Wix doesn't rank" has been circulating since 2014, when pages shipped as heavy JavaScript and the important HTML appeared after load. That specific problem is solved. This site already has equivalent guides for WordPress and for Shopify, and in all three cases the useful question is the same.
Google evaluates the page, not the builder's brand: useful content, crawlability, links, speed and mobile experience. A well configured Wix site beats a WordPress install with twelve unvetted plugins. The platform sets the technical ceiling; content and daily decisions determine where you land under it.
What does break, over and over, lives in the blog, in structured data and in the weight of apps and images.
What Wix handles for you (leave it alone)
Automatic canonicals, and when to change one
Wix creates a default canonical URL on every page. You edit it only under Advanced SEO, inside Additional Tags, typing the tag by hand, and a Reset to Default button restores the original (Wix documentation).
A canonical is a hint, not an order: Google may ignore it when it detects conflicting signals, as explained in Consolidate duplicate URLs. It is worth changing only when several URLs serve the same content. If that is not your case, leave it alone.
Sitemap and robots.txt: what is already covered
Wix's robots.txt includes the sitemap URL and allows bots to crawl every page by default. It is edited under SEO & GEO, Tools and settings, Robots.txt Editor, which Wix flags as an advanced feature with no support for your changes (editing your site's robots.txt). If you are going to touch it, how to create a correct robots.txt covers the usual mistakes.
The same page explains why a page looks "missing": password-protected pages, members-only pages and pages marked as not indexable are not accessible to crawlers.
And one myth that costs traffic every month: blocking a URL in robots.txt does not remove it from the index. It can still appear in results, without a snippet. To exclude it you need noindex, per Google's robots.txt guide. A sitemap, meanwhile, is a crawl hint rather than an indexing guarantee (sitemaps documentation); the mechanics are in how to set up XML sitemaps.
hreflang and x-default with Wix Multilingual
With several languages active, Wix adds hreflang and x-default automatically and lets you edit titles, descriptions, slugs and alt text per language (SEO for multilingual sites). Keep versions in subdirectories, the default structure, without mixing subdomains: each variant must be crawlable and link to itself.
The SEO & GEO panel and per-page-type settings
The panel is now called SEO & GEO, and the name acknowledges that part of the traffic arrives from generative answers rather than ten blue links.
Inside is SEO Settings, which groups settings by page type (editor pages, products, blog posts, events), with a defaults tab and a custom values tab. The order that works: defaults first, using title and description variables, then the pages that actually matter, starting with the home page and service landings. Reviewing fifty system pages before those three is wasted time.
The "Let search engines index this page" toggle is the real noindex. Turning it off is the correct way to remove a page from Google; what the tag does is covered in meta robots and noindex.
URLs and redirects: where Wix SEO breaks most often
The automatic 301, except in the blog
When you change a slug, Wix creates an automatic 301 redirect on editor pages, Wix Stores products and categories, Wix Bookings services, Online Programs and Wix Events (301 redirects in Wix).
In Wix Blog it does not. If you change a post's URL, you must create the redirect by hand in the URL Redirect Manager. Skip that step and the old URL returns 404, the link pointing there is lost and the authority it had built goes nowhere. It is the most expensive and most common mistake: renaming a slug "because it looks better" without checking what pointed at it. A 301 exists precisely to preserve signals (Google documentation).
Redirect Manager, group redirects and the custom domain requirement
The path is SEO & GEO, Tools and settings, URL Redirect Manager, + New Redirect, Single redirect: you enter the old path and the new page or an external URL. For several paths sharing a structure there are group redirects, which save you a hundred separate rules.
The requirement everyone overlooks: 301s only work with a custom domain. You cannot redirect from a free Wix URL to a Premium site. If you are coming from another CMS, recreate every old URL you cannot keep; the full procedure is in website migration without losing rankings.
Structured data in Wix: presets, AI markup for the blog and limits
Wix ships preset markup on Wix Stores product pages and can generate AI markup only for Wix Blog posts (toggle under SEO Settings, Blog posts, Customize defaults, Structured data markup), refreshed on publish. For other page types you add JSON-LD by hand (adding structured data).
Three limits the official documentation states clearly and almost nobody reads: only JSON-LD is accepted, each block must stay under 7,000 characters, and whatever you mark up must be visible on the page. That last one is not a Wix quirk: it comes from Google's structured data policies, and if the data is not visible there is no rich result. To start from scratch, rich snippets and schema markup is the entry point.
Validate on the published URL with the Rich Results Test, never on the draft. And remember that correct markup guarantees neither a rich result nor better rankings on its own.
What Wix will not fix: content, speed and internal links
Speed and Core Web Vitals: what is up to you
Without server access, your margin sits in what you load: compressed images in a modern format, correctly sized and lazy-loaded except for the main one; fonts that do not block rendering; and above all third-party apps and scripts, which pile up widget after widget into whole seconds. Choosing the right image format saves more than any trick, as shown in WebP vs AVIF.
Measure with field data, not just lab tests: PageSpeed Insights and the Core Web Vitals section of Search Console reflect real users.
Thin content and pages that add nothing
Some system pages get indexed by accident: empty blog tags and categories, paginated archives, thank-you pages and product duplicates created by variants. Review them with site: searches and Search Console, then decide between noindex and consolidation; you do not need to delete anything for them to stop competing with each other. The other loose end is blog internal linking: without contextual links between posts, new ones take months to collect signals.
Checklist: Wix SEO in 10 steps
- Custom domain connected: without it there are no 301s.
- SEO & GEO panel reviewed, defaults first.
- Unique titles and descriptions on your top ten pages.
- Final slugs before publishing; in the blog, a manual 301.
- Default robots.txt, without blocking CSS or JavaScript.
- noindex on system pages and on pages that should not compete.
- Schema: presets where they exist, manual JSON-LD under 7,000 characters.
- hreflang and x-default checked if more than one language is live.
- Core Web Vitals measured in the field, apps pruned one by one.
- Search Console connected and sitemap verified without errors.
The builder handles the mechanical part; the judgement stays with you. Coming from another platform, the menu paths change, not the principles.