Home / Insights / Article

All insights

AI websites

Built your website with AI? 10 checks before you rely on it

It looks great, but is it working? How to check whether Google can read your AI-built site, whether every claim is true, whether enquiries arrive and whether you really own it.

In short: a website built with an AI tool can work well for a small business, but only if it passes the same basic checks as any other site. The failures are usually invisible: Google can't read the content, every page shares one title, the text makes claims that aren't true, the form goes nowhere, private data is exposed, or you can't move the site. Here are ten checks you can run in about an hour, and how to decide whether to fix or rebuild.

AI tools can now turn a few sentences into a polished-looking website in minutes. The questions owners ask afterwards are telling. A recent r/smallbusiness thread asked owners who built their site with AI whether it actually worked after launch: did it get organic traffic or leads, did Google index it properly, and was it still easy to maintain six months later? On r/ai_website_builder, an owner who used an AI builder for their business asked a blunter question: do sites built with AI actually rank on Google?

The honest answer: using AI isn't the problem. Shipping something nobody has checked is.

First, work out what kind of AI-built site you have

"Built with AI" covers different things, with different risks:

How it was madeWhat you usually end up withBiggest things to check
A chat assistant wrote the code and someone uploaded itHTML files or a small app on your own hostingForms, security, whether anyone can update it, accuracy of the text
An AI app builder generated and hosts the siteOften a JavaScript app that builds the page in the browserWhether Google can read it, separate page URLs, exposed data, export and ownership
A regular website builder's AI feature created the first draftA normal builder site with AI-written text and layoutAccuracy of the text, generic copy, speed, who controls the domain
Your existing site, with new pages written by AIThe same site, more pagesThin or repetitive pages, false claims

The first two checks matter most if you want to be found on Google.

The 10 checks

1. Can Google actually read your pages?

Some AI app builders produce sites where the HTML sent by the server is almost empty, and the text and links only appear after JavaScript runs in the browser. You see a finished page; a search engine may first see a blank shell. Google can run JavaScript, but its own documentation says pages wait in a rendering queue that can take longer than a few seconds, and it still recommends server-side or pre-rendering because it is faster for users and crawlers and "not all bots can run JavaScript".

The test takes two minutes:

  1. Open your home page on a computer. Right-click and choose View page source (or press Ctrl+U, Cmd+Option+U on a Mac).
  2. Press Ctrl+F and search for a sentence you can see on the page, such as your main heading or your phone number.
  3. If it's there, good. If the source is mostly a few empty tags and script files, the page is built in the browser.
  4. Confirm in Google Search Console: paste the URL into URL Inspection, choose Test live URL, then View tested page, and check the HTML for your text.

If your content is missing, more blog posts or a re-submitted sitemap won't help. The page needs to be delivered as real HTML, through a pre-rendering option if the tool has one, or by rebuilding the public pages. If Google can read the page but it still isn't appearing, our guide to why a website isn't showing on Google covers the other causes.

2. Does every page have its own address, title and description?

Click through your menu and watch the address bar. Each page should have a clean, separate URL such as /services or /contact. Addresses like /#/services are a warning sign: Google's JavaScript guidance says not to use fragments to load different page content, because Googlebot can't reliably resolve those URLs.

Then check the browser tab on each page. AI tools often leave the project name as the title everywhere. Each important page needs a unique title (under about 60 characters, saying what you do and where) and its own meta description.

3. Is everything on the site true?

This is the check people skip. AI writing tools fill gaps confidently, so read every page slowly and look for:

  • Years in business, licences, insurance, certifications or awards you don't have.
  • Services, areas or opening hours you don't offer.
  • Testimonials, star ratings or review counts that didn't come from real customers.
  • Statistics, guarantees or "trusted by" logos with nothing behind them.

Invented testimonials are more than embarrassing. In the US, the FTC's rule on consumer reviews and testimonials, in force since 21 October 2024, bans fake reviews and testimonials, including AI-generated ones, and allows civil penalties. In the UK, fake reviews became a banned practice under the Digital Markets, Competition and Consumers Act from 6 April 2025. Delete anything you can't back up, and use real proof instead: genuine reviews, photos of your own work and plain facts.

4. Do the forms, buttons and phone links reach you?

A form can show "Thanks, we'll be in touch" while sending the message nowhere. The visible form is easy to generate; actually delivering the email depends on hosting, mail settings and DNS records the tool may never have set up.

  1. From your phone, fill in every form with a test enquiry.
  2. Check the receiving inbox, including spam, within ten minutes.
  3. Tap every phone number, email link, booking button and map link.
  4. Repeat monthly, and after any change to the site or hosting.

If nothing arrives, the fix is usually in how form emails are sent and authenticated, as explained in getting visitors but no enquiries. If the form works but fills up with junk, see how to stop contact form spam without blocking real customers.

5. Is anything private exposed?

Simple brochure sites carry little risk here. It rises sharply once the tool adds logins, customer accounts, bookings with personal details or payments. In 2025 a published vulnerability, CVE-2025-48757, described apps generated by one popular AI app builder exposing their databases because access rules weren't set; the researcher reported problems in 170 of 1,645 apps checked. It's an easy mistake for generated code to make and a hard one for a non-developer to spot.

If your site stores customer data, ask a developer to confirm that database access rules are on for every table, that no secret keys appear in files the browser downloads, and that one customer can't see another's records by changing a number in the address bar. If something was exposed, our guide to what to do if your website has been hacked covers the first steps.

6. Do you own the domain, the code and the hosting?

With some AI builders, the site can't leave the tool. That's fine until prices change or you want someone else to work on it. Check:

  • Domain: registered in your name, in an account you can log in to, with auto-renew on.
  • Code or export: can you download the site's files or code? Try it now, not when you need it.
  • Hosting: whose account and card pays for it, and what happens to the site if you stop paying.

If someone else set it all up and you can't get in, start with what to do if you're locked out of your website.

7. Does it work on a phone, quickly?

AI-generated layouts often look best at the screen size they were previewed on. On your own phone, check that text is readable without zooming, nothing spills off the side and buttons are easy to tap. Then run your home page through Google's PageSpeed Insights. Large images and heavy scripts are the usual culprits; our guide to why a website is slow explains what to fix first.

8. Can everyone use it?

Generated pages often miss accessibility basics: images without text alternatives, low-contrast text, and form fields with no labels. Try using your site with only the Tab key and check you can reach every link and form. This matters legally for many businesses too, as we cover in ADA website compliance for small businesses.

9. Are the business basics right?

Your business name, address, phone number and hours should match your Google Business Profile exactly. If the site collects personal details, its privacy policy should describe what you actually do, not a generic one written for a different business. Our comparison of Google Business Profile vs a website explains how the two work together.

10. Who fixes it when something breaks?

A site generated in an afternoon still needs someone to renew the domain, keep the security certificate valid and notice when a form stops working. Write down who does each job. If the answer is "the AI", you're the one prompting changes, checking every result and keeping backups. Our guide to website care plans lists the jobs and how often they need doing.

The checklist at a glance

CheckA pass looks likeIf it fails
1. Google can read itYour headings and text are in the HTMLTurn on pre-rendering or rebuild public pages
2. Separate pagesClean URLs, a unique title on each pageFix routing, write titles and descriptions
3. Everything is trueOnly claims you can prove, real reviews onlyDelete or rewrite, add real proof
4. Enquiries arriveEmail arrives in the inbox within minutesFix form delivery and email records
5. Nothing exposedAccess rules on, no secrets in the pageStop collecting data until it's fixed
6. You own itYour name, your login, files you can downloadMove the domain to your account
7. Phone and speedReadable, tappable, loads quicklyCompress images, cut heavy scripts
8. AccessibleEverything reachable and labelledFix labels, contrast and alt text
9. Business basicsSame name, phone, hours; honest privacy policyCorrect details, rewrite policy
10. Someone owns upkeepA named person for each jobAssign it, or get help

Does Google penalise AI-written content?

Not for being written with AI. Google's guidance says appropriate use of AI or automation isn't against its guidelines, and it rewards helpful content however it's produced. What it acts against is churning out pages mainly to rank: its scaled content abuse policy, introduced in March 2024, covers mass-produced low-value pages, whether written by people, AI or both.

So a few genuinely useful pages beat fifty near-identical ones. If a tool offers to generate a page for every nearby town, read our guide to service area pages that aren't spam first. Pages that work are specific: real price ranges, real photos and the questions your customers actually ask.

Fix it, or rebuild?

  • Keep and fix if Google can read the pages, you own the domain and the failures are content, titles, forms or speed. These are usually quick jobs.
  • Rebuild the public pages if the content is missing from the page source and can't be pre-rendered, or nothing can be exported. Your text, photos and layout still serve as the blueprint.
  • Get a developer review first if the site handles accounts, payments or personal data and nobody has done check 5.

A rebuild needn't be long: a site with a handful of pages can often be rebuilt as fast, static HTML in a few weeks, as our guide to how long a website takes to build explains.

An example of how this plays out

This is a hypothetical example, not a client story. A two-person cleaning company in a mid-sized town builds its site with an AI app builder over a weekend. Three months later it has brought no enquiries and doesn't appear in Google even for the company's name.

The checks take about an hour. View page source shows only a few empty tags and script files, so Google is seeing very little (check 1). Every page has the same tab title, the project name (check 2). The About page says "over 15 years of experience" for a business that started two years ago, and three glowing testimonials were invented by the tool (check 3). The quote form shows a thank-you message but has never sent an email (check 4). The domain was bought inside the builder's account, and there's no export (check 6).

With no pre-rendering or export option, they rebuild the five public pages as plain HTML, move the domain into their own account, delete the invented claims, ask real customers for reviews and set up a form that delivers. They still use AI to draft new text, and read every word before it goes live.

FAQ

Can a website built with AI rank on Google?

Yes, if Google can read the content as normal HTML, each page has its own URL and title, and the content is genuinely useful. Sites that build content only in the browser are slower and less reliable to index.

How do I know if Google can see my AI-built website?

Choose View page source and search for a sentence you can see on screen, then run a live test in Search Console's URL Inspection. If your text is missing from both, Google sees very little.

Is AI-written website content bad for SEO?

Not in itself. Google says appropriate use of AI isn't against its guidelines. Problems come from mass-produced, low-value pages, which its scaled content abuse policy targets, and from text that is generic or not true.

Can I move my AI-built website to normal hosting?

Only if the tool lets you export the files or code, and you control the domain. If there's no export, the content, images and design can still be used to rebuild the site somewhere you control.

Should I use AI to build my small business website?

It's a quick way to draft a first version. Before relying on it for customers, run the ten checks above, especially Google readability, accuracy, working forms and domain ownership.

Next step

If you've run these checks and aren't sure what to do with the results, we can help. Aurel Digital builds small business websites and custom websites as fast, static HTML that Google can read, with the domain and hosting in your name. New sites start from $300, and if your AI-built site is worth keeping, we'll say so.

Send us your site's address through our contact page, or email James at james@aureldigitals.com, and we'll tell you which checks it passes and what fixing the rest would take.

Related: Website not showing on Google?, Website visitors but no enquiries?, Locked out of your website?, Small business website checklist 2026

About the author: James is the founder of Aurel Digital, a remote studio founded in 2026 that builds websites, stores and apps for brands, nonprofits and service businesses. More about James and Aurel Digital.

Work Contact Call