Website acceptance is the step that helps a business confirm that the delivered product matches the agreed scope, runs reliably, and meets the stated objectives. Checking the website on just one device or reviewing a few representative pages can leave display, functionality, and administration issues undiscovered.
This website acceptance criteria checklist covers the key areas: design, functionality, content, performance, and administrative capabilities. Businesses can use it to compare the finished website against the initial requirements, document issues, and agree on handover conditions with the development team.
1. Preparing for website acceptance
Before testing, gather the relevant documents and information so the acceptance process has a clear basis. Compare the live website with the quotation, proposal, contract, functional specifications, and any content approved by both parties. If requirements changed during development, review the corresponding meeting notes or written confirmations.
Agree on the acceptance scope in advance: which pages to check, which features are included in the project, which devices and browsers are supported, and who has approval authority. For each issue found, record the page URL, device used, steps that triggered the problem, a screenshot, and its impact. This gives the development team clear information to act on and avoids vague discussions.
- Prepare administrator accounts and test login details.
- Test in the agreed environment, such as a staging site or the production domain.
- Classify issues as critical, requiring resolution before handover, or suggested improvements for after handover.
- Agree on fix deadlines, retesting procedures, and the criteria for confirming completion.
2. Design and user experience acceptance checklist
The design should be consistent with the brand identity and help customers find information and take the desired action. Don’t check only the homepage. Review key pages such as About, Services, Products, Articles, Contact, and any project-specific pages within scope.

- Brand identity: The logo, colors, typography, images, and presentation style match the supplied brand guidelines.
- Layout: Content blocks are arranged logically, and headings, paragraphs, images, and calls to action are easy to distinguish.
- Navigation: Menus, submenus, breadcrumbs, and footers work correctly; users can easily return to a previous page or find the page they need.
- Responsive design: The website displays appropriately on desktop, tablet, and mobile; content doesn’t overflow, text isn’t cut off, and unexpected horizontal scrolling doesn’t appear.
- Readability: Font size, contrast, line spacing, and touch targets are clear, especially on smaller screens.
- Interaction states: Buttons, links, form fields, and menus provide clear visual feedback when users interact with them.
Test on common devices or screen sizes rather than simply shrinking the browser window. Also test at least the browsers most commonly used by your target customers. If you find minor display differences, distinguish usability issues from variations that don’t affect the core experience.
3. Functionality and user journey acceptance checklist
Test the website through real-world user journeys, from the moment a visitor arrives to the completion of an action. For each feature, try valid data as well as missing, incorrectly formatted, or blank inputs. The goal is to confirm that the feature works correctly, messages are easy to understand, and user data isn’t lost.

- Forms: Contact, consultation request, and quote request forms send data to the correct email address, administration system, or agreed integration platform.
- Data validation: Required fields, email addresses, phone numbers, and character limits are validated appropriately; error messages explain how to correct the problem.
- Search and filters: Search results are relevant to the query; filters, categories, and sorting return accurate results if the website includes these features.
- Accounts and permissions: Login, logout, password recovery, and access permissions work according to the specified roles.
- Commerce features: If the website has a shopping cart, ordering, or payment, test the entire process, order statuses, and confirmation messages.
- Integrations: Check agreed connections such as maps, analytics tools, CRM, email marketing, or payment gateways.
Don’t just check whether a button can be clicked. Confirm what happens afterward: where the data is stored, whether the responsible person receives a notification, and whether visitors see the appropriate confirmation page. Features that depend on third-party services should be tested in real operating conditions or according to the agreed testing process.
4. Content and basic SEO acceptance checklist
Content should be accurate, complete, and displayed correctly. Businesses should assign someone to approve technical information, prices, policies, addresses, phone numbers, and claims relating to products or services. Inaccurate or outdated information in these areas can harm the company’s reputation.
- Check spelling, punctuation, brand name usage, and consistency of terminology.
- Confirm that images, icons, and downloadable documents are correct, unbroken, and displayed at the right proportions.
- Make sure internal links and links to documents work; remove placeholder content and unintended blank pages.
- Check page titles, meta descriptions, heading structure, and page URLs against the agreed SEO scope.
- Confirm that images have appropriate file names and alt text when these are included in the requirements.
- Check the 404 error page, policy pages, and essential contact information.
For SEO, website acceptance criteria should focus on settings that can be verified at handover. Search ranking commitments should not be treated as acceptance conditions. Rankings also depend on the market, content quality, competition, and optimization work after the website goes live.
5. Performance, security, and administration acceptance checklist
Performance has a direct impact on user experience and conversion rates. Open key pages over a typical internet connection, observe loading times, and check whether the main content appears consistently. If the website is slow, identify the cause and compare performance with the project’s agreed requirements or thresholds rather than relying on impressions alone.

- Performance: Pages don’t freeze or load indefinitely; images are appropriately optimized; and essential elements work on mobile devices.
- Basic security: HTTPS works, administrator accounts are assigned to the right people, and easy-to-guess default login credentials aren’t used.
- Backup and recovery: Confirm the data backup process, frequency, and responsibility for carrying it out if these are part of the handover scope.
- Administrative capabilities: The responsible staff member can log in, create and edit content, update images, or manage data according to their assigned permissions.
- User guidance: Documentation or training is available for routine administration; form fields have clear labels.
- Technical handover: Agree on the domain, hosting, service accounts, source code, and support contact in line with the contract.
Give an internal staff member a specific task, such as publishing a new article or updating service information, and see whether they can complete it independently or need help at any step. This gives the business a practical measure of administrative readiness rather than simply confirming that account details have been received.
6. Preparing the acceptance record and concluding the process
After completing the checklist, compile the results into an acceptance record listing items that passed, items that did not, and issues that need follow-up. For each issue, note its priority, the person responsible, the resolution deadline, and the retest result. If an item can’t be completed because it depends on data or an external service, specify the outstanding requirements and next steps.
Confirm acceptance only when essential requirements have been met, issues affecting core functionality have been resolved, and handover accounts and documents have been checked. Suggested improvements outside the original scope can be recorded separately for consideration in a later phase. This distinction helps both parties agree on their responsibilities and reduces the risk of disputes after handover.
Applying website acceptance criteria in full helps businesses control quality before launch and gives them a clear basis for working with the development team. If you need a checklist tailored to your business objectives, help reviewing requirements, or a new website, contact LilyTech for advice on an approach suited to your company’s size and plans.
Đoàn Lê Minh Anh