Free resource
Website Launch Checklist
25 things to verify before your website goes live. Covers content, design, technical SEO, performance, and legal compliance — with guidance on what to do if anything fails.
Used by Brambla on every website we launch. No sign-up required — just work through it.
Work through each section in order. Every item includes a brief explanation of why it matters and what to do if the check fails. Allow 2–3 hours for a thorough run-through on a site of 5–10 pages.
Section 1 of 5
Content & Copy
Proofread all text on every page
Why it matters
Spelling mistakes and grammatical errors undermine trust immediately. Visitors notice them — and so does Google, which may treat poor-quality copy as a signal of low-quality content.
If it fails
Read every page aloud: this catches errors your eyes skip over. Use Grammarly or a fresh pair of eyes for a final check. Pay particular attention to your homepage, About page, and any pages with pricing.
Check all contact details are correct
Why it matters
Incorrect phone numbers, email addresses, or physical addresses will lose you enquiries directly. If your contact details are wrong, visitors who want to reach you simply cannot.
If it fails
Update every instance site-wide — header, footer, contact page, and any embedded maps. If you have a Google Business Profile, verify it matches too.
Verify opening hours are accurate
Why it matters
Opening hours shown on a website create an expectation. If a customer arrives at your premises because your website says you're open and you're not, you've actively damaged the relationship.
If it fails
Update the hours and set a calendar reminder to revisit them seasonally or if your hours change. If your hours vary, consider removing them from the site and directing visitors to call.
Test all phone numbers and email links
Why it matters
Click-to-call links that don't work or mailto links that open the wrong address mean wasted visits. On mobile, a non-functioning phone link is a direct lost conversion.
If it fails
Test on a real mobile device, not just a desktop browser. Check every instance independently — footer, contact page, and any calls-to-action that include contact details.
Check all images have descriptive alt text
Why it matters
Alt text is used by screen readers for visually impaired users, and by search engines to understand what an image shows. Missing or generic alt text ("image1.jpg") is both an accessibility failure and an SEO miss.
If it fails
Add concise, descriptive alt text to every non-decorative image. Pure decorative images (dividers, backgrounds) can have empty alt text (`alt=""`). A sentence like "Web designer working at a desk in a Devon studio" is ideal.
Section 2 of 5
Design & UX
Verify the site is fully mobile responsive
Why it matters
Over 60% of UK web traffic is on mobile. Google also uses mobile-first indexing — meaning your mobile version is what Google primarily evaluates for ranking. A site that breaks on small screens is penalised both by users and by search.
If it fails
Use Chrome DevTools (right-click → Inspect → toggle device toolbar) to test at 375px, 414px, and 768px widths. Look for text overflow, images that exceed the viewport, and buttons that are too small to tap.
Test on a real iPhone and a real Android device
Why it matters
Browser simulators are useful but imperfect. Real devices catch issues like iOS Safari rendering quirks, font rendering differences, and touch target sizes that only show up on physical hardware.
If it fails
Test on at least two real devices — an iPhone (Safari) and an Android phone (Chrome). If you only have one device, ask a friend or colleague to test the other. Focus on the homepage, contact page, and any forms.
Test every button and internal link
Why it matters
Broken internal links send users to error pages. Buttons that do nothing (missing `href` or broken JavaScript) prevent visitors from taking the actions you want them to take.
If it fails
Click every button and link on every page. Use a tool like Screaming Frog or Google Search Console (after launch) to scan for broken links systematically.
Confirm the logo displays correctly on all screen sizes
Why it matters
Your logo is the primary brand identifier. If it renders blurry, oversized, or invisible against certain backgrounds, it signals an unprofessional build to visitors.
If it fails
Ensure your logo is served as SVG (infinitely scalable) or a high-resolution PNG with a transparent background. Check it on both light and dark backgrounds and at mobile widths.
Confirm a custom 404 page exists
Why it matters
When visitors reach a page that does not exist — through an old link, a mistyped URL, or a broken redirect — a branded 404 page can redirect them to useful content and retain the visit. A generic server error page loses them entirely.
If it fails
Create a custom 404 page that includes your navigation, a brief explanation, and links to your homepage and key service pages. It doesn't need to be elaborate — just useful.
Section 3 of 5
Technical SEO
Verify every page has a unique title tag
Why it matters
Title tags are the most important on-page SEO element. Duplicate titles tell Google that two pages cover the same thing — it can't decide which to rank and may rank neither. Each page should describe its specific content in 50–60 characters.
If it fails
Audit your title tags in Screaming Frog or by viewing page source on each page. Write unique, descriptive titles for every page. Format: "Primary Keyword | Brand Name".
Check all pages have a written meta description
Why it matters
Meta descriptions do not directly affect rankings, but they appear in search results and directly affect click-through rate. A blank description means Google writes one for you — usually badly.
If it fails
Write a 140–160 character meta description for every page. Include a compelling reason to click and, where appropriate, a keyword. Avoid duplicating descriptions across pages.
Confirm sitemap.xml is accessible
Why it matters
A sitemap tells Google which pages exist on your site and when they were last updated. Without one, Google discovers your pages through crawling alone — slower and less reliable, especially for new sites.
If it fails
Visit `yourdomain.co.uk/sitemap.xml` in a browser. You should see an XML file listing all your pages. If it returns a 404, generate one through your CMS or manually. Submit it in Google Search Console.
Check robots.txt is correctly configured
Why it matters
Many development environments set robots.txt to block all crawlers to keep the work-in-progress out of search results. If you forget to update it before launch, Google cannot index your new site.
If it fails
Visit `yourdomain.co.uk/robots.txt`. Check that it does not contain `Disallow: /` for Googlebot. The production robots.txt should allow crawling and include a `Sitemap:` directive pointing to your sitemap URL.
Connect the site to Google Search Console
Why it matters
Google Search Console is the direct line between your website and Google's search index. It lets you submit your sitemap, monitor indexing status, spot crawl errors, and track which queries your site appears for. Not connecting it is like launching a shop and never checking whether customers can find the door.
If it fails
Add your site to Google Search Console (search.google.com/search-console), verify ownership, and submit your sitemap. Set up email alerts for coverage issues.
Section 4 of 5
Performance
Page load time under 3 seconds on mobile
Why it matters
53% of mobile visitors abandon a page that takes more than 3 seconds to load. Google's Core Web Vitals also use load speed as a direct ranking factor. A slow site loses both traffic and conversions.
If it fails
Test with Google PageSpeed Insights (pagespeed.web.dev). Common fixes: compress and convert images to WebP, remove unused JavaScript, upgrade to faster hosting. If you score below 70 on mobile, treat it as a priority fix before launch.
All images are optimised (compressed and correct format)
Why it matters
Images are typically responsible for 60–80% of a page's file size. An unoptimised JPEG uploaded straight from a camera can be 5–10MB. The same image, properly compressed and served as WebP, can be under 100KB — a 50x improvement in load time.
If it fails
Run images through Squoosh, TinyPNG, or ShortPixel. Convert to WebP format where your CMS supports it. Aim for under 200KB per image on standard pages, under 500KB for hero images. Use `width` and `height` attributes to prevent layout shift.
No broken links (internal or external)
Why it matters
Broken links signal neglect to both visitors and search crawlers. Internal 404s waste crawl budget and frustrate users. External links pointing to discontinued pages reflect poorly on the quality of your site.
If it fails
Use Screaming Frog (free up to 500 URLs) or Broken Link Checker to scan for 404 errors. Fix internal broken links at source. For broken external links, either update to a working URL or remove the link.
SSL certificate is active (site loads on HTTPS)
Why it matters
An SSL certificate encrypts data between the visitor's browser and your server. Without it, browsers show a "Not Secure" warning — which immediately destroys visitor trust. Google also uses HTTPS as a ranking signal.
If it fails
Most hosting providers include SSL for free via Let's Encrypt. Contact your hosting provider to enable it if it's not active. Ensure all HTTP URLs redirect to HTTPS and that there are no mixed-content warnings (HTTP assets on an HTTPS page).
Redirects from old URLs are working (if relaunching)
Why it matters
If you're replacing an existing website, any pages that existed at specific URLs carry SEO value — links, rankings, and history attached to those URLs. Without 301 redirects, that value evaporates overnight when the old URLs return 404 errors.
If it fails
Map every old URL to its closest equivalent on the new site. Set up 301 (permanent) redirects — not 302 (temporary). Test each redirect by visiting the old URL in a browser and confirming it lands on the correct new page.
Section 5 of 5
Legal & Compliance
Privacy policy page is live and linked in the footer
Why it matters
Under UK GDPR and the Data Protection Act 2018, any website that collects personal data — including contact forms, analytics, and newsletter sign-ups — must have a privacy policy. It must be accessible from every page, clearly written, and explain what data you collect and how you use it.
If it fails
If you do not have one, use a privacy policy generator (Termly, iubenda, or similar) and customise it for your specific data processing. Add a link in your footer. Review it with a solicitor if you handle sensitive categories of data.
Cookie consent banner is implemented and functional
Why it matters
UK PECR (Privacy and Electronic Communications Regulations) requires informed consent before setting non-essential cookies. Analytics tools like Google Analytics, Facebook Pixel, and most third-party embeds use non-essential cookies. A cookie banner that doesn't actually block cookies before consent is non-compliant.
If it fails
Install a compliant consent management solution — either an off-the-shelf platform (CookieYes, Cookiebot) or a custom Consent Mode v2 implementation. Either way, non-essential cookies must be blocked until consent is given — not just disclosed. Test by clearing cookies, reloading the page, and checking your browser's cookie store before accepting.
GDPR data handling is in place for form submissions
Why it matters
Every contact form submission involves processing personal data. Under UK GDPR, you need a lawful basis for processing (usually legitimate interest or consent), you must not retain data longer than necessary, and individuals have the right to request deletion of their data.
If it fails
Ensure your contact form includes a brief privacy notice (a sentence linking to your policy is sufficient for most cases). Confirm form data is stored securely and that you have a process for handling data subject access requests or deletion requests.
Terms of service page exists (if applicable)
Why it matters
If your website sells products, offers services with specific conditions, or allows user-generated content, you need terms of service (or terms and conditions). These set out the rules of engagement and provide legal protection if disputes arise.
If it fails
Not all sites need full terms of service — a brochure-only website with no transactions or user accounts can often rely on the privacy policy alone. If you sell online, take bookings, or offer subscription services, engage a solicitor to draft appropriate terms.
Basic accessibility requirements are met (WCAG 2.1 AA)
Why it matters
In the UK, the Equality Act 2010 requires websites to be reasonably accessible to people with disabilities. Beyond legal obligation, accessible sites reach more users — and many accessibility improvements also benefit SEO.
If it fails
Run your site through the WAVE accessibility checker (wave.webaim.org). Common issues: missing alt text on images, insufficient colour contrast, missing form labels, and links with non-descriptive text ("click here"). Fix critical and serious errors before launch.
Don't want to do this yourself?
That's what we do.
Every Brambla website goes through this checklist before launch — and then our SiteCare plans keep it secure, fast, and backed up on an ongoing basis. If your current site has issues, our Website Audit will find them.
Frequently Asked Questions
Common questions about website launches and what to do when checks fail.
Useful Next Steps
Related pages that are worth reading before or after your launch.
ARE YOU READY?
Let's create something extraordinary together. Get in touch and let's talk about your next project.
START A PROJECT