A website launch checklist, from final week to first week live
Launch day problems are rarely exotic. They are a contact form that emails nobody, an old URL that now returns 404, or a staging setting left switched on. Work through this list in order and tick each line.
One week before
Content
- Proofread every page out loud, including the footer, error page and confirmation messages.
- Replace all placeholder text and sample images. Search the code for “lorem”, “TODO” and “test”.
- Check that phone numbers, email addresses and opening hours are current.
- Confirm you have the rights to every image, font and icon set.
Old site, if this is a redesign
- Export a list of every URL on the old site.
- Map each old URL to its new equivalent in a two-column sheet.
- Prepare permanent (301 or 308) redirects for every row. Old URLs with links pointing at them matter most.
Two days before
Things that do something
- Submit every form with real-looking test data and confirm the message arrives where it should.
- Test any checkout, booking or sign-up flow end to end, including the failure messages.
- Click every link in the main menu and footer on a phone and on a desktop.
- Try the site in at least two different browsers.
Legal and trust
- A privacy policy that matches what the site actually collects.
- A cookie notice if your site and your audience’s location require one.
- Clear contact details so visitors can reach a real person.
Launch day
- Take a full backup of the old site and its database before switching anything.
- Lower the DNS TTL a day ahead if you are changing hosts, so the switch spreads faster.
- Point the domain, then confirm HTTPS works on both the www and bare versions and that one redirects to the other.
- Remove any staging password,
noindextag orDisallow: /line. - Spot-check ten old URLs from your redirect map.
- Submit the new sitemap in your webmaster tools.
First week live
- Watch server logs or your error report for 404s and fix the missing redirects they reveal.
- Make sure an external uptime check is running and its alerts reach someone.
- Confirm that scheduled backups ran and that you can restore one.
- Collect feedback from a few people who were not involved in building the site; they spot what you no longer see.
Sample rollback note
Write this before launch, so nobody has to think under pressure:
If the new site has a fault we cannot fix within one hour, we point DNS back to the old host, restore the backup taken on launch morning and post a short notice on the home page. The person who decides is the project lead; the person who does it is whoever holds the hosting login.
Common mistakes
- Launching on a Friday afternoon with nobody available over the weekend.
- Forgetting email DNS records when moving name servers, so mail stops arriving.
- Letting the old hosting account lapse before every file has been checked.
Questions
Will a redesign hurt my search traffic?
It can dip while search engines process the change. Complete redirects, unchanged or improved content and no accidental noindex keep the dip small.
Is a soft launch worth it?
Often yes. Opening the site quietly to a small group first finds problems before you announce it widely.