Opened 21 months ago

Last modified 6 months ago

#18672 new enhancement

Implement rel="prev" and rel="next" for archives

Reported by: joostdevalk Owned by: joostdevalk
Priority: normal Milestone: Awaiting Review
Component: Permalinks Version: 3.3
Severity: normal Keywords: needs-patch 2nd-opinion
Cc: djpaul@…, 24-7@…, mcepl

Description

As can be seen here:

http://googlewebmastercentral.blogspot.com/2011/09/pagination-with-relnext-and-relprev.html

Google now uses rel="prev" and rel="next" to navigate paginated archives. As we already do a lot of these types of links (rel="index", rel="start" etc.) I think we should add these. I'll come up with a first version of a patch.

Change History (9)

Related to #18128, should probably fix in one pass.

comment:2 follow-up: ↓ 3   joostdevalk21 months ago

Should also consider how we use next and prev in relation to posts now. If a post is paginated, according to how Google now treats it, if you're on page 1, next should lead to the 2nd page of that post, and I don't think we do that.

comment:3 in reply to: ↑ 2   hd-J21 months ago

Replying to joostdevalk:

Should also consider how we use next and prev in relation to posts now.

Considering this, shouldn't we remove next and prev altogether from the single articles, and keep them only for "real" pagination, such as the archive pages?

Version 0, edited 21 months ago by hd-J (next)
  • Cc djpaul@… added

comment:6 follow-up: ↓ 7   F J Kaiser20 months ago

  • Cc 24-7@… added

I added this to my example pagination plugin some time ago. Point is that I added it to the link itself. What would be the reason to add another function and add it to the head?

comment:7 in reply to: ↑ 6   hd-J20 months ago

Replying to F J Kaiser:

Point is that I added it to the link itself. What would be the reason to add another function and add it to the head?

Google seems to prefer the link added to the head, rather than on the link itself. Here is what they say in their annoucement:

rel=”next” and rel=”prev” only need to be declared within the <head> section, not within the document <body>.

1+ , I fix this in my framework theme , I will send a PATCH soon .

  • Cc mcepl added
Note: See TracTickets for help on using tickets.