The final payment is the last moment you have real leverage over the result. This website acceptance checklist helps you test a site in a couple of hours, so you do not find broken contact forms, a domain in someone else’s name or an empty admin panel after you have signed off.

How to run website acceptance

Do not accept a site from a link in a chat in five minutes. Set aside time, take the brief, the approved design and the contract, and open the site on a computer and on a phone. It helps to have two people check it: you and the employee who will work with the site every day.

Write every issue into one document or spreadsheet: the page, what is wrong, how it should be, a screenshot. Send it to the developer as one list, not twenty separate messages. Nothing gets lost, and the developer can estimate the fixes more easily.

Keep bugs separate from new wishes. A bug is anything that does not match the brief or the design, and fixing it is part of the job. A new idea you had while reviewing is a separate request and will likely cost extra. Without a brief, or with a vague one, this is much harder to argue, which is why a website brief is worth writing up front.

How to check a website before launch: brief and design

Go through the brief point by point:

  • every page on the list exists and opens;
  • the promised features work: catalog, filters, search, customer account, calculator;
  • the look matches the approved design: fonts, colors, spacing, order of sections;
  • every language version from the brief is there and fully translated;
  • the promised integrations are connected: payments, 1C, CRM, Telegram notifications.

A difference from the design is not always bad: sometimes the developer simplifies something for technical reasons. But you should have been told before handover, not at it.

Forms, leads and payments

This is the most important check, because a business site usually exists to bring in leads. A nice form that sends data nowhere is worse than no form at all.

Fill in every form on the site as a real customer would, and check:

  • where the lead arrived: email, Telegram, CRM, and whether it arrived at all;
  • whether every field made it into the lead, including phone number and comment;
  • what the customer sees after sending: a success message, not a blank page;
  • what happens when a field is filled in wrong: whether the hint makes sense.

If the site takes payments, run a test payment, or a real one for a small amount followed by a refund. Make sure the money lands in your account and the customer gets a confirmation.

While you are at it, check which addresses receive the notifications. During development they are often set to the developer’s email, and after launch your leads keep quietly going to them.

Phones, browsers and speed

Most of your visitors will probably come from a phone. Open the site on several devices: your phone, a colleague’s phone with the other operating system, a tablet, a laptop. Check it in two or three different browsers.

What to look for:

  • text is readable without zooming and nothing spills off the screen;
  • the menu opens and closes, and buttons are easy to tap;
  • the phone number is tappable and starts a call;
  • links to WhatsApp, Telegram and Instagram go to the right place.

Judge speed on mobile data too, not just on the office Wi-Fi. If the home page takes several noticeable seconds to load, ask the developer to compress images and find out what is slowing it down.

Read the whole site, slowly. Look for typos, placeholders like “Lorem ipsum” or “Text coming soon,” outdated prices and test products.

Check the contacts separately: phone, address, opening hours, email, social links. One wrong digit in a phone number costs more than any typo.

If the site collects names, phone numbers or other personal data, it needs a privacy policy, and forms need a clear consent to data processing. Exact requirements depend on the country and type of business. If you are not sure the text is enough, have a lawyer look at it.

Search and analytics

Basic search setup costs almost nothing at launch and much more to fix later. Check that:

  • each page has its own title and description shown in Google search results, not the same ones across the whole site;
  • the site is open to search engines: it is often hidden during development and nobody remembers to open it;
  • if you had an old site, its addresses redirect to the new pages instead of leading to an error;
  • there is a 404 error page with a link back to the home page.

Analytics should be connected from day one and registered to your account. Send a test lead and confirm it shows up in the stats as a goal.

Admin panel, access and backups

Ask the developer to show you the admin panel, then do everything yourself: add a product, change a price, edit the text on the home page, upload a photo. If you cannot manage without the developer, the admin panel is not ready or the instructions are missing.

Next, access. The domain, hosting, admin panel, analytics, email and paid services should be in your name, and you should be able to log in to each account yourself. For the full list, see who owns your website.

Find out how backups work: how often they run, where they are stored and who can restore the site from one. Ask for your own copy of the code and the database.

Do not sign off or make the final payment until you have logged in to every account yourself and received your own test lead from the site.

Instructions, warranty and sign-off

Before you sign the acceptance document, you should have:

  • a short guide to the admin panel, written or on video;
  • a list of all access and paid subscriptions with renewal dates;
  • clear warranty terms: how long the developer fixes bugs for free and how quickly they respond;
  • an agreement on support after the warranty, if you need it.

The warranty period and acceptance procedure should be in your website development contract. If they are not, agree on them in writing now. For what happens to the site next and what support costs, read our article on website support after launch.

Sign the acceptance document once every issue on the list is fixed or has a written agreement. Make the final payment after sign-off, not before. That is how we work at NOVO: the client checks the finished result first, then the stage is closed.

In short

  • Accept the site against the brief and design, and send issues as one written list.
  • Submit every form and check where the lead actually arrives.
  • Test the site on phones, in different browsers and on mobile data.
  • Check contacts, texts, the privacy policy, page titles and analytics.
  • Log in to the admin panel and every account yourself, and get a copy of the code and a guide.
  • Sign off and make the last payment after the issues are fixed.