Website QA Checklist: Free Interactive Tool

From staging to live website. Use this website QA checklist to check the most important items before you ship. 👇

Checklist categories explained

Functional Testing

Verify key user flows, and all interactive components behave as expected.

Design

Confirm the build matches the intended designs – branding, typography, layout, interactive elements etc.

Content

Check for typos, placeholder text, accurate product info, consistent tone, and legal pages are in place.

Accessibility

Meet WCAG 2.1 AA: alt text, color contrast, keyboard navigation, visible focus rings etc.

SEO, AEO & Performance

Cover everything search engines and AI tools need to find and cite your content.

Cross-browser & Device

Ensuring the website renders correctly across the main browsers, different breakpoints and devices.

How to use the website QA checklist

Work through each category with your team/clients before launching your website.

1
Open the website on staging

Run through the checklist with your staging or pre-production environment open in a second tab.

2
Work category by category

Start with Functional Testing and work down. Each item has a description to guide what to look for.

3
Log bugs as you find them

Make your web developer's life easier by using a website QA tool like BugHerd to pin issues directly on the page.

4
Share what's been done with your team

When done, hit "Copy summary" to export a plain-text report of what passed and what remains.

Frequently asked questions

Common questions about website QA testing.

What is website QA testing?

Website QA (Quality Assurance) testing is the process of systematically checking a website before launch to identify bugs, broken links, accessibility issues, performance problems, and other defects. It covers visual design, content accuracy, functional behaviour, cross-browser compatibility, and SEO — ensuring the site meets requirements before it goes live to real users.

How long does website QA take?

For a standard marketing website, a thorough QA pass typically takes 4–8 hours for an experienced tester. Larger sites with complex functionality, e-commerce checkout flows, or many page templates can take several days. Using a structured checklist like this one significantly reduces the time spent and ensures nothing is missed.

Who should be responsible for website QA?

Ideally, QA is a shared responsibility. Developers check technical correctness. Designers verify visual fidelity. Content editors proofread copy. A dedicated QA tester or project manager then runs a final pass against a checklist like this one before sign-off. Using a visual bug tracker such as BugHerd keeps all stakeholders aligned during the process.

What's the difference between QA testing and UAT?

QA testing is performed by the team building the site to catch technical issues, visual bugs, and broken functionality. User Acceptance Testing (UAT) is performed by the client or end-users to confirm the site meets their business requirements. Both are important: QA catches defects, UAT validates the solution. BugHerd is designed specifically to support UAT by letting clients annotate feedback directly on the live site.

How does BugHerd help with website QA?

BugHerd is a visual bug tracker that lets clients and stakeholders pin feedback directly onto a website — no screenshot attachments or lengthy email threads. Testers click on any element, leave a comment, and BugHerd automatically captures browser details, OS, and a screenshot. The team sees all feedback in a Kanban board and can resolve issues without chasing vague descriptions.

More guides and tools to help you ship client websites with confidence.