Hi,

I have started using Nodewords and, so far, everything goes rather smoothly (though there's a UI little nuisance I'll comment later in another separate issue).

However, I'd like to ask for a feature:

I use a vocabulary to grant/hinder access to nodes (term: edited/term: not edited) depending on the role (administrator: access to 'edited' / others: not accessing to 'edited'). I'd like to assign automatically meta tags like "robots -> No Index / No follow" to all the nodes marked with the 'not edited' term.

So, I am asking the feature of adding metatags on the basis not only of vocabulary but of individual term.

Asking perhaps too much, I know, but thanks in advance.

Gustavo, from Madrid

Comments

avpaderno’s picture

Title: Assign Meta tags (robots -> noindex, to be precise) to a Term in a Vocabulary in taxonomy » Use the taxonomy term meta tags for the nodes using that taxonomy term
Version: 6.x-1.12-beta2 » 6.x-1.x-dev
Status: Active » Postponed (maintainer needs more info)

Nodewords already makes possible to assign meta tags to taxonomy terms, and it uses them.
What you are asking is to use the meta tags assigned to a taxonomy term for all the nodes using that taxonomy term.

What you are asking is possible, but there are also some points that need to be cleared.

  • A node can have more taxonomy terms, and the code can just apply a set of meta tags; the code would use the meta tags of the first taxonomy term it finds (which is the one with lower weight, or the one that is associated with the vocabulary with lower weight).
  • The module should have a way to let the admin user decide which node meta tags should be overridden from the taxonomy term meta tags.
  • The taxonomy meta tags could be used in all the cases, when the node meta tags are empty. For some meta tags it could be possible to use both the meta tag sets, or just one of the sets. This would mean that if the meta tag ROBOTS content is NOARCHIVE, NOODP for the node, and NOINDEX for the taxonomy term, then the content used for the node would be NOARCHIVE, NOINDEX, NOODP.

Anonymous’s picture

I understand what you are saying...

Let's put it from another (absolutelly different) point of view: Would it be possible to assign meta tags to nodes/pages depending on who can access to them?

I mean: a general option so that "All pages marked as no accesible to anonymous users (and that, I guess, always includes search bots) by any mean (ie: any module, Drupal Core... whatever) -> Assigned meta tags no index / no follow?"

Maybe easier / simpler?

As soon as they become accesible to anonymous, they lose those meta tags (ie: "not accesible set") .

G.

In the end the point is that, for example, any page resulting in a 403 error should not be indexed (but they are indexed, as they cannot be marked themselves as 'no indexed', or so Google webmaster tools say.

avpaderno’s picture

Status: Postponed (maintainer needs more info) » Active

Considering that most meta tags are used from the search engines, making a difference between meta tags for anonymous users and other roles doesn't make sense.
Meta tags such as canonical URL, description, robots, and site verification tags are not used from the browser but the search engines, which are identified as anonymous users from Drupal. If a search engine cannot access the content, then you don't need to use Nodewords.

What I reported in the previous comment didn't mean the feature is not implementable; it was meant to point out how the feature would be implemented.

I think the feature can be implemented, and it would be a complement for the option that allow to populate the meta tag KEYWORDS using the taxonomy term names associated with a node.

Anonymous’s picture

I see. As you say, it would be useful then the "metatag by term" approach (for other uses).

Thanks a lot for your atention and remarks anyway.

G.

Anonymous’s picture

Status: Active » Closed (works as designed)

The module can just use a list of meta tag values for each object. Using the meta tags assigned to each taxonomy term associated with a node would just complicate the code; it's not clear what the code should do with multiple values for the same meta tag, when the meta tag can just accept a value (see a meta tag containing a date, in example).

quazardous’s picture

I needed taxonomy metatags inheritance :

http://drupal.org/project/metaxo