An AI tool can produce a good-looking website in an afternoon. That speed is useful, but a polished homepage cannot show what matters once real customers start sending enquiries. You need to know who can log in and where passwords and keys are stored. You also need to know where form submissions go, what the site connects to, how it is updated and how you would recover from a problem.

This checklist helps a non-technical owner request evidence on each of those. For every item, it says what to ask for and who should be responsible.

What this checklist cannot do. It is a practical review, not a security assessment. A completed checklist does not prove a site is secure. If your site takes payments or handles health or other sensitive information, ask a qualified security professional to review it. Even the tools that build AI websites say this. Lovable’s documentation states that its scans “do not replace a thorough security review” and cannot guarantee complete security. It advises considering a professional review for apps that handle sensitive data.

Start with who can get in

Most small-business site problems begin with access. Common causes are a shared password, a former contractor who still has a login, or an administrator account with a guessable name.

Ask for a list of every person and tool that can sign in to the site, the hosting account and the domain. Remove anyone who no longer needs access. Turn on two-step authentication wherever it is offered.

The WordPress hardening guide recommends avoiding obvious usernames such as “admin”, using long passwords and enabling two-step authentication. The Canadian Centre for Cyber Security’s baseline controls add that people should have unique accounts and that access should follow least privilege. Access should also be removed when it is no longer needed. That guidance is version 1.2 and dates from 2020, so use it as a starting point rather than a current standard.

Look for exposed secrets

A secret is a password, key or token that lets one system talk to another, such as an email service key or a payment key. If a secret ends up in code that visitors can view, someone else can use it.

Ask the builder to show you where each secret is kept and who can see it. Lovable’s documentation says browser-side code cannot safely hold API keys, and recommends keeping them as secrets and calling the service from server-side code. That is one vendor’s guidance for its own platform, so read the documents for the tool you use. Do not paste real passwords or keys into an AI chat unless you have checked how the product handles them.

Treat form data carefully

Your contact form collects names, phone numbers and often a description of a problem at someone’s home. That is personal information.

Check where submissions are stored, who can read them, how long they are kept and where notification emails go. Submit a test enquiry, then check that it arrives, that spam is filtered and that someone would notice if delivery failed. If submissions are stored in a database, ask who can read the rows. Lovable’s documentation says row-level security policies, which control who can see which records, should be reviewed regularly, especially before publishing.

Make sure your privacy page describes what you actually do. If you are unsure about your legal duties, ask a qualified adviser.

Review every connection to another service

Booking tools, email services, analytics, chat widgets and payment links each add a connection. List them all. For each one, find out what information it receives, who owns the account and what happens if it stops working or is cancelled.

If your builder or developer uses AI coding agents with add-on tools, ask which ones. OWASP’s Q3 2026 roundup, published on 8 October 2026, reported incidents in AI coding tools and software package supply chains, and advised treating added tool servers as controlled dependencies. It did not report a verified compromise of an AI-generated website, so this is a question to ask, not a reason for alarm.

Ask which security standard the site meets

The baseline controls include one for websites. In its body text, the guidance asks that websites meet the OWASP Application Security Verification Standard at Level 1, and that outsourced websites have this as a contractual requirement. The guidance words this control slightly differently in its annexes, so ask your builder in writing which standard they apply and how they check it.

Make updates and backups somebody’s job

Websites need updates. The WordPress guide says to keep WordPress current, update plugins and delete the ones you do not use. It also says to keep regular backups of both the database and the full installation, with older snapshots kept in case a problem is noticed late. An AI tool that built your site may not maintain it for you. Ask who will do updates, how often, and how you will know it happened.

Know how you would recover

Ask three things before launch. Where are the backups kept? Who can restore them? Has anyone tested a restore? The baseline guidance says backups should be verified by restoring them. A backup nobody has tested is a hope, not a plan.

Ask also who you call if something goes wrong. The same guidance recommends a basic incident response plan that names responsibilities and contacts.

The launch checklist

Copy this table into a document. Fill in the last column before launch. Anything unresolved needs an owner and a date.

Check Evidence to request Who is responsible Unresolved issue
Administrator accounts reviewed List of all users with roles; removed accounts noted Owner and builder
Two-step authentication on Confirmation for the site, hosting and domain accounts Owner
Strong, unique passwords Password manager in use; no shared logins Owner
Secrets stored safely Written note of where keys live; none in public code Builder
Form test Test submission received; spam test; failure test Builder, then owner confirms
Form data handling Where submissions are stored, who can see them, how long they are kept Owner with builder
Database access rules Written confirmation that row-level security was reviewed, if a database is used Builder
Connections listed Table of tools, account owners and information shared Owner
Security standard Written answer on the standard the site meets Builder
Software updates Named person and schedule Care provider or owner
Unused plugins and tools removed List of what was removed Builder
Backups running Location, frequency, last successful run Host or care provider
Restore tested Date and result of a test restore Care provider or builder
HTTPS on every page Check across the main pages Builder
Monitoring and alerts Who is told if the site goes down Care provider or owner
Incident contact Who you call, and how Owner and provider
Domain and hosting ownership Accounts are in the business’s name Owner

What to do with the result

If most rows are complete, you are better prepared than many small sites. If several are empty, delay launch until each gap has an owner.

Security is not a one-time task. A site that is safe on launch day can be unsafe six months later if nobody updates it. That is the purpose of a care plan: a named provider who handles updates, backups, monitoring and fixes. Our Website Care & Management service covers those, and our Web Design & Development work plans for them from the start. If you have an AI-built site and want help reading your results, a free consultation is a sensible first step.