make field_seo_keywords optional or remove it [#925218]

what is the real purpose of field_seo_keywords ? There is something that I don't understand. I thought they will get extracted automatically from content or at least added to keywords meta tag of the page heading if we have to enter them manually or somehow related to nodewords module keywords.
If it is just a simple text field in a node type, what is they're purpose as seo?

How you check "Usage of keywords in headings" as you name them, and how you check
"Usage of keywords in node titles" or "Keyword density in the body" ? You compare what keywords with what ?

How SEO Compliance Checker defines a "keyword" ?

I have'nt played around too much with this module, but I saw that "Usage of keywords in headings" depends of having keyword in nodewords module keywords field. Am I Right ? the rest of checkings is done against this field_seo_keywords created by SEO Compliance Checker ?

Comments

Comment #1

miruoss CreditAttribution: miruoss commented 29 September 2010 at 06:47

Assigned:	Unassigned	» miruoss
Status:	Active	» Fixed

Hi Marcel

I think you got a wrong idea of this module. The SEO Checker does not define nor fill in any keywords. When you create a node you normally know what it is about and what are the keywords to it. So actually it is you defining the body AND the keywords. The SEO Compliance Checker then takes the body and checks it agains your keywords. Finally you should get a report showing you the keyword density in your content and if it is a good range.

Now the module automatically creates a CCK field field_seo_keywords. If you use nodewords, you can configure the SEO Checker on its module settings page to use the nodewords field as keywords and remove the field_seo_keywords. You won't need two keyword fields.

I set this ticket to fixed, feel free to reopen it if you have further questions.

Regards,
Michael

Comment #2

zet CreditAttribution: zet commented 29 September 2010 at 17:55

K, i understood now . This module checking nodewords keywords this is awesome. I just did that setting now.

Many thanks, miruoss!

But wouldn't it be better to just leave all the keywords handling to nodewords and this module just to check them? I mean the field_seo_keywords filed seems useless if his keywords are not used in the page meta tags (or at least auto generated from node body content - but that wold be insufficient too). The nodewords module keywords can do that ( auto generate keywords ) and they generate the page keywords meta tag too.
So I still don't get it - what is the sense of this field_seo_keywords, beside just checking a thing that was already checked. ( Someone who enters the keywords manually and in field_seo_keywords, have to look and extract them from the body content is writing, so is already checking them to exist in the body. If not, and he enters whatever he thinks, makes no sense, so it's something ambiguous) All this just to output a simple text field. Or might be the scope that is duplicating the wanted keywords in the page content , so we have +1 no of a keyword appearance? We might as well create better seo content in the node body just to doo that.
So field_seo_keywords might create confusion, like in my case.

Comment #3

miruoss CreditAttribution: miruoss commented 29 September 2010 at 18:39

You're right of course. For people using nodewords, the field_seo_keywords is useless and might even be confusing. Until now I just didn't want to depend on the nodewords module so people could still use my module without the need to install nodewords. However, I might have to think about this again. Maybe at some point I remove field_seo_keywords and just add a dependency to the nodewords module as probably most of the people using the SEO keywords checker use nodewords anyway.

Comment #4

13 October 2010 at 18:40

Status:

Fixed

» Closed (fixed)

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

Comment #5

lpalgarvio CreditAttribution: lpalgarvio commented 22 October 2010 at 00:35

Title:	real purpose of field_seo_keywords	» make field_seo_keywords optional or remove it
Version:	6.x-2.2	» 6.x-2.x-dev
Component:	Documentation	» Keyword Rules (Code)
Category:	support	» feature
Priority:	Normal	» Major
Status:	Closed (fixed)	» Active

i don't think field_seo_keywords should be created automatically.
it SHOULD be OPTIONAL imo.

also, if the module is called SEO Checker, why does it create that metatag?
if the purpose was to create tags, then it should be called SEO Creator.
and it's overlapping with int_meta and nodewords.

please make the field optional, with a button somewhere to automatically create it for those who want it.
or remove the creation of the field entirely. we already can select whichever field we want for keywords.

im my case, i'm happy with the greatly flawed Nodewords, knowing that in the future, in D7, Metatags will replace it, probably with CCK fields, and deprecating all the old modules and methods.

i will also point out a great flaw on this creation of the field.
supposing that UNINSTALL removes the field (idk if it does), and we had previously created it with some other module, we then loose data.

Comment #6

miruoss CreditAttribution: miruoss commented 13 January 2011 at 12:57

This has been improved with the last commit (next -dev release)

The CCK field is not created automatically anymore
If the Meta Tags module is present upon installation, its field is set as default for the keyword_rules module
If Meta Tags module is not present, the user has to set up the cck field manually
A requirement warning is displayed on the status page if the cck field is not set up correctly