• Pre-publish checklist

  Review the most important things teams often forget before publishing a site. Use this checklist before publishing a new website or launching a major update. It focuses on the areas that most often cause issues after going live. Before publishing Review the homepage and the main conversion pages first. Check that the page tree is correctly organized, including main pages, subpages, landings, and system pages. Make sure unfinished pages are hidden from the menu or not visibleFew readers

• 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 pointiSome readers

• Domains and URL format

  Understand how the root domain, the www version, and trailing slashes should work together. A website can often be reached through more than one version of the same domain. For example, visitors may use the root domain or the www version. Both can work, but the site should have one preferred version to keep URLs consistent. Root domain and www The root domain is the domain without www, for example: yourdomain.com The www version is a subdomain, for example: wwSome readers

• Hosting, CDN, and SSL

  Understand what happens after a site is connected to its final domain. When a site is published, the platform hosts the website and serves its public pages, assets, and media through managed infrastructure. You do not need to configure or maintain servers manually. Hosting The platform manages the hosting environment for the website. Once the domain points to the platform, public pages can be served from the final domain. Your responsibility is usually to configure the required DNS reFew readers