Building a business website with AI: supporting every step
Support the creation of a website with AI, from the first conversation to the handover, and check the result before launch.
Start with what visitors need to be able to do
An individual wants to show their photographs and be contacted about an exhibition. A renovation company wants to present its services and receive enquiries within its service area. Both ask for a website. Yet their visitors are looking for different information, and the decisions will differ.
A presentation website introduces a person, a business or an organisation. It can provide contact details and link to a booking service. If the project includes payments, a customer area or confidential documents, those uses must be clarified and the technical scope reviewed. Requirements and checks increase as features are added.
AI can help organise pages, rephrase text and produce an initial interface. France Num lists website creation among the uses accessible to small businesses. Wix's guide to building with a language model also emphasises project preparation and adjustments after generation. It presents a commercial vendor's workflow; its claims are not an independent evaluation.
Here I propose a support process that applies to personal projects and small businesses alike. The situations described are fictional. The aim is to make decisions understandable for the person commissioning the site, right up to the point when they need to change it themselves or request help.
Share decisions between the owner, the adviser and AI
The owner knows their activity and decides what they want to make public. The adviser turns requirements into pages, explains trade-offs and checks the result. AI provides proposals within that framework. A well-written response may still contain a nonexistent service, a misleading photograph or a form with no recipient.
For an individual, I would start with their level of confidence: do they want to learn by building the site with someone, delegate the work, or simply have someone review an initial version they created alone? For a business, someone must also be appointed to make decisions. Conflicting feedback from management and the sales team can multiply versions without moving the project forward.
- The owner approves the facts: contact details, services, displayed prices, references and publication permissions.
- The adviser explains decisions that affect what comes next: tools, subscriptions, possible changes and maintenance arrangements.
- AI receives a bounded request. Its proposals are reviewed before integration and checked against the available information.
- At each step, the chosen decision is recorded in a shared document. An AI conversation alone is not enough to recover what was accepted.
I would arrange short approval steps around visible deliverables: a brief, a page outline, a representative page, then the complete site. Each approval resolves a specific question. The client can flag an incorrectly described service before it is repeated on every page.
Write a brief the client can correct
The first conversation should reveal a concrete situation. Where does the visitor come from? What do they already know? What hesitation stops them contacting the person or business? A portfolio sent after a meeting serves a different purpose from a site found while searching for a local tradesperson.
- Main goal: receive a quote request, present work or help people find reliable information.
- Target audience: the people concerned, their questions and the information that will help them choose.
- Available content: existing text, photographs, visual identity, authorised references and information still missing.
- Scope: expected pages, language, contact method and features explicitly deferred.
- Constraints: creation budget, acceptable recurring costs, deadline and the time the owner can devote to the project.
- Website upkeep: who edits the text, how often, and who steps in if a feature stops working.
For the amateur photographer in our example, a first version could bring together selected photo series, an introduction and a dedicated contact address. For the renovation company, it could explain the services, show authorised project photographs, specify the service area and offer a quote request. These scopes are starting points for discussion; they describe neither a real quote nor a required page count.
AI can turn anonymised notes into clarification questions. I would ask it to identify missing information and distinguish it from supplied facts. The owner corrects this summary before moving to the mockup. A gap remains marked as such rather than being filled with a plausible invention.
Choose the tool around future changes
The question that often separates solutions is simple: how will we change opening hours or a photograph in six months? A generation demo provides little information about that task. I would suggest performing the change during the trial, with the person who will later be responsible for it.
- A visual builder may suit an owner who wants to edit pages through an interface. Check the proposed plan for custom domains, useful features, editor limitations and export options.
- A CMS, or content management system, may suit regular publishing or multiple contributors. Plan for its hosting, updates and maintenance of the chosen extensions.
- A custom-built site can meet specific presentation needs or integrate into an existing environment. A few rarely edited pages may only need static pages. Define how changes will be published and who can handle them.
Services such as Wix combine generation and visual editing. That does not establish that a particular plan meets every requirement. Prices, export options and integrations change, so they must be checked when choosing. For a solution that produces code, ask for a demonstration of retrieving the project and rebuilding it outside the original conversation.
The quote should separate creation from recurring expenses: domain name, hosting or subscription, email if needed, form services and technical support. Add generation costs if they are billed by usage. A site built with AI does not necessarily need AI running after delivery.
I would also specify the content expected from the client, approval stages and how additional requests will be priced. The schedule depends in part on the availability of photographs and feedback. A mockup appearing quickly does not justify promising the same turnaround for a site ready to operate.
Gather evidence before generating text and images
Generic copy readily talks about quality and local service. To present a business, you need to know what it actually offers, whom it serves and how first contact works. I would ask the owner to answer, in their own words, questions their visitors or customers already ask.
AI can then shorten an introduction, suggest headings or make an explanation more accessible. Every claim remains tied to approved information. Years of experience, certifications, testimonials and client names must never appear merely because they make the page more persuasive. An unauthorised reference can be replaced with an anonymised description, after checking what it still allows someone to identify.
For a portfolio, images are often the main content: choose those their creator wants to publish and check the necessary rights. For the fictional renovation company, a generated image must not be presented as completed work. An atmospheric illustration can be labelled as such, but it does not replace evidence of actual work.
I would prepare a shared folder containing approved text, original files and their usage conditions. Documents sent to an AI tool must be limited to what is useful and authorised. A customer list, a named quote or access credentials do not belong in a mockup request. Check the service's data handling terms before sending anything.
Approve the visitor journey before building out the pages
The site plan connects visitors' questions to information that answers them. The home page introduces the activity and provides direction. A service page can then describe the cases covered, limitations and how an enquiry proceeds. References provide verifiable evidence; the contact page explains how to continue.
A single page may be enough for a simple personal project. Separate pages become useful when services or audiences need different explanations. I would limit the first version to content the owner can review and maintain, instead of immediately generating a blog and dozens of local pages.
The first mockup should contain real copy, even if it is still short. An attractive composition filled with placeholder sentences hides space and comprehension problems. I would start with a representative page on a phone, then check its adaptation to a wide screen.
During review, ask someone discovering the project to explain what they understand and find how to make contact. Observing where they hesitate gives more actionable feedback than asking whether they find the site attractive. Their comments help correct the wording, information order and visibility of actions.
Give AI a precise request and explicit boundaries
Here is a fictional request for preparing a first page. Information in brackets must be supplied or left pending. This instruction is intended to produce a proposal for review; it does not guarantee the quality of the result.
Prépare une proposition de page d’accueil pour un site vitrine.
Projet fictif : entreprise de rénovation intérieure.
Public : propriétaires cherchant un prestataire dans [zone validée].
Objectif : comprendre les prestations puis demander un devis.
Prestations confirmées : [liste fournie par le propriétaire].
Preuves autorisées : [photos et références validées].
Contact : [canal décidé avec le propriétaire].
Commence par relever les informations manquantes.
Propose ensuite l’ordre des sections et un premier texte court.
Indique ce que chaque section aide le visiteur à décider.
Prévois une lecture sur téléphone et des intitulés explicites.
N’invente aucun avis, prix, délai, label ou chiffre d’expérience.
Signale les éléments à compléter, sans les présenter comme acquis.
N’ajoute ni paiement, ni espace client, ni chatbot.
Attends la validation du plan avant de produire les autres pages.For an individual, replace the business activity with the personal project and services with the work to be presented. The goal may be to browse a selection and then write to its creator. Also specify which information the person agrees to make public.
Subsequent requests benefit from remaining focused: shorten the introduction, clarify labels or improve a gallery on mobile. Keeping a known version before a major change allows comparison. If a correction also changes the menu and colours without being asked, the adviser can spot the expanded scope and return to what was intended.
Check the functions behind the mockup
Once the journey is approved, implementation can continue in the chosen tool. If code is generated, I would plan for changes reviewed in a repository and appropriate checks before integration. With a visual builder, use its previews and available restore options. In both cases, check the version that will actually be published.
The form deserves particular attention. Displaying a success message does not prove the enquiry reaches its recipient. Follow a fictional submission through to receipt, then check what the visitor sees when the service rejects it. A service key must remain protected on the server; hiding it visually in the page does not make it confidential.
A public form also needs server-side field validation and appropriate protection against abusive submissions. Starting with a dedicated contact address is an option if it meets the need. That simplifies some operations while leaving the owner responsible for managing messages and spam.
For a redesign, inventory the old URLs before switching over. Useful pages must be preserved or redirected to their equivalents. Changing the domain or hosting must also preserve necessary email settings. A website change should not make existing enquiries disappear.
Work on visibility and accessibility with real content
To be found, the site must first describe clearly what it presents. Page titles, URLs and internal links should help people understand the activity. For a local business, contact information and the stated service area must reflect reality. Avoid generating pages for towns where it does not operate.
Google Search Central says AI can help research and structure content. Generating many pages without added value, however, may fall under its policy against scaled content abuse intended to manipulate results. I would prioritise precise answers to visitors' questions and examples the owner can document. No writing or technical configuration guarantees a search ranking.
Accessibility starts during design: a heading hierarchy, adequate contrast, understandable form labels and relevant image alternatives. An informative photograph needs a description suited to its role. A purely decorative image can have empty alternative text. Text should not be trapped inside an image for the sake of an attractive composition.
W3C's Easy Checks provide initial checks, including keyboard and form checks. They are not a complete compliance audit. I would also test the site with enlarged text and on a real phone. An oversized image or intrusive animation can obstruct browsing even when the mockup looks good on its creator's screen.
Adapt legal information and data handling to the project
A personal site and a professional site each require examination of their actual situation. Service Public Entreprendre notes that professional websites must display accessible legal notices. Their contents depend in part on the publisher's legal status. Registration information, hosting details and contact information must come from verified documents. Generated text must not turn missing data into public information.
For the individual in our example, decide which contact details will be public, then check the obligations applicable to their case. The word 'personal' alone does not settle every question: publishing, image use and collecting messages need examination. For the company, rules specific to its activity or any sales supplement this work.
When a form collects personal data, the CNIL provides examples of information to give people. In particular, cover the purpose of collection, recipients, retention and exercising rights, using information appropriate to the actual processing. Request only useful fields. A contact enquiry and subscribing to marketing have different purposes; silently combining them creates an ambiguity that needs correcting.
Adding audience measurement, an embedded video or a map can introduce trackers. According to the CNIL, trackers requiring consent must wait for that consent; some exemptions exist under conditions. A banner displayed by default does not prove the services are actually blocked. Examine what the site loads and configure visitors' choices for the tools selected.
Run acceptance checks with the owner before launch
Acceptance testing means checking together that the site meets the brief. I would prepare a short list of journeys to perform on the version ready to publish. Automated checks can detect technical defects; the owner's review remains necessary to confirm the content and expected behaviour.
- From a phone, identify the activity and find the service or work sought without guessing what labels mean.
- Open every page and check links, images and contact details. Review the facts and remove all placeholder content.
- Submit a fictional enquiry and confirm receipt. Also try an invalid field and a sending failure, without transmitting real customer data.
- Navigate the menu and contact options with the keyboard, checking visible focus, enlarged text and the main contrasts.
- Check the domain, HTTPS and page titles. Verify that the test environment remains excluded from indexing and that the public site is not excluded by mistake.
- Check applicable legal information and the behaviour of third-party services, including before any consent choice.
- Have the future person responsible perform a common edit, then check the backup or restore procedure appropriate to the tool.
Every blocking issue needs a correction or an explicit decision to defer it with its consequences. I would distinguish visual refinements from a defect that prevents contacting the company. Final approval must concern an identified version. After the authorised launch, repeat essential checks on the real domain, since configuration may differ from the preview.
Hand over access and organise ongoing care
The owner must control the accounts that ensure continuity: domain, hosting or platform, email and any contact services. I would arrange accounts in their name or the company's name, with suitable invitations for the specialist, stronger authentication where available and recovery methods retained by the owner.
Delivery includes the content and recoverable files, recurring costs and renewal dates, and instructions for common changes. For custom code, add the repository, instructions needed to rebuild it and service configuration without exposing secrets. For a platform, document export limitations and what leaving would require rebuilding.
A short introduction can focus on a real task: replacing an image and publishing a correction. The owner should know where to ask for help and what support after delivery covers. Updates, contact checks and incident fixes need an owner even if content rarely changes.
After an agreed period, review the enquiries received and difficulties observed. A qualified enquiry or recurring question offers a more concrete improvement opportunity than an isolated visitor count. If traffic is low, supplement it with a few conversations with visitors instead of drawing conclusions from fragile percentages.
To prepare for a first conversation, gather an introduction to your project, the content you have and an example of a change you would like to make yourself. Add your budget and deadline, even approximate ones. These details will help define the scope and working approach before the first generation.
Sources and useful links
- France Num: AI uses for very small and small businesses, including website creation (updated 16 September 2026)
- Wix: preparing and building a website with a language model, vendor guide (accessed 21 October 2026)
- Google Search Central: guidance on AI-generated content (accessed 21 October 2026)
- W3C WAI: initial accessibility checks and their limitations (accessed 21 October 2026)
- Service Public Entreprendre: required information on a business website (verified 13 October 2026)
- CNIL: examples of information for a data collection form (accessed 21 October 2026)
- CNIL: cookies and trackers, configuring a site in accordance with the rules (accessed 21 October 2026)
- Choose a tool by first examining the need
- SEO, AEO and GEO: understanding visibility in search engines and AI answers
- Argos: audit a page and prioritise corrections
- Describe your project and the support you need