United Kingdom version. Written for UK websites: PECR consent before non-essential cookies are set, UK GDPR privacy information, required trading information, cancellation rights, and accessibility duties. US version
Website Launch Checklist (UK)
PECR means non-essential cookies need consent before they are set, and UK traders must show specific information. Then the accessibility duty if public sector.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the Website Launch Checklist?
The UK legal layer on a website launch is more specific than a generic checklist suggests, and the sharpest rule is about cookies. Under PECR, non-essential cookies and similar technologies require consent before they are set, which means analytics and advertising scripts must not run on first load while a banner is still being considered. A banner that sets cookies on arrival is the most common compliance failure on UK sites.
Consent also has to be as easy to refuse as to accept, which rules out a prominent accept button with a reject option buried a click deeper. The Information Commissioner has been explicit about this pattern.
Separately, a UK business trading online must display specific information: the legal name, a geographic address, contact details, and for a limited company the registered number and registered office, plus VAT number where registered. A site with only a contact form and a first name is not compliant.
- Built on PECR consent before non-essential cookies are set
- Covers the trading information UK businesses must display
- Includes the 14-day cancellation right and the cost of not disclosing it
- Notes public sector accessibility regulations and the Equality Act duty
- Tick, reword and delete items, then export as a Google Form, PDF, CSV or Markdown
Updated
How to use the Website Launch Checklist
- Block non-essential cookies and scripts until consent is given, and make refusing as easy as accepting.
- Publish privacy information that matches what the site actually does, including lawful bases and the ICO complaint route.
- Display the required trading information: legal name, address, company number, registered office and VAT number.
- For consumer sales, provide pre-contract information and the 14-day cancellation rights correctly.
- Put processing agreements in place with every supplier, enforce HTTPS, and test a restore from backup.
Worked examples
Analytics loads before consent
Input
Cookie section, Essentials only
Output
Scripts blocked until consent is recorded
PECR requires consent before non-essential cookies are set, so a banner that appears while analytics already runs is the most common UK compliance failure.
Accept button prominent, reject buried
Input
Consent items
Output
Reject made equally easy
Consent must be as easy to refuse as to give, and the regulator has been explicit that asymmetric designs do not produce valid consent.
Contact page shows only a form
Input
Trading items
Output
Legal name, address, company number and VAT added
A UK business trading online must display specific identifying information, and a company must include its registered number and registered office.
Selling to consumers with no cancellation notice
Input
Consumer items
Output
Fourteen-day right explained in the pre-contract information
Failing to inform a consumer of the cancellation right extends the period substantially, which turns an omission into a long-tail liability.
Background and insight
Consumer rights add obligations for anything sold to consumers: pre-contract information, a clear total price including delivery, and the 14-day right to cancel most distance contracts with its own information requirements, since failing to tell the consumer about the right extends it substantially. Terms that try to exclude statutory rights are unenforceable rather than merely unfair.
Privacy information under UK GDPR has to be accessible and specific: what you collect, the purposes, the lawful basis for each, retention, recipients, international transfers and the rights available, including how to complain to the ICO. A generic template that does not match what the site actually does is worse than useless because it is evidence of what you claimed.
Accessibility is a legal duty for public sector bodies in the UK, requiring conformance with the accessibility standard and a published accessibility statement, with specific content. For private businesses the Equality Act duty not to discriminate still applies, so inaccessibility carries risk even without the regulations.
On the technical side the launch items that bite in the UK context are a cookie solution that genuinely blocks scripts before consent rather than only hiding a banner, consent records that can be evidenced, server location and transfer mechanisms where personal data leaves the UK, and a data processing agreement with every supplier that touches personal data including the host and the analytics provider.
Email marketing has its own rules under PECR: consent is generally required for unsolicited marketing to individuals, with the soft opt-in available for existing customers on similar products, and every message needs an identifiable sender and a working unsubscribe. Buying a list of consumer email addresses is almost never lawful here.
Standard launch engineering still matters and should not be displaced by compliance: backups tested by restoring rather than by existing, monitoring that alerts a person, a staging environment, TLS with renewal automated, a 404 and 500 page that work, analytics configured to respect consent, and a rollback plan.
Finally the content security headers and the basics a UK regulator would expect of a site handling personal data: a content security policy, HTTPS enforced, secure cookie attributes, and a documented process for a data breach with the 72-hour clock in mind.
Common use cases
Launching a UK site
Cookies, privacy and trading information.
Selling to consumers
Pre-contract information and cancellation rights.
Public sector sites
The accessibility duty and statement.
Technical readiness
Backups, monitoring and a tested rollback.
Tips and limitations
- Block the scripts, not just the banner. Consent comes before cookies.
- Reject must be as easy as accept.
- Show the legal name, address, company number and VAT number.
- Not telling consumers about the 14-day right extends it.
- Test a restore. A backup you have never restored is a hope.
Sources and further reading
- Data protection and your business, UK Government. UK GDPR duties, privacy information and breach reporting
- Consumer rights, UK Government. Distance selling, cancellation rights and unfair terms
- Make your website or app accessible and publish an accessibility statement, UK Government. Public sector accessibility regulations and statements
- Information Commissioner’s Office, UK Government. PECR cookie and marketing rules and enforcement
Frequently asked questions
What does UK law require of cookie banners?
Under PECR, non-essential cookies and similar technologies require consent before they are set, so analytics and advertising must not run on first load. Consent must also be as easy to refuse as to accept, which rules out a buried reject option.
What information must a UK business show on its website?
The legal name, a geographic address and contact details, and for a limited company the registered number and registered office, plus a VAT number where registered. A contact form alone does not satisfy it.
What are my obligations when selling to consumers online?
Clear pre-contract information including the total price with delivery, and the 14-day right to cancel most distance contracts together with the required information about it. Failing to inform the consumer of that right extends the cancellation period substantially.
Is accessibility a legal requirement?
For public sector bodies in the UK, yes, with a conformance requirement and a published accessibility statement with prescribed content. For private businesses the Equality Act duty not to discriminate still applies, so inaccessibility carries legal risk regardless.
Can I email a purchased list of addresses?
Almost never lawfully to individuals. PECR generally requires consent for unsolicited marketing, with a soft opt-in for existing customers on similar products, and every message needs an identifiable sender and a working unsubscribe.
What do I need in place with suppliers?
A data processing agreement with every supplier that touches personal data, including the host and the analytics provider, plus a transfer mechanism and assessment where data leaves the UK. These are contractual obligations rather than optional diligence.
Is there an in-depth guide to the Website Launch Checklist?
Yes. “Why Checklists Work, and How to Use One Properly” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.