I Built My Website With AI. What Should I Check Before Launch?
Test the live site before you share it. This practical checklist covers mobile layout, forms, accessibility, SEO, performance, privacy and deployment.

Start with what visitors need to do
Before launching an AI-built website, test the path from the homepage to the action a visitor needs to complete. On a service site, that may be finding the right service and sending an enquiry. On a portfolio, it may be opening a case study and finding a contact method. For a shop, it is finding an item, checking its details and completing the checkout flow in an approved test environment.
Write down the three things visitors should be able to do. Beside each one, describe the result you expect. For example: “A visitor can submit a contact form on a phone. They see a confirmation and we receive their message.” This separates a working feature from a button or message that only looks right on the screen.
Run the checks on the website users will actually visit, ideally just after a production deploy. Builders often show previews with different domains, environment variables and permissions. A button that works in the editor can behave differently when it points to the live URL. Retest after any change that affects routing, forms, payments or consent.
Check the live address and navigation
Open your preferred HTTPS URL in a fresh browser window. Visit the homepage and several individual pages directly. Open a tool or blog URL from the address bar, refresh it and confirm that the same content appears. Individual URLs should work when someone arrives from a search result or shared link without first visiting the homepage.
Check your chosen domain variant. If visitors can reach both the www and non-www versions, make sure the less preferred version leads to the intended destination. Follow an old link if you moved a page. Confirm that it takes you to the closest replacement when one exists. For an unknown URL, check that it shows a helpful error page and returns a 404 response.
Go through the header, mobile menu and footer. Click primary buttons, logo links and contact links. Look for placeholders, empty links and buttons that lead to the builder’s preview URL. Test related content links as well. A menu that points to the wrong page may be more damaging than a minor design flaw because it stops visitors from reaching what they came for.
Test on a real phone
Open the site on a phone as well as a desktop. Start with a narrow screen and scroll through a page with a form, cards or long headings. Check for sideways scrolling, text cut off at the edges and buttons that are hard to tap. Open and close the menu, then follow two links from it to see whether it behaves consistently across pages.
Try the contact or booking form with the phone keyboard open. Make sure the field you are typing in remains visible and that a sticky header, cookie banner or chat widget does not cover the submit button. Check whether the keyboard type suits the entry, for example when typing an email address. Read the confirmation or error while still on the same screen.
For a shop or booking site, inspect the points where layouts commonly get crowded: price and option controls, date selectors, checkout details, and the final confirmation. Rotate the phone or use another browser if your audience is likely to do that. Desktop device simulation can help find layout problems quickly, but a real phone also reveals touch and keyboard behaviour that a quick desktop scan can miss.
Send a real test through each form
Submit a clearly labelled test enquiry using a mailbox you can check. Confirm that the website accepts it and that it arrives at the intended destination. If the app stores messages in a dashboard, open the dashboard and check the record. If email notifications are part of the setup, check the inbox and spam folder, and verify that replying goes to the right address.
Try an empty required field and an obviously invalid email address. Check that the form explains what must be fixed. If it intentionally accepts an optional message, make sure the user can submit without that field. Try a short and a longer message. For a form that supports attachments, use a harmless test file and check the permitted format and size.
A success banner should mean the receiving system actually accepted the request. If the form shows success but nothing arrives, trace the delivery before launch. The configuration might point to an old inbox or a test environment. Fix the issue and run the full test again. Keep a note of when it was sent so you can distinguish a delayed notification from one that was never delivered.
Verify booking and payment flows safely
If the site takes payments, use the provider’s sandbox or test mode for the first full check. Try a successful test payment and a failure or cancellation that the provider supports. Verify what the customer sees at each stage and confirm that the order record shows the expected state. Check whether any receipt or confirmation reaches the correct address.
On a booking site, verify the time zone and the appointment details before and after confirming a test booking. Test whether an already reserved slot remains unavailable where it should. Cancel or change a test booking through the normal flow if customers are allowed to do so. Check what the dashboard and email say after the change, especially if different staff members will use the booking system.
Review the wording of key buttons. A button that says “Send enquiry” should not suggest a booking is confirmed unless that is what it does. A price shown before a request should match the offer the customer actually receives. Do not run an unnecessary live charge to prove that a test flow works. Follow the provider’s documented process for moving from test credentials to the production account.
Review the copy and accessibility
Read all the text that a customer can see, including the title, FAQ, service descriptions and contact pages. Remove placeholder copy and replace invented prices, testimonials or client names. Verify business hours and service areas. An AI-generated claim can look convincing even when it has no basis in your actual business.
Use the keyboard to move through the main navigation, form and any dialog. Check for a visible focus indicator and make sure you can leave the dialog and return to where you were. Verify that form labels clearly identify each field and errors explain what to correct. Add useful alternative text to images when their content matters. Decorative images do not need to repeat information that is already in surrounding text.
Check contrast and readability, including smaller text in the footer, pale button labels and form help messages. Reduce motion or remove a distracting animation if it interferes with reading. The W3C accessibility quick checks provide a useful starting point. A quick check helps identify issues, but a more thorough evaluation is needed if you are assessing conformance to a specific accessibility standard.
Check SEO and indexing before you share the URL
Give each important public page a title and description that match the content the visitor will find. Check the homepage, a main service or product page and one article. Use a clear main heading and link to important pages from the navigation or related content. A search engine should be able to discover the page through a normal link.
Inspect the site’s robots.txt file, page indexing directives and canonical URLs. A staging site may have a noindex directive that should be removed from public pages that are meant to be indexed. A canonical should point to the preferred URL for the content. Keep intentional indexing settings on private or utility pages as appropriate. Use actual access controls for private content because blocking crawling does not make a page private.
Add the production domain to Search Console and submit the production sitemap. Look at the list in that sitemap and check whether it contains your important final URLs. Use URL Inspection on a homepage and one priority page to verify what Google can fetch. A sitemap and successful live test help you diagnose discovery and access. Neither guarantees indexing or ranking. For more detail, see Google’s SEO Starter Guide.
Measure performance on the pages people will use
Start with the homepage and one page with an important task, such as a service page with a booking button. Run a mobile performance check in PageSpeed Insights. Lab results can show what happened in a simulated test. Real-user data, when available, describes how actual visitors experienced the page over time. A newly launched site may have little real-user data at first.
Look first for large images, slow third-party scripts and layout shifts. If a large image takes most of the initial loading time, test a smaller version that still looks good at the size it is displayed. The FixHubLab Image Compressor can help you compare image exports before deployment. Set appropriate image dimensions in your site so the page can reserve space before the image finishes loading.
Track the Core Web Vitals that match what you are checking. Largest Contentful Paint covers when the main visible content loads, Interaction to Next Paint measures responsiveness to interactions, and Cumulative Layout Shift captures unexpected movement. The web.dev thresholds guide explains how to interpret them. Save a baseline and retest after one change at a time so you know which change helped.
Review what the site collects and where it goes
Make a short inventory of the forms, analytics tags, maps, embeds and chat widgets on the site. For each one, record what visitors submit, which service receives it and where the operator can view it. Remove test integrations or duplicate trackers that were included by default. If a feature claims that data stays on the device, verify that claim against what the feature actually sends.
Check the privacy and cookie notices against the site you are launching. The notice should describe the tools you actually use, such as contact forms, analytics and external services. A generic policy can contain statements that do not match the website. Update those statements and make it easy for users to find privacy information and manage any relevant choices.
Test your consent controls in a fresh session where you can review their real behaviour. Decline optional settings and check that the site still works as intended. Then choose an optional setting and verify that it does what the notice describes. If the site serves different regions or needs specialised compliance review, verify the rules that apply before enabling additional tracking or ads.
Check access and production settings
Review who can sign in to the admin panel and who can deploy the site. Remove unneeded test accounts and keep access limited to the people who need it. Confirm that the admin editor and private pages require the expected sign-in. Search engine settings and hidden links are not a substitute for authentication or access checks.
Keep credentials in the hosting platform’s protected settings or an appropriate secrets manager. Check that API keys, database passwords and deployment credentials are not embedded in public client-side code or committed to a repository. If you discover that a secret was exposed, rotate it and review how it was used. The OWASP Secrets Management Cheat Sheet explains practical controls for handling credentials.
Check which environment the live site uses. Confirm that plans, notifications and integrations point to the right settings. Make sure you have a known working version to restore if the deployment causes a serious problem. If the site stores orders, messages or other records, check whether restoring code requires a separate data recovery plan. A code backup does not necessarily contain the database or uploaded files.
A worked example for a small service website
Imagine you used AI to build a renovation website with a homepage, gallery and enquiry form. On desktop the design looks ready. On a phone the gallery scrolls sideways and the form shows success even though no enquiry appears in the dashboard. The gallery also has a large banner image that delays the first view on a slow connection.
Fix the form first because it affects the main customer action. Submit a test, check both the dashboard and the configured inbox, and then confirm that invalid entries show a useful error. Fix the phone layout next and repeat the full tap path from the homepage to the form. Optimise the banner image and check the page again at the actual display size. Give the service page a descriptive title and link to it directly from the homepage.
Write a short launch record: the URL tested, the device, the expected result and what you observed. Save a screenshot of the confirmation or a reference to the test entry. If someone else built the site, the record keeps the handover clear. It also tells you which checks to run again after a redesign or a change to the email provider. If you hire someone to finish an AI-generated build, our guide to AI and freelancing explains how to define a testable first milestone.
Decide which issues should delay launch
Sort outstanding issues by their effect on visitors. A broken enquiry form, incorrect checkout state, inaccessible account flow or public exposure of private material should be fixed before you promote the website. A slightly uneven card layout on an informational page may be acceptable for the first release if people can still read it and use the links. Keep the issue visible in your notes so it gets assigned instead of forgotten.
Choose who can make the release decision and who can restore the previous version. On a small project that may be the same person. Write down the hosting dashboard or repository they need, and confirm that they can sign in before launch day. If a core flow fails after deployment, assign a clear action: restore the known working release or temporarily pause the affected feature while the team investigates.
What to check after launch
Within the first day, open the live site again from a different device or network. Verify that the key pages still load and that the form or other main action continues to work. Check the site logs or dashboard for unfamiliar errors if you have access. If the launch included changing domains or redirects, test important old links people may already be using.
During the first week, look for indexing and traffic signals rather than assuming you will see search growth immediately. Make sure the sitemap was read, inspect important URLs if there is a problem, and review any genuine visitor messages. Keep notes about changes you make so you can relate a new issue to the right release.
Before calling the work complete, answer these questions: can a mobile visitor complete the main task, does the result reach the right place, can important public pages be opened directly, and can you restore a known working version if something breaks? If one of those answers is unclear, assign that check to someone and verify it. The version visitors rely on is the live site, so use its behaviour to decide what is ready.
