citymarketing
asked on
IIS REdirect or webconfig ?
Hello,
I was hoping for a little advice. We are currently in the middle of a rebrand and will shortly introduce a new URL. We'll be copying over our current content so it will be exactly the same website under a new URL.
What I was hoping was that someone might be able to advise on is what method of 301 redirect I should be using. I have read that using page to page redirects is the best method to maintain our Google rankings (we are more or less the first result on a Google search of our key words) and we want to carry over that ranking.
So should I do this with the web.config file to get this 1:1 page match, or is an IIS domain level redirect suitable or......
many thanks in advance for any replies.
I was hoping for a little advice. We are currently in the middle of a rebrand and will shortly introduce a new URL. We'll be copying over our current content so it will be exactly the same website under a new URL.
What I was hoping was that someone might be able to advise on is what method of 301 redirect I should be using. I have read that using page to page redirects is the best method to maintain our Google rankings (we are more or less the first result on a Google search of our key words) and we want to carry over that ranking.
So should I do this with the web.config file to get this 1:1 page match, or is an IIS domain level redirect suitable or......
many thanks in advance for any replies.
@Patricksr1972, The question is about 301 redirects and not meta refresh redirects.
If you are just changing domain and all the page paths are the same then you can do a site wide redirect. But if pages are moving you will have to do each one separately.
web.config is the simplest way to set them up. If you have 100s to do you may find web.config is slow and hard to maintain. Then you will be looking into custom code using the Routing module to handle your redirects.
If you are just changing domain and all the page paths are the same then you can do a site wide redirect. But if pages are moving you will have to do each one separately.
web.config is the simplest way to set them up. If you have 100s to do you may find web.config is slow and hard to maintain. Then you will be looking into custom code using the Routing module to handle your redirects.
ASKER
Thanks for your reply tiggerito
We are just changing domain, as you say page paths will be the same. So perhaps a domain level redirect will suffice. However, Google seems to discourage blanket redirects and suggest creating page:page redirects to make the link between old and new domains and maintain page ranking. We do have several hundred pages and so web.config as you say might be too slow, in fact it would.
We just wanna keep our first returned result page rank on Google and keep our app functioning which runs off our primary domain !
We are just changing domain, as you say page paths will be the same. So perhaps a domain level redirect will suffice. However, Google seems to discourage blanket redirects and suggest creating page:page redirects to make the link between old and new domains and maintain page ranking. We do have several hundred pages and so web.config as you say might be too slow, in fact it would.
We just wanna keep our first returned result page rank on Google and keep our app functioning which runs off our primary domain !
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Quickest and easiest way is to have your old website URL include a index.html with following code
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="refresh" content="0;URL=http://www.mynewurl.com" />
<title></title>
</head>
<body>
</body>
</html>