Simple SEO URL (OLD version) [support thread]

[yellow1912]

Here is the ultimate format I've been thinking about:
cpath along with category names will be appended to all product_info links
All product info links should use only one single form of link, anything else will be redirected (301)

1. form 1:
cat1name-id/cat2name-id/cat3name-id/productname-id

2. form 2:
cat1name-cat2name-cat3name-id1_id2_id3/productname-id

[jeking]

yellow1912,

Are you are a stable release yet? The new versions have been slower, which I interpret as a good sign.

[yellow1912]

Actually, I have a number of urgent projects on hand and couldnt get the time to finish some important tasks before releasing a stable release.

But I'll try to do this asap.
If someone else want to take the code and further improve it, you are welcome to do so, and dont forget to share your code here.

[jeking]

That was my other interpretation of no new release. I was trying to be positive. :-)

I wish I could, but I'm no coder.

[profitshock]

Wow. Great work. Am Glad I found this.

I use an earlier version of (?) SEF mod at .mutualadvantage.co.uk

While your version does have many benefits one thing that I would love to see changed is the format of your cat url display.

Mine displays - this-category-c while yours displays c-this-category.

From an SEO perspective having the actual category name before the 'c' does help.
I also firmly believe that the SE's 'like' a visible structure to the urls i.e.

wine/red-wine/merlot/product.php

I know that SE's can see the 'page' and that to some extent the url path format isn't important (a node is a node is ... the same node) but I like to think that encouraging the SE's to theme your structure helps.

Thanks

Kev

[empower]

Where is the install.sql file?

Also, I seem to get this warning error:
Warning: preg_replace() [function.preg-replace]: No ending delimiter '/' found in /home/empowerm/public_html/includes/init_includes/init_ssu.php on line 36

[yellow1912]

This mod is installed automatically, just visit admin/ssu.php

[empower]

Here is the ultimate format I've been thinking about:
cpath along with category names will be appended to all product_info links
All product info links should use only one single form of link, anything else will be redirected (301)

1. form 1:
cat1name-id/cat2name-id/cat3name-id/productname-id

2. form 2:
cat1name-cat2name-cat3name-id1_id2_id3/productname-id

Is there a relatively easy way to customize it to mimic Amazon's style?

http://www.amazon.com/Zen-Cart-Building-Online-Store/dp/141206645X

Amazon has spent tons of Research on SEO, and I like the way their URLs are user-friendly and descriptive and short. I just found this mod, so I haven't had the time to dive into the code.. but just wondering if it would be doable just to have something like this.

Ideally, I think it's best to have:

www.site.com/productname-id

or:

www.site.com/catXname-idX/productname-id

where X is the LAST child in the category tree (deepest category level)

What do you think?

[yellow1912]

This module is commented quite well, and in the matter of fact there are users that customized it for their own link style already.

You can try to look at the class and see if you can figure it out. You should be able to mess around with it easily, of course a certain level of php knowledge is required.

[yellow1912]

To answer your question:

www.site.com/catXname-idX/productname-id

Yes, it is possible, but remember 1 thing: zencart needs the whole cPath string which including the parent of the cat in certain situations.
1 solution: re-build the path from the child id, which is really easy actually
a. dont rebuild it everytime, save cPath of each cat in files which can be retrieved later (so we dont waste mysql resource)

b. Another way, which is far better:
Look at my Simple Category Tree module, this module does many things, but 1 of the nice thing it does is: you can retrieve the cPath of and category easily.
https://svn.rubikintegration.com/zen...tegories_tree/
Note: I havent documented this mod well, so you will have to dig in the code. The code is commented quite well tho.