A website launch checklist helps you check whether your site is ready for visitors to use. For an AI-built website, that means checking the content, privacy and security settings, search visibility, account ownership and the actions visitors can take. This guide gives you 30 pre-launch checks, explains how to verify each result, and sets out what to review during the first 30 days after launch. It also explains when a self-check is sufficient and when to involve a specialist.
TL;DR
Before launching an AI-built website, verify six areas: content, legal and privacy information, SEO, technical security, visitor experience, and account ownership. A finished design does not confirm these areas are ready. Use the 30 checks to record what you have tested, fix issues that affect visitors or their data, and assign someone to check the live site after launch.
- Pre-launch checks need evidence: confirm that claims are accurate, test enquiries at the receiving end, and verify company access to essential accounts.
- A missing enquiry, an exposed secret key or a consent failure needs attention before the affected feature goes live. One serious issue is enough to require a closer review.
- Use day 1, day 7 and day 30 as follow-up checkpoints, then repeat relevant tests whenever forms, tracking tools or site settings change.
What a design preview cannot confirm
A design preview shows how a page looks and responds to clicks. It does not, by itself, show whether a form submission reaches its intended destination or whether a testimonial is genuine. Those checks require evidence from outside the preview, such as a received test submission or an approved customer quote.
For example, a contact form could display a thank-you message while sending its notification to an old email address. To verify the form, submit a test enquiry and find that same enquiry in the intended inbox or customer relationship management system (CRM). Apply the same approach throughout the checklist: identify the result you need, then confirm it where it happens.
Apply the checklist to the features your website uses. Booking, payment and chatbot checks are only relevant when those features are present. If your website includes user accounts, stored records or transactions, add tests for permissions, data handling and recovery. Our guide to AI-generated code in production explains the broader technical checks for those features.
The website launch checklist: 30 pre-launch checks

The website launch checklist groups 30 checks into six areas, with five checks in each. Record each result as passed, needs a fix, not checked or not applicable. Add the evidence, the person responsible and the next action. A check that nobody has verified remains not checked.
Start with company access if an agency or freelancer will hand over the site, because you need that access to change settings and complete the other checks. Work through the content and visitor-facing functions next. Ask the developer or relevant adviser to confirm anything your team cannot verify.
1. Content accuracy and business details
Content checks confirm that the website describes your business accurately. AI-generated copy can contain invented facts, sometimes called hallucinations. A generated testimonial or an award claim therefore needs the same verification as any other claim you publish.
| Check | How to confirm it is ready |
|---|---|
| 1. Remove placeholder content and check image rights | Search for sample names, dummy contact details and unfinished text. Confirm that you have the right to use each image, including any conditions in the AI tool’s terms. |
| 2. Verify testimonials, logos and awards | Match each testimonial, client logo, case result and award to an approved record. Remove anything you cannot substantiate or do not have permission to publish. |
| 3. Confirm prices, numbers and service claims | Check prices, dates, service areas and statistics against current business records or reliable sources. Replace unsupported claims with accurate wording. |
| 4. Match business details across the site | Check the company name, address, phone, email and opening hours on key pages and in the footer. Confirm the KvK number for a Dutch business where relevant, and match the details to your Google Business Profile if you use one. |
| 5. Make the website’s purpose and next step clear | Read the home page heading and other key pages. A visitor should be able to identify what the website offers and where to find the information or action they need. Test the main navigation and calls to action. |
2. Legal and privacy information
Legal and privacy information needs to match what the website does. Begin by listing the data collected through forms, analytics, chatbots and newsletter sign-ups. Then check where that data goes and use the list to review the notices and consent settings.
Where GDPR applies and you collect personal data directly from visitors, Article 13 requires information about that processing at the time of collection. A privacy notice needs to explain who handles the data, the purposes and legal basis, retention, recipients and relevant rights. A generic template needs checking against your actual setup.
| Check | How to confirm it is ready |
|---|---|
| 6. Review the privacy notice | Match the notice to the actual forms and services in use. Make the relevant information available where visitors submit personal data, and check any chatbot or AI provider that receives it. |
| 7. Test cookie choices | Identify which cookies and tags require consent. Test the site before a choice, after acceptance, after rejection and after withdrawal. Consent-required tracking must follow the visitor’s choice. |
| 8. Check sales and booking information | If visitors can buy or book online, confirm the information required for that transaction. Make applicable prices, business details, contract terms and cancellation conditions available before commitment. |
| 9. Check withdrawal and refund information | For consumer sales, confirm which withdrawal rights and exceptions apply to the goods or services. Make the relevant information and cancellation process clear before purchase. |
| 10. Keep marketing choices separate | If marketing relies on consent, use a separate, unticked opt-in with clear wording. Confirm that a visitor can send an enquiry without signing up for marketing, and that the chosen preference reaches your mailing system. |
Cookie rules depend on the technology and its purpose. Dutch regulator ACM distinguishes tracking and privacy-sensitive analytics that require consent from functional and low-impact analytics cookies that may be exempt. Test the scripts themselves; a visible banner does not show whether tracking has stopped.
For EU consumer distance purchases, the withdrawal period is generally 14 days, with exceptions such as personalised goods and certain bookings for specific dates. The period starts at delivery for goods and contract conclusion for services. Ask a qualified adviser to confirm the requirements for your business. Our GDPR website checklist covers the wider privacy review.
3. SEO and Google AI search readiness
SEO checks confirm that search engines can access your public pages and understand their content. Focus on the pages you want visitors to find, such as your home page, product pages or key information pages. Test and private pages need their own access settings.
| Check | How to confirm it is ready |
|---|---|
| 11. Allow indexing of public pages | Check that important public pages load without a password and are not blocked by robots.txt or a noindex instruction. A noindex instruction tells search engines to leave a page out of results. Keep appropriate restrictions on private and test content. |
| 12. Review page titles and descriptions | Give each important page a specific title and meta description. Check that its main heading describes the page and that the remaining headings follow a clear hierarchy. |
| 13. Check the XML sitemap | Confirm that the sitemap lists the preferred public URLs you want indexed, excludes test and private pages, and is submitted in Google Search Console. Open a sample of its URLs to check that they work. |
| 14. Confirm preferred URLs and redirects | Choose the HTTPS address and preferred www or non-www version. Ask the developer to check that redirects and canonical tags consistently point to the intended public URLs. Map permanently moved old pages to relevant replacements. |
| 15. Validate any structured data | If the site uses structured data, check that it accurately describes the business and page content. Validate the markup and use Google’s Rich Results Test for supported search features. |
A canonical tag identifies your preferred URL when similar content is available at several addresses. A redirect sends a visitor from one address to another. For a permanent move, 301 and 308 are both permanent redirect codes; the important check is whether the old address reaches the correct replacement.
For Google’s AI Overviews and AI Mode, the usual SEO requirements still apply, with no special AI schema or extra technical requirement. A page must be indexed and eligible for a search snippet to be considered as a supporting link. Passing the checks does not guarantee indexing, rankings or inclusion in an AI answer.
4. Technical setup and security
Technical checks cover the live connection, access to site administration and any code added to the site. Confirm which tasks the hosting or website platform handles and which tasks belong to your team. Custom scripts and integrations need checking even when the platform manages the underlying hosting.
| Check | How to confirm it is ready |
|---|---|
| 16. Check HTTPS across the live site | Open key pages and confirm that they use HTTPS without certificate warnings. Check that HTTP addresses redirect correctly and that images and scripts do not load through insecure HTTP connections. |
| 17. Review browser-visible code for secrets | Ask the developer to check published code, embeds and browser responses for secret credentials, including private API keys and database passwords. A search for words such as “key” or “token” is only an initial check. |
| 18. Restrict admin access and assign updates | Give each authorised person an individual account with appropriate permissions. Enable multi-factor authentication and remove unused access. Confirm who applies updates to the CMS, plugins and custom components. |
| 19. Review third-party scripts and embeds | List each script, widget and integration, what it does, what data it receives and who maintains it. Remove unused additions and include relevant tools in the privacy and consent checks. |
| 20. Check error pages and browser identity | Open a made-up URL and confirm that the site returns a proper 404 response with useful navigation. Check that the favicon identifies your business in the browser tab. |
Browser-visible code is accessible to visitors, but not every visible key is a secret. For example, Supabase distinguishes publishable keys intended for client applications from secret keys that must stay on the server. Ask the developer to identify the key type and verify its permissions before deciding whether it is exposed.
If a secret credential has been published, revoke or rotate it and check for misuse. Removing it from the page does not invalidate a copy someone already obtained. Our guide to leaked API keys in AI products covers the response, while the website security checklist for Dutch SMEs covers the wider security assessment.
Need help checking custom code or data connections?
If your team cannot verify how an integration handles data or whether published code contains secrets, include those questions in an AI-Built Product Review before enabling the affected feature.
5. Forms, accessibility and mobile experience
Visitor testing confirms that people can use the site and complete the actions you offer. Follow each important route from the visitor’s first click to the result your team receives. Include keyboard use, form errors and mobile screens in those tests.
| Check | How to confirm it is ready |
|---|---|
| 21. Test forms and key website actions | Submit each form and complete any booking or purchase journey the website offers. Find the matching submission, booking or order in the receiving system. Test invalid input and failed steps, and check that confirmations match the recorded result. |
| 22. Test chatbot answers and handover | If you use a chatbot, ask about prices, availability, refunds and questions outside its approved information. Check that answers match business policy, uncertainty is handled clearly and visitors can reach a person. |
| 23. Check form labels and error messages | Give each field a clear label. Trigger an error and confirm that the message identifies what to fix, remains accessible to assistive technology and preserves valid entries. |
| 24. Check keyboard use, image alternatives and contrast | Complete key routes using only a keyboard, with a visible focus indicator. Check text contrast and text alternatives for meaningful images. Mark purely decorative images appropriately. Ask for an accessibility review where specialist testing is needed. |
| 25. Test mobile layout, controls and speed | Use representative phones and screen widths. Check menus, forms and buttons for clipping, overlap and accidental taps. Test key pages on a mobile connection, and investigate delays or layout shifts that interrupt reading or submission. |
For an end-to-end test, compare the visitor’s input with what the receiving system stored. A form record missing its message, a booking with the wrong date or an order with the wrong payment status still needs fixing. Check the relevant settings and integration logs, then repeat the test after correcting the problem.
For buttons and other pointer controls, WCAG 2.2 AA’s target-size criterion uses 24 by 24 CSS pixels, with spacing and other defined exceptions. This is one accessibility check, not a complete assessment. Use our WCAG accessibility guide for the wider review and website performance guide for AI-built sites when mobile tests reveal loading or layout problems.
6. Company ownership and access
Company ownership means authorised staff can operate, recover and transfer the website without relying on one external person. Verify access by signing in through approved company-managed identities. A list of account names alone does not show that access works.
| Check | How to confirm it is ready |
|---|---|
| 26. Verify domain and DNS control | Confirm that the company controls the domain registration, renewal details and DNS settings that connect the domain to the site. Check that recovery messages reach an authorised company contact. |
| 27. Verify builder or hosting access | Confirm company ownership or control of the workspace and billing. Give at least two authorised people individual admin access, with multi-factor authentication, and test the recovery process. |
| 28. Verify analytics and Search Console access | Check that authorised company users hold the required administrative or ownership permissions in analytics, Google Search Console and the tag manager. Remove obsolete access. |
| 29. Test backup or version recovery | Confirm what the backup or version history includes and how to restore it. Test recovery on a safe copy where possible. Record any items, such as form records or external settings, that the recovery process does not include. |
| 30. Complete the written handover | Record the services, owners, renewal dates, support contacts and steps for changing or removing access. Store credentials in an approved password manager, and confirm that someone other than the builder can follow the handover. |
After launch: website audit checklist for the first 30 days
A post-launch website audit checklist checks whether the public site continues to work after the launch settings, domain and traffic change. Use day 1, day 7 and day 30 as planned review points. These are suggested checkpoints; repeat a test sooner when a related setting or integration changes.
| When | What to check | Evidence to review |
|---|---|---|
| Day 1 | Important public pages are accessible to search engines. | Run Search Console’s live URL test for key pages. Check access and indexing instructions separately from whether Google has already indexed the page. |
| Day 1 | Old and alternative addresses reach the right pages. | Test important old URLs, HTTP addresses and the chosen www or non-www redirects. Confirm permanent moves use 301 or 308 where appropriate. |
| Day 1 | Forms and key website actions work on the public domain. | Test the live site’s forms and any booking or purchase journey. Confirm that submissions, bookings or orders reach the correct destination and produce accurate notifications. |
| Day 7 | Indexing reports show no unintended exclusions. | Review Search Console’s Page indexing report. Investigate important pages blocked or excluded unexpectedly; a new site may still be awaiting crawling or indexing. |
| Day 7 | Submissions and transactions match the receiving records. | Compare available form, booking or transaction logs with the intended destination. Investigate missing, incomplete or duplicate records, accounting for spam, failed attempts and intended routing. |
| Day 7 | Consent settings and structured data still behave correctly. | Repeat cookie acceptance, rejection and withdrawal tests. Revalidate changed markup, and review Search Console enhancement reports where relevant. |
| Day 30 | Content edits have not broken key visitor routes. | Check internal links, forms and mobile layouts after edits. Repeat performance tests on important or changed pages. |
| Day 30 | Chatbot information still matches business policy. | If a chatbot is active, review a privacy-appropriate sample of conversations and repeat questions about current prices, availability and handover. |
| Day 30 | Access and recovery remain current. | Review authorised users, remove leavers, check renewal contacts and confirm the recovery instructions still work. |
Keep a record of problems, the people responsible for fixing them and the retest results. A clean day-30 review is a record of those checks at that time. Continue monitoring key website functions, site changes and access after the first month.
Does the European Accessibility Act apply to your website?
The European Accessibility Act can apply when your website provides a covered service to consumers, including e-commerce. Dutch regulator ACM explains that covered e-commerce services have had accessibility obligations since 28 June 2025, with exemptions for qualifying microenterprises and other defined exceptions.
A website is not covered simply because AI helped build it. Check the service offered, the customers it serves and the applicable exemptions. If the rules apply, include the full relevant customer journey in the review. Basic keyboard, contrast and mobile checks alone do not establish legal compliance.
When a self-check is enough and when to get a review
A team can start with a self-check when it can verify the website’s content, data handling, key functions and account access. Bring in a relevant specialist when an important result remains unverified or a problem could expose data, lose transactions or block visitors from an essential service.
| Situation | Who to involve | What to ask them to verify |
|---|---|---|
| Public pages and a contact form | Site owner and builder, with another person testing the visitor route | Claims are supported, the form reaches the right destination, privacy information matches the setup and company access works. |
| User accounts or stored records | Developer or technical reviewer | Users can access only the records and actions permitted for their role. Test denied access as well as successful use, and check how records can be recovered after a failure. |
| CRM, booking or payment connections | Developer or technical reviewer | Information reaches the right system, access is restricted and failures are visible. Include the relevant transaction checks when a booking or payment is involved. |
| Custom code or uncertain credentials | Developer or security reviewer | Browser-visible code contains no secret credentials, and the connected services enforce the intended permissions. |
| Chatbot or additional personal-data collection | Technical reviewer and privacy adviser as relevant | Answers stay within approved business information, data destinations are understood and the privacy setup matches the processing. |
| Possible accessibility obligations | Accessibility specialist and legal adviser as relevant | The service’s legal scope and the accessibility of the relevant customer journey. |
| Builder or agency handover | Company administrator and the outgoing builder | Company staff can access, update and recover the site, and remove external access without losing control. |
Choose the review according to the issue and the evidence your team lacks. One exposed secret or a form that loses enquiries can justify holding back the affected feature. A count of minor issues does not determine whether the website is ready.
How Sunbytes reviews AI-built websites before launch
When a launch check raises a question about custom code, permissions or an integration, Sunbytes can scope an AI-Built Product Review around the relevant technical areas. Software engineers and security specialists examine the agreed code, product behaviour and setup, then explain the findings and their implications.
You receive findings with supporting evidence, a prioritised action plan and guidance for the team making changes. Your team can address the findings, or fixes and rechecks can be scoped separately with Sunbytes. The review covers the agreed technical scope; legal advice and any formal accessibility assessment need their own scope.
Sunbytes brings 15+ years of software delivery experience across 300+ projects, with Netherlands-led delivery. Access and information handling operate under its ISO 27001-certified information security management system; project-specific security controls are scoped separately.
Discuss your website’s launch checks with Sunbytes to agree which technical questions need review before visitors depend on the site.







