Built Your Website With AI? Modern SEO and AEO for AI Site Builders

What changes when an AI builds your website?

AI website builders turn a description into a working site. They come in two broad kinds: app builders that write the code for you (Lovable, Bolt, v0, Replit and similar tools), and hosted website platforms with AI features built in (Wix, Squarespace, Framer, Webflow, Hostinger and others). Both can get a business online in an afternoon.

What they optimise for is how the site looks in a preview. Search engines and AI assistants don't look at the preview — they read the code underneath. That's where AI-built sites most often fall short, and it's fixable once you know where to look.

Can Google and AI assistants actually read your AI-built site?

Not always. Many AI app builders have generated single-page apps that build the page in the visitor's browser with JavaScript. A person sees a finished site. A crawler that reads only the raw HTML sees an almost empty file. Google can run JavaScript, but it does so later and less reliably, and most AI crawlers — the ones behind ChatGPT, Claude and Perplexity — don't run it at all.

Some builders have started generating server-rendered sites for new projects, which sends the full content in the first response. Older projects, and anything built from a single-page template, may still be client-rendered. Don't assume — check.

1. Open your homepage in a browser, right-click and choose "View page source".
2. Search the source for a sentence you can see on the page, such as your headline.
3. If the sentence isn't there — only a near-empty <div> and some script tags — crawlers that don't run JavaScript can't read your content.
4. Fix it by asking your builder to use server-side rendering or static pre-rendering for public pages, or by moving to a template or host that supports it.

A free SiteScan report runs this check for you. Look for "Readable content in page source" under AI Visibility.

What does an AI builder usually leave out?

AI builders are good at layouts and copy, and inconsistent at the invisible details search engines rely on. These are the gaps we see most often on AI-built sites:

• The same title and meta description on every page, or generic ones like "Home" and "Vite + React".
• No sitemap.xml, or a robots.txt copied from a template that blocks more than it should.
• Links that are buttons with click handlers instead of real <a href> links, so crawlers can't follow them to your other pages.
• Missing pages that answer "200 OK" instead of a real 404, so search engines index empty error pages.
• No structured data, so machines have to guess your business name, location and services.
• No canonical tags, no language attribute and no social-sharing image.
• Several H1 headings per page, or none, because headings were chosen for how they look.
• Huge images and animation libraries that make the site slow on a phone.

How do you prompt an AI builder for good SEO?

AI builders do what they're asked, so ask specifically. Paste requests like these into your builder one at a time and check the result after each:

1. "Render every public page on the server (or pre-render it as static HTML) so the full text is in the initial HTML response."
2. "Give every page a unique <title> under 60 characters and a unique meta description under 160 characters, based on that page's content."
3. "Generate a sitemap.xml listing every public page with lastmod dates, and a robots.txt that allows all crawlers and points to the sitemap."
4. "Use real <a href> links for all navigation, one H1 per page, and H2/H3 headings in order."
5. "Add a self-referencing canonical tag, lang="en" on the html element, and Open Graph tags with a share image on every page."
6. "Add Organization (or LocalBusiness) JSON-LD with our name, address, phone, logo and sameAs links to our official profiles."
7. "Return a real 404 status code for pages that don't exist."
8. "Compress and resize all images, lazy-load images below the fold, and remove animation libraries we don't need."

How do you make an AI-built site quotable by AI assistants?

Being readable is step one. Being worth quoting is step two — that's answer engine optimization (AEO). AI assistants break a customer's question into smaller questions, pull short passages that answer each one, and cite sources they can verify. Structure your pages for that:

• Use headings phrased as the questions customers ask, and answer each one in the first sentence underneath.
• State concrete facts plainly: what you offer, where you work, prices or price ranges, timelines, opening hours.
• Keep paragraphs short and use lists and tables for services, steps and prices — they're the easiest pieces to quote.
• Make your business identity unmistakable: the same name, address and phone number on your site, your Google Business Profile and your social profiles, tied together with schema.
• Show dates. Add a visible "last updated" date to key pages and keep your sitemap's lastmod dates accurate.
• Let the AI search crawlers in. Some hosting and security settings now include a one-click "block AI bots" option — make sure it isn't also blocking the bots that cite sources, such as OAI-SearchBot, Claude-SearchBot and PerplexityBot.

Is it OK to use AI to write the website copy too?

Yes — Google's guidance is that it rewards helpful content however it was produced. What it penalises is mass-producing pages mainly to rank, which its spam policies call scaled content abuse. The practical problem with AI-written copy is that it sounds like everyone else's: smooth, general and missing anything an AI assistant couldn't already say on its own.

Use AI for the first draft, then add what only you know: real prices, the questions customers actually ask you, the neighbourhoods you serve, photos of your own work, named team members and genuine reviews. That first-hand detail is what both Google's quality guidelines and AI assistants look for when deciding whom to trust — and it's the part no builder can generate for you.

What should you check before you launch?

• Your main text appears in "View page source", not only in the browser.
• Every page has its own title, description, H1 and canonical tag.
• yoursite.com/sitemap.xml and yoursite.com/robots.txt both load and look sensible.
• Organization or LocalBusiness schema is present, with your exact business name and contact details.
• A made-up address like yoursite.com/test-404 shows a 404 page with a real 404 status.
• The site loads quickly on a phone, not just on your laptop.
• Search and AI crawlers aren't blocked in robots.txt or by a firewall setting.
• The site is verified in Google Search Console and Bing Webmaster Tools, with the sitemap submitted.

AI builders have made a professional-looking website cheap and fast. Being found still takes the same groundwork it always has — the good news is that most of it is a handful of precise requests away.