Setting up a Bluehost website: checks before purchase and after installation

Bluehost's installer can create a WordPress environment, but a working public website still needs content, a domain, connectivity and a maintenance plan. Before starting, write down the site's main tasks, such as letting visitors view your work, understand your services and send an enquiry. These tasks help determine the features you need and become acceptance criteria at launch.

This guide follows Bluehost's currently public Portal documentation; it does not report hands-on testing in a user account or performance testing. Interfaces may differ by product and account. In particular, the standard website installation flow should not be applied directly to a self-managed VPS. Check your product name first and follow its documentation, so you do not confuse reinstalling a server with adding a website.

Turn purchasing requirements into a comparable checklist

List the number of websites, data volume and whether you need a shop, email, backups and a staging environment, then check what the current plan includes. A label saying it is suitable for WordPress does not establish that every requirement is covered. If you are migrating a site, also check compatibility with its existing code, database, scheduled tasks and plugins, and prepare a complete backup you can access.

Before checkout, record the prepaid term, initial total, renewal cost, domain and other add-ons separately. A displayed monthly equivalent does not necessarily mean monthly payment; backup, email and security services may have separate subscriptions. This guide offers no discount codes or untested recommendation rankings. Confirm the full cost against your selected plan and its current terms.

Create the correct WordPress site from Websites

According to Bluehost's current installation documentation, sign in to Portal, open Websites in the left menu, choose Add Website and then WordPress to start installation. First confirm the correct account and available plan, and give the site a name that identifies its purpose. If other sites already exist, avoid functions that delete content, remove WordPress or rebuild the environment.

The official documentation offers flows such as AI Site Creator and Import an Existing WordPress Site after installation. For a new website, follow the guidance to set up initial pages; for an existing site, handle its source and data through the import flow. Their purposes differ: one creates a starting point for content, while the other moves existing data. Do not overwrite your only live website just to try a design.

1. Sign in to the official Portal, confirm your plan, open Websites and select Add Website and WordPress.
2. Choose the new-site or import flow according to the site's state, enter an identifiable name and purpose, and save the completion result.
3. Use that site's Manage section to check its status and open the WordPress dashboard; confirm the administrator and notification email address.
4. Set up the necessary pages and navigation first, then test with the final domain or temporary URL instead of immediately adding many plugins.

Treat automatically generated content as a draft

If using the AI site-building flow, enter the site's purpose, language, service area and actual contact details, then inspect every generated page. Do not publish generated company histories, figures, customer reviews or service promises without checking them. Remove unsupported content or replace it with verifiable descriptions, and confirm usage rights for images and trademarks.

Complete the home page, about page, main service or portfolio pages, and necessary contact and data-use information first. Use button labels that readers in Taiwan can easily understand, and make navigation correspond directly to visitor tasks. Test the path from the home page to the contact page. Check that buttons do not all lead to the same default section and that no sample phone numbers or blank prices remain.

In WordPress General and Reading settings, check the language, time zone, site title and home-page display. If using a static home page, distinguish it from the posts page. Search-engine visibility is an indexing signal to search engines, not a mechanism for restricting visitor access. A staging site containing unpublished information needs suitable access controls separately.

An external domain needs both site binding and DNS configuration

A domain purchased from another registrar can also be used by following Bluehost's external-domain connection documentation. Under Websites, choose Manage for the site, then follow the domain-connection guidance to enter the name and complete the required settings. Adding a domain to the site and changing DNS are related but separate tasks. Completing only one does not necessarily make the website visible to outside visitors.

Before changing nameservers, save the existing DNS records, particularly the MX and verification records used for email. Use the values supplied by your account and official documentation instead of copying an IP from years ago or someone else's screenshot. If you use another DNS or proxy service, confirm the appropriate route first. Moving the website does not necessarily require transferring domain registration, and must not inadvertently alter email.

Check the public entry points as a visitor

Once the final domain resolves, test the root domain, www and HTTPS, and check the certificate and redirects. A connected status in the administration interface does not mean every path has been verified. Open the home page and a deeper article in a signed-out browser window to confirm that visitors see the public content, rather than a preview available only to administrators.

Next, use a phone to check navigation, images, line wrapping and buttons. Submit a test enquiry without sensitive data and confirm that the notification arrives. If the site includes search or membership features, complete the necessary flows too. Remove test data after handling it, and record the results as acceptance checks for this website. Do not present a supplier's feature description as evidence of your own testing.

Retain management information beyond the website at handover

Record the Portal account, WordPress administrator, domain registrar, DNS location, backup method and person responsible for renewals. Transfer passwords securely instead of placing them in ordinary instructional documents. Give collaborators the permissions their work requires, then check for unnecessary access or notification settings when the engagement ends.

After launch, schedule update and backup checks, and identify the function or support contact needed for restoration. Before removing a test site, check whether it shares data or a domain with the live site, and read what deletion covers. Initial installation can be quick, but a maintainable website also requires clear responsibilities and a usable way to retain its data.

Read the full description

Four stages of a Bluehost website—plan, WordPress, domain and visitor acceptance—with the necessary checks for each.

Bluehost domains and billing: check add-ons, payment and renewal separately

Enable HTTPS on a website: certificates, redirects and mixed content

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