{"id":24594,"date":"2011-09-15T00:00:00","date_gmt":"2011-09-15T00:00:00","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/view-all-in-search-results\/"},"modified":"2011-09-15T00:00:00","modified_gmt":"2011-09-15T00:00:00","slug":"view-all-in-search-results","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/view-all-in-search-results\/","title":{"rendered":"View-all in search results"},"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.<\/aside>\n<p>\n  User testing has taught us that searchers much prefer the view-all, single-page version of content<br \/>\n  over a component page containing only a portion of the same information with arbitrary page breaks<br \/>\n  (which cause the user to click &#8220;next&#8221; and load another URL).\n<\/p>\n<figure class=\"attempt-right\">\n  <img decoding=\"async\" src=\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-5298fc5917ba.jpg\" loading=\"lazy\"\n       alt=\"Example of preferred search experiences for paginated content\" class=\"screenshot\"><figcaption>\n    Searchers often prefer the view-all vs. paginated content with arbitrary page breaks and worse<br \/>\n    latency.<br \/>\n  <\/figcaption><\/figure>\n<p>\n  Therefore, to improve the user experience, when we detect that a content series (for example,<br \/>\n  <code>page-1.html<\/code>, <code>page-2.html<\/code>, etc.) also contains a single-page version<br \/>\n  (for example, <code>page-all.html<\/code>), we&#8217;re now making a larger effort to return the single-page<br \/>\n  version in search results. If your site has a view-all option, there&#8217;s nothing you need to do;<br \/>\n  we&#8217;ll work to do it on your behalf. Also, indexing properties, like links, will be consolidated<br \/>\n  from the component pages in the series to the view-all page.\n<\/p>\n<h2 id=\"high-latency-can-make-the-view-all-less-preferred\" tabindex=\"-1\">High latency can make the view-all less preferred<\/h2>\n<p>\n  Interestingly, the cases when users didn&#8217;t prefer the view-all page were correlated with high<br \/>\n  latency (for example, when the view-all page took a while to load, say, because it contained many<br \/>\n  images). This makes sense because we know users are<br \/>\n  <a href=\"https:\/\/googleresearch.blogspot.com\/2009\/06\/speed-matters.html\" class=\"external-link\">less satisfied with slow results<\/a>.<br \/>\n  So while a view-all page is commonly desired, as a webmaster it&#8217;s important to balance this<br \/>\n  preference with the page&#8217;s load time and overall user experience.\n<\/p>\n<h2 id=\"best-practices-for-a-series-of-content\" tabindex=\"-1\">Best practices for a series of content<\/h2>\n<ol>\n<li>\n<p>\n      <b>If your site includes view-all pages:<\/b> We aim to detect the view-all version of your<br \/>\n      content and, if available, its associated component pages. There&#8217;s nothing more you need to<br \/>\n      do! However, if you&#8217;d like to make it more explicit to us, you can include<br \/>\n      <code>rel=\"canonical\"<\/code> from your component pages to your view-all to increase the<br \/>\n      likelihood that we detect your series of pages appropriately.\n    <\/p>\n<figure class=\"attempt-right\">\n      <img decoding=\"async\" src=\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-c137cdf537d1.jpg\" loading=\"lazy\"\n           alt=\"Implementation diagram for rel-canonical for content series\" class=\"screenshot\"><figcaption>\n        <code>rel=\"canonical\"<\/code> can specify the superset of content (that is, the view-all<br \/>\n        page, in this case <code>page-all.html<\/code>) from the same information in a series of<br \/>\n        URLs.<br \/>\n      <\/figcaption><\/figure>\n<p>\n      <i>Why does this work?<\/i> In the diagram, <code>page-2.html<\/code> of a series may specify<br \/>\n      the canonical target as <code>page-all.html<\/code> because <code>page-all.html<\/code> is a<br \/>\n      superset of <code>page-2.html<\/code>&#8216;s content. When a user searches for a query term and<br \/>\n      <code>page-all.html<\/code> is selected in search results, even if the query most related to<br \/>\n      <code>page-2.html<\/code>, we know the user will still see <code>page-2.html<\/code>&#8216;s relevant<br \/>\n      information within <code>page-all.html<\/code>.\n    <\/p>\n<p>\n      On the other hand, <code>page-2.html<\/code> shouldn&#8217;t designate <code>page-1.html<\/code> as<br \/>\n      the canonical because <code>page-2.html<\/code>&#8216;s content isn&#8217;t included on<br \/>\n      <code>page-1.html<\/code>. It&#8217;s possible that a user&#8217;s search query is relevant to content on<br \/>\n      <code>page-2.html<\/code>, but if <code>page-2.html<\/code>&#8216;s canonical is set to<br \/>\n      <code>page-1.html<\/code>, the user could then select <code>page-1.html<\/code> in search<br \/>\n      results and find herself in a position where she has to further navigate to a different page<br \/>\n      to arrive at the desired information. That&#8217;s a poor experience for the user, a suboptimal<br \/>\n      result from us, and it could also bring poorly targeted traffic to your site.\n    <\/p>\n<p>\n      However, if you strongly desire your view-all page not to appear in search results:\n    <\/p>\n<ol>\n<li>\n        Make sure the component pages in the series don&#8217;t include <code>rel=\"canonical\"<\/code> to<br \/>\n        the view-all page, and<\/li>\n<li>\n        Mark the view-all page as<br \/>\n        <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/block-search-indexing-with-noindex\/\"><code>noindex<\/code><\/a> using any<br \/>\n        of the standard methods.\n      <\/li>\n<\/ol>\n<li>\n<p>\n      <b>If you&#8217;d like to surface individual, component pages (or there&#8217;s no view-all available)<\/b>:<br \/>\n      It may be the case that one or both of the situations below apply to your site:\n    <\/p>\n<ul>\n<li>\n        The view-all page is undesirable as a search result (for example, load time too high or too<br \/>\n        difficult for users to navigate).\n      <\/li>\n<li>\n        Your users prefer the multi-page experience and to be directed to a component page in search<br \/>\n        results, rather than the view-all page.\n      <\/li>\n<\/ul>\n<p>\n      If so, you can use standard HTML<br \/>\n      <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/pagination-with-relnext-and-relprev\/\"><code>rel=\"next\"<\/code> and <code>rel=\"prev\"<\/code> elements<\/a><br \/>\n      to specify a relationship between the component pages in your series of content. If done<br \/>\n      correctly, Google will generally strive to:\n    <\/p>\n<ul>\n<li>\n        Consolidate indexing properties, such as links, between the component pages\/URLs.\n      <\/li>\n<li>\n        Send users to the most relevant page\/URL from the component pages. Typically, the most<br \/>\n        relevant page is the first page of your content, but our algorithms may point users to one<br \/>\n        of the component pages in the series.\n      <\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<p>\n  It&#8217;s not uncommon for webmasters to incorrectly use <code>rel=\"canonical\"<\/code> from component<br \/>\n  pages to the first page of their series (for example, <code>page-2.html<\/code> with<br \/>\n  <code>rel=\"canonical\"<\/code> to <code>page-1.html<\/code>). We recommend against this<br \/>\n  implementation because the component pages don&#8217;t actually contain duplicate content. Using<br \/>\n  <code>rel=\"next\"<\/code> and <code>rel=\"prev\"<\/code> is far more appropriate.\n<\/p>\n<h2 id=\"summary\" tabindex=\"-1\">Summary<\/h2>\n<p>\n  Because users generally prefer the view-all option in search results, we&#8217;re making more of an<br \/>\n  effort to properly detect and serve this version to searchers. If you have a series of content,<br \/>\n  there&#8217;s nothing more you need to do. If you&#8217;d like to hint more to Google how best to serve users<br \/>\n  your information:\n<\/p>\n<ol>\n<li>\n    To better optimize your view-all page, you can use <code>rel=\"canonical\"<\/code> from component<br \/>\n    pages to the single-page version; otherwise,\n  <\/li>\n<li>\n    If a view-all page doesn&#8217;t provide a good user experience for your site, you can use the<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/pagination-with-relnext-and-relprev\/\"><code>rel=\"next\"<\/code> and <code>rel=\"prev\"<\/code><\/a><br \/>\n    attributes as a strong hint for Google to identify the series of pages and still surface a<br \/>\n    component page in results.\n  <\/li>\n<\/ol>\n<p>\n  As always, you can ask questions 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. User testing has taught us that searchers much prefer the view-all, single-page version [&hellip;]<\/p>\n","protected":false},"menu_order":84768,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[665],"ar_kb_etiket":[],"class_list":["post-24594","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\/24594","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\/24594\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/26901"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=24594"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=24594"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=24594"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}