To build a website with AI, describe the site you want in plain language, attach your logo, photos or price list, and let an AI builder generate and host it. Review the live result, then ask for changes in the same chat until it is right. Finally, connect your own domain and launch.
- Prepare before you type: the site's one main goal, its pages, and your real text, photos and prices.
- One detailed first message beats a string of short ones, especially on a free plan with one build per 5-hour window.
- Attach what you already have, like a logo, menu PDF or price list, so the site uses your content instead of placeholders.
- Forms, bookings, logins and payments are added by asking. Payments and email go live only after you add your own keys under Integrations.
- Test on a phone, check every price and claim, and move to your own domain before the address goes on anything printed.
Before you start: goal, pages, real content and photos
The quality of an AI-built site depends far more on what you bring than on the tool. A little preparation saves several rounds of corrections. Gather these first:
- One main goal. What should a visitor do: call, book, order, send an enquiry, join a list? A site that tries to push five actions equally ends up pushing none.
- The pages. A typical local business site has Home, Services or Menu, About, Contact, and maybe Book or Order. A one-page site with sections is fine for a freelancer or an event.
- Real content. Business name, address, phone, opening hours, services with prices, and a few short customer quotes you have permission to use. Paste them in or attach them as files.
- Photos. Your own photos of the shop, the team and the work beat any stock image. Without them, WisyLink uses stock photos or simple vector illustrations; it doesn't generate photos.
- Language. Decide which languages the site needs. A site in two languages gets proper language versions with their own URLs, which is easier to ask for at the start than to add later.
Here is the whole process at a glance:
- Describe the site in one clear message.
- Attach your logo, photos, menu or price list.
- Watch the build and open the live link.
- Refine with follow-up messages.
- Add forms, bookings, logins or payments when you need them.
- Move it to your own domain and launch.
Can you do this for free? Yes. WisyLink's Community plan costs nothing and needs no card, and it builds and hosts a complete site. It has two limits to plan around: one build per 5-hour window, and links that last 30 days, then stay marked for deletion for one more week before they are removed unless you upgrade. Links that don't expire need a paid plan, starting at $7 a month; a custom domain works on any plan. You can start on Community and upgrade only when the site is ready to share.
Step 1: Describe the site in one clear message
Write the way you would brief a designer you trust: what the business is, who it is for, which pages and features it needs, and how it should feel. The table shows what each part does.
| Element | Why it matters | Example |
|---|---|---|
| Goal | Decides what the home page pushes and where the main button goes | "Get people to pre-order celebration cakes" |
| Audience | Sets tone, wording and what to put first | "Local families and office managers ordering for events" |
| Pages | Prevents missing or invented sections | "Home, Menu, Cakes, About, Contact" |
| Features | Anything interactive needs logic and storage built in | "A pre-order form with pickup date" |
| Data | Says what must be saved and who sees it | "Save each order; only I can see them in an admin page" |
| Look and feel | Avoids a generic default design | "Warm and handmade: cream background, dark green accents" |
| Language | The page stays in the language you choose | "English only" or "English and Spanish" |
Put together, a first message for a local bakery might read:
Build a website for Little Oak Bakery, a neighborhood bakery and cafe at 14 Station Road. Main goal: get people to visit and to pre-order celebration cakes.
Pages: Home (hero photo, today's specials, opening hours), Menu (breads, pastries and cakes with prices from the attached price list), Cakes (pre-order form: name, email, phone, cake type, size, pickup date, message on the cake), About (our story, the attached team photos) and Contact (phone, address with a map link, hours).
Save every pre-order and give me a simple admin page to see and mark them as done. Warm, handmade look: cream background, dark green accents, the attached logo. English only.
Wisy, WisyLink's chat assistant, reads this and either asks one short question about something that changes the result ("Should cake orders take a deposit online?") or starts building. It fills in the small decisions itself, such as button labels and section order. Answering its question in one line is enough.
Step 2: Attach your logo, photos, menu or price list
Attachments are the fastest way to get your real content onto the site. WisyLink accepts 17 file types, up to 25 MB each, including JPEG, PNG, WebP, HEIC and SVG images, PDF, Word and Excel documents, CSV and plain text. What works best:
- Logo: SVG, or a PNG with a transparent background.
- Photos: straight from your phone is fine, HEIC included. Pick a few strong ones rather than forty similar ones.
- Menu or services: the PDF or Word file you already hand out.
- Prices or product lists: a CSV or Excel sheet with clear column names, such as item, category, price.
Say in the message what each file is for: "use team.jpg on the About page", "take prices from prices.xlsx". Files you attach stay in the link's Reference Files, so later builds can use them too. Only upload photos and text you have the right to use.
Replacing an existing site? Copy each page's text into a Word or text file and attach it, and list the old page addresses, such as /menu or /prices, so the new site can keep them. Keeping the same addresses protects whatever search rankings those pages already have.
Step 3: Watch the build and open the live link
Once the build starts, a live task list in the chat shows what the build agent is doing, and a Stop button ends the build if you spot a misunderstanding early. In the iOS or Android app you get a notification when it finishes. Until the first build is done, the site's address shows a "building" page.
The finished site is live at its own HTTPS address, https://<id>.wisylink.com, and you can preview it in the chat or open it in a new tab. Read the build's closing note: it lists what was built and anything you need to do, such as admin sign-in details or keys to add. Then run a first pass:
- Open the site on your phone first; that is how many customers will meet it.
- Check the name, address, phone number, hours and every price against your own records.
- Tap the phone number and the map link.
- Submit the form with real-looking details, then check that the entry appears in the admin page.
- Write down everything you want changed before sending anything.
Step 4: Refine with follow-up messages
All changes happen in the same chat; there is no drag-and-drop editor and no code to touch. Good follow-ups name the page, the element and the change:
- "On the Menu page, group items under Breads, Pastries and Cakes, with prices aligned to the right."
- "Replace the home page photo with the attached shopfront.jpg."
- "Put the phone number in the header on mobile and make it tap-to-call."
- "The pickup date must be at least two days from today. Block earlier dates."
Batch your changes. Each change is a new build, and on the free plan you get one build per 5-hour window, so a list of eight fixes in one message moves much faster than eight separate messages. Paid plans have larger allowances and shorter waits between builds. If a build fails, the previous version stays live, so experimenting doesn't put the site at risk.
One request saves a lot of builds later: ask for an admin page where you can edit things that change often, like today's specials, opening hours or prices. Edits made there appear on the site within about a minute and don't need a build at all.
Step 5: Add forms, bookings, logins or payments
Interactive features are one message away, because the site has a real backend: saved data, accounts and file storage are added when the project needs them. The common ones:
- Contact and enquiry forms
- Entries are saved and listed in an admin page. Email notifications go out through your own email account (SMTP); until you connect one, the form still saves entries and simply sends no email.
- Bookings
- Time slots or classes with a capacity. Bookings are saved atomically, so two visitors can't take the same last slot.
- Logins
- A members' area or a client portal, with the site's own sign-up, login, roles and admin area. Google or GitHub sign-in can be added with your own OAuth credentials.
- Payments
- Deposits, orders or subscriptions through your own Stripe account or another provider. An order is marked paid only when the provider confirms it.
- A password on the whole site
- Useful for showing a draft to a partner before launch. One shared password protects every page.
Anything that relies on an outside account stays switched off until you add its credentials under Integrations. The build's closing note tells you which ones are needed, and the Integrations screen shows the steps for each provider. Never paste keys into the chat. For payments, start with your provider's test keys, place a test order, and switch to live keys once it works end to end.
You don't need everything on day one. Add features in the order customers will use them: the bakery can launch with the menu and the pre-order form, then add online deposits once orders are coming in. Each addition is one more message in the same chat.
Step 6: Move it to your own domain and launch
You can connect a custom domain on any plan, the free one included. If you don't have a domain yet, register one with any domain registrar first. In Domains you then have two options:
- Connect a domain you own with a DNS record. Your DNS stays where it is; you add the record shown (a CNAME to
cname.wisylink.comor an A record). Your email is not affected. - Point your nameservers to WisyLink for full DNS management. This replaces every existing DNS record, including email (MX), so only choose it if you are ready to recreate those records in WisyLink's DNS manager.
Two pitfalls come up again and again. Many DNS providers don't allow a CNAME on the bare domain (example.com), so use the A record option there. And an old A or AAAA record left on the same name will stop verification from passing, so delete it. Verification starts when you ask for it, retries automatically, and gives up after 6 hours if the records still aren't right; fix them and start again. The HTTPS certificate is issued automatically.
Once the domain is verified, choose it in the link's Domains and deploy; it takes over within seconds. Each link serves one domain at a time. Then tell search engines: add the domain as a property in Google Search Console, which verifies domain ownership with a DNS record, and submit the sitemap at /sitemap.xml, which every WisyLink site serves on its own.
What AI does well, and what you still need to check
An AI builder is strong at the parts that used to need a designer and a developer: a consistent layout that works on phones, clear page structure, working forms and saved data, and the technical SEO basics. Every WisyLink page is rendered on the server with a title, description, canonical URL and social share image, and the site serves its own sitemap and robots.txt.
Is a website made with AI good for SEO? Technically, yes. Search engines see the full content of each page on first load. Ranking is a different question. Google states that appropriate use of AI or automation is not against its guidelines and that it rewards original, helpful content, however it is produced. The AI builds the container; your real prices, photos, expertise and local details are what make the page worth ranking.
What you still need to check yourself:
- Facts. Every price, opening hour, address and claim. AI can fill gaps with plausible text, and WisyLink's own terms make reviewing the output your responsibility.
- Wording. Read every page aloud. Cut anything you wouldn't say to a customer at the counter.
- Forms and flows. Submit each form, make a test booking, place a test payment, and confirm what lands in the admin page.
- Legal pages. If you collect names, emails or payments, you need a privacy notice that matches what you actually collect. Ask for the page, then have the wording checked against your local rules.
- Images and text descriptions. Check that photos show what the text says and that each important image has a meaningful description for screen readers.
Treat this review as part of building, not an afterthought. Our essay on evaluating what is generated explains why measured checks beat a quick glance.
Launch your site with WisyLink
If you are new to the idea, what an AI app builder is and how it works covers the basics, and the generative web explains why a sentence can now become a hosted site. For ideas beyond a business site, browse the use cases: booking systems, client portals, stores, event RSVPs and more.
When you are ready, write your first message using the table above, attach your files and send it. Test the live link on your phone, batch your fixes, and compare plans when you want the site to stay live on your own domain.
Describe it in one message and get a live link: start free on Community, no card required.
F.A.Q.