SEO Class in Chicago, IL
Learn How To Optimize Your Website on July 26, 2013
High Rankings is offering a 1-day customized SEO training class in Chicago. Class size is limited so please sign-up now if you want in!
Are you a Google Analytics enthusiast?
Share and download Custom Google Analytics Reports, dashboards and advanced segments--for FREE!

www.CustomReportSharing.com
From the folks who brought you High Rankings!
More SEO Content
Using Nofollow Tag On Your Own Internal Links?
#106
Posted 23 October 2006 - 12:04 PM
I'll stop using the term black hat - but will continue to believe as I do about it's uses.
#107
Posted 23 October 2006 - 01:48 PM
Besides, I still don't like the idea of doing the search engines' job for them.
#108
Posted 23 October 2006 - 03:39 PM
As an example, if a page on the site was www.examplesite.com/products/, the printer friendly version would be www.examplesite.com/products/?printver=yes. Since the only difference is the parameters in the query string, I can't use the robots.txt exclusion.
Another set of pages I was considering nofollow for was an online perpetual calendar. I want the SEs to index the calendar for this current month and the three months prior and following, but I would then put the nofollow on months earlier or later than that. Otherwise the spider could in theory crawl from January 1 AD to December 9999 AD by following the Previous and Next links.
Any thoughts on this? Thanks!
#109
Posted 23 October 2006 - 03:54 PM
No, that's silly. You want to use the noindex tag for that. Nofollow won't do what you want, it just tells the engines you don't trust those pages.
#110
Posted 23 October 2006 - 04:20 PM
Thanks for the quick response.
#111
Posted 19 January 2007 - 08:21 PM
My bet is on the latter, but feel free to test that theory and see how it works for you!
Google clearly says on their blog that it doesn't have a negative effect or anything of the sort, but I also think the PR bleeding thing is fishy ;p
If any of you know other top SEs who follow this rule, please list, too. I can't find anything on Yahoo about them listening to it.
#112
Posted 23 August 2007 - 10:03 AM
Fascinating thread. NOFOLLOW surely is a curate's egg of a thing. So many ways to perceive it.
I don't go with the idea that NOFOLLOW expresses distrust or no-confidence. As it's been pointed out, we just don't host links to dodgy locations if we're sensible. And there's plenty of evidence that it deters comment spam. Note I say 'deters' and not 'prevents'.
As for using NOFOLLOW on internal links within a site (subject of the original post that kicked off this thread) I wonder how many correspondents have a different view nowadays?
How about this situation? I own a domain. I therefore own and control all the URLs under that domain. I've taken the trouble to design a logical URL structure that's extensible, but put together in a way that's pretty well future-proof. In other words the URLs are an abstraction, unrelated to physical disk folders and files.
I'm putting a site together for this domain. This is a data-driven site that presents pages generated from an external RSS feed whose content changes all the time. Dynamic pages list items from the feed in blocks of ten, and each listed item contains one or more links that will lead to the actual item hosted on the originating site. Yes, it's an eBay or similar affiliate site.
The item-links on my pages point to URLs in my domain. I don't want to generate a unique URL for every item listed (these destinations are oh-so temporary), so I re-use aliases in the range #1 - #10 within the URLs as identifiers. This strategy masks the affiliate nature of the page, obviating problems of bypassing and hijacking. Clicking a link sends the visitor back to the main script on my server, which 301-Redirects to the actual product on the merchant's site. This takes them exactly where they expect to go (I make it plainly obvious that these items are on an external merchant's site).
Given the 'conveyor-belt' nature of the merchant's inventory, item X on any page will likely be different every other page-view. I'm re-using a pool of aliases, so I can't really be putting a 301 on each of them, although I must 301 each request that gets back to my server. But by putting NOFOLLOW on my aliased internal links, I'm merely saying 'this takes you somewhere beyond my control', which it does, even if it initially points inside my domain.
Aside from anything else, my role is to send traffic, not page rank.
Any thoughts? Will NOFOLLOW on internal links bring about my unceremonious doom?
#113
Posted 23 August 2007 - 03:24 PM
Doom? Probably not. I've not seen any evidence of that sort of thing. However you can never predict when an engine or all of the engines change how they perceive something.
But on the other hand it would be so much easier to simply exclude your jump file via robots.txt. That's a method that has always worked and carries no risk whatsoever.
#114
Posted 28 August 2007 - 02:37 PM
I decided to go with unique URLs on the item links using an encode of the catalogue number. An URL is forever whether it's a throwaway or not, right?
So I have options. Neuter with NOFOLLOW and/or block with robots.txt. I can play around with that.
Thanks again. If there's anything to tell, I'll get back.
Jeff
#115
Posted 26 September 2007 - 08:20 PM
#116
Posted 26 September 2007 - 09:39 PM
#117
Posted 27 September 2007 - 12:32 AM
It must be in Internal Linking. The search results showed nothing in the Page Rank Forum. I'll keep searching.
#119
Posted 27 September 2007 - 01:35 PM
#120
Posted 22 June 2008 - 11:52 AM
Does anyone know how big of an effect this can have?
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users






This topic is locked



