Copy WordPress To Wamp Localhost Manually

WAMP localhost interface

Copying a hosted WordPress installation to a local machine for development is a fairly common task for many web designers. I prefer to accomplish this task with the excellent WordPress Duplicator Plugin by Life in the Grid. However, the Duplicator plugin is often an inadequate solution for larger sites on a shared hosting platform – you may experience frustrating sever timeouts and other difficulties.

Sometimes old ways is best ways, so role up your sleeves and prepare to copy WordPress to WAMP server manually, just like developers did before the various WordPress migration plugins existed.

I found the following instructions on the WordPress forum, they were contributed back in 2012 by Sunny Johol and still work perfectly for WordPress 4.5.2 and WAMP with phpmyadmin 4.0.4. It you follow the steps exactly you should have no trouble copying a WordPress site to a local test server. If you follow the forum link above you may find these instructions can be modified to work with XAMP as well. Many, many thanks to Sunny for sharing his technique.

Notes:

Step 3 – Problem importing large database? Read this.

Steps 4, 5 and 6 – As in the examples below, be sure to leave the trailing slash off your urls.


  1. Copy your files from your webhost to your local server folder.
  2. On your webhost login to phpmyadmin and export your database (By Selecting your database and selecting the export tab and downloading to your computer)
  3. Log into your local phpmyadmin, create a new database and import the sql database into it by selecting the import tab and uploading your file.
  4. Once Uploaded we want to modify the database to reflect the new blog location being on the localhost. So we run the following SQL (Select the SQL tab and paste the following code):UPDATE wp_options SET option_value = replace(option_value, ‘http://www.hostedversion.com’, ‘http://localhost/testsite’) WHERE option_name = ‘home’ OR option_name = ‘siteurl’;
  5. We now want to fix the urls of posts and pages. So we run the following SQL:UPDATE wp_posts SET guid = replace(guid, ‘http://www.hostedversion.com’,’http://localhost/testsite’);
  6. If you have linked internally within blog posts or pages with absolute URLs, these links will point to wrong locations after you move the blog location. So we run the following SQL to fix this issue:UPDATE wp_posts SET post_content = replace(post_content, ‘http://www.hostedversion.com’, ‘http://localhost/testsite’);
  7. We want to now modify our wp-config.php file in our local server. Honestly, the easiest way to do this is to delete the wp-config.php file in your local server and then visit http://localhost/testsite in a browser.
  8. With the dialog message that comes up click the ‘Create a Configuration File’ button. Then click the ‘Lets Go’ button on the next screen.
  9. Fill in all of the fields:
    Database Name: This is the name of the database in your local phpmyadmin
    Username: This is your phpmyadmin username (usually root)
    Password: This is your phpmyadmin username’s password
    Database Host: This is usually localhost
    Database Prefix: normally is wp_ unless someone has changed it manually.
  10. Click Submit, the wp-config file will be created and everything should work on the local host.

Google Declares Mobile Friendly a Must for Websites

woman viewing mobile friendly website on mobile phone

On April 21, 2015, Google began using a website’s “mobile friendliness” as a ranking factor. That means that if your site isn’t mobile friendly, then it could be penalized in mobile search results. That could have an effect on traffic to your website. Here’s a link to test to see if your site is already mobile-friendly, https://www.google.com/webmasters/tools/mobile-friendly/.

Google’s mobile search algorithm update targets non-mobile friendly sites and rolled out through April of 2015. This is a big one, and could affect a large portion of your web traffic and SEO results.

In the last few years, mobile traffic has increased dramatically. It’s speculated that more than 50% of Google searches are performed on mobile.

Even Google is saying this update is going to have a bigger effect on search rankings than Panda or Penguin, the biggest updates Google has ever launched, as quoted by a member of Google’s Webmaster Trends team, Zineb Ait Bahajji at SMX Munich.

The problem is many sites are not responsive, meaning that they were only built for desktop computers and are hard to navigate on mobile devices.

Google doesn’t want to serve up results that are not mobile user friendly, so they are implementing a new algorithm change to demote sites that aren’t usable on phones and tablets. Google has said there is no degree of “mobileness”; it’s either yes or no.

If your website isn’t responsive, call ScreenTrend now! 515-243-0892 or email us at info@screentrend.com. If your website is responsive and mobile friendly, relax and pour yourself a cup of coffee and grin.

Additional Reading

The strategy behind Google’s mobile algorithm update and how “This update is really about Google’s vision of what the web should be—using its search results as a lever to move everyone in the direction it wants them to go.”