Wix ecommerce SEO

Wix store SEO using the tools in the panel: patterns for the catalogue, hand-written pages where it counts, redirects before any slug changes.

Wix has more SEO control than its reputation suggests, and the limits are in different places than people expect. You can edit page titles, descriptions and slugs. You can set patterns that generate meta data across a whole catalogue at once. There is a redirect manager, the robots file is editable, the sitemap is produced for you, and the structured data templates for product and collection pages can be edited rather than only accepted.

What you cannot do is restructure the site the way you would on a self-hosted platform. Store product pages carry a fixed segment in the path before your slug. Templates are shared, so a change to the product page changes every product page. Heavy media added in the editor is the usual cause of slow pages, and no setting undoes that.

The practical approach is to lean on the patterns for the long tail of the catalogue, write the pages that matter by hand, and use the editor's constraints as a discipline rather than fighting them. Most Wix stores we look at have never opened the SEO panel beyond the homepage, so there is usually a lot available before any limit is reached.

Native on wix

The SEO panel, with per-page titles, descriptions, slugs and indexing control
SEO patterns that generate titles and descriptions across products and collections at once
A built-in redirect manager for changed URLs
An editable robots file and an automatically generated sitemap
Editable structured data templates for product and collection pages
Alt text and image settings held with the media rather than in the theme

Settings that matter

Use patterns for the catalogue and write the pages that matter

Patterns are the right tool for hundreds of products, because they keep every title consistent and stop items shipping with no meta data at all. They are the wrong tool for your main collections and best sellers, which deserve titles and descriptions written for the specific search. We set a sensible pattern for the tail, then override the pages that carry the traffic, and record which ones have been written by hand so a later pattern change does not overwrite them.

Add the redirect before changing any slug

Slugs are editable, which makes them easy to change on impulse. The redirect manager is where that becomes safe. We make it a rule that no product or page slug changes without the redirect being created in the same session, and we audit the existing list for chains. On a store that has been reorganised a few times, this alone often recovers pages that were quietly dropped.

Edit the product structured data template once

Because the markup is generated from a template, correcting it fixes the whole catalogue rather than one page. We check what is actually being emitted on a live product page, make sure price, currency and availability reflect the real values, and remove anything describing reviews or offers that no longer exist. Markup that contradicts the visible page is worse than no markup, so accuracy matters more than completeness.

Give collections content the template can hold

Collection pages default to a grid, and a grid does not answer a search. We add text sections above and below the products with an introduction, the differences between the options and the questions buyers ask, using the layout tools rather than a code workaround. Keeping it inside the editor means your team can update it later without asking anyone.

What we avoid

Publishing a whole catalogue of pages that differ only by the words a pattern substituted
Uploading large images and video in the editor and expecting a setting to make the page fast
Changing the store's page structure repeatedly, since each change is a set of URLs to redirect

Questions

The slug is yours to write, and the path segment the store adds before it is not something to plan around. It is not the reason a store does or does not rank. Spend the effort on the slug itself, on the page title and on the content, all of which you control fully.

Not in the way people assume. The platform gives you titles, descriptions, slugs, redirects, robots control, structured data templates and a sitemap, which covers the great majority of what a store needs. The real constraints are structural flexibility and page weight from media added in the editor. We have seen far more Wix stores held back by empty meta data than by the platform.

With patterns, using the fields you already hold, so every product gets a title built from its name, its key attribute and your brand rather than being left blank. Then override the products and collections that actually attract search demand. Trying to hand-write several hundred product titles is a project that never finishes and rarely changes anything.

Yes, the templates for product and collection pages can be edited, which means a correction applies across the catalogue. That is more useful than per-page control for a store. The thing to check is that what the template outputs matches what the page shows, particularly price and availability, since those are the values most often left describing an older setup.

Send your wix store.

The plan is written for your store on the platform it runs on.