Wix SEO: a map of every control, and the one you cannot have

Wix SEO settings are spread across three places, and knowing which is which saves an hour of hunting. Per-page controls live in the SEO panel attached to each page. Site-wide behaviour — redirects, robots, the structured-data defaults — lives in the dashboard under Marketing & SEO. And a third category, the one this page spends most of its time on, is made of things that look like settings but are not: fixed platform behaviour you will have to design around instead.

One piece of context before the map, because it changes how you read everything after it. Wix pages are server-side rendered. The objection that shaped this platform's reputation — that the content arrived as JavaScript and crawlers saw an empty shell — describes a version of Wix that no longer exists. That does not make Wix a good choice for every project, and the rest of this page is not an argument that it is. It means the old objection is spent and the real trade-offs are elsewhere.

Titles and descriptions, per page and by pattern

Each page carries its own SEO panel with a title tag and meta description field. Fill them in and they override whatever Wix would otherwise generate. That much is unremarkable; every builder in this class does it.

The part worth understanding is the layer above. Wix also supports site-wide patterns — templates that generate a title from variables such as the page name and the site name — which is genuinely useful on a shop with two hundred products and genuinely dangerous on a brochure site with nine pages. A pattern applied across a small site produces nine titles that differ only by a noun, and near-duplicate titles are one of the few on-page problems that is both easy to create and easy to see in a crawl. Set the pattern, then override it by hand anywhere the page deserves better. The general case for doing that is in the note on meta fields.

Slugs, and the path segment that is not negotiable

Page slugs are editable per page from the same panel, and changing one is the normal way to fix a URL that was named badly at build time. There is no site-wide find-and-replace, so a restructure is a page-at-a-time job.

Blog posts are where the platform stops negotiating. Wix documents that the /post/ segment in a blog post's URL cannot be removed. Every article you publish will live at a path containing it, permanently, and no setting anywhere changes that. It is not a ranking problem in any sense anybody has demonstrated — but it is a permanent structural decision you are accepting on the day you choose the platform, and it is the single most common reason people migrate off a Wix blog years later and then have to redirect every URL they ever published. The wider pattern of builders imposing path segments is covered in what builders do to your URLs.

The redirect manager

Wix's URL Redirect Manager lives in the dashboard under Marketing & SEO, handles 301 redirects, and accepts bulk imports rather than making you enter a restructure line by line. It also checks submitted rules for errors and loops before they go live, which is the kind of guard rail that separates a redirect feature from a redirect text box.

In practice this is the control that earns Wix most of its score. A platform that lets you rename things and catch the consequences is a platform you can still reorganise in year three. The comparison across all seven builders is in the redirects note; the short version is that only Webflow and Duda offer meaningfully more.

robots.txt, and the restraint to leave it alone

Wix generates a robots.txt for every site and provides a built-in editor for it. Almost nobody should use it. The default file is sensible, and the overwhelming majority of the reasons people reach for robots.txt — keeping a page out of the index, stopping a thin archive being crawled — are better handled with a noindex directive, because a page blocked in robots.txt cannot be crawled and therefore cannot have its noindex read.

The legitimate uses are narrower than the internet suggests: excluding a genuinely infinite URL space, or a staging path, or a parameter pattern that generates thousands of near-identical pages. If you cannot name which of those applies to you, the right edit is no edit. The longer note on robots, sitemaps and noindex works through the distinction properly.

Canonical tags, including on blog posts

Wix writes a self-referencing canonical on every page by default, which is correct behaviour and needs no attention from you on a normal site. Where it matters is that the default can be overridden: open a page's SEO panel, go to the advanced tab, find the additional-tags section, and the canonical is editable there with a plain URL field.

That override reaches blog posts as well, via the blog's own SEO settings. This is worth saying plainly because it is the exception in this category — most hosted builders that expose canonical control at all expose it on static pages and leave the blog on autopilot. If you syndicate posts elsewhere, or you are consolidating two overlapping articles, this is the control that makes the fix possible without deleting anything.

Custom structured data

Wix adds structured data automatically to the page types where it can infer the shape — products, events, blog and forum posts — and lets you modify those presets or paste your own markup in. The panel has two details that make it better than the feature usually is: it refuses markup that is not valid JSON-LD and warns you about syntax rather than saving something broken, and it links straight out to Google's Rich Results Test from inside the editor.

Temper what you expect from it. FAQ markup will not produce a rich result on an ordinary site — Google restricted FAQ rich results to well-known authoritative government and health sites in August 2023 — and HowTo rich results were withdrawn entirely at the same time. Structured data is still worth shipping because it is how machines read your page, but if somebody is selling you schema work on the promise of snippet decoration, they are quoting a 2022 playbook. The schema note covers what is actually still live.

What none of this buys you

It buys you a site you can configure correctly. It does not buy you a position, and nobody who tells you otherwise can show their working. Google's own page-experience documentation says there is no single signal behind these judgements, and that Search "always seeks to show the most relevant content, even if the page experience is sub-par."

So the honest summary of Wix in 2026 is this: the controls are there, they are better than the platform's reputation, and they are roughly two-thirds of what a developer-grade platform would give you. Whether that is enough depends entirely on what you are going to do with them — which is the question the seven-builder control audit is built to answer.