How To Move Your WordPress Blog The SEO Friendly Way

wp-iconI recently had the urge to move my 4 year-old WordPress blog from over to a fresh WordPress install on this site, and I wanted to use a newly created directory named /blog/. Why? I didn’t like the layout of the old site at all, plus it makes more sense to blog here than from my own personal domain.

I knew this would be a challenge from a 301 redirect perspective, due to the fact that I decided to go with a completely different permalink structure AND have WordPress installed in its’ own directory instead of the web root like it was on the old site. So I figured I’d share my experiences…

If you need instructions on how to move your entire WordPress install to your new host/domain, check out the following pages depending on your situation:

Moving WordPress

Move Your WordPress Blog To A New Domain In 10 Steps

How To Move Your WordPress Blog to a New Domain

How To Move From To

The actual moving part was extremely easy, since I didn’t care about the theme, categories, tags, or any extra data from installed plugins remaining intact. In my particular case, I wanted to migrate all posts and comments ONLY, so that’s what I did.

The built-in WordPress import/export functionality didn’t work at all for some reason, so I had to find another way. The next best way to do it (if you’re comfortable working with the database) is below:

Moving Comments and Posts ONLY To A Fresh WordPress Install

  1. Just to be sure everything goes according to plan and the table structures match, verify that both WordPress installs are the exact same version. Upgrade if not.
  2. Log into the old WordPress MySQL database via phpMyAdmin (if you have forgotten or don’t know your login details, just open wp-config.php which is in the root folder of your blog…it contains all your db info), then select your database from the available options.
  3. Export the posts table to a file (also called a sqldump), then save the text file.
  4. Export the comments table to a file, then save the text file.
  5. Now log into the new WordPress MySQL database, select the database, then drop the comments and posts tables.
  6. Go to import and import each sqldump (text files) created from the old WordPress database.
  7. That’s it!

Great, but you’re not done. You still need a way to permanently redirect all visitors, search engines, and inbound links to the new site without just redirecting everything to the home page.

If you’re keeping the same permalink and directory structure this is very easy, just add this to the .htaccess file on the old site:

RewriteEngine On

RewriteCond %{HTTP_HOST} ^ [NC] RewriteRule ^(.*)$$1 [L,R=301]

NOTE: The ‘(*.)$’ says that we’ll take anything that comes after ‘‘ or ‘‘ and append it to the end of ‘‘ (that’s the ‘$1’ part), and redirect to that URL.

Important Notes About .htaccess Redirection

  • Verify that you’re not overwriting an old .htaccess file, sometimes servers place one there for your custom 404 pages, existing applications, etc.
  • Always be sure to upload .htaccess files in ascii mode, uploading as binary won’t work.
  • .htaccess will not work if you’re on a Windows Server (IIS).
  • Since some operating systems don’t allow you to make a file without something before the ‘.’, you may need to save it as htaccess.txt and rename it once you’ve uploaded it.
  • Make sure your ftp program will show .htaccess files (FileZilla does and is free).
  • Make sure you triple check your changes. Test the server headers to make sure you see a 301 (that means it’s permanent) not a 302 (temporary) unless you are absolutely sure you really mean temporary.

Unfortunately this was not the case for me. Everything went very smoothly when it came to moving the site itself, but now I need to redirect all old page names to the new URL and permalink structure.

In the past, I had two options here. I could create a very lengthy .htaccess file containing entries that map all old pages to new ones, but this would take forever so that’s out. I could use regular expressions with mod_rewrite in .htaccess to create rules to handle the 301 redirects, but that would be time consuming/complicated as well. What to do?

Luckily there’s a WordPress plugin called Redirection to do this for you. Not only will it save you tons of time, it also automatically prevents headaches for you down the road. Once installed, I was able to create 301 redirects with regular expressions to take care of everything using a simple admin panel:

Redirection Plugin Configuration

Let’s run through these quickly, shall we?

Redirections Sorted By Order

  1. /page/(.*)/ =>$1 – redirects all requests for paginated URLs to their corresponding paginated URL on the new site, for example ‘‘ to ‘
  2. /(d*)/(d*)/ =>$1/$2/ – redirects all requests for date-based URLs such as archives to their corresponding URL on the new site, for example ‘‘ to ‘
  3. /(.*)/(.*)/ =>$2.htm – redirects all requests for blog posts using the old permalink structure of /%category%/%postname%/ to their corresponding URL on the new site using the permalink structure of /%postname%.htm (notice the category is stripped from the URL), for example ‘‘ to ‘
  4. /(.*)/ =>$1 – redirects all requests for blog pages to their corresponding URL on the new site, for example ‘‘ to ‘
  5. / => – redirects all requests for the old parent domain name to the new parent domain, for example ‘‘ to ‘

NOTE: Be sure to test using your old URLs in your browser and verify that the order of redirection is correct. Also note that ‘‘ will no longer work after you’ve configured Redirection as I have. To login to your old site to check redirection/error logs and view stats, use ‘http//‘.

For more on regular expressions, how to use them with Redirection, and to download the plugin, scroll through the plugin author’s page:

WordPress Redirection Plugin

Pretty cool, right (OK…maybe not cool, but you know what I mean)? As if that’s not enough, here are several more features of the Redirection plugin worth noting:

  • 404 error monitoring – captures a log of 404 errors and allows you to easily map these to 301 redirects
  • Full logs for all redirected URLs
  • Automatically add a 301 redirection when a post’s URL changes
  • Apache .htaccess is not required – works entirely inside WordPress
  • Redirection methods – redirect based upon login status, redirect to random pages, redirect based upon the referrer!

If you find this plugin incredibly useful like I did, be sure to donate to the author and help support free software.

Related Post:

301 Redirect Example When Using Wildcard DNS For Subdomains



  1. Fatih
    April 18th

    Thanks for the post Jason. I experience the same difficulties when migrating old permalink (year/month/day/postname) to the new one (postname). Actually, platinum seo pack automatic redirect works well, except those links ended with trackback. E.g. cannot automatically redirect to Can you give me a simple guide what regular expression I should use to redirect those trackback url?

    Thanks in advance

  2. Hi Fatih, great question. Below is the regular expression for what you’re trying to accomplish.

    Source URL: /(d*)/(d*)/(d*)/(.*)/(.*)/

    Target URL:$4/

  3. These redirects would be the exact same as the regular expressions in your first comment, minus the trailing slash, so:

    Source URL: /(d*)/(d*)/(d*)/(.*)/(.*)

    Target URL:$4/

    As I noted in the original post, be sure to test using your old URLs in your browser and verify that the order of redirection is correct.

  4. shob
    May 1st

    had been using following permalink

    now i am using this permalink

    What regex should I use?

  5. shob
    May 1st

    Just wanna add that I am using my blog in subdomain

  6. Hi, in your first permalink do you mean, not %postid%?

  7. shob
    May 2nd

    Hi Jason,
    I am using post id e.g.

  8. Just making sure. Try this:

    Source URL: /(.*).html

    Target URL: /(d*)/(d*)/(.*)/

  9. shob
    May 2nd

    Hi Jason,
    Many thanks for your help. Unfortuntely, I am getting 404 errors.

  10. Hi Shob, after researching this a little more thoroughly, I don’t believe you can correctly setup these redirects using regular expressions.

    Unfortunately you will have to create separate 301 redirect entries in your .htaccess file that map old pages to the new ones.

  11. Fatih
    May 11th

    Hi Jason, another question..
    How to use regex to redirect non-slash url into the slash one?


    I got some duplicate content issue because of this

    Thanks a lot

  12. Hello again Fatih, this one is no problem at all:

    Source URL: /(.*)

    Target URL:$1/

  13. Bryan Lee
    May 13th

    Jason, I want to do the opposite of what you did. My site is at because at first I was going to do something else with the main domain. Well now three years later, I’ve changed my mind and want the blog to reside on the main domain. Any pointers on the best way to do this? Also do you think it will screw up my ranking with google if I make this change?

  14. Hi Bryan, this is no problem at all and very common. Check out the following support page for instructions, specifically the section titled “Moving WordPress Within Your Site”:

    Once you have everything moved over, here’s your configuration for the Redirection plugin:

    /blog/page/(.*) =>$1

    /blog/(d*)/(d*) =>$1/$2

    /blog/(d*)/(d*)/(d*)/(.*) =>$1/$2/$3/$4

    /blog/(.*)/(.*) =>$1/$2

    /blog/(.*) =>$1

    /blog/ =>

    Be sure to test the old URLs to ensure the order of redirection is correct.

    Also, notice that you need to include an extra expression that I didn’t need to because your permalink structure for posts include the date, for example:

    To answer your question about rankings…you might see a temporary decrease in traffic/rankings while Google updates their index with the newly redirected pages, but again this will only be temporary. Since these are 301 (permanent) redirects you will not experience any duplicate content issues.

  15. Hi Jason. You have good post. I really need it. I have a question. How do I redirect the following links using regex:

    Thanks in advance!

  16. SEO
    May 15th

    Thanks for posting! I really enjoyed the report. I’ve already bookmarked this article for future reference.

  17. Hi, try this and let me know how it goes:

    Source URL: /(d*)/(d*)/(.*)?comments=true

    Target URL:$1/$2/$3#comments

  18. Huang
    May 16th

    Great article, very useful for us…thank you

  19. Lee
    May 17th

    Very good information, you write very well. This information from you helped me tremendously with my blog migration.

  20. Hi Jason,

    I catch your post while looking for regex. I know you can answer or confirm, because the first comment in this post seems really similar to my question.

    I want to redirect all links in my site:

    from: http://example/2010/05/test-this.html
    or better

    can this be the solution

    source: /(d*)/(d*)/(.*).html

    or what?

    thanx in advance,

  21. That’s it exactly Kartal, except you need to make sure you include http in the target, so it would be:

    Source URL: /(d*)/(d*)/(.*).html

    Target URL:$3/

    Nice work!

  22. Devojke
    July 8th

    thanks for post, a have one question, is this default theme, or what is her name?



  23. Hi Marina, it’s actually a custom theme. 🙂

  24. Bryan Lee
    July 24th

    Jason, thanks for your advice. I forgot to look back to see your response before I went forward with the redirection plugin. If I read your response it would have saved me alot of headache 🙂 I basically made a couple sets of redirection entries:


    I then went through the 404 errors module of the redirection plugin to see if I missed any others. It was definitely a learning experience.

  25. Missy
    August 3rd

    Is there even a way to do this?

    Take this:

    To this:

    This is my permalink structure: /%year%/%monthnum%/%day%/%category%/%postname%/

    Thank you for any insight!!

  26. Missy
    August 3rd

    P.S…Sorry, I only want that url structure for a specific category that I want to appear to be separate from the blog… : )

  27. I believe you can but have no way of testing it myself. Try this and let me know:

    Source URL: /blog/(d*)/(d*)/(d*)/specific-cat/(.*)/

    Target URL:$4/

  28. Missy
    August 3rd

    Poo…throws this error:
    “The page isn’t redirecting properly

    Firefox has detected that the server is redirecting the request for this address in a way that will never complete.”

    The url shown is keeping the /blog/ path as well as the /yyyy/mm/dd/

    It’s like it doesn’t like when I try to remove the dates…I have tried a ton of variations and if I use:$1/$2/$3/specific-cat/$4/

    I can drop the /blog/ and have it work…but take out 1,2, or 3 and pffftt…

    I would even be happy if I could rearrange them i.e..$1/$2/$3/$4/ but it doesn’t like that eithier… : (

    Thanks you so much for helping it’s been driving me nuts any ideas are super appreciated!!

  29. choe
    August 13th

    Thanks for sharing this.

  30. Jawwad
    November 6th

    Dear Jason

    You are a life saver. I have spent the last 3 weeks trying to figure out how to redirect my year old site using the redirection plugin and despite a lot of help from a lot of people simply couldn’t figure it out. Your post, images, explanation and responses to comments are possibly the best resource for people who are using the redirect plugin. Thank you very much for putting it out there. Mucho appreciated.


  31. Jason Hendricks
    November 6th

    Thanks Jawwad, glad I could help!

  32. Todd
    December 6th

    Thank you so much for the tips. I was very helpful to me! Cheers.

  33. Dopisivanje
    December 21st

    thnx for this post mate.

    I use these tips a lot!

Leave a Reply

Quick Contact Form

Uncheck box to submit
(please prove you're human)

RSS Feed

Enter your email address to subscribe and receive notifications of new blog content by email:

Content Calendar
Free Consultation