Software teams rarely fail because nobody cared about quality. They fail because important assumptions stayed implicit until users, support teams, or production systems exposed them. A website can look complete while still hiding broken links, failed forms, missing assets, and mobile usability problems.

This guide is written for teams launching marketing sites, product sites, and web applications. It provides a focused way to review the subject without pretending every product needs the same amount of process or coverage. The aim is to make risk visible, gather useful evidence, and help the team decide what to fix, what to monitor, and what can reasonably wait.

Why this matters

Website quality combines working behavior, clear content, responsive interaction, accessibility, production configuration, and reliable conversion paths. A checklist is valuable only when it changes a decision or prevents an important omission. It should therefore reflect the product’s actual users, revenue model, data, integrations, platforms, and release constraints.

Before starting, define the scope. Record the build or version, environment, target users, relevant roles, and the critical outcome being protected. This small amount of context prevents a common problem: a test result that looks positive but applies to the wrong configuration or an unrealistic account state.

Practical checklist

1. Check every conversion path

Submit contact, signup, checkout, download, and booking forms with valid and invalid data. Treat this as an observable release condition rather than a general intention. For teams launching marketing sites, product sites, and web applications, the useful question is not simply whether the screen appears to work. Ask what evidence would make the team comfortable shipping, what result would stop the release, and how a failure would be detected after launch.

Practical check: write one expected result, one important variation, and one failure condition for this area. Add the build, environment, account state, and any relevant data to the test note so another person can reproduce the result.

Review navigation, buttons, footer links, old URLs, canonical paths, and external destinations. Use representative accounts, data, devices, and states so the result reflects real usage. For teams launching marketing sites, product sites, and web applications, the useful question is not simply whether the screen appears to work. Ask what evidence would make the team comfortable shipping, what result would stop the release, and how a failure would be detected after launch.

Practical check: write one expected result, one important variation, and one failure condition for this area. Add the build, environment, account state, and any relevant data to the test note so another person can reproduce the result.

3. Test responsive layouts

Inspect key pages at narrow, medium, and wide widths, including long text and error states. Record the evidence, unresolved questions, and owner instead of relying on memory after the test session. For teams launching marketing sites, product sites, and web applications, the useful question is not simply whether the screen appears to work. Ask what evidence would make the team comfortable shipping, what result would stop the release, and how a failure would be detected after launch.

Practical check: write one expected result, one important variation, and one failure condition for this area. Add the build, environment, account state, and any relevant data to the test note so another person can reproduce the result.

4. Review content and metadata

Check titles, descriptions, headings, social previews, spelling, legal copy, and consistency. Test both the expected path and at least one realistic failure or recovery path. For teams launching marketing sites, product sites, and web applications, the useful question is not simply whether the screen appears to work. Ask what evidence would make the team comfortable shipping, what result would stop the release, and how a failure would be detected after launch.

Practical check: write one expected result, one important variation, and one failure condition for this area. Add the build, environment, account state, and any relevant data to the test note so another person can reproduce the result.

5. Validate assets and loading states

Look for missing images, layout shifts, unreadable fallbacks, blocked scripts, and slow third-party widgets. Connect the check to user impact so the team can distinguish a blocker from a lower-priority imperfection. For teams launching marketing sites, product sites, and web applications, the useful question is not simply whether the screen appears to work. Ask what evidence would make the team comfortable shipping, what result would stop the release, and how a failure would be detected after launch.

Practical check: write one expected result, one important variation, and one failure condition for this area. Add the build, environment, account state, and any relevant data to the test note so another person can reproduce the result.

6. Test accessibility basics

Use keyboard navigation, visible focus, labels, contrast, alt text, and zoom as quick quality gates. Repeat the check on the actual release candidate whenever configuration or deployment can change the result. For teams launching marketing sites, product sites, and web applications, the useful question is not simply whether the screen appears to work. Ask what evidence would make the team comfortable shipping, what result would stop the release, and how a failure would be detected after launch.

Practical check: write one expected result, one important variation, and one failure condition for this area. Add the build, environment, account state, and any relevant data to the test note so another person can reproduce the result.

7. Confirm production configuration

Verify analytics, robots.txt, sitemap, cookies, security headers, domains, and environment-specific settings. Keep the check small enough to run consistently, then expand it only when defects or incidents reveal additional risk. For teams launching marketing sites, product sites, and web applications, the useful question is not simply whether the screen appears to work. Ask what evidence would make the team comfortable shipping, what result would stop the release, and how a failure would be detected after launch.

Practical check: write one expected result, one important variation, and one failure condition for this area. Add the build, environment, account state, and any relevant data to the test note so another person can reproduce the result.

Common mistakes to avoid

  • Testing only the homepage. This usually hides uncertainty rather than removing it. Make the assumption visible, decide whether it creates material user or business risk, and assign a specific follow-up action.
  • Assuming desktop approval means mobile is ready. This usually hides uncertainty rather than removing it. Make the assumption visible, decide whether it creates material user or business risk, and assign a specific follow-up action.
  • Forgetting production configuration differs from staging. This usually hides uncertainty rather than removing it. Make the assumption visible, decide whether it creates material user or business risk, and assign a specific follow-up action.

These mistakes are especially dangerous when a team is moving quickly because the absence of evidence can be mistaken for the absence of risk. A short written note is enough: state what was checked, what was not checked, which defects remain, and who owns the decision.

A lightweight way to put this into practice

  1. Run the free Website Health Checker. Keep the output short and usable. A named owner, clear evidence, and a decision deadline are more valuable than a large document that no one updates.
  2. Manually test critical pages and forms. Keep the output short and usable. A named owner, clear evidence, and a decision deadline are more valuable than a large document that no one updates.
  3. Repeat a production smoke test immediately after deployment. Keep the output short and usable. A named owner, clear evidence, and a decision deadline are more valuable than a large document that no one updates.

During execution, avoid turning the checklist into a mechanical pass-or-fail exercise. When a result is surprising, investigate the surrounding states, dependencies, and user impact. One well-explored risk often provides more release value than dozens of shallow confirmations.

What to include in the final QA note

A useful summary can fit on one page. Include the release or feature reviewed, environment and build, critical journeys covered, devices or browsers used, open blockers, accepted risks, untested areas, workarounds, monitoring needs, and the final recommendation. Link defects and evidence rather than copying every detail into the summary.

The recommendation should be explicit: ready, ready with conditions, or not ready. When the answer is conditional, name the conditions and their owners. This makes QA useful to founders and product leaders who need to make a decision, not merely receive another status update.

Final takeaway

A website can look complete while still hiding broken links, failed forms, missing assets, and mobile usability problems. Start with the highest-impact user outcome, test the conditions most likely to threaten it, and document the remaining uncertainty honestly. The best quality process is not the largest one; it is the one the team can repeat and trust.

Run the free Website Health Checker, then discuss deeper manual QA coverage for critical journeys.