Installing WordPress is often described as a one-click job. It can be—but only after you find the correct button for the hosting product you actually bought.
One company may sell managed WordPress hosting, ordinary web hosting, a separate website builder and a virtual private server. Each can have a different setup process. It is therefore possible for a beginner to buy something that technically supports WordPress without receiving the guided installation they expected.
This article will help you understand how the pieces fit together, identify the installation route that applies to you and confirm that the result is a working WordPress site you can access independently.
The short answer
Start inside the account of the company providing your hosting.
- If you chose WordPress.com, WordPress is already built into the hosting service.
- If you bought managed WordPress hosting or an all-in-one platform, the provider should supply a guided site-creation process.
- If you bought general web hosting, look for an application or WordPress installer in its control panel.
- If you bought an unmanaged VPS or server, you may need a prepared WordPress server image or a manual installation.
Follow the current instructions for your exact product—not merely a tutorial mentioning the same hosting company.
The installation is not finished merely because a progress bar reaches 100%. Later in this guide, I will show you how to check the public site, HTTPS, dashboard and your independent route into WordPress.
If you have not selected your hosting yet, begin with my guide to choosing web hosting for a hobby website.
How a domain, hosting and WordPress fit together
The process becomes easier to understand when the components are separated.
The domain is the address
A domain such as example.com is the human-readable address people use to reach the website.
Through its DNS settings, the domain directs visitors towards the hosting infrastructure responsible for delivering the site. The domain does not contain the website itself.
Hosting is where the website runs
Hosting provides the server space and resources used to store the WordPress files, images and database and deliver the resulting pages to visitors.
It is often described as the place where the website files are physically saved. “Stored on the hosting provider’s servers” is more accurate because modern hosting can distribute information across several pieces of infrastructure.
WordPress is the website-management software
WordPress supplies the dashboard, editor, themes, plugins, user accounts, media management, menus and settings used to build and manage the website.
Before you can use it, the WordPress software needs to be placed on the hosting, connected to a database and associated with the intended domain.
That process is what installing WordPress means.
WordPress.com and WordPress.org in plain English
The names confuse many people because both involve the same underlying WordPress software.
WordPress.org is the home of the software project
WordPress.org provides the free, open-source WordPress software, official documentation, themes, plugins and community resources.
You can download WordPress from there and install it manually on hosting obtained elsewhere. In practice, many hosting companies obtain and configure the software for you through their own installer.
WordPress.com is a managed WordPress hosting service
WordPress.com is a commercial managed hosting service operated by Automattic and built specifically around WordPress. The software and hosting are already combined, so you create a WordPress website within that service.
WordPress.com and WordPress.org share software and history, but they are not two departments of the same commercial company. WordPress.com’s official explanation
What “self-hosted WordPress” means
If WA, Hostinger, SiteGround, IONOS or another company hosts your WordPress installation, this is commonly called self-hosted WordPress or the WordPress.org route.
That does not normally mean running a server in your home. It means that you chose a hosting provider other than WordPress.com for your copy of the open-source WordPress software.
If you have already paid another company for WordPress hosting, you do not normally need a separate WordPress.com account.
Which setup do you have?
You may not know whether your plan is managed, shared or self-hosted. You probably know which company you paid. Begin there, then check the exact product name inside your account or invoice.
The providers below are examples, not recommendations. Product names and interfaces were checked in July 2026 and can change.
1. You created your website through WordPress.com
WordPress is already part of the service. Sign into WordPress.com and follow its own site-creation instructions rather than looking for an installer at WordPress.org.
The general lessons in this article about secure credentials, recovery information and useful support requests still apply. The third-party hosting instructions do not apply in quite the same way because WordPress.com is both the WordPress platform and the host.
2. You bought managed WordPress hosting or an all-in-one platform
The provider may preinstall WordPress or guide you through a short website-creation process.
Look for wording such as:
- Create Website;
- Add WordPress Site;
- Start WordPress Installation;
- SiteBuilder;
- Set Up Project.
Wealthy Affiliate fits this route in my experience. IONOS also sells WordPress-specific products with their own project setup, although it offers other kinds of hosting as well. IONOS WordPress project guidance
3. You bought general web hosting with an application installer
General hosting may allow several content-management systems and applications rather than being designed solely for WordPress.
The installer may appear inside cPanel, Plesk or the provider’s own control panel and may be called:
- Auto Installer;
- App Installer;
- Softaculous;
- WordPress Toolkit;
- Click & Build;
- One-Click Install.
For example, Hostinger currently uses an Auto Installer that offers WordPress and other applications. SiteGround provides routes through New Website or its App Installer. IONOS Click & Build is available with relevant web-hosting packages. Hostinger, SiteGround, IONOS
The existence of an installer does not mean every plan uses the same screen or includes the same level of support.
4. You bought a VPS, cloud server or hosting without an installer
This route may require more technical involvement. The provider might offer a prepared WordPress server image, a managed add-on or instructions for a manual installation.
If you are a beginner who purchased this type of hosting without realising what it involved, ask whether the provider offers a managed WordPress product before attempting unfamiliar server work.
Use the instructions for your exact hosting product
The company name alone may not identify the correct process.
Start with your account, invoice or contract and find the exact plan name. Then search the provider’s help centre for instructions applying to that product. This matters because one provider may sell a website builder, managed WordPress, general hosting and VPS plans with different setup processes.
Before proceeding, you should be able to answer:
- Does this plan include WordPress or a supported installer?
- Where does its installation process begin?
- Does it connect the domain and activate SSL during setup?
- Who creates the administrator credentials, and where do I get installation support?
If you cannot find the answer, ask the provider:
What is the exact name of my hosting plan, and where is the supported WordPress installation guide for it?
“WordPress compatible” does not necessarily mean “guided beginner installation”. Instructions, training and support are part of the service you are buying.
What an automatic installer does
The official manual WordPress process involves downloading and uploading files, creating a database, supplying its details and running an installation script. Official WordPress installation guidance
An automatic installer performs most or all of those jobs for you. It broadly:
- places the WordPress files on the hosting;
- creates the database;
- connects WordPress to that database;
- creates an administrator account;
- records the site address and basic information;
- makes the dashboard available;
- may connect the domain and configure HTTPS.
The final two jobs vary between providers. Domain connection, WordPress installation and SSL activation are technically separate tasks even when one platform combines them into a single guided process.
Using automation is not inherently careless. A beginner using supported WordPress hosting normally has no reason to perform the manual process merely to prove that they can.
My WA installation experience
I have always valued the joined-up process inside Wealthy Affiliate.
I can search for a domain, buy it and pay for it within WA. Once it is registered, I open SiteBuilder, choose the domain from a dropdown list and ask it to create the website.
In my experience, WordPress is normally installed in about a minute. WA generates the credentials, sets up SSL and provides a route into the WordPress dashboard. I can also log into WordPress directly.
The value is not only the installer. WA’s core training has included a walkthrough showing members how to use the platform’s website-creation process. That removes the uncertainty about which product, installer and tutorial apply.
I understand why a more experienced user might prefer separate services or a more configurable hosting plan. My priority is different. If a reliable platform can connect the domain, install WordPress and configure HTTPS properly, I would rather spend my limited time researching, creating and publishing useful content.
That does not mean WA is the only place where WordPress can be installed easily. It means beginners should compare the complete process—not simply whether a plan says it supports WordPress.
Before you start the installation
Installer screens vary, but check these points where the choices are offered.
Confirm the domain and location
Make sure you are using the intended domain rather than a temporary address or another domain in the account. For an ordinary new hobby site, you will normally want example.com, not an accidental subdirectory such as example.com/wordpress.
Use an email address you control
Use an email account you control and expect to retain. Do not leave administration messages or account recovery dependent on somebody who helped create the site.
Protect the administrator account
Use a strong, unique password or accept a securely generated one, and store it securely before leaving the installer. Do not rely on memory or assume that the host’s shortcut will always be available.
Avoid optional distractions
Some installers offer themes, plugins, AI setup tools and other extras. They may be useful later, but the immediate objective is a secure, working WordPress installation under your control.
How to know the installation succeeded
Do not treat a completed progress bar as the only evidence. Check the result yourself.
1. Open the public website
Visit the domain in a private browser window. You should see a WordPress site rather than a registrar holding page, installer or error.
The site may look plain and contain sample material. That is normal. Installation and design are different stages.
2. Confirm HTTPS
Check that the address begins with https:// and that the browser displays no certificate or security warning.
HTTPS encrypts the connection between the visitor and the website. It is essential, but it does not prove that every part of the site is secure. WordPress HTTPS guidance
3. Open the WordPress dashboard
Use the route supplied by the provider and confirm that the dashboard loads. Check that you can see the normal administration areas for posts, pages, appearance, users and settings.
4. Check the owner and recovery information
Confirm that the administrator user and relevant email addresses are under your control. WordPress distinguishes the site administration email from the email attached to an individual user account, although they may be the same. WordPress General Settings guidance
If the domain or certificate needs a short time to become available, follow the provider’s stated timeframe. If it does not resolve as expected, contact support rather than changing several unfamiliar settings.
Keep an independent way into your website
Why this matters
Automatic installation is not the problem. Depending on one convenient route without knowing an alternative can be.
During some recent WA internal upgrades, the normal dashboard shortcut became unavailable for short periods. In live chat, it became apparent that some members had never recorded their WordPress credentials or did not know that they could log in directly.
Their websites had not necessarily stopped working; the familiar route into them had. Without an alternative, those situations can look identical to a beginner.
I observed those member discussions; I am not claiming to know the underlying technical cause. The lesson is that outsourcing installation should not mean surrendering access.
Perform the independent-login test
For a standard independently hosted WordPress installation, the direct administration address is normally formed by adding /wp-admin after the domain:
WordPress includes this route in its first-steps guidance. Security plugins or custom configurations can change or hide it, so record the actual login address used by your site. WordPress dashboard guidance
Then test it:
- Store the login address, administrator username and password securely.
- Log out of WordPress and the hosting platform.
- Open a private browser window.
- Visit the direct address and confirm that your stored credentials open the dashboard.
I have completed this test with ActionWithAI.com and can enter WordPress directly without using the WA shortcut.
Also confirm which email is attached to the WordPress user. The normal first recovery route is the Lost your password? link on the login screen. Test your access now rather than discovering a problem when a platform shortcut fails. WordPress password-reset guidance
Keep these seven details independently
Retain a secure record of:
- Public website address
- Direct WordPress login address
- WordPress administrator username
- WordPress administrator password
- Administrator and user-account email addresses
- Domain registrar and domain-account access
- Hosting provider, hosting-account access and support route
This is not about memorising DNS records. It is about knowing which accounts control the main parts of the website.
Do not send your password to support or expose it in a screenshot.
Is the website down, or is one route failing?
When access fails, separate three questions.
Can visitors open the public website?
Open the domain in a private window. If it works, the entire website is not necessarily down.
Can you reach WordPress directly?
Open the direct login address and try your stored credentials.
If the public site and direct login both work but the host’s shortcut fails, that suggests a problem with the convenience route rather than the whole website.
If the login page appears but the credentials fail, the issue may concern the username, password, user account or an access control.
Can you use the hosting-platform shortcut?
Try the usual route through the provider. If the public site and direct login also fail, the problem may be wider and require support investigation.
These checks do not diagnose the technical cause. They identify what works.
Give support useful information
Sometimes technical knowledge is not about fixing the problem yourself. It is about asking a better question and giving support better information.
Safely collect:
- the affected domain;
- the route used and what happened instead of the expected result;
- the complete error message and approximately when it began;
- whether the public site and direct login work;
- whether a private window changes the result;
- any change made immediately beforehand;
- a redacted screenshot if useful.
A useful request might say:
My public website at
[domain]and direct WordPress login at[address]both work. The shortcut from[hosting platform]stopped opening the dashboard at approximately[time]and shows[error message]. Please help me investigate that access route.
Change the template to match what you actually observed.
Opening the site, trying the direct login and recording an error are safe checks. Editing files, changing DNS, deleting plugin folders or altering the database merely to see what happens are not. Sometimes the safest technical decision is to stop changing things and ask for help.
Stop when WordPress is installed
At this stage, the website may use a default theme, contain a sample post and look nothing like the finished project. That is not a failed website. It is a successful installation waiting to be configured and filled with useful material.
Once you have completed the installation checks and stored the access information securely, stop. You do not need to make every design and technical decision immediately.
The next task is to check the small number of WordPress settings that should be correct before you begin publishing—not to install every attractive theme and plugin offered to you.
My conclusion
Identify the exact hosting product you bought, use its supported installation process and confirm that you retain control of the finished site. For me, WA’s installer, training and joined-up support remove friction that I would rather not recreate. Other readers may prefer separate services and greater technical control. Both can work when the choice is informed.
The best installation process is not the one that makes you perform the most technical work. It is the one that gets WordPress running reliably while leaving you with control and enough understanding to ask for the right help.