---
title: "Professional website launch checklist: 12 checks · Lyntev"
description: "Test content, forms, mobile use, accessibility and configuration before publication. Includes 12 checks and an approval worksheet."
url: "https://lyntev.com/en/guides/professional-website-launch-checklist"
language: "en-GB"
date_published: "2026-11-21T17:20:13.047Z"
date_modified: "2026-11-21T17:20:13.047Z"
---

1. [Home](<https://lyntev.com/en>)
2. [Practical guides](<https://lyntev.com/en/guides>)
3. Checklist for publishing a professional website

# Checklist for publishing a professional website

A website is ready when visitors understand the offer, complete the intended action and the team receives the result. This checklist turns “everything seems fine” into observable checks. Use it on the preview and repeat the essential points at the public address, where the configuration may differ.

By [Lyntev](<https://lyntev.com/en/company>). Updated on 17 November 2026.
About 5 minutes to read.

[Use the checklist](<https://lyntev.com/en/guides/professional-website-launch-checklist#lista-de-verificacao>)[Download worksheet](<https://lyntev.com/recursos/en/checklist-publicar-site-profissional.txt>)

**From review to publication**A process with approval criteria at every stage.

Translation published on 21 November 2026. [Original Portuguese guide](<https://lyntev.com/guias/checklist-publicar-site-profissional>); source revision 17 November 2026.

By the end, you can:

- Test the main journey from start to finish
- Distinguish publication blockers from later adjustments
- Prepare an approval and rollback record

In this guide

1. [Define what must work before you can publish](<https://lyntev.com/en/guides/professional-website-launch-checklist#criterio-de-pronto>)
2. [Review facts, content and button destinations](<https://lyntev.com/en/guides/professional-website-launch-checklist#conteudo-e-destinos>)
3. [Test the form through to receipt of the enquiry](<https://lyntev.com/en/guides/professional-website-launch-checklist#testar-formulario>)
4. [Try the website with other ways of navigating](<https://lyntev.com/en/guides/professional-website-launch-checklist#telemovel-e-acessibilidade>)
5. [The 12 checks for your publication](<https://lyntev.com/en/guides/professional-website-launch-checklist#lista-de-verificacao>)
6. [Separate blockers, corrections and improvements](<https://lyntev.com/en/guides/professional-website-launch-checklist#decidir-publicacao>)
7. [Record approval and confirm publication](<https://lyntev.com/en/guides/professional-website-launch-checklist#ficha-publicacao>)
8. [Sources and criteria](<https://lyntev.com/en/guides/professional-website-launch-checklist#fontes>)

## Define what must work before you can publish

Describe the beginning, action and evidence of completion for the main journey. On a services website: open a page, choose the service, complete the form and confirm receipt. In a shop: choose, check delivery and pay. For an appointment: check availability, book and receive confirmation.

List the pages and functions supporting that journey. A button that opens WhatsApp is not the same as automatic appointment booking. Test the essentials first: a lost enquiry, an incorrect price or a payment for the wrong amount requires correction before publication.

The journey that needs evidence

1. **Understand**

  The visitor identifies the offer, terms and next action.
2. **Act**

  They can complete, choose or get in touch.
3. **Confirm**

  They receive a message that matches the result.
4. **Follow up**

  The team finds the request and knows what to do.

## Review facts, content and button destinations

Read as someone who does not yet know the company. Does the heading identify the activity? Do the services explain what is included? Check contact details, opening hours, areas served, prices and terms against approved sources. Look for provisional copy, photographs without permission, empty links and contradictory information.

Open every important action. For an email button, check the recipient; for a WhatsApp button, the number and message; for a downloadable file, the content and version. If you are replacing a website, inventory useful old addresses and decide the destination of each one. A page that has moved should redirect to equivalent content when it exists, rather than sending everything to the homepage.

- [Organise the materials before review](<https://lyntev.com/en/guides/prepare-a-website-brief>)

## Test the form through to receipt of the enquiry

A success message on the screen does not, by itself, prove that the request was saved or the notification arrived. Agree an identified test with the team, using fictitious data and a controlled test email inbox. Confirm the record at the destination, fields received, confirmation displayed and who follows up the reply. Do not send real personal data just to try it out.

Repeat the journey with an empty required field, an invalid email address and a simulated network error in a test environment. The interface should explain the problem and allow correction without unnecessarily erasing what the person wrote. Also check prevention of duplicate submissions. For payments, use the provider’s test environment and its fictitious payment methods; a real charge is not needed for this review.

Test the form through to receipt of the enquiry

| Situation | What to observe | Evidence to keep |
| --- | --- | --- |
| Valid request | Confirmation and record at the correct destination | Test reference and fields received |
| Invalid field | Error linked to the field, with useful instructions | Steps and message displayed |
| Temporary failure | Clear status and a way to recover | Controlled trial result |
| Repeated submission | Defined behaviour for duplicates | Number of records created |

- [W3C: instructions, validation and notifications in forms](<https://www.w3.org/WAI/tutorials/forms/>)

## Try the website with other ways of navigating

Open the website on a phone and computer. Observe long headings, menus, tables, fields, error messages and fixed elements while scrolling. Enlarge the text and confirm you can still read and act. Simulating width in a browser helps find problems, but should be accompanied by a test on a real device, especially for essential journeys.

Move through controls with Tab, Shift+Tab and Enter. Focus must be visible, follow an understandable order and return to the appropriate point after closing a dialogue. Check field names, alternatives for informative images, contrast and behaviour with reduced motion. These initial checks find common barriers; a complete accessibility assessment requires a more extensive analysis.

- [W3C: initial accessibility checks](<https://www.w3.org/WAI/test-evaluate/easy-checks/>)

## The 12 checks for your publication

Tick each item after carrying it out. Record the page, date and evidence in the final worksheet; explain why any items do not apply. This list supports approval and does not replace specialist assessments of accessibility, security or legal compliance.

Tick each item after checking it. The list does not analyse the website automatically. Your selections are temporary and are not saved.

  **Content and terms approved**Check names, contact details, services, prices and images against the version approved by the company.**Main journey completed**Start on an entry page and finish with the action the website should facilitate.**Request received at its destination**Confirm the record and notification with an identified test; do not stop at the screen message.**Errors and repetition handled**Try invalid fields and confirm how to recover from a failure or repeated submission.**Mobile and zoom reviewed**Check text, menus, forms and fixed elements, including while scrolling.**Keyboard and focus usable**Move through actions without a mouse; confirm visible focus and a way out of dialogues.**Images and motion checked**Review image alternatives, necessary captions and the reduced-motion preference.**Domain and HTTPS correct**Open the public address and intended variants; confirm the certificate and final destination.**Indexing decided for each page**Check canonicals, sitemap and exclusion rules; keep private areas protected by access controls.**Resources and privacy information reviewed**Inventory forms, external services and storage; confirm the intended behaviour before and after choices.**Loading and interaction measured**Keep a test’s conditions and results; also test the menu and form after loading.**Responsibilities and rollback defined**Record who approves, who follows up requests and how to restore the previous version if a failure occurs.

## Separate blockers, corrections and improvements

In a fictitious example, a maintenance company finds three situations: the form sends to an old inbox, a heading breaks poorly on mobile and a photograph could be framed better. All three deserve attention, but they do not have the same impact. Recording priority and ownership prevents an aesthetic discussion from hiding a functional problem.

Classify by the specific impact: a heading covering the submit button blocks the journey; a less elegant line break may be able to wait. After correcting, repeat the test and the following step. If you changed the form, confirm receipt again.

Separate blockers, corrections and improvements

| Priority | Example | Decision |
| --- | --- | --- |
| Blocks the journey | Lost enquiries, unauthorised access or incorrect terms | Correct and repeat the test before publishing |
| Makes use difficult | Ambiguous label or difficult reading on a screen | Assess impact and correct with an assigned owner |
| Presentation improvement | Image framing without loss of content | Record and plan after functional problems |

## Record approval and confirm publication

Keep the approved version, results and rollback method. After publishing, open the public address in a new visit, recheck the domain and essential pages, repeat the main journey and confirm receipt of the request. Confirm that changes reached the hosting service and do not depend on old files stored in the browser. Choose someone responsible for initial follow-up and a date to review requests received.

### Worksheet for your project

```
Website and public address:
Approved version and date:
Person responsible for approval:
Main journey tested:
Devices, browser and conditions:
Test request reference and confirmed destination:
Completed checks and their evidence:
Items not applicable and reason:
Open problems, priority and owner:
How to restore the previous version:
Checks repeated after publication:
Who follows up enquiries and until when:
Date of the next review:
```

- [How to measure and improve speed](<https://lyntev.com/en/guides/improve-website-speed>)
- [How to prepare discovery in Google](<https://lyntev.com/en/guides/help-google-find-understand-website>)

## Sources and criteria

Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.

- [W3C: verificações iniciais de acessibilidade](<https://www.w3.org/WAI/test-evaluate/easy-checks/>)
- [W3C: formulários acessíveis](<https://www.w3.org/WAI/tutorials/forms/>)
- [Lyntev: aprovação e publicação](<https://lyntev.com/en/help/approve-and-publish-your-website>)

## Continue to your next decision.

- [Prepare your website brief](<https://lyntev.com/en/guides/prepare-a-website-brief>)
- [How to approve and publish a Lyntev website](<https://lyntev.com/en/help/approve-and-publish-your-website>)
- [Explore the website creation service](<https://lyntev.com/en/website-design>)

[Explore the guide library](<https://lyntev.com/en/guides>)

## Explore the research behind this decision.

Articles with sources, clearly identified examples and worksheets for assessing websites, AI customer service and business management systems.

[Explore all articles](<https://lyntev.com/en/research>)

Experience and measurement · About 12 min

### [Your website gets visits. Why aren't you receiving enquiries?](<https://lyntev.com/en/research/website-visits-without-enquiries>)

A method for finding obstacles between a visit and an enquiry: audience, offer, forms, performance and measurement, with a practical observation guide.

## Would you like to apply this to your business?

Send us your worksheet or explain what you need to improve. We help you choose the next step for your project.

- [Lyntev assistant Immediate answers about services, prices and timescales, with a cost estimate. Read the assistant guide](<https://lyntev.com/en/help/ai-assistant>)
- [WhatsApp +351 928 412 891. The message is only sent when you confirm it in WhatsApp. Write on WhatsApp](<https://wa.me/351928412891?text=Hello!%20I%20came%20from%20the%20Lyntev%20website%20and%20would%20like%20to%20discuss%20a%20project.>)
- [Form Describe what you need and receive the reply by email. Complete the form](<https://lyntev.com/en/contact>)
- [Email contacto@lyntev.com Send an email](<mailto:contacto@lyntev.com?subject=Request%20for%20information>)

![Wellinton Oliveira](<https://lyntev.com/media/autores/wellinton-oliveira.webp>)

Written by

[Wellinton Oliveira](<https://lyntev.com/en/company>)

CEO of Lyntev

Technology with context, original analysis and sources you can consult.
