ofbiz-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anil K Patel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-5312) Proposal: URL-Generation Changes (mostly for SEO reasons but not only)
Date Thu, 20 Mar 2014 21:59:42 GMT

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

Anil K Patel commented on OFBIZ-5312:
-------------------------------------

Paul mentions below points as cons of CMS approach. Please see my response to them.

This issue is about SEO and Paul starts by saying we can ignore Page Meta data. SEO is not
just about URL, we have to consider many things. 

Potentially duplicate content
Anil> With CMS approach you don't have this issue. 

Doesn't "fix" partial matches
Anil > Partial Matches may cause duplicate content issue. Its not good for SEO.

No historisation of former URLs
Anil > WebsitePathAlias entity keeps all valid URLs. When a URL no more exists, you can
forward request for a path alias to something else by setting aliasTo field. 

No automatic generation of URLs for Products
Anil > Automatic URL generation is bad idea but if needed,  Simple eca can be put in place
to maintain pathAlias field value e.g When Product name is modified.

No automatic generation of URLs for Categories
Anil > Same as for Product page URL.
Increases DB (Database entries)
Anil > I am surprised this is a bad thing. 

Requires additional manual work for all entries --> potentially risky when used by non-tech
people
Anil > Maintaining Content data is not much different from maintaining Product data. With
right scripts data maintenance is not that hard.

I can be helpful if Paul will take time to understand CMS, I hate it when people take wrong
approach and expect others to defend.

> 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)

Mime
View raw message