I used to have this blog hosted at http://www.imbermedia.net/blog/en for English, and /jp for Japanese with a standard HTML site at the root for imbermedia.net. Not long ago, I decided that I will figure out how to make my own WordPress themes, and that I will put my blog, bi-lingualy right here at the default root folder. While I have yet to make my own theme, I did move the blog.
My hosting provider, Media Temple keeps track of processor usage calling them GPU’s, and each user gets a limited amount of GPU’s included before they have to start paying. Since I ran my blog at the old URL for a rather long time, lots of people are still accessing the old URL and either getting errors, or the round-about on getting my RSS feed.
Here’s a screenshot of my GPU usage:
As you can see, hits for my old RSS feeds are consuming more than anything else on my site. Now it’s not like it really amounts to so much traffic that I really have to worry about it in the sense that it could cost me money, but I would like to clean things up, and be sure that everyone who is trying to access my blog is able to do so.
Is there anyone that knows how to do something about that? I want to be sure that I don’t loose anyone, particularly my Mom and Grandparents who have my old RSS feed bookmarked on their address bar back home.
You could set up a re-direct in your .htaccess file to send people from the old locations to the new. I can’t remember the syntax off hand, but I’m sure you can find it on google.
Yea, I tried that, but I’m not sure that I did it right. Do I need to put a seperate .htacces file in each of the directories that I need re-routed, or can I put them all inside the main one in the root folder?
The syntax I found seemed to want to redirect everything, (for example domain.com/blog to blog.domain.com where is I want to go domain.com/blog to domain.com)
Actually, I think I may have it. Here’s what I did:
It certainly forwarding, and it’s maintaining the url instead of recreating like it was before (which I think is what took up the processor time). Now to wait another billing cycle to see if there is a drop
One .htaccess file should be enough