What Wix Headless is

"Headless" means the part people see (the website) is separated from the part that runs the business (products, bookings, posts, members). Wix keeps running the business part. A developer builds the website part in code and connects the two through Wix's SDK and APIs.

What stays in Wix

• Stores: products, inventory, cart and hosted checkout, payments.
• Bookings: services, staff, calendars, payments.
• Blog and CMS: posts and collections, edited in the dashboard as before.
• Members, forms, events, pricing plans through their SDK modules.
• Hosting, optionally: Wix can host the headless site too ("Wix Managed Headless"), with the domain and SSL handled in Wix.

What the developer builds

• Every page template: home, product, post, service, category, landing pages.
• Navigation, search, filters, forms, animations, SEO tags, structured data, sitemaps.
• Anything an Editor app used to do that isn't in the SDK (chat widgets, some forms, galleries).

Where it fits

• Content-heavy sites where speed and SEO control matter (guides, directories, publications).
• Stores or booking businesses that need a design or flow the Editor can't do, while keeping Wix's checkout.
• Businesses that want the same content on a site and an app.

Where it doesn't

• An owner who edits pages themselves and has no developer.
• Sites that lean on many Editor apps.
• Small sites where a tuned Editor or Studio site would be fast enough.

Things learned from real rebuilds

• Keep checkout on Wix's hosted pages; rebuilding it is where budgets die.
• Some SDK modules are heavy; load them only where needed or call the REST API server-side.
• Test the bare domain and every locale after enabling any Wix site-level feature; a few (multilingual mode, for one) change edge behaviour.
• Keep robots.txt, redirects and the sitemap under your control from day one so rankings survive the move.

Wix Developers: Go Headless · checked Oct 2026