Website Acceptance Checklist: How to Accept a Finished Site
A website acceptance checklist saves you from the usual scenario: the client opens the homepage on a laptop, sees that it looks good and signs the act. A month later it turns out that leads never arrive, the phone layout is broken and the credentials stayed with the contractor. Below is a review routine of one or two working days that protects your budget.
Website acceptance checklist: what to prepare first
Acceptance starts when the contract is signed, not on delivery day. Make sure the contract or technical brief states exactly what you receive: the list of pages, language versions, number of forms, integrations (Telegram, CRM, analytics), deadlines and the revision process. Without that, acceptance turns into an argument about what was meant.
Ask for a staging URL and check against the brief rather than your impression. Record every comment in a single document: number, page address, what is wrong and a screenshot. That makes fixes easier for the developer and re-checks easier for you.
Find out in advance how many rounds of revisions are included in the price and how quickly they are made. Usually fixes within the original scope are free, while new wishes count as separate work. It is better to understand the difference before the first comment.
Mobile version and loading speed
Open the site on your own phone over mobile data rather than wifi, ideally on both an iPhone and an Android device. Text should read without zooming, buttons should be easy to tap, nothing should spill off the screen, and the phone number and Telegram link should open with a single tap.
Check speed with Google's free PageSpeed Insights: paste the address and read the mobile report. Google treats a largest contentful paint (LCP) of up to 2.5 seconds as good. Typical causes of a slow site are images of several megabytes, unnecessary scripts and heavy fonts.
Scroll every page to the bottom and try menus, galleries, tables and pop-ups. Breakages tend to hide on inner pages rather than the homepage.
Forms, leads and notifications
Send a test request through every form: in the header, the services block, the footer, the pop-up and each language version. Confirm that the alert arrives somewhere it will be seen quickly, such as a Telegram bot or a work chat, rather than an inbox opened once a week.
Check form behaviour with an empty field, a malformed phone number and two submissions in a row. After sending, the visitor must see a clear confirmation. If requests vanish, you lose customers without knowing it.
Find out where leads are stored and who can access them. If the site is connected to a CRM, run a test request through the whole chain to the sales manager.
Content, languages and SEO basics
Go through every page looking for demo text, someone else's phone numbers and addresses, placeholders such as 'text coming soon' and stock images left as fillers. Verify contacts, opening hours, company details and social links.
Switch the language and repeat the walk-through. In Uzbekistan you usually need Russian and Uzbek versions, sometimes English too. A common problem is a complete Russian version next to a half-empty or machine-translated Uzbek one with awkward terminology. Check menus, buttons and form messages as well.
SEO basics: each page has its own title and description, a single H1, alt text on images, working SSL (the padlock in the browser), robots.txt and sitemap.xml, and a designed 404 page. If the site replaces an old one, test redirects: old URLs must lead to the new pages, otherwise the search positions you built up will be lost.
Confirm that Google Analytics and Yandex Metrica are installed and that your test visit shows up in the reports. It is a plus if goals are set up for form submissions and phone clicks.
Credentials, documents and signing the act
Before signing, get every credential: domain registrar, hosting, site admin, analytics, code repository. The domain should be registered to you or your company, not to the contractor. Log into each panel from your own device during acceptance.
Make sure you can change text and a phone number and add a news item or product yourself. Ask for a short demonstration and a screen recording: half an hour that saves dozens of support requests.
Clarify the warranty: how long bugs are fixed for free, what counts as a bug and what counts as a new task, and how hosting and domain renewals work. Sign the act once critical comments are closed; list minor items in the act with deadlines.
FAQ
How long does acceptance take? For a site of a few pages, one or two working days are usually enough for review and a few more for fixes; allow more for a large project.
Can I sign the act with minor comments outstanding? Yes, if they are written down as a list with specific deadlines. Close critical items, such as forms, the mobile version and credentials, before signing.
What if the developer will not hand over credentials? Request them in writing, referring to the contract, and do not sign the act until you have them. It is best to write the handover of credentials into the contract in advance.
Should I test the site in different browsers? Yes, at least in Chrome and Safari, on a computer and on a phone.
Order of work and the next step
In short: compare with the brief, check phone and speed, test all forms, review content and languages, verify SEO and analytics, collect credentials and get training, then sign the act. Save it as a list and tick items off.
If you need a turnkey website, the 4 Digital studio in Tashkent builds sites from 1,399,000 UZS. You can discuss the task and the scope of work before the project starts, which also makes acceptance easier.