There's a lot of overlap with the Integrated Metatags module, merge it in.


DamienMcKenna’s picture

The best approach might be to review the feature differences between the two modules and add separate tickets for each feature missing from Nodewords.

lpalgarvio’s picture

Integrated Metatags functionalities:

  • Global and per Node Type tags
  • Optional Global tags inheritance per Node Type
  • Support for custom tags
  • Support for multiple tags with same name
  • Support for static tags
  • Support for dynamic tags
  • (aggregates data from all the tags added with the same name)

  • Integration with Tokens
  • (on Global/Node Type; any tokens)

  • Integration with CCK
  • (on Node Type only; can fetch values from field_****.data, field_****.fid, field_****.list)

  • Integration with Node
  • (on Global/Node Type; can fetch values from node.changed, node.comment, node.created, node.nid, node.promote, node.status, node.sticky, node.teaser, node.title, node.type, node.uid, node.vid)

  • Integration with Taxonomy
  • (on Global/Node Type; can fetch values from term.*.name, term.*.tid, term.*.vid, term.*.vocab)

  • Integration with User
  • (on Global/Node Type; can fetch values from user.mail,, user.signature, user.uid)

  • Optional tags in Teasers

It does not however allow creating tags per NODE.

from the project page:

Posted by fractile81 on March 1, 2008

Integrated Metatags allows you to expose content data in META-tags on full-page node views, with Metatag options stored per content type. Node, taxonomy, and user information are all available out of the box, with an optional CCK module that exposes CCK data. Additionally, if the Token module is enabled you can use tokens in your Metatags. Using all of these different sources for data, you can name your Metatags however you would like, and can even combine like-named Metatags into a single comma-separated tag.

NOTE: only the "keywords" and "description" Metatags will have any benefit with today's search engines. This module can be used to dynamically generate these Metatags. Other Metatags will NOT improve your site's Search Engine Optimization (or SEO) with most search engines. However, if you control your own crawler this extra data could be used for things like a faceted search.


* Expose data from multiple sources - Data from the node object, including taxonomy and user information, can be exposed in a Metatag. Name your tags however you would like, and optionally combine like-named tags into a single comma-separated tag. Metatags are displayed on full-page views of a node.
* CCK Support - A module for exposing CCK field data is also included with this module.
* Set Metatags for each content type - Metatags are configured for each content type. A special set of inheritable Metatags can also be set, allowing content types to share the same Metatags.
* Extendible - The Integrated Metatags module can be extended in two ways:
1. Adding Metatag data directly to the node object.
2. A hook to both define exposable data and to provide that data when needed.
* Basic support for the Token module - When defining static Metatags, you can enable the Token module and utilize the power of that module as well.
* DRUPAL 6 ONLY: Show Metatags with teasers - In Drupal 6, you can optionally have Metatags displayed whenever nodes are rendered as a teaser.

What's the difference between this module and the Nodewords/Meta tags module? Have a look at this forum topic, including all comments, for a functional comparison of this module with the Nodewords/Meta tags module.

further comparison of both modules here -

lpalgarvio’s picture

IMO, i don't think this should be taken in consideration for Nodewords.

The reason is that D7 is closing in, and with so much work going to be needed for this, possibly close to a rewrite, i think it's wiser that Metatags module for D7 should instead take this into account.

unless ofc the maintainer of Nodewords has lots of free time.

DamienMcKenna’s picture

Status: Active » Postponed

@LPCA: thanks again for your help.

One of the missing pieces is already listed as a separate issue (#945676: Allow defaults to be defined per content type), so I'm not sure how much functionality from int_meta is valid. Going to postpone this to deal with later.

lpalgarvio’s picture

i've written additional information in a Metatags (D7) issue located here:

Dave Reid’s picture

I highly recommend we just merge in the default per content type variables feature, and everything else should be put back into metatags.module. If Damien agrees, we can just close this issue since 945676 and 948102 have been created.

DamienMcKenna’s picture

Out of interest, does int_meta do anything with CCK that Nodewords' Token support doesn't cover?

lpalgarvio’s picture

i think they don't cover exactly the same CCK information

Tokens at Nodewords default metatags is listing these for Page content type at my test site:

CCK file tokens
[field_image-filefield-fid]	ID do ficheiro
[field_image-filefield-description]	Descrição do ficheiro
[field_image-filefield-filename]	Nome do ficheiro
[field_image-filefield-filepath]	Caminho do ficheiro
[field_image-filefield-filemime]	File MIME type
[field_image-filefield-filesize]	Tamanho do ficheiro (em bytes)
[field_image-filefield-filesize_formatted]	File size (pretty printed)
[field_image-filefield-view]	Fully formatted HTML file tag
[field_image-filefield-onlyname]	Nome do ficheiro sem extensão
[field_image-filefield-extension]	Extensão do ficheiro

Integrated Metatags exposed these CCK:

these are all relevant to ImageFields.
i haven't had the need to toy around with CCK, for example, with a Text Field.

Dave Reid’s picture

Status: Postponed » Closed (duplicate)

Now that we have #945676: Allow defaults to be defined per content type filed there's no reason to keep this open. If file fields are missing tokens, then that should be filed against filefield.module, not nodewords.