Scattered thoughts...

If you've done any search engine optimization work you know about keywords. Keywords don't do much directly for users, but are included as meta data to help search engines understand what the designer/developer/content producer thought was important about the page being indexed. Anyone who works in SEO will tell you that relevant content is king. Keep your content relevant, link to relevant sources and provide relevant meta data. What do I mean by relevant meta data? I mean 3 meta tags that should be included on all pages: title, description and keywords. These 3 components can provide a lot of information about each individual page to the search engine spiders.

One of the things I noticed after installing BlogCFC and setting up this site was that I could set and update keywords for the entire site. Knowing the importance of those keywords, I thought this was great and during setup gave a few generic keywords to be used. But then I realized an issue: my blog is not about 1 specific topic so 1 set of keywords could actually prove to be a negative!

If you have delved into Google's webmaster tools you may have seen reports that show pages that have duplicate keyword content. Google, and I dare to guess Bing, Yahoo and Blekko. apparently don't like it when every page on your site has the same keywords. And that stands to reason; is EVERY page about the EXACT same thing? Probably not. So, I set about rectifying this issue in my BlogCFC installation. Several hours after I did it, when I couldn't get to sleep, I decided to write-up how I did it. This is my first attempt at writing about my coding adventures. I hope I didn't forget anything. I'm going to break this into 2 parts. This part will cover the admin side and part 2 will cover the implementation on the client side.

First things first, I needed a place to store my new keywords, so I went to the database (SQL Server 2005 in my case) and in the tblblogentries table, added a nullable, nvarchar(200) field named pageKeywords. It is important to make it nullable because no previous entries will have a value for this field.

Data storage out of the way, I had to populate it! this is my first foray into the BlogCFC code, so I had to do a little looking around. IN short order I discovered that I would need to amend 2 functions in org.camden.blog.cfc and then update admin/entry.cfm to ask for the data and pass it along to the functions.

Update addEntry function The first function I updated was addEntry. I'm not going to paste the whole function as the modifications were minor and should be easy to do should you choose. I'm passing in some new data, so I added a new parameter

I also created a var-scoped local variable. I know CF9 offers the local scope, but I'm running CF8.

Because I'm going to add a text field to the form, argument.pageKeywords should always be defined. I went ahead and assigned the local variable final_pageKeywords the default, site-wide values. this way, if I decide not to specify distinct keywords, the data will still be populated. This has the benefit of presenting the list to me later should I choose to edit the entry, but let's not get ahead of ourselves.

Then I added the following snippet:

At this point, I considered appending or prepending my desired keywords into the preassigned final_pagekeywords to make a more robust list. I decided against it as I want to make sure my keywords are relevant to this page.

Finally, I updated the insert query to the following, which just added the pageKeyword field and final_pagekeyWords value:

Updating saveEntry function While in blog.cfc, I made similar updates to the saveEntry function. I'll only post the line I added to the update sql statement to save time. I copied/pasted the code from addEntry to add the arguments.pageKeywords parameter, the var-scoped final_pageKeywords and the if-statement to determine the value for frinal_pageKeywords.

Add the line below to end of the update statement, just like any other value (don't forget the comma at the beginning of the line).

Update admin/entry.cfm Entry.cfm does some processing at the top to allow for displaying values that have already been entered. So, I needed to define a new variable for the page to hold my keywords when the page loads pre-populated with data. Actually I had to do it twice because variables are defined based on whether or not the entry has already been saved or not. For simplicity here is the entire if-else statement that includes my additions.

I named the variable form.pageKeywords and if the field has already been populated, I set it to #entry.pageKeywords#, otherwise it is set to blank.

When the form is submitted, I need to tell it to pass this new value to our functions addEntry (for first time saving) and saveEntry (after making changes). A quick search of entry.cfm for 'addEntry' finds the following line and you will see that I have just added our value pageKeywords to the end of the parameters list, recalling that this parameter has already been defined in blog.cfc.

Another quick search for 'saveEntry' yields the following line just above the addEntry code similarly updated.

Now I just needed to actually update the form to get the information for our functions. In entry.cfm, search for this comment:

That will put you right at the top of the "Additional Settings" tab. I then copied and pasted one of the existing divs into the outer div like so:

These simple changes will now save and update new page independent keywords for your entries. In part 2, I will describe the much simpler code I used to actually display the new keywords n my pages while maintaining the site-wide keyword list for non-entry pages.

This entry was posted on December 21, 2011 at 3:32 AM and has received 4326 views. There are currently 2 comments. Print this entry.