Re: Joomla 1.1 and SEO improvements

Reply #49 on: March 02, 2006, 12:19:15 AM

vavroom
Joomla! Hero

Thanks David,  I don't know what the Core guys are doing with this at this point.  But what I like to keep in mind is that a lot of the SE stuff goes way beyond search engine stuff.  It's not a vaccuum, and improvements in one area will improve other areas.


Re: Joomla 1.1 and SEO improvements

Reply #48 on: February 28, 2006, 09:52:45 PM

spinfx
New Member

Quote from: vavroom on December 30, 2005, 08:51:57 PM

DRAFT
Suggestion Summary
Introduction of Dublin Core Metadata elements

Suggestion Description
Implement Dublin Core metadata elements as per http://dublincore.org/ in addition to current/improved meta keywords and description handling.

Supporting Argument(s)

References

How other systems handle this


Vavoom - this is likely to become a requirement for Australian Govt websites (still some discussion to go on this, but there is pressure from bodies such as NOI or its recent replacement).

The ability to select from a list of metadata (ie Dublin Core) those that will be displayed or perhaps the ability to create new meta tags might be a solution.

Most of us appreciate that SEs rarely look beyond Description and Keywords, but nevertheless, there will likely be a requirement to satisfy govt guidelines.

Hope that helps

Cheers, David

Reply #47 Omitted


Re: Joomla 1.1 and SEO improvements

Reply #46 on: January 18, 2006, 09:49:42 AM

Zorro
Jr. Member

Part 3 covers ModX. It allows for some more flexibility.

The simplest way for having SEF URLs is based on the page's ID (just like standard Joomla SEF):

http://mydomain.com/index.php?id=2 becomes
http://mydomain.com/2

You can define a prefix and suffix too, so with a prefix of "page" and a suffix of ".html" the above URL would read

http://mydomain.com/page2.html

Page aliases entered in the administration can be used as well (Kind of repeating myself, aren't I?) so the URL becomes

http://mydomain.com/about.html

More flexibility: The URL can reflect content hierarchy. If you so wish, you can have URLs such as

http://mydomain.com/grandparent/parent/child.html

so even duplicate aliases can be used in different content hierarchies.

The system can also automatically generate aliases from the page title when saving items.

Pretty neat and OpenSEF-ish ... except it's right there in the core.

Sample .htaccess file attached. The rewrite rules are pretty basic, all the magic is done inside the core.

I think I'll be skipping BlogCMS since at first glance it only seems to support ID-based URLS such as /item/1234 which is not what we're after here.

Of the four systems I looked at, ModX's flexibility and power with regard to friendly URLs impressed me the most.

Kind regards,
Zorro

Last Edit: January 18, 2006, 09:52:32 AM by Zorro


Re: Joomla 1.1 and SEO improvements

Reply #45 on: January 18, 2006, 09:21:13 AM

Zorro
Jr. Member

Here's part 2. This covers CMS Made Simple.

It too allows you to define a "page alias" when entering a "content" item, i.e. a page.

The use of a .htaccess file allows you to have URLs ending in .html, .shtml or whatever. So, http://mydomain.com/index.php?page=about_us
becomes
http://mydomain.com/about_us.html
once a configuration directive to use mod_rewrite is set.

I've attached a sample .htaccess file below.

Kind regards,
Zorro

Last Edit: January 18, 2006, 09:52:19 AM by Zorro


Reply #44 Omitted


Re: Joomla 1.1 and SEO improvements

Reply #43 on: January 16, 2006, 10:27:28 AM

Zorro
Jr. Member

Here's part 1, more when I find the time. This covers Drupal.

Drupal allows you to define a "page alias" once the module "path" is activated.

When entering the page's (or item's) contents, an extra field can optionally be used to type an alias, e.g. "about" or "products". The alias then replaces the parameters in the URL, e.g. http://mydomain.com/?q=item_name becomes http://mydomain.com/about.

Drupal allows users to modify the URL replacement scheme by "mass URL aliasing". The way to do this involves getting your hands a little dirty by tweaking a bit of code and is described in the help file I attached below.

To rewrite URLs, Drupal of course needs mod_rewrite and a .htaccess file which I also included in the file below.

Kind regards,
Zorro


Reply #42 Omitted


Reply #41 Omitted


Reply #40 Omitted


Reply #39 Omitted