Mtekk’s Testimonials 1.0.0

After over a year sitting idle, Mtekk’s Testimonials is now available for public consumption. This initial public release brings a ton of fixes to the old testimonials plug-in originally written for the Weblogs.us front page (more on that later). Mtekk’s Testimonials is a modern WordPress plug-in, which requires WordPress 2.5 to function. Naturally, it has full i18n support (POT file coming soon). It sports Short Code tags for displaying testimonials on any WordPress post or page. When located on a front page, AJAX support is available (this limitation is changing in 1.1), which automatically changes to the next testimonial in 10 seconds (can be disabled by modifying the testimonials.js file).

User submission of testimonials is possible, and can be disabled. These submissions are never automatically approved for showing up in the testimonial stream. Along with this, the domain and TLD can be restricted for user testimonial submissions as a anti-spam measure (to be honest right now it is compulsory, this is changing in 1.1).

You can see it in action at beta.weblogs.us and download it from it’s project page.

Next up on the update block is Iframe-B-Gone. Iframe-B-Gone is getting a full overhaul for it’s 1.1 release, the ETA for right now is by mid June. Then Breadcrumb NavXT’s June bugfix release, this will include some i18n related fixes as well as better handling of some “unique” category structures. WP Trainer is on hold until MooTools 1.2 is released.

-John Havlik

[end of transmission, stay tuned]

Tagged:
Updated:

SEO Misconceptions

Search Engine Optimization, a rather popular, yet misunderstood topic. SEO promises increased page views by appearing as close to the top of a search results page as possible. Naturally, this requires optimizing towards specific keywords related to the content of the site being optimized. There are many common sense things that can be done to increase pagerank, but there is a ton of bad advice going around. After reading several articles on SEO which offered poor advice one can advise against some poor choices.

Multiple (identical) links to the same content are not bad. People tend to confuse, multiple pages containing the same content, and multiple links (on separate pages) to a single page that contains content. Cross linking is beneficial, not only for SEO but also usability. In WordPress (since 2.3), there are three methods of organizing posts, archive by date, category or tag. In most cases using only one of these for organizing data is not wise. Tags and categories and work together, as visible on this blog.

Contrary to popular belief, WordPress only generates one permalink to a particular post. Sure all the different ways to get to a post still work if manually entered. The links WordPress generates, however, result in only one location for a page, independent of taxonomy (it is all in the permalink structure). Need proof? Look at the link to this post. Visit the archives of the tags this post belongs to. Then visit the archives for the category this post is in. Lastly visit the by date archives for the day, month, or year this post was published. Notice how all the links are the same? This is by design, WordPress does this naturally, and it does not adversely affect pagerank.

Do not use nofollows. Simply put, the nofollow attribute produces a contradiction of intent. What is the point of creating an hyperlink if the user (be it human or robot) is not supposed to follow it? Sure, they do have a use for linking to outgoing content in things like user comment. However, in sections where the content is fully controlled (e.g., blog posts) why instruct the user not to follow the provided links. Under no circumstances should an internal link contain the nofollow attribute. If internal content is not trustable, then there are greater problems to worry about than pagerank.

Never substitute usability with SEO. A user may find a your site faster, but if they can not navigate the site they will not stay long. Someone suggested that a usability enhancer (breadcrumbs) should only be used on pages (not categories) as a SEO tip. Sadly, this is completely wrong and is detrimental to usability. Breadcrumbs should be placed in the same location on every page of a site if implemented. The single exception is for the front page, but thats an entirely different story.

-John Havlik

[end of transmission, stay tuned]

Tagged:
Updated:

Breadcrumb NavXT 2.1.2

The second maintenance release for the 2.1 series, and this month’s release brings some useful bug fixes. Static front page support has been improved (serious testing of it’s functionality took place in the past month.). This includes automagical detection of static front pages, which will do all the heavy lifting for you. Paged items now work as they did in 2.0. Do note that paged item support is not complete (that’s getting thrown into the July 2.2.0 release). Additionally, the behavior of the link current item option has changed, now instead of trying to actually generate a link the href is left blank. This seems to be the best way to link to the current page, as it is the simplest method for implementation and is guarenteed to work 100% of the time. Of course, that may change again in the future.

-John Havlik

[end of transmission, stay tuned]

New Database Server

So this past weekend the new database server was installed (physically) at the data center. On Monday JD installed Gentoo, and then I setup mySQL on it (plus some security things). Last night JD transfered over this blog and another over to the new database server for initial performance testing. Later this week and month, additional blogs hosted by Weblogs.us will be transfered over and performance tweaks will be applied. Hopefully, by June everyone will be on the new database server. At that point, signups for more blogs may be possible. It also looks like we may be reintroducing the Weblogs.us front page that I designed a while back.

Right now, the speed increase is apparent on this blog, especially when working in the WordPress dashboard. All those AJAX elements instantaneously load now. Additionally, Spam Karma 2’s administrative section loads much faster than before. There should not be any more of those failed comment submissions due to timeouts now, which is an all around plus.

-John Havlik

[end of transmission, stay tuned]