[wp-meta] [Making WordPress.org] #4070: Consolidate 301 redirects from legacy URL structures

Making WordPress.org noreply at wordpress.org
Fri Jan 18 13:26:52 UTC 2019

#4070: Consolidate 301 redirects from legacy URL structures
 Reporter:  jonoaldersonwp  |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  low             |  Milestone:
Component:  General         |   Keywords:  seo
 Requests to legacy URL structures undergo multiple 301 redirects, which
 represents an SEO and performance issue.

 E.g., requests to http://www.wordpress.org/plugins/knews-contact-
 form-7-glue undergo the following:

 301 to https://www.wordpress.org/plugins/knews-contact-form-7-glue (`http`
 > `https`)
 301 to https://wordpress.org/plugins/knews-contact-form-7-glue (`www` >
 301 to https://wordpress.org/plugins/knews-contact-form-7-glue/ (force
 trailing slash)

 We should consolidate this into as few 'hops' as possible.

 - The `http` > `https` and removal of `www` should be consolidated into a
 single rule.
 - Where possible elsewhere, the trailing slash rule should also be
 integrated into the same step.
 - In this case, the addition of the trailing slash should be integrated
 into the same rule, based on the path beginning with `/plugins/ `, and the
 omission of a file extension at the end.

Ticket URL: <https://meta.trac.wordpress.org/ticket/4070>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list