{"id":3241,"date":"2022-02-11T14:06:10","date_gmt":"2022-02-11T12:06:10","guid":{"rendered":"https:\/\/www.scalahosting.com\/kb\/?p=3241"},"modified":"2025-11-27T14:18:59","modified_gmt":"2025-11-27T12:18:59","slug":"what-do-i-need-before-my-wordpress-site-can-go-live","status":"publish","type":"post","link":"https:\/\/www.scalahosting.com\/kb\/what-do-i-need-before-my-wordpress-site-can-go-live\/","title":{"rendered":"WordPress Site Launch Checklist"},"content":{"rendered":"

Launching a new website can be both exciting and stressful. For example, while you’re <\/span>developing your WordPress project<\/b><\/a>, you get to<\/span> see your ideas take shape<\/b>, and you draw a <\/span>strategy <\/b>for how your business will grow. However, you don’t want to reveal your plans before you’re completely ready with the website, so the preparation usually happens <\/span>offline<\/b>.<\/span><\/p>\n

Unfortunately, when it comes to bringing the site live, things<\/span> don’t always go according to plan<\/b>. Let’s examine the process in more detail and see what you can do to avoid potential setbacks.<\/span><\/b><\/p>\n

What Do You Need to Do to Get Your WordPress Website Live?<\/b><\/b><\/h2>\n

Launching any site requires <\/span>a host for the files and databases<\/b> and <\/span>a correctly pointed domain<\/b> so people can access the web pages from anywhere in the world. Many people try to save a bit of cash by hosting their websites on their home computers.<\/span><\/p>\n

Indeed, you can theoretically point a domain to your personal PC, but the loopholes you need to go through are so enormously complicated, it’s really not worth the effort. What’s more, <\/span>you’ll never get the performance<\/b> you’re after if you host from home.<\/span><\/p>\n

You’re much better off hosting your website on a proper server situated in a proper data center. There, it will be powered by <\/span>enterprise-grade hardware<\/b> providing excellent performance, and people will connect to it via <\/span>a blistering internet connection<\/b>, ensuring great loading speeds all over the world.<\/span><\/p>\n

But if you’ve already developed your WordPress website at home, how do you move it to your hosting account. Well, there are several ways of tackling the job.<\/span><\/b><\/p>\n

Transferring Your Site Manually<\/b><\/b><\/h2>\n

This is <\/span>the most hands-on approach<\/b>. As we’ll find out in a minute, there are simpler ways of getting a similar result, but if you’re careful, you’re unlikely to get it wrong. At the same time, the process will let you learn more about the tools and systems that power your WordPress site and could help you develop your technical skills. Let’s take a look at the steps.<\/span><\/p>\n

1. Upload your website’s files to your hosting account<\/b><\/h3>\n

This is the most straightforward part of the process. You can use either an <\/span>FTP client<\/b><\/a> or your control panel’s File Manager to copy your website’s files and folder to your document root directory (usually, the <\/span>public_html <\/b>folder).<\/span><\/p>\n

Make sure you <\/span>don’t change the folder structure<\/b>. The files must be arranged as they are on your hard disk.<\/span><\/p>\n

\"WordPress<\/figure>\n

2. Export your database from localhost<\/b><\/h3>\n

If you’re developing your WordPress website with the help of a platform like the WampServer, you have access to <\/span>phpMyAdmin<\/b> \u2013 a database management system that, among other things, lets you export and import databases.<\/span><\/p>\n

To access the functionality, open phpMyAdmin at <\/span>localhost\/phpmyadmin<\/span><\/i>, log in with <\/span>root<\/span><\/i> as a username and no password, and go to the <\/span>Export <\/b>tab. Choose the <\/span>Quick<\/b> method, and click <\/span>Go<\/b> to save your database on your hard drive.<\/span><\/p>\n

\"WordPress<\/figure>\n

3. Create a new database and import the data<\/b><\/h3>\n

Next, you need to open your hosting account’s control panel. You should have a tool for creating databases. Here, for example, is what you’ll work with if you use <\/span>ScalaHosting’s SPanel management platform<\/b><\/a>.<\/span><\/p>\n

\"WordPress<\/figure>\n

You need both <\/span>a <\/b>database and a MySQL user account<\/b><\/a>. Later on, WordPress will use this user account to communicate with the database, so it’s essential to keep note of its credentials.<\/span><\/p>\n

After creating the database, you need to fill it with the data exported from your local computer. To do that, you’ll need <\/span>phpMyAdmin<\/b>. It’s usually accessible from your control panel’s homepage. Select the database you’ve just created from the navigation bar on the left, and click the <\/span>Import<\/b> tab.<\/span><\/p>\n

\"WordPress<\/figure>\n

Click the <\/span>Browse<\/b> button inside the <\/span>File to import<\/b> section to select the SQL file you exported from your localhost installation.<\/span><\/p>\n

\"WordPress<\/figure>\n

With that, you’ve migrated all your files and data from your personal computer to the hosting server. It’s now time to get them to work together.<\/span><\/p>\n

4. Edit the wp-config.php file<\/b><\/h3>\n

If you try to load your website at this stage, you’ll see that <\/span>WordPress is unable to establish a database connection<\/b>. That’s because the <\/span>wp-config.php<\/b> file you copied is still telling it to connect to the database you used on your local computer, not the one you created during the previous step.<\/span><\/p>\n

You can edit it either via an FTP client, or you can use your control panel’s File Manager to update it straight on the server. Below, you can see the lines you’ll need to update, using <\/span>the new database’s name<\/b> and<\/span> the username and password of the MySQL user account<\/b>.<\/span><\/p>\n

\"WordPress<\/figure>\n

Don’t forget to save the changes and, if you’re using an FTP client, re-upload the file to your site’s document root directory.<\/span><\/p>\n

5. Configure WordPress to work with your domain name<\/b><\/h3>\n

The final job is to make sure your website works with the new domain. Since you’ve been developing it locally, <\/span>it’s been configured to load under a localhost URL<\/b>. To make it work with the domain name, you need to update some database entries. The easiest way to do that is with <\/span>WP-CLI<\/b>.<\/span><\/p>\n

WP-CLI is a command-line tool for WordPress that packs many useful features, including the <\/span>search-replace<\/b> functionality. With it, you can change the domain name of a WordPress website with a single command.<\/span><\/p>\n

We’ll assume that the URL you used to develop your website on your personal computer is <\/span>localhost\/project<\/span><\/i>, and your domain is <\/span>www.domain.com<\/span><\/i>. In that case, the command you’ll need to use is as follows:<\/span><\/p>\n

wp search-replace localhost\/project <\/span><\/i>www.domain.com<\/span><\/i><\/p>\n

You can use the <\/span>–dry-run <\/span><\/i>parameter to find out exactly what’s going to happen. If you do, WP-CLI will scan your database and show you which entries need to be modified. If you run the command without –dry-run, it will go ahead with the changes.<\/span><\/p>\n

\"WordPress<\/figure>\n

The site should load normally now. If your links don’t work, you can log into the WordPress dashboard, go to <\/span>Settings<\/b> ><\/span> Permalinks <\/b>and click <\/span>Save Changes<\/b> to rewrite the <\/span>.htaccess file<\/b>.<\/span><\/p>\n

With that, you should be ready to go.<\/span><\/b><\/p>\n

Transferring a WordPress Website Using the Import\/Export Features<\/b><\/b><\/h2>\n

WordPress has a built-in mechanism for moving data between installations. You need to bear in mind, however, that this is not a complete site migration. With the <\/span>Export\/Import <\/b>function, you can move all your posts, <\/span>pages, categories, comments, users, and media files<\/b>. After they’ve been transferred to the new installation, you’ll need to add the plugins and themes manually.<\/span><\/p>\n

Let’s see how you can take advantage of this particular feature.<\/span><\/p>\n

1. Export the data from your local site<\/b><\/h3>\n

Go to <\/span>Tools<\/b> > <\/span>Export <\/b>inside your local <\/span>WordPress dashboard<\/b><\/a>. Select <\/span>All content<\/b> and click <\/span>Download Export File<\/b>.<\/span><\/p>\n

\"WordPress<\/figure>\n

WordPress will <\/span>generate an XML file<\/b> with all the data inside it. You need to save it to your computer.<\/span><\/p>\n

2. Install WordPress on your hosting account<\/b><\/h3>\n

There are many ways to <\/span>install WordPress on your account<\/b>. Most probably, the control panel you use has either <\/span>Softaculous<\/b> or another automatic installer that can set up the content management system in seconds.<\/span><\/p>\n

Make sure you don’t add any content to the new installation. Otherwise, you may run into conflicts later on.<\/span><\/p>\n

3. Import the data into the new installation<\/b><\/h3>\n

Log into the new installation’s dashboard, and go to. <\/span>Tools<\/b> > <\/span>Import<\/b>.<\/span><\/p>\n

This section allows you to import data from many different platforms through add-ons. Since you’re interested in transferring data from one WordPress website to another, you need to click <\/span>Install Now<\/b> under the WordPress section.<\/span><\/p>\n

\"WordPress<\/figure>\n

After a few seconds, the additional utility is ready, and you can click <\/span>Run Importer<\/b>.<\/span><\/p>\n

You’ll get a brief explanation of what you’re about to do, and there’s a <\/span>Choose File<\/b> button through which you can navigate to and select the XML file you exported from your local site. Click <\/span>Upload file and import<\/b> to initiate the process.<\/span><\/p>\n

\"WordPress<\/figure>\n

 <\/p>\n

Transferring a WordPress Website Using a Plugin<\/b><\/b><\/h2>\n

Plugins are a fundamental part of the WordPress ecosystem, so it shouldn’t really be a surprise that there are solutions for transferring a website from one device to another. In fact, there are quite a few WordPress migration plugins, but with <\/span>over 1 million active installations<\/b> and predominantly positive reviews, <\/span>Duplicator<\/span><\/a> seems to be one of the most popular choices. Let’s trace the steps you need to take to transfer your website with it.<\/span><\/p>\n

1. Install Duplicator on your local website<\/b><\/h3>\n

Duplicator needs to be installed <\/span>only on your local website<\/b>. The plugin is a part of <\/span>WP’s official directory<\/b>, so the installation process is pretty straightforward.<\/span><\/p>\n

2. Create a package and set it up on your hosting account<\/b><\/h3>\n

Duplicator works by creating the so-called <\/span>packages<\/b> \u2013 archives full of the site’s data, which you can deploy on a hosting account. The Duplicator menu appears in the WordPress dashboard’s main navigation bar, and from there, you can create and manage packages. You start with the <\/span>Create New<\/b> button.<\/span><\/p>\n

\"WordPress<\/figure>\n

The plugin gives you plenty of options to play with, but since you need to transfer the entire website, you can use the default settings and click <\/span>Next<\/b> until the package is created. Click <\/span>One-Click Download <\/b>to download both the installer and the archive.<\/span><\/p>\n

\"WordPress<\/figure>\n

You’ll get two files: <\/span>installer.php and a ZIP archive<\/b> full of your data. You can upload them straight to the document root folder of your hosting account.<\/span><\/p>\n

NOTE: <\/b>If the transfer is to work, you need to make sure that there’s <\/span>nothing else in your account’s document root<\/b>. You <\/span>DON’T<\/b> need to install WordPress on your hosting account.<\/span><\/p>\n

3. Create a database<\/b><\/h3>\n

Duplicator can’t create a database on its own, so you’ll have to do it yourself. Once again, you need both a <\/span>database and a MySQL user account to access it.<\/b><\/p>\n

Keep track of the <\/span>user account’s username and password<\/b>, as you’ll need them later.<\/span><\/p>\n

4. Deploy the package<\/b><\/h3>\n

Deploying the Duplicator package takes a few steps, the first of which is to make your way to <\/span>https:\/\/yourdomain.com\/installer.php<\/span><\/i>.<\/span><\/p>\n

During the first step, the installer will perform some checks to make sure the underlying hosting environment is suitable for the <\/span>WordPress installation<\/b><\/a>. There are some settings, as well, though leaving them in their default state is probably the best strategy.<\/span><\/p>\n

You also need to accept the Terms of service to continue.<\/span><\/p>\n

\"WordPress<\/figure>\n

Your next job is to configure the database. You’ll have to enter <\/span>the database’s name and the MySQL user account’s credentials<\/b>.<\/span><\/p>\n

\"WordPress<\/figure>\n

Click <\/span>Test Database<\/b> to see if you have entered the correct data. If you have, the Duplicator installer will ask you to confirm the settings, after which it will deploy the installation.<\/span><\/p>\n

The installer will try to fetch the<\/span> site URL from your hosting account<\/b>, but if it’s unable to do so, you’ll need to enter it manually.<\/span><\/p>\n

\"WordPress<\/figure>\n

Finally, Duplicator will perform a few checks to ensure everything has gone according to plan. The deployment does leave some installation files behind, and the plugin will ask you to log into your WP dashboard and remove them.<\/span><\/p>\n

Developing Your Website Directly on Your Hosting Account<\/b><\/h2>\n

You can certainly save some cash by <\/span>developing your site on your home computer<\/b>. You only start paying for a hosting service after your site is live, so it’s certainly a good decision budget-wise. However, if your financial restrictions are not that tight, you might want to consider getting a hosting account from the very start.<\/span><\/p>\n

For one, it will be easier to get going. Most plans come with a<\/span> control panel and a one-click installer<\/b> that sets up WordPress in seconds. In some cases, you even get tools to set up a staging environment.<\/span><\/p>\n

During the installation, you can <\/span>configure WordPress to discourage search engines<\/b> from indexing the website. You can also configure the functionality under the <\/span>Settings<\/b> > <\/span>Reading<\/b> menu in the WP dashboard. Thanks to it, you don’t need to worry about users accidentally stumbling upon your site before it’s ready.<\/span><\/p>\n

\"WordPress<\/figure>\n

It’s trivial to put up an <\/span>Under Construction<\/b> page, and if you don’t want to do that, you can simply point your domain away from your hosting account and work on the site with the help of your <\/span>hosts file<\/span><\/a>.<\/span><\/p>\n

While it’s not the cheapest strategy, developing your WordPress project directly on your hosting account can<\/span> save you some hassle<\/b>.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Launching a new website can be both exciting and stressful. For example, while you’re developing your WordPress project, you get to see your ideas take shape, and you draw a strategy for how your business will grow. However, you don’t want to reveal your plans before you’re completely ready with the website, so the preparation […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_seopress_robots_primary_cat":"none","_seopress_titles_title":"WordPress Site Launch Checklist | ScalaHosting KB","_seopress_titles_desc":"","_seopress_robots_index":"","_seopress_analysis_target_kw":"","footnotes":""},"categories":[34],"tags":[],"class_list":["post-3241","post","type-post","status-publish","format-standard","hentry","category-web-hosting"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/posts\/3241","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/comments?post=3241"}],"version-history":[{"count":7,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/posts\/3241\/revisions"}],"predecessor-version":[{"id":5887,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/posts\/3241\/revisions\/5887"}],"wp:attachment":[{"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/media?parent=3241"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/categories?post=3241"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/tags?post=3241"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}