[jira] [Comment Edited] (OFBIZ-5312) Proposal: URL-Generation Changes (mostly for SEO reasons but not only)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Comment Edited] (OFBIZ-5312) Proposal: URL-Generation Changes (mostly for SEO reasons but not only)

Nicolas Malin (Jira)

    [ https://issues.apache.org/jira/browse/OFBIZ-5312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943308#comment-13943308 ]

Sebastian Wachinger edited comment on OFBIZ-5312 at 3/21/14 6:06 PM:
---------------------------------------------------------------------

To optimize SEO we allegedly should include the page's language in the URL. For those using Google Webmaster Tools it seems to be considered best practice to have a URL like _example.com/de/_ (if you do not use subdomains _de.example.com_ or specific TLDs _example.de_).

Maybe it's a good idea to take this information from the _Locale String_ of the _Product Name_ and/or _Alternative URL_ product content in order to automatically generate the URL (based again on [Parimal's proposition|https://issues.apache.org/jira/browse/OFBIZ-5312?focusedCommentId=13823583&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13823583]).
I think this would also work for multi-regional websites, e.g. _example.com/es-es/_ and _example.com/es-mx/_ (same language, different region).

Speaking of product pages we would have URLs like _example.com/product/en/Product-Name-product-id_. In case I did not miss any repercussions, do you think this can and should be done?




was (Author: komdata):
To optimize SEO we allegedly should include the page's language in the URL. For those using Google Webmaster Tools it seems to be considered best practice to have a URL like _example.com/de/_ (if you do not use subdomains _de.example.com_ or specific TLDs _example.de_).

Maybe it's a good idea to take this information from the _Locale String_ of the _Product Name_ and/or _Alternative URL_ product content in order to automatically generate the URL (based again on [Parimal's proposition|https://issues.apache.org/jira/browse/OFBIZ-5312?focusedCommentId=13823583&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13823583]).
I think this would also work for multi-regional websites, e.g. _example.com/es-es/_ and _example.com/es-mx/_ (same language, different region).

In case I did not miss any repercussions, do you think this can and should be done?



> Proposal: URL-Generation Changes (mostly for SEO reasons but not only)
> ----------------------------------------------------------------------
>
>                 Key: OFBIZ-5312
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5312
>             Project: OFBiz
>          Issue Type: New Feature
>          Components: specialpurpose/ecommerce
>    Affects Versions: SVN trunk
>            Reporter: Jacques Le Roux
>            Assignee: Jacques Le Roux
>            Priority: Minor
>              Labels: changes, ecommerce, friendly, seo, url
>             Fix For: SVN trunk
>
>         Attachments: OFBIZ-5312 - ofbiz-ecommerce-seo.patch, OFBIZ-5312 - ofbiz-ecommerce-seo.patch, OFBIZ-5312 - ofbiz-ecommerce-seo.patch, OFBIZ-5312 - ofbiz-ecommerce-seo.patch, OFBIZ-5312 - ofbiz-ecommerce-seo.patch, OFBIZ-5312 - ofbiz-ecommerce-seo.patch, OFBIZ-5312 - ofbiz-ecommerce-seo.patch, OFBIZ-5312 - ofbiz-ecommerce-seo.patch, OFBIZ-5312 - ofbiz-ecommerce-seo.patch, OFBIZ-5312 - ofbiz-ecommerce-seo.patch, OFBIZ-5312 - ofbiz-ecommerce-seo.patch, OFBIZ-5312 - ofbiz-ecommerce-seo.patch, OFBiz-5312-product-ecommerce-seo-20131031.patch, OFBiz-5312-product-ecommerce-seo-for-seo-branch.patch, OFBiz-5312-product-ecommerce-seo.patch, SeoContextFilter.java.patch
>
>
> [This was proposed by Paul Piper in Nabble 7 months ago|http://ofbiz.135035.n4.nabble.com/Proposal-URL-Generation-Changes-td4639289.html]. Here is quoted Paul's proposal
> {quote}
> Hey Everyone,
> over at ilscipio (www.ilscipio.com) we developed a set of functional OFBiz changes that we believe the entire community could benefit from. The changes have been implemented in parts in Syracus (www.syracus.net) for a while now, but we figured that some of which are too crucial for ofbiz' success in the long run, so we are considering the contribution (as we did with the SOLR component).
> As you are probably aware, OFBiz has a pretty uncommon way of generating URLs. Most of this has to do with the fact that OFBiz uses a servlet (ControlServlet)  to handle all requests. The servlet is mounted at /control, so that it won't interfere with other servlets. Though functionally valid, this has the sideeffect that all urls are actually created on /control, which is neither pretty, nor good by any measures of SEO. It also means that a few 302 redirects are necessary to forward the user from / to /control/main. It also makes requests more complicated, since many forwards are necessary whenever somebody wants to move away from this implementation.
> Since this is hurtful to many of the implementers, I wanted to discuss whether or not you guys would be interested in the changes we have made. The functional changes contain:
> * Removal of /control out of all the urls
> * SEO-friendly URLS
> * Configurable product/category and other URLs
> * Frontpage mapping from /main to /
> It was tested on our end and contains all necessary improvements (Transforms, Sample Configuration, Servlets & Filters) for it to be applicable.
> If interested, I would create a new JIRA ticket for this and after a few minor internal discussions, we will gladly provide the rest of you with it.
> Regards,
> Paul
> {quote}
> There is even a patch, mostly done by Jinghai Shi, that I attach here. Even if it has been already used in [Syracus|http://syracus.net/] since early this year, some help would be needed to test it thoroughly in OFBiz.
> Then we should discuss if it's the way to go. I believe it is. Who needs a /control/ or /main by default in ecommerce urls? Would you not prefer http://localhost:8080/ecommerce/ over http://localhost:8080/ecommerce/control/main ?



--
This message was sent by Atlassian JIRA
(v6.2#6252)