CMS / WIX
Wix: Complete Guide to the Website Builder, CMS, Dynamic Pages & Website Design
Wix combines visual website creation, CMS capabilities, dynamic content, hosting, business tools, SEO controls, ecommerce and developer features in a hosted website platform.
This guide uses Wix’s own terminology accurately, with honest comparisons and no invented plan limits or pricing.
- Wix Editor and Wix Studio, and how they differ
- Collections, fields, items, datasets and dynamic pages
- SEO, apps, Velo, ecommerce, hosting and migration
Collections hold the content, datasets connect it, dynamic pages display it. Those three concepts are the heart of the Wix CMS.
THE BASICS
What Is Wix?
Wix is a hosted website creation platform. You design sites visually in a browser, store structured content in a CMS, extend functionality through apps, and publish to Wix’s own infrastructure — hosting, SSL and domains included.
The description people reach for is “drag-and-drop builder”, and it undersells what the platform now covers. Alongside visual editing there is a genuine CMS with collections and dynamic pages, an app marketplace, ecommerce, bookings, a developer platform called Velo, and SEO controls that go well beyond a title field.
The defining characteristic is that everything is hosted and integrated. There are no server updates, no plugin version conflicts and no security patching. You work within one company’s platform — its capabilities, its pricing, its roadmap — which is a genuinely different proposition from self-hosted software.
Wix is also not one editing environment but two. Wix Editor and Wix Studio are separate products with different workflows, and knowing which you are using determines which instructions apply. A great deal of confusing Wix advice comes from mixing the two.
On plans and limits: Wix pricing, storage, collection limits, form handling and feature availability vary by plan and change over time. Check wix.com for current figures rather than any article’s.
What Wix combines
Built around getting a site made and running it yourself.
Built for people making sites for other people.
TWO ENVIRONMENTS
Wix Editor and Wix Studio
Wix Editor is the long-standing visual environment. You work with templates, sections and elements, designing pages directly with separate desktop and mobile views. It is built around someone making and running their own site.
Wix Studio is the professional environment, aimed at agencies, freelancers and web creators building for clients. Its layout model is responsive-first with finer breakpoint and scaling control, closer to how a designer who knows CSS would expect to work, plus workflows built around teams and client projects.
They share the CMS, dynamic pages, Velo and apps. What differs is the editing model and the workflow around it.
Neither is better. They target different people doing different work. Studio’s extra control is an advantage if you want it and overhead if you do not — a small business owner updating their own site is well served by the Editor and would find Studio’s layout model unnecessarily involved.
The practical consequence worth knowing: tutorials and documentation are often specific to one environment. If instructions do not match what you see, check which product you are in before assuming something is broken.
BUILDING PAGES
Elements, Layout and Responsive Design
Wix pages are built from sections containing containers and elements — text, headings, images, buttons, galleries, forms, menus, videos, embeds and repeaters. Both editors expose this structure, though the layout behaviour differs between them.
How you place elements affects the published markup, which matters for both SEO and accessibility. Choosing a heading element because the size looks right, rather than because it is a heading, produces the same semantic problems it would anywhere else.
On responsive design: Wix handles a good deal automatically, and that is genuinely useful. It is also where expectations need managing — Wix does not guarantee every design works perfectly on every screen. Elements positioned freely at desktop width can overlap or misalign on narrow screens, and text sized for a large viewport can become unreadable.
The Editor provides a separate mobile view where you adjust layout for small screens. Studio works from a responsive-first model with breakpoints and scaling behaviour. Either way, checking every screen size before publishing is work you have to do, not something the platform does for you. See our responsive design guide.
└── Section — a major page region
├── Container
│ ├── Heading
│ ├── Text
│ └── Button
├── Repeater — repeating layout
│ └── Item layout
└── Gallery
Structure affects published markup, headings and reading order.
You design the item layout once. Connected to a dataset, the repeater renders one copy per collection item.
COLLECTION: PROJECTS
Illustrative structure. You define which fields a collection has and of which types.
CMS
Wix CMS: Collections, Fields, Items and Datasets
The Wix CMS stores content separately from page design. Instead of typing a team member’s details onto a page, you store them in a collection and connect page elements to that data.
A Collection is a structured set of content for one type of thing — Blog Posts, Team Members, Projects, Testimonials, Events, Locations, FAQs. Collection Fields define what each record can hold, with types including text, rich content, image, file, number, date, boolean, URL, address, email, phone, and the relational ones: reference and multi-reference. A Collection Item is an individual record holding values for those fields.
Then there is the concept people find least intuitive. A dataset is the connector between collection content and page elements. It determines which collection is used, which items load, how they are filtered and sorted, and how many appear. Elements on the page connect to the dataset, and the dataset supplies the values.
Two clarifications that save confusion. A dataset is not the collection — it is the connection to it, and one collection can be used by several datasets with different filters. And a dataset is functional rather than visual: it does not appear as an element on the published site.
Most “my CMS content is not showing” problems are dataset problems — the wrong collection connected, a filter excluding everything, or elements not actually connected to the dataset.
DYNAMIC PAGES
Dynamic Pages: List, Item and Category
Dynamic pages are what make the CMS worth using. One page design displays different collection items, generating a unique URL for each — so a hundred projects means one design, not a hundred pages.
There are three kinds, and they do different jobs.
A dynamic list page shows multiple items from a collection, usually through a repeater, gallery or table, with filtering and sorting controlled by the dataset. This is your projects index or blog listing.
A dynamic item page is the detail view. One design renders every item in the collection, each at its own URL — the individual project page or blog post. Editing the design updates every generated page with it.
A dynamic category page groups items through a category collection, so selecting a category shows the items belonging to it. A recipes site with Indian, Italian and Japanese categories would use one category page design for all three.
Dynamic URLs are built from a page-link field in the collection, usually derived from the item title. The URL pattern is configured in the dynamic page settings. Plan these before publishing — changing them later changes live URLs, which means setting up redirects.
Five pages, each designed and updated separately. Adding a sixth means building another.
One design, many URLs. Adding an item adds a page automatically.
│
├── Item 1 → /projects/item-one
├── Item 2 → /projects/item-two
├── Item 3 → /projects/item-three
└── Item 4 → /projects/item-four
↓
ONE DYNAMIC ITEM PAGE
Same design, different content
├── Author → Reference → AUTHORS
└── Categories → Multi-reference → CATEGORIES
PROJECT
├── Client → Reference → CLIENTS
└── Services → Multi-reference → SERVICES
EVENT
└── Location → Reference → LOCATIONS
RELATIONSHIPS & INPUT
CMS References, Repeaters and Forms
Reference and multi-reference fields connect collections. A reference field points one item at a single item in another collection — a project at its client. A multi-reference field points at several — a project at multiple services.
These make genuinely useful structures possible: a client page listing every project referencing it, or a category page listing everything tagged with it. They are also where the Wix CMS has real boundaries. It handles straightforward relational structures well and is not an arbitrary relational database — deeply nested or many-layered requirements will meet limits.
Repeaters are the main display mechanism for list content. You design the item layout once, connect the repeater to a dataset, and it renders one copy per item. Changing the layout changes every copy, which is what keeps a listing visually consistent.
Forms handle contact, enquiry and registration input with fields, validation and submission handling. Submissions can be collected in Wix, trigger notifications, pass to integrations, and in supported workflows write into CMS collections — which is how user-submitted content such as directory entries or reviews can be built.
Form capabilities, submission handling and storage depend on your plan and the form tooling you use, so check current Wix documentation rather than assuming.
SEO
Wix SEO and Dynamic Page Metadata
Wix provides substantial SEO controls: per-page titles and meta descriptions, URL control, Open Graph settings, structured data options, sitemap generation, robots directives, redirects and an SEO setup assistant.
Worth addressing directly: “Wix is bad for SEO” is outdated. It had some basis many years ago and does not reflect the current platform. The opposite claim — that Wix sites rank better — is equally unfounded. No platform produces rankings; content, relevance and implementation do. See our website SEO guides.
The genuinely important piece is dynamic page SEO. On a dynamic page you can connect SEO fields to collection data, so each generated page gets a title and description built from that item’s own content.
Getting this wrong is the common Wix SEO failure: a dynamic item page with a static title means every project or blog post shares identical metadata. Worth checking on any Wix site you inherit — it is invisible until someone looks.
Two further points. URL patterns for dynamic pages come from a page-link field and are configured in the dynamic page settings — plan them before publishing, because changing them changes live URLs. And dynamic list pages with filtering can produce URL variations worth reviewing for canonical handling.
Wix SEO checklist
- Page title and meta description set for every page
- Dynamic page SEO connected to collection fields
- URL patterns planned before publishing
- One H1 per page with a logical heading structure
- Alt text on images including CMS image fields
- Open Graph settings for social sharing
- Sitemap reviewed and submitted
- Redirects set for any changed URLs
- Canonical handling checked on filtered listings
- Internal links placed within content
- Images compressed and appropriately sized
- Performance measured with real-user data
[ ] Page title and meta description set for every page [ ] Dynamic page SEO connected to collection fields [ ] URL patterns planned before publishing [ ] One H1 per page with a logical heading structure [ ] Alt text on images including CMS image fields [ ] Open Graph settings for social sharing [ ] Sitemap reviewed and submitted [ ] Redirects set for any changed URLs [ ] Canonical handling checked on filtered listings [ ] Internal links placed within content [ ] Images compressed and appropriately sized [ ] Performance measured with real-user data
PLATFORM
Hosting, Apps, Velo and Integrations
Hosting is part of Wix rather than something you arrange. Publishing deploys to Wix infrastructure with a CDN, SSL and custom domain support. No server updates, no security patching, no PHP versions — a real reduction in operational burden, and the main reason many small businesses choose a hosted platform.
The corresponding reality: a Wix site cannot be exported and hosted elsewhere as a working site. Content can be extracted, but the site itself lives on the platform. That is worth understanding before committing rather than discovering later.
Publishing runs from editor to preview to live, with version history available for reverting. Domains can be purchased through Wix or connected from an external registrar — follow Wix’s current documented DNS instructions rather than records quoted in any article.
Apps extend functionality from a marketplace covering marketing, forms, bookings, ecommerce, analytics, communication, events and customer management. Some are built by Wix, many by third parties.
Treat them like plugins anywhere: app quality varies. Each adds code to your pages, and apps nobody remembers installing are a common cause of slow Wix sites. Install what you need and remove what you stopped using.
Velo is Wix’s developer platform, letting you add custom JavaScript on the frontend and backend, work with CMS data programmatically, call external services and build functionality the editors do not cover. Wix also provides APIs for programmatic access to site and CMS data, supporting integrations and automation. See our website APIs guide.
Wix Ecommerce
Products, variants, categories, cart, checkout, payments, orders and customer accounts, designed within the same editor. Suits small to mid-sized catalogues. Not equivalent to Shopify or WooCommerce in catalogue depth or app ecosystem.
Wix Bookings
Services, staff, schedules, appointments, reminders and payment — useful for salons, clinics, consultants and trainers. One of the stronger reasons service businesses choose Wix over a general builder.
Wix Blog
Posts, categories, authors, scheduling and comments as a dedicated blogging system, separate from building a blog yourself through CMS collections. Either approach works; the blog app arrives configured.
Automation
Workflows triggered by site events — a form submission creating a contact and sending a notification, or an order triggering follow-up. Useful, and each needs configuring rather than arriving ready.
Multilingual
Wix supports multiple languages with translated pages, CMS content and SEO settings, plus a language switcher. Depth and availability depend on configuration and plan.
Templates
Industry-specific starting points covering structure, styling and sometimes content. A template is a starting point — content, SEO, accessibility and responsive checking all remain to be done.
Common causes of a slow Wix site
- Large, unoptimised images uploaded at full size
- Apps installed and forgotten, each adding code
- Many font families and weights loaded
- Third-party scripts added for one-off purposes
- Heavy animation and video backgrounds
- Very long pages loading everything at once
EXPERIENCE
Accessibility and Performance
Wix provides accessibility tooling — an accessibility checker, alt text fields, heading controls, keyboard navigation support and focus handling. These are useful, and they do not make a site accessible by themselves.
Accessibility depends on how you build and what you write. Headings chosen for size rather than structure, images without meaningful alt text, insufficient colour contrast, link text reading “click here” and forms without labels all produce problems regardless of platform. The checker catches some of this; a keyboard test catches more. See our website accessibility guide.
On performance: Wix handles delivery — CDN, compression, image serving. What remains yours is page weight, and that is where Wix sites most often struggle.
The usual causes are unglamorous: oversized images, accumulated apps, excessive fonts and third-party scripts. None is the platform’s doing, and all are fixable. Measure before optimising rather than guessing — see Core Web Vitals.
One honest note: you have less control over a hosted platform’s output than over a self-hosted site. You cannot restructure how the platform loads its own assets. For most business sites that ceiling is comfortably above what matters; for performance-critical projects it is worth knowing about in advance.
COMPARISONS
Wix Compared With Other Platforms
These describe differences rather than declaring winners. Each platform suits some projects and not others.
Wix vs WordPress
The trade is managed simplicity against ownership and flexibility. Wix removes maintenance and arrives with business tools built in. WordPress gives you ownership, portability and an enormous ecosystem, along with responsibility for keeping it running.
Wix vs Webflow and Squarespace
All three are hosted. Webflow targets people who want direct control over the layout model; Wix targets a broader audience and includes more business tooling. Squarespace sits closer to Wix, with a stronger design-template emphasis and a smaller app ecosystem.
Wix vs Joomla and Drupal
Wix vs WordPress with Elementor
Both offer visual building with a CMS behind it, which makes this the closest comparison — and it still needs care. Elementor is a third-party WordPress plugin, not part of WordPress Core, and not a CMS in its own right. The comparison is Wix against WordPress-plus-Elementor as a combination.
The visual editing experience is broadly comparable in ambition. The differences sit around it. Wix is one subscription with hosting, security and updates handled, plus ecommerce and bookings built in — and the site stays on the platform.
WordPress with Elementor means managing hosting, updates and plugin compatibility, in exchange for ownership, portability and a far larger ecosystem. Which is better depends entirely on whether you want to manage a website or just have one.
FIT
When Can Wix Be a Good Fit?
Wix can be considered when a project’s shape matches what it does well. Fit is the honest question rather than ranking.
Small Business Sites
Where a professional presence matters more than platform flexibility.
Service & Booking Businesses
Salons, clinics, consultants and trainers, where Bookings genuinely helps.
Portfolios
Where visual presentation matters and content volume is manageable.
Marketing Sites
Where a team needs to publish without developer involvement.
Smaller Stores
Where catalogue depth is moderate and design matters.
Self-Managed Sites
Where the owner will maintain it and wants no technical overhead.
And where a project needs closer evaluation:
Complex Backend Logic
Server-side processing beyond Velo and integrations.
Unusual Data Models
Deeply relational or arbitrary database structures.
Self-Hosting Requirements
Where data residency or infrastructure control is mandatory.
Platform Dependency Concerns
Where the inability to move the site is unacceptable.
Large Catalogues
Where commerce depth outweighs everything else.
Performance-Critical Sites
Where you need control over every byte the platform sends.
The consideration deserving most weight is platform dependency. A Wix site cannot be moved elsewhere and remain a Wix site. For a small business that wants a website rather than a web project, that is often a sensible trade for everything the platform handles. For organisations with long-term infrastructure requirements, it is a decision to make deliberately.
Local Business
Service Business
Consultants
Agencies
Restaurants
Real Estate
Portfolios
Professional Services
Events
Education
Blogs
Small Stores
OPERATIONS
Migration, Maintenance and Troubleshooting
Migrating to Wix is a rebuild rather than a transfer. There is no import that recreates a WordPress or Joomla site in the Wix editor — the design is rebuilt and content is modelled into collections.
The order that works: audit the existing site, inventory content, map every URL, plan the design and CMS structure, migrate content, apply SEO settings, set redirects for every changed URL, test thoroughly, publish and monitor.
The step most often skipped is redirects. A rebuild usually changes URL structure, and without mapping old URLs to new ones you lose accumulated search visibility and break every external link pointing at the old site.
Migrating away from Wix deserves honest mention: content can be extracted, but the site cannot be exported as a working site to host elsewhere. Moving off Wix is also a rebuild. Knowing that before you start is better than discovering it in three years.
On maintenance: hosted platforms remove infrastructure maintenance, not website maintenance. Content ages, SEO metadata still needs setting on new pages, forms break, apps accumulate, performance regresses and accessibility needs rechecking after design changes.
These are possible causes rather than diagnoses. The same symptom frequently has several causes.
Maintenance checklist
- Content and CMS items kept current
- SEO metadata set on new pages and dynamic designs
- Forms tested end to end
- Redirects maintained for changed URLs
- Broken links checked
- Unused apps removed
- Analytics reviewed
- Performance measured periodically
- Accessibility rechecked after design changes
- Mobile layouts verified after edits
- Domain and billing current
- Integrations confirmed still working
- Ecommerce and booking flows tested
[ ] Content and CMS items kept current [ ] SEO metadata set on new pages and dynamic designs [ ] Forms tested end to end [ ] Redirects maintained for changed URLs [ ] Broken links checked [ ] Unused apps removed [ ] Analytics reviewed [ ] Performance measured periodically [ ] Accessibility rechecked after design changes [ ] Mobile layouts verified after edits [ ] Domain and billing current [ ] Integrations confirmed still working [ ] Ecommerce and booking flows tested
REFERENCE
Wix Core Concepts at a Glance
Wix’s vocabulary is specific, and using it correctly makes documentation and support considerably easier to follow.
Plan Structure First
Pages, content and URLs before designing.
Use Collections for Repeatable Content
Anything appearing many times belongs in the CMS.
Plan Dynamic URLs
Changing them later means redirects.
Connect Dynamic SEO Fields
Or every generated page shares one title.
Check Every Screen Size
Responsive behaviour needs verifying, not assuming.
Optimise Images
The most common cause of a slow Wix site.
Remove Unused Apps
Each one adds code to your pages.
Maintain Redirects
After any URL change, without exception.
Test Forms Regularly
Silent form failures cost enquiries.
FAQ
Wix: Frequently Asked Questions
Short answers to the questions people ask most about Wix as a website builder, CMS and hosted platform.
NEXT TOPICS
Related CMS Topics
Each platform trades control, ease of use, hosting responsibility and portability differently. Which suits a project depends on the project.
WordPress
A self-hosted open-source CMS with a very large plugin ecosystem.
Joomla
An open-source CMS with hierarchical content and granular access control.
Drupal
An open-source CMS built around arbitrary content modelling.
Webflow
A hosted platform exposing the layout model for precise design control.
Shopify
A hosted commerce platform built specifically for selling online.
Squarespace
A hosted builder with a strong design-template emphasis.
Framer
A design-led site builder with a visual canvas and publishing.
Website SEO
How SEO principles apply across any platform, including Wix.
Explore the CMS Landscape
Continue exploring CMS platforms, hosting, website development, SEO, performance and ecommerce topics.