Maybe it would be a improvement to add a configuration section to set global keywords which should be added to every site (of a content type?).

Comments

valthebald’s picture

I really feel that nodewords nostalgie in your words :)
Seriously now, similar effect can be achieved by setting default field values - which is per-instance setting.
This will allow to set default meta values for each content type, taxonomy and users - one separate from another.

valthebald’s picture

However, the problem can arise when you decide to change default values. What should happen with existing data?

JohnnyX’s picture

Ok, set default values is a quick way to do it, but a configuration page would be a nicer way ;) Was only an idea to improve this module a litte bit.

I think I'll repeat the keywords and not use default values at the moment... But thank you for the suggestion!

I used nodewords only to set keywords and descriptions and also global keywords before ;)

valthebald’s picture

I try to be very careful about adding new features, at least until I have clear answer from Dave Reid, nodewords/metatags maintainer, about my suggestion to join efforts.
Without joining efforts, long delay in metatags development brings fragmentation problem, and this is the worst thing I can think about. What had started as my personal workaround for missing meta tags in D7, has passed milestone of 500 installations. And, if metatags_quick user base will continue to grow at the same rate - and, actually, I don't see any reason it won't, - very soon it will become hard question for newcomer what module to choose.

JohnnyX’s picture

Problem is the slow development with metatags (I know it's a lot of really hard work!!!). I think a statement from Dave Reid is needed soon. If metatags_quick and metatags could merged and get a user friendly module it would be great.

I think the best way should be to merge the projects and release a first and simple basically working module (like metatags_quick for keywords and description) and than add the planned features (token support,...) to following releases...

chrisschaub’s picture

I want to chime in about this module vs nodewords. This module is the perfect solution. Ask any seo expert and they will tell you that they do not want a module "doing things" in a way that is hard to control. You really need control over keywords and descriptions, that's it. The rest of the meta tags are mostly useless for seo -- but your module allows total flexibility to create any type which is awesome. Global keywords and descriptions are useless for seo and could be very, very bad. Empty keywords are not an issue, but empty description tags can be.

I think the only features I would add to this would be:

1. A button on a config page to add a standard keywords & description tags to selected content types. Sort of an auto populate for the cctypes with a basic set of tags.
2. Have an option to populate the description field from the body text if nothing is specified. This could be a per content type setting.

Other than those two, this is the best approach for seo. We've had so many problems with nodewords, I'd say let it be.

valthebald’s picture

Version: 7.x-1.2 » 7.x-1.x-dev
Assigned: Unassigned » valthebald
valthebald’s picture

Status: Active » Fixed

I have added global settings screen at admin/structure/metatags_quick
Only configurable thing so far is front page meta tags, since default front page (/node) is not fieldable.

raffij’s picture

Hi, I am not able to use the admin/structure/metatags_quick page. i'm running the latest dev release...never mind..its there...

valthebald’s picture

So it's all right now?

Status: Fixed » Closed (fixed)

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

CodeBru’s picture

I can not access admin/structure/metatags_quick. I have tried updating to the development version and the latest 1.7 version. Do you have any ideas why I can not get to this screen? I need to add a meta description to the front page.

valthebald’s picture

Please post that in another issue, this is not related to the topic.
If you are not user #1, check that you have 'administer content types' permission