How to build a website with AI without the mistakes everyone makes.

What are your options for building a website with AI?

You have three routes: an AI website builder, a vibe coding tool that generates code from prompts, or a coding agent paired with a developer. With a builder, you write one prompt and get a custom site for your business. And then you edit it in a visual editor. No chat required.

With a code generator, you export the HTML once you like the result. Your domain and hosting plan are bought separately, and you upload your files through a file manager. One video creator calls that 'a little bit too confusing' for beginners, so weigh it before you start. There is also a 24-step walkthrough for non-technical readers that shows you how to build, edit and deploy your free site with Claude Cowork, GitHub and Cloudflare Pages, without writing code.

Judge your route by what your pages ship to a browser: rendering model, script weight, headers, structured data, headings and crawler access. Your route changes how you build. But neither the browser nor crawlers care how you got there, because they receive what your site sends. Run the free assessment on your site to see it.

Which option fits a non-developer, and which needs a developer?

If you are not a developer, pick Squarespace, Shopify, Showit or Wix's basic editor. All four are built for people like you. Webflow, Framer and Wix Studio's editor lean toward developers, so they fit you less if you run a business and have no website background. And if you choose a developer-leaning tool, or export code you must host yourself, expect to need a developer (budget for one before you start). Your skills decide where you land, not the marketing page you read. You know them best.

Squarespace gives you Blueprint AI, a lighter AI builder that leaves creative control with you, or templates you can use with no coding. Jimdo Dolphin is pitched at local businesses. Its AI asks about your business hours, location and services. But the tradeoff is less flexibility if your site is complex or needs a unique layout, so check what your layout requires before you pick. Only you can decide whether that limit costs too much, and no feature list will decide it for you.

One vendor-published comparison says Wix and Squarespace need no technical skills, while Webflow, WordPress and Lovable do. Treat that as the vendor's view, not yours. Test it against what you can do and what you need. A public read of your finished site can't tell you how hard the tool was for you to use; it sees only what your site shipped. So run the free assessment on your pages and see what your visitors get. Evidence beats a comparison table. Check yours.

What should you decide before you prompt anything?

Before you prompt, decide four things: who will edit your site, where it will live, which domain you will use, and what each page must help your visitor do. Write your answers in a one-page note you can reread. The video's 11-step workflow settles the tool, hosting and domain name in steps 1 to 4, and your prompt comes in step 5. So think first. Then type.

Decide how much lock-in you will accept. Platform dependency and vendor lock-in are listed risks of AI-built sites, alongside limited customization, privacy concerns and accessibility gaps, so weigh them for your site. If you can export your content and code, you can move. If you can't, you have chosen a landlord.

Decide what your prompt must contain. Give it your real facts, such as your hours, location, services and the pages you need, so you aren't fixing invented ones. And don't skip the last step. Every AI-generated page still needs your review, editing and fact-checking before you publish it.

How do you keep an AI-built site fast, findable and secure?

To keep your AI-built site fast, findable and secure, check what your pages send to the browser, not how your site looks on your screen. Run your homepage through PageSpeed Insights and read your three Core Web Vitals. Your targets: LCP (loading) within 2.5 seconds, INP (responsiveness) within 200 milliseconds, and CLS (visual stability) within 0.1. Write down your numbers before you change anything. Without them, you have nothing to compare against.

Check your mobile number first. In an audit of 5 AI-built sites, all 5 handled responsive layout correctly. But mobile performance scores were still poor across the board, so a layout that fits your phone doesn't mean your page loads well there. Lab data is a simulated load on one device (a single guess, in effect), whereas field data covers 28 days, which means your lab and field numbers may differ. Read both before you act.

For findability, you must not block Googlebot, and your page must return HTTP 200 with indexable content. Open your robots.txt and your sitemap. On four or five of the five audited sites, these were missing, misconfigured or broken. Only 2 of the 5 handled cookie consent correctly, so test yours. As for security, the assessment reads your response headers, which shows you what your server sends and lets you fix what you find.

What do AI tools get wrong on their own?

AI tools get structure, content and accessibility wrong on their own, and you won't see most of the damage on your page. Start with your H1s and H2s. In an audit of 5 AI-built sites like yours, every one had headings written for how they read, not for what they signal to search engines. And yours may do the same (it's an easy habit to miss). Reread your headings as a crawler would.

Four or five of those five sites also had problems you can check on yours. Look at your heading hierarchy (broken) and your robots.txt (missing or misconfigured). Then check your sitemaps (missing or broken), your category and tag pages (indexed when they shouldn't be), your schema (absent or incorrect), and your mobile performance, which runs weaker than desktop. A canonical tag pointing to the wrong URL changes nothing on your page, so you won't spot it. You see your page, but a crawler reads your source.

Check your copy for repeated wording, weak calls to action, factual errors, outdated information and shifts in tone. Your accessibility can slip too. Look at your images for missing alt text. Check your pages for poor color contrast, and your videos for missing captions. Then tab through your forms with the keyboard and see whether you can use them at all. Run the free assessment on your site, and the problems you can't see by eye will show up on the report.

What does launch day look like, step by step?

The video's workflow gets you to launch in 11 steps: choose a tool, get hosting, install the AI builder, secure your domain, start with a prompt, customize, edit your contact form, edit your header menu and logo, add your pages, edit your site for mobile, then launch. Steps 7 and 10 cover your form and your mobile layout. And before you press launch, send a test message through your contact form from a phone.

The video stops at launch, but your list should go on. Confirm Googlebot isn't blocked from your site and your page returns HTTP 200 with indexable content. Verify your site in Search Console and test one of your pages with the URL Inspection tool. Then submit your sitemap so Google learns about your new or updated pages.

Getting your page into search results costs you nothing. But meeting these requirements doesn't guarantee crawling, indexing or serving for your site, so plan to request a recrawl after you fix anything.

How do you check the result before you share it?

You check an AI-built site by reading what it ships to a browser, and the free assessment reads your site in about two minutes. You enter your URL and your work email. It samples your homepage plus up to eight of your pages, then scores your site on eight pillars: architecture 15%, performance 15%, security 12%, search 12%, schema 10%, AI readiness 10%, editorial experience 10% and operational health 16%.

You get one score out of 100, with the evidence behind each of your pillars. A score of 80 to 100 means good standing; 60 to 79, constrained; 40 to 59, at risk; 0 to 39, legacy condition. Your report link is sent once. You can run three checks per hour per connection.

The assessment does not log in to your site, read your analytics, pull your field performance data or interview anyone. So before you share your link, review your copy, your facts and your accessibility yourself.

Questions, answered.

Check your own site.

1. 01Website audit checklistThe eight pillars as a list you can run yourself.
2. 02Core Web Vitals testLCP, INP and CLS from what the page ships.
3. 03Website health checkThe general read, all eight pillars.

More from What Ships.

1. 01The best vibe coding tools in 2026, judged by what they ship.Tools · 2026-10-25
2. 02The best AI website builders, by what their sites score.Builders · 2026-10-25
3. 03Lovable vs Bolt vs v0: what each one ships.Head to head · 2026-10-25