Skip to content
← Blog

Technical · 5 min read

A website launch checklist for agencies

A practical pre-launch checklist for agency client sites: access, forms, redirects, speed, search settings, analytics, backups and the first 48 hours.

November 4, 2026

A website launch checklist for agencies

Key takeaways

  • Most launch problems are not design problems; they are forms that do not send, redirects that were never set and a site still hidden from search.
  • Work through access, content, forms, redirects, speed, search settings, analytics and backups before the switch.
  • Plan the first 48 hours after launch as part of the project, not as an afterthought.
  • Keep a written sign-off so nobody argues later about what was checked.

Launch day is when small oversights become public. A contact form that goes nowhere, a site that still tells search engines to stay away, old URLs that now return errors: none of these are hard to fix, and all of them are easy to miss. This is the checklist we would want an agency to work through before pressing the button.

Before you start

Make sure you have access to the domain, hosting and the site’s admin, and know who will own them after launch. If the brief did not cover this, our guide to briefing a white label build shows what to settle at the start.

Two women talking and looking at a laptop screen together
A final walk-through with a second pair of eyes catches what the builder has stopped seeing.

Content and design

  1. All placeholder text and images are replaced or removed.
  2. Spelling, phone numbers, addresses and opening hours are checked against what the client sent.
  3. The site is checked on a phone, a tablet and a desktop, and in the main browsers.
  4. Links go where they should; no link points at a staging address.

Forms and integrations

  1. Every form is submitted for real and arrives in the right inbox.
  2. Confirmation or thank-you messages display, and any automatic reply is sent.
  3. Booking, payment, chat and CRM connections are tested end to end.
Tip: Ask the client to submit the contact form themselves and confirm they receive it. It proves the inbox, spam folder and routing in one step.

Redirects and URLs

  1. If the site replaces an old one, every important old URL redirects to its new equivalent. Google explains how in its guide to 301 redirects and for site moves.
  2. The custom 404 page is helpful and links back to key pages.

Search settings

  1. The site is not set to discourage search engines, and no leftover staging password or noindex remains. This is the most common launch mistake.
  2. Every page has a unique title and description; see Google’s notes on title links and snippets.
  3. A sitemap exists and is submitted; see Google’s sitemap overview.
  4. The robots file does not block anything it should not; see Google’s robots.txt introduction.
Watch out: Double-check search visibility after the final DNS or domain change, not only on staging. Settings can change when a site moves.

Speed and quality

  1. Key pages are tested on mobile with PageSpeed Insights and the numbers are saved as a baseline.
  2. Images are sized and compressed, and fonts load without layout jumps.

Analytics and tracking

  1. Analytics and Search Console are connected to the live domain.
  2. Conversions, such as form submissions, are being recorded.

Backups and ownership

  1. A full backup exists from the moment before launch, and a restore has been tested. See WordPress’s backup guide for what to include.
  2. Logins are handed to the right people, unused accounts are removed and licences are in the client’s or agency’s name.
  3. The client has a short guide on how to edit the site and who to contact.

The first 48 hours

Plan to check the site again the next day: forms, search settings, errors in Search Console and anything the client reports. Agree who is on call and how quickly changes will be made. After that, a care plan with a clear scope covers ongoing maintenance, and for stores our Shopify handoff checklist adds the store-specific items.

Laptop screen showing a video call with a houseplant beside it
A short post-launch call confirms the client is happy and the issue list is clear.

A launch sign-off table

Area Owner Done
Content and design Agency
Forms and integrations Studio and agency
Redirects and URLs Studio
Search settings Studio
Speed baseline Studio
Analytics Agency
Backups and access Studio and agency
Client guide Agency

How we launch

We build WordPress and custom-coded Shopify sites under your brand, let you review the build before your client does and close our access at launch where the client owns the account. See how we work, white label WordPress development and white label Shopify development, or talk to us about your next launch.

Frequently asked questions

What is the most common launch mistake?
Leaving the site hidden from search engines, or forgetting redirects from the old URLs.
Should we launch on a Friday?
Avoid it unless someone will be available over the weekend. Early in the week gives you time to fix issues.
How long should pre-launch checking take?
It depends on the site; allow real time in the schedule instead of squeezing it in on the day.
Who signs off?
The agency, with the client’s approval of content and design. Keep it in writing.

Sources and further reading

  1. Google: 301 redirects — redirecting old URLs.
  2. Google: site moves with URL changes — protecting search visibility.
  3. Google: sitemaps overview — submitting a sitemap.
  4. Google: robots.txt introduction — what robots rules do.
  5. PageSpeed Insights — testing speed before and after launch.
  6. WordPress: backups — what a complete backup includes.

Ready to talk?

Looking for a white label web partner you can actually rely on?