Checklist for website acceptance
Systematically check a web project before handing it over to the client: domain, email, content, SEO/GEO, image rights, CMS functions, modules, legal information, and approval.
Goal of the website acceptance
With this checklist, you conduct a final quality control before handing over a website to the client. Technical functions, content, presentation, SEO/GEO, image rights, modules, legal information, and the client handover are systematically checked.
The checklist helps to make open points visible before the approval and to work through the most important checks of a web project step by step.
Capture project data
At the beginning, the most important project data can be entered: client or project, website or domain, review date, and the person who performed the acceptance.
Additionally, there is a section for open points and remarks. Necessary follow-up work, responsible persons, or additional notes can be recorded there.
Work with the checklist
Each checklist item can be marked as completed. Points that do not apply to the respective project can be marked as N/A or not applicable. The progress of the review shows how many points are completed, not applicable, or still open.
- Erledigt: Der Prüfpunkt wurde kontrolliert und abgeschlossen.
- N/A: Der Prüfpunkt ist für dieses Projekt nicht relevant.
- Offen: Der Prüfpunkt muss noch kontrolliert oder nachbearbeitet werden.
The inputs from the provided checklist are stored locally in the browser. Additionally, the checklist can be fully opened and saved as a PDF using the print function. The reset function allows the stored review results and project data to be deleted.
Note: The checklist is intended as a final quality control. Not every checklist item is required for every project. In this case, use the N/A designation.
Interactive checklist for website acceptance
The complete checklist is directly embedded in this documentation entry. You can check off the review points, mark non-applicable points with N/A, enter project data and notes, and track the progress directly.
Note: The checklist runs in its own embedded area. This keeps its design, functionalities, and local storage separate from the documentation page.
Document open points
After the review, enter all remaining tasks in the remarks section. This keeps track of which follow-up work needs to be done before final approval.
Complete acceptance
Once all relevant points are completed or marked as not applicable, the checklist can be saved for project documentation or exported as a PDF. The admin access can then be handed over to the client, and the project can be approved.
Summary
The website acceptance consolidates the most important checks before client handover in nine areas. This ensures that domain and publication, email, content and presentation, SEO/GEO, image rights, CMS functions, shop and booking modules, legal information, and final client handover are structured and examined.
FAQ
what customers often ask us
What is the checklist for website acceptance intended for?
It serves as a final quality control before handing over a website to the client.
What project data can be captured in the checklist?
The customer or project, website or domain, inspection date, and the person who conducted the inspection can be recorded.
What does N/A mean in the checklist?
N/A means not applicable. This can be used to mark checklist items that are not relevant to the respective project.
How is the inspection progress represented?
The checklist distinguishes between completed, not applicable, and open items, calculating the percentage progress from this.
Are my inputs saved?
Yes. The provided checklist saves inputs locally in the browser used.
Can I save the checklist as a PDF?
Yes. By using Print / Save as PDF, the fully opened checklist can be output via the browser's print function.
What domain checks are planned?
Checks include HTTPS, main domain, language domains or language subdomains, as well as the accessibility of pages and language versions.
What email checks are included in the acceptance?
These include agreed customer email addresses, webmail access data, and – if external SMTP access data is available – the email dispatch via forms.
What is checked with regards to content and presentation?
Texts and company data are checked, as well as the presentation on phone, tablet, and desktop. If available, the language switch will also be checked.
Which CMS functions are checked?
The checklist includes forms, form archive, email notifications, file uploads, spam protection, search, dark mode, language switch, permissions, as well as page and section templates.
What is checked for shop or booking projects?
A test order or test booking is conducted, and it is checked whether it appears in the designated overview.
What legal points does the checklist include?
The checklist includes checks for imprint, data protection, external services, consents, newsletters, general terms and conditions, revocation, accessibility requirements, and the approval of legal texts.
When is the website acceptance completed?
When all checklist items relevant to the project are completed or marked as not applicable, and any open tasks are documented.