Skip to content
All articles
AIWeb DevelopmentWebsite SecurityHiring a DeveloperSmall Business

AI-Built Website Checklist: 5 Security, Legal and SEO Gaps to Check (With Prompts)

Suley Tangun

Suley Tangun

Digital Marketing Specialist

Laptop showing a list of AI check prompts and a phone showing a website with a cookie banner on a garden room desk

Published · Updated · 12 min read

This AI-built website checklist covers the five gaps that cost businesses real money: customer data you are legally responsible for, exposed API keys, a missing privacy policy, cookie banners that don't block tracking, and weak security. AI tools rarely mention any of them unless you ask. Below you'll find what to check, and a library of prompts you can paste into your own AI tool to check it for you.

The bottom line

What can go wrong
Compensation claims, a bill run up on a stolen key, or a breach you have to report to the regulator
How long the checks take
About an afternoon with the prompts below
What to do
Run the security and privacy prompts before customers use the site
Conclusion
Better to find a problem yourself than hear about it from a customer, the ICO or your bank

Why AI-built websites need checking

AI is fast at layouts, forms, repeated components and first drafts. I build client sites with AI coding tools every day, and the first draft is often better than people expect.

What AI doesn't know is your business, your customers or your legal duties. It produces something plausible, and plausible is a long way from safe. It also writes confident sentences about things it cannot know, such as your prices, how long you have been trading or the awards you have won. Those claims go live unless a person reads every one.

If you haven't built your site yet and want to know whether AI is the right route, start with Can you build a business website with AI? This post is for checking a site that already exists.

The five gaps that can cost you money

Most problems on an AI-built site are annoying. These five can lead to legal claims, fines, surprise bills or lost customers, so check them first.

43%

of UK businesses had a cyber breach or attack in the past 12 months

23.8 million

passwords and keys leaked in public code on GitHub in 2024

72 hours

to report a risky personal data breach to the ICO

1. Customer data you are legally responsible for

If your site collects names, emails, phone numbers or bookings, you are responsible for that data under UK GDPR, the UK's data protection law. The ICO, the UK's data protection regulator, says anyone who suffers damage because an organisation broke that law, whether they lost money or suffered distress, can claim compensation through the courts.

That is separate from any action the ICO takes itself, which can include fines. An AI tool will happily build a form without asking where the data goes, who can see it or how long you keep it.

2. Exposed API keys that run up a bill in your name

An API key is the password your site uses to talk to other services, such as payments, email, maps or an AI model. AI builders sometimes paste these keys into code that runs in the visitor's browser, or into a public code repository.

Bots scan for leaked keys constantly, and a stolen key for a paid service is billed to you. Keep keys on the server, never in front-end code, and set spending limits and alerts on every account that has one.

3. A missing or mismatched privacy policy

UK GDPR gives people the right to be told what you do with their data when you collect it. On a website, that is your privacy policy: what you collect, why, who you share it with (your email platform, booking tool or analytics), how long you keep it and how people can ask for it to be deleted.

AI builders often leave the page out, or write a generic one that lists services your site doesn't use and misses the ones it does.

A cookie banner only helps if it is wired up properly. Advertising tags such as the Meta pixel and Google Ads need a visitor's consent before they load, and the ICO says rejecting should be as easy as accepting. A common AI-built mistake is a banner that looks right while the tracking fires the moment the page opens.

Google has its own rules. Its EU user consent policy covers visitors in the UK and EEA, and advertisers pass each visitor's choice to Google through Consent Mode. If your banner doesn't send those signals to Google Analytics 4 (GA4) and Google Ads, you can lose remarketing audiences and conversion data, which makes your ad spend harder to judge.

The ICO's 2026 guidance allows some statistical analytics without consent, with conditions. Check the guidance or take advice before deciding what your analytics needs.

5. Weak security that puts customer data at risk

The government's Cyber Security Breaches Survey 2025 found that 43% of UK businesses had a cyber breach or attack in the previous 12 months. On an AI-built site the usual weak spots are an admin page anyone can open, a database whose privacy settings were never switched on, forms with no protection against spam bots, and packages nobody updates.

If personal data leaks and people could be at risk, you must report it to the ICO within 72 hours where you can.

Other things AI-built sites often get wrong

  • Content you can't take with you. Some platforms make it easy to build and hard to leave, so moving later means starting again. I compare the options in WordPress vs AI website builders.

  • Search engines seeing less than you do. Some AI builders make pages whose content only appears once JavaScript has loaded. Google says not all bots can run JavaScript, so some crawlers may see a page with little or nothing on it.

  • Weeks going in circles. Without the technical words to describe a fault, you ask the tool to "fix the layout" over and over while it changes the wrong thing.

What the prompt library checks

Each group has its own prompts in the library, starting with the ones that carry the most risk.

  • Security. Keys in the wrong place, admin pages that are not really protected, forms anyone can abuse, out-of-date packages.

  • Privacy and cookies. What loads before a visitor agrees, whether your banner controls GA4 and ad pixels, and what personal data you hold without realising.

  • Pages and legal. Privacy policy, terms, contact and company details, a proper 404 page, and placeholder text nobody replaced.

  • Forms and email. Enquiries that quietly fail, and email that lands in spam.

  • Search and speed. Titles, sitemaps, redirects from your old site, and the images and scripts that slow a phone down.

  • Accessibility and quality. Keyboard use, contrast, layout on real phones, and claims on the page that are wrong or can't be proved.

  • Running it. Backups you have never restored, accounts you don't own, and nothing to tell you the site is down.

How to use the prompts on your own site

  1. Open your project in an AI coding tool that can read your files, such as Claude Code, Cursor, Codex or GitHub Copilot in agent mode. On Wix, Squarespace or a similar builder you can't open the code, but the Pages and legal, Privacy and cookies, and Accessibility and quality prompts still work if you paste in your page text.

  2. Back the project up first, or commit it, so there is always a way back.

  3. Copy one prompt, paste it and read the report. Every prompt tells the AI to report only and leave your files alone.

  4. Fix the Critical and High items first, one at a time, then run the same prompt again to confirm each fix worked.

  5. Tick the prompt off in the library. Your ticks stay in your own browser.

Three cautions before you start

  • Never paste a real password or key into a chat.

  • Treat findings as leads, not a verdict. The AI can be wrong.

  • Use a different tool or model from the one that built the site. One tool checking its own work tends to repeat its blind spots.

The prompt library

Pick a group, open a prompt and read what it checks. The bar shows one line of the prompt beside a Copy button, and Show full prompt reveals the whole text that Copy puts on your clipboard.

20 prompts in 7 groups. Run them one at a time in an AI tool that can read your project, and tick each one off as you go. Your ticks are saved in this browser only.

0 of 20 run

Most hacked small-business sites are not hit by anything clever. A key was left where anyone could read it, an admin page was open, a form had no limits, or a package nobody updated had a known hole. These five prompts look for those. Start with secrets and access, because they are the ones that cost the most when they go wrong.

  • AI tools often put a key straight into the code to make something work, then forget it. A key in the code that reaches the browser, or in the project's history, can be found and used by anyone. This prompt looks for keys in files, in the browser bundle, in git history and in logs, and tells you which ones to replace.

    Find passwords, API keys and tokens that are exposed in the code, the browser bundle, git history or logs.

    You are a senior application security reviewer. Audit this project for exposed secrets.
    
    First:
    - Work out what this project is built with (framework, hosting, database, login system, payment and email services) by reading the config and package files, and tell me in two lines before you start.
    
    Ground rules:
    - Report only. Do not change, create, move or delete any file, and do not run anything that changes data, sends email or deploys.
    - If you cannot tell something from the code, write "cannot tell from the code" and say what I would need to check, instead of guessing.
    - Never print a real secret, key or password. Show the file, the line and the first four characters only.
    - Be specific: name the file and line for every finding, and quote the short piece of code involved.
    
    Check each of these:
    1. Search every file, including config, scripts, docs, tests and example files, for API keys, tokens, passwords, private keys, database connection strings and webhook secrets.
    2. Check which environment variables are exposed to the browser. In Next.js that is anything starting NEXT_PUBLIC_, in Vite anything starting VITE_, and so on. Flag any secret, service-role key, admin key or private API key that has been given a browser-visible name.
    3. Check whether .env files, key files or backups are committed, or listed in .gitignore too late. Look through git history for secrets that were committed and later removed, because removing them from the latest version does not remove them from history.
    4. Check the built output and any source maps for embedded keys.
    5. Check logging and error handling for places that print keys, tokens, session cookies, passwords or full request bodies.
    6. Check that example files (.env.example and similar) contain only placeholders.
    
    Report as a table with these columns: Severity (Critical, High, Medium or Low), Where (file and line), What is wrong, Why it matters, How to fix it.
    Add a second table called "Replace these": for each secret that has been exposed, say which service it belongs to and that I should create a new one and revoke the old one, because deleting it from the code does not make it safe again.
    Then list what looks fine, in one line each. Finish with the three fixes I should make first, in order, and what each one would take (minutes, hours or days).
  • A hidden button is not protection. If the admin area, an API route or a database table answers anyone who asks, it is open. This prompt checks that every protected page and action is checked on the server, that one customer cannot read another's data, and that login, sessions and password reset are built properly.

    Check that every admin page, API route and database rule is protected on the server, not just hidden in the interface.

    You are a senior application security reviewer. Audit this project for broken access control and weak login.
    
    First:
    - Work out what this project is built with (framework, hosting, database, login system, payment and email services) by reading the config and package files, and tell me in two lines before you start.
    - List every route, page, API endpoint, server action and database table or collection in the project, and mark which ones are meant to be private.
    
    Ground rules:
    - Report only. Do not change, create, move or delete any file, and do not run anything that changes data, sends email or deploys.
    - If you cannot tell something from the code, write "cannot tell from the code" and say what I would need to check, instead of guessing.
    - Never print a real secret, key or password. Show the file, the line and the first four characters only.
    - Be specific: name the file and line for every finding, and quote the short piece of code involved.
    
    Check each of these:
    1. For each private route or action, confirm the code checks who is asking on the server before doing anything. Hiding a link or button in the interface does not count.
    2. Look for places where a user could change an id in a URL or request (an order, invoice, booking or profile) and see someone else's data. Check that each lookup also checks ownership.
    3. Check roles. Can an ordinary user reach admin functions by calling the endpoint directly?
    4. If the project uses a hosted database with row-level security or security rules (Supabase, Firebase or similar), check that every table that holds private data has rules switched on and that the rules are not simply allowing everyone.
    5. Check login: passwords are hashed by a proven library or the provider, there is a limit on repeated attempts, and error messages do not reveal whether an email exists.
    6. Check password reset and magic links: tokens are random, expire quickly, work once, and are not logged.
    7. Check sessions and cookies: HttpOnly, Secure and SameSite are set, sessions end on sign-out, and sensitive actions (changing email or password) ask for the password or a second factor again.
    8. Check whether two-factor sign-in is available for admin accounts, and say if it is not.
    
    Report as a table with these columns: Severity (Critical, High, Medium or Low), Where (file and line), What is wrong, Why it matters, How to fix it.
    Then list what looks fine, in one line each. Finish with the three fixes I should make first, in order, and what each one would take (minutes, hours or days).
  • Every box a visitor can type into, every file they can upload and every link parameter is a way in. This prompt checks that the site does not trust any of it: that input is validated on the server, nothing is put into a page or a database query unsafely, uploads are restricted, and forms cannot be hammered by bots.

    Check forms, URL parameters and file uploads for injection, script injection, unsafe uploads and missing limits.

    You are a senior application security reviewer. Audit this project for injection, cross-site scripting, unsafe uploads and abusable forms.
    
    First:
    - Work out what this project is built with (framework, hosting, database, login system, payment and email services) by reading the config and package files, and tell me in two lines before you start.
    - List every place the project accepts input from a visitor: forms, URL parameters, headers, cookies, uploads, webhooks and API calls.
    
    Ground rules:
    - Report only. Do not change, create, move or delete any file, and do not run anything that changes data, sends email or deploys.
    - If you cannot tell something from the code, write "cannot tell from the code" and say what I would need to check, instead of guessing.
    - Never print a real secret, key or password. Show the file, the line and the first four characters only.
    - Be specific: name the file and line for every finding, and quote the short piece of code involved.
    
    Check each of these:
    1. Check that every input is validated on the server (type, length, allowed values), not only in the browser.
    2. Look for database queries built by joining strings or using raw SQL with user input. Parameterised queries or the library's own query builder should be used.
    3. Look for any use of dangerouslySetInnerHTML, innerHTML, document.write, eval or template rendering that outputs user-supplied text without escaping, and for user content shown in emails.
    4. Check redirects that take a destination from the URL, and any server code that fetches a web address supplied by the visitor, because both can be abused.
    5. Check uploads: allowed file types are checked by content and not only by name, there is a size limit, files are stored outside the web root or in a private bucket, filenames are not trusted, and uploaded files cannot be run as code.
    6. Check forms that change data (not only the contact form) for protection against forged requests, such as SameSite cookies or tokens.
    7. Check every public form for spam and abuse protection: rate limiting, a honeypot or a bot check, and a cap on message length. Check that a bot cannot use the form to send email to other people.
    8. Check that error messages shown to visitors do not include stack traces, file paths, queries or internal ids.
    
    Report as a table with these columns: Severity (Critical, High, Medium or Low), Where (file and line), What is wrong, Why it matters, How to fix it.
    Then list what looks fine, in one line each. Finish with the three fixes I should make first, in order, and what each one would take (minutes, hours or days).
  • A site is built from hundreds of other people's packages, and old ones get known holes. The way the site is served matters too: security headers tell the browser what it may and may not do, and a few leftover files or debug settings give attackers a map. This prompt checks both.

    Check dependencies for known vulnerabilities, and the site's security headers, HTTPS, CORS, cookies and exposed files.

    You are a senior application security reviewer. Audit this project for vulnerable packages and weak hosting configuration.
    
    First:
    - Work out what this project is built with (framework, hosting, database, login system, payment and email services) by reading the config and package files, and tell me in two lines before you start.
    - If you can run a read-only dependency audit (for example npm audit, pip-audit or the equivalent), do so and include the results. If you cannot run it, tell me the exact command to run.
    
    Ground rules:
    - Report only. Do not change, create, move or delete any file, and do not run anything that changes data, sends email or deploys.
    - If you cannot tell something from the code, write "cannot tell from the code" and say what I would need to check, instead of guessing.
    - Never print a real secret, key or password. Show the file, the line and the first four characters only.
    - Be specific: name the file and line for every finding, and quote the short piece of code involved.
    
    Check each of these:
    1. List dependencies with known vulnerabilities, with severity and the version that fixes each. Say which ones are in production code and which are only used during development.
    2. List packages that are abandoned, very old, or far behind the current major version, and note anything that needs a major upgrade to be safe.
    3. Check that a lockfile is committed and that the install in production uses it.
    4. Check the security headers the site sends (in the framework config, a middleware file, hosting config or a headers file): Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, Referrer-Policy, Permissions-Policy and frame protection (frame-ancestors or X-Frame-Options). Say which are missing and suggest values that will not break the site.
    5. Check that everything is served over HTTPS, that http redirects to https, and that cookies are marked Secure.
    6. Check CORS: flag any rule that allows every origin on endpoints that use cookies or return private data.
    7. Check that debug mode, verbose errors, test routes, sample data and admin tools are switched off for production, and that source maps are not publicly served unless intended.
    8. Check for files and paths that should never be public: .env, .git, backups, database dumps, config files, /admin or /phpinfo style pages, and directory listings.
    
    Report as a table with these columns: Severity (Critical, High, Medium or Low), Where (file and line), What is wrong, Why it matters, How to fix it.
    Then list what looks fine, in one line each. Finish with the three fixes I should make first, in order, and what each one would take (minutes, hours or days).
  • The services your site connects to need handling carefully. A payment webhook that does not check who sent it can be faked, a card number should never touch your own server, and every third-party script on the page runs with the same power as your own code. This prompt checks each of those connections.

    Check payment and webhook handling, API key scope and every third-party script loaded on the site.

    You are a senior application security reviewer. Audit this project for unsafe use of third-party services, payments and scripts.
    
    First:
    - Work out what this project is built with (framework, hosting, database, login system, payment and email services) by reading the config and package files, and tell me in two lines before you start.
    - List every external service the project talks to (payments, email, analytics, maps, chat, forms, CMS, storage) and every third-party script or iframe the pages load.
    
    Ground rules:
    - Report only. Do not change, create, move or delete any file, and do not run anything that changes data, sends email or deploys.
    - If you cannot tell something from the code, write "cannot tell from the code" and say what I would need to check, instead of guessing.
    - Never print a real secret, key or password. Show the file, the line and the first four characters only.
    - Be specific: name the file and line for every finding, and quote the short piece of code involved.
    
    Check each of these:
    1. For payments, confirm that card details are collected by the payment provider's hosted fields or checkout and never pass through this project's own server or logs.
    2. For every webhook endpoint, confirm the code verifies the sender's signature before doing anything, rejects repeats of the same event, and does not trust amounts or prices sent by the browser. Prices and totals must be calculated on the server.
    3. For each API key the project uses, say whether it has more permission than it needs, and whether a restricted key or a separate read-only key would do.
    4. List third-party scripts loaded on pages. For each, say what it is for, whether it loads before the visitor has agreed to anything, and whether it is still needed. Flag scripts loaded from a domain that is not clearly the vendor's.
    5. Check embeds (maps, video, chat widgets) for permissions they do not need, and for whether they set cookies before consent.
    6. Check that outgoing emails and notifications cannot be used to send content to arbitrary addresses.
    
    Report as a table with these columns: Severity (Critical, High, Medium or Low), Where (file and line), What is wrong, Why it matters, How to fix it.
    Then list what looks fine, in one line each. Finish with the three fixes I should make first, in order, and what each one would take (minutes, hours or days).

Free tools to check your live site from the outside

The prompts read your code. These tools look at the live site the way a visitor, a search engine or an attacker would.

What to ask whoever builds or looks after your site

Most developers use AI in some form now, so the useful question is how they check what it produces:

  • Where are the API keys kept, and is there a spending limit on each account?

  • Does the cookie banner actually block GA4, the Meta pixel and Google Ads until a visitor agrees?

  • Who can see the customer data the site collects, and how is it protected?

  • Could they explain what is in the code if something breaks a year from now?

When to bring in a person

An AI audit finds a lot, but it can't give legal advice, it can't attack your site the way a professional penetration tester would, and it can't decide which findings matter most to your business.

Get someone who understands code to look at the site if it takes payments, stores customer accounts or personal details, runs advertising tags or works in a regulated sector. The same goes if any report contains something you don't understand. Twenty findings with no priority is a to-do list that never gets done.

Use AI freely for drafts. Before anything goes live, check where the keys are kept, that a real privacy policy is in place and that nothing tracks visitors before they agree.

If you have built a site with AI and got stuck, or want a second opinion on one that is already live, get in touch and I'll take an honest look.

This is general information based on what I see in practice, not legal advice.

Sources (9)

Frequently asked questions

Is an AI-built website secure?

Not automatically. AI tools do what they are asked, so gaps such as exposed keys, open admin pages or unprotected forms can go unnoticed. Security needs someone deliberately checking for it, which is what the security prompts in this checklist are for.

Can I be sued if my website mishandles customer data?

Yes. Under UK GDPR, anyone who suffers damage because a business broke data protection law, including financial loss or distress, can claim compensation through the courts. The ICO can also take its own action, which can include fines.

What happens if my website's API key is exposed?

Anyone who finds it can use the service it gives access to, and the bill comes to you. Keep keys on the server, set spending limits and alerts on every account, and replace any key you think has been exposed straight away.

Do I need a cookie banner on a UK website?

If your site uses advertising or tracking tags such as the Meta pixel or Google Ads, yes, and the banner must stop them loading until the visitor agrees. The ICO's 2026 guidance allows some statistical analytics without consent, with conditions, so check it before deciding.

Does my website need a privacy policy?

If it collects personal data such as names, emails or phone numbers, UK GDPR says you must tell people what you do with it when you collect it. A privacy policy is the usual way, and it should match the tools your site really uses.

Can I use these prompts on Wix, Squarespace or Shopify?

Partly. You can't open the code on a hosted builder, but the pages, privacy, accessibility and content prompts work if you paste in your page text, and the free outside-in tools work on any live site.

Will the AI fix the problems it finds?

Not unless you ask. Every prompt tells the AI to report only. Fix the most serious items one at a time, with a backup first, and run the same prompt again to check each fix.

Was this helpful?

Share this article

Found this useful? Let's talk about yours.

Tell me about your project and I'll come back with an honest recommendation, timeline and cost, with no obligation.

Start a project