[buddypress-trac] [BuddyPress] #1741: Resolve redundant URLs for SEO reasons

buddypress-trac at lists.automattic.com buddypress-trac at lists.automattic.com
Tue Feb 21 14:55:18 UTC 2012

#1741: Resolve redundant URLs for SEO reasons
 Reporter:  Ezd          |       Owner:  boonebgorges
     Type:  enhancement  |      Status:  reopened
 Priority:  major        |   Milestone:  1.6
Component:  Core         |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  2nd-opinion  |
Changes (by boonebgorges):

 * keywords:  has-patch 2nd-opinion => 2nd-opinion


 > bb_redirect_canonical should hook into template_redirect, ideally, not
 new bp_core_pre_load_template hooks

 This was not possible before, because of our load order. Due to changes
 made in the past day or two, it should now be possible. See #4031.

 > I would tend to think that canonicalization should roll up. We don't
 standardize on /some-post/page-1/, we standardize on /some-post/

 I am of two minds. The core team discussed this pretty thoroughly before
 implementation. On the one hand, there's no question that rolling up means
 prettier URLs.

 On the other hand, there are a couple of considerations in favor of
 "rolling down".
 - It's done. No more work would be required.
 - The analogy with /page-1/ is not perfect. It seems to me that the
 difference between /users/nacin/profile/ and /users/nacin/activity/ is
 more substantive than the difference between /some-post/page-1/ and /some-
 post/page-2/. The latter is a way of distinguishing between different
 parts of the same resource; the former is (arguably) about different
 resources. So, while in the case of pagination I agree 100% percent that
 you should roll up (pagination does not provide any semantically relevant
 information about the resource), it's not as obvious that we should, since
 the additional URL chunks give insight into the fact that it's a different
 sub-resource of the user.
 - We allow admins to change default nav/subnav, either by defining
 constants, filtering various values, or using bp_core_new_nav_default().
 This means that, on one installation of BP, /users/nacin/ could resolve to
 the Profile, while on another it could resolve to the user Activity
 Stream. That means that there would be some conceptual inconsistency
 between different BP installations.

 None of these is a knockdown argument. Rewriting to roll up will not be
 difficult. It's possible that the additional information provided by the
 more specific URLs isn't very valuable, and in any case it can be inferred
 from the <title> tag, navigation states, etc. And different conceptual
 schemes on different BP instances may be a good thing rather than bad.

 Would like the feedback of another core dev before making a final decision
 about it.

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/1741#comment:13>
BuddyPress <http://buddypress.org/>

More information about the buddypress-trac mailing list