Your developer sends a preview and asks for approval. The pages look finished, but what are you supposed to check? This website launch acceptance checklist turns that decision into a short walkthrough of the things customers need to do. You don't need to inspect the code. You do need to know which tasks work, which issues remain and who is responsible for the launch decision.
Take the Customer's Route Through the Site
Start on an important service page rather than assuming everyone enters through the homepage. Read it on a phone. Find the service, look for the phone number and make a labeled test inquiry through the normal route, with the team's agreement.
Try one imperfect submission too. Leave out a required answer, read the error and correct it. Confirm that the form preserves the other information and explains what needs fixing. Then ask the person receiving the inquiry to confirm it arrived with the details needed to reply.
A screenshot can show that a form looks right. Completing that route tells you more about whether the business can use it.
Check the Details You Know Better Than the Developer
Read names, services, contact information and hours against the business's records. Look for old logos, placeholder copy and services you no longer offer. Have the responsible person check claims about credentials and customer work.
Check downloads and current advertising links as well. A customer may arrive through an old quote link or a saved PDF address. If this is a replacement site, ask the developer how important old URLs are being handled.
Google's site-move guidance calls for relevant permanent redirects when URLs move. Ask for representative checks, including internal links, rather than assuming every old page should point to the new homepage.
Agree on What Must Be Fixed Before Launch
Separate a broken customer task from a preference you can decide later. An inquiry going to the wrong address affects whether customers can reach you. A sentence you'd like to shorten may be a smaller follow-up edit, unless it changes the meaning of the offer.
Your acceptance note can be plain:
Ready: [tasks checked and who confirmed them]. Before launch: [specific issues and owners]. After launch: [agreed smaller edits]. [Person] makes the go-live decision, and [technical contact] handles a problem during the switch.
Adapt that example to the project. It creates a shared decision record instead of an email that says only "looks good."
Repeat the Important Checks on the Public Address
Before the switch, confirm who can access the domain, hosting and reporting accounts. Agree on the support contact and the recovery plan if something goes wrong. Keep those details in company records, separate from passwords.
Once the site is live, repeat the phone, form and important link checks. The public site has a different role from the preview, and a successful preview doesn't prove the deployed route works.
For reporting, distinguish a page view, a phone tap and an actual inquiry. Ask what is being counted and how it was tested. You should understand the meaning of the numbers you will receive.
When you reply to the approval request, include the tasks you checked and any unresolved launch blocker. The developer can then see what your approval covers.
Related Guides
Reference
Google Search Central: Site Moves With URL Changes. Reference checked November 15, 2026.
Drafted with AI assistance.
