[wp-meta] [Making WordPress.org] #4684: Trac 'reports' crawl and indexing controls

Making WordPress.org noreply at wordpress.org
Fri Aug 16 12:12:10 UTC 2019


#4684: Trac 'reports' crawl and indexing controls
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Trac            |  Resolution:
 Keywords:  seo analytics   |
----------------------------+---------------------
Changes (by jonoaldersonwp):

 * priority:  low => normal


Old description:

> Trac 'reports' pages, like https://core.trac.wordpress.org/report/5,
> require the following improvements:
>
> * Remove default sort (and other) parameters from pagination links. E.g.,
> the link to 'page 2' in this state includes a redundant `asc=``
> parameter. This is the default behaviour, and it should be removed.
>
> * Add a canonical URL tag, referencing the current report and paginated
> state, omitting the (now removed) `asc=1` parameter.
>
> * Update the page title to include the paginated state (E.g., `{5} Next
> Major Release – Page 1 of 5 – WordPress Trac`)
>
> Note that these must all be deployed as a single change. A
> partial/selective implementation of these may make things worse.

New description:

 Trac 'reports' pages, like https://core.trac.wordpress.org/report/5,
 require the following improvements:

 * Remove default sort (and other) parameters from pagination links. E.g.,
 the link to 'page 2' in this state includes a redundant `asc=`` parameter.
 This is the default behaviour, and it should be removed.

 * Add a canonical URL tag, referencing the current report and paginated
 state, omitting the (now removed) `asc=1` parameter.

 * Update the page title to include the paginated state (E.g., `{5} Next
 Major Release – Page 1 of 5 – WordPress Trac`)

 * Add (or modify the output of) a meta robots tag with a value of
 `noindex, follow` on all requests which include the following parameters:
 `max`, `sfp_email`, `sfph_mail`, `sort`, `USER`, `asc`

 Note that these must all be deployed as a single change. A
 partial/selective implementation of these may make things worse.

--

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4684#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list