I will soon be 301'ing my entire site to its new home on a new domain, where it will live as a subdirectory of the main domain. It lives at the root of its current domain. Now, if every single old page had the exact same url structure as every single new page, the redirects are trivial. However, of the 200ish old urls that will need to be redirected, very few will exist at their new site "equivalent" (www.olddomain.com/somepage -> www.newdomain.com/olddomain/somepage) as most pages will have either a slight url change or exist somewhere else entirely, like at the root of the new site.
I'm assuming 200ish lines of specific singular 301 redirects in .htaccess would slow down the site pretty bad since .htaccess is loaded for every asset on the page, correct? As would (relatively) complex conditional logic with mod_rewrite?
Any ideas?
Side note: both sites, new and old, use WordPress, so if there are any WordPress-specific solutions, fire away.
It depends on your traffic, if it is a personal blog, then mod_rewrite should be fast enough for users not to notice.
Related
To add more detail, my current situation is that we are moving from Symfony2 to Wordpress (resources choice). Usually the redirect would require a relative link as source and a permalink as destination.
Let's call the domain http://example.com
Users with old links such as http://example.com/article/[id] need to be redirected to the new urls which is something like http://example.com/title
We have around 200 links that require redirecting and as you can see the new urls don't allow much for automating the process. My issue is if we set the .htaccess under the old installation and change the domain for it to example2.com, none of the users will ever stumble on it to be redirected.
Which leads me to ask if its possible to have a permalink on both ends of the redirect. I am open to any other suggestions to how to tackle the issue, except the old and new url formatting can't be changed in the current situation.
It might not be the most efficient way of doing it but, I get a list of all the links I need to redirect and a list of the new urls they are directing to and do a 301 redirect in the htaccess. This will change all indexes on google so they will show up without any issues.
Redirect 301 /article/1 /title
I'm new to the web world and i have a great mess in my head.
i got a project to build a website for a company and i did.
now this website was built with some cms and i built it with Wordpress.
So now i have to take care that some of the SEO meta tags will not ruin when moving to the new website, i used YOAST SEO plugin to do so.
Now my boss is keeping on asking about redirect 301 which i don't understand why do i need to use it?
if we dont transfer any campaigns and only moving to a new website why do i need it?
another problem is the mails on the domain.
the company has like 5 mails on the domain adress and the domain is sitting on the old company they used to work with,which are not cooperative.
how do i transfer the mails from their servers to a new one?
Thanks a lot.
The 301 redirects are for the newly created Url's.
Because every site has their own way or wwriting url's you need to make sure that you carry across the links to the old urls to the new url structure of the wordpress site.
Example
sitename.com/about_us.html is now sitename.com/about-us/ you will then need to redirect the old about_us url to the new one.
This ensures that any old indexed or shared pages don't server a page not found error.
Very important and can be done using the HTACCESS file or a redirect plugin.
I have a WordPress site. which is now moving to asp.net cms (Sitefinity). In this process my url structures are getting changed but I want to keep the traffic of previous urls on the new urls as well.
Old as the domain will be transferred to new site old pages will not be found (404)
Things making it complicated.
Old and new site has lots of Dynamic urls
Old site has different urls structure than new url
I do not wan't to put all these urls in web.config file.
Solutions I tried
I tried to write 301 redirect on Robot.txt as I can capture old and new url at the time of migration
I searched for solutions all over net but didn't got any straight forward solutions
One of the forums mentioned that we should not write 301 redirects on Robot.txt
Don't know what to follow or where to search. Please guide me to correct path.
Thank You
Chandresh
If you have an identifiable pattern between the two using the URL rewrite module would be your best bet. Or write some code to insert the old urls as multiple URLs on the content items.
Do you have an example of the old URL and what the new URL will look like? It is possible that if you know how the URL pattern will change you can create a redirect rule in your web.config.
Also, Sitefinity allows you to create redirects as well. This includes creating alternative urls for pages or creating redirecting pages.
The exact solution really depends on how much the URL is changing and how many redirect urls are needed.
I'm a new in web development so the question is maybe pretty simple, but I can't handle it by myself.
I have a wordpress website which hosts on hostmonster.com and it has a URL, let's say, http://aaa.com/bbb.org. So it is located in the subdirectory bbb.org of the main directory http://aaa.com in my host monster account.
I also have a domain name, let's say, http://bbb.org on godaddy.com and now I want to make my site available on address http://bbb.org. How to do that?
I did the following thing. I forwarded http://bbb.org to http://aaa.com/bbb.org in settings on godaddy.com, but it's not what I need, because user still see old address (http://aaa.com/bbb.org) in his address line. So what am I doing wrong?
I think you don't want to redirect from http://aaa.com/bbb.org.If so you will be need 5 step.
STEP 1: TRANSFERRING FILES
The first step in moving your website to your new domain name is to create an account on your server or shared hosting plan for the new domain and then transfer over all of the old website files to the new account you have created for the new domain. Be sure to just copy the files over and do not in any case delete the files from the old account for the old domain name yet.
STEP 2: CHANGE NAMESERVERS
Be sure and change the nameservers of the new domain name to point to the newly created account that you have created on your server or shared hosting plan. Keep in mind that it will typically take between 48 and 72 hours for the DNS to propogate throughout the web.
STEP 3: CHANGE FILES
The next step is to change all instances of the old domain to the new domain within the files that you have transferred over to the new account on your server. You will most likely be able to accomplish this very quickly if you just use the find and replace feature in your FTP client (i.e. Dreamweaver, FileZilla, etc.). Making all of your links absolute links rather than relative links is usually the best way to go for SEO purposes so if this is something that you had ever considered changing over then now would be a good time to go through and audit all of your website files to change relative links to absolute when appropriate.
STEP 4: CREATE 301 REDIRECTS
Setting up 301 redirects in your .htaccess (assuming you have a Linux server) under your old account is very important. A 301 redirect will work to automatically and permanently redirect visitors and search engine bots who visit www.olddomain.com/my-page to www.newdomain.com/my-page. This is very important from an SEO perspective because 301 redirects have the potential to pass through the “link juice” of any backlinks pointing to the old domain to the new domain along with any accompanying search engine rankings. This is also very important from a user perspective because anyone that tries to visit any page on your old domain will be automatically sent to the appropriate page on your new domain. Read this guide on how to set up 301 redirects to get all of the nitty gritty 301 redirect setup details.
STEP 5: TEST
Make sure that your nameservers have been set up on your new domain and that the DNS has finished propogating. Once you verify that the DNS is resolving correctly for the new domain then it is time to test out all of the old pages that you are redirecting from the old domain to the new domain and then also test by looking through each page of the new site and make sure that there are no errors (from find and replace errors when changing files or other issues).
If all of the pages of your old site have been indexed by Google then a quick way to test out that the 301 redirects have all been set up and working properly is to simply do an advanced Google search query that will return all of the pages from your old site indexed by Google. You can do this simply by typing “site:olddomain.com” into Google (without the “”). Now all you have to do is click on every page and if you have set up the 301 redirects properly then each time you click on the page link your server should automatically and instantly redirect you to the appropriate new page on your new domain.
That all you need ?
Typically, a hosting solution will have DNS redirecting that it will help you. The issue is that you might be using GoDaddy for your DNS managing. In which cause the redirecting DNS with hostmonster will not come through.
The best thing to do is have your GoDaddy point to the nameservers from HostMonster and have HostMonster control DNS. Then you can just create a redirect inside HostMonster and point bb.org it to http://aaa.com/bbb.org but your URL will just be bbb.org.
This sounds like a Masking problem, (you have enabled forwarding, but not masking) http://support.godaddy.com/help/article/422/forwarding-or-masking-your-domain-name
Also, note that you 301 redirects will be cached by clients, so use 302 redirects unless you are sure you've set it up the way you want it.
Make sure to follow the above answers. But using the The Duplicator plugin will streamline the actual Wordpress website migration very easily.
I have an old website that hasn't gotten much love over the years and that's about to change. The existing site is based on a 3.* version of an ASP.NET portal framework called DotNetNuke (DNN).
I'm going to pull that site down and bring up a new site based on a static site generator called Nanoc (Ruby based). I'll be serving the site with nginx.
I'm not sure how to go about redirecting the old pages on the new site. Many of the new pages will be completely new; several of the old pages will not be back up. I suspect there will be a few that I'll want to keep alive in some form, but certainly not with the same urls.
Should I be concerned with doing a fine grained redirect on each of the pages on the site (it's not a large site), or just handle it with a general redirect?
You only need to bother with 301's (permanent redirect, better than 302) on links you want search engines to know changed, or if people might have them bookmarked. Other than that, I would just redirect 404's that look like an old URL to your new home page.