Hi Eno,
Symfony would differentiate those routes because they have a unique
URL without wildcards.
The literal route definition would be
url: /category1
param: { module: categories, action: show, id: 1 }
The issue with having category in the url is that this is not some
ecommerce website with countless categories. I am talking about 3
categories, so for visitors to the site, typing website.com/category1
is much more concise. Believe me, I do use /category/product wherever
I find it appropriate, but in this case it is simply not.
I'm no expert on SEO, so I'm always looking to learn. Can you explain
why having "category" in the url helps my SEO score for the term?
Everything else constant, I would assume that a site somesite.com/
butterflies ranks better than somesite.com/animals/bugs/butterflies. I
know that search engines like structure, but when, like in my case,
you have only 3 categories, I doubt it would be considered structured.
Thank you for your help.
Daniel
On Jun 19, 2:34 pm, Eno <symb...@gmail.com> wrote:
> On Fri, 19 Jun 2009, Richtermeister wrote:
> > The first
> > version is not interesting from an "aesthetics" standpoint - I don't
> > want those urls to start with /categories.
>
> So how would symfony differentiate the URLs with non-category URLs?
>
> I think /category/:name is actually clearer to the user that its a
> category page and its better from an SEO standpoint.
>
> --
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---
