A website always looks finished before it is finished. The design is signed off, the pages are built, and everyone is keen to launch — which is exactly when the broken contact form, the placeholder text nobody replaced, and the link to a page that does not exist tend to slip through. A structured pre-launch review is what catches them.
Review content, not just design
Design review usually happens; content review often does not. Read every page as a visitor would: check for placeholder text left in, typos, outdated information, and calls to action that actually make sense. The prettiest page in the world still fails if the copy says 'Lorem ipsum' or the phone number is from the last rebrand.
Test everything interactive
Static pages are the easy part. The things that break are the things that do something: contact forms that go nowhere, newsletter signups that error, buttons that link to the wrong place, and search that returns nothing. Every interactive element needs to be clicked and confirmed working before launch, not after a customer reports it.
Check it on real devices
A layout that is perfect on a desktop monitor can fall apart on a phone, and most of your visitors are on a phone. Review the site at mobile and tablet sizes, checking that text is readable, tap targets are big enough, and nothing overflows the screen. Responsive problems are far cheaper to fix before launch than after.
Collect feedback where everyone can see it
Pre-launch feedback tends to arrive as a chaotic mix of emails, screenshots, and 'the button on the about page is broken — which button? which about page?'. Reviewing the site in a tool where each comment is pinned to the exact spot on the page turns that mess into a clear, actionable list that the developer can work through and check off.
“A website always looks finished before it is finished. The broken form and the leftover placeholder text slip through precisely because everyone is keen to launch — which is why a structured review exists.”
Pre-launch website review checklist
- Read every page for placeholder text, typos, and stale info
- Test every form, signup, button, and search
- Check all links go where they should
- Review on mobile and tablet, not just desktop
- Collect feedback pinned to exact spots on the page
Frequently asked questions
What should I check before launching a website?
Read every page for placeholder text and typos, test every form and interactive element, confirm all links work, review the layout on mobile and tablet, and collect feedback in one place where each comment is pinned to the exact spot it refers to.
How do I collect feedback on a website?
Use a tool that lets reviewers comment directly on the live page or a capture of it, with each note pinned to the exact element. That turns a scatter of vague emails and screenshots into a clear, located list a developer can action.
Why review a website on mobile?
Because most visitors are on a phone, and a layout that looks perfect on a desktop can break on a small screen — unreadable text, overflowing elements, tap targets too small. Responsive issues are far cheaper to fix before launch.
FileFeedback
Struggling with client feedback on your projects?
FileFeedback lets clients leave frame-accurate, timestamped comments directly on your videos and images — no more email chains, no more confusion about which version they mean.
Try FileFeedback free