The Website Sign-Off Checklist Every Web Designer Should Use Before Launch

Click below if you’d prefer to listen to the audio version of this post:

There’s a particular kind of satisfaction that comes with finishing a website project.

The client is delighted. You’re proud of the work. And if you’re anything like me, you’ve spent so many hours looking at that website that you can practically see it when you close your eyes.

At that point, you’re ready to move on to the next project.

But before you do, there’s one final stage that can make the difference between a smooth handover and weeks of frustrating emails asking you to fix things that could have been avoided.

Having a consistent website sign-off process protects you, reassures your client, and leaves everyone with a positive experience.

After building hundreds of websites over the past 20 years, here’s the checklist I recommend every website designer follows before launching a client’s site.

Don’t rely on memory here. I *know* you’ve done it a tonne of times and can repeat the process in your sleep. But it’s when we’re so used to doing something that our brain shortcuts and we miss steps.

Whether you use Trello, ClickUp, Notion, Apple Notes or even a paper checklist, create a repeatable process that you follow for every project.

The checklist removes guesswork, reduces mistakes and gives you confidence that nothing has been forgotten. It also means that if a client comes back to you saying ‘you haven’t done this….’ You’ll be able to go back to the checklist and prove that you have.

If you don’t already have one, I’ve created my own website sign-off checklist that you can download and adapt for your own business.

If the website uses analytics, marketing pixels or tracking software, make sure you’ve installed a GDPR-compliant cookie notice.

It should:

• Link to the privacy policy
• Allow visitors to manage consent where required
• Cover any tracking tools installed on the website

Even if analytics will be connected after launch, it’s worth having this ready before the website goes live.

Before handing over any website, I always run a PageSpeed Insights report.

I’m looking for:

• Strong performance scores
• 100 for Accessibility
• 100 for Best Practices
• 100 for SEO where possible

If something needs tweaking, now is the perfect time to do it.

Once I’m happy, I save screenshots of the report.

Why?

Because they become evidence of the condition of the website on launch day.

They’re useful for:

• Showing clients the quality of your work
• Including inside your website user manual
• Protecting yourself if someone later claims the website was poorly built after other developers have worked on it

Those screenshots have proved incredibly valuable over the years.

It sounds obvious…until you forget.

I’ve launched websites before only for the client to ask:

“That’s lovely Holly… but how do I actually log in?” 🫣

Before launch:

• Create their administrator account.
• Send them the login details (or password reset link).
• Explain exactly where they log in.

Never assume they’ll know.

If the client has provided:

• Google Analytics
• Google Tag Manager
• Meta Pixel
• Email marketing scripts
• Other tracking codes

Install them before handover.

Your clients aren’t website developers. They won’t know where these scripts belong, so it’s part of providing the launch. It’s also helpful to have them there, so if the client comes back in a few months and says their website isn’t working, you’ll be able to help them look at their analytics and work out why.

Caching catches everyone out.

You might be seeing the latest version while your client is seeing something completely different.

Always check the live website using an incognito window.

This gives you a much more accurate picture of what visitors will actually experience. Trust me on this one. 20 years in the industry and one of my recent launches caught me out with cacheing.

Never assume your theme has handled everything perfectly.

Go through the website page by page on mobile.

Check:

• Layout
• Buttons
• Menus
• Forms
• Images
• Spacing
• Typography

Many clients look at their new website on their phone first. If something’s not aligned properly or a clickable element isn’t showing, or is too close to another clickable element, they’re going to lose faith in the rest of the website and they’ll be bugging you to fix it.

Before publishing, ask one simple question:

“Are you happy for me to launch the website?”

Encourage your client to check:

• Desktop
• Mobile
• Content
• Images
• Contact details

Then get their approval in writing.

This creates a clear point where the project moves from development into completion.

For me, this is also when I send the final invoice, making the end of the project crystal clear for everyone involved.

Having approval in writing is also really important because the clients who are the most delighted, and are brimming to tell everyone about their new site, are often the same people who come storming back with accusations once the site hasn’t delivered what they hoped. Having everything in writing helps to make things an open and shut case and keep things steady.

If you’re moving the website onto the client’s hosting, don’t assume everything has transferred perfectly.

Check:

• SSL certificate installed
• Website loads over HTTPS
• Caching is working correctly
• Third-party forms still load
• Integrations still function

Migration is often where small technical issues appear.

It’s much better for you to spot them first.

Never assume a form works simply because it looks right.

Submit test enquiries.

Confirm:

• Emails arrive.
• They arrive at the correct email address.
• Entries are saved in the database.
• Everything remains GDPR compliant.
• The reply to email field is set.

A contact form that fails can cost your client enquiries from day one, making you look bad because their website won’t be bringing in leads.

A confident client is a happier client.

Whether you provide:

• A live Zoom training session
• A personalised website manual
• Video tutorials
• Written guides

Make sure they know how to:

• Log in
• Edit text
• Replace images
• Update plugins (if they’re responsible)
• Find help when they need it

As a bare minimum. This reduces support requests and helps clients get far more value from their website. It also means that they won’t be disturbing you every time they want to make a change to their website.

One thing many designers forget is explaining where your responsibility for the website build ends.

Let your client know:

• How to request future updates
• Whether changes are billed as new work
• How maintenance works
• How to contact you

Having clear expectations will prevent awkward conversations later. Trust me on this one!

Once your client is happy with the finished website, don’t miss the opportunity to ask for a testimonial.

Make it easy by including direct links to places like:

• Google Reviews
• LinkedIn Recommendations

Most happy clients are willing to leave a review. But they may need reminding. Don’t be afraid to follow them up a week or so later.

One of the biggest benefits of having a documented sign-off process is that it protects both you and your client.

Sometimes another freelancer or SEO specialist will work on the website months later and suggest something wasn’t done correctly.

Having launch documentation, performance reports, client approval and a consistent checklist means you have evidence of exactly how the website performed when it left your hands.

More importantly, it gives your clients confidence that they’ve been looked after properly from start to finish.

And confidence is what creates repeat business and referrals.

If you’d like to adapt the exact process I use for my own website projects, you can download my free Website Sign-Off Checklist.

It’ll help you standardise your handovers, avoid those last-minute mistakes, and give every client a professional finish they’ll remember.