Guide
Website review checklist
A website review (some teams call it a QA pass) is a last look before something goes live: a new page, a redesign, a marketing campaign. It's smaller than a full launch or a full UAT round, and it's easy to rush. This is the list to go through instead of just scrolling the page once and calling it done.
Content
- Headings, body text and CTAs are proofread, including on mobile where text can reflow oddly.
- Every image has alt text, and none are stretched, blurry or showing a placeholder.
- Dates, prices, and names are current, not leftover from a template or a previous campaign.
- Tone and terminology match the rest of the site (the same feature isn't called three different things).
Links and navigation
- Every link on the page goes where it says it goes, checked by clicking, not assumed.
- External links open sensibly (new tab if that's your convention, not inconsistently).
- Anchors and in-page jump links land on the right section.
- The page is reachable from where it should be: the main nav, a sitemap, or wherever it's meant to be linked from.
Forms and interactive elements
- Every field validates sensibly: required fields are enforced, and the error message says what's wrong.
- A successful submission shows clear confirmation, not just a blank reload.
- Buttons and toggles respond immediately; nothing looks clickable but silently does nothing.
Responsiveness
- The page looks right at common widths: a large desktop, a laptop, a tablet in both orientations, and a phone.
- Nothing overlaps, gets cut off, or requires horizontal scrolling that shouldn't be there.
- Touch targets are big enough to tap accurately on a phone.
Performance and SEO basics
- Images are compressed, not full-resolution files shrunk by CSS.
- The page title and meta description are written for this page, not copied from another one.
- There's exactly one H1, and headings are in a sensible order (no skipping from H1 to H4).
- The page loads without visible layout shift as images and fonts come in.
Cross-browser sanity check
- Chrome, Safari and Firefox at minimum, even for five minutes each.
- Dark mode, if the site supports it, doesn't leave any text unreadable.
Before you call it done
- Someone other than the person who built the page does the review. A second set of eyes catches what the builder stopped seeing.
- Every issue found has an owner and is tracked somewhere, not fixed silently and forgotten, or mentioned once and lost.
Do it in StiqNote
Open the page and pin each issue to the exact spot: the broken link, the cut-off button, the typo in the third paragraph. Add a screenshot if it helps, assign it to whoever owns the fix, and resolve it once it's done. Invite a second reviewer with a guest link if you want another set of eyes without giving them an account.
See client review with no install if the people reviewing aren't on your team.
Stop sending screenshots in Slack
Pin the feedback where it belongs. Free to start, with 14 days of Agency for your first team.