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. Updated on .
About 5 minutes to read.

From review to publicationA process with approval criteria at every stage.

Translation published on . Original Portuguese guide; source revision .

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

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.

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
SituationWhat to observeEvidence to keep
Valid requestConfirmation and record at the correct destinationTest reference and fields received
Invalid fieldError linked to the field, with useful instructionsSteps and message displayed
Temporary failureClear status and a way to recoverControlled trial result
Repeated submissionDefined behaviour for duplicatesNumber of records created

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.

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.

Website checks

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
PriorityExampleDecision
Blocks the journeyLost enquiries, unauthorised access or incorrect termsCorrect and repeat the test before publishing
Makes use difficultAmbiguous label or difficult reading on a screenAssess impact and correct with an assigned owner
Presentation improvementImage framing without loss of contentRecord 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:

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.

Wellinton Oliveira

Written by

CEO of Lyntev

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