How to Publish a Website: Domain, Hosting, DNS & Go-Live Steps WhatsApp Ashish

Go-live checklist · published 6 Oct 2026

How to publish a website: the go-live checklist for business owners

Designing the pages is the visible half of the job. Publishing is the half that decides whether the site opens on a customer’s phone, shows a padlock, appears in Google and still belongs to you next year. Here is the sequence, in the order that avoids rework.

Quick answer

To publish a website you need four things working together: a registered domain name, a hosting account or platform where the files or CMS live, DNS records that point the domain at that hosting, and an SSL certificate so the site loads over HTTPS.

The practical order is to register the domain in your own account, choose hosting that matches the build (static files, WordPress or a hosted platform such as Shopify), connect the domain through DNS, upload the files or install the CMS, switch on HTTPS with a redirect, test every page and form on a phone, then submit the sitemap in Google Search Console and link the site from your Business Profile.

Ask Ashish about your own site See pricing

The steps apply whether you built the site yourself, used a builder or hired a developer. Where a platform does a step for you, it says so.

What publishing a website actually involves

Four separate services that have to agree with each other.

A website that “is ready” on a developer’s laptop or inside a builder’s preview is not yet published. Publishing means a real domain resolves to a real server that serves the real pages over a secure connection. That involves a registrar (who sells the domain), a host (who stores and serves the site), DNS (the records that connect one to the other) and a certificate authority (who issues the SSL certificate, usually automatically through the host).

Builders like Wix and platforms like Shopify bundle hosting and SSL, so publishing there is mostly domain and DNS work. WordPress and custom sites need every step. Knowing which model you are on tells you which steps below are already done.

One principle runs through all of it: every account should be created with the business’s own email address and paid from the business’s own card. The ownership checklist explains why, and the developer-disappeared guide shows what happens when it is skipped.

Step 1: Register the domain in your own name

The one step that is hard to undo if done wrong.

Choose a registrar, search for the name and register it from an account that belongs to the business. A .in domain signals an Indian business clearly; a .com is the safer choice if you export or expect international buyers. Register for multiple years if you can and switch on auto-renewal, because an expired domain is the most common way a working website disappears.

Turn on two-factor authentication, confirm the recovery email and phone are the owner’s, and note the renewal date in the business calendar. If a developer is handling this for you, the account should still be yours; they can be given delegated or DNS-level access. The domain guide covers registrars and renewals in more depth.

Step 2: Choose hosting that matches the build

Static files, a PHP CMS and a hosted store need three different things.

Static site. Plain HTML, CSS and images can live on almost anything: a basic shared plan, or free static hosts such as Cloudflare Pages, Netlify or GitHub Pages that also allow a custom domain. Requirements are minimal; reliability and a nearby or global edge network matter more than CPU.

WordPress or other PHP CMS. You need PHP and a MySQL database, enough memory for the plugins you actually run, daily backups and a one-click SSL. Shared hosting from an Indian or international provider is fine for most business sites; managed WordPress hosting costs more and does the updates and backups for you. The GoDaddy vs Hostinger comparison is a starting point for the two providers Indian owners ask about most.

Hosted platform. Shopify, Wix and similar include hosting in the subscription. There is nothing to choose, but there is also nothing to move if you leave.

Whichever you pick, open the hosting account in the business’s name too. The static vs dynamic guide explains how the build type drives this choice.

Step 3: Connect the domain to the hosting (DNS)

Two ways to do it; one is simpler, one is more flexible.

Option A: change nameservers. In the registrar, replace the default nameservers with the ones your host gives you. The host then controls all DNS, which is simple and what most hosting guides assume. The downside is that your email and any other services must also be configured at the host.

Option B: keep DNS at the registrar and add records. Add an A record pointing the bare domain at the host’s IP address, and a CNAME pointing www at the host’s address. This keeps email and other records where they are and is the better choice if the business already uses Google Workspace or Zoho Mail on the domain.

Changes can take from a few minutes to about 48 hours to spread across the internet. Do not panic if the site opens on one phone and not another during that window. If it still does not open after two days, work through the website not opening checklist.

Step 4: Upload the site or install the CMS

Where the pages actually arrive on the server.

For a static site, upload the files to the host’s public folder (often called public_html) by FTP, the host’s file manager, or by connecting a Git repository on a static host. Make sure the homepage file is named index.html and that file paths match the live domain rather than a local folder.

For WordPress, use the host’s one-click installer or upload the files and run the installer, create the database, then import the content and theme from the development copy. Update the site URL settings to the real domain, regenerate permalinks and check that uploaded images point at the live address rather than a staging one.

On a hosted platform this step is simply pressing publish once the domain is connected.

Step 5: Switch on HTTPS and force the redirect

The padlock is not optional for a business site.

Most hosts issue a free Let’s Encrypt certificate automatically once DNS points at them; look for an SSL section in the hosting panel and enable it for both the bare domain and www. Then set a redirect so that every http:// request and the non-preferred www or non-www version lands on one canonical HTTPS address. On Apache hosting that is a few lines in the .htaccess file; most panels have a toggle.

After enabling, open the site in a private browser window and check for the padlock on several pages. A warning or a “Not secure” label after SSL is installed usually means mixed content: an image or script still loading over plain HTTP. The not-secure fix guide walks through finding and fixing it.

Step 6: Test before you tell anyone

Fifteen minutes here saves embarrassing messages later.

  • Open every page on a phone using mobile data, not office Wi-Fi.
  • Tap every call, WhatsApp and email button and confirm it opens the right app with the right number or address.
  • Submit the contact form and confirm the message reaches the business inbox, not the developer’s.
  • Type a wrong address such as yourdomain.in/xyz and confirm a proper not-found page appears rather than a server error.
  • Check the title shown in the browser tab on each page; placeholder titles are common leftovers.
  • Run the homepage through a speed test and look at what loads first on mobile.
  • Search the site text for “lorem”, “coming soon”, the old staging address and any phone number that is not yours.

If the site is a redesign replacing an older one, confirm every old URL redirects to its new equivalent before the old site is switched off. The redesign service page describes why that redirect map matters.

Step 7: Tell Google and your customers

Publishing is not the same as being found.

Add the site to Google Search Console, verify ownership through DNS or an HTML file, and submit the sitemap, usually at yourdomain.in/sitemap.xml. Bing Webmaster Tools accepts the same sitemap. Neither guarantees ranking, but both show you whether Google can crawl the pages and what it finds, which is the first thing to check if the site is not showing on Google after a few weeks.

Then update every place customers already look: the Google Business Profile website field, Instagram and Facebook bios, the WhatsApp Business profile, email signatures, invoices and visiting cards. Those links bring the first real visitors long before organic search does.

Install analytics only if someone will look at it, and configure it in the business’s own Google account so the history stays with you.

After launch: renewals, backups and access

The site is published. Keeping it published is a small recurring job.

Put the domain and hosting renewal dates in a shared calendar with the account logins in a password manager the owner controls. If the site runs on WordPress, decide now who applies updates and checks backups each month; a site nobody maintains is a site somebody will eventually break into. The maintenance service page sets out what a defined retainer covers, and the maintenance cost guide shows what to expect to pay.

Finally, write down the handover: registrar, host, DNS location, CMS login, email provider, analytics and Search Console owners. Five lines in a document today saves a week of recovery later.

Questions

Publishing questions

How long does it take to publish a website?
If the pages are ready and the domain is registered, the technical steps take an afternoon. DNS changes can take from minutes to about 48 hours to spread, so allow two days before relying on the address publicly.
Can I publish a website without buying hosting?
Static sites can be published free on Cloudflare Pages, Netlify or GitHub Pages with your own domain. WordPress and other database-driven sites need paid hosting or a managed platform.
Do I need to publish with www or without?
Either works. Pick one, make it the canonical address, and redirect the other to it so search engines and visitors see a single version of every page.
Why does my published site show “Not secure”?
Either the SSL certificate is not yet active for that exact address, or a page is loading an image or script over plain HTTP. Enable SSL for both domain versions, force the HTTPS redirect, and fix mixed content.
How do I get my new website on Google?
Verify the site in Google Search Console and submit the sitemap. Google will crawl and index the pages over the following days or weeks. Ranking for competitive searches takes longer and depends on content and links.
Who should own the hosting and domain accounts?
The business. Create them with a business email and card, and give the developer delegated access if they need it. This keeps the site recoverable if the working relationship ends.

Next step

Want the launch handled properly?

Every Overbuilt project ends with a documented go-live: accounts in your name, HTTPS forced, forms tested and Search Console set up. Tell Ashish what you are launching.