Wordpress

SEO At Word Camp

Word Camp is over with for 2007 but during the conference, one of the talking points of discussion revolved around SEO. Some of the tips that were highlighted during this meeting include:

Don’t put blog at root of domain

  • What if you want something besides a blog?
  • People link to a main pageand a main blog page so you get extra links

Name Directory Blog (not wordpress)

  • Case you change
  • If you upgrade.

SEO Tips

various keyword tools: AdWords, Overture/Yahoo

Use a variant of the word in post slug verses title.

use categories that are good keywords

  • dashes are best
  • next best is underscores
  • no spaces are worst
  1. Keep it simple, and search engines will like it.
  2. Don’t change your site, its not worth the hassle.
  3. Use alt tags on your images, 3-4 relevant words
  4. Don’t forget image search and video search.
  5. Full sentence verses a few words? the scoring algorithms don’t mind unless it actually notices the spam.
  6. Question marks or Hashmarks? They get truncated.

Check out all of the other great tips that were covered at the conference by visiting the WordCamp Info Blog.

The WordCamp Report

The WordCamp Report

If you are a WordPress user, you are definitely going to want to bookmark this site. The WordCamp Report is specifically reporting on everything going on at WordCamp. I can’t attend because I live in Ohio but the WordCamp Report blog should keep me informed as if I were there. Special thanks to the blogs authors, Patrick Havens and Charles Stricklin for keeping those who couldn’t attend up to date.

Digg Like Comment Editor For WordPress

http://www.raproject.com/wordpress/wp-ajax-edit-comments/How many times have you published a comment, realizing just a few seconds later that you misspelled something, or your URL was incorrect. Usually, you would have to create another comment which would dismiss the previous comment.

Ronald Huereca of the Reader Appreciation Project has released a WordPress plugin which gives administrators and regular users the ability to edit their own comments within a given time frame. The plugin pretty much works in the same way that the Digg commenting system works.

The plugin uses Ajax so the entire page never needs to reload. Once a comment is published, a timer starts to count down the remaining time available to edit the comment. Once the timer reaches zero, only the administrator can edit the comment. Users can also edit their email address, or their URL by clicking on the text that needs to be edited. This will open the comment editor window allowing you to make the necessary changes.

Plugin Features

  • Utilizes the jQuery library.
  • Comment editing times out after 15 seconds.
  • Better error handling.
  • Graceful deletion for compatible themes.
  • A hook for other plugin authors to tap into.
  • Compatible with many plugins, including Akismet, WP Cache, Better Comments Manager, WP Grins, TinyMCEComments, and many more.

I have installed this plugin on this blog so now you’ll be able to edit your own comments. We need every WordPress blogger to install this plugin, or something similar so that users can edit their comments. Why this functionality is missing from WordPress by default is beyond me, but the solution provided above works out very nicely. Please visit The Reader Appreciation Project and grab your copy today and install it as soon as possible so people can edit their own comments.

Special thanks to the guys who host the WordPress Podcast for tipping me off on this plugin.

WordPress Releases 2.2.1

WordPress 2.2.1 is now available. 2.2.1 is a bug fix release for the 2.2 series. Since 2.2 was released a month ago, the WordPress community has been improving fit-and-finish by identifying and fixing those little bugs that can be so annoying and by fine-tuning some small details. The result is a nicely polished 2.2.1 release. The full list of bugs fixed in 2.2.1 is available here. Here are some highlights.

Unfortunately, 2.2.1 is not just a bug fix release. Some security issues came to light during 2.2.1 development, making 2.2.1 a required upgrade. 2.2.1 addresses the following vulnerabilities:

Jeffro2pt0.com has successfully been upgraded to version 2.2.1