AI-Built Website Pre-Launch Checklist: What to Check Before You Go Live

An AI tool will tell you the site is done when it looks done. Launch readiness is a different test. These are the checks I run before a generated site goes in front of customers. Work through them in order and tick them off.

Does it work?

• Every link and button goes where it should. Click all of them, including the footer.
• The contact form sends. Submit a real test and confirm the message arrives in your inbox, not the spam folder.
• Refreshing a page other than the home page does not give a 404.
• The site works on a real phone, in portrait and landscape.
• Nothing says “Lorem ipsum”, “Your Company” or has a placeholder image.

Is the content true?

• Phone number, address and opening hours are correct.
• Every statistic and claim on the page is one you can prove. AI tools often invent numbers.
• Testimonials are from real customers who agreed to be quoted. Delete any that are not.
• Prices, if shown, are current.

Can people and Google find it?

• Each page has its own title and meta description, not the same text everywhere.
• There is one h1 per page, and the headings follow a logical order.
• Images have meaningful alt text.
• A sitemap.xml and a robots.txt exist, and robots.txt does not block the whole site. Preview environments sometimes ship with a noindex tag that carries over to production, so check the page source.
• The site is added to Google Search Console.
• If you serve a local area, your business name, address and phone are shown consistently.

Is it fast?

• Run the page through PageSpeed Insights and read the mobile result.
• Images are compressed and sized for display, not uploaded at camera resolution.
• There are no unused libraries or large animation packages loaded for one effect.

Is it safe?

• The site loads over HTTPS with no mixed-content warnings.
• No API keys or secrets are in the front-end code or the repository. Anything in the browser bundle is public.
• If there is a database, access rules are set so that visitors can only read and write what they should. Generated apps sometimes ship with permissive defaults.
• Forms have spam protection.
• Dependencies are installed from the lockfile and are not wildly out of date.

Is it legal?

If you operate in the EU, which includes Hungary, you need these before launch:

• A privacy policy that describes what data you actually collect.
• A cookie banner that blocks analytics and marketing scripts until the visitor agrees. A banner that only hides itself does not count.
• Company details in the footer or an imprint, as required for your business type.

Can you keep it running?

• The code is in a repository you own.
• You know where the domain is registered and who can log in.
• DNS records, including email, are written down somewhere.
• There is a backup plan, or the site can be rebuilt from the repository.
• Someone is responsible for updates.

When a checklist is not enough

If several of these boxes stay empty and you are not sure how to fill them, that is a normal point to ask for help. I check AI-generated sites against a list like this, fix what is broken and hand it back with notes.

Read more about the AI site cleanup and launch service, or send me a message with a link to your project. If the design is what bothers you, start with 10 fixes for an AI-built site that looks generic.