{"id":24588,"date":"2011-09-15T00:00:00","date_gmt":"2011-09-15T00:00:00","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/pagination-with-relnext-and-relprev\/"},"modified":"2011-09-15T00:00:00","modified_gmt":"2011-09-15T00:00:00","slug":"pagination-with-relnext-and-relprev","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/pagination-with-relnext-and-relprev\/","title":{"rendered":"Pagination with rel=&#8221;next&#8221; and rel=&#8221;prev&#8221;"},"content":{"rendered":"<p class=\"gargardate\">Thursday, September 15, 2011<\/p>\n<aside class=\"key-point\">It&#8217;s been a while since we published this blog post. Some of the information may be outdated (for example, some images may be missing, and some links may not work anymore). <code>rel=prev\/next<\/code> is not an indexing signal anymore. Check out our<br \/>\nup-to-date <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/pagination-incremental-page-loading-and-their-impact-on-google-search\/\">guide to pagination<\/a>.<\/aside>\n<p>\n  Much like <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/specify-your-canonical\/\"><code>rel=\"canonical\"<\/code><\/a><br \/>\n  acts a strong hint for duplicate content, you can now use the HTML link elements<br \/>\n  <a href=\"https:\/\/www.whatwg.org\/specs\/web-apps\/current-work\/multipage\/links.html#sequential-link-types\" class=\"external-link\"><code>rel=\"next\"<\/code> and <code>rel=\"prev\"<\/code><\/a><br \/>\n  to indicate the relationship between component URLs in a paginated series. Throughout the web, a<br \/>\n  paginated series of content may take many shapes\u2014it can be an article divided into several<br \/>\n  component pages, or a product category with items spread across several pages, or a forum thread<br \/>\n  divided into a sequence of URLs. Now, if you choose to include <code>rel=\"next\"<\/code> and<br \/>\n  <code>rel=\"prev\"<\/code> markup on the component pages within a series, you&#8217;re giving Google a<br \/>\n  strong hint that you&#8217;d like us to:\n<\/p>\n<ul>\n<li>\n    Consolidate indexing properties, such as links, from the component pages\/URLs to the series as a<br \/>\n    whole (that is, links should not remain dispersed between <code>page-1.html<\/code>,<br \/>\n    <code>page-2.html<\/code>, etc., but be grouped with the sequence).\n  <\/li>\n<li>\n    Send users to the most relevant page\/URL\u2014typically the first page of the series.\n  <\/li>\n<\/ul>\n<figure class=\"attempt-right\">\n  <img decoding=\"async\" src=\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-7d45337bd030.jpg\" loading=\"lazy\"\n       alt=\"Pages suitable for rel=prev and rel=next annotations\" class=\"screenshot\"><figcaption>\n    The relationship between component URLs in a series can now be indicated to Google through<br \/>\n    <code>rel=\"next\"<\/code> and <code>rel=\"prev\"<\/code>.<br \/>\n  <\/figcaption><\/figure>\n<p>\n  There&#8217;s an exception to the <code>rel=\"prev\"<\/code> and <code>rel=\"next\"<\/code> implementation:<br \/>\n  If, alongside your series of content, you also offer users a view-all page, or if you&#8217;re<br \/>\n  considering a view-all page, please see our post on<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/view-all-in-search-results\/\">View-all in search results<\/a> for more<br \/>\n  information. Because view-all pages are most commonly preferred by searchers, we do our best to<br \/>\n  surface this version when appropriate in results rather than a component page (component pages are<br \/>\n  more likely to surface with <code>rel=\"next\"<\/code> and <code>rel=\"prev\"<\/code>).\n<\/p>\n<p>\n  If you don&#8217;t have a view-all page or you&#8217;d like to override Google returning a view-all page, you<br \/>\n  can use <code>rel=\"next\"<\/code> and <code>rel=\"prev\"<\/code> as described in this post.\n<\/p>\n<figure class=\"attempt-right\">\n  <img decoding=\"async\" src=\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-1aef979f319b.jpg\" loading=\"lazy\"\n       alt=\"Examples of pages that have a view-all version\" class=\"screenshot\"><figcaption>\n    For information on paginated configurations that include a view-all page, please see our post on<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/view-all-in-search-results\/\">View-all in search results<\/a>.<br \/>\n  <\/figcaption><\/figure>\n<h2 id=\"outlining-your-options\" tabindex=\"-1\">Outlining your options<\/h2>\n<p>\n  Here are three options for a series:\n<\/p>\n<ol>\n<li>\n    Leave whatever you have exactly as-is. Paginated content exists throughout the web and we&#8217;ll<br \/>\n    continue to strive to give searchers the best result, regardless of the page&#8217;s<br \/>\n    <code>rel=\"next\"<\/code>\/<code>rel=\"prev\"<\/code> HTML markup\u2014or lack thereof.\n  <\/li>\n<li>\n    If you have a view-all page, or are considering a view-all page, see our post on<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/view-all-in-search-results\/\">View-all in search results<\/a>.\n  <\/li>\n<li>\n    Hint to Google the relationship between the component URLs of your series with<br \/>\n    <code>rel=\"next\"<\/code> and <code>rel=\"prev\"<\/code>. This helps us more accurately index your<br \/>\n    content and serve to users the most relevant page (commonly the first page). Implementation<br \/>\n    details below.\n  <\/li>\n<\/ol>\n<h2 id=\"implementing-rel=next-and-rel=prev\" data-text='Implementing rel=\"next\" and rel=\"prev\"' tabindex=\"-1\">Implementing <code>rel=\"next\"<\/code> and <code>rel=\"prev\"<\/code><\/h2>\n<p>\n  If you prefer option 3 (above) for your site, let&#8217;s get started! Let&#8217;s say you have content<br \/>\n  paginated into the URLs:\n<\/p>\n<div><\/div>\n<p>\n  On the first page, <code>https:\/\/www.example.com\/article?story=abc&amp;page=1<\/code>, you&#8217;d include<br \/>\n  in the <code>&lt;head&gt;<\/code> section:<\/p>\n<div><\/div>\n<p>\n  On the second page, <code>https:\/\/www.example.com\/article?story=abc&amp;page=2<\/code>:<\/p>\n<div><\/div>\n<p>\n  On the third page, <code>https:\/\/www.example.com\/article?story=abc&amp;page=3<\/code>:<\/p>\n<div><\/div>\n<p>\n  And on the last page, <code>https:\/\/www.example.com\/article?story=abc&amp;page=4<\/code>:<\/p>\n<div><\/div>\n<p>A few points to mention:<\/p>\n<ul>\n<li>\n    The first page only contains <code>rel=\"next\"<\/code> and no <code>rel=\"prev\"<\/code> markup.\n  <\/li>\n<li>\n    Pages two to the second-to-last page should be doubly-linked with both <code>rel=\"next\"<\/code><br \/>\n    and <code>rel=\"prev\"<\/code> markup.\n  <\/li>\n<li>\n    The last page only contains markup for <code>rel=\"prev\"<\/code>, not <code>rel=\"next\"<\/code>.\n  <\/li>\n<li>\n    <code>rel=\"next\"<\/code> and <code>rel=\"prev\"<\/code> values can be either relative or absolute<br \/>\n    URLs (as allowed by the <code>&lt;link \/&gt;<\/code> tag). And, if you include a<br \/>\n    <code>&lt;base\/&gt;<\/code> link in your document, relative paths will resolve according to the<br \/>\n    base URL.\n  <\/li>\n<li>\n    <code>rel=\"next\"<\/code> and <code>rel=\"prev\"<\/code> only need to be declared within the<br \/>\n    <code>&lt;head&gt;<\/code> section, not within the document <code>&lt;body&gt;<\/code>.\n  <\/li>\n<li>\n    We allow <code>rel=\"previous\"<\/code> as a syntactic variant of <code>rel=\"prev\"<\/code> links.\n  <\/li>\n<li>\n    <code>rel=\"next\"<\/code> and <code>rel=\"previous\"<\/code> on the one hand and<br \/>\n    <code>rel=\"canonical\"<\/code> on the other constitute independent concepts. Both declarations can<br \/>\n    be included in the same page. For example,<br \/>\n    <code>https:\/\/www.example.com\/article?story=abc&amp;page=2&amp;sessionid=123<\/code> may contain:<\/p>\n<div><\/div>\n<\/li>\n<li>\n    <code>rel=\"prev\"<\/code> and <code>rel=\"next\"<\/code> act as hints to Google, not absolute<br \/>\n    commands.\n  <\/li>\n<li>\n    When implemented incorrectly, such as omitting an expected <code>rel=\"prev\"<\/code> v\u0259 ya<br \/>\n    <code>rel=\"next\"<\/code> designation in the series, we&#8217;ll continue to index the page(s), and<br \/>\n    rely on our own heuristics to understand your content.\n  <\/li>\n<\/ul>\n<p>\n  More information can be found in our<br \/>\n  <a href=\"https:\/\/support.google.com\/webmasters\" class=\"external-link\">Help Center<\/a>, or join the<br \/>\n  conversation in our<br \/>\n  <a href=\"https:\/\/support.google.com\/webmasters\/community\" class=\"external-link\">Webmaster Help Forum<\/a>!\n<\/p>\n<p class=\"byline-author\">\n  Written by Benjia Li and Joachim Kupke, Software Engineers, Indexing Team<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Thursday, September 15, 2011 It&#8217;s been a while since we published this blog post. Some of the information may be outdated (for example, some images may be missing, and some links may not work anymore). rel=prev\/next is not an indexing signal anymore. Check out our up-to-date guide to pagination. Much like rel=&#8221;canonical&#8221; acts a strong [&hellip;]<\/p>\n","protected":false},"menu_order":84768,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[665],"ar_kb_etiket":[],"class_list":["post-24588","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-blog"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24588","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":0,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24588\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/26897"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=24588"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=24588"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=24588"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}