Your first WordPress site: from a test site to a public website

Start with a small WordPress site that people can read, that you can update and that can be restored, then add features gradually. A successful installation only shows that the software is running. You still need to check separately whether readers can find posts, contact emails arrive and a broken site can be restored.

This guide uses a personal website with its own domain to explain the sequence from preparing hosting to checking the site before launch. If you use WordPress.com, installation and hosting are provided by the service, so follow that platform’s setup process instead. The content organisation, visitor tests and handover checks below can still help you organise your site.

Keep control of the site before installing

Use an email account you can continue to manage when registering hosting, a domain and the site administrator. It need not be the public contact address, and it should not be controlled only by a contractor. Keep a private management record of each service’s purpose, sign-in method and payer. Store passwords in a password manager, not in public website documentation or post drafts.

Confirm that the host provides the runtime environment, database and HTTPS needed by WordPress, and locate the provider’s installation and backup instructions. Use a protected test site while the final content is undecided. Asking search engines not to index a site is only a search setting: it does not prevent someone who knows the URL from opening it. Private materials therefore need separate access protection.

Choose an installation method and check the URL

A host’s automatic installer will usually help create the database and configuration files. Before proceeding, check the selected domain, installation location and administrator details. If you want the site to appear directly at the home-page address, avoid accidentally installing it in an unnecessary folder. If the account already contains other sites, ensure this operation targets an empty location so existing files or data are not overwritten.

The main manual-installation steps are to obtain the official WordPress software, create a database and dedicated account, place the site files and enter the database connection details in the installer. The database password and site-administrator password serve different purposes and are not interchangeable. Afterwards, sign in to the dashboard and open a separate visitor window to confirm the home page is served from the intended URL.

1. Confirm the domain and installation directory in the hosting control panel, and note whether existing sites will be affected.
2. Install using the host’s tool or official manual procedure, checking the database, administrator and contact email separately.
3. Sign in to the dashboard and open the public-facing home page; make sure it is not the host’s default page or a different test site.
4. Check the HTTPS URL and browser warnings. If there is an error, follow the host’s documentation to resolve certificate and domain-resolution issues first.

Complete the basic dashboard settings first

In General Settings, check the site title, site language, administration email and time zone. The time zone affects how you interpret scheduling and post times. If you maintain a site in Taiwan, choose a regional time zone appropriate to your situation and preview a scheduled post again. Changing the site-address fields can affect sign-in and resource paths. Do not edit them casually as ordinary text before confirming the domain and HTTPS.

Next, organise users and default content. Give people who edit posts a role sufficient for their work, and reserve administrator accounts for those who need to change settings. Review sample posts, sample pages and default comments, replacing them with your own content. Check the purpose and licence of theme demo materials too. Reviewing the defaults first makes the site’s state easier to understand than installing many plugins straight away.

Organise the home page, posts and basic navigation

A personal site can start with information about you, your work or services, and contact details. A site with ongoing writing can start by organising post categories. Reading Settings lets you show recent posts on the home page or choose a static page. If you also need a separate posts-list page, assign the home page and posts page separately rather than making one page serve both purposes and confusing visitors about where they are.

Write a test post with real content, including paragraphs, headings, images and links. Give images alternative text that describes their purpose, and check on a phone that long titles, tables and navigation do not extend beyond the screen. A preview only shows the current editing state. When a post is saved as a draft, signed-out visitors generally cannot read it through a preview link, so check the real post URL before launch.

Test important features as a visitor

Close the administrator dashboard and go through the site in a signed-out browser. Find a post from the home page, return from the post to its category and try the contact route. A form showing success and an email actually arriving are separate checkpoints. Submit test content and check both the inbox and spam folder; a thank-you message on screen is not proof of email delivery.

If the site includes sign-in, bookings or shopping, create a separate complete acceptance checklist. Passing checks for a general content site does not mean transaction workflows have passed. Avoid using real customer personal data in tests. Also ask at least one person who did not help build the site to read the main pages, and see whether they can explain in their own words what the site offers and what to do next.

Create a backup before going public

Before launch, save the site files, database and necessary settings, and confirm how to restore them. A hosting screen saying ‘backed up’ does not mean you know how to recover the site. Find a procedure you can actually follow, and record what is retained and where backups are stored. If an isolated test environment is available, verify the restored result there instead of using the live site for your first practice run.

Finally, check the public site’s search visibility, domain, contact details and navigation, then remove access restrictions set only for testing. Keep a record of the launch-day settings. When later updating themes or plugins or adding features, handle one related group of changes at a time and revisit the visitor workflow. Completion means readers can use the site and a maintainer can take it over, not merely that the installer has finished.

Read the full description

Verify installation and URLs, organise content, test visitor actions, then confirm backups and public-access settings.

Choosing a CMS or website platform: let your update workflow guide the choice

Enable HTTPS on your website: certificates, redirects and mixed-content checks

Website maintenance: routine backups, updates and fault reporting

• Tutorials
• Apps & software
• Websites & e-commerce
• WordPress