New Features

• Same Guiding Philosophy
• YAML Ready
• Multlingual Ready
• Internationalization
• Improved Dynamic Menus
• Pre-Coded Forms
• Edit This Entry Link
• Improved Search Results Page
• New Template Structure
• Better SEO
• Enhanced Breadcrumbs & Page Titles
  • Sub Category Friendly

 

Site Search

Enter Keywords

[ category page template ]

Better Search Engine Optimization

Introducing smart segment checking for URI segments 1, 2 and 3.

ExpressionEngine has a 404 (Page not Found) system that checks for bad info against segment 1 of its URI’s, but its default URI method has difficulty checking for bad inbound requests beyond segment 1.

eeSiteKit 2.0 accurately evaluates the contents of segments 1, 2 and 3 of inbound URIs. Any invalid requests are directed to a 404 page with correct headers.

This helps prevent search-bots from indexing nonexistent pages on your site. You can test it out by removing any part of segments 1, 2 or three in the URIs of this site to see smart URI checking in action.

Also, 2.0 has improved permalinks for single entries. The URI structure for 2.0 will be the same as 1.0 with one exception, we’re adding an entry ID number at the very end of single entry page URIs so that eeSiteKit will do an even better job of preventing possible duplicate content indexing by search engines.

As an example, the permalink to this entry is:

http://demo.eesitekit.com/new-features/better-seo/better-search-engine-optimization/120/

This will give each entry a true achievable permalink while keeping the human readable title and 3-level nested URI’s. This also gives us a unique id number we can use for better accuracy when 2 entries in a site have an identical title, and with some of the new optional multilingual features of 2.0.

We’ve also reversed the nesting of page titles for all pages other than the home page to help put keywords used in entry and category titles at the front of search results to immediately reward the searcher.

We even added a dynamic Robots-Noindex meta tag to help avoid the potential for duplicate content on some pages.

Coming in version 2.0.1 (fourth quarter 2009): We’ve got a meta_data_engine in beta-testing right now that will be ready for release in the next version of eeSiteKit. This new feature is being developed for people who need traditional static-content type control over meta data on a entry-by-entry basis.