Rel Next and Previous on Listing Pages of Blog
-
Hi,
Need to know does rel next and previous is more appropriate for content based articles and not blog listings.. Like an article spread across 3 pages - there it makes sense for rel next and previous as the content of the article is in series
However, for blog listing page, for pages 1, 2, 3, 4 where every page is unique as the blog has all independent listings or separate articles - does rel next and previous wont of much help
Our blog - http://www.mycarhelpline.com/index.php?option=com_easyblog&view=latest&Itemid=91
This is what been said by the developer
"The whole idea of adding the "next" and "previous" tag in the header is only when your single blog post has permalinks like:
site.com/blog/entry/blog-post.html
site.com/blog/entry/blog-post.html?page=1
site.com/blog/entry/blog-post.html?page=2 "The link in the head is only applicable when your content is separated into multiple pages and it doesn't actually apply on listings. If you have a single blog post that is broken down to multiple pages, this is applicable and it works similarly like rel="canonical"
Can we safely ignore rel next and previous tag for this blog pagination for the listing pages !!
-
My gut feeling is that that's not really worth worrying about right now - 10 pages of paginated blog post summaries can easily be crawled and indexed and isn't going to dilute your index. Where we usually see problems on blogs is if you have a log of categories/sub-categories, including tags. Some sites with 100 articles end up with 300 pages of search results, because they have 50 tags, etc. That can end up looking thin fast. Ten pages of results is nothing, IMO.
-
Thanks Dr Peter for the insights
We were just wondering that - due to blog posts (96 articles) spread across 10 pages - does the listing rel next and previous should be applied on the pagination listing page.. With our current speed - may be we will additionally write 100 - 120 articles in a year
With your answer and recommendation and basis the current size of the blog along with future posts :-
-
we are ignoring the rel next and previous parameter for the blog
-
Neither are we applying any kind of noindex, follow too
Many thanks !!
-
-
Thanks Dr. Pete.
Just to clarify, I would typically not use rel/next prev on any sort keyword search result pages etc as I am keeping those totally out of the index. For my 2 cents, it is not just that they are thin, but they are a waste of time in helping Google find my deep content. You end up with potentially an infinite number of pages (due to the nature of kw queries) that are not worth the time to crawl. I have /search/ behind robots.txt for that matter. I depend more on other tools such as my XML sitemap and one set of paginated pages using rel=prev/next to help Google in discovering content.
We are testing rel=prev/next on one site I manage. I have about 3400 pages of content and over 130 paginated pages to let users and spiders browse the content in chronological order. Just a simple "browse our archives" type of pages. We set this up with prev/next and did not implement the noindex meta (based on the citations above). Overall we have not seen any negative effects from doing this. I would bet that if someone is using rel=next/prev on KW search results that could be resorted and filtered, that would cause the spiders to get confused.
Cheers!
-
While rel=prev/next was originally designed for paginated content, it is appropriate for search results as well. While you're right - they are technically unique - search results tend to have similar (or the same) title tags, similar templates, etc., and are often considered thin by Google.
Truthfully, the data on how well rel=prev/next works seems very mixed. I know mega-site SEOs who still haven't decided how they feel about it. Google's official advice is often conflicting, I've found, on this topic. As @CleverPHD said, Adam Audette has some good material on the subject.
It all comes down to scope. If your blog has a few dozen search pages, and hundreds of posts and other content, I wouldn't worry about it much. This is often more appropriate for e-commerce sites where search results may have filters and sorts and could spin out hundreds or thousands of URLs.
-
Hi Gagan,
I think Irving only suggested using noindex on the additional pages if those pages do not have any index value. As you mention, you feel they do have index value and so you do not want to use noindex on them. I would agree with that
There is an article by Adam Audette, that quotes Maile Ohye from Google
http://searchengineland.com/the-latest-greatest-on-seo-pagination-114284
"However, using rel next/prev doesn’t prevent a component page from displaying in search results. So while these pages will “roll up” to the canonical (or default) page 1, they could still fire at search time if the query was relevant for that specific page.
At SMX West, Maile assured us that it would be a very rare thing for that situation to occur. But it could occur. Because of this, an additional recommendation (strictly as an optional step) is to add a robots noindex, follow to the rel prev/next component pages. This would ensure that component pages would never fire at search time."
More input from Maile Ohye
http://productforums.google.com/forum/#!topic/webmasters/YbXqwoyooGM
Maile Ohye is responding to various questions on pagination.
"@TheDonald, @jerenel: If you've marked page 2 to n of your paginated series as "noindex, follow" to keep low quality content from affecting users and/or your site's rankings, that's fine, you can additionally include rel="next" and rel="prev." Noindex and rel="next"/"prev" are entirely independent annotations.
This means that if you add rel="next" and rel="prev" to noindex'd pages, it still signals to Google that the noindex'd pages are components of the series (though the noindex'd pages will not be returned in search results). This configuration is totally possible (and we'll honor it), but the benefit is mostly theoretical."
I think the key here is that if you have a section of your site that links to all of your blog postings and it is paginated, I would let Google crawl those, use rel next prev and do not use the noindex tag on pages 2-n. I always want to provide Google with a simple crawlable path of all of my content. But Google only needs that one path! Don't distract the Google! Any other versions of the path (i.e. re-sorts of the pagination based on date, or keyword search etc) I hide all of that from Google using noindex/nofollow or robots.txt where appropriate, as Google does not need to waste time browsing those duplicative pages.
Good luck!
-
Thanks, but why to noindex internal page as every page has unique listings. For rel previous and next - its more apt as a markup when content article is in sequence.
How about the blog listings - where there are listings only. Do you still feel that rel next and previous should be declared in header for blog listings. If yes - may give more reasons too specific to the blog
Also, for Panda Penalty - dint get you much on it .. Does the blog listing if not given markup invite a penalty from the search engines...
Many thanks
-
Your listing pages should definitely have the prev and next tags. These tags were created for pagination. There are other solutions on how deal with pagination, but this is the one that Google recommends . The bigger question for you is if you see value in Google indexing the listing pages and what possible landing page traffic you can expect from these pages. Without much index value, I would suggest adding a noindex, follow tag to your listing pages and avoid a potential Panda penalty.
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
-
Category pages
I am a very basic question on managing categories in WordPress. We have an Android website, and we cover news, rumors, tips and tricks about new devices. We have been creating categories for the new devices or at least for the popular ones which are launched every year, and link to them internally with the hope that it would improve the page authority and ranking. For example, we have a category page for Moto X, another one for Moto X (2014) and one more for Moto X (2015). One of the reasons for creating a category was to ensure that it is easier for readers to get information about a particular device rather than going to a category page that has information about all the models. However, the problem with their strategy we're now realizing is that it means we have to build page authority for the new category page from scratch, which can take time. So we are thinking of reusing the same category for multiple models. So reuse the Moto X category page for Moto X (2016). However, we are not sure if it would be right approach as we would be linking to the same category page with different anchor texts. So while it would be good to reuse a page rather than rebuild the page authority from scratch, would we be diluting the authority for the main keyword by using it for different models. I would love to hear your thoughts on how we should be handling categories and internal links in this case.
Intermediate & Advanced SEO | | Gautam0 -
Duplicate Content Errors new website. How do you know which page to put the rel canonical tag on?
I am having problems with duplicate content. This is a new website and all the pages have the same page and domain rank, the following is an example of the homepage. How do you know which page to use the canonical tag on? http://medresourcesupply.com/index.php http://medresourcesupply.com/ Would this be the correct way to use this? Here is another example where Moz says these are duplicates. I can't figure out why because they have different url's and content. http://medresourcesupply.com/clutching_at_the_throat http://medresourcesupply.com/index.php?src=gendocs&ref=detailed_specfications &category=Main
Intermediate & Advanced SEO | | artscube.biz0 -
I've got duplicate pages. For example, blog/page/2 is the same as author/admin/page/2\. Is this something I should just ignore, or should I create the author/admin/page2 and then 301 redirect?
I'm going through the crawl report and it says I've got duplicate pages. For example, blog/page/2 is the same as author/admin/page/2/ Now, the author/admin/page/2 I can't even find in WordPress, but it is the same thing as blog/page/2 nonetheless. Is this something I should just ignore, or should I create the author/admin/page2 and then 301 redirect it to blog/page/2?
Intermediate & Advanced SEO | | shift-inc0 -
Pagination on a product page with reviews spread out on multiple pages
Our current product pages markup only have the canonical URL on the first page (each page loads more user reviews). Since we don't want to increase load times, we don't currently have a canonical view all product page. Do we need to mark up each subsequent page with its own canonical URL? My understanding was that canonical and rel next prev tags are independent of each other. So that if we mark up the middle pages with a paginated URL, e.g: Product page #1http://www.example.co.uk/Product.aspx?p=2692"/>http://www.example.co.uk/Product.aspx?p=2692&pageid=2" />**Product page #2 **http://www.example.co.uk/Product.aspx?p=2692&pageid=2"/>http://www.example.co.uk/Product.aspx?p=2692" />http://www.example.co.uk/Product.aspx?p=2692&pageid=3" />Would mean that each canonical page would suggest to google another piece of unique content, which this obviously isn't. Is the PREV NEXT able to "override" the canonical and explain to Googlebot that its part of a series? Wouldn't the canonical then be redundant?Thanks
Intermediate & Advanced SEO | | Don340 -
How Should We Best List Events Pages?
Hi everyone! Luke here from CHARGED.fm hoping that a brilliant mind could help me with another annoying (at least for me) technical seo question. It's about how we list the events on our ticketing site. Here's the rundown: We currently list tickets by event id, but our competitors keep the event page in the same silo and use the venue name and date of event in the url. So we do this: http://www.charged.fm/kinky-boots-tickets (disregard redirect for now) List the events where you can choose from these: http://www.charged.fm/event/tickets/2518362/kinky-boots
Intermediate & Advanced SEO | | keL.A.xT.o
http://www.charged.fm/event/tickets/2511448/kinky-boots Moz lists these as duplicate content, so we're wondering how to resolve this. We're also wondering if it would be benficial to keep the events page in the same silo like our competitors: http://www.vividseats.com/theatre/kinky-boots-tickets/kinky-boots-9-20-1537274.html (notice how they go /theatre/kinky-boots-tickets/event/) Would it be beneficial to list like this? Is it inconsequential? Could we leave things the way that they are or should we at least add the venue and date to the events page URL? Thanks a lot for any help,
Luke0 -
Page Rank
Hi guys I have an ecommerce in prestashop (unfortunatelly I can not change it at this moment). I made all main activities both off and on the page. And actually it is working pretty well since I am up on the SERP for all the target keywords. BUT, the page rank still be 0. The site is about 2 years old. My main competitor has the same domain authority than mine, but he has a page rank > 0 Moreover I have more quality links then it has, but it is older Any suggestions? Many thanks Ciao Diego
Intermediate & Advanced SEO | | sbrelax0 -
Too many on page links - product pages
Some of the pages on my client's website have too many on page links because they have lists of all their products. Is there anything I should/could do about this?
Intermediate & Advanced SEO | | AlightAnalytics0 -
Canonical category pages
A couple of years ago I used to receive a lot of traffic via my category pages but now I don't receive as much, in the past year I've modified the category pages to canonical. I have 15 genres for the category pages, other than the most recent sorting there is no sorting available for the users on the cat pages, a recent image link added can over time drop off to page 2 of the category page, for example mysite.com/cat-page1.html = 100 image links per page with numbered page navigation, number of cat pages 1-23. New image link can drop off to page 2. mysite.com/dog-page1.html = 100 image links per page with numbered page navigation, number of cat pages 1-53. New image link can drop off to page 2. mysite.com/turtle-page1.html = 100 image links per page with numbered page navigation, number of cat pages 1-2. New image link can drop off to page 2. Now on the first page (eg mysite.com/cat-page1.html) I've set this up to rel= canonical = mysite.com/cat-page1.html One thing that I have noticed is the unique popup short description tooltips that I have on the image links only appears in google for the first pages of each category page, it seems to ignore the other pages. In view of this am I right in applying canonical ref or just treating it as normal pages.? thanks
Intermediate & Advanced SEO | | Flapjack0