Relocating from WordPress.com to WordPress.Org

WordPress is a free and open source blogging tool

From WordPress.Com to WordPress.Org

So, you have reached that pivotal moment in which you crave more out of your WordPress website. Using the .Com Platform, You have had some good times with all the free maintenance and access to numerous widgets you might have otherwise had to pay for. However, now the time has come where you want your WordPress Site to put out as much as you have put in.

By moving to WordPress.Org you have the ability to customize themes and incorporate specific plug in’s you wouldn’t normally have access to using the freely hosted WordPress.Com. You can also start to make money from your website through Google AdSense and other affiliate programs. These are two very reasons many get into blogging, to monetize; something you can’t do with WordPress.Com

There are a multitude of differences in WordPress.Com compared to WordPress.Org, but we are here to help you with a problem that a lot of WordPress.Com Site Owners encounter: How to make the transition to WordPress.Org.

We know you’re anxious to move your content [images included] and keep your Sites traffic unaffected; to do so you need to also redirect visitors to your new WordPress.Org Site. Let’s transition your freely managed WordPress.com Site into a self-hosted website.

Moving From WordPress.ComWordPress CMS

Before we can begin the transition, there are some things you will need to have; such as a unique Domain Name. Try a quick Google Search or use a popular Keyword Tool, like SerpStat.Com to help you craft a great [and potentially high ranking] relevant Domain Name for your new WordPress.Org Website. If you already possess a Domain Name your transition to WordPress.Org may be a little easier.

Next invest time in researching companies that know WordPress. Not just popular CMS in general, but WordPress Specifically. This ensures that your Websites Maintenance and Support needs are met by experienced professional and not run-of-the-mill tech guys. Blue Host and Site Ground are two highly recommended providers.

You will also need access to your WordPress.Com account so that you can easily relocate all your existing data to your new WordPress.Org Website. This will include imagery, post, links, etc. Any content that you feel like you would want to incorporate in you WordPress.Org Website later.

Step 1: Transferring Data from WordPress.Com

By signing into your existing WordPress Account you can access Export under Tools Menu. Exports will redirect you to a new page where you have the option of Free or Guided Transfer.

By choosing the Free option and clicking Export, you will be asked what content you wish to transfer. Select All Content>Download Export File.  Downloaded unto your computer will be an XML file which contains navigation menus, images, comments, and other data stored on your existing WordPress.Com Site.

Step 2: Setting Up Self-Hosted WordPress Sitetop 5 wordpress security plugins

Once you have completed you WordPress.Com content transfer successfully, you can begin setting up your self-hosted WordPress Site.

Following the simple guide given by WordPress.Org you can have your new site set up within five minutes. When you have finished WordPress installed you can begin importing your saved WordPress.Com data.

Step 3: Incorporating Previous Content into Self Hosted Site

To begin adding your previous WordPress.Com data into your new self-hosted WordPress Site, head to your new Dashboard and locate Tools>Import. Select WordPress and install the WordPress  Importer plug in as prompted. You must install, activate, and run the Importer plug in.

Once complete you will be directed to a screen which allows you to upload your previously stored WordPress XML file. Once the import has begun, you can assign the content to a new user or an existing user.

You will also be asked whether or not you want to include attachments. You most certainly do, as these include images!

Step 4: Importing your Existing Blog Link Roll

In case you had been using the Links Feature on WordPress.Com, let’s take a moment to import those as well.

As an OPML File, in XML Format enabling you to export links and their respective categories, the location address for WordPress.com reads something like this: http://example.wordpress.com/wp-links-opml.php. If you have a custom domain name already, yours will read as follows: http://www.example.com/wp-links-opml.php. By replacing Example with your WordPress Sites Domain to access your OPML File in your browser for downloading.

Once you have finished backing up your Blog Link Roll, you can begin importing them; however, Self-Hosted WordPress doesn’t come with the Link manager enabled, so we have to take a second to install a reliable Link Manager plug in. This particular plug in is said to be the best one to incorporate. When completely installed and activated, a new option will be added to your WordPress.Org Dashboard: Links.

The Link Plug in will direct you to the Importer tool, where you can start uploading your existing OPML File by clicking its Import Button.  WordPress will handle the importing of the saved data and once completed send you a success notification.

Step 5: Your Private WordPress.Org Blog

Finally, you want to set your fresh WordPress.Org Website to Private. Note: these next few steps are for those who do not intend on redirecting their previous site traffic to their new WordPress.Org. If you want a completely fresh start and don’t want to bring sand to the beach, you can set your new site to private, here’s how.

Located on your New WordPress.Org Dashboard Settings, click Reading, continue to Site Visibility. Select the last option, “I would like my site private…” and you have just blocked access to your site to anyone you have not invited or approved.

Step 6: Redirecting Site Traffic & Keeping Previous WordPress Following

If you have developed a great following with your WordPress.Com Site and want to keep them around, you can easily redirect them to your Self-Hosted Site. We are pretty sure that experienced bloggers might have managed to get their blogs indexed and would want to miss out on that continued Site Traffic.

Using a 301 Header to redirect visitors and search engine bots is the most common way to retain your existing WordPress Sites following and transfer it to your new self-hosted site. Since WordPress.Com doesn’t have .htaccess for freely hosted sites, you will have to purchase an upgrade called Site Redirect if you wish to retain Search Engine Traffic as well. This can be located within WordPress.Com Store and priced around $13.

You can choose to purchase this however long you think it will take to fully transition your exiting WordPress Following and future Site Traffic to your new WordPress.Org Blog; it is recommended between a year or two, however with social alerts and Newsletters you can also inform your readers of site changes.

Also, note that if you have decided to change your domain name as well, you might want to do so with your contents attached URLs and Location Addresses. You want to make sure to update all imported content URLs including Imagery.

Support Moving your WordPress Blog

business people group with headphones giving support in help desk office to customers, manager giving training and education instructions

Making the transition from WordPress.Com to WordPress.Org can be written to seem easy; however, CMS Managers understands that not every one may understand how to implement to information provided here, which is why they provide help with moving WordPress Blogs and other Support and Maintenance needs WordPress Users might encounter.

Contact them when you are ready to make the transition from WordPress.Com to WordPress.Org. They will have hands on https://www.cmsmanagers.com/the-top-wordpress-maintenance-service/ to assist you or manage to the transition for you today.


This entry has 0 replies

Comments open

Leave a reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>