Example build / Local service website
A customer journey supported by real business facts
A useful business site says what the company does, where it works, why the visitor should trust it, and what happens after the visitor asks for help.
Pages
Home, services, areas, about, contact, privacy.
Action
A working quote-request journey.
Search
Unique metadata, sitemap, and truthful schema.
Proof
Mobile, form, accessibility, and build checks.
Before you prompt
Bring facts the AI is not allowed to guess
Collect the real service area, services, contact details, policies, and proof before generating pages. Missing information should remain a placeholder, not become persuasive fiction.
Real business facts
Write down the exact name, services, locations, contact details, and operating constraints.
One customer action
Choose call, request a quote, or book. Do not make three actions compete on every screen.
Provable trust
Use only supplied licenses, years, reviews, people, photos, guarantees, and affiliations.
Form destination
Decide where personal data goes, who receives it, how errors work, and which privacy text applies.
If you only need one promotional page rather than a multi-page site, create an AI landing page instead.
Facts before copy
Turn verified business information into a page plan
Replace the bracketed fields with real information or label them as missing. The agent must separate facts from gaps and wait before it writes marketing copy.
Help me turn the real facts about my service business into a website plan. Do not write copy or edit files yet.
Business facts:
- Business name: [NAME]
- Service area: [REAL LOCATIONS]
- Main services: [SERVICES]
- Best customer: [CUSTOMER]
- Primary action: [CALL, REQUEST A QUOTE, OR BOOK]
- Contact details: [REAL DETAILS OR CLEAR PLACEHOLDERS]
- Evidence I can prove: [LICENSE, YEARS, REVIEWS, PHOTOS, OR NONE]
- Brand direction: [COLORS, TONE, AND VISUAL REFERENCES]
Plan the smallest useful multi-page site. Separate facts I supplied from information still missing. Do not invent reviews, awards, certifications, customer counts, locations, prices, guarantees, or before-and-after results.
Return the page map, goal of each page, primary navigation, required content and images, form fields, privacy considerations, and mobile test plan. Wait for my approval before editing.What a useful response contains
- A small page map tied to the customer journey
- A visible list of missing facts
- One consistent primary action
- Form, privacy, and mobile requirements
Build from approved facts
Generate the multi-page site without inventing trust
This prompt preserves the existing project and makes placeholders, forms, accessibility, metadata, and tests part of the build rather than cleanup tasks.
Build the approved business website in this Adios workspace.
Requirements:
- Inspect and preserve the current framework, package manager, health route, and adios.yaml.
- Build the approved pages with one clear primary action and consistent navigation.
- Use only the business facts I provided. Mark missing facts with visible development placeholders instead of inventing them.
- Make headings, links, buttons, forms, focus states, and error messages usable with a keyboard and screen reader.
- Make the layout work on small phones, tablets, and desktop screens.
- Add unique titles and descriptions, a canonical URL pattern, robots.txt, sitemap.xml, and truthful structured data only where the visible page supports it.
- Optimize local images and avoid adding a new third-party script without explaining why.
- If the site includes a lead form, validate it on the server and explain where submissions go. Do not silently collect personal data.
- Keep secrets and provider credentials out of source.
- Add or update tests for navigation, the primary form, and metadata routes.
- Run the existing lint, test, and build checks.
Show me the changed files, every placeholder I must replace, check results, and a page-by-page Preview checklist. Do not deploy.What a useful response contains
- Distinct pages with consistent navigation
- Visible placeholders instead of invented claims
- A defined and validated form destination
- Metadata, accessibility, and build evidence
Review like a customer
Check every claim, action, breakpoint, and failure state
Use this prompt after your own mobile and desktop review. It tells the agent to fix confirmed issues without adding fresh marketing claims.
Review this business website from the perspective of a first-time customer. Fix only confirmed issues and do not invent new claims.
Check:
- the first screen says what the business does, where it works, and what to do next;
- every service and location statement matches the facts I supplied;
- navigation, forms, phone links, email links, and calls to action work;
- form success, validation, privacy, spam, and failure behavior are clear;
- no fake review, logo, award, certification, statistic, or stock-photo caption appears;
- titles, descriptions, canonicals, robots.txt, sitemap.xml, and visible structured data agree;
- images have useful alternative text when needed and decorative images are treated as decorative;
- the pages are readable and usable at mobile and desktop widths; and
- the existing lint, tests, and production build pass.
Return the issues found, changes made, unresolved content I must provide, and the exact Preview journeys I should test.What a useful response contains
- Claims matched to supplied facts
- Working forms and contact actions
- Consistent search metadata
- Mobile and accessibility test paths
Replace every placeholder
Prepare the site, form, metadata, and domain together
A placeholder address or test form can damage trust quickly. This final prompt inventories them and stops before the production change.
Prepare this website for a human-approved Adios release. Do not deploy yet.
Verify the production hostname placeholders, canonical URLs, robots.txt, sitemap.xml, analytics consent requirements, form destination, privacy link, contact details, health route, build command, and adios.yaml.
List every item that still contains a placeholder. Then give me a final mobile, desktop, form, metadata, accessibility, and custom-domain checklist. Stop for my approval before production deployment.What a useful response contains
- A complete placeholder inventory
- Hostname, canonical, robots, and sitemap agreement
- A verified form and privacy path
- An explicit pause before publishing
Test the result
A passing build is the start of the review
Open Preview and perform the important journeys yourself. Ask the agent for evidence, but do not confuse its summary with your approval.
Customer path
- The first screen names the service, real area, and primary action.
- Every navigation item, phone link, email link, form, and CTA has a useful result.
- Success, validation, spam, and provider-failure states explain what happens next.
Trust and search
- Every business claim is supplied, provable, or visibly marked as a placeholder.
- Titles, descriptions, canonicals, robots, sitemap, and visible schema agree.
- No fake review, customer logo, award, certification, location, or result appears.
Experience
- Pages work with a keyboard and remain readable at phone, tablet, and desktop widths.
- Images have dimensions, sensible alternative text, and no avoidable layout shift.
- Lint, tests, build, health, and form checks pass.
Human approval gate
Connect the domain only after the facts and forms are final
Use Preview to check every page at phone and desktop widths, replace all development placeholders, and confirm the real form destination before approving the release and attaching the production hostname.
host and deploy the finished AI-built website- 01Replace or remove every development placeholder and unverified claim.
- 02Submit valid and invalid forms and confirm their real destination.
- 03Verify titles, canonicals, robots, sitemap, visible schema, and privacy links.
- 04Run mobile, keyboard, accessibility, lint, test, build, and health checks.
- 05Approve the release, attach the verified domain, and repeat the primary customer path.
Questions before you start
What this guide does—and does not—promise
Can AI build a complete business website?
AI can generate the source, pages, forms, metadata, and responsive interface, but the business must supply accurate facts, proof, policies, contact details, and final approval. The guide keeps missing information visible rather than asking the AI to guess.
How is this different from the Adios landing-page creator?
The landing-page creator is the faster path for one promotional page. This guide covers a source-backed multi-page website with navigation, service and location content, a form workflow, metadata, tests, and a reviewed deployment.
Will an AI-generated website rank in Google?
No tool can promise rankings. A useful site still needs accurate and distinctive content, crawlable pages, sound metadata, good performance, relevant links, real authority, and time for search engines and users to evaluate it.
Can I edit the website after it is live?
Yes. The source remains in the workspace and can be kept in Git. Make the next change, review it in Preview, rerun checks, and approve a new version while the current release remains live.