MozBar > General Attributes > Meta Robots > noindex
-
I'm having a hard time figuring out where the noindex value for Meta Robots is coming from so I can fix it. Can anybody spot the issue or point me to some docs that show were the MozBar finds this information http://www.produnkhoops.com
-
I can't actually see anything myself Ryan - is this being found on the homepage? Or can you tell me what page this is seen on? The only ones I can see are:
http://www.produnkhoops.com/photos/albums/sean-56x65-hercules-diamond-basketball-system-137/
http://produnkhoops.com/photos/albums/sean-56x65-hercules-diamond-basketball-system-137/
If it isn't those, could it be something in your .htaccess file?
-Andy
-
Yes, these pages...
Home Page: http://www.produnkhoops.com
Other Pages
http://www.produnkhoops.com/basketball_goals/adjustable_in_ground/
http://www.produnkhoops.com/basketball_goals/adjustable_in_ground/pro_dunk_diamond.php
http://www.produnkhoops.com/basketball_goals/adjustable_in_ground/pro_dunk_platinum.php
http://www.produnkhoops.com/basketball_goals/adjustable_in_ground/pro_dunk_gold.php
http://www.produnkhoops.com/basketball_goals/adjustable_in_ground/pro_dunk_silver.phpScreen shot attached.
I'd ignore this but Google seems to see the same thing. You'll see a query using the site operator does not return any of these pages.
.htaccess looks okay to me but take a look for yourself...
RewriteEngine on
RewriteBase /Allows for php caching of images
RewriteRule ^cache_image/([^/.]+).gif?$ img.php?img=$1 [L]
#TEMP Get crawlers to the correct new parts page - Remove in Fall 2015
RewriteRule ^basketball_goals/parts/index.php(.?)$ http://www.produnkhoops.com/parts/ [R=301,L]
RewriteRule ^basketball_goals/parts(.?)$ http://www.produnkhoops.com/parts/ [R=301,L]
RewriteRule ^basketball_goals/parts/pole_padding.php(.?)$ http://www.produnkhoops.com/parts/ [R=301,L]
RewriteRule ^basketball_goals/parts/backboard.php(.?)$ http://www.produnkhoops.com/parts/ [R=301,L]
RewriteRule ^basketball_goals/parts/backboard_padding.php(.?)$ http://www.produnkhoops.com/parts/ [R=301,L]
RewriteRule ^basketball_goals/parts/pier_kit.php(.?)$ http://www.produnkhoops.com/parts/ [R=301,L]
RewriteRule ^basketball_goals/parts/rim.php(.?)$ http://www.produnkhoops.com/parts/ [R=301,L]Retain Link Juice
RewriteRule ^giveaway(.?)$ http://www.produnkhoops.com [R=301,L]
Force www version of site
RewriteCond %{HTTP_HOST} !^www.
RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L] -
If you check the page using (for example) Chrome's Developer Tools, you can clearly see that the rendered page includes no-index directives in each photo album
. (screenshot below)
Google is clear that it will honour no-index directives it finds anywhere in the page, not just in the .
You need to figure how and why those meta-robots noindex tags are getting added by your gallery implementation and get them removed asap.
Hope that helps?
Paul
P.S. You have to use something like Developer Tools, rather than just View Source to inspect the page. That way you're inspecting the DOM (the actual rendered page) rather than just the source code.
-
You sir are a genius. Thank you very much.
Also mad props to the MozBar for picking up on this.
Some observations...
-
We've had these noindex tags on there for almost a year and just now Google found them or decided to honor them.
-
We had a recent situation where Google was basically probing our website with fake URLs to see if anything turned up. Source? incorrectly parsed URLs from JavaScript on houzz.com. I think they are making some big changes on how they crawl JavaScript recently.
-
One of these "problem" pages has some links pointing at it with a query string. Nothing changes on the site because of these. Google indexed the page with a query string despite the noindex. Weird. I guess Google does not always honor the noindex directive.
-
One of these "problem" pages would come up when looking up the cached version in Google but could not be found in the index. Odd again.
Lesson to me is don't count on the meta robots tag for two reasons ...
-
Google inconsistently implements it
-
It's dangerous as a little bad code can take your whole site out of the index.
-