Nofollow tags
-
So on the homepage, should all the links like privacy, contact us, etc...be rel="nofollow" ?
I want to get a better handle on passing as much link juice on homepage to important internal pages as I can, and want to get it right.
Thanks in advance.
-
What about 12 outbound links to external client sites not related to your service.
-
unfortunately, if you can't place a NOINDEX meta tag due to limitations of the CMS then you probably won't be able to place a rel=nofollow either... leaving you with a disallow in your robots.txt.
-
what if you can't place noindex into the html head (limitation of the cms) would a exclude in the robots be enough on its own? (or at least better than nofollow links to the page)
-
simply exclude or 'disallow' the file path in the Robots.txt. Then place NOINDEX, NOFOLLOW meta tag on those pages (in the HTML head before the body). If you have important links on those pages then use the meta tag NOINDEX, FOLLOW. I hope this helps... please ask for clarification if you need.
-
Yes - follow the link in my expanded answer above... the ink points to Matt Cutts original article from February 2009 explaining how/when/why the change was made.
-
"They changed this (I think in 2009) to : If you had 10 links on a page and 5 were nofollowed each link would still only pass on 1 PR point. The remaining 5 points essentially disappear into thin air."
R u 100% sure about this? any sources to back this up?
Thanks
-
You are "over my head" lol.
So for sitewide contact, privacy, etc...what is the best thing to do?
Thanks!
-
Haha! For some reason I didn't see the other post... thought I was the only responder.
Be well!
-
Anthony, I never said I disagree with you. I did not see your answer at first, I must have opened the thread before you posted your answer. reading your answer now yes, we are in agreement.
-
I'm confused about what you are disagreeing with me about... there is the meta NOFOLLOW tag that is placed at the page level and the more granular rel=nofollow attribute at the link level. They are not interchangeable but simply give more macro or micro control over links on a page. If you read my answer carefully you will see that we are in complete agreement over link decay using the rel=nofollow attribute on individual links.
-
No you should not.
When the nofollow tag first came out you could "sculpt" page rank by saying which pages you can pass it on to, this is no longer the case. Google made a change a few years back to stop people from doing this. An example would be:
When nofollow first came out: If you page had 10 links on it, each link would pass on 1 point of page rank (PR). If you nofollowed 5 of these links then each link without the nofollow tag would then pass on 2 points.
They changed this (I think in 2009) to : If you had 10 links on a page and 5 were nofollowed each link would still only pass on 1 PR point. The remaining 5 points essentially disappear into thin air.
So by adding nofollow to internal pages you are wasting your PR, rather let it be passed on to your less important pages which will return a certain amount back to the top level if you linking structure is correct. Only use nofollow for external links which you don't want to pass on PR to e.g. If it could be considered a bad neighbourhood etc. This may not be 100% how it works but the basic concept is correct, there are extensive explanations of this on Matt Cutts blog.
-
First there was the NOFOLLOW meta tag for page-level exclusion and then Google adopted the more granular rel=nofollow attribute for individual links on a page. I find that too many SEOs overuse the rel=nofollow attribute when there is a much more elegant solution available. The reason for this is now myth formerly known as the abused tactic called PageRank sculpting. I had a well-known culture/nightlife site in NYC as a client that had placed literally thousands of rel=nofollow attributes on links throughout the site... granted this does not seem to be your problem but I digress...
To illustrate my point, Matt Cutts discusses how rel=nofollow attributes affect how Google passes PageRank to other parts of your site (or more precisely how nofollows decay the amount of link juice passed). In the case of a few pages or even large directories, etc, I would do the following:
- Disallow crawling of less valuable pages via Robots.txt
- Use the meta exclusion NOINDEX, NOFOLLOW tag at the page level - unless these pages pass valuable link juice/anchor text to other parts of the site then use NOINDEX, FOLLOW (page is not indexed but important links are followed)
- Also, leave these pages out of your XML sitemap(s) - although you may want leave them in the HTML sitemap and place a granular rel=nofollow at link-level in the case of a 404 error page for usability purposes or required privacy statement for landing pages.
Saving your Googlebot crawl budget for only high value pages is a great way to get more of those pages in the Google index providing you with more opportunity to promote your products, services, etc. Also, limiting the number of rel=nofollows used and allowing link juice (or Page Rank) to flow more freely throughout your site will prove beneficial.
-
There was a time I would have said yes. Nowadays its hardly worth the trouble.
However, if its easy to implement, why not? You might get some marginal benefit out of it.
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Canonical tags in the body?
Hi there, Does anyone know if placing canonical tags in the body instead of the header of a page will still "take"? The system we are on means that making an editable header is no easy business and I was just wondering how big of a difference it makes to have it in a different area. Thank you in advance.
On-Page Optimization | | Whittie0 -
Titling and H1 Tag Question
What to do if you have hundreds of thousands of a particular product. Comic Books for example. Is it ok to have the words Comic Book in the title and H1 tag as long as it is qualified? For example, if I have the following as both the Title tag and the H1 tag. Comic Book - Spider Man Versus Wolverine Comic Book - Silver Surfer Goes Home to Visit Mom. Comic Book - Superman Gets a New Kitten Comic Book - Wonder Woman is More Wonderful Than You Know As of now, I have been doing it this way, but only in the title tag. However, Google has been using my H1 tag as my title, so in the search results, I am only getting: "Superman Gets a New Kitten" And I am afraid that that is leaving out important info for searchers, especially qualifying that the product is a Comic Book and if someone is searching for a Comic Book, I need that to return. But I don't want any 'more' trouble from the Panda. Again, this will be hundreds of thousands of products. Thanks for your help! Craig
On-Page Optimization | | TheCraig0 -
On page "F" and I changed my tags long ago to match everything and still F?
My on-page analysis shows that my title tags are not supporting my keyword..........but they are! My title tag has my EXACT keyword phrase. What gives? Keyword is "San Diego Party Bus" Title is "San Diego Party Bus | xoxoxox | xoxoxoxo" F grade! ????????
On-Page Optimization | | DrewSpinoso0 -
SEO Location Pages - ALT Image Tag Question
Hello Guru's, I have a Hire Website whereby you can rent products online. I have created different Location pages for these which are in essence the same pages page but with different location specific urls, title tags , on page content etc etc. This helps me to rank for local search. These location pages also display 20 products per page. My question is Should I make the ALT IMAGE TEXT location specific for each of the 20 products . Example - Steam Cleaner Rental in "location" or should I only amend a few of the Atl Image Texts to be location specific. I don't want to come accross as spammy in google eyes but I also don't want to be seen as having duplicate content , images etc etc What do you think ? thanks Sarah.
On-Page Optimization | | SarahCollins0 -
Alt image tags not being read by on-page optimization tool
Can bots see the keyword among other words in aIt image tags? For example, if the keyword is upholstery leather and the image tag says "our upholstery leather collection" will the keyword be recognized? Another example is buy leather. I have a image tag on a slide that reads "free samples before you buy leather" but an on-page analysis in moz does not show an alt tag title for buy leather? Same problem with an moz on-page analysis of the term upholstery leather. Thanks! Hunter
On-Page Optimization | | leatherhidestore0 -
Nofollow images to sculpt internal anchor tags
One of my client tags image-links with nofollow if those links are before a regular HTML link in the source code, e.g.:
On-Page Optimization | | Sebes
.
.
.
Check our page aboutreally cool shoes. They do this to "better pass anchor tags" to the page /page-about-shoes.html. My question: Is this a good practice to do? Thanks Sebes0 -
Is is it true that Google will not penalize duplicated content found in UL and LI tags?
I've read in a few places now that if you absolutely have to use a key term several times in a piece of copy, then it is preferable to use li and ul tags, as google will not penalise excessive density of keywords found in these tags. Does anyone know if there is any truth in this?
On-Page Optimization | | jdjamie0 -
Should I noindex both category and tag archive pages if I have an excerpt format?
I am creating a blog and want to know if I should noindex archives for categories and tags. I changed the format of my blog to excerpts to prevent duplicate content, but I want to make sure I also need to noindex those pages. Please help!
On-Page Optimization | | lwilkins1