> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.banana.tech/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to publish a website

### Publish a site by coordinating the final domain setup and launch validation.

Once the site is ready to go live, coordinate the launch with your project or support team. They will provide the exact DNS records that must be configured for the domain.


## Before publishing

Before starting the domain change, make sure the site has been reviewed and is ready to launch.
Check the main pages, languages, booking links, forms, SEO settings, redirects, integrations, and tracking setup before pointing the domain to the platform.


## Point the domain to the platform

To connect the final domain, the DNS provider must be updated with the records provided for your site.

The usual setup includes:
* A root domain record for `@`, pointing to the IP address provided by the platform.
* A `www` subdomain configured as a `CNAME`, pointing to the host provided by the platform.
* A certificate validation `CNAME`, used to validate the SSL certificate.

The exact values are different for each project, so always use the DNS records provided for your site.


## Root domain and `www`

The root domain and the `www` version may use different DNS record types. In many DNS providers, the root domain cannot point to a `CNAME`. For that reason, the platform may provide an IP address for the root domain and a `CNAME` for the `www` subdomain. This is normal and does not mean both records need to resolve to the same IP address.


## DNS propagation

After DNS records are updated, propagation time can vary. In many cases, changes propagate in around one hour, but it can sometimes take up to 24-48 hours depending on the DNS provider and previous configuration.


## SSL certificate validation

The SSL certificate can only be validated after the domain is pointing to the platform. For that reason, the website may be reachable before the SSL certificate is fully active. Once the DNS change has been made, notify your project or support team so they can monitor propagation and complete the SSL validation as soon as possible.

|| When possible, schedule domain changes during working hours. This makes it easier to monitor DNS propagation and complete SSL validation quickly.


## After publishing

After the site is live, review the final domain in the browser.

Check that:
* The root domain loads correctly.
* The `www` version works as expected.
* HTTPS is active.
* Main pages load correctly.
* Redirects work.
* Booking links and forms work.
* Tracking and integrations load correctly.