Installing WordPress in 2026 is usually straightforward because many hosting providers offer one-click or guided installation. Manual installation is still useful when you need control over the server, database, files, or deployment process.
This guide covers both approaches, then walks through the configuration and security checks worth completing before a new WordPress site goes live.
What You Need Before Installing WordPress
- A domain name or temporary development URL.
- Hosting that supports the current WordPress version and a supported PHP/database environment.
- HTTPS support and an SSL/TLS certificate.
- A database for a manual installation.
- Hosting-panel, SFTP/FTP, or file-manager access, depending on the installation method.
- A plan for backups, administrator access, and whether the site should be public immediately.
For WordPress 7.1, WordPress.org recommends PHP 8.3 or newer and MySQL 8.0 or MariaDB 10.11 or newer on its download page. The WordPress Hosting Team’s current 7.1 guidance recommends newer versions for new installations, including PHP 8.4 or 8.5 and MySQL 8.4 or supported MariaDB 10.11, 11.4, or 11.8. Always check your host’s current environment and WordPress’s official requirements before deployment.
Option 1: Install WordPress with Your Hosting Provider
For most beginners, the hosting-provider installer is the simplest option. Sign in to your hosting control panel, locate its WordPress installer, choose the domain or directory, create the administrator account, and complete the setup.
The exact screens vary by provider. Use the host’s current documentation rather than relying on screenshots from an older tutorial.
Before you finish the installer
- Use a strong, unique administrator password.
- Confirm the correct domain and installation directory.
- Enable HTTPS if the host provides that option.
- Do not use a predictable administrator username.
- Confirm whether the installer creates automatic backups or update rules, and do not assume it does.
Option 2: Install WordPress Manually
1. Download the current WordPress package
Download WordPress from WordPress.org. Use the official download rather than an unofficial software mirror.
2. Prepare the database
Create a MySQL or MariaDB database through your hosting panel and record the database name, username, password, and database host. WordPress requires database access to store site content and configuration.
3. Upload the WordPress files
Upload the WordPress files to the site’s document root using SFTP, FTP, or your hosting file manager. The directory may be called public_html, www, htdocs, or something specific to your provider.
Prefer SFTP when your host supports it because it encrypts the connection. If you use FTP, confirm what secure transport options your host provides.
4. Run the installation
Open the site’s installation URL in your browser. WordPress will ask for the database connection details and then guide you through the site title and administrator account setup.
5. Confirm the installation
Log in to the WordPress dashboard and check the front end in a separate browser window. Confirm that the expected domain, HTTPS URL, administrator account, theme, and basic navigation are working before adding more plugins or content.
Essential WordPress Configuration After Installation
Set the site identity
Open Settings → General and review the site title, tagline, site language, timezone, and administration email. WordPress’s current getting-started guidance also recommends planning the site structure and reviewing the administration settings after installation.
Choose the permalink structure
Select a clean URL structure that fits the site’s content. Avoid changing established permalink structures after publishing unless you have a redirect and internal-linking plan.
Enable and verify HTTPS
Make sure the site loads over HTTPS and that important pages do not contain mixed-content warnings. If your host provides automatic HTTP-to-HTTPS redirects, test both versions rather than assuming the redirect is configured correctly.
Review search visibility before launch
If the site is still under development, keep its search visibility setting appropriate for a private or staging environment. Before launch, confirm that production pages are allowed to be indexed and that you have not accidentally left a noindex directive or development restriction in place.
WordPress’s Reading Settings include a search-engine visibility option that asks search engines not to index the site. This setting should be reviewed when moving from staging to production.
Install only the plugins you need
Do not install plugins simply because they are popular. Choose actively maintained plugins from reputable sources, check compatibility with your WordPress version, and remove plugins you no longer use.
Choose and configure a maintained theme
Select a theme that is appropriate for your site’s requirements and is maintained for current WordPress releases. Configure navigation, branding, typography, templates, and responsive behavior, then test important pages on mobile and desktop.
Security Checklist for a New WordPress Site
- Use a unique, strong administrator password.
- Enable multi-factor authentication when available.
- Give users only the role and capabilities they need.
- Keep WordPress, plugins, and themes updated.
- Set up backups and test that a restoration is actually possible.
- Use HTTPS and secure hosting connections.
- Remove unused plugins and themes.
- Limit administrator accounts to people who need administrative capabilities.
- Review unfamiliar users and installed plugins before launch.
WordPress uses roles and capabilities to control what users can do, so not every person who publishes content needs administrator access.
SEO Checklist After Installation
- Set the site title and description appropriately.
- Choose a stable permalink structure.
- Create logical navigation and category architecture.
- Verify the XML sitemap generated by your WordPress setup or SEO plugin.
- Connect Google Search Console and analytics when appropriate.
- Check robots.txt, canonical URLs, noindex directives, and search visibility settings.
- Make sure important pages are reachable through internal links.
- Check that the preferred HTTPS version is used consistently.
What to Check Before Going Live
| Area | Check |
|---|---|
| Hosting | Supported PHP/database versions, storage, resources, and HTTPS |
| Security | Admin access, MFA where available, updates, backups, and user roles |
| URLs | Domain, HTTPS, permalinks, redirects, and canonical behavior |
| Search | Indexability, robots.txt, sitemap, and no accidental staging restrictions |
| Performance | Theme, plugins, images, caching/CDN configuration, and mobile rendering |
| Recovery | Backup exists and restoration steps are known and tested |
Common WordPress Installation Problems
Database connection errors
Recheck the database name, username, password, host, and permissions. A typo in any of these values can prevent WordPress from connecting to the database.
HTTPS or redirect problems
Check the site’s WordPress URL settings, hosting redirect rules, SSL certificate, and any CDN or proxy configuration. Avoid adding multiple overlapping redirect rules without testing the final request path.
Plugins or themes causing errors
If the site becomes unstable after installing an extension, identify the last change and disable the suspected plugin or theme through an appropriate recovery method. Add extensions one at a time so problems are easier to isolate.
Site is not appearing in search
First confirm that the site is actually ready for indexing. Then check WordPress search visibility, robots.txt, noindex directives, canonical URLs, sitemap availability, and whether search engines can crawl the important pages.
Final Takeaway
WordPress installation is only the first step. A production-ready site also needs a supported hosting environment, HTTPS, appropriate user access, backups, current software, stable URLs, clean information architecture, and deliberate search visibility settings.
Use the automated installer when it fits your environment. Choose manual installation when you need more control over the files, database, or deployment process. Either way, verify the configuration before publishing the site publicly.
Related: If you prefer manual deployment, see our guide to uploading WordPress with FileZilla.
