Web Design & Development · 8 min read · 1,780 words

How to publish a website: from domain name to live site

How to publish a website: from domain name to live site

Quick answer

To publish a finished website, make sure the domain is registered in your name, choose hosting, move the site files and database onto that hosting, point the domain at it through DNS, switch on an SSL certificate, run final checks on the live address, then submit it to Google Search Console. Afterwards, keep it updated and backed up.

The moment a website is “finished” is often the moment people get stuck. The pages look right on the designer’s preview link, everyone has signed them off, and then nobody is quite sure how it becomes the site customers see when they type the address. A kitchen fitter in Swansea might have a domain bought years ago by a nephew, a new site sitting on a developer’s test server, and an email account that must not break in the process.

This guide walks through the whole journey from built to live, in the order it should happen, and explains which parts you can do yourself and which are best handed over. Where a step has its own detailed guide, we link to it rather than repeat it.

Six steps for publishing a finished website, from owning the domain to Search Console and upkeep
Most stalled launches trace back to step one: who owns the domain.

The journey at a glance

Stage What happens Who usually does it
Domain Register or confirm ownership of the address You, in your own name
Hosting Choose where the site will live You, with advice
Move the site Copy files and database to the hosting Your developer or host
DNS Point the domain at the hosting Whoever controls the domain
SSL Switch on the padlock and HTTPS Usually the host
Checks Test forms, links, mobile, speed Developer and you
Google Verify the site and submit a sitemap Developer or you
Upkeep Updates, backups, monitoring You or a managed plan

Step 1: make sure you own the domain

Before anything else, check who the domain is registered to. It should be your business, with your email address on the account and your card paying the renewal. Domains registered by a former web designer, a relative or an old employee are one of the most common reasons launches stall. Our guide on what to do when a developer owns your domain explains how to get it back.

If you have not bought the domain yet, choose a short, memorable name and buy it through a reputable registrar. UK domains ending in .uk and .co.uk are run by Nominet and sold through accredited registrars. Our UK domain names guide covers choosing and registering one.

Step 2: choose where the site will live

Hosting is the server that stores your website and sends it to visitors. What you need depends on how the site was built:

  • Website builders such as Wix or Squarespace include hosting. Publishing is a button, and you only need to connect the domain.
  • WordPress sites need hosting with PHP and a database. Shared hosting suits most small sites; managed WordPress hosting adds updates, backups and security.
  • Static HTML sites can live almost anywhere, including very low-cost static hosting.

Choose UK-based hosting if your customers are in the UK, and check that backups, SSL and support are included rather than extras. Our guide to website hosting costs compares typical options and what you get at each level.

Step 3: move the site onto the hosting

If the site was built on a test server or a developer’s computer, it now has to be copied to the live hosting. For a static site, that is uploading the files. For WordPress, it means copying the files and the database, then updating the site’s address from the test address to the real one, so links and images point to the right place. The WordPress project’s guide to migrating WordPress explains what is involved.

This step is where most things go wrong when done in a hurry: missing images, broken links, forms that send to the developer’s inbox. If you are replacing an existing site, there is also the old site’s content and search visibility to think about; our guide to website migration covers moving from one site to another without losing ground.

Step 4: point the domain at the hosting

Your domain is connected to your hosting through DNS settings, usually by changing the domain’s nameservers to the host’s, or by updating specific records to point at the server. Changes can take a little while to spread across the internet, so plan the switch for a quiet time.

The detail depends on where your domain and email live, and getting it wrong can stop email working as well as the website. Our step-by-step guide on connecting a domain to a website covers the records and the order to change them, including how to keep email running throughout.

Step 5: switch on SSL

An SSL certificate makes your site load over HTTPS with the padlock in the browser. Without it, browsers warn visitors that the site is not secure, and forms that collect personal details should never run without it. Many hosts now include free certificates from Let’s Encrypt, which renew automatically.

Once the certificate is active, make sure every visit goes to the HTTPS version of the site, including the version without “www”. If visitors still see a warning, our guide to a website showing not secure explains the usual causes.

Step 6: test the live site properly

Do not assume the live site behaves exactly like the preview. Before you announce it, check on the real address:

  1. Every page loads, on a phone and a computer.
  2. Contact and quote forms send to the right inbox, and confirmation emails arrive.
  3. Phone numbers and email links work when tapped.
  4. No links still point to the test address.
  5. Images are sharp and pages load quickly on mobile data.
  6. Any “discourage search engines” setting used during the build has been switched off.
  7. Analytics is recording visits.

Our full website launch checklist goes through every check in more detail.

Step 7: tell Google the site exists

Search engines will find a new site eventually, but you can speed things up. Verify the site in Google Search Console, submit its sitemap, and use the inspection tool to request indexing of the homepage and key service pages. Search Console also tells you about problems Google finds, which is invaluable in the first few weeks.

If you are replacing an old site, set up redirects from old page addresses to their new equivalents before launch, so visitors and search engines are sent to the right place. If the site still does not appear after a few weeks, our guide to a website not showing on Google covers the usual causes.

Step 8: keep it running

Publishing is not the end. A live website needs regular care:

  • Updates: WordPress core, themes and plugins need updating to stay secure.
  • Backups: daily, stored away from the server, and tested now and then.
  • Monitoring: an alert if the site goes down or the certificate stops renewing.
  • Renewals: domain and hosting renewals on a card that will not expire unnoticed.
  • Content: prices, services, photos and opening hours kept current.

Our WordPress maintenance guide explains what each task involves and how often to do it.

Launch-day problems and quick fixes

Even a careful launch can hit a snag. These are the most common, and where to look first:

  • The old site still appears. DNS changes have not reached everyone yet, or your browser has cached the old version. Try another device on mobile data before assuming something is broken.
  • Email stops arriving. The domain’s email records were lost when the nameservers changed. Restore them at the new DNS host straight away.
  • Images are missing or point to the test site. The site address was not fully updated during the move. A search and replace of the old address in the database usually fixes it.
  • Forms send nothing. The live server’s email settings differ from the test server’s. Test each form and set up authenticated sending.
  • The padlock is missing on some pages. Some images or scripts still load over plain HTTP. Update those addresses to HTTPS.
  • Google shows the old pages. Redirects are missing, or Google has not recrawled yet. Check redirects, then request indexing in Search Console.

Keep the old site’s files and a backup of the new one for a few weeks after launch, so either can be restored quickly if something unexpected turns up.

A worked example: the Swansea kitchen fitter

Back to the kitchen fitter from the start of this guide. The domain was registered by a nephew years ago, so step one is getting it transferred into the business’s own account with the nephew’s help. The business then chooses UK hosting that includes SSL, daily backups and mailboxes. The developer copies the new WordPress site across, updates its address and checks the forms on a temporary link. On a quiet Sunday evening, the email records are copied to the new DNS first, then the nameservers are changed. By Monday morning the new site is live with the padlock showing, the quote form is tested, the sitemap is submitted and the old pages redirect to the new ones. Nothing about it is difficult; it simply happens in the right order.

What you can do yourself, and what to hand over

Owning the domain, choosing a host and running the final checks are well within reach for most business owners. Moving a WordPress site, changing DNS without breaking email and setting up redirects are where a mistake can take the site or your inbox offline, so many people hand those steps to their developer or host.

Our Website Management and Hosting plan is £20 a month and covers UK hosting, SSL, daily backups, security monitoring, automatic updates and up to 3 business email mailboxes, so steps 2, 5 and 8 are handled for you. If you are still at the build stage, use our website cost calculator, and see every price on our pricing page.

Free resource

Get the UK Website Project Brief Template (free)

A two-page template for briefing any UK web designer: sitemap, integrations, audience and deliverables. Cuts revision rounds in half.

No spam. UK GDPR compliant. We only use your email to send this resource, unless you tick the box to hear from us.

Frequently asked questions

What do I need to publish a website? +

A domain name registered in your name, hosting that suits how the site was built, the site files and database copied onto that hosting, DNS settings pointing the domain at it, and an SSL certificate. After launch you need someone keeping it updated and backed up. Website builders bundle hosting, so you only connect the domain.

How long does it take for a new website to go live? +

Once the site is on the hosting, connecting the domain is quick, but DNS changes can take a while to spread across the internet, sometimes several hours. Plan the switch for a quiet time and test the live address before announcing it. Appearing in Google takes longer, often days or weeks, which Search Console can help speed up.

Can I publish a website myself? +

Often, yes. Owning the domain, choosing a host and running the final checks are manageable for most owners, and website builders make publishing a button. Moving a WordPress site, changing DNS without breaking email and setting up redirects are riskier, so many people hand those steps to a developer or their host.

Why does my new website say not secure? +

Usually because the SSL certificate is not active yet, or the site is still loading some pages or images over plain HTTP. Many hosts provide free certificates that renew automatically. Once it is active, make sure every visit is sent to the HTTPS version of the site, including the address without www.

Do I need to tell Google about my new website? +

It helps. Verify the site in Google Search Console, submit its sitemap and request indexing of key pages. Check that any setting used during the build to discourage search engines has been switched off. If you replaced an old site, add redirects from old addresses to new pages before launch.

Work With Us

Need help with your brand or website?

Luxbranding is a UK online creative agency. Fixed prices, unlimited revisions, 48-hour start. Logo design from £129, websites from £299.

Ask Us a Question

Reply within one working day · No commitment