Skip to content
Web Quality Assurance

Guide · checklist

Built your website with AI? What to check before you launch it

AI tools can produce a good-looking website in an afternoon. They also leave behind problems that are easy to miss because the site looks finished. Here's what to check before real visitors arrive.

Updated · by Adeoje Afeez

AI website builders and coding assistants are good at layout and confident-sounding copy. They're less good at knowing what's true about your business, and they don't click through every link on a phone. The result is a site that looks right on the first screen of a laptop and falls apart under a closer look.

None of this means AI-built sites are bad. It means the last 10% (the checking) is still your job.

1. Copy the AI made up

Generated copy fills gaps with plausible details. Read every sentence and ask whether it's true.

  • Invented numbers and claims

    “Trusted by 10,000 teams”, “4.9 stars”, “99.9% uptime”. If you can't back it up, remove it. Invented proof does more damage than no proof once someone notices.

  • Made-up testimonials

    Generated quotes with stock names are common in AI templates. Replace them with real ones or remove the section.

    Our review checks this

  • Features you don't have

    AI copy tends to list what products like yours usually do. Check every feature claim against what you've actually built.

  • Claims that contradict each other

    Generated pages are often written separately, so prices, limits and numbers drift between them.

    Our scan compares this across pages

  • Generic headlines

    “Revolutionize your workflow with our all-in-one platform” could describe anything. Say what it is, who it's for and what changes for them.

    Our review checks this

  • Leftover placeholders

    Search for lorem ipsum, “Your Company”, example email addresses, “#” links and template names.

2. Things that look right but don't work

  • Links that go nowhere

    Generated navigation and footers often point to pages that were never created.

    Our scan measures this

  • Buttons with no destination

    Click every button. Some are styled links with an empty or “#” address.

  • Forms that don't send

    Contact and sign-up forms are often wired to nothing. Submit each one and confirm the message arrives.

  • Missing images

    Images referenced but never uploaded, or pointing at the builder's preview server.

    Our scan measures this

  • Errors in the browser console

    Generated code can throw errors that break parts of the page in some browsers.

    Our scan measures this

3. Phones

AI previews are often judged on a desktop screen. Most visitors won't see it that way.

  • The page fits a narrow screen

    Wide tables, fixed-width sections and long words cause sideways scrolling on phones.

    Our scan measures this

  • The first mobile screen still makes sense

    Headline, what it is and the main button should all be visible on a phone without scrolling.

    Our review checks this

  • Menus open and close

    Generated mobile menus sometimes don't open, can't be closed, or cover the page.

4. The details that make a business look real

  • Who you are and how to reach you

    AI templates rarely include a real name, location or support address. Add them.

    Our review checks this

  • Policies that are linked

    Your site needs the policies that fit what it does, linked from every page.

    Our scan measures this

  • Policies that are true

    A generated privacy policy or terms page may describe data practices you don't have. Rewrite it to match what your site actually does.

  • A favicon and page titles

    Builders often leave the default icon and the same title on every page.

    Our scan measures this

  • Meta descriptions and alt text

    Often left empty or filled with generic text.

    Our scan measures this

5. Settings left over from development

  • Search engines are allowed in

    Remove any “noindex” tags and check robots.txt doesn't block everything.

  • HTTPS and the real domain

    The site should load on your own domain over HTTPS, and preview or staging addresses shouldn't be the ones you share.

    Our scan measures this

  • Analytics is yours and works

    Make sure analytics and pixels use your own account IDs, not the template's. Our scan checks that they send data when a page loads; the account IDs are yours to confirm.

    Our scan measures this

  • No test data in public

    Check for sample users, test products and demo content that shouldn't be visible.

Have it read by something that doesn't know what you meant

Our scan reads your public pages like a first-time visitor: it checks the technical basics marked above, compares claims across pages, and every finding quotes the page it comes from, so you can see exactly what to change.

It doesn't log in, submit forms or test checkout, so check those yourself.

More guides