Skip to content
YOUR WEB PAGE

Newsletter

A website launch checklist

Twelve checks to run before pointing DNS at a new site, from form delivery and redirects to SPF records and a 404 page.

October 28, 20265 min readLaunch · QA · Operations

Launch mistakes are almost always the same ones: a form still pointed at a test inbox, a redirect missing for the old pricing page, or an SSL warning on the www version. An hour of checks prevents all of it.

This is the list we work through on a staging copy before touching DNS.

Content and links

  • Proofread on a phone, not just a laptop. Check the phone number, address, hours and business name on every template.
  • Click every navigation item, footer link, card and button. Watch for 404s and links that open in the same tab when they should not.
  • Check the 404 page itself. It should offer the menu and a way back, not a default server error.
  • Confirm the favicon and social share image are the new ones, not last year’s logo.

Forms and email

  • Submit every form and confirm the email arrives in the real inbox, not spam. Check the reply-to address too.
  • Test validation: empty required fields, a malformed email, and the success message.
  • Verify SPF and DKIM records before launch. Missing records are the usual reason enquiry emails land in spam.
  • If the form sends an auto-reply, read it as a customer would.

Technical checks

  • Test at 360 px, 768 px and 1440 px. Look for sideways scrolling and clipped headings.
  • Tab through the menu, forms and accordions. Focus should stay visible and Escape should close any open menu.
  • Check page titles, meta descriptions, canonical URLs and the sitemap. Every page should have a unique title.
  • Map 301 redirects from every old URL that still gets traffic, including printed QR codes and old campaign links.
  • Confirm HTTPS on both the apex domain and www, with no mixed-content warnings.

The switch itself

Lower DNS TTL to 300 seconds a day before the switch so changes propagate quickly. Make the change in the morning, mid-week, when you can watch it. Then test the live site from a phone on mobile data, outside your office network.

Keep the old site archived for 30 days and leave the redirects in place permanently. Submit the sitemap in Search Console and check for crawl errors a week later.

Start a conversation

Have a project in mind?

Tell us what you are building. We will come back with questions, ideas and a clear plan.