What an AI-built website looks like, page by page

The home page says who you are, where you work, and what to do next

Take a plumber in a mid-sized city. The home page leads with one main heading that names the trade and the place. Under it sits the answer capsule: what the business does, who it serves, and how to reach it.

Then come short sections that point to the service pages and the area pages, written from what the plumber told the in-app assistant. The lead form is on this page, as it is on every page, and the structured data says who the business is and what it offers.

No claim the plumber did not make, and no number the plumber did not say.

One page per service, each answering its own question

Drain cleaning, water heaters, leak repair: each service the plumber named gets its own page. Each has its own title and description, one main heading, an answer capsule, sections, and the questions people ask about that job.

Every service page links back to the home page and across to related services, with breadcrumbs that show where it sits. It has a clean address of its own and a line in the sitemap.

The copy is written from a conversation about that service, so the water heater page reads like a water heater page and not like the drain page with a word swapped.

One page per area, and why they cannot be copies

The plumber serves a few towns around the city. Each gets an area page. The temptation, on any builder, is to make one page and swap the town name. That does not work here.

The uniqueness check strips city, state and industry names before it measures. An area page has to say something true and specific about serving that place, from what the plumber said, or it scores as a copy and does not publish.

See SEO location pages for how to do area pages honestly.

About, Contact and a questions page, added in one click

The About page is written from what the assistant already knows: who runs the business, what it does, what makes it different. The Contact page carries the lead form, the phone number and, if the plumber ticked the box, a Text us link beside it.

If the plumber pasted a booking link from Calendly, Cal.com, Acuity, Square Appointments, YouCanBookMe, Microsoft Bookings, Google Calendar or HubSpot Meetings, the site has a book-a-time section. It loads only when a visitor opens it.

The questions page collects the questions people ask, with plain answers, written from the same conversation.

The not-found page is branded and tells the truth

Type a wrong address and you land on a not-found page that looks like the plumber's site, not a blank server error. It is served with a real not-found status, a 404, so search engines know the page is not there.

See 404 page SEO for why the status matters.

What every page on the site shares

Every page passed a check validated against Google Search Essentials and modern web standards before it went live. Search engines read the parts below. So do the AI answer engines like ChatGPT and Google's AI answers. That is a description of what is on the page, not a promise about where it shows up.

• A clean address, a title and a description of its own.
• One main heading and an answer capsule near the top.
• Breadcrumbs and links to related pages.
• Structured data that says who the business is and what it offers.
• The lead form, delivered to wherever the plumber works.
• A line in the sitemap.
• A check that runs before anything publishes.

What you would not see

No cookie and no analytics script, unless the plumber added a Google Analytics 4 tag. Page views and conversions are counted on the server.

No made-up review, no invented statistic, no years-in-business figure the plumber did not give. Legal pages appear exactly as uploaded, and the builder does not write legal, medical or financial advice.

No online store checkout, no blog posts, no second language. Those are not offered today, and a page that pretends otherwise would be worse than one that says so.