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
-
Duplicate content across similar computer "models" and how to properly handle it.
I run a website that revolves around a niche rugged computer market. There are several "main" models for each computer that also has several (300-400) "sub" models that only vary by specifications for each model. My problem is I can't really consolidate each model to one product page to avoid duplicate content. To have something like a drop down list would be massive and confusing to the customer when they could just search the model they needed. Also I would say 80-90% of the market searches for a specific model when they go to purchase or in Google. A lot of our customers are city government, fire departments, police departments etc. they get a list of approved models and purchase off that they don't really search by specs or "configure" a model so each model number having a chance to rank is important. Currently we have all models in each sub category rel=canonical back to the main category page for that model. Is there a better way to go about this? Example page you can see how there are several models all product descriptions are the same they only vary by model writing a unique description for each one is an unrealistic possibility for us. Any suggestions on this would be appreciated I keep going back on forth on what the correct solution would be.
Intermediate & Advanced SEO | | The_Rugged_Store0 -
Ecommerce SEO: Title Tags for pagination
Here's a specific question about title tags for ecommerce website... We've got lists of products (category list pages) that stretch for many pages... is there any benefit to added a something to make the title tag unique. For example: Page 1: <title></span><span class="html-tag" data-mce-mark="1">Category List Page Example</span><span class="html-tag" data-mce-mark="1"></title> Page 2: <title></span><span class="html-tag" data-mce-mark="1">Category List Page Example - Page 2</span><span class="html-tag" data-mce-mark="1"></title> Page 3: <title></span><span class="html-tag" data-mce-mark="1">Category List Page Example - Page 3</span><span class="html-tag" data-mce-mark="1"></title> FWIW, we've got the pagination and canonicalization nailed down tight. Moz crawl actual brought a dupe content issue based on title tags.
Intermediate & Advanced SEO | | 19prince0 -
How important is the user experience for SEO in google's eyes?
So far I've gathered that backlinks are really king, however you can't get good backlinks without well written content that serves a purpose. As well you can't do a great job with that content and not keep a good user experience, since why would anyone want to backlink to content that can be helpful if you squint an eye and suffer a few scrolling cramps. So how would you rank user experience in the everlasting war of SEO for Google? With this in mind, why would using bootstrap resources pose a problem? I've seen it could add issue to pageload times, however seems minifying could easily solve that. I personally enjoy the use of Bootstrap since it's very easy on the eyes and can have real positive effects when a user looks at content on such a framework.
Intermediate & Advanced SEO | | Deacyde0 -
How important is the optional <priority>tag in an XML sitemap of your website? Can this help search engines understand the hierarchy of a website?</priority>
Can the <priority>tag be used to tell search engines the hierarchy of a site or should it be used to let search engines know which priority to we want pages to be indexed in?</priority>
Intermediate & Advanced SEO | | mycity4kids0 -
Yoast & rel canonical for paginated Wordpress URLs
Hello, our Wordpress blog at http://www.jobs.ca/career-resources has a rel canonical issue since we added pagination to the front page and category-pages. We're using Yoast and it's incorrectly applying a rel-canonical meta tag referencing page 1 on page 2, 3, etc. This is a known misuse of the rel-canonical tag (per Google's Webmaster Blog - http://googlewebmastercentral.blogspot.ca/2013/04/5-common-mistakes-with-relcanonical.html, which says rel-canonical should be replaced with rel-prev and rel-next for page 2, 3, etc.). We don't see a way to specify anywhere in Yoast's options to correct this behaviour for page 2, 3, etc. Yoast allows you to override a page's canonical URL, otherwise it automatically uses the Wordpress permalink. My question is, does anyone know how to configure Yoast to properly replace rel-canonical tags with rel-prev and rel-next for paginated URLs, or do I need to look at another plugin or customize the behavior directly in my child theme code? This issue was brought up here as well: http://moz.com/community/q/canonical-help, but the only response did not relate to Yoast. (We're using Wordpress 3.6.1 and Yoast "Wordpress SEO" 1.4.18)
Intermediate & Advanced SEO | | aactive0 -
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 -
What is the Proper Use of 301 redirects for SEO purposes?
I heard and read from different sources that 301 redirects from aged domains with healthy link profiles is great to boost a sites rank as oppose to building a site around the page and linking it to the domain you want to rank. Whats is the best practice for this strategy? Thanks
Intermediate & Advanced SEO | | junkcars0 -
What are the best way to get a new subdomain ranked properly
Our main site (blog with 700 high quality articles) ranks pretty well and we recently launced a rapidly growing forum (55.000 posts in the first 11 weeks) on a subdomain. What would be a good strategy for ranking the forum quickly
Intermediate & Advanced SEO | | xpd1