How To Implement Pagination Properly? Important and Urgent!
-
I have seen many instructions but I am still uncertain. Here is the situation
We will be implementing rel prev rel next on our paginted pages.
The question is:
- Do we implement self referencing canonical URL on the main page and each paginated page?
- Do we implement noindex/follow meta robots tag on each paginated page?
- Do we include the canonical URL for each paginated page in the sitemap if we do not add the meta robots tag?
- We have a view all but will not be using it due to page load capabilities...what do we do with the viewl all URL? Do we add meta robots to it?
- For website search results pages containing pagination should we just put a noindex/follow meta robots tag on them?
- We have seperate mobile URL's that also contain pagination. Do we need to consider these pages as a seperate pagination project? We already canonical all the mobile URL's to the main page of the desktop URL.
Thanks!
-
Hello SEO32,
I apologize for the delayed response. There are several good questions here. They're also complicated questions, which don't really always have a single "correct" answer. So much revolves around the specific situation, and without seeing your website it is difficult to say what is best for you. Also, much of what we think we know about this kind of stuff is either based on what Google tells us (which isn't always the truth) and what we've observed and deduced from our own experiences (which aren't always the same). True "testing" of this stuff one variable at a time isn't always possible so we rely on best practices and our own experience.
That said, I will attempt to answer your questions with what I would probably do in most situations, including links to more information when possible.
Do we implement self referencing canonical URL on the main page and each paginated page?
Here's what Rand says, and he's probably seen way more data than I have:
"Whatever you do, DO NOT:
- Put a rel=canonical directive on paginated results pointing back to the top page in an attempt to flow link juice to that URL. You'll either misdirect the engines into thinking you have only a single page of results or convince them that your directives aren't worth following (as they find clearly unique content on those pages).
- Add nofollow to the paginated links on the results pages. This tells the engines not to flow link juice/votes/authority down into the results pages that desperately need those votes to help them get indexed and pass value to the deeper pages.
- Create a conditional redirect so that when search engines request paginated results, they 301 redirect or meta refresh back to the top page of results."
Keep in mind that post is from 2010, and I think before Google said a "View All" canonical <a>was their preference</a>.
I have seen plenty of sites do well ranking the canonical category page, and with indexing most of the product pages, while all paginated pages had a rel canonical that referenced the first page in the series (i.e. .com/category/ or .com/categry1/category2/). It probably helps that they had good XML sitemaps for product pages, and plenty of internal linking, unique content on category pages, etc.
I have also seen sites do well using rel next/prev without rel canonical, or rel next/prev with self-referencing canonicals on paginated category pages.
I think where you run into problems is when you also allow the facet/filter/sort versions to have self-referencing rel canonical tags.
Here is what I advise in most cases:
Use rel next/prev (not because I think it works, but because Google says to and I don't think it hurts) along with self-referencing rel canonical tags, and "follow,noindex" robots meta tags on paginated pages.
Always include a followable link to the first page in the series from every subsequent page. For example:
<previous>first...1...25...26...27...last...</previous>
I recommend always having a first and last page link. The first is obvious because it means pagerank is going to flow into it from every other page in the set, giving it the most internal links of all. The last is more of a crawlability and usability thing. For users it helps us figure out how much further we have to go. It does the same thing for search engines. Instead of blindly following a path that may or may not have an end, a message is sent that tells a spider how much further it has to go. I don't know if Google takes advantage of that signal or not, but it just makes sense to include it. If you want to get fancy you can try making the 'last' link flash or javascript or something so it doesn't pass (as much?) page rank.
The category root pages usually have links from site-wide navigation, unlike the paginated versions, which further establishes it as the page that should be ranked highest.
Make sure the first page in each series is indexable, and has content that does not appear on the paginated versions. Also, make sure that ?p=1 doesn't have a self-referencing canonical tag, but references the root page for that series (e.g. /category1/category2/).
All subsequent variations (e.g. color, size) should rel canonical back to their root page. For example:
/category1/category2/?page=2&size=s&color=blue would have the following URL in the rel canonical tag:
/category1/category2/?page=2
Which happens to be followable, but not-indexable, and has a self-referencing rel canonical tag.In this way you give search engines a strong signal about which URL in the whole set is the strongest (i.e. /category1/category2/) because it is indexable, has its own content, has the most internal and external links, is the simplest version of this URL pattern, and is at the root of the directory. You're telling search engines which page is next in the series, and that this page is first in the series. You're telling search engines which page is last in the series, as well. Google usually does an awesome job figuring it out from there. There are always exceptions.
Do we implement noindex/follow meta robots tag on each paginated page?
I would. Consider this from Google's perspective, or from that of a searcher. Someone types "Blue Flower Dress" into Google. Is the best page to return a deep category page full of blue dresses, one of which happens to have flowers? Or would it be the Blue Flower Dress product page? I can't think of any reason why I would want to land on page 3, where what I'm looking for is listed among dozens of other things, when I could just go straight to the thing I'm looking for.
Likewise, if someone searches for "Blue Dresses" is the best page /dresses/blue/?page=3 (paginated page in the Blue Dresses category), OR /dresses/blue/ (the very first page of the Blue Dresses category), which also has useful content about blue dresses?
Long story short, when it comes to transactional eCommerce queries, they're usually either looking for a product page or the first page of a specific category or sub-category. Or sometimes the home page. Therefore, I don't see any reason for allowing paginated URLs to be indexable in most cases. Non-transactional eCommerce content is different (e.g. buying guides, comparison charts, reviews...) but I still wouldn't allow paginated pages to be indexed in most cases.
Slightly Off Topic - Filters/Facets/Sorts
Or perhaps the category is "casual dresses" and "blue" is specified in the "color" attribute. In this case, would the best page be /dresses/casual/?color=blue , /dresses/casual/ or /dresses/casual/?color=blue&page=4 for someone who Googled "blue dresses"? I've bolded the one I'd prefer as a searcher.
Here again, as with the internal search results, there is an opportunity to use real data to inform your decision. Pay attention to the facet/filter/sort URLs most accessed by shoppers and consider turning those into category or collections pages with their own URL pattern (e.g. /dresses/casual/blue/). One example I come across all the time is when "Brand" is a filter instead of its own limb in the category structure. If people are shopping by brand, as they do with most consumer products, then you should have a brand subcategory under each major top-level category. If I search for Levi Jeans Google doesn't want to send me to a "pants" page where I have to set a filter to see only Levis. I should go to pants/brand/levi/ . If I Google Chefmate Pots I want to see cookware/pots/brands/chefmate so I don't have to set a filter after I get there.
This doesn't mean all filter pages should be turned into category pages either. Use your best judgement based on the pages most of your users are accessing from the navigation and filters.
Do we include the canonical URL for each paginated page in the sitemap if we do not add the meta robots tag?
I would add the robots meta tag. Please let me know if I've misunderstood the question.
We have a view all but will not be using it due to page load capabilities...what do we do with the view-all URL? Do we add meta robots to it?
I would add a meta robots "index,nofollow" tag, and would also use the canonical page's URL (e.g. /category1/category2) in the rel canonical tag.
For website search results pages containing pagination should we just put a noindex/follow meta robots tag on them?
This is one of those situations involving crawl budget potentially being eaten up by an infinite amount of pages. I would consider blocking the internal search result URLs in the robots.txt file. They are of no use to Google, as they consider a search engine returning search results with links to more search results somewhere else a bad user experience. This is also what Google recommends in their Webmaster Guidelines:
"Use robots.txt to prevent crawling of search results pages or other auto-generated pages that don't add much value for users coming from search engines."
However, I would also make use of those pages internally. Rather than relying on a search result page for things people often look for, track what is being searched for and create static, indexable pages. For example, try "Collections" pages on eCommerce sites, as well as FAQ pages, or "Industries" or "Use Case"-type pages on lead generation sites. This is a much better user experience for someone arriving on that page from a search engine.
We have separate mobile URL's that also contain pagination. Do we need to consider these pages as a separate pagination project? We already canonical all the mobile URL's to the main page of the desktop URL.
I think you should if that's the way you're handling it. Here is a post I did on mobile best practices. It covers some other options. I would also add a rel=”alternate” tag in the HTML header of the desktop page, which alerts search engines to the corresponding mobile URL and helps define the relationship between the two pages.
The bottom line for me is to always think about what would be the best experience for someone searching from Google for something, and to try and use all of the various technical options to ensure that is the page I'm telling Google they should rank for that query, or those types of queries. The 'best practice' changes, depending on the situation.
I hope others will join the discussion with their own experiences and findings.
-
Hi,
Please check this moz article on this @ SEO Guide to Google Webmaster Recommendations for Pagination
Hope this helps you.
Thanks
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Pagination & duplicate meta
Hi I have a few pages flagged for duplicate meta e.g.: http://www.key.co.uk/en/key/workbenches?page=2
Intermediate & Advanced SEO | | BeckyKey
http://www.key.co.uk/en/key/workbenches I can;t see anything wrong with the pagination & other pages have the same code, but aren't flagged for duplicate: http://www.key.co.uk/en/key/coshh-cabinets http://www.key.co.uk/en/key/coshh-cabinets?page=2 I can't see to find the issue - any ideas? Becky0 -
Are these Magento security concerns urgent?
Hey Mozzers! I recently started working with a new Magento programmer for our ecommerce site. He sent me this scan/report outlining some security issues that need to be addressed. This is a new partnership so I'm not sure which issues should be a major concern, or if I should not focus on them. Would you be able to give me your opinion on the importance of the security issues? https://www.magereport.com/scan/?s=http://metallumcreations.com/
Intermediate & Advanced SEO | | localwork0 -
Solving pagination issues for e-commerce
I would like to ask about a technical SEO issue that may cause duplicate content/crawling issues. For pagination, how the rel=canonical, rel="prev" rel="next" and noindex tag should be implemented. Should all three be within the same page source? Say for example, for one particular category we may have 10 pages of products (product catalogues). So we should noindex page 2 onwards, rel canonical it back to the first page and also rel="prev" and rel="next" each page so Google can understand they contain multiple pages. If we index these multiple pages it will cause duplicate content issues. But I'm not sure whether all 3 tags need adding. It's also my understanding that the search results should be noindexed as it does not provide much value as an entry point in search engines.
Intermediate & Advanced SEO | | Jseddon920 -
Pagination, Canonical, Prev & Next
Hello All
Intermediate & Advanced SEO | | Vitalized
I have a question about my Magento setup. I have lots of categories which have many products so the categories paginate. I've seen info about making sure the Canonical tag doesn't simply send Search Engines back to the first page meaning the paginated pages won't get indexed. I've also seen info about using the rel=next & rel=prev to help Search Engines understand the category pages are paginated... Is it okay to use both? I've made sure that: category/?p=1 has a canonical of category/ to make sure there isn't duplicate content. Here's an example of category/?p=2 meta data:
http://website.com/category/?p=2" />
http://website.com/category/" />
http://website.com/category/?p=3" />0 -
Should I use selected Keywords in Meta Title of non important pages
Hi All, I have identified 2 main keywords that I want a website to be found for 1: Alarm Systems 2: Security Systems I have two relevant landing pages set up and optimised for these terms and I have also optimised the home page for these terms I have countless other pages on the website that I don't really need to optimise such as Distributor Benefits or Supplier Benefits, About Us etc My question is should I use my selected keywords (alarm systems, security systems) in the Meta Title on these non important pages or should I just use them on the selected landing pages and home page? Historically I have used my primary keywords on all non important pages but not sure if Google looks down on this now. Thanks Robbie
Intermediate & Advanced SEO | | daracreative0 -
Bing flags multiple H1's as an issue of high importance--any case studies?
Going through Bing's SEO Analyzer and found that Bing thinks having multiple H1's on a page is an issue. It's going to be quite a bit of work to remove the H1 tags from various pages. Do you think this is a major issue or not? Does anyone know of any case studies / interviews to show that fixing this will lead to improvement?
Intermediate & Advanced SEO | | nicole.healthline0 -
Implementing Canonicals on Existing ASP Ecommerce Store with Pagination
So I have a store which has been around for a while and is custom built on ASP.net. Store has thousands of sku's and at least a few hundred subcategories. Have been tackling a bunch of the onsite issues and for categories which have more than 6 products in them, there are multiple pages and a view all present. Example.com/category example.com/category?PageIndex=2 example.com/category?PageIndex=3 example.com/category?PageIndex=4 example.com/category?viewall=True As well as the following for every page example.com/category?PageIndex=2&viewall=True So I know how I wish to handle the pagination/canoncial issue as per google's suggestions you do it to the view all or they have the rel=next/prev. But my question is google says if view all is present they should already do a good job at ranking the view all version. Well in the rankings, there are a lot of page1 variations showing. So once this is implementated, is it safe to assume that I will see a drop? Feel like if it was a brand new site it is easy but for something this old and established, it could cause some decent harm which at the current time we are already tackling a massive list of issues which in the long haul will improve it. Looking for some insight for someone who has dealt with ASP.net and this specific area. thanks
Intermediate & Advanced SEO | | Sean_Dawes
Sean0 -
Adding rel=next / prev to pagination that uses Ajax?
Hi I have just been informed that I should be using the rel=next / rel=prev markup on my category pages and search results pages that use pagination. How do i add these in? Is it just the simple case of adding rel=next in the<a href="" for="" item="" in="" the="" pagination?<="" p=""></a> <a href="" for="" item="" in="" the="" pagination?<="" p="">Also does this work if your are using AJAX - on page load it displays the search / category pages then uses AJAX for additional pages so there is no page refresh</a> <a href="" for="" item="" in="" the="" pagination?<="" p="">Many Thanks</a>
Intermediate & Advanced SEO | | ocelot0