Wix to code you own.

[ Why teams move ]

Wix got the company online. Now the website has a pipeline to carry.

Wix is very good at what it promises: a real site, live this week, without a developer. Plenty of businesses were right to start there, and plenty should stay. This page is for a narrower group: software and B2B companies that started on Wix and have since made the website a growth channel.

For that team it shows up as a series of small limits. The layout that would work isn’t one the editor makes easy. The page loads what the builder decides to load. Custom behaviour lives in Velo code that only runs on Wix. And there’s no way to take the site with you, which makes every year a bigger decision. And now a newer one: your team works with AI every day, and the website is the one place its agent can only reach in from outside.

[ Is it time? ]

Three signs your site has outgrown Wix.

Your team uses AI every day, for everything except the website.
Changes queue behind the one person who knows how the site is wired.
The site can’t leave Wix, and every page you add makes that truer.

And it’s fine to stay if the site is a brochure that changes a few times a year and it’s earning what you need it to earn. Wix is a sensible home for that. We’ll tell you which on the Discovery call, with the evidence from your own site.

[ The path ]

From Wix to an agentic website, in six steps.

Step 1

Map your Wix site.

Discovery reads the site as it stands: every page and its mobile layout, the blog, any Wix apps in use and what each one does, any Velo code, and every live URL, including the older URL formats Wix has used over the years. You leave with a roadmap that says what moves, what it becomes, and in what order.
Step 2

Rebuild the design as a system.

Part of what a Wix site looks like belongs to the editor and its templates, so this step separates the two. What’s yours, type, colour, voice, photography, structure, is kept and written into a brand.md. What was the template’s is rebuilt as a component library that fits your brand. Pages are checked against the live site, side by side.
Step 3

Move the content into your repository.

Wix has no site export, so content is read out deliberately rather than downloaded. Pages, blog posts and images are extracted, checked against the live site item by item, and become structured content files. From here your content sits next to the code, under your name, where your agent can read all of it.
Step 4

Add the rails and the machine layer.

The guardrails and skills your agent will run on go in: what it may touch, how a page gets built, what gets checked before anything ships. The machine layer goes in with them: structured data, schemas, llms.txt and a clean sitemap, on pages whose speed no longer depends on what the builder loads.
Step 5

Switch over, with a net.

The redirects go live with the switch, written from your live sitemap and your Search Console data, because Wix URLs aren’t always obvious from the outside. Your domain is pointed at the new site, the Wix site keeps running until the new one takes over, and the Wix plan isn’t cancelled until you’ve watched the new site run.
Step 6

Take the keys.

Your team connects the agent it already uses and ships its first supervised changes in the first week of handover: a real page, a real edit, with us in the room. Whether the site can do something stops depending on what the editor allows.

[ Piece by piece ]

What each part of your Wix site becomes.

	On Wix	On an agentic website
[ 01/ Design ]	An editor layout that started from a template	A component library and a brand.md your agent builds against
[ 02/ Content ]	Pages and blog posts held inside Wix, with no export	Structured content files in your repository. The repo is the CMS
[ 03/ Custom behaviour ]	Velo code that only runs on Wix	Code in your repository that runs anywhere
[ 04/ Add-ons ]	Apps from the Wix App Market	Each job rebuilt, replaced or retired, decided in Discovery
[ 05/ Page speed ]	Whatever the builder loads	A fast, server-rendered site you control
[ 06/ URLs and rankings ]	Wix’s URL formats, old and new	Every URL redirected, metadata carried over, rankings watched through cutover
[ 07/ Making a change ]	Ask what the editor will allow	Brief the agent, check the preview, approve it
[ 08/ When something goes wrong ]	Undo in the editor and hope	A broken layout fails before it ships, and any change can be undone

[ The agent layer ]

On Wix, your agent can query the site. On your code, it builds it.

Wix has moved quickly here. Every Wix site now has its own MCP server, so an agent can connect to it, ask questions of the site’s data and manage some of its content, and Wix has its own AI for generating sites and copy. What the agent can’t do is work on the site itself. The layout, the code and the build belong to the platform, so it can’t see the whole thing, run it, or check its own work before it ships.

On an agentic website the site is plain, structured files in your repository, so the agent your team already uses, Claude, Claude Code, ChatGPT, Gemini, Cursor, Codex, reads all of it and changes any of it. It builds inside your encoded brand and our rails, and the change arrives on a preview. The AI proposes, you approve what ships. A new campaign page becomes a brief, not a ticket, and adding ten marketers doesn’t add to the cost of shipping.

[ Where you land ]

An agentic website: yours, and run by your team.

The keys.

Code and content in your GitHub repository, under your name, from the first commit.
Your agent ships it.

Your team briefs the change in plain language and it lands on a preview. The AI proposes, you approve what ships.
Your brand, encoded.

A brand.md in the codebase, so every change, from anyone, is made against your rules.
Our standards, baked into the rails.

More than a decade of design and development standards, checked before anything ships.
The machine layer.

Structured data, schemas, llms.txt and a clean sitemap, so the AI systems answering your buyers can read and cite your site.
The handover.

Playbooks and paired working, until your team runs the site themselves.

[ Recent work ]

Built for SaaS teams like yours.

Autohive: a website that keeps pace with their marketing teamAn AI-agent company's first website, built on a component framework their designers, marketers and agents could all work in, so their marketing team builds its own landing pages and updates without waiting on anyone.Read more
Future of Marketing Work: a brand and website for a three-way eventAn Auckland event on how marketers adapt to digital transformation and AI, brought together by a university, the AI community and an events group. We made the brand, the website and the print.Read more
Landlord Studio: one system for two markets, run by their marketing teamProperty management software for landlords in the US and UK. A five-year-old Webflow build redesigned, migrated onto a component-driven framework, and handed to a marketing team that now builds its own pages with AI.Read more

Will we lose our rankings moving off Wix?

A migration is built to keep them. Every live URL is mapped to its destination before anything moves, metadata travels with it, and rankings are watched through cutover so anything that shifts is caught and fixed. Wix sites can carry unusual URL history, so the map is built from your live sitemap and your Search Console data rather than from assumptions.

How long does a Wix migration take?

The roadmap sets the timeline. It depends on the number of templates more than the number of pages. What stays fixed is the cadence: something visible ships every fortnight, from the first fortnight, on a live preview.

What happens to our Wix apps and Velo code?

Each one is read as a job rather than a thing to port. Forms, SEO settings and analytics become part of the site itself. Velo code is rewritten as ordinary code in your repository. Anything the business depends on that only Wix provides, a store, bookings, a members area, is listed in Discovery with a plan before anything moves.

Wix has AI and an MCP server now. Isn’t that enough?

For answering questions about the site and managing some content, it helps. The difference is reach. On Wix the agent connects to the platform; it doesn’t work on the site. On code you own it works on the site itself: it can see all of it, run it, and check its own work before anything reaches a preview. If your team wants the agent doing the legwork across the whole site, that’s the case for moving.

Can our team still make changes ourselves?

More than before. Anyone on your team describes the change in plain language, the same way they’d brief a designer. The agent builds it inside your encoded design rules and it arrives as a preview for someone to approve. Nobody writes code or opens a terminal, and nothing ships without a person saying yes.

What’s the alternative to Wix for a marketing team?

The usual answers are another builder such as Squarespace or Webflow, or WordPress. Each solves the limit you’ve just hit and brings its own. The third option is to own it: the site as code in your own repository, with your team’s agent making the changes inside rules we set, and a person approving each one. That’s an agentic website , and a migration is how most teams get there.

Can we export our Wix site?

No. Wix doesn’t offer a way to export a site and host it somewhere else, which is why this is a rebuild rather than a transfer. Content is read out page by page and checked against the live site, the design is rebuilt as components, and your domain comes with you.

Isn’t Wix fine for a software company’s marketing site?

Early on, yes. It gets a credible site live while the product is the priority. It stops being fine when the website becomes how the company gets found: when you’re running campaigns, shipping pages every week, and caring how fast the site loads and how AI systems read it. That’s the point this page is for.