0.3Installing WordPress (1-click, manual or local)
The essentials in 30 seconds
- Three routes: 1-click with the hosting provider (most common), manual via FTP (instructive), local on your computer (learn without risk).
- WordPress needs a database: the 1-click installer creates it, the manual installation asks for it.
- Security from installation: an admin username that is not obvious (never “admin”) and a strong password.
Running mini-case — Samir installs and practises
Samir must deliver Hassan's site, but first he wants to test the theme and plugins without breaking anything. He decides to install WordPress locally on his computer to prepare the site, then use the 1-click installation with the hosting provider at launch time. This section describes the three routes and the precautions to take.
Sequel to case 0.2 — the foundations are laid, now we install.
1. Three routes, one result
The 1-click installation is offered by most hosting providers (Softaculous or equivalent): you choose WordPress, enter the site name and the admin account, and the platform creates the files and the database. It is the fastest route to put a site online.
The manual installation consists of downloading WordPress.org, creating a MySQL database, uploading the files via FTP, then running the wizard. Longer, it teaches you the site's real structure (files, database, wp-config.php) and helps when 1-click fails. Finally, the local installation (Local, XAMPP, MAMP) runs WordPress on your computer: ideal for learning and testing without risk.
2. Secure from the first minute
At installation, WordPress asks for an administrator account. This is the most powerful account: it can change everything, including breaking the site. Samir therefore chooses a non-obvious username — never “admin”, a classic attack target — and a long, unique password, kept in a password manager.
He also checks that the installation created the database and that the site address is correct. On an existing site, back up before any intervention: an installation or theme change can alter the display. These reflexes prevent most early-project incidents.
🔎 Concrete example — Installing locally to prepare the site (Samir case)
1. Install Local (localwp.com), free.
2. Create a site "atelier-bahja": Local sets up PHP, MySQL and WordPress.
3. Admin username: samir_bahja (not "admin") + long password.
4. Open WP Admin and check that the dashboard appears.
→ Hassan's site will be prepared here, then migrated online.Result: a complete WordPress, with no risk to the public site.
Lesson: prepare locally, publish afterwards.
Section vocabulary
- 1-click installation
- The hosting provider's installer that deploys WordPress and creates the database in a few clicks.
Simple example: Samir puts the site online in 1 click with the hosting provider.
What it is not: believing 1-click also installs the themes and final content.
Reflex: fast, but check the settings afterwards.
- Manual installation
- Uploading WordPress via FTP after creating the database, then running the wizard.
Simple example: useful when 1-click is not available.
What it is not: starting FTP work without a backup on an existing site.
Reflex: instructive, do it at least once.
- Local installation
- WordPress on your own computer (Local, XAMPP) to test without going live.
Simple example: Samir prepares Hassan's theme locally.
What it is not: publishing tests directly on the client's site.
Reflex: local = training ground.
- Database
- Structured storage of content and settings; separate from the site's files.
Simple example: the wizard asks for the database name and credentials.
What it is not: confusing files and database during a backup.
Reflex: files + database = complete backup.
- Administrator account
- The site's master account, with unlimited rights; protect it first.
Simple example: non-obvious username and unique password.
What it is not: using “admin” and a short password.
Reflex: the less guessable the account, the better.
In practice — Installing WordPress locally
- Download and install Local (localwp.com) or XAMPP.
- Create a site: the tool sets up PHP, MySQL and WordPress automatically.
- In the wizard, choose a non-obvious admin username and a strong password.
- Open WP Admin, check the dashboard and note the site's local address.
Ready-to-say script — reassuring about installation (20s)
“I install WordPress on your hosting, with a secure administrator account. Before going live, I prepare everything on my computer: you will only see the site once it is ready, and nothing will be published by mistake.”
Mention the backup if the site already existed.
Copy-paste template — installation checklist
CHOSEN ROUTE: 1-click / manual / local
DATABASE CREATED: yes / no
SITE ADDRESS: _______________
ADMIN USERNAME (non-obvious): _______________
STRONG PASSWORD + MANAGER: yes / no
BACKUP MADE (existing site): yes / noNew site online
1-click with the hosting provider, then basic settings: fastest.
Learning
Local: full installation with no risk, repeat as often as needed.
Taking over a site
Full backup before any installation or update.
Host without 1-click
Manual installation: MySQL database, FTP, wizard — allow 20 minutes.
✓ Best practices
- Practise locally before touching the live site.
- Choose a non-obvious admin username.
- Back up before any intervention on an existing site.
✗ Common pitfalls
- Using “admin” as the username.
- Forgetting to create or check the database.
- Testing settings directly in production.
Key takeaways
- Three routes: 1-click, manual, local.
- The database is essential for operation.
- Non-obvious username + strong password from installation.
- Local is the ideal training ground.
48h Challenge — apply tomorrow
Install WordPress locally and create your secure admin account. Note the total time and the steps that raised questions: those are the ones to review before working on a client site. 25 minutes.
- I know the three installation routes.
- I have installed WordPress locally with a secure account.
- I know why the database is necessary.
Frequently asked questions
Local installation or directly online?
Local to learn and test: no risk, fast, free. Online for a real site intended for the public. Many professionals prepare locally then go live (migration, section 5.2).
Is manual installation still useful?
Yes, at least once: it demystifies WordPress's structure (files, database, wp-config.php) and helps when 1-click is not available. Day to day, 1-click or local is enough.
What if the wizard cannot find the database?
Check the database name, user, password and host provided by the hosting provider. Locally, the tool creates this information automatically; online, it appears in the hosting panel.
Samir wants to practise and test settings without risking Hassan's live site. Which route should he choose?