SEO Wix

I start with the sitemap. Wix generates one automatically, but I've seen it exclude pages from a collection if the template has a broken indexing rule. I submit the XML URL to Google Search Console, then I check the Coverage report for any 'Submitted URL not selected' warnings. That's usually a canonical issue. Next, I audit the [canonical tags](/canonical-tag/) on every dynamic page. Wix defaults to 'self', but if your collection uses query parameters (e.g., ?sort=price), those URLs are not canonicalised. You must set a master URL in the page settings. I once saw a client's product pages indexed under three different parameter variations—Google chose the wrong one. After fixing the canonicals, I configure [301 redirects](/301-redirect/) for any old URLs. Wix's redirect manager is straightforward, but you need to do it manually. I then connect the site to Google Search Console and check the mobile usability report. Wix sites are responsive by default, but I always test on a real phone because the emulator can miss layout shifts. Finally, I run a [Core Web Vitals](/core-web-vitals/) audit using PageSpeed Insights. The biggest gains come from compressing images and removing unused apps. I aim for LCP under 2.5 seconds and CLS below 0.1. That usually means replacing large hero images with WebP and deferring third-party scripts. The entire process takes about three hours for a typical Wix site, but it prevents weeks of indexing headaches. I also check the [robots.txt](/robots-txt/) to ensure no important pages are blocked. Wix allows you to edit it, but the default is clean. Still, I verify.

The biggest trap is assuming Wix handles everything. It doesn't. For example, the canonical tag default is often 'self', but if you use a dynamic collection page, the same URL can have multiple versions (e.g., with different query parameters). Wix does not auto-canonicalise parameter variations. I've seen sites where product pages were indexed under ?colour=red and ?colour=blue, both ranking against each other. You must manually set the canonical URL in the page settings. Another watch-out is [duplicate content](/duplicate-content/) from blog tag archives. Wix creates separate pages for each tag, and they often have thin content. I deselect 'Let search engines find this page' in the blog settings for those tag pages. Performance is also a gotcha. Wix's image CDN is fast, but adding a heavy app (like a live chat or a popup) can tank your LCP. I once saw a site drop from 1.2s to 3.5s after installing a third-party gallery app. Remove unused apps and test after every change. Mobile usability is another area where Wix's preview lies. The mobile editor is separate, but sometimes elements overlap or become too small on actual devices. I test with Chrome DevTools device emulation and then on a real phone. Finally, watch out for the default meta titles and descriptions. Wix pulls them from the page name unless you overwrite them, so you often end up with 'Home | Wix Site' as the title. I write unique titles and descriptions for every page, keeping them under 60 and 160 characters respectively. And I never rely on Wix's 'SEO Wizard'—it recommends generic changes that often hurt more than help.

I used to believe that Wix sites were inherently slower than custom-built ones. That was wrong. I ran a performance test on a well-optimised Wix site and a WordPress site with the same content. The Wix site had a better LCP (1.2s vs 1.8s) because its image CDN is faster. The issue is not the platform but the configuration. I also thought that Wix's automatic sitemap was always complete. It isn't. I missed it the first time I worked on a Wix ecommerce site—the sitemap only included the homepage and two collection pages, ignoring 50 product pages. The problem was that the product template had a 'No index' checkbox enabled by default. I had to uncheck it and regenerate the sitemap. Another mistake: I assumed that Wix's mobile responsiveness was perfect. I once optimised a site on desktop, only to find that the mobile version had a huge white gap at the bottom caused by a floating element. I now check the mobile viewport carefully. I also underestimated the importance of [JavaScript SEO](/javascript-seo/) on Wix. Wix uses client-side rendering for some components. If you load content via JavaScript, Google may not see it. I now use the Wix Corvid dev tools to pre-render critical content. Finally, I assumed that Wix's built-in SEO tools were enough. They are not. I still need to manually set up structured data, handle redirects, and monitor index coverage. The platform is a good starting point, but not a set-and-forget solution.