John,
The googleoff and googleon tags are meant for Google's enterprise site search product, Google Search Appliance. They "shouldn't" have any effect on the public index. Do you have an example where you can prove they work in Google search?
Welcome to the Q&A Forum
Browse the forum for helpful insights and fresh discussions about all things SEO.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
John,
The googleoff and googleon tags are meant for Google's enterprise site search product, Google Search Appliance. They "shouldn't" have any effect on the public index. Do you have an example where you can prove they work in Google search?
Takeshi gave some great advise, and I agree.
I do like the idea of varying the footer navigation by category though. For example, you might interlink Men's Shoes with Women's Shoes, but you wouldn't want to link to Women's Shoes from Men's Shirts. Keeping the footer from being site-wide and making the links more relevant to the page their on will, I think, allow those footer links to carry more weight than they would otherwise.
Whatever you choose, make sure it's best for your users. Do that and it's difficult to go wrong.
Steve,
Yes that would be cloaking. I wouldn't do that.
As Pete mentioned below, your only real options at this point are to make some of the content, or new content, available for public use. If you can't publish abstracts at least, then you'll have to invest in copywriting content that is legally available for the public to get traffic that way, and do your best to convert them into subscribers.
From - http://www.amazon.com/gp/help/customer/display.html/?nodeId=508088
COPYRIGHT
All content included in or made available through any Amazon Service, such as text, graphics, logos, button icons, images, audio clips, digital downloads, and data compilations is the property of Amazon or its content suppliers and protected by United States and international copyright laws. The compilation of all content included in or made available through any Amazon Service is the exclusive property of Amazon and protected by U.S. and international copyright laws.
In short, you don't own those reviews even though they are about your product. The reviews were left on Amazon.com, and are therefore the property of Amazon.com.
Oleg makes some good points about putting those links on an index page for the articles (like the articles "section" of the site, which would be linked to from the home page) instead of putting every article link on the home page. However, I would argue that if these articles aren't helping "your website accomplish its goals" they shouldn't be on your site at all. Even if "SEO" is considered a goal of your website, you're bound to fail if you publish article-style content just for that reason.
So in your strategy I would really think about how this content is helping your users. For example, where in the process of their journey on your site they might need/want to see that content (e.g. 'How to Choose a Widget' might be linked to from your widget category, or 'Ten Ways to Use Your New Widget' might go on a widget product page)? That would be where you want to link to it from.
Bryan,
If I were removing 100 product pages from an eCommerce site because they barely convert I would approach it this way:
#1. Run the URls through a tool to see which ones have external backlinks.
Often times none of the pages will have any external backlinks, and those that do are usually not very good. If this is the case - or if you "really" aren't able to do any 301 redirects (and if so that's something that needs to be fixed) - skip to step #3. Otherwise...
#2. 301 redirect those with external backlinks to the most relevant page, be that a similar product or the category page directly above the product to be removed. Try to avoid redirecting them all to the homepage or some other "catch all" page, as these may be treated like a 404 by Google.
#3. Simply remove the pages and show the custom 404 page that suggests other products, or whatever messaging you want to show there (e.g. "This product has been removed from our catalog. Please see these other products...") and be sure to check the http header response code (lots of free tools for that) to ensure these URLs actually serve a 404 response (note: This should show up on the removed URL, as opposed to redirecting the visitor to another page like .../404.html).
#4. Since the now-removed URLs are not linked to from anywhere, either internally or externally, it could take awhile for Google to recrawl them and see the 404 error. If you need this to happen more quickly, such as when dealing with duplicate manufacturer descriptions and removal of page to recover from Panda, it may be wise to provide some type of html sitemap file listing out the URLs long enough for Google to recrawl them.
I would not block them in the robots.txt file, as that could result in Google not seeing the 404 and not removing it from the index (though they will cease to show the meta description).
If it's Amazon you are concerned with you could probably just leave them as-is. However, you could also run a scan of your site using a tool like Screaming Frog or OSE and look for outbound links going to Amazon.com and other known affiliate sites. This will at least make tracking them down to manually update them easier.
You could probably have this done at the database level too, though that is something for which you'll probably want to hire a DBA.
The following article has the best idea I could find for your situation, though it still isn't perfect because you could be applying a nofollow meta tag (as opposed to a nofollow link attribute) to pages that have both affiliate links AND editorial links that you want followed. At any rate, I hope this helps: http://www.bradlinder.net/2011/05/how-to-add-nofollow-attribute-to-all.html
I think this is actually a really good question. The main reason most SEOs these days don't "sculpt" or "shape" with nofollow links anymore has to do with the fact that they will still take away from the total amount of pagerank available to be passed on to other links on the page. So the question I'm reading above seems to be:
Do<a data-href...="" links="" still="" take="" a="" portion="" of="" pagerank="" away="" from="" the="" total="" pr="" available="" to="" be="" passed="" on="" other="" same="" page?<="" p=""></a>
<a data-href...="" links="" still="" take="" a="" portion="" of="" pagerank="" away="" from="" the="" total="" pr="" available="" to="" be="" passed="" on="" other="" same="" page?<="" p="">My answer is "I don't know" but I'd like to see a test if anyone can think of a way to try it out.</a>
<a data-href...="" links="" still="" take="" a="" portion="" of="" pagerank="" away="" from="" the="" total="" pr="" available="" to="" be="" passed="" on="" other="" same="" page?<="" p="">However, even if the test came back saying "No, these are treated differently and do not currently affect the total amount of PR available to other links on the page" I still would not use it for the purpose of pagerank sculpting. The reason is that how Google treats these links today can change tomorrow, making "tactics" like this a bad idea IMHO. It just leaves a mess for either you or some other poor SEO to cleanup later.
If I don't want pagerank to pass through a link on a page I simply don't put the link on the page. In extreme circumstances where there is no other way around it I might consider obfuscating the link with some javascript, for instance. However, even if you block the .js file that handles this "link" in the robots.txt file Google still executes it (as you can see when viewing the cached version on Google for pages that do this).</a>
Hello Henrique,
2. I mean putting /ads/ on a totally separate domain (e.g. youraffiliateprogram.com/ads/) which then redirects to yoursite.com. This way you can totally block that entire domain if you wanted to. When an affiliate links to youraffiliateprogram.com/ads/pageID the user who clicks on the link will get redirected to yoursite.com/pageID.
This set up has the advantage that you can block the entire affiliate program domain from being indexed in the robots.txt file if you wanted to, or you could try to use a 301 redirect and benefit from the links - until it stops working or you get penalized, at which point it you could block the affiliate program domain in the robots.txt, and/or change the redirects from 301 to a 302 rather quickly.
To answer your last question, yes you could simply change the redirect from a 301 to a 302 and that should solve the issue at the final landing page level, but since a lot of affiliates are still linking directly to your domain prior to getting redirected it could still cause issues. For example...
Affiliate A links to YourSite.com/ads/123 without using a rel nofollow tag in the link. This is still a link to your site from them, regardless of what happens next.
YourSite.com/ads/123 proceeds to 302 redirect the visitor to YourSite.com/123. The won't bass the pagerank on to your landing page, but it did nothing to stop the fact that you have a direct, followable affiliate link going to your site.
If you put in your Terms for affiliates that they have to use a nofollow tag in links to you, and you supply the nofollow tag in the code when they are "building" links from within your affiliate system, you should be ok. You may also want to block /ads/ in the robots.txt file just to be sure if you're going to take this route.