top of page

What we check before your website goes live

Holly Hinton

Holly Hinton

22 October 2026

WEB DESIGN, SEO, STRATEGY

Checklist for your website before launch

Getting a new website live is a milestone. After the planning, content gathering, design decisions and feedback, you’re understandably keen to share it with the world. You’ve probably looked at the homepage so many times that you could describe it in your sleep.


But approving the design and being ready to launch are two different stages. A website can look polished while still making it difficult for people to understand your services, find the right information or get in touch. It can also contain unfinished settings that aren’t obvious when you’re reviewing colours and photographs.


At Web Goddess, the final review is part of delivering the project. It gives us a chance to step back from individual design decisions and assess whether the website does the job we agreed it needed to do.


Our internal checks cover plenty of detail, but what matters to you is what those checks achieve. Here are the questions behind them.


 

Can someone unfamiliar with your organisation understand it?

When you know your business or charity inside out, it’s surprisingly difficult to look at your website through a newcomer’s eyes. You understand your terminology, the differences between your services and which team handles what. A visitor arriving from a search result has none of that background.


They need enough information to recognise whether they’re in the right place. What do you offer? Who do you work with? What problem can you help them solve? If those answers are buried beneath an impressive-sounding introduction, people may leave before they reach the useful bit.


We review the messaging with that first visit in mind. For an established consultancy, this might mean making the distinction between coaching, training and consultancy clearer. For a charity, it might mean separating information for people seeking support from information for potential funders. Both audiences matter, but they arrive with different questions.


A clear website respects those differences. It gives people a sensible starting point and enough context to decide where to go next.


If you’re struggling to explain your services clearly, our guide to writing website content that people want to read is a useful starting point.


 

Does the navigation follow your visitors’ thinking?

Your website menu has a practical job: helping people find what they need. That sounds obvious until you encounter a menu organised around internal departments, unfamiliar programme names or a miscellaneous collection of pages added over several years.


We consider whether the navigation makes sense to the people using it. Are the labels understandable? Are related pages grouped logically? Can someone reach an important service without guessing which heading it sits beneath?


This is particularly important when an organisation serves several audiences. A growing business may work with different sectors, while a charity may need routes for service users, supporters, volunteers and professional referrers. The structure needs to accommodate that complexity without passing all the hard work to the visitor.


A bigger menu isn’t automatically more helpful. Neither is hiding everything behind three vague headings. The aim is to make useful choices visible at the point people need them.


 

Can people complete the actions that matter?

Most websites exist to help something happen. That could be an enquiry, a booking, a donation, a job application or someone finding the support they need. Before launch, we review the routes to those actions within the agreed project scope.


The wording matters as much as the button itself. “Book a call” creates a different expectation from “Email us”. “Apply now” suggests a process that someone should be able to start, rather than a page explaining that applications might open at some unspecified point.


Forms also need to make sense. We consider what information you need to collect, whether the instructions are clear and what happens after submission. Visitors should understand whether their message has been sent and what they can expect next.


These details can feel small when you’re looking at a whole website, but they sit at the point where someone decides to act. An unclear instruction or an unnecessarily awkward form can undo the work that brought them there.


 

Has the mobile experience had proper attention?

A website review often happens on a laptop or desktop computer, usually with a decent connection and time to concentrate. Your visitors may be using a phone between meetings, on public transport or while trying to do three other things.


The mobile version needs to support that reality. Text must remain comfortable to read, navigation needs to be manageable and important information should appear in a sensible order. A layout that works beautifully on a wide screen may need different decisions on a narrow one.


We review how the pages behave on smaller screens and whether the important tasks remain straightforward. That includes considering what happens when a visitor opens a menu, reads a service page or tries to complete an enquiry.


Mobile design involves judgement. It’s about deciding what deserves attention, how content should flow and what will help someone move forward without unnecessary effort.


We’ve explained more about mobile-first design and why it matters, including why checking the desktop version alone isn’t enough.


 

Do the pages have clear search foundations?

“SEO ready” is a reassuring phrase, but it needs an explanation. You should be able to ask what has been included and receive an answer you understand.


For us, reviewing the search foundations means considering whether the website’s pages have clear purposes and whether their structure and settings support those purposes. A page about leadership training should communicate that service clearly. Its search information should help a potential customer understand what they’ll find when they click.


We also review the relevant settings that support discovery and check for obvious unfinished work within the project scope. The detail varies depending on whether we’re building a new website, refreshing an existing one or moving content from another platform.


Those foundations are a starting point. They don’t guarantee a particular Google position, and they don’t replace an ongoing SEO strategy where one is needed. Our article on why SEO isn’t a one-and-done job explains what that involves. What they should give you is clarity about what has been done, what hasn’t and what further work may be worthwhile.


If a supplier describes your website as optimised, you’re entitled to ask what that means in practice. You shouldn’t need to accept the phrase on trust alone.


 

Have we protected what already works?

We’ve seen what happens when existing content is removed without a plan and shared the graphs in our article on whether deleting blog posts can harm SEO.


Refreshing an existing website involves responsibilities that don’t apply in quite the same way to a brand-new site. Your current pages may already receive visits, appear in search results or have links pointing to them from other websites.


That history deserves consideration before pages are renamed, removed or moved. An old page may look untidy and still be useful to your organisation. Understanding its purpose helps inform what should happen to it.


Where changes to existing pages and addresses form part of the project, we plan how those changes will be handled. The aim is to help people reach the right content and avoid creating unnecessary dead ends.


This is one reason strategy comes before design. Rebuilding a website starts with understanding what you have, what you need and what should be carried forward. A fresh appearance alone doesn’t answer those questions.


 

Can more people use the website comfortably?

People use websites in different ways. Some read every word; others scan headings. Some navigate with a keyboard or use assistive technology. Others may be viewing the site in difficult lighting, dealing with fatigue or struggling to understand unfamiliar language.


Accessibility considerations belong throughout the project. Clear content, meaningful links, readable design and sensible page structure all help make information easier to use.


We review accessibility within the agreed scope and explain where further assessment or specialist testing may be needed. Any accessibility statement should reflect what has actually been assessed, with realistic expectations about the work involved.


Images are one example: understanding what alt text does helps your team make more informed choices when adding content.


It’s also an ongoing responsibility. A carefully structured page can become harder to use after several rounds of updates, especially if new content is added without guidance. That makes the handover and the choices your team makes afterwards part of the picture too.

 


Does the content feel accurate and trustworthy?

A website can be technically functional and still leave people unsure about the organisation behind it. Conflicting contact details, outdated offers or descriptions that don’t match the service can create doubt at exactly the wrong moment.


We review content for consistency and obvious unfinished elements. That includes considering whether visitors can understand who they’re dealing with, whether claims are supported and whether the information gives them confidence to take the next step.


Your input is essential here. You know whether a qualification is current, a service is still available or a team member’s role has changed. Our job is to ask the right questions and help present that information clearly; yours is to confirm that it accurately represents your organisation.


Good content review is a shared responsibility. It needs time and attention from both sides, rather than a rushed request to “just check everything” five minutes before launch.


 

Can your team manage the finished website?

The website needs to work for the people responsible for it after launch. That might be a marketing team, a charity administrator, a business owner or us as your ongoing support provider.


We consider which updates you’ll need to make and how you’ll manage them. If your organisation publishes news, changes team information or adds projects regularly, those tasks should be reflected in how the website is structured and handed over.


Training should also relate to your actual responsibilities. Showing someone every available setting is rarely as useful as helping them confidently complete the tasks they’ll do each month.


Some clients want to manage their own content, while others prefer to hand it over. Both are reasonable choices. What matters is that you understand the arrangement, know where to get help and aren’t left afraid to touch a page in case the whole thing falls over.


 

Does it still support the original strategy?

Website projects generate ideas. A new feature sounds useful, another service needs a mention and someone spots something on a competitor’s site that they’d quite like too. Some additions improve the result. Others make it harder to see what the website is meant to achieve.


This is why we put website strategy before platform choice: the technology should support what your organisation needs to achieve.


Before launch, we return to the agreed goals. If the priority was to attract better-fit enquiries, are the services and next steps clear? If the aim was to reduce routine administration, have we made the relevant information easier to find? If a charity needed to explain its work more effectively, does the finished content help people understand its impact?


That review gives us a practical basis for decisions. It also helps distinguish work that belongs in the launch from ideas that would be better considered as a future phase.


A website is never completely finished in the sense that it will need no further changes. Your organisation will evolve, and the website should evolve with it. Launch means reaching an agreed, reviewed point where it is ready to start doing its job.


 

What should you ask before commissioning a website?

You don’t need our internal checklist to make an informed decision. You need a supplier who can explain their approach and take responsibility for the work they’ve agreed to deliver.


Ask how they’ll understand your organisation before designing the site, what their pre-launch review includes and what they mean by SEO setup. If you already have a website, ask how existing content and page changes will be handled. Find out what you’ll be able to manage afterwards and what support is available.


The answers should help you understand the service you’re buying. They should also make any limitations clear. No supplier knows everything, and recognising when specialist support is needed is part of doing a professional job.


For more help choosing a supplier, read our guide to finding the right web designer for your business.


 

At Web Goddess, we start with strategy because it gives the whole project a purpose. Design, content, functionality and the final review all follow from understanding what your organisation needs the website to achieve.


If you’re planning a new website or a substantial refresh, book a free 15-minute discovery call. We’ll ask about your organisation, talk through what you need and help you understand whether we’re the right team for the project.

 

RECENT POSTS

scrabble tiles spelling out SEO

What does ‘SEO ready’ really mean?

Checklist for your website before launch

What we check before your website goes live

Piggy bank with money being put into it for website design

Your charity doesn't need a volunteer web designer. It needs a digital budget.

seedlings growing

Your business has grown. Has your website caught up?

charity pot of cash showing coins saved for a charity

How Charities can save money on websites, software and digital tools

Tech we Love

Capsule.jpg
SE Ranking.jpg
FreeAgent.jpg
Proposify.jpg
Timetastic-Logo-Black-Small.png

About

Holly Hinton

Holly Hinton has been building websites for over 20 years – since way back in the days of Dreamweaver and FrontPage – and started Web Goddess in 2014 to combat all the bad advice small business owners received about web design and SEO. She loves sharing her knowledge and empowering those same business owners to take control of their online presence. Holly is a mum to teenage boys who love destroying the offence on an American Football field and loves crochet when she gets a chance.

Sign up to our newsletter

bottom of page