As of 13 August 2026, AI can only partly create a cookie consent banner for your website.

What to actually do

1. Hand it to a person

   The route this page recommends

   Someone with a licence or accountable authority has to sign this before it counts.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, power-user skill, and roughly 1 hour until you can act on the result.

   How to actually do it

   1. Open your website in a private browser window and use the browser developer tools to record cookies, local-storage entries, network requests and third-party scripts loaded before any choice is made.
   2. Open the settings pages for your website platform, analytics, advertising, chat, video, payment and other third-party services, then gather their cookie and tracking details and note which scripts can be held back.
   3. Paste the gathered details, platform information and the copyable prompt into a chatbot, then ask it to produce the banner, preference centre, blocking code, assumptions and testing checklist.
   4. Open the generated code in a staging copy of your website and replace every marked placeholder with confirmed service, cookie, category and contact information.
   5. Test the staging site in a private browser window by rejecting all non-essential cookies, accepting only selected categories, accepting all, withdrawing consent and revisiting the site; compare the browser storage and network requests with the choices made.
   6. Test the banner on a phone and with keyboard navigation and a screen reader, then fix focus order, labels, contrast, dismissal behaviour and the ability to change the choice later.
   7. Send the final wording, cookie inventory, data flows, code and test results to your data-protection solicitor or other suitably qualified professional for a UK GDPR and PECR review before publishing.

   Prompt

   Create a cookie consent banner for a UK business website using the details below. This is a technical drafting task, not professional advice. Do not invent cookies, trackers, vendors, purposes, retention periods or legal conclusions. If information is missing, mark it as [NEEDS CONFIRMATION].
   
   Website platform: [for example, WordPress, Shopify or custom site]
   Website URL or site description: [insert]
   Organisation and contact details: [insert]
   Known analytics, advertising, chat, video, payment and other third-party services: [list each one]
   Known cookies and local-storage items: [list them or say unknown]
   Scripts that currently load before consent: [list them or say unknown]
   Countries targeted by the website: [insert]
   Consent records or consent-management system already in use: [insert or none]
   
   Produce:
   1. Plain UK English banner wording with separate options to accept all, reject non-essential cookies and manage preferences.
   2. A preference centre with necessary, analytics, advertising and other relevant categories, making necessary cookies non-optional only where justified.
   3. Accessible HTML, CSS and JavaScript suitable for the stated platform, with placeholders clearly labelled.
   4. A method for preventing non-essential scripts from loading until the relevant consent is recorded, and for withdrawing consent later.
   5. A list of every assumption and missing fact.
   6. A testing checklist covering first visit, reject all, accept selected categories, withdraw consent, returning visits, mobile layout, keyboard use, screen readers, and script blocking.
   7. A separate list of points that a UK data-protection professional must check against current UK GDPR and PECR before publication.
   Do not claim that the result is legally compliant. Keep the code separate from the explanation and never put real personal data into the example.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.