The short answer: launch a website only when customers can understand the offer, contact the business and receive a response, and search engines can read the correct URLs. An attractive opening screen does not replace testing forms, redirects and consent settings. This checklist supports launch acceptance; it does not guarantee rankings or traffic from Google.
Decide who has authority to approve the launch
Before launch day, name one person who approves release, the person implementing changes and the owner of testing. Record the version, planned time and an emergency contact method. “Everything looks fine” is not a precise acceptance criterion. Each checklist item needs a result, a check date and a responsible person.
Separate business-critical failures from minor adjustments. Undelivered forms, an incorrect phone number, missing administrative access or noindex left on important pages need attention before launch. Small spacing differences can enter an explicit follow-up list. This is a suggested acceptance process: agree the final conditions with your provider in the contract.
Before launch: URLs, SEO and access to content
Collect your current URLs, especially service pages and content attracting visitors. During a rebuild, map each changed address to its appropriate replacement. Do not redirect every old page to the homepage. If content disappears without a replacement, deliberately agree how that URL will be handled instead of hiding the issue behind an unrelated redirect.
- Check the title, description and one main heading on important pages. They should describe the visible offer, not leftover template text.
- Confirm that the canonical points to the correct public address, not a test domain or another service.
- Check robots metadata and server headers. Remove indexing restrictions from production while retaining them on staging.
- Follow navigation and contextual links. Look for old staging addresses and buttons with no useful destination.
- Open the sitemap. It should list the correct canonical URLs, exclude test pages and use factual modification dates.
Test a 301 redirect using a specific old address: where does it lead, and what status does the destination return? HTTP 200 does not prove that Google has indexed the page. Review Search Console reports after launch, but do not make technical acceptance depend on a promise of immediate indexing. The SEO checklist before a rebuild explains URL preservation in more detail.
Mobile: follow the customer journey, not just a smaller window
On a real phone, open the homepage, choose a service and continue to contact. Check that the header does not cover the offer, the menu can be closed and the consent banner does not block a button. Test portrait and landscape orientation, enlarged text and the form with the keyboard open. Essential information must not depend on hovering a cursor.
On a computer, also check Tab navigation and visible keyboard focus. Field labels, errors and buttons must make sense without guessing what an icon means. In a table, scroll to the last column: the absence of horizontal overflow across the whole page does not prove that data has not been hidden. Inspect a page with a long title, not just the neatest example.
Measure performance on representative pages, but compare the tool's result with the user experience. Useful content appearing, the menu responding and the layout remaining stable all matter. One laboratory score does not describe every customer. See the practical guide to website speed without technical jargon.
Forms: success means the business receives the enquiry
Start in a test environment. Submit a controlled test on production only after agreeing it with the owner, clearly marking it as a test and avoiding real customer data. Do not accidentally trigger a payment, booking or automated campaign. This checklist describes an acceptance test; it does not submit an enquiry on the reader's behalf.
Check required fields, an invalid email address and a lost connection. Does the visitor keep their text and understand what needs correcting? The on-screen success message should appear after the server accepts the data. Browser validation helps users but does not replace server-side validation, as W3C's documentation emphasises.
The recipient must confirm that the enquiry exists in the intended inbox or CRM. Check the reply address, spam folder and the person assigned to respond. Clicking twice should not create accidental duplicates. If the form shows success but the business receives nothing, the contact journey has not passed acceptance.
Analytics and consent: check different choices
In a new session, inspect behaviour before a choice, after rejecting optional tools and after accepting them. The contact form should remain available without marketing consent. The tool inventory and privacy information must match the actual implementation. Consult an appropriate specialist about legal requirements; a banner alone does not establish compliance.
Define an event for a successfully submitted enquiry separately from a button click. Google describes generate_lead as an event associated with submitting a form or requesting information. Implementation and counting rules need their own checks. Do not send names, email addresses or message content to analytics. Record that rejected consent and browser blocking can limit data completeness.
A simple launch decision sheet
| Area | Acceptance evidence | What blocks launch |
|---|---|---|
| Contact | An agreed test enquiry received by the business | No delivery or an incorrect recipient |
| SEO and URLs | Important URL list and checked redirects | Production indexing blocked or key content lost |
| Mobile | A complete offer-to-contact journey on a device | An inaccessible menu or form |
| Measurement and privacy | Checked consent choices and a success event | Data leakage or consent behaviour contradicting the choice |
| Recovery | A known backup and someone authorised to restore it | No safe way to reverse the change |
After launch: verify production and retain evidence
Repeat the essential checks at the public address, outside an administrator session. Check HTTPS, navigation, contact, several old links and the public sitemap. Retain results and phone screenshots. A working staging environment is insufficient: production may use different caching, email or consent settings.
Agree monitoring for the first few days and a date for reviewing defects. In an incident, restore only a verified version and account for enquiries saved since launch. Restoring an old database without agreement can delete new information. Close the release when acceptance criteria are confirmed and access has been handed over, not simply when files have been copied.
What to hand over with the website
Acceptance also includes access to the domain, hosting and content management system. Accounts should belong to the business, and the provider's permissions should match the work required. Do not send passwords in an ordinary checklist message. Agree a secure handover method and identify who will manage access afterwards.
Include brief instructions for changing the offer, images and contact details, and explain how to report incidents. Name the person responsible for updates and backups. Check that the owner can find an enquiry and publish a simple correction without breaking the layout. This is a separate usability test of the administration system, not an optional design detail. If maintenance ends at launch, state that explicitly and agree ongoing support. Do not leave critical responsibilities implied.
Sources and limits of this checklist
This is a practical acceptance procedure, not a complete security audit or legal opinion. Technical foundations: Google's site migration guidance, W3C form validation and GA4 recommended events. Adapt the tests to the site's actual features.
Planning a new website or a redesign?
Describe your project in the brief. It is not a substitute for technical acceptance or an analytics audit. The form is in Polish.
Open the website brief (in Polish) ↗