In this article 8 sections
On Monday the site looks finished. By Friday the contact form is sending leads to a developer’s test inbox, the noindex tag from staging has gone live with everything else, and the client finds a typo in the footer on their phone at nine in the evening.
None of that is a design problem. It is a website launch checklist problem: the last week is full of small checks that sit between design, development and the client, and nobody owns them. This post is the checklist we would hand a project manager on the Monday of launch week, plus a way to run the last client review round without drowning in email.
What a website launch checklist is (and what it is not)
A launch checklist is a list of checks where each line has a yes/no answer and one owner. You run it twice: on the production candidate (a staging copy that matches production) and again on the live domain in the first hour after the switch.
It is not:
- A design review. “Could the hero be bigger?” is a new request, not a launch check. It goes on a post-launch list.
- A full audit. Accessibility audits, security tests and legal reviews are separate jobs. The checklist catches the basics that break on launch day.
- A document for the client to fill in. The technical lines stay with your team.
If a line cannot be answered with yes or no, rewrite it. “Check forms” is not a line. “Every form on the live domain delivers to the client’s inbox” is.
Why the last week goes wrong
Three things tend to happen at once.
- The team has moved on. The designer is on the next pitch, the developer on another client’s bug. Re-testing gets skipped.
- The risky items have no owner. Form e-mails, DNS records, cookie consent and redirects are not in anyone’s job title. Everyone assumes someone else checked them.
- The client’s review arrives late and scattered. Three people send notes in separate emails, with screenshots of the wrong page. Whatever lands in the last 48 hours gets fixed in a rush and never re-checked.
Content, forms and redirects
Content
- Search the CMS and templates for placeholder text:
lorem,ipsum,TODO,test,xxx,[client name]. - Contact details match the client’s current ones: phone, e-mail, address, opening hours. Phone numbers are
tel:links. - No links or image paths still point at the staging domain. On WordPress, run a search-replace on the database after migration, not just on the settings screen.
- Final photos only: no stock watermarks, no 5 MB uploads straight from a camera.
- Favicon, page titles in the browser tab and a social share image are in place.
Forms
- Submit every form on the live domain, not only on staging. Check who receives it (the client’s inbox, not your test address), the subject line, and that reply-to is the visitor’s address.
- Deliverability: mail sent straight from the web server often lands in spam. Send through an SMTP or transactional e-mail provider, with SPF and DKIM set for the domain.
- A thank-you message or page appears, and your conversion event fires on it.
- Spam protection is on, required fields are marked, and error messages are readable.
- If the form feeds a CRM or a newsletter list, a test entry arrives there. Delete the test entries afterwards.
Redirects
- Replacing an old site? Export its URLs (old sitemap, top pages from analytics, Search Console), map each to a new URL and set 301 redirects. Test the top 20 by hand.
- One canonical host:
httpgoes tohttps,wwwand the bare domain resolve to one version, in a single hop. - Trailing slashes behave the same way across the site.
Consent, legal pages and analytics
- Cookie consent. If the site uses non-essential cookies (analytics, ads, embedded video, chat), EU rules require consent before they are set. Test it: open the site in a private window, open the Network tab and confirm no analytics requests go out before you click accept.
- Rejecting actually keeps tracking off, the choice is remembered, and there is a link (usually in the footer) to change it later.
- The privacy policy lists the tools the site really uses: analytics, form processing, chat, maps, embedded fonts. A tool added in week eleven needs to be in it.
- Company details, terms for online shops, and any legally required business information are on the site. Your client’s lawyer decides the wording, you make sure the pages exist and are linked.
- Analytics sits in the client’s own account, not your agency’s. Conversions are set up, internal traffic is filtered, and a test visit shows in the real-time report.
- Search Console is verified for the live domain, ready for the sitemap after launch.
Speed, accessibility, SEO and the 404 page
Speed
Run PageSpeed Insights or Lighthouse on mobile for the home page and two main templates. Google’s “good” thresholds for Core Web Vitals are LCP up to 2.5 s, INP up to 200 ms and CLS up to 0.1. Lab tests show LCP and CLS; INP needs real users, so click through the heaviest interactions yourself (menus, filters, sliders).
The usual last-week culprits: an uncompressed hero image, a slider plugin, fonts loaded from three places, and a chat widget loading on every page.
Accessibility basics
This is not an audit, it is the minimum that breaks visibly:
- You can reach the menu, every link and every form field with the keyboard, and the focus outline is visible.
- Text on top of photos has enough contrast.
- Form fields have labels, meaningful images have alt text, headings go in order.
- The page language is set in
<html lang>.
For some businesses selling to consumers in the EU, the European Accessibility Act has applied since June 2025, so ask whether it covers your client. For a fuller process, see our accessibility workflow.
SEO meta
- Unique title and meta description on every page, one H1.
- No
noindexleft over from staging in the robots meta tag or the SEO plugin settings, and noDisallow: /inrobots.txt. This is the most common launch-week miss, and it quietly removes the site from search. - Canonical URLs point to the live domain, not to staging.
- The XML sitemap loads on the live domain.
The 404 page
A custom 404 page exists and, just as important, returns HTTP status 404. Many setups show a nice “page not found” page with status 200, which search engines treat as a real, thin page (a soft 404). Check it with curl -I https://example.com/this-page-does-not-exist or in the Network tab.
Launch day: backups, DNS and SSL
- Backups: automatic backups are set up on production, stored off the server, and one restore has been tested. Take a snapshot just before the switch.
- DNS: lower the TTL of the records you will change (300 seconds is common) a day ahead. Write down every current record before touching anything. Change only what serves the website (A, AAAA or CNAME). Leave MX, SPF, DKIM and verification TXT records alone: e-mail breaks quietly when someone moves a whole DNS zone and forgets them.
- SSL: the certificate covers the bare domain and
www, the browser shows no mixed-content warnings (images or scripts still loaded overhttp). - After the switch, on the live domain: submit every form again, load a missing URL to check the 404, watch the analytics real-time report, test the top redirects, submit the sitemap.
- Monitoring: an uptime check on the home page, and a named person who gets the alert.
How to run the last client review round
The client’s last round covers what only they can judge: their content, prices, phone number and flows. Run it like this.
- Freeze the scope in writing. “This round is for errors and missing content. New ideas go on the post-launch list.” Send it before the round starts, not after the first new idea arrives.
- Give reports one place to land. Put a feedback widget on staging so the client clicks the element they mean instead of describing it. With Zorko each report carries the page URL, browser, device, window size, a pin on the exact spot and the page’s recent console errors, and the widget can stay hidden so only the people you send the link to see it. If some reviewers will still write by hand, give them a bug report template.
- Timebox it. A 48-hour window, named reviewers, and a page list per person: marketing reads the copy, the owner checks contact details and prices, someone goes through the site on their own phone.
- Triage once a day with the table below. Blockers get fixed before launch, the rest gets a date.
- Close the loop. Mark reports as done, so the client sees what changed without asking. Re-check blockers on the live domain after the switch.
- Get sign-off in writing, referring to the list of reports, not to “the site”.
Launch blocker or after launch?
| Found in the last round | Blocks launch? | Why |
|---|---|---|
| Form delivers to the wrong inbox | Yes | Leads are lost from day one |
noindex from staging still on | Yes | Pages drop out of search |
| No redirect for the old site’s top URLs | Yes | Lost traffic and backlinks |
| Analytics runs before consent | Yes | Legal risk for the client |
| Wrong phone number or price | Yes | Customers act on it |
| Typo on an inner page | No, fix in week one | Low impact, quick to fix |
| Hero image a bit heavy | Only if mobile LCP is poor | Measure, then decide |
| ”Could the button be orange?” | No | New request: post-launch list or change request |
An example with numbers
Say a four-person agency is launching a 12-page site, and three people on the client side review it by email. Thirty notes arrive over five days in eleven emails. For each one, the project manager finds the page, works out which element is meant, checks the browser and writes a task. At 10 minutes a note, that is 5 hours before anyone fixes anything.
Run the same round through a widget on staging with a 48-hour window, and the thirty notes arrive as thirty separate reports, each pinned to its element with the URL and browser attached. At maybe 3 minutes a report to read, triage and assign: about 1.5 hours. The numbers are an illustration; put in your own and the gap is usually still there.
If you are still choosing a tool for this round, here is how agencies choose a website feedback tool.
If your last review round still runs through email, put Zorko on staging for your next launch: one script tag, no account for the client. Start free, no credit card needed.
FAQ
When should we start the launch checklist?
At the start of the last week, on staging. Prepare DNS and backups two to three days before the switch, and repeat the live-domain part in the first hour after launch.
Who should own the checklist?
One person, usually the project manager, owns the list. Each line has its own owner, so “someone checked it” always has a name.
Should the client go through the checklist too?
No. Give the client a short task list for the review round: content, prices, contact details, their key flows on their own phone. DNS, redirects, consent and status codes stay with the team.
What if the client keeps sending new ideas in the last round?
Thank them, put each idea on a post-launch list with a date, and keep the round for errors. If the ideas add real work, they become a change request after launch.
Is a feedback tool worth it for one launch?
For a small site, Zorko’s Free plan (1 project, 10 feedback reports a month) may cover the last round. If several people review or you run several projects, Pro is $19 a month with unlimited projects, feedback and teammates at one flat price.