Wix SEO in 2026: what the platform handles and what is left to you

Wix covers the core plumbing in 2026. You set titles, descriptions, slugs and robots per page. It ships an automatic sitemap and an editable robots.txt. It adds an automatic canonical. It has structured data presets by page type. There is a 301 redirect manager. Blog and product URLs have fixed prefixes. Wix also renders pages server side for crawlers.

• Per page SEO panel: title, description, slug, robots
• Automatic XML sitemap at /sitemap.xml
• Editable robots.txt since 2021
• Automatic canonical tags
• Structured data presets for common types
• 301 redirects in a manager
• Fixed URL prefixes for blog and products
• Server side rendering for crawlers

That covers crawl, index and basic appearance in results. You still need to write pages that answer searches, link them well and keep pages fast for users.

Open any page, click SEO settings. You will see fields for the title, meta description, URL slug and robots settings. Fill these on every page you want to rank.

• Title: target about 60 characters. Put the main term first, then a qualifier. Example: Pricing for Acme CRM, monthly and annual plans.
• Meta description: one or two sentences under 155 characters that sell the click. Example: See Acme CRM pricing, monthly and annual. Compare plans, features and support. Start a 14 day free trial.
• Slug: keep it short, use hyphens, match the topic. Example: /pricing, /guides/getting-started.
• Robots: keep index, follow for pages you want in Google. Set noindex for thin or private pages, like /thank-you or /cart.

Wix adds a canonical link automatically. If you clone a page or create variants, check that the canonical points to the main version you want ranked, not to a copy or a query string URL.

For a worked example, edit /pricing. Set the title to Pricing, plans and billing for YourProduct. Set the description. Keep the slug /pricing. Leave robots as index, follow. Publish and test the live URL in the URL Inspection tool in Search Console after it is indexed.

Wix generates an XML sitemap at /sitemap.xml. Submit it in Search Console. It helps discovery but does not guarantee indexing. The sitemap updates as you publish and unpublish pages. You also can edit robots.txt in Wix site settings.

1. 1

   Submit the sitemap

   Copy https://yourdomain.com/sitemap.xml. In Search Console, Sitemaps, paste the URL and submit. Check the status after a few minutes.

2. 2

   Review robots.txt

   In Wix, open the robots.txt editor. Keep User agent: * and Allow for your content paths. Do not block / or your key sections.

3. 3

   Hide utility pages

   Use meta robots noindex on pages like /checkout, /account, /thank-you. Leave them in robots.txt so Google can see the noindex.

4. 4

   Avoid crawl traps

   If you use parameters that create duplicates, keep them crawlable but canonicalised to the clean URL. Check the platform's current settings if you rely on apps that add parameters.

A healthy robots.txt is short. It points to the sitemap and avoids blanket Disallow lines. A healthy sitemap lists only canonical, indexable URLs. If a URL is noindexed or redirects, remove it from internal links and let Wix update the sitemap on publish.

Wix applies structured data presets to common page types. Blog posts get Article. Product pages get Product. Some presets include breadcrumbs or organisation details where relevant. This helps eligibility for rich results.

Check the preset on a template. In the SEO panel for a template or page type, review the JSON LD. If the fields are empty or not a fit, edit them. Use the page’s data fields. Keep one primary type per page. Do not paste overlapping schemas from multiple apps.

• Company pages: ensure Organisation details are accurate. Name, logo, sameAs links.
• Product pages: confirm Product, price, availability, and review fields map to your store data.
• Blog posts: make sure headline, datePublished and author render.
• Breadcrumbs: enable breadcrumb markup if the theme supports it.

Test live pages in the Rich Results Test. Fix errors, then publish again. Example: on /product-page/acme-pro, add missing price and availability so Google can show price in results. On /blog/post/how-we-built-x, ensure Article dates are valid and the author has a name string, not empty.

Wix uses fixed prefixes for some content types. Blog posts live under /post/. Product pages live under /product-page/. You cannot remove these prefixes. Plan your internal links and navigation with them in mind.

Use the redirect manager to keep old URLs working. You can add 301 redirects from any old path to the new Wix path. This protects history and links when you migrate or rename. Keep patterns simple. Test each one.

1. 1

   Map old to new

   Export a list of your old URLs. List their new Wix paths. Example: /blog/building-x to /post/building-x. /shop/acme-pro to /product-page/acme-pro.

2. 2

   Add 301s in Wix

   Open the URL Redirect Manager. Add one-to-one redirects. Avoid redirect chains.

3. 3

   Fix internal links

   Update menus, buttons and in-article links to the new URLs. Do not rely on redirects inside your own site.

4. 4

   Verify in Search Console

   Use the Page with redirect report and the URL Inspection tool to confirm Google sees the 301 and the canonical target.

If you must change a prefix or remove a section later, plan a redirect map first. Publish during a low traffic window. Watch 404s and fix any misses on day one. Use clear 410 Gone only when you retire content on purpose and do not have a replacement.

Core Web Vitals matter. Target Largest Contentful Paint at 2.5 seconds or less, Cumulative Layout Shift at 0.1 or less, and Interaction to Next Paint at 200 ms or less. The field score uses the 75th percentile of real Chrome users over 28 days, per URL or per origin. PageSpeed Insights shows this field data when there is enough traffic, and also runs a Lighthouse test on a mid phone on throttled 4G.

Wix renders HTML for crawlers. For users, speed depends on what you add: images, videos, fonts, apps and interactions. Keep pages lean. The home page and pricing page should load fast. Strip heavy widgets you do not need. Prefer text and images over third party embeds on your key pages.

• Images: upload the right size, use modern formats if offered, and lazy load below the fold.
• Fonts: use system fonts or a small number of weights. Host in Wix settings where possible. Avoid layout jumps with defined font sizes.
• Apps: each adds scripts. Remove apps you do not use. Check their impact in PageSpeed Insights.
• Video: avoid auto play above the fold. Use a poster image and a click to play.
• Animations: keep them subtle. Heavy interactions raise Total Blocking Time and harm INP.

1. 1

   Measure field data

   Open PageSpeed Insights for yourdomain.com. Check the field data cards for LCP, CLS and INP. If there is no field data, use the Lighthouse lab run as a guide.

2. 2

   Fix the LCP element

   Find the largest element above the fold. Make its image smaller, compress it, or move it lower. Avoid render blocking fonts and scripts.

3. 3

   Stabilise layout

   Set fixed sizes for images and embeds. Avoid font swaps that shift content. Reserve space for banners.

4. 4

   Reduce input delay

   Cut unused scripts. Remove slow apps. Avoid long tasks in the main thread that block interaction.

A fixed page looks like this: the hero image is under 150 KB, the headline renders with a system font, the primary button works in under 200 ms on a mid phone. CLS stays at 0 when the cookie banner appears because its space is reserved.

Wix had a poor SEO reputation before 2019. That was then. In 2026, it ships the core features small sites need: page SEO fields, a sitemap, an editable robots.txt, canonical links, structured data presets and 301 redirects. It also renders server side for crawlers. That closes the gap for most use cases.

What has not changed: you work within Wix’s structure. Blog and product URLs have fixed prefixes. You rely on Wix for performance budgets and caching, so heavy apps and designs can slow pages. You do not manage plugins like on WordPress, but you also cannot swap the SEO layer for another. If you need custom URL patterns across the whole site or a bespoke schema system, you may hit limits.

Compare that with WordPress. The CMS ships an XML sitemap and permalink settings. You install an SEO plugin for titles, descriptions, canonicals, robots and schema. You control robots.txt through a plugin. Speed depends on the theme, plugins and host. You get power and risk. On Webflow, you control metadata, canonicals, robots.txt, the sitemap and redirects in the designer and CMS. The risk is heavy interactions and images. On Squarespace, you get per page SEO fields, an automatic sitemap and fixed structured data with fewer knobs. You cannot edit robots.txt.

1. 1

   Set site basics

   Add the site name, primary logo and favicon. Check the default social image. These appear in rich results and shares.

2. 2

   Fill page SEO fields

   For every live page, set a unique title and meta description. Keep slugs short and stable. Use index, follow on public pages.

3. 3

   Check structured data

   Open the templates for products and posts. Review the JSON LD presets. Map fields to your content. Test with the Rich Results Test.

4. 4

   Build internal links

   From / to your key pages like /pricing and /guides/. Add breadcrumbs if the design supports them. Avoid orphan pages.

5. 5

   Submit the sitemap

   Submit /sitemap.xml in Search Console. Fix reported errors. Resubmit after launches.

6. 6

   Review robots.txt

   Open the robots editor. Keep your content allowed. Add the sitemap line. Do not disallow the whole site.

7. 7

   Set redirects

   Add 301s for any changed or migrated URLs. Test each. Update internal links to the final URL.

8. 8

   Measure speed

   Run PageSpeed Insights on your top templates and URLs. Fix LCP, CLS and INP issues. Remove slow apps.

9. 9

   Track queries

   In Search Console, open the Performance report. Watch the queries that drive clicks to /pricing and /product-page/ URLs. Improve titles for low CTR terms.

10. 10

    Ship content

    Publish pages that match search intent: comparisons, alternatives, guides and feature pages. Link them from the home page and hub pages.

When this is done, a search for your brand shows a clean snippet with your logo on the knowledge panel, sitelinks for /pricing and /guides/, and products with price in the results when eligible. Non brand queries pull your guides and comparisons with clear titles and descriptions.

Keep a short routine. New page shipped means SEO fields filled, linked from a hub, checked in the sitemap and tested for speed. Quarterly, review the Search Console Performance report for pages that lost clicks and update them.

• Watch for title rewrites. If Google rewrites a page title, adjust yours. Aim for clarity over stuffing.
• Consolidate thin pages. If two posts rank for the same query, merge them and redirect the weaker one.
• Refresh key posts. Update a guide when it slides down the results. Add new steps and current screenshots.
• Retire dead pages. 301 to a close match. Use 410 only when there is no replacement.
• Audit apps and embeds. Remove slow ones. Replace third party forms and widgets on high intent pages if they cost speed.

For launches and design changes, run a pre launch checklist. Crawl the site, compare counts, test top templates in PageSpeed Insights and verify that /sitemap.xml loads. After launch, check Search Console for spikes in errors and fix within a day.