Hi,
There's a bug that makes the tag noindex to show up in the front page. My site lost the homepage from the Google index and I had no idea how that happened. I thought it’s some Google penalty but it was that tag only showing up in .
This is a critical bug and to make this worse the new functionality “Remove ads from remote search engines” is on by default.
Thanks,
introfini
Comments
Comment #1
jeremy commentedIf you are displaying ad nodes on your front page, then you will get the noindex meta tag there. I doubt that this is a typical configuration -- but as you have noticed if you have configured your website this way you will want to disable "Remove ads from remote search engines".
Documentation updated to better explain this.
Comment #2
introfini commented"The 'noindex' tag is not added when ads are displayed via blocks, direct calls to ad(), using views, or when embedded with the ad_embed module."
There's something wrong because the ads are beeing dispayed via blocks.
Thanks,
introfini
Comment #3
jeremy commentedI am unable to duplicate. What ad modules are you using? Do you have a custom front page type, or the default node listing front page? What may be nonstandard about your configuration?
Comment #4
introfini commentedYes, I have a custom homepage but the ads are being displayed via blocks in theme regions.
Comment #5
jeremy commentedWhat are you using for your custom homepage? Evidently this is confusingthe noindex logic into thinking you are displaying ad nodes on your front page.
Comment #6
introfini commentedHi Jeremy,
I'll try to do the debugging myself and then I will let you know what I find out.
Thanks.
Comment #7
3dloco commentedHello,
I was lucky to finally come across this post as I have painfully lost ranking and indexing due to this issue of a noindex meta appearing on pages.
I am currently using 6.x-2.1 with 6.13, I have one ad a block that displays on several pages including the home page. My front page is a custom frontpage (just a node page).
Unchecking the "remove ads from remote search engines" fixed the noindex meta on all a bunch of pages including homepage, blog, blog posting, ubercart product view, etc.
I raised its priority to critical since really all efforts are fruitless if one has a NOINDEX tag one can't control or did not know about like that...hmm SEO folks were pulling their hair out!
Meanwhile, I think it would be most helpful to have the default "remove ads from remote search engines" unchecked with an explanation that will allow us to know/check this behaviour and verify if the noindex tag is appearing on every page there is an AD (teaser/block) vs on the AD node itself.
Thanks,
KH
Comment #8
jeremy commentedHow are you building your custom homepage? Displaying ads in the default block should not cause the NOINDEX meta tag to display -- in both cases where this has been reported as an issue a custom homepage has been used.
I have gone ahead and disabled this option by default:
http://drupal.org/cvs?commit=292800
Comment #9
3dloco commentedHi,
There is nothing special about this page. The AD is on a block which is displayed on the right sidebar. At the bottom of the page I am pulling the teasers from a couple of nodes (the nodes don't have a NOINDEX metatag, since I want them to be indexed).
Below find the steps that reproduced this NOINDEX tag on the front page and all other pages that have the ad in a block.
1) Create a page (with default node type page).
2) Add the path of the page to Settings->Site Information-> Default Front Page.
3) Add frontpage metatags using the Nodewords module. Note that the nodewords module has an area to specify the robots metatags. Here, I leave the NOINDEX tag unchecked (since I want the homepage to be indexed).
4) Create the AD (image ad, with premiere status).
5) Add the AD a block using Nodes in Block module.
6) Edit the block page visibility to show the block on specific pages. In my case this list includes the frontpage.
Let me know if you need additional info.
Thanks,
KH
Comment #10
jeremy commented> 5) Add the AD a block using Nodes in Block module.
This is the source of your problem. If you are displaying ads this way, then as far as the ad module is concerned the ad node is being displayed: it is, it's just being displayed in a block. Why are you displaying the ads with the Nodes As Block module? Why are you not using the default blocks provided by the ad module, or at minimum by calling the ad() function in a custom block as described in the documentation? The way you are displaying ads not only causes this noindex tag to be added to all pages where your ad blocks are displayed, it also means that the ad module no longer can count how many ad impressions there are.
Comment #11
introfini commentedHi Jeremy,
I'm sorry but I havent had the time to look at this :-( But in my case I wasn't using Nodes As Block module.
Here is the code for page-front.tpl.php that I was using. the ad was displayed as a block in the $homepage_right region.
Hope it helps...
Comment #12
3dloco commentedJeremy,
Thanks for your response and explanation...this could be very well the cause of this I will test in a couple of days and advise.
I am using Nodes in Block as it allows non-admin users to choose whether a node should display in existing blocks when they are creating/editing content.
Thanks,
KH
Comment #13
3dloco commentedJeremy
I was able to confirm that placing Ads in a block provided by the Nodes in Block was the source of the NOINDEX metatag showing up on all pages that contained this block.
Here is what I did to confirm this.
1) Removed the Ads from the block provided by Nodes in Block.
2) Enabled the block provided by Ad module.
3) Checked the "remove ads from remote search engines" Ad->Settings
4) Noindex metatag is gone and no longer appears on the pages were this block appears.
Would this be more of a Nodes in Block issue then?
Thanks
KH
Comment #14
jeremy commented@3dloco: There is no bug. If an ad node is displayed on a page, then a meta tag is added telling search engines to not index the page. In your case, you're putting an ad node on many pages using blocks -- so the ad logic is working as designed.
Comment #15
dave reidRemoving tag.
Comment #16
lrwebks commentedDrupal 6 is EOL and no longer supported. Closing this as outdated for that reason. Thanks for your contribution!