Welcome to WebmasterWorld Guest from 18.104.22.168
Forum Moderators: open
According to Google:
"...if your old URLs redirect to your new site using HTTP 301 (permanent) redirects, our crawler will know to use the new URL. Changes made in this way will take 6-8 weeks to be reflected in Google."
I have had BlueWidget.com set up to do a 301 permanent redirect to BlueWidgets.com for over a year, so I'm not sure why BlueWidget.com is suddenly appearing in the Google. Also, since I'm using a 301 redirect, I cannot add a NOINDEX metatag to the page.
How can I remove BlueWidget.com from Google so I do not have 2 listings for the same website?
I agree about consistancy's sake. But for now, having two listings just means people are more likely to see it :)
Server Header Checker [searchengineworld.com]
I have had BlueWidget.com set up to do a 301 permanent redirect to BlueWidgets.com for over a year, so I'm not sure why BlueWidget.com is suddenly appearing in the Google.
I'll assume that you've made no host changes in the past 60-90 days and that nothing has changed with your current host and the 301 redirect.
I changed hosts last October and about every month or two gogglebot still tries to Get my old shopping cart and gets a 404 every time.
I also have a lot of redirects because of structure changes (over a year ago) and googlebot is still trying to Get many of them - sometimes several times a month despite getting a 301 every time. I think the reason for these is due to some other engine(Ink)/site that still has the old link. Took the bot about two months to get all the redirects listed correctly, but she still keeps a checkin' the old ones.
I do not want 2 listings because I do not want my site to be penalized for duplicate content.
Honestly, I wouldn't worry about it.
I have found Google not to be as strict on 'duplicate content' as they say they are. One site pointing to another is not a problem. You are obviously not duplicating content intentionally to put Google's listings in your favor.
The reason Google penalizes for 'duplicate content' is because they don't want people to try to list 50 urls with the same content.
Worry about other things like your consumer's usability of the site. The folks at Google are grown-ups: they can take care of their own site.
Also, I can't think of any reason why you couldn't use the meta NOINDEX on the old page with the 301. If it was a temporary change, you might not want to, but with the 301 the bots should go right on by to the new page the 301 directs them to so they would never see the NOINDEX unless the redirect was improperly set up - as has happend to you.
There is no old page. I simply purchased the domain name BlueWidget.com from GoDaddy and redirected it to BlueWidgets.com. Since my domain name is also a trademark, I didn't want someone buying BlueWidget.com trying to steal my traffic.
One site I work with was losing type-in traffic to another site with a very similar name - two words instead of three. The owner purchased the other domain name and "pointed it." I had specifically cautioned that it was OK as long as a 301 redirect was used. The web designer, not having a clue, "pointed" it, resulting in a 302.
The problem was that the other domain name had had a full site on it, with many inbound links, including an ODP listing. ALL the search engines messed up with it. The other domain - same theme, same target market, but totally different products, was kept by the engines and the correct domain got dropped. Obviously the rankings were all lost, since none of the titles and text coincided with the right keywords. I actually found it out accidentally when doing the regular hand checking so it was corrected.
It can have a very serious impact in some cases, since all traffic can be lost, with no one ever getting to the site. No rankings = no traffic = no income.
Not all search engines handle it as well as Google when it comes to correcting the error, either. On another site, Inktomi now has the OLD location of a site listed after a hosting change, in spite of a 301 for a year. Of course, the old location has no links pointing to it - they're all for the correct location, and rankings are around 15/16 instead of #1. That's caused a significant drop in sales.
It's very interesting because it shows us what the balance is between the weight of links vs. on page optimization, but it's not a good thing when it comes to earning income from a site.
HTTP Status Codes
10.3.3 302 Found
The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests.
10.3.2 301 Moved Permanently
The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs.
Since I got burnt by an incorrectly redirected domain a couple years ago, I went on a mission to learn everything I could about HTTP Status Codes.
In theory, a 302 implementation on parked domains or any domain that should be permanently redirecting is not correct. I feel registrars and those who offer redirecting services should be using the 301 moved permanently.
If I were a registrar, I'd probably allow the user to select either option; 301 or 302. I can think of very few instances where a 302 is needed but, if it is needed, then the option should be available. The 301 would be the default option with an explanation why a 301 is recommended.
I feel registrars and those who offer redirecting services should be using the 301 moved permanently.
Yes, 301 should always be the default unless there's a specific reason why it's temporary, and I can't think of many instances that really are. Unfortunately, 302 is the default in many places.
A lot of people don't understand the difference because browsers treat them the same.
URI - Uniform Resource Identifier
The generic set of all names/addresses that are short strings that refer to resources.
URL - Uniform Resource Locator
An informal term (no longer used in technical specifications) associated with popular URI schemes: http, ftp, mailto, etc.
URL is now deprecated. ;)
Well, normally on domain forwarding, the domain only points to the page, right? My domain registrar has done something weird and the forwarded domain picks up the page it is pointing to, but keeps the forwarded domain name as it's URL. I didn't choose domain masking...just regular forwarding.
When I enter the forwarded domain, its Google PR still shows...not the PR of the site I have forwarded it to.
By doing this, don't I now have two duplicate pages? One with the forwarded domain name and the page that I created to forward to? Also, am I still not guilty of cross-linking because all the links on the page go to my main domain?
I hope this all makes sense...it was a little difficult to explain without names. :)