{"id":284,"date":"2026-09-17T00:34:45","date_gmt":"2026-09-16T15:34:45","guid":{"rendered":"https:\/\/www.studio-jt.co.kr\/seo-glossary\/pagination\/"},"modified":"2026-11-15T18:46:52","modified_gmt":"2026-11-15T09:46:52","slug":"pagination","status":"publish","type":"seo_glossary","link":"https:\/\/www.studio-jt.co.kr\/en\/seo-glossary\/pagination\/","title":{"rendered":"Pagination"},"content":{"rendered":"<h2 class=\"wp-block-heading\">Three ways to split a long list into pages<\/h2>\n<p class=\"wp-block-paragraph\">Pagination means splitting content into pages. Instead of putting a product list, a list of blog posts or a long article on one screen, you split it into page 1, page 2 and so on, and let users move through them with next, previous and page number links. Google&#8217;s documentation also defines pagination as a way to browse results one page at a time through links such as next, previous and page numbers.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/ecommerce\/pagination-and-incremental-page-loading\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> The same document defines two other methods as well: &#8220;load more,&#8221; where a button expands the initially shown results, and infinite scroll, where more content loads as you scroll to the bottom of the screen.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/ecommerce\/pagination-and-incremental-page-loading\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<p class=\"wp-block-paragraph\">To users, the difference between the three is a matter of preference, but to search engines it is a fork in the road. When finding pages to index, Google generally crawls the URLs in the href attribute of a tags. Crawlers don&#8217;t click buttons, and they generally don&#8217;t run JavaScript functions that change the screen only after a user action.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/ecommerce\/pagination-and-incremental-page-loading\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> Yet load more and infinite scroll are usually implemented with JavaScript.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/ecommerce\/pagination-and-incremental-page-loading\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> That is why people can scroll down and see page 2 products, while Googlebot stops at page 1. <a href=\"\/en\/seo-glossary\/javascript-seo\/\">JavaScript SEO<\/a> covers the underlying mechanics in detail.<\/p>\n<h2 class=\"wp-block-heading\">Five rules Google wrote into its documentation<\/h2>\n<p class=\"wp-block-paragraph\">Google&#8217;s pagination document is not long. Boiled down, there are five things to follow.<\/p>\n<ul class=\"wp-block-list\"><li>Link pages sequentially by including a link to the next page on each page with an a href tag.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/ecommerce\/pagination-and-incremental-page-loading\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><li>Consider including a link back to the first page on every page in the series, so Google knows where the series starts.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/ecommerce\/pagination-and-incremental-page-loading\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><li>Give each page a unique URL such as ?page=2. Google treats each of these URLs as a separate page.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/ecommerce\/pagination-and-incremental-page-loading\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><li>Don&#8217;t use URL fragment identifiers (the part after #) for page numbers. Google ignores what comes after # and may not follow links that differ only after the #.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/ecommerce\/pagination-and-incremental-page-loading\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><li>Don&#8217;t use the first page as the canonical page for the whole series; give each page its own canonical URL.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/ecommerce\/pagination-and-incremental-page-loading\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><\/ul>\n<p class=\"wp-block-paragraph\">The document also has one line about rel=next and rel=prev. It says Google used these tags in the past to understand the relationship between pages but no longer does, while other search engines may still use them.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/ecommerce\/pagination-and-incremental-page-loading\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> Behind this one line lies an eight-year story.<\/p>\n<h2 class=\"wp-block-heading\">rel=next\/prev was retired in 2019<\/h2>\n<p class=\"wp-block-paragraph\">In September 2011, Google offered three options for pagination. Since paginated content is everywhere on the web, you could leave it as it is; if you had or planned to make a view-all page, you could follow the guidance for view-all pages; or you could add rel=next and rel=prev to each page as a hint that the pages belong to one series. Google said that with these hints it would index more accurately and show users the most relevant page, usually the first one.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.seroundtable.com\/google-pagination-solution-14037.html\" target=\"_blank\" rel=\"noopener\">Search Engine Roundtable<\/a><\/p>\n<p class=\"wp-block-paragraph\">For years afterward, these tags were considered the standard for pagination SEO. Then on March 21, 2019, Google said that after re-evaluating its indexing signals it had retired rel=prev\/next. It added that, according to studies, users love single-page content, so aim for that when possible, but splitting content across multiple pages is also fine for Google Search.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.seroundtable.com\/google-rel-prev-next-change-27295.html\" target=\"_blank\" rel=\"noopener\">Search Engine Roundtable<\/a> Even more surprising was John Mueller&#8217;s explanation: Google had realized it hadn&#8217;t been using the tags for indexing for years, so it removed the documentation.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.seroundtable.com\/google-rel-prev-next-change-27295.html\" target=\"_blank\" rel=\"noopener\">Search Engine Roundtable<\/a> Mueller said that because Google indexes pages as it finds them, each page needs to be able to stand on its own, and that since the tags had gone unused for so long, most sites seemed to be paginating in reasonable ways regardless of these links.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.seroundtable.com\/googles-advice-on-pagination-page-series-post-rel-next-and-rel-prev-27297.html\" target=\"_blank\" rel=\"noopener\">Search Engine Roundtable<\/a><\/p>\n<p class=\"wp-block-paragraph\">The tags have not become useless. Bing&#8217;s Fr\u00e9d\u00e9ric Dubut said Bing uses rel=prev\/next as hints for page discovery and understanding site structure, but not for merging pages in the index or for ranking.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.seroundtable.com\/how-bing-uses-rel-next-and-rel-prev-27298.html\" target=\"_blank\" rel=\"noopener\">Search Engine Roundtable<\/a> In the HTML standard, next also lives on, meaning the current document is part of a series and the referenced document is the next one in that series.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/html.spec.whatwg.org\/multipage\/links.html#link-type-next\" target=\"_blank\" rel=\"noopener\">HTML Standard<\/a> So Ahrefs recommends leaving existing rel=prev\/next tags in place. There is no reason to change them, and touching them is likely to do more harm than good.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/rel-prev-next-pagination\/\" target=\"_blank\" rel=\"noopener\">Ahrefs<\/a><\/p>\n<h2 class=\"wp-block-heading\">Canonicalizing page 2 to page 1 strands your content<\/h2>\n<p class=\"wp-block-paragraph\">A common wrong answer after the retirement news was to point the <a href=\"\/en\/seo-glossary\/canonical-tag\/\">canonical tags<\/a> of page 2 onward all to page 1. Ahrefs names this as the first mistake, noting that after the announcement more sites changed their implementation and ended up hurting themselves.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/rel-prev-next-pagination\/\" target=\"_blank\" rel=\"noopener\">Ahrefs<\/a> Mueller had already said in February 2019, before the retirement announcement, that this was the main thing to avoid, because page 2 does not have the same content as page 1.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.searchenginejournal.com\/pagination-seo\/295627\/\" target=\"_blank\" rel=\"noopener\">Search Engine Journal<\/a> What happens if Google accepts that canonical? As Ahrefs explains, the crawl paths to the other pages are cut, and content linked only from those pages is stranded.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/rel-prev-next-pagination\/\" target=\"_blank\" rel=\"noopener\">Ahrefs<\/a> If 100 products are split across 10 pages and Google knows only page 1, then 90 of them have effectively been erased from the map.<\/p>\n<p class=\"wp-block-paragraph\">Semrush gives the same advice. Each page in a paginated series should have a canonical tag pointing to itself, indicating that it is a unique page.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.semrush.com\/blog\/pagination-seo\/\" target=\"_blank\" rel=\"noopener\">Semrush<\/a> If your system outputs unique URLs like \/page\/2\/ and regular links by default, as WordPress does, the unique URL and link requirements are already met. However, WordPress core outputs canonicals only for single posts, so check the canonical for page 2 in your SEO plugin settings.<\/p>\n<h2 class=\"wp-block-heading\">noindex is not forbidden, but it is a trade-off<\/h2>\n<p class=\"wp-block-paragraph\">Should you noindex page 2 onward? Google&#8217;s answer depends on the situation. Mueller said not to think of paginated pages as having special SEO elements, but to ask whether it would be okay if someone saw only this page on your site, and to noindex it if not.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.seroundtable.com\/google-on-pagination-indexing-31018.html\" target=\"_blank\" rel=\"noopener\">Search Engine Roundtable<\/a> In 2019, in a similar discussion on Reddit, he answered to ask whether the page sparks joy and to noindex it if not, and added that if your site has only a few such series, don&#8217;t worry and let them be indexed normally.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.searchenginejournal.com\/pagination-seo\/295627\/\" target=\"_blank\" rel=\"noopener\">Search Engine Journal<\/a><\/p>\n<p class=\"wp-block-paragraph\">But noindex comes at a cost. Mueller explained that if noindex stays in place for a long time, Google removes the page from the index completely and stops following its links too.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.seroundtable.com\/google-long-term-noindex-follow-24990.html\" target=\"_blank\" rel=\"noopener\">Search Engine Roundtable<\/a> Ahrefs sums up that adding noindex removes the page from the index so it can&#8217;t rank, and PageRank (the strength passed through links) is no longer passed on. It also warns that blocking crawling with robots.txt makes content harder to discover, strands pages and cuts off the flow of PageRank.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/rel-prev-next-pagination\/\" target=\"_blank\" rel=\"noopener\">Ahrefs<\/a> Semrush advises against noindex because link equity stops flowing and discovery of new content through pagination links may be blocked.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.semrush.com\/blog\/pagination-seo\/\" target=\"_blank\" rel=\"noopener\">Semrush<\/a> In short, even if page 2 itself isn&#8217;t worth showing in search, if some products or posts are linked only from that page, noindex is a switch that also turns off the strength of those links.<\/p>\n<h2 class=\"wp-block-heading\">The farther from the home page, the less important Google considers it<\/h2>\n<p class=\"wp-block-paragraph\">How many clicks from the home page is page 250 of a 300-page list? Mueller explained that the home page is the most important, things linked from the home page are generally important too, and the farther a page is from the home page, the less important Google tends to consider it.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.searchenginejournal.com\/pagination-seo-2\/352386\/\" target=\"_blank\" rel=\"noopener\">Search Engine Journal<\/a> So his recommendation was to reduce the number of pages: cross-link by category or tag to create several series of just a few pages each by type, and maintain a balanced hierarchy that is neither too flat nor too deep.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.searchenginejournal.com\/pagination-seo-2\/352386\/\" target=\"_blank\" rel=\"noopener\">Search Engine Journal<\/a> In other words, 30 categories of 10 pages each is better than 300 pages in a single line. This is also a matter of <a href=\"\/en\/seo-glossary\/internal-link\/\">internal link<\/a> design and <a href=\"\/en\/seo-glossary\/crawl-budget\/\">crawl budget<\/a>.<\/p>\n<h2 class=\"wp-block-heading\">Filter and sort pages are a different problem<\/h2>\n<p class=\"wp-block-paragraph\">Sort URLs (by price, by popularity) and filter URLs (by color, by size) are often confused with pagination. What Google&#8217;s documentation recommends handling with a noindex meta tag or robots.txt is these variant URLs, not page numbers. To keep variants of the same result list from being indexed, it advises blocking unwanted URLs with noindex or using robots.txt to discourage crawling of particular URL patterns.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/ecommerce\/pagination-and-incremental-page-loading\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> If you treat page 2 and sort variants as one group and block both, you get exactly the stranding problem described above.<\/p>\n<h2 class=\"wp-block-heading\">Common traps on Korean sites<\/h2>\n<p class=\"wp-block-paragraph\">Some Korean e-commerce platforms and bulletin board templates handle page numbers with JavaScript functions, so the links have no href or only a #. Others have only a load more button and no regular page links. As explained above, Googlebot doesn&#8217;t click buttons and ignores what comes after #, so in lists like these, products and posts beyond page 1 may never be discovered by Google. The quickest check is whether you can right-click a page number in the list and open it in a new tab, and whether the URL in the address bar changes for each page.<\/p>\n<p class=\"wp-block-paragraph\">Long articles split across multiple pages follow the same rules. If each page has a unique URL and the pages are connected by regular links, Google indexes each page separately. As Google says, users prefer single-page content, so unless there is a real reason to split it, keeping it on one page is simpler.<\/p>\n<h2 class=\"wp-block-heading\">References<\/h2>\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/ecommerce\/pagination-and-incremental-page-loading\" target=\"_blank\" rel=\"noopener\">Pagination, incremental page loading, and their impact on Google Search &#8211; Google Search Central<\/a><\/li><li><a href=\"https:\/\/www.seroundtable.com\/google-rel-prev-next-change-27295.html\" target=\"_blank\" rel=\"noopener\">Google: Rel=prev\/next Is Not An Indexing Signal Anymore; Help Docs Removed &#8211; Search Engine Roundtable<\/a><\/li><li><a href=\"https:\/\/www.seroundtable.com\/how-bing-uses-rel-next-and-rel-prev-27298.html\" target=\"_blank\" rel=\"noopener\">Bing Uses rel=next and rel=prev For Discovery But Not Merging Pages &#8211; Search Engine Roundtable<\/a><\/li><li><a href=\"https:\/\/html.spec.whatwg.org\/multipage\/links.html#link-type-next\" target=\"_blank\" rel=\"noopener\">HTML Living Standard, Link types next and prev &#8211; WHATWG<\/a><\/li><li><a href=\"https:\/\/www.seroundtable.com\/google-pagination-solution-14037.html\" target=\"_blank\" rel=\"noopener\">Google To Solve Pagination SEO Issue: Google&#8217;s three options in 2011 &#8211; Search Engine Roundtable<\/a><\/li><li><a href=\"https:\/\/www.searchenginejournal.com\/pagination-seo\/295627\/\" target=\"_blank\" rel=\"noopener\">Google Shares Guidance on Pagination for SEO &#8211; Search Engine Journal<\/a><\/li><li><a href=\"https:\/\/www.seroundtable.com\/google-on-pagination-indexing-31018.html\" target=\"_blank\" rel=\"noopener\">Google On Pagination: Would It Be Okay If The Page Was Only Accessible Via Your Site &#8211; Search Engine Roundtable<\/a><\/li><li><a href=\"https:\/\/ahrefs.com\/blog\/rel-prev-next-pagination\/\" target=\"_blank\" rel=\"noopener\">SEOs Are Breaking Pagination After Google Changed Rel=Prev\/Next, Here&#8217;s How to Get It Right &#8211; Ahrefs<\/a><\/li><\/ul>","protected":false},"excerpt":{"rendered":"<p>Pagination is the practice of splitting a long list or article into multiple pages, such as page 1 and page 2. Google says to give each page a unique URL and include a regular link to the next page, and it advises against pointing page 2 onward to page 1 as the canonical. In 2019, Google announced that it no longer uses rel=next\/prev, which it once recommended.<\/p>\n","protected":false},"template":"","glossary_categories":[21],"class_list":["post-284","seo_glossary","type-seo_glossary","status-publish","hentry","glossary_categories-technical"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/284","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary"}],"about":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/types\/seo_glossary"}],"version-history":[{"count":1,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/284\/revisions"}],"predecessor-version":[{"id":2369,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/284\/revisions\/2369"}],"wp:attachment":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/media?parent=284"}],"wp:term":[{"taxonomy":"glossary_categories","embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/glossary_categories?post=284"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}