How to connect a domain to WordPress – a beginner’s guide

You’ve bought your domain name. You’ve got your WordPress hosting sorted. Now you need to connect the two – so that when someone types your domain into a browser, they land on your WordPress site.

This guide on how to connect a domain to WordPress covers exactly that process, and it’s one of those tasks that sounds more technical than it actually is. Most people get it done in about ten minutes. No coding skills are required, no server knowledge is needed, and if you follow the steps in this guide carefully, it will work the first time.

Let’s get it sorted.

connect-your-domain-to-wordpress-step-by-step

First – understand what you’re actually doing

Before the steps, a quick explanation of what connecting a domain actually involves. This will make everything else make more sense.

Your domain name and your web hosting are two separate services – usually bought from two different companies. Your domain registrar knows your website’s address. Your hosting provider knows where your website lives. Connecting a domain to WordPress is the process of telling your domain registrar to point your address to your hosting provider’s servers.

The mechanism for this is called nameservers. Nameservers are the internet’s address book – they translate your domain name into the server’s IP address so browsers know where to send visitors.

When you connect a domain to WordPress, you’re updating the nameservers on your domain to point to your hosting provider. After that, anyone who types your domain into a browser gets sent to your host’s servers – and from there, to your WordPress site.

That’s it. That’s all that’s happening.

The two main scenarios

How you connect your domain to WordPress depends on where you bought your domain.

Scenario A – You bought your domain through your hosting provider

If you bought your domain directly through Bluehost, SiteGround, or Hostinger when you signed up for hosting, the domain is almost certainly already connected. Your registrar and your host are the same company, so they handle the connection automatically.

Check by visiting your domain in a browser. If your WordPress site loads – even if it’s just the default installation – you’re already connected. Skip to the “forcing HTTPS” section below, and you’re done.

Scenario B – You bought your domain from a separate registrar (Namecheap, GoDaddy, Google Domains, etc.)

This is the scenario that requires action on your part. Your domain registrar doesn’t know where your WordPress site is hosted, so you need to tell it. This guide will walk you through exactly how to do that.

Step 1 – Find your hosting provider’s nameservers

The first thing you need is your hosting provider’s nameserver addresses. These are provided by your host and typically look something like:

ns1.bluehost.com and ns2.bluehost.com

or

ns1.siteground.net and ns2.siteground.net

Where to find your nameservers:

Bluehost: Log in to your Bluehost account. Go to Domains → My Domains. Click on the domain you want to connect (or any domain – you’re looking for the nameserver information, not domain-specific settings). The nameservers are displayed in the domain management section. Alternatively, check your Bluehost welcome email – nameserver details are often included there.

SiteGround: Log in to your SiteGround account. Go to Websites → your site → Site Tools. Under the Domain section, look for nameservers. SiteGround’s nameservers are typically ns1.siteground.net and ns2.siteground.net – You can also find the specific ones for your account in your welcome email.

Hostinger: Log in to your Hostinger account. Go to Hosting → Manage → DNS / Nameservers. Your nameservers are displayed here.

Other hosts: Log in to your hosting account dashboard and look for a section called DNS, Nameservers, or Domain Settings. If you can’t find it, contact your host’s support – nameserver details are a standard thing to ask for, and any support agent will know them immediately.

Make a note of both nameservers. You’ll need them in the next step.

Step 2 – Update your nameservers at your domain registrar

Now go to the place where you bought your domain and update the nameservers to point to your hosting provider.

If your domain is registered with Namecheap:

  1. Log in to your Namecheap account at namecheap.com
  2. Click Domain List in the left sidebar
  3. Find your domain and click Manage
  4. Under the Nameservers section, change the dropdown from “Namecheap BasicDNS” to Custom DNS
  5. Enter your hosting provider’s nameservers in the fields provided – one per field
  6. Click the green tick/checkmark to save

If your domain is registered with GoDaddy:

  1. Log in to your GoDaddy account
  2. Click your name in the top right and select My Products
  3. Find your domain and click DNS
  4. Scroll down to the Nameservers section and click Change
  5. Select Enter my own nameservers (advanced)
  6. Enter your hosting provider’s nameservers
  7. Click Save and confirm the change

If your domain is registered with Google Domains / Squarespace Domains:

  1. Log in to your account at domains.google.com
  2. Click on your domain name
  3. In the left sidebar, click DNS
  4. Under Name servers, click Switch to custom name servers
  5. Enter your hosting provider’s nameservers
  6. Click Save

If your domain is registered elsewhere:

The process is broadly the same across most registrars: log in, find the DNS or nameserver settings for your domain, change from the default nameservers to custom, enter your hosting provider’s nameservers, and save. If you’re stuck, your registrar’s help documentation or support team will walk you through it.

Step 3 – Wait for DNS propagation

Once you’ve saved the nameserver change, you need to wait.

DNS propagation is the process of the change spreading across the Internet’s global network of servers. It typically takes between 30 minutes and a few hours – though in some cases it can take up to 48 hours for the change to be visible everywhere in the world.

During this time, some visitors to your domain might see the old version (or nothing at all), while others see the new version. This is normal. It doesn’t mean something has gone wrong.

How to check if propagation is complete:

Visit whatsmydns.net and enter your domain name. This tool checks your domain’s DNS records from multiple locations worldwide and shows whether the nameserver change has propagated. When most locations show your new hosting provider’s nameservers, you’re good.

You can also simply visit your domain in a browser – if your WordPress site loads, propagation is complete for your location.

While you’re waiting: Don’t make any further changes to your nameservers or DNS records. Multiple conflicting changes slow down propagation and can create confusion.

Step 4 – Add your domain to WordPress

Once propagation is complete and your domain points to your host, you may need to add the domain to your WordPress installation.

If WordPress was installed during your hosting setup and the domain is already associated with your hosting account, this step is usually automatic – your WordPress site simply starts loading when someone visits your domain.

If your WordPress installation is showing a different domain or you need to add your domain manually:

In your hosting dashboard:

Bluehost: Go to My Sites → Create Site or connect the domain through the domain settings in your dashboard.

SiteGround: Go to Websites → Add Website and follow the prompts to associate your domain with your WordPress installation.

Hostinger: Go to hPanel → Websites and add or update the domain associated with your site.

In WordPress itself:

If WordPress is installed but showing the wrong URL:

  1. Log in to your WordPress dashboard at yourdomain.com/wp-admin
  2. Go to Settings → General
  3. Check that both the WordPress Address (URL) and Site Address (URL) show your correct domain with https://
  4. Update if needed and click Save Changes

Step 5 – Activate your SSL certificate

Once your domain is connected and your WordPress site is loading, activate your SSL certificate. This gives your site the padlock in the browser bar and the https:// prefix – essential for any modern website.

Most hosts automatically enable SSL once your domain is connected and propagated. Check by visiting your site – if the URL shows https:// and there’s a padlock, SSL is already active.

If SSL isn’t showing:

In your hosting dashboard, find the SSL section and activate it manually. On Bluehost, this is under My Sites → your site → Security. On SiteGround, it’s under Security → SSL Manager. On Hostinger, it’s under SSL in the main hPanel menu.

SSL can take a few minutes to activate after requesting it. Refresh your browser after a few minutes if it doesn’t appear immediately.

Force HTTPS across your site:

Once SSL is active, make sure your whole site uses https:// rather than http://. In your WordPress dashboard, go to Settings → General and update both URLs to use https://. Click Save Changes.

You may also want to install a plugin like Really Simple SSL (free), which handles the redirect from HTTP to HTTPS automatically and fixes any mixed content warnings.

Step 6 – Test everything

Once your domain is connected and SSL is active, do a quick check to make sure everything is working as expected.

Visit your domain – type it into a browser and confirm your WordPress site loads.

Check for the padlock – the padlock icon should appear in the browser bar next to your URL. If it doesn’t, SSL isn’t fully active, or there’s a mixed content issue (some elements on the page are loading over HTTP rather than HTTPS). Really Simple SSL handles this automatically.

Test your pages – click through your main pages and posts to make sure everything loads correctly.

Check your admin access – confirm you can still log in yourdomain.com/wp-admin with your credentials.

Send yourself an email – if you have a contact form, submit it and make sure you receive the email. Domain changes can occasionally affect email settings if your email was configured through your registrar.

Common problems and how to fix them

My domain still shows the old website after 24 hours

DNS propagation occasionally takes up to 48 hours, but if it’s been longer than that, something has likely gone wrong with the nameserver update. Go back to your domain registrar and check the nameservers are saved correctly – it’s easy to accidentally save the wrong nameservers or miss a step in the process. Also, try clearing your browser cache, which can show you a cached version of the old site even after the DNS has changed.

My domain shows a “site not found” or “server not found” error

This usually means one of three things: the nameserver update hasn’t propagated yet, the nameservers were entered incorrectly, or WordPress hasn’t been properly installed on your host. Check your nameservers at your registrar, verify them against the nameservers your host provided, and confirm WordPress is installed in your hosting dashboard.

I’m getting a “this site can’t provide a secure connection” error

SSL hasn’t been activated or hasn’t propagated yet. Go to your hosting dashboard and activate SSL for your domain. Wait a few minutes and try again. If the problem persists, contact your host’s support – they’ll activate it manually.

My site loads, but shows “Not Secure” instead of the padlock

Mixed content issue – some elements on your page are loading over HTTP rather than HTTPS. Install Really Simple SSL to fix this automatically, or check your WordPress settings are showing https:// in both URL fields under Settings → General.

My WordPress dashboard is showing a different URL from my domain

Go to Settings → General in your WordPress dashboard and update both URL fields to your correct domain with https://. If you can’t access your dashboard because the URL is completely wrong, you may need to update the URLs directly in your database via your hosting control panel – your host’s support team can help with this.

My contact form emails stopped arriving after the domain change

Domain changes can occasionally affect MX records (which handle email). Check your email MX records at your domain registrar and make sure they’re still pointing to your email provider. If you use Gmail or another third-party email service, those MX records should be unchanged – but it’s worth verifying.

What if you want to use Cloudflare?

Many WordPress users add Cloudflare between their domain registrar and hosting provider for performance and security benefits.

If you want to use Cloudflare, the process is slightly different:

  1. Sign up for a free Cloudflare account at cloudflare.com
  2. Add your domain to Cloudflare
  3. Cloudflare will scan your existing DNS records and import them
  4. Cloudflare will give you two nameservers to use
  5. Update your domain registrar’s nameservers to point to Cloudflare’s nameservers (rather than your host’s)
  6. Cloudflare then forwards traffic to your hosting provider

The benefit is that Cloudflare acts as a middleman – caching your site, blocking malicious traffic, and generally improving performance. The free plan is genuinely useful.

If you’re not sure whether you need Cloudflare at this stage, you don’t. You can add it later without disrupting your site.


Your domain is connected – what next?

With your domain pointing to your WordPress site and SSL active, you’re ready to build.

If you haven’t already set up the essential pages, installed your key plugins, and connected Google Search Console, now is the time. Our full WordPress setup guide walks you through everything.

Read: How to start a WordPress website for beginners →

If you’re still deciding which hosting provider is right for you, our quiz will match you to the best option based on your budget and site type.

Take the WordPress hosting quiz →

Frequently asked questions

How do I connect a domain to WordPress? Find your hosting provider’s nameservers, log in to your domain registrar, switch from the default nameservers to custom nameservers, and enter your host’s nameservers. Wait for DNS propagation (usually a few hours), then activate SSL. The manual steps take about ten minutes; the whole process is typically done within a few hours.

How long does it take to connect a domain to WordPress? The manual steps — updating nameservers at your registrar — take about ten minutes. DNS propagation then takes anywhere from 30 minutes to 48 hours. Most people see their site loading on the new domain within a few hours.

Do I need technical knowledge to connect a domain to WordPress? No — the process involves logging in to two accounts, finding nameserver settings, and copying and pasting two addresses. No coding or technical knowledge required.

Can I connect a domain I already own to a new hosting provider? Yes — this is exactly what this guide covers. Update the nameservers at your domain registrar to point to your new hosting provider. Your domain stays where it is; you’re just redirecting it.

What’s the difference between nameservers and DNS records? Nameservers tell the internet which company manages your domain’s DNS records. DNS records (like A records, CNAME records, and MX records) are the individual settings within those — controlling where your website traffic goes, where your email goes, and so on. For most beginners, updating nameservers is all you need to do.

Can I use the same domain with multiple WordPress sites? No — a domain can only point to one place at a time. You can have multiple WordPress sites on the same hosting account, but each needs its own domain.

Will connecting my domain affect my email? If your email is hosted through the same provider as your old domain settings, changing nameservers can affect it. Make sure your email MX records are carried over correctly — most registrars let you import DNS records from a scan, or your new host’s support team can advise.

Howtostartyourwebsite.com may get paid commission for purchases made after clicking a link on this page. This website is for inspiration purposes only. The content provided is meant to spark creativity and ideas, not to serve as professional advice or as endorsement.

Similar Posts