Opened 5 years ago

Closed 5 years ago

#4063 closed defect (bug) (fixed)

Paginated states in the plugin and theme directories should use rel next/prev tags

Reported by: jonoaldersonwp's profile jonoaldersonwp Owned by:
Milestone: Priority: high
Component: Plugin Directory Keywords: seo


Pages like and should declare the next and previous pages in the series, via relational link tags in the <head>.

See for guidelines.

Attachments (1)

themes.4063.diff (5.0 KB) - added by dd32 5 years ago.

Download all attachments as: .zip

Change History (7)

#1 @jonoaldersonwp
5 years ago

  • Keywords seo added

#2 @dd32
5 years ago

In 8118:

Plugin Directory: Implement <link rel="prev|next"> for archives & searches.

See #4063.

#3 @dd32
5 years ago

I have the code for the theme directory too, but it's worth noting that the JS version of the page doesn't use the pagination URL format so currently those links actually end up as empty pages for users who have JS enabled..

Adding pagination support to the URL so that /browse/popular/page/2 works isn't out of the question, but is a little beyond my rusty Backbone skillset right now it seems.

I'm actually wondering if the paginated urls should be noindex, follow as well to get them out of search indexes, but leave the themes and base-urls such as /browse/popular there?

#4 @jonoaldersonwp
5 years ago

Ooh, complexity!

Let's see...

We shouldn't add this until the with-JS version of the pagination works. Do you want a new ticket for that?

And, we definitely *shouldn't* add noindex to paginated states - rationale here ;)

#5 @dd32
5 years ago

Lets leave everything in this ticket for now, can be split off if it's still an issue in a few days.

5 years ago

#6 @dd32
5 years ago

  • Component changed from General to Plugin Directory
  • Resolution set to fixed
  • Status changed from new to closed

I've spun off the Theme Directory part into #4092, I'm going to mark this ticket as fixed for the Plugin Directory.

Unfortunately Themes are a very different codebase, and isn't likely to be fixed anytime soon.

Note: See TracTickets for help on using tickets.