Internal QA checklist before a site goes to the client
Every comment a client leaves about a broken link or a line of lorem ipsum is a comment about something the team could have caught. This website QA checklist is the internal pass to run before the review link goes out, so the client spends their review on content and decisions instead of finding your loose ends. Each item is one line with how to check it, and there is a copyable version for your project tool.
What this pass is for
Clients are good at spotting problems that aren't theirs to spot. Give them a review link with a broken menu item on the phone and that becomes their first comment, and often their impression of the whole round. The internal QA pass is the hour the team spends finding those things first, so the client review is about wording, images and whether the site does its job.
It sits between two other checks. Design QA compares the build with the approved design: spacing, type, colour, states. The website launch checklist covers going live: the domain, redirects, analytics and removing the noindex setting. This list is neither. It's a short pass for the things a client would otherwise report, run on staging, the day before the review link goes out.
The checklist
Work through one page of each template in full (home, a service or product page, a blog post, the contact page), then click through the rest of the pages looking for anything odd.
Content
- No leftover filler text. Search the page source or CMS for "lorem", "ipsum", "TBC", "TODO" and "xxx".
- No stock or stand-in images that should have been swapped. Compare each image with the client's asset folder or the content doc.
- Names, prices, phone numbers and addresses match what the client sent. Check each one against their email or brief, not from memory.
- Spelling and grammar checked. Paste the copy of each page into a spell checker, including buttons and the footer.
- The footer is current. Copyright year, company name and social links.
Links
- No broken links. Run each main page through the broken link checker, then click the main menu and footer by hand.
- No links to the old site or a dev address. Hover over menu, logo and button links and read the address in the corner of the browser.
- No dead "#" links. Click every button. If one does nothing, either finish it or tell the client in the review email that it's coming.
- Phone and email links work. Tap them on a phone and check the right number or address opens.
Forms
- Every form sends. Submit each one with a test entry and check it arrives in the inbox the client expects.
- Errors make sense. Submit with a required field empty and a badly typed email, and read the messages.
- Something happens after sending. A thank-you message or page shows, and the button can't be pressed twice.
Layout on phone, tablet and desktop
- Checked on a real phone. Open the staging link on your own phone, not only a narrow browser window.
- Nothing scrolls sideways on a phone. Swipe left on each page. If the page moves, something is too wide.
- Tablet width holds up. Look at each template in the responsive checker at tablet size, where layouts often fall between two breakpoints.
- The menu works on a phone. Open it, use every link, close it.
- Long text doesn't break the layout. Look for headings that wrap to one word per line and buttons with text spilling out.
Images and speed
- No oversized images. Run the home page through PageSpeed Insights and look at the image suggestions.
- Images are sharp and cropped well. Check on a phone and on a large screen, and look for cut-off faces or stretched logos.
- The page doesn't jump while it loads. Reload on a phone and watch whether text moves as images and fonts arrive.
Accessibility basics
- Text is readable against its background. Check light grey text and text on photos with a contrast checker.
- Every image that carries meaning has a description. Check the alt text in the CMS, and leave purely decorative images empty.
- Forms have labels. Every field has a visible label, not only grey hint text inside the box.
- The keyboard works. Press Tab through the home page and check you can see where you are and reach the menu and buttons.
Browsers
- Checked in Safari as well as Chrome. Many clients use a Mac or an iPhone, so Safari is the one to check first after Chrome.
- Checked in the client's own browser. If you know they use Edge or Firefox at work, open the site there too.
The SEO basics clients notice
- The browser tab shows a real title. Look at the tab on each template. "Home" or the theme's name is a comment waiting to happen.
- Each page has its own title and description. View the page source and read the title and meta description on each template.
- The favicon is the client's. Check the browser tab icon isn't the platform's default.
- The link preview looks right. Paste the staging link into Slack or WhatsApp and check the title, text and image, because that's how the client will forward it.
- Staging stays hidden from search engines. The noindex setting or password stays on until launch.
The accessibility items above are a quick screen, not an audit. For the contrast item, WCAG 2.2 asks for a ratio of at least 4.5:1 for normal text and 3:1 for large text (W3C, Understanding SC 1.4.3). For the tab title, Google sets no character limit but cuts long titles in results and asks for a distinct, descriptive title on every page (Google Search Central). PageSpeed Insights reports on mobile and desktop, and its lab data comes from Lighthouse, which flags images that are larger than they display, could be compressed further or could use a smaller format such as WebP or AVIF (About PageSpeed Insights, Chrome for Developers).
Copy the checklist
Paste this into a task in your project tool, a ticket or a doc, and tick it off as you go. The second block is a short note for the person who sends the review link, so they know the pass is done.
Ready for client review
For the team chat when the pass is done.Who does it and when
Who: one person who didn't build the pages. A project manager is the usual choice, because they also send the review link and know what the client asked for. A designer or a second developer works too. The developer who built it can run the automated checks first, but shouldn't be the one who signs the pass off.
When: the working day before the review link goes out, after design QA and once the content is in. Leave time to fix what you find. A pass run an hour before the client email turns into a list of known problems sent along with the link.
How long: an hour or two for a small site. On a bigger one, check each template in full and click through the rest.
What to do with what you find: fix the quick things straight away. For anything that can't be fixed in time, say so in the review email ("the blog page is waiting on your copy"), so the client doesn't spend a comment on it. Our guide to sharing a staging site with a client covers the email and the link itself.
Where a tool helps, and where it doesn't
Some of these checks are mechanical, and a tool does them faster than a person. When you share a page on HTMLAnnotate, a page health check runs 17 checks across content, search, accessibility and the share preview: broken links, images without a description, dummy text, the page title and description, form labels, the link preview and more. Show on page takes you to each problem. On the free plan the content checks show in full and the rest as totals; Pro shows all 17 in full. The free broken link checker and responsive checker need no account.
None of that replaces the person going through the list. A tool can tell you a form field has no label. It can't tell you the form sends to an inbox nobody reads, that the phone number is last year's, or that the hero heading wraps badly on the client's phone. Run the tools first to clear the easy items, then do the rest by hand.
Questions
How is this different from a website launch checklist?
A launch checklist covers going live: the domain, redirects, analytics, removing the noindex setting and the first week after. This checklist comes earlier, before the client's first review, and only covers what a client would otherwise point out. Some items overlap, such as links and forms, because they need checking at both stages.
How long should an internal QA pass take?
For a small brochure site, an hour or two for one person. Larger sites take longer, so check one page of each template in full and then click through the rest. If the pass keeps finding the same problem, stop and fix the cause before carrying on.
Who should run QA before the client review?
Someone who didn't build the pages: a project manager, a designer or a second developer. The person who built it checks against what they meant to build, which is where the mistakes came from. Developers can still run the automated checks, such as a link checker, before handing over.
Should the staging site be hidden from search engines during client review?
Usually yes. Keep the noindex setting or a password on staging while the client reviews it, and remove it only at launch. Our launch checklist covers that switch.
Can an automated tool replace this checklist?
No. Tools are good at broken links, missing image descriptions, missing titles and filler text. They can't tell you that a phone number is wrong, a form sends to an old inbox or a heading reads badly on a phone. Use the tools first, then have a person go through the list.
When the internal pass is done, send one review link. The client clicks anything on the page to comment, with no account.
Start a free review