Making a Website Using AI With Good SEO: A Step-by-Step Build

Make a small-business website with AI by mapping one useful page to each customer need, drafting from verified business facts, editing the copy yourself, and then checking titles, internal links, crawl access, mobile speed and Search Console. AI can speed the build, but no builder or prompt can guarantee rankings; usefulness and technical access need testing.

Start with what customers ask before they buy, not a request for “an SEO website” from a builder. A search engine must be able to discover a page, understand its topic and find content that answers the visitor's question. Google says AI-assisted content still needs accuracy, quality and relevance, and warns against mass-producing pages with little original value.

Stage 1: write down the buyer questions and page jobs

Take 10 recent enquiries, sales calls or customer-service threads and group the questions. For a furniture maker, illustrative groups might be made-to-measure sizing, material choices, delivery, care and how to request a quote. These are useful because they reflect actual decisions, not a keyword list invented by AI. Ask staff which answers they give repeatedly and where prospects hesitate. Then select a small set of pages: home, one page for each distinct service or product family, an about or process page, and a contact or quote page. Add a guide only where you can offer detail beyond the commercial page.

Make a one-line job for every page. “Made-to-measure desks: explain dimensions, materials, lead-time range as confirmed by the business, how the quote works and examples of completed options” is better than “rank for desk keywords”. If the business has no confirmed lead time, the page should say how customers receive a timetable, not invent a number. Do the same for the contact page: what information a buyer should supply, what happens after sending, and which contact methods genuinely work. The keyword research tutorial can help refine the terms after these real customer questions are clear.

Illustrative page map for a seven-page site: home; made-to-measure desks; shelving; materials and finishes; the design process; care advice; and request a quote. The desks page has a buying intent. The care page answers an after-purchase question and can link back to materials without pretending to be another sales page. Avoid making ten variations of “custom desk” whose only difference is wording. Google advises creating helpful content for people, and its starter guide emphasises clear, discoverable links.

Write a small acceptance test for each page before drafting. For the desks page: a visitor should learn which measurements to take, see a real example of a finished design, understand what can be varied, and find a quote request that asks only for useful information. For the care page: a visitor should find instructions based on the actual finish used, with uncertain cases directed to the workshop. These tests help the owner reject an AI draft that sounds polished but omits the answer. They also stop every page from drifting into the same sales pitch. Keep the test beside the source facts so an editor can review the page after future changes.

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

Stage 2: choose a builder you can inspect and maintain

An AI website builder can produce a draft layout and copy; a general assistant can produce a content brief for a builder or developer. Choose based on what you can control after launch: page URLs, title elements, meta descriptions, headings, image descriptions, navigation, canonical URLs where needed, redirects, mobile layout, structured data if relevant, and access to analytics and Search Console. Ask the vendor to demonstrate these controls on a trial page. Do not buy on the strength of an attractive desktop preview alone.

Before committing, publish a test page that can be opened on a phone without logging in. Turn off scripts temporarily or use a basic browser to see whether navigation and core text remain available. Check whether the builder hides important text inside images, whether menus work by keyboard, and whether the contact form clearly reports success or failure. For a site that depends on enquiries, a beautiful page with a broken form has failed the business goal even if its SEO controls look complete.

An illustrative comparison illustrates the decision. Builder A offers quick layouts but its trial cannot set a page-specific title or export content; Builder B takes two extra hours to style but allows unique titles, clean URLs and a tested form. The small furniture maker chooses B because the owner can maintain the seven pages. These are imaginary builders, not product claims. If you need to compare a designer's fee with a builder subscription, use the builder-versus-designer cost tutorial.

Stage 3: give AI a fact pack, not a blank page

Create a short source file for each page: confirmed products or services, process steps, price approach, photographs you own, customer questions, exact contact path, any restrictions, and things you will not claim. Replace customer names with generic descriptors unless you have permission to publish them. AI should be told to mark missing facts rather than fill them. The person who knows the business must review the copy for specificity, truth and voice. A generic sentence such as “we provide outstanding craftsmanship and exceptional service” tells a visitor almost nothing about materials, dimensions or how to buy. Paste the fact pack into ChatGPT, Claude or Gemini, or into the builder's own AI writer, with a prompt along these lines.

Draft a service page for [service] using only this fact pack: [facts].
Audience: a buyer comparing options for [real question].
Give: a plain opening answer, process, options, evidence, limitations,
three practical buyer questions and a clear enquiry step.
Flag any fact you need but do not have as [CHECK].
Do not invent testimonials, prices, certifications or delivery dates.
Avoid repeating the wording of our other page: [page purpose].

Illustrative draft output: “Our made-to-measure desks can be built in oak or ash, with a choice of cable openings. Send your wall width and preferred finish for a quote.” If the fact pack confirms oak but says nothing about ash, the editor removes ash. If cable openings are possible only for certain designs, add that condition. The human edit might become: “We make desks to fit your measured space. Send the wall width, intended use and a photograph of the room; we will discuss suitable materials and quote for the agreed design.” The point is a verifiable next step, not more adjectives.

For another concrete example, an online clothing store should not let AI turn “machine washable” into “wash at 60 degrees” unless the care label supports it. A specialist food importer should not let an assistant invent origin or ingredient claims. A builder can publish copy instantly, so establish a two-person approval for factual pages if possible. Keep the fact pack and approved copy version; when a product changes, you can find the affected pages.

Before approving a draft, mark each claim as observed, documented, explained by staff or unverified. “We make the legs in-house” needs a process source; “many buyers choose oak” needs actual sales knowledge; “delivery is free” needs a current policy. Delete unverified claims or replace them with a precise question the business can answer. Then read the copy aloud and remove sentences that could sit on any competitor's site. An illustrative change is to replace “beautiful bespoke furniture for every home” with “Send the width of your alcove and a photograph; we will discuss a shelf layout that fits the opening.” The second sentence tells the buyer what to do and can be checked against the real process.

Stage 4: give each page one clear search identity

Write a distinct title element that identifies the page's subject and business, then a useful main heading in the visible content. The meta description should explain what the visitor will find; Google says it may occasionally supply the snippet, so write it for the reader, short and unique to the page, rather than stuffing it with phrases. Use short readable URLs based on the page job. Keep navigation labels natural: “Desks”, “Materials”, “How ordering works” and “Request a quote” are more useful than a menu of search phrases. Link from the home page to important service pages and from related pages where the link helps the reader.

Illustrative title and heading pair: title element “Made-to-measure desks | Furniture workshop”; visible H1 “Desks made for your space”. The opening should answer the buyer's question about how to order, not repeat the title. A description might read: “See desk options, the measurements we need and how a made-to-measure quote is prepared.” Avoid publishing four pages with the same title and only swapping a material word. The website copy tutorial goes deeper on the individual home, about and service pages.

Check images separately. Rename source files so your team can find them, add concise alternative text when an image carries information, and describe a product accurately rather than inserting keywords. A photo of a built-in desk can show how a corner was used; the alt text should say that in ordinary language. Compress large images and check they remain sharp enough to help a buyer. If the AI builder produces decorative images of products that are not real, replace them with your own evidence or clearly label them as illustrations. A visual promise that cannot be supplied hurts trust.

Do an internal-link walk as a visitor. From the home page, can someone reach desks in one click? From desks, can they find the materials explanation and then request a quote? Is the care guide reachable from a product page where it answers a likely question? Use descriptive link text such as “compare available finishes” instead of a row of “learn more” buttons. An illustrative failed test is a published shelving page present in the sitemap but absent from navigation and every related page. It may be technically accessible, yet a buyer has no clear route to it. Add a relevant link from the materials page and retest the path on a phone.

Stage 5: add structured data only for visible facts

Structured data is machine-readable markup that can help search systems understand content. It is optional for a useful site and does not guarantee a rich result. Follow Google's type-specific rules, use only facts visible on the page and validate the markup. For a small business, basic organisation or product information may be appropriate when the page truly supplies the required fields. Do not mark up invented reviews, invisible FAQs or prices that the business does not show. If the builder auto-generates schema, inspect the rendered output instead of assuming it matches the visible page.

A realistic failure is a furniture maker's product page that says “quote on request”, while the builder emits a fixed offer price copied from a placeholder. Search systems and customers would see inconsistent facts. Delete or correct the markup and test the page again. Another failure is a page whose structured data refers to an old product name after the visible heading changes. Treat schema as part of content maintenance, not a once-only technical task. Run key pages through Google's Rich Results Test before launch and again after a template change, because Google notes that markup can break after deployment through templating or serving issues. Google's structured-data introduction explains the general validation approach.

Stage 6: test speed, mobile use and crawl access

Open each key page on a phone and a slower connection. Read it without zooming; tap the navigation and form; check that important text does not shift as images load. Google's Core Web Vitals measure real-world loading, responsiveness and visual stability; its targets are Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint under 200 milliseconds and Cumulative Layout Shift under 0.1. You need not memorise the metric names to spot a huge hero image, a menu blocked by animation, or a button moving just as someone taps it. Use a speed-testing tool to identify the slow asset and fix the actual bottleneck rather than chasing a perfect score.

Check the live URL, not only a staging preview. Make sure it is not blocked by a noindex setting or robots rule accidentally carried from staging. Confirm that internal links point to the final clean URLs, that old URLs redirect if replacing a site, and that the canonical choice is sensible when duplicate versions exist. Submit a sitemap if your platform provides one, but remember that a sitemap is a discovery aid, not a guarantee of indexing. Google's SEO Starter Guide provides the baseline crawl and link checks.

Illustrative mobile failure: the furniture maker's hero photograph is 8 MB, and the quote button sits below three screens of generic copy. The owner compresses the image, keeps a short evidence-led opening and moves the enquiry step into view after the essential explanation. A different failure is a desktop navigation menu that cannot be opened by keyboard, leaving the shelving page effectively hidden for some visitors. Fixing these problems improves the experience regardless of ranking position.

Stage 7: launch seven pages and inspect what search sees

In an illustrative project, the owner spends two hours gathering real questions and facts, three hours drafting and editing seven pages, two hours adding photographs and checks, and one hour testing forms, mobile layout and search setup. That is eight hours of internal work, not a universal cost estimate. A quote or subscription may add external cost; assess it separately. If the owner has only four hours, publish fewer complete pages first rather than seven thin placeholders. One useful service page can outperform several pages that all say the same thing, though no outcome is guaranteed.

After launch, verify the property in Search Console, inspect the home and two key service URLs, and submit a sitemap if available. The URL Inspection tool reports index status and can test a live URL. Even a “URL is on Google” result means the page is eligible to appear, not guaranteed, and requesting indexing does not promise inclusion either. The performance report later shows queries, impressions and clicks. Save a launch baseline: published URL list, titles, form test result, important page load issues and the first Search Console checks. If a page is excluded, investigate the reported reason and the live page before changing its wording. If it is indexed but receives irrelevant queries, reconsider whether the page clearly answers the intended buyer question.

Consider an illustrative result after several weeks: the desk page gets 120 impressions and four clicks for sizing-related queries, while the shelving page gets 15 impressions and no clicks. These invented numbers are only a method demonstration. Read the queries and pages, then decide whether shelving needs clearer examples, better internal links or simply more time and demand. Do not ask AI to manufacture 20 similar shelving pages because a single report looks quiet. The focused SEO audit tutorial helps when enough live data exists to review.

Search Console should be paired with enquiries, not treated as the only measure. Record which page a visitor used before sending a form, what they asked for and whether the request matched the service. An illustrative desk page might attract fewer clicks than a broad care guide but bring more qualified quote requests. That does not mean the guide is useless: it may support existing customers and link to the right service. If an AI-generated title draws clicks from people looking for ready-made desks while the maker only offers commissioned work, correct the title and opening. More traffic with the wrong expectation wastes both the visitor's time and the workshop's response effort.

Maintain the facts that make the site worth finding

Keep a monthly change log for products, services, photos, fulfilment information and contact routes. If the furniture maker stops offering a particular finish, search for that claim across the site and edit each occurrence. If customers ask a new question repeatedly, add the answer to the most relevant existing page before creating another URL. If a page attracts visitors but few enquiries, review the offer clarity and form experience as well as the search snippet. SEO is a continuing feedback loop, not a switch the AI builder turns on.

Test changes one group at a time. Rewrite a vague service opening, add a measured example or improve navigation, then note the date and observe Search Console and enquiry quality. Do not treat a short-term click change as proof of causation; seasonality and ranking movement can interfere. Ask a colleague unfamiliar with the business to find the answer to a buyer question on the published page. If they cannot, a search visitor may struggle too. The final check is whether the site helps a real buyer decide and reach the business, with AI used for drafting and review rather than inventing the business behind it.

Search questions after the site goes live

Will AI-written pages automatically rank lower?

Google's published guidance focuses on the accuracy, usefulness and purpose of content, including AI-assisted content. A thin page made from generic claims is weak regardless of how it was written. Use AI for structure and drafts, then add your own evidence, check every claim and make each page answer a distinct customer need.

Should every page have schema markup?

No. Add structured data only when a supported type accurately describes visible page content and you can maintain it. Validate the markup against the relevant Google guidance and test it after changes. Schema can help search systems understand a page, but it does not guarantee a particular search feature or ranking.

How soon will Search Console show results?

Search Console is for checking discovery, indexing and performance; it is not a promise of immediate ranking. Inspect important URLs after launch and compare impressions, clicks and queries over a meaningful period. If a page is absent, check its index status, canonical choice, internal links and crawl access before rewriting the copy.

Further reads

• How to Write Website Articles With AI That Still Rank on Google — Develop individual editorial pages after the core site.
• How to Write an AI Disclosure Statement for Your Website — Decide whether a disclosure belongs on the site.
• Does Google Penalise AI-Written Content on a Business Website? — Understand the quality rules for AI-assisted copy.
• How to Use AI to Find Out Why Website Visitors Don't Buy — Investigate visits that do not become enquiries.
• How to Audit Your Website for AI Content That Needs Fixing — Find weak pages once real visitors arrive.
• AI Real Estate SEO: Neighbourhood Pages That Avoid Steering — How agents can draft neighbourhood pages with AI without steering language: verified facts, a page template, wording rewrites and a review routine.
• SEO for AI Search: A Client Audit Checklist for Agencies — A seven-part agency audit checklist: crawler access, indexability, answer clarity, entity facts and citations, tied to Google's own AI-search guidance.
• SRA Transparency Rules: Use AI to Draft Price and Service Pages — Use AI to draft price, service, complaints and regulatory pages against the SRA transparency rules, then fact-check every figure against your own pricing.
• Scaled Content Abuse: An AI Content Checklist for SEO Agencies — What Google's scaled content abuse policy covers, a value-added test, a page-level QA checklist and an AI content workflow agencies can run per client.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Google Search Central, SEO Starter Guide; Creating Helpful, Reliable, People-First Content; Guidance on Generative AI Content on Your Website; How To Use Search Console; Intro to How Structured Data Markup Works; Structured data general guidelines; Understanding Core Web Vitals; Search Console Help, URL Inspection tool (read 4 November 2026).