Connecting a domain to a new WordPress site is usually the last step before your website becomes publicly accessible. In a hosting or control panel environment such as Plesk, the process typically involves pointing the domain to the correct hosting account, confirming the DNS records, and making sure WordPress is installed in the right document root. If everything is set correctly, visitors who type your domain name will reach your new site instead of a placeholder page or an old installation.
This guide explains how to connect a domain to a new WordPress site, what needs to happen at the DNS and hosting level, and how to troubleshoot the most common issues. It is written for beginners, but it also includes practical checks that help prevent setup problems later.
What it means to connect a domain to WordPress
When you connect a domain to WordPress, you are linking three things:
- The domain name — for example, example.co.uk.
- The DNS settings — records that tell the internet where the domain should point.
- The hosting environment — where the WordPress files and database are stored.
A domain can be registered anywhere, while WordPress can be installed on a separate hosting account. The connection works only when the domain’s DNS records point to the correct server and the hosting panel is configured to serve the WordPress site for that domain.
If you are using managed hosting, the setup may be simplified because the hosting platform handles part of the configuration automatically. In a control panel such as Plesk, you often add the domain first, then install WordPress, and finally update the DNS records at your registrar or DNS provider.
Before you start
Make sure you have the following ready:
- Access to your domain registrar or DNS provider
- Access to your hosting control panel
- The new WordPress installation already created, or the ability to create it
- The correct IP address or nameservers for your hosting account
- SSL certificate details if HTTPS is already enabled
It also helps to know whether your domain will use:
- Nameservers provided by your hosting company, or
- DNS records managed by your registrar or a third-party DNS service
Either method can work well. The important part is to use one clear DNS setup and avoid conflicting records.
Step 1: Add the domain to your hosting account
The first task is to make sure the hosting platform recognises the domain. In many hosting panels, this is done by creating a new domain, subscription, or site entry.
In a control panel such as Plesk
In Plesk, you typically add the domain under the hosting subscription and confirm the document root, which is the folder where the website files will live. For a WordPress site, this folder usually contains the WordPress core files, themes, plugins, and uploads directory.
Check that:
- The domain name is entered correctly
- The document root points to the intended WordPress directory
- The hosting package has enough disk space and database access
If you are hosting multiple sites, make sure you do not accidentally connect the domain to the wrong subscription or directory. This is one of the most common causes of “the site shows the wrong page” issues.
If the WordPress site already exists
If WordPress has already been installed on a temporary domain or staging URL, you may need to update the site URL in WordPress after the domain is connected. This is normal when moving from a test address to the final live domain.
Step 2: Decide whether to change nameservers or DNS records
There are two common ways to connect a domain to hosting.
Option A: Use your hosting provider’s nameservers
When you change the domain to use your hosting company’s nameservers, DNS is managed by the hosting platform. This can be easier for beginners because the A records, CNAMEs, and other entries are usually configured in one place.
This option is useful if you want:
- Simpler DNS management
- Hosting and DNS in the same panel
- Less chance of mismatch between DNS and hosting
Option B: Keep DNS at your registrar or DNS provider
If you prefer to manage DNS separately, update the domain’s A record to point to your hosting server IP address. In some setups, you may also need a www CNAME record pointing to the root domain.
This option is useful if you already use:
- A third-party DNS platform
- Email services that rely on existing DNS records
- Multiple systems connected to the same domain
Either method is valid. The important thing is not to mix both approaches accidentally. If you change nameservers, DNS records at the registrar become inactive. If you keep external DNS, the hosting panel will not control the domain’s public records.
Step 3: Point the domain to the correct server
If you are using external DNS, the main record to update is usually the A record. This record should point the domain to the server IP address supplied by your hosting provider.
Typical DNS records to check
- A record for the root domain, such as example.co.uk
- CNAME record for www, often pointing to the root domain
- AAAA record if IPv6 is enabled and supported
- MX records if email is also configured on the domain
For a standard WordPress site, the root A record and the www record are usually the most important. If both are not aligned, visitors may see different behaviour depending on whether they type www or not.
Example setup:
- example.co.uk → A record → hosting IP address
- www.example.co.uk → CNAME → example.co.uk
After updating DNS, allow time for propagation. Some changes take effect quickly, but it can take longer depending on the TTL and caching at internet providers.
Step 4: Install WordPress in the correct location
Once the domain is linked to the hosting account, install WordPress in the document root that belongs to that domain. If WordPress is installed in a subfolder or in the wrong directory, the domain may not load the site as expected.
Check the installation path
In a hosting control panel, confirm the website files are placed in the correct folder. Common examples include:
/httpdocs//public_html//var/www/vhosts/domain-name/
The exact path depends on your platform. What matters is that the domain’s document root matches the folder containing the WordPress installation.
Install WordPress automatically or manually
Most managed hosting panels offer an app installer or WordPress toolkit. This is usually the fastest way to get started. The installer may create the database, set the admin account, and configure basic files automatically.
If you install WordPress manually, make sure to:
- Create the database and database user
- Upload the WordPress files to the correct directory
- Run the installation script in the browser
- Save admin credentials securely
After installation, confirm that the site loads on the domain and not only on a temporary address.
Step 5: Update WordPress site URLs if needed
If your WordPress site was first installed on a temporary domain, staging URL, or localhost setup, the WordPress Address and Site Address may still point to the old location. In that case, you need to update the URLs so the site uses the new domain.
Where to change the URL
You can usually update the site URL in one of these places:
- The WordPress dashboard under general settings
- The hosting panel’s WordPress toolkit or site management tools
- The database, if the dashboard is not accessible
After changing the URL, check the following:
- Images and internal links load correctly
- The login page uses the new domain
- There are no redirect loops
If the site was copied from another environment, a search-and-replace may also be needed in the database to update old domain references inside content, page builder data, and plugin settings.
Step 6: Enable SSL and force HTTPS
For a new WordPress site, SSL should be active as soon as possible. Most hosting platforms let you issue a free certificate and attach it to the domain.
Why SSL matters
- It encrypts traffic between visitors and the site
- It improves trust in the browser
- It avoids “Not secure” warnings
- It helps keep login pages and admin sessions protected
After enabling SSL, visit the site with https:// and confirm that the certificate matches the domain. Then update WordPress to use HTTPS and, if needed, set up a redirect from HTTP to HTTPS.
In some hosting environments, you can enable the redirect from the control panel. In others, it is done in WordPress or through server configuration such as Apache redirect rules.
Step 7: Test the domain connection
Before announcing the site, test the setup carefully. A correct domain connection should behave consistently across devices and browsers.
What to test
- Root domain loads the WordPress site
- www version redirects correctly, or resolves correctly if both are used
- HTTPS works without browser warnings
- WordPress admin login page opens
- Homepage, posts, and images load without errors
- Contact forms and email notifications work if configured
You can also check DNS propagation using online lookup tools or the command line. If the domain still shows the old site or a default hosting page, the most likely cause is either an incorrect DNS record or a mismatch between the domain and the document root.
Common problems and how to fix them
The site shows a default hosting page
This usually means the domain is pointing to the server, but not to the correct website folder. Check the document root and the hosting assignment in the control panel.
The domain does not open at all
Possible causes include:
- Wrong nameservers
- Incorrect A record
- DNS propagation not complete
- Hosting account suspended or not configured
Verify the nameservers or DNS records first, then confirm the hosting side is ready.
www works but the root domain does not, or the other way around
This usually means only one of the required records was created. Make sure both the root domain and www are configured consistently.
WordPress redirects to an old domain
If WordPress was cloned or migrated, old URLs may still be saved in the database or configuration files. Update the site URL, then clear caching and test again.
HTTPS shows a warning
Make sure the SSL certificate is issued for the exact domain you are using, including www if that version is active. Also confirm the redirect rules are not forcing the browser to a different hostname.
Email stops working after DNS changes
If you changed nameservers or DNS records, check that MX, SPF, DKIM, and DMARC records were copied over correctly. Domain connection changes should not break email, but missing DNS entries often cause delivery issues.
Best practices for a clean WordPress launch
- Choose one canonical version of the domain, with or without www, and redirect the other version
- Keep DNS records organised and documented
- Use SSL before sharing the site publicly
- Install WordPress in the correct document root from the start
- Verify the site URL after cloning or migration
- Test both the front end and the admin area before launch
These steps reduce setup issues and make future maintenance easier, especially if you later add email, staging, or additional WordPress sites in the same hosting account.
FAQ
How long does it take for a domain to connect to a new WordPress site?
It can happen within minutes, but DNS propagation may take several hours and occasionally up to 24–48 hours depending on caching and TTL values.
Do I need to change nameservers to connect my domain?
No. You can either change nameservers to your hosting provider or keep DNS at your registrar and update the A record. Both methods are common.
Can I connect a domain before installing WordPress?
Yes. In many hosting setups, the domain can be added first and WordPress installed afterward. This is often the easiest order for a new site.
Why is my WordPress site still showing the old address?
The WordPress Address or Site Address may still be set to the previous URL. Update the site URL and check for cached redirects or stored links in the database.
What is the difference between a domain and hosting?
The domain is the web address people type in their browser. Hosting is the service that stores and serves the WordPress files and database. Both are needed for a live website.
Do I need special settings in Plesk for WordPress?
Usually you only need the correct domain assignment, document root, database, and SSL configuration. Plesk tools can simplify installation and site management, but the exact setup depends on your hosting plan.
Conclusion
Connecting a domain to a new WordPress site is mostly about getting the DNS and hosting settings to match. Add the domain to the hosting account, point the DNS to the right server, install WordPress in the correct folder, and confirm the site URL and SSL settings. Once those pieces are aligned, the domain should load the new WordPress site reliably.
If the site does not appear immediately, start by checking the DNS records, document root, and WordPress URL settings. In most cases, the issue is small and easy to correct once you know where to look.