[wp-meta] [Making WordPress.org] #3671: index.php files for static pages on wordpress.org are accessible/indexable

Making WordPress.org noreply at wordpress.org
Sun Jun 17 18:58:47 UTC 2018

#3671: index.php files for static pages on wordpress.org are accessible/indexable
 Reporter:  jonoaldersonwp            |      Owner:  (none)
     Type:  enhancement               |     Status:  new
 Priority:  low                       |  Milestone:
Component:  Make (Get Involved) / P2  |   Keywords:
 Static pages are implemented by creating `index.php` files within named
 folders. As a result, the actual `index.php` file is directly accessible
 (in addition to the named folder), which results in SEO, accessibility and
 analytics issues.

 E.g., `wordpress.org/download/` co-exists with

 This includes the homepage, `/downloads/`, and other significant pages. As
 far as I can see, this issue can be resolved in three ways, in order of

 1) All requests ending in `/index.php` should be configured to serve a 301
 redirect to the previous level folder. Note, however, this logic would
 need to be stored/executed somewhere central/low in the stack (which may
 prove challenging to implement and manage), and may create unexpected
 behaviours for other requests which legitmately end in index.php - and
 whilst I haven't seen any such cases, I haven't dug particularly deeply.

 2) 301 redirects should be created all static/standalone paths/pages
 created in this manner (i.e., folders with `index.php` files), and
 stored/executed via `.htaccess` files (or equivalent) in the respective

 3) 301 redirects should be created on a case-by-case basis for specified

 In all cases, query parameters and/or fragments should be preserved during
 the redirect (e.g., `/page/index.php?key=var#hash` should redirect to

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

More information about the wp-meta mailing list