Skip to content
Overflow Sites Discuss a partnership

Agency Website QA Checklist

A practical website production review checklist covering the brief, design, content, responsive behavior, forms, accessibility, and handoff.

💡
Key Takeaways
  • Review against agreed acceptance criteria rather than subjective impressions alone.
  • Test critical interactions and responsive layouts, not only the home page.
  • Record issues with steps, expected behavior, actual behavior, and severity.

Quality assurance is easier when the agency defines what “done” means before implementation begins. A visual review alone can miss a broken form, inaccurate content, or a layout issue that appears only on a phone. Use the original brief and acceptance criteria as the checklist, then record defects so the implementer can reproduce them.

Review the agreed scope

Start with the task list: pages, templates, features, integrations, and exclusions. Confirm that every agreed deliverable is present and that no unapproved feature has been added in a way that changes scope. Compare the build with the latest approved design and content. If the source file changed during production, note which version governs acceptance.

Check page titles, headings, links, images, and supplied copy. Confirm that placeholders have been removed or clearly flagged. Verify that the page uses the intended navigation and that internal links point to the right destinations. If the project includes a content migration, check a sample from each content type rather than only the homepage.

Check responsive behavior

Review the design at the viewport sizes named in the brief, plus a narrow mobile width. Look for clipped text, unexpected horizontal scrolling, broken menus, overlapping buttons, unreadable font sizes, and images that crop away important information. Test touch targets on an actual phone when practical.

Responsive QA should follow the approved design intent, not demand identical pixels at every width. If the design does not specify small-screen behavior, record the ambiguity and agree on an expected result rather than leaving the partner to guess.

Test interactions and workflows

Use a test plan for forms, search, menus, account flows, checkout, booking, and integrations included in the scope. Check both a successful path and useful error or confirmation states. Confirm that submissions reach the expected destination and that notification emails are configured as agreed. Avoid entering real customer data in test records.

For a WordPress build, verify that the editor experience supports the agency or client’s expected updates. Check that the intended theme and plugins are active and that custom fields or blocks behave as designed. WordPress troubleshooting guidance often relies on specific reproduction steps, so record the exact steps for any failure.

Review accessibility and technical basics

Follow the accessibility requirements that were agreed for the project. At minimum, check keyboard navigation, visible focus, heading order, form labels, contrast against the chosen standard, and meaningful alternative text for informative images. Automated checks can help find issues, but they do not replace a human review.

Check links, page loading, browser console errors if the team uses them, and any agreed performance or security checks. Do not add new standards after work is complete without agreeing on scope; instead, note gaps and decide how to address them.

Write actionable defect reports

For each issue, record the URL, device or browser, steps to reproduce, expected result, actual result, screenshot or recording, and priority. Group related issues and distinguish blockers from polish. Avoid vague feedback such as “make it nicer.” Explain what violates the brief or creates a user problem.

Confirm handoff and client readiness

Before client approval, confirm that the staging link works, access is provided securely, source files or credentials are included as agreed, and known limitations are documented. Check the launch plan and rollback contact if the assignment includes deployment. The agency should keep final responsibility for approving work against the client’s requirements.

Prioritize checks by project risk

Not every page needs the same depth of review. Start with the parts that could block a customer or create a costly misunderstanding: contact and checkout flows, navigation to key services, mobile layouts, and any data sent to another system. Then sample repeated page patterns to confirm that shared components behave consistently. Keep a record of the browsers, viewport sizes, accounts, and content states used during review so someone else can understand what was checked. If a test could alter customer data or trigger a real notification, use a controlled environment or a clearly identified test account. Record anything that could not be safely tested.

Explore the topic hub and these related guides:

For work involving WordPress, the official WordPress documentation is a useful reference for maintenance responsibilities and recovery planning.

Sources