Website launch checklist
Before publication, the site may look ready, but the external part is only one level of verification. An error in DNS, form, redirection or analytics is detected after launch and affects not the layout, but the actual requests and data.
A technical checklist helps to carry out the switch consistently. It does not replace project testing, but identifies critical points that must be checked before opening the site to visitors and search engines.
1. Prepare the domain, DNS and HTTPS
You need to confirm the domain owner, DNS access and registration period in advance. Records must go to the correct server, and mail records must remain correct after changes. If the IP address changes, take into account the DNS update time and do not disable the old site too early.
An HTTPS certificate must be issued for all domain names used, and the transition from HTTP must be carried out to a single canonical version. They check the home page, internal pages, files and API requests: mixed content may leave some resources blocked by the browser.
2. Keep a backup and rollback plan
Before switching, create a copy of files, database and important configuration. The archive is checked for size and composition, stored separately from the work site, and a clear recovery procedure is recorded.
You also need a rollback plan: who decides what changes are returned and how much time can be spent on correction. For a site with active orders or requests, they separately determine how not to lose the data that appeared between the backup and switching.
3. Test forms and integrations end to end
Every form is processed as a visitor: required fields are filled out, errors, consents, successful responses, and resubmission protection are checked. Then they confirm that the enquiry actually reached the mail, CRM, Telegram or client dashboard.
One message “sent” is not enough. It is important to check the entire chain to the manager, including attachments, notifications and the source of the request. A detailed scheme of such control is described in the article about the path of an enquiry from the site to the manager.
4. Check realistic mobile screen sizes
The site is checked not only in window reduction mode. We need real widths of phones and tablets, portrait and landscape orientation, text enlargement and finger control. Particular attention is paid to menus, forms, pop-ups, tables and fixed buttons.
Headings should not extend off the screen or break mid-word, interactive elements should not overlap content, and margins should not create unexpected scale. Checking the keyboard and visible focus helps detect some accessibility issues before launch.
5. Measure speed on actual working pages
Speed is measured on those pages where traffic actually comes: the main page, services, articles, form or catalog. They separately look at the first visit without a cache and re-download, as well as behavior on a mobile connection.
Before launching, they optimize images, remove unnecessary scripts and check that the cache does not hide the latest version. The server must have a reserve of resources, and the logs must not be filled with repeated errors. When choosing an infrastructure, it is useful to check the guide for choosing a VPS for a site.
6. Configure SEO, URLs and analytics
On the public version, page titles, descriptions, canonical addresses, robots.txt and Sitemap are checked. The test site may be closed from indexing, but this ban cannot be accidentally transferred to the main domain.
If addresses change, create a map of constant redirects from old URLs to the most suitable new ones. Analytics counters and goals are verified by real action, and not just by the presence of code. Error pages, social media images and favicons are also included in the final review.
7. Assign access, security and monitoring responsibilities
Before opening, temporary accounts are deleted, transferred passwords are changed, administrative rights are limited, and secrets are not located in public files. The system, plugins and dependencies must be on consistent versions without unnecessary components.
After launch, a person is appointed responsible for the domain, certificate, backups, updates and response to errors. Monitoring of availability and critical scenarios is enabled immediately, and not after the first failure. The list of regular tasks can be checked with the article about site support after launch.
Launch is a controlled transition
The launch must have a time, people responsible, a list of checks, and a clear cancellation criterion. First, they perform backup and preparation, then switchover, a short check of critical functions and extended control already on the public domain.
The results record: what has been checked, what restrictions remain and who is responsible for the next step. Prepare the launch of a website with Skycode – describe the project, and we will prepare a test for its technologies and business scenarios.
Final control after publication
The list of what to check before launching a site does not end with transfer to the main domain. Once published, submit test forms, test emails and notifications, open pages on your phone, and make sure analytics are receiving events.
For the search part, use Official Google SEO Guide to check for crawlable pages, clear headings, and useful content. Such a repeated pass confirmsthat it was possible to check before launching the sitenot only on a test bench, but also in a production environment.
The team should agree in advance what to check before launching the site again immediately after switching the domain and clearing the cache.