AI Website Builders Fall into Three Types, but Discussion in China Mostly Covers Just One
Map the landscape of AI website builders first, then decide what role WordPress should play.
AI × WordPress Series · Part 1 of 8
Map the landscape of AI website builders first, then decide what role WordPress should play.View the series contents
I have recently been reading a great deal of English-language material on AI website building: official documentation, reviews and YouTube videos.
My strongest impression was not how impressive the tools are, but how little of this information has reached Chinese-language discussions. English-language communities have debated these tools for over a year, with several distinct approaches and fairly thorough discussions of their strengths and weaknesses. Most Chinese-language content still focuses on the idea that AI can generate a website from one sentence, grouping very different products together.
For export businesses, that information gap has a real cost. If you understand everything through the single label "AI website building," you may choose a route entirely unsuited to your needs, and the mistake may only become apparent a year later.
So this article starts by drawing a clear map, rather than arguing a position.
If you are still assessing how much time AI website building can save, also read Building an Export Business Website Quickly: Which Steps Can AI Save You, and Which Can It Not? Tools determine the production method; they cannot replace source materials, judgment or ongoing operations.
The first distinction: three types, not one
What is commonly called "AI website building" actually covers three different categories. There is one simple way to distinguish them: where the website lives after generation.
Type 1: hosted platforms. The generated website lives on the platform.
A representative example is Harmony, launched by Wix in January this year. You describe what you want in natural language, and its AI agent works directly inside the Wix editor. After generation, the platform handles the servers, database, backend and security updates. Similar offerings include Squarespace Blueprint, Framer, Durable and Webflow's AI features.
This type gives you a complete package: a working site and a backend your colleagues can use to make changes. The trade-off is that the system belongs to the platform. Usually, you can export only the content data, not the design and functionality. Moving elsewhere effectively means rebuilding.
Type 2: code export. The generated website lives with you.
Examples include Lovable and Bolt, followed by v0 and Replit, and then Cursor, Claude Code and Codex, which are technically tools to help developers write code faster rather than website builders.
This type gives you real code that belongs entirely to you and can be changed however you want. The trade-off is that it gives you only code. Deployment, domain connection and ongoing maintenance are your responsibility, and most tools do not provide a content backend. If a colleague wants to add a product, they need someone who can code.
Type 3: generate directly into WordPress. This is barely discussed in Chinese-language communities.
Examples include ZipWP and 10Web. Answer a few business questions and they generate a real WordPress site, with standard themes, plugins and a backend, just like a site built by hand. WordPress itself is also pursuing this direction. Automattic's Telex can generate Gutenberg blocks from a sentence and package them as plugins to install on your own site. Page builders such as Elementor, Divi and SeedProd have also added their own AI features.
The significance is that **the output is an ordinary WordPress site.** All WordPress migration paths, plugins and maintenance methods remain available.
The essential difference between the three types is this:
Hosted platforms give you a backend without ownership; code-export tools give you ownership without a backend; WordPress-based tools give you both, with the responsibility for operations and maintenance.
The second distinction: the three types differ greatly on SEO
This matters especially to export businesses, because it determines whether the site can be found in search. It has only become a serious topic in English-language reviews over the past year.
Code-export tools have a hidden issue. Tools such as Lovable and Bolt generate purely client-rendered single-page applications by default. The first HTML a crawler receives is essentially empty; content appears only after JavaScript runs. Google has a rendering queue and will gradually fill in the gap, but that takes time. Meanwhile, the increasingly important AI crawlers do not run JavaScript.
Your page may therefore look beautiful in a browser while appearing empty to crawlers. This can be solved through prerendering or a server-rendered framework; for example, v0 outputs server-rendered Next.js by default. But that is engineering work, beyond the promise of a single prompt.
Hosted platforms are the reverse. The platform handles rendering and basic SEO, so the issue above generally does not arise. But your depth of control depends on what the platform exposes. For a simple, single-language site, it is usually sufficient. For precise control over multilingual hreflang, URL structure and structured data, confirm that the platform grants that control first.
WordPress-based tools are the most conservative and safest on this point. Because they produce standard WordPress sites, you retain the same SEO tools and degree of control as before.
Where does WordPress fit on this map?
Here is a judgment that may differ from your first instinct.
WordPress is not a fourth option outside these three types. It sits on a different dimension.
The three types of tools address generation: taking a website from nonexistent to existent. WordPress addresses updates: how people will keep changing the site over the years after it is built.
The two are easily confused because almost all English-language content focuses on generation. The reason is understandable: turning one sentence into a website makes a natural video. Someone spending forty minutes changing product specifications in a backend does not make a compelling opening sequence.
**Generation speed does not equal operating cost.** These are independent curves, but most of the information we see plots only the first.
How an export business can identify its situation
Based on the cases I have recently encountered, there are roughly three situations.
Situation 1: you have no website, or the current site can essentially be discarded.
If you have few products, one language and acquire customers mainly through trade shows and social media, a hosted platform can be cost-effective, especially without technical staff. The current polish of products such as Wix Harmony is indeed far better than two years ago. You need to accept an ongoing subscription and greater difficulty moving later.
If you have a large product range, need multiple languages and plan to generate inquiries through search, I suggest looking directly at Type 3. The difference between ZipWP and 10Web is worth explaining: after generation, ZipWP lets you export the site to any host and does not tie you to its hosting. 10Web's output is generally more consistent, but you must use its hosting. Whether to accept that dependency is a decision to make before choosing, rather than leaving it for later.
Situation 2: you already have a WordPress site that has been running for years.
This is the situation I encounter most often, and the one I most want to address.
The question is not whether to switch to an AI builder, but where AI can fit into your existing workflow. Your real assets are not the pages themselves: they are hundreds of products and articles, years of indexing and rankings, and the working habits your marketing team already knows. These do not simply come with you when switching platforms, and rebuilding costs much more than people imagine.
For an existing site, do not begin by asking which tool to switch to. First read how an existing WordPress site can set boundaries between content and structure. If you have already been patching it repeatedly, use the framework for choosing continued maintenance, targeted upgrades or a rebuild to classify the situation further.
WordPress itself has made significant AI moves over the past year. Version 7.0 has integrated some AI capabilities into core, providing a standardized way for external AI tools to connect. In other words, connecting AI to an existing site is easier than it was a year ago and does not require starting over.
Situation 3: you want something for rapid validation.
A landing page, a campaign page or a small site to test market response is fastest with code-export tools and can be ready in hours. SEO and a backend are unimportant in this scenario because the site is not intended to last long. The cost of choosing the wrong tool is close to zero.
Questions worth asking before you choose
If I could leave just one checklist, it would be this:
**A year from now, who will work on this site every week?** If the answer is a colleague rather than you, you need a backend they can understand. That should take priority over the appearance of the pages.
**How many steps does adding a product take?** If it requires an external person, it becomes a procurement exercise every quarter.
**How much indexing and ranking does the site already have?** If it has accumulated these, rebuilding is a cost decision rather than just a technical one. Calculate what you stand to give up first.
**If you want to switch platforms in three years, what can you take with you?** Asking before you choose costs nothing. Asking just before you move may cost an entire website.
Finally
The purpose of this article is straightforward: organize what English-language discussions have already worked through but Chinese-language discussions have barely covered.
My judgment is that none of these three categories will win outright, because they serve different people. The question that matters is how your team will work with the site over the next few years. Once you understand that, choosing the tool becomes the easiest step.
Discuss your website approach
Tell us about your products, content, editing requirements and handover needs so we can discuss a suitable development approach.
Continue reading
Next: Building an Export Business Website Quickly: Which Steps Can AI Save You, and Which Can It Not?