A staging checklist works when a client can finish it in twenty minutes without asking what a line means. Most do not. They are written for developers, so the person who actually has to approve the website skims it, clicks the home page and says it looks great. Then a form goes to the wrong inbox for a month.
Here is how to build a staging checklist that people click through, and what belongs on it. Staging is the private copy of your site where changes are reviewed before they go live.
What should a website staging checklist cover?
Cover the things that cost you money if they break: how people contact you, how the site looks on a phone, and whether the right text is on each page. Check also that search engines can still find the site after launch. Skip anything that only a developer could verify, and handle that separately.
Group items by what the reviewer is doing, not by technical area. “Send yourself a test inquiry through every form” is a task. “Verify SMTP configuration” is a worry. The first one has a visible result, which is an email arriving in a particular inbox.
Keep the list to one page. Anything longer gets abandoned halfway, and the half that gets skipped is usually the bottom, where the unglamorous items sit.
How do you test forms and phone numbers?
Submit every form, using a real address you can check. Then confirm three things: the message arrives, it arrives at the right place, and the visitor sees a sensible thank-you message. Do this for the contact form, any quote request, newsletter signup and any download form. Then check the spam folder, because that is where a misconfigured form often sends its mail.
Tap each phone number on an actual phone to confirm it dials the correct line. Click each email link. Check that the opening hours, address and service area match what you really offer today, since staging copy is often a mix of old and placeholder text.
If your site has a booking link, make a test booking. Our note on service pages with a calendar link explains why that path deserves the same care as a form.
What do you check on mobile?
Use a real phone, not just a narrowed browser window. Open the home page, one service page and the contact page. Look for text that is too small to read without zooming, buttons too close together to tap, menus that do not open, or images that push the page sideways.
Rotate the phone once. Check that a sticky header does not cover half the screen. Scroll to the footer and confirm the links there work, since legal pages tend to be forgotten. If you have a second phone, ideally a different brand, test there too. One of them will show a problem the other hides.
Reviewers often stop at “it fits.” Ask them to complete one real task instead: find the price of a service, or reach the booking page. A task shows friction that a glance does not.
What about SEO and the launch switch?
Staging sites should be hidden from search engines, and the live site should not be. This one setting is easy to get backwards: either the new site launches still blocked and traffic quietly drops, or the staging copy gets indexed and competes with the real one. In WordPress, the “Discourage search engines from indexing this site” box under Settings, then Reading, should be off on the live site and on for staging. Check it on launch day.
Then confirm page titles and descriptions made it across, the old addresses redirect to new ones where they changed, and analytics is recording visits. Google’s own SEO starter guide is a fair reference for what to verify.
For what to do when the studio hands you the keys, the handoff checklist picks up where this one ends.
Make the review hard to skip
- One page, written as actions with visible results.
- Every form submitted, every phone number tapped.
- One real task completed on a real phone.
- Search visibility checked on launch day, not assumed.
- A named person signs off, with a date.