Website QA is where polished product work meets real browsers, devices, permissions, integrations, and impatient users. A page can look correct in a design review and still fail when a customer tries to sign up, invite a teammate, update billing, or submit a support question.
This checklist is built for SaaS teams shipping websites and web apps. Use it before major launches, redesigns, onboarding changes, pricing updates, and high-traffic campaigns.
For faster issue capture, pair the checklist with a website feedback tool so testers can report problems with screenshots, replay, logs, and page context attached.
1. Core user flows
Check the workflows that produce business value:
- Signup and login.
- Password reset.
- Trial start.
- Invite teammate.
- Create or edit a project.
- Connect an integration.
- Submit a support request.
- Upgrade, downgrade, or cancel.
- Billing and invoice access.
For every flow, test the happy path, an error path, and a permission edge case.
2. Forms and validation
Forms are common failure points because they mix UI, validation, API calls, email, and database state.
Check required fields, invalid email formats, long names, special characters, duplicate submissions, loading states, success messages, and error messages. Confirm users know what happened after submitting.
3. Responsive layout
Test desktop, tablet, and mobile. Look for clipped headings, overlapping CTAs, unusable menus, hidden form fields, images that push content below the fold, and tables that do not scroll.
If your product is used inside mobile browsers, test the actual app flows on physical devices, not only browser resize mode.
4. Browser coverage
At minimum, test current Chrome, Safari, Firefox, and Edge. If you have meaningful mobile traffic, test iOS Safari and Android Chrome. Browser-specific layout and auth issues are still common.
When a tester reports a browser issue, make sure the report includes browser version, OS, screen size, console logs, and network request data.
5. Visual and content QA
Check page titles, hero copy, button text, product names, pricing, legal links, customer logos, alt text, screenshots, and broken image states.
Marketing pages should answer the visitor’s buying question quickly: what this is, who it is for, what workflow it replaces, and why it is different.
6. Support and feedback paths
Every important page should give users a clear next step when they get stuck. Check live chat, help center links, contact forms, chatbot handoff, and feedback widgets.
For product pages, a feedback path is not just support. It is a way to capture bugs, product feedback, and feature requests while the context is fresh.
7. Analytics and conversion tracking
Confirm tracking for page views, signup starts, trial starts, demo requests, pricing clicks, form errors, and checkout events. Check that events fire once, use the correct property names, and do not expose sensitive data.
8. Performance and loading states
Check above-the-fold loading, image weight, layout shift, skeleton states, delayed third-party scripts, and slow API responses. QA should include the experience on average connections, not only office Wi-Fi.
9. Accessibility basics
Run through keyboard navigation, visible focus states, labels for inputs, meaningful alt text, contrast on key text, and readable error messages. These basics improve both accessibility and general usability.
10. Launch feedback workflow
Define where issues go before QA starts. A useful workflow has:
- One place to submit issues.
- Clear severity labels.
- Ownership for triage.
- Links to session replay, screenshots, and logs.
- A way to group duplicates.
- A handoff to engineering or product.
Gleap helps here by connecting website feedback, in-app bug reporting, support conversations, and product feedback software in one workspace.
Website QA checklist template
Core flows tested:
Forms validated:
Desktop layouts checked:
Mobile layouts checked:
Browsers checked:
Visual/content issues logged:
Support and feedback paths verified:
Analytics events verified:
Performance issues logged:
Accessibility basics checked:
Open launch blockers:
Owner:
Ship/no-ship decision:The goal of website QA is not to find every possible imperfection. The goal is to catch the issues that block trust, conversion, support, and product adoption before customers have to report them the hard way.