Welcome to WebmasterWorld Guest from 220.127.116.11
Here is my experience with a recent 301 redirect:
--Popular travel niche website approx 4 years old.
--Actively covering all topics related to my niche but we also sell entire vacationsÖ think of this site as being a vortal covering everything and anything dealing with this niche including up-to-date news, weather, unique articles, forums, interactive tools for planning a vacation and a bunch more all of which are free.
--Very little link trading with the bulk of links coming in naturally
--Very little outbound linking
--Clean HTML (for the most part)
--Listed in DMOZ, Yahoo Directory, Zeal and Google Directory
--Was a PR 4 with about 50 inbound links
--Index count was 6,080
--Was in the top 10 results pretty solid even through Bourbon and other various updates
The 301 bomb (website suicide), applied a domain wide 301 redirect via IIS to a domain that is 18 months old. E.G. olddomain.com/widgets --> newdomain.com/widgets
I have seen some people post ďwhy would you do this?Ē Ö this isnít a valid question in my opinion because there are lots of very good reasons to do so.
--301 was put in place roughly 80 days ago
--After approx 5 days the site was nowhere to be found in the SERPís
--Sent a request to help@ and was told the site was not banned or penalized
--Started the long waiting process
--Quasay non existent update Gilligan started
--Old domain was stripped of PR across all DCís
--New domain still has no PR on any DCís
--BLís update to 138 on most DCís
--Google Directory updated showing the new domain as a PR 6 and at the top of my niche
--site:oldsite.com would reveal the new domain
--index count is fluxing between 10,300 and 10,900
--PR begins to return to the old domain!
--alas, no where in the SERPís even after going 50 pages deep.
Sounds like classic sandbox in my opinion but I think a better name would be ďGilliganís IslandĒ because most of us in 301 club feel stranded on a deserted island with no hope of rescue but occasionally there is a glimmer of hope on the horizon.
I also want to point out that until you have been through an experience like this itís not helping anyone to call people in this situation whiners, or something inflammatory because we are simply trying to figure out how to make a some what smooth transition and to avoid the sandbox.
Well, if you are still reading you are probably in this position now but if you are thinking about doing a 301 redirect, do so understanding that you will loss rank for at least several weeks.
Here some alternatives that have been discussed
1)Meta refresh to new domain Ė bad, could get a dupe content filter
3)302 redirect Ė is not permanent and is also very spammy looking
4)404 all old pages Ė donít know how this would work
5)Build a new site which simply wasnít an option for me because I have a lot of unique content that would take weeks to regenerate without having any duplication
Another way to look at this was put best by jd01
New Domain with 301 from old site = New Site
New Domain with no redirect from old site = New Site
New Domain with meta refresh from old site = New Site
New Domain and old domain with old content = New Site & Dup Content
IOW New Domain = New Site
Don't change if you don't have to - the, for lack of a better term, sandbox is in play.
Being that GoogleGuy is the closest thing we have to a direct contact (for most of us anyway) I would greatly appreciate his feedback.
As I said, the 301 redirects have been in place for a very long time and previously Google saw both www and non-www as the same (ie showed the same backlinks for both)
301 update for me,
My site is now showing a PR5 for the homepage and many interior pages but as of today still not appearing in the SERPS.
The old domain is still in the supplement index.
Index count is 13,300
Gbot is putting the smack down on me a couple of times a day.
My HTTPS pages are showing a grey PR bar.
My allinanchor searchs are mostly in the top 10 (what does this mean anyways‚Ä¶ is this supposed to represent your actual position?).
My only Google traffic is from images!
All of the sites with 301s are still showing in the SERPs. With traffic being more or less the same as it was 2 weeks ago (pre Jagger). Only one of the sites has seen a reduction in Google traffic (down about 43% from pre Jagger).
At this time I am just trying to determine why the non-www URLs no longer show any backlinks (and of course if this issue is going to result in further problems down the road).
Say you have a high ranking website with thousands of backlinks, and you buy out another website/company/take possession of it. Would having that site 301 redirect to your high ranking website cause problems or even the sandbox again!?! Maybe it would be better to just say our new link is at: and the link to your high ranking website? Google needs to fix this 301 problem.
we may be due to replace the code that handles that in the next couple months or so. If it‚Äôs really easy for you to wait a couple months or so, you may want to do that; it‚Äôs always easier to ask crawl/index folks to examine newer code than code that will be turned off in a while.
I would not risk another redirect for any reason so I would just place a link to the new site and 404 all the pages.
marty98, if you are running ASP I might have some code for you on my personal site that would be of help... sticky mail me for the URL. To answer you question however I don't think either method is safer than the other but consider 301'ing a single page at a time would only effect that page. Again, it appears Google is working on new 301 code so Iwould wait until that is in place before doing anything else.
Is it possible that the lack of the "/" could be the problem?
Here is my situation.
Several long exisiting domains with 301 redirects from the non-www URLs to the www URLs (redirects have been in place for about 2 years).
Backlink checks for www and non-www URL used to always show the same number.
Now a [link:example.com] for all of them show zero (0)backlinks.
They are all hosted on IIS servers and the 301 redirects are to http://www.example.com and not to http://www.example.com/
Any insight into this?
Our programmer wants to use ASP on our retail site product pages, rather than the existing html, mainly as he wants to handle basket function without the need for a cookie (there are some other reasons, but I don't have a great understanding of prgramming issues). But I do know it is very disruptive to Google results when page URLs change.
Would appreciate it if you could expand on your above comment, or point me in the right direction for getting more info.
With IIS you right click the domain name, click properties, click the home directory tab, click configuration, click add, the executable is C:\WINDOWS\system32\inetsrv\asp.dll, the extension is .htm or .html or add both... this should force IIS to process .htm files as ASP. I will sticky you a link to my personal site that has screen captures of the process.
With Apache using .htaccess file you can use:
AddType application/x-httpd-asp .html
AddType application/x-httpd-asp .htm
I haven't tested these examples fully but this will get you on the right track.
Some control panels will also let you do this sort of thing... I believe it's considered mime types...
Let us know how it works out for you...
From my experience I would say that this should go over pretty easily if we just 301 the old underscore pages to the new matching hyphen pages.
Can anyone say if they see a problem with this? Or how they would do it. The site has a very high PR and I just think that if we let the old 404 pages just die out and wait for the new pages with hyphens to index that we could really set ourselves back.
Let me know - thanks
It's a 5 year old site with good rankings...am I risking my serps by doing this?
Btw, how long do I need to keep a 301 redirect in my .htaccess before I can remove it? 99% of my IBL's are to my domain (http://www.grenvillestation.com/) and not subpages. I also use google sitemaps regularly.
Most of you are talking about 301 redir from old domain to new domain...
what about using 301 redir for redirecting old pages (that are still indexed) to new pages with simular content?
is it better to do so or should I delete them and use 404 or maybe just leave it as it is?
Thanks in advance,
I just checked the server headers using:
and it is returning this:
#1 Server Response: [domainname.com...]
HTTP Status Code: HTTP/1.1 301 Error
#2 Server Response: [domainname.com...]
HTTP Status Code: HTTP/1.1 200 OK
Is the #1 Server Response okay ie: "301 Error"
Should it not be:
#1 Server Response: [domainname.com...]
HTTP Status Code: HTTP/1.1 301 Moved Permanently
As you can ses from the #2 Server Response, the redirect is working okay. (200 OK)
Thanks for your help!
I set up a 301 to redirect http:// to [www...] on Nov. 6. I used some code in another thread on Jagger as I was under the impression this "double" listing could indicate trouble ahead if I didn't fix it.
The redirect is working fine, correct header responses etc, but I'm now noticing:
is returning 0
returns the usual number of backlinks.
Added to this, when I search for my site name (not domain), I'm presented with my DMOZ title on the link and the DMOZ description, then one of my sub-pages underneath that (with correct page title and description).
If I search on my domain name, I only get the http:// listing - no fresh tag either. This is happening on most DC's.
Rankings have plummeted for most terms. For those of you who've done this type of redirect before, should I reverse the htaccess fix, or is this normal behavior and I should just wait it out? Is it the same sort of wait as on a usual single page redirect?
I've performed 301's before for single pages, but this is a different scenario, behaving totally differently and I'm a little concerned. I wasn't expecting my [site.com...] listing to get buried/virtually disappear, just to get rid of the [site.com...] listing. Any advice would be appreciated.
BTW, Googlebot is very active on the site at the moment.
Try and find any major incoming links that point to the wrong version and get them amended.
Make sure that your internal linking points to the correct one. Add the <base> tag if necessary - especially to the root index page.
If you link to a folder anywhere on your site, make sure that the URL ends with a trailing / on the link. This is VERY important. Check your site with Xenu LinkSleuth and look for any irregularities.
I would suggest to see where you are at the end of the month...
you right on target about that one. I have Part Number for my widgets that is unique to my site(well unless the page has been scraped so it shows on scraper site)
if I do a search Google for that Part number: results are shown in the following order
1. Listing for a page that used to list the Item, now this page was 301nd in march, and Googlebot had revisited the page at lease 7 times already, shows as a suplemental page.
2. Page that had this part number, later removed. This page was removed from the index using Removal Tool in February due to a duplicate content, and after comming back in to index as Suplemental has been revisited twice already where GBot got 410 code.
The URI is Still there.
3. message says that: 'In order to show you the most relevant results, we have omitted some entries very similar to the 2 already displayed.
If you like, you can repeat the search with the omitted results included.'
Now if I expand the message:
First 2 stay the same.
then goes #3 as a non WWW version of the page with cached date of LAST NOVEMBER. page returns 301 for the past 9 month and has been revisited at least 3 times by GBot
4. A version of the same page cached date in JUne.
problem with this one is that there was a link to this page from a scraper site with 4Ws like htt*://wwww.mysite.tld/mypage.cfm - suplemendal result. if you click on the page the page returns 410.
and then Finaly my beloved widget page as a current with a current cached date couple of days ago.
Notice: Pre Jager this page ranked #1 out of 2Million or so, where now its at #80 or so.
Interesting, Should I stay or should I Go?