Hello,

I've used Nodewords in the past with no problems. However, on the latest (Recommended) version I can't find a way to set the "Default robots meta tag".

Previously, at /admin/content/nodewords/ there was "Default robots meta tag:" with the default set at "ALL=INDEX,FOLLOW". However, now at /admin/content/nodewords/ there is no such option. The only related thing I see now is "Meta tag ROBOTS for lists:"

Note that the core module and "Nodewords - basic meta tags" are currently enabled. Also, at /admin/content/nodewords/ I have selected everything under "Meta tags to output in HTML".

And when I check the website's source code, there is no mention of Robots at all:

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="canonical" href="http://www.domain.com/" />
<meta name="keywords" content="words, added here, for example" />
<meta name="description" content="Description text." />
<meta name="revisit-after" content="1 day" />

I've also searched the issues here, to no avail. Any advice would be much appreciated.

Jim

CommentFileSizeAuthor
#39 nodewords-n792218-39.patch4.41 KBDamienMcKenna
#7 robots ui.png12.97 KBinvisibleink
#6 Picture 1.png27.19 KBjimmb
#5 Voila_Capture_60.png40.36 KBAnonymous (not verified)
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

apaderno’s picture

Status: Active » Fixed

The use of the default value for the meta tag ROBOTS (as well as other meta tags) can be forced only from users with the permission to administer meta tags; the settings page contains the options to select when a meta tag is replaced from the default value, and which meta tags are replaced from the default value.

jimmb’s picture

Thanks for the reply kiam!

To be clear, I have given all possible Meta Tags permissions to admin and am logged in with the user/1 account. From your reply, it sounds like the default Robots setting of "ALL=INDEX,FOLLOW" should be in effect unless someone overrides it.

If so, that is fine - I don't want to change the setting. But if that's true, I still don't understand why this:

<meta name="robots" content="index,follow" />

isn't this in the source code?

Jim

apaderno’s picture

The default values are the ones set in the settings page for the default values; with the correct settings, the module will use "index, follow" for any nodes, or user profiles without any value specificed for that meta tag, or "noindex, nofollow" if you prefer that value.

Mike Kennedy’s picture

He is right, I don't see them either. Unless I am missing some setting, Index Follow seems to be missing.

apaderno’s picture

FileSize
40.36 KB

Unless I am missing some setting, Index Follow seems to be missing.

This screenshot shows what I see. I can see the option INDEX,FOLLOW.

screenshot

jimmb’s picture

FileSize
27.19 KB

Yes, Mike is describing my situation as well.

When I go to admin/content/nodewords/meta-tags, I do not see the same thing as kiam's screenshot.

The attached screenshot shows what I see there.

Thanks,

Jim

invisibleink’s picture

FileSize
12.97 KB

Same as Jim & Mike...I don't have a drop-down box like kiam's. And can't get defaults of index,follow to set on any page. Is there a patch for the stable version, or is this corrected in the dev version?

apaderno’s picture

@jimmb: Check you don't have different version of Nodewords installed on your site; the description of form field you get seems the old one. The problem you are having is normally caused by two different copy of the modules that are trying to win over each other.

jimmb’s picture

Hi kiam,

Okay, I double-checked at /sites/all/modules, but there is only 1 directory called "nodewords" there (and at /modules there is no directory called "nodewords"). I also checked available updates, and the current version (6.x-1.11) is detected. So there doesn't appear to be 2 competing versions of Nodewords here, at least as far as I can tell.

Thanks,

Jim

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

jimmb’s picture

Status: Closed (fixed) » Active

I have to re-open this because the issue is not solved. I spent a good deal of time today looking into it, and here's what the status appears to be:

  • With the recommended version (6.x-1.11), on the "Settings" page there are no global settings for Robots. There is "Meta tag ROBOTS for lists", with "NOARCHIVE, NOFOLLOW, NOINDEX, NOODP, NOSNIPPET, NOYDIR" as the options.
  • On the "Default values" page, there is a section called "Robots". The options there are: "NOARCHIVE, NOFOLLOW, NOINDEX, NOODP, NOSNIPPET, NOYDIR".

Again, there is no option for setting a default of (for example) "INDEX" and "FOLLOW" that I can see. This would be fine (I think) if the module outputted those standard values by default unless you overrode them via the "Default values" form.

But that's not the case. For example, on the "Settings" page, under "Meta tags to output in HTML", I have checked "Description", "Keywords" and "Robots". However, only "http-equiv" and "keywords" (and "description" on the homepage) are being outputted.

I tried upgrading to "6.x-1.x-dev", but this actually made things worse overall... Yet when I did so, at least there emerged an option for setting "index,follow" on the admin settings pages.

After reverting back to the recommended version, I found a node I didn't want to be indexed. I checked "NOFOLLOW" and "NOINDEX" on the node. This, happily, did work for that node, as the source code now outputs <meta name="robots" content="nofollow, noindex" /> .

So it appears this only works if you specify something not to happen regarding Robots. I'm not sure what else to do at this point - any advice will be appreciated.

Jim

alien73’s picture

Same problem I can't seem to find index, follow there's no drop box anywhere.

alien73’s picture

@kiam

You state this on the settings:

"The meta tag ROBOTS offers a simple mechanism to indicate to web robots and crawlers whether the page should be indexed (NOINDEX) and whether links on the page should be followed (NOFOLLOW)."

Did you mean (Index) and (Follow)? because indexed is not NOINDEX.

alien73’s picture

I upgraded to the DEV version and the drop box is there along with a lot of other cool features. Not sure why 6.x-1.11 is recommend since it doesn't work properly.

jimmb’s picture

It's recommended because it works more properly than the DEV version.

At least for me, as I also tried switching to DEV (as mentioned in my last post). It ended up not working correctly, and being a lot more confusing...

This issue is for the 6.x-1.11 version, and I'm still hoping there will be an answer or fix for that version.

Jim

apaderno’s picture

Not sure why 6.x-1.11 is recommend since it doesn't work properly.

The module that handles project releases always report as recommended the latest official release that is not an alpha, beta or an unstable version, or a release candidate. It's not something project maintainers can change, nor control.

alien73’s picture

A little in your window humor... LOL

mustang’s picture

I have the same problem as described above.

Just boosting this so it doesn't die an untimely death through automated ticket closure :-)

apaderno’s picture

Open issues are not automatically closed.

jelo’s picture

Subscribed. I have exactly the same issue. I am using version 6.x-1.3-beta5.

At admin/content/nodewords/settings I cannot set a default for robots (no dropdown to specify index - follow). I activated robots both to show on edit pages and html output. If I go to edit any page and view under Meta tags - Robots, it shows me 6 check boxes for these options: NOARCHIVE, NOFOLLOW, NOINDEX, NOODP, NOSNIPPET, NOYDIR and additionally "Use the default value - The default value is currently not set."

Unfortunately, I have no way to set the default value...

Jens

webservant316’s picture

subscribe

webservant316’s picture

subscribe

Helmut Neubauer’s picture

subscribe

vincentdemers’s picture

Subscribing, I'm using beta9

nitink12’s picture

Subscribed..
I am using the current recommended version.

Dave Reid’s picture

Status: Active » Fixed

BTW the default that should be respected by all search engines even if there is no robots meta tag is always 'index,follow' so if that's the value you're wanting on your page then you do not need to even edit any meta tags. I believe this issue has also been resolved completely by the latest code.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

marty.true’s picture

I actually DO have the dropdown that is in the screenshot, however with it set to INDEX, FOLLOW - my robots meta tag on my homepage (default) is showing NOINDEX, NOFOLLOW. So even though I have the default set one way, it shows the opposite on the homepage.

Anyone else experience this?

tr-drupal’s picture

Status: Closed (fixed) » Needs review

Hi all,
I have installed:
- Nodewords 6.x-1.11 (activated)
- Nodewords - basic meta tags 6.x-1.11 (activated)
- Nodewords - extra meta tags 6.x-1.11 (activated)
- Nodewords - site verification meta tags 6.x-1.11 (not activated)

and I'm having the same problems as in the comments #9, #11 etc.

There are still no options to set / select "index,follow", i.e. no dropdown box, no checkboxes for those two options. ONly the 6 checkboxes with NO-something.

Althought it's not needed (as Dave Reid has described in his last comment), many analyzing tools consider the missing robots meta tags "bad". Since it is apparently supposed to be so, that one can set "index,follow", there is a problem then, since the options are missing.

polishyourimage’s picture

I also am missing the drop-down

tigron’s picture

subscribing. Also missing the drop down.

webservant316’s picture

Any ETA on Nodewords 6.x-1.12? Tried to install the development version and got a number of WSOD on the admin pages.

raven_web’s picture

I am using 6.x-1.x-dev. I have the drop down menu in the nodewords admin section.

wb54321’s picture

Subscribing. Nodewords 6.x-1.11. Also missing the drop down.

kollo-dherbois’s picture

I`m also missing the drop down... oh, or it`s not have to be there at all. Please release stable version at last!

kollo-dherbois’s picture

Status: Needs review » Active

Dave Reid: "BTW the default that should be respected by all search engines even if there is no robots meta tag is always 'index,follow' so if that's the value you're wanting on your page then you do not need to even edit any meta tags."

So not having "index/follow" on setting page is intended for this release, yes? Then users should`ve been warned about this behaviour... It should be posted somewhere on project`s page and/or in readme (we talking about "recommended" release anyway). Something like this:
"You can set meta robots not to follow and index. But you CANNOT set robots "index,follow" - there`s no use of this option and Nodewords module WILL NOT output meta robots "index,follow" anyway. It will output only "noindex,nofollow" if you choose this option".

Instead people see this:

"The meta tag ROBOTS offers a simple mechanism to indicate to web robots and crawlers whether the page should be indexed (NOINDEX) and whether links on the page should be followed (NOFOLLOW)"

and... search for holy graal of missing drop down. kiam posting http://drupal.org/node/792218#comment-2945556 having it, and some not...

p.s. I set it to active. It`s not only "interface" problem in my opinion. People get confused, loosing their time, making wrong movements, get problems with site indexing etc... It`s not so hard to put one or two single sentence on project`s information page. Why not tell to users they`re wont be able to print simple meta robots=""index,follow" - it`s no fun for Drupal CMS but it`s true.

hagit’s picture

subscribe

stuchl4n3k’s picture

subscribe

DamienMcKenna’s picture

Version: 6.x-1.11 » 6.x-1.x-dev
Status: Active » Needs review
FileSize
4.41 KB

How's about something like this, which adds two new options (FOLLOW, INDEX) and adds the following note to the forms:

Search engines will automatically assume "INDEX" and "FOLLOW" unless these are specifically disabled above; these two options are available for completeness sake but can be ignored.

I also caught a bug in how it was identifying whether to use the default tags or not, due to the poorly implemented "Use defaults" option that is *only* available for the Robots tags and nothing else (ultimately, either the "Use defaults" option will be removed or all tags will be given this option).

DamienMcKenna’s picture

Status: Needs review » Fixed

After some testing I've committed this patch to the 6.x-1.x branch.

DamienMcKenna’s picture

I created a follow-up issue to remove the "Use defaults" option: #1271812: Remove "use defaults" ROBOTS option for custom pages

DamienMcKenna’s picture

Issue tags: +v6.x-1.12 blocker

This should have been tagged.

Status: Fixed » Closed (fixed)
Issue tags: -v6.x-1.12 blocker

Automatically closed -- issue fixed for 2 weeks with no activity.