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
-
Page 1 Reached, Further Page Improvements and What Next ?
Moz, I have a particularly tricky competitive keyword that i have finally climbed our website to the 10th position of page 1, i am particularly pleased about this as all of the website and content is German which i have little understanding of and i have little support on this, I am pleased with the content and layout of the page and i am monitoring all Google Analytics values very closely, as well as the SERP positions, So as far as further progression with this page and hopefully climbing further up page 1, where do you think i should focus my efforts ? Page Speed optimization?, Building links to this page ?, blogging on this topic (with links) , Mobile responsive design (More difficult), further improvements to pages and content linked from this page ? Further improvements to the website in general?,further effort on tracking visitors and user experience monitoring (Like setting up Crazyegg or something?) Any other ideas would be greatly appreciated, Thanks all, James
Intermediate & Advanced SEO | | Antony_Towle0 -
How long takes to a page show up in Google results after removing noindex from a page?
Hi folks, A client of mine created a new page and used meta robots noindex to not show the page while they are not ready to launch it. The problem is that somehow Google "crawled" the page and now, after removing the meta robots noindex, the page does not show up in the results. We've tried to crawl it using Fetch as Googlebot, and then submit it using the button that appears. We've included the page in sitemap.xml and also used the old Google submit new page URL https://www.google.com/webmasters/tools/submit-url Does anyone know how long will it take for Google to show the page AFTER removing meta robots noindex from the page? Any reliable references of the statement? I did not find any Google video/post about this. I know that in some days it will appear but I'd like to have a good reference for the future. Thanks.
Intermediate & Advanced SEO | | fabioricotta-840380 -
My home page is not found by the "Grade a Page" tool
My home page as well as several important pages are not found by the Grade a Page tool. With our full https address I got this http://screencast.com/t/s1gESMlGwpa With just the www address I got this http://screencast.com/t/BMRHy36Ih https://www.joomlashack.com
Intermediate & Advanced SEO | | etabush
https://www.joomlashack.com/joomla-templates We recently lost a lot of positions for our most important keyword: Joomla Templates Please help us figure this out. Whats screwy with our site?0 -
Is it ok to add rel=CANONICAL into the desktop version on top of the rel="alternate" Tag (Mobile vs Desktop version)
Hi mozzers, We launched a mobile site a couples months ago following the parallel mobile structure with a URL:m.example.com The week later my moz crawl detected thousands of dups which I resolved by implementing canonical tags on the mobile version and rel=alternate onto the desktop version. The problem here is that I still also got Dups from that got generated by the CMS. ?device=mobile ?device=desktop One of the options to resolve those is to add canonicals on the desktop versions as well on top of the rel=alternate tag we just implemented. So my question here: is it dangerous to add rel=canonical and rel=alternate tags on the desktop version of the site or not? will it disrupt the rel=canonical on mobile? Thanks
Intermediate & Advanced SEO | | Ideas-Money-Art0 -
Ecommerce: remove duplicate product pages or use rel=canonical
Say we have a white-widget that is in our white widget collection and also in our wedding widget collection. Currently, we have 3 different URLs for that product (white-widgets/white-widget and wedding-widgets/white-widget and all-widgets/white-widget).We are automatically generating a rel=canonical tag for those individual collection product pages that canonical the original product page (/all-widgets/white-widget). This guide says that is the structure Zappos uses and says "There is an elegance to this approach. However, I would re-visit it today in light of changes in the SEO world."
Intermediate & Advanced SEO | | birchlore
I noticed that Zappos, and many other shops now actually just link back to the parent product page (e.g. If I am in wedding widget section and click on the widget, I go to all-products/white-widget instead of wedding-widgets/white-widget).So my question is:Should we even have these individual product URLs or just get rid of them altogether? My original thought was that it would help SEO for search term "white wedding widget" to have a product URL wedding-widget/white-widget but we won't even be taking advantage of that by using rel=canonical anyway.0 -
What constitutes a duplicate page?
Hi, I have a question about duplicate page content and wondered if someone is able to shed some light on what actually constitutes a "duplicate". We publish hundreds of bus timetable pages that have similar, but technically with unique urls and content. For example http://www.intercity.co.nz/travel-info/timetable/lookup/akl The template of the page is oblivious duplicated, but the vast majority of the content is unique to each page, with data being refreshed each night. Our crawl shows these as duplicate page errors, but is this just a generalisation because the urls are very similar? (only the last three characters change for each page - in this case /akl) Thanks in advance.
Intermediate & Advanced SEO | | BusBoyNZ0 -
Rel=canonical on image pages
Hi, Im working on a Wordpress hosted blog site. I recently did a "site:search" in Google for a specific article page to make sure it was getting crawled, and it returned three separate URLs in the search results. One was the article page, and the other two were the URLs that hosted the images that are found in the article. Would you suggest adding the rel=canonical tag to the pages that host the images so they point back to the actual context article page? Or are they fine being left alone? Thank you!
Intermediate & Advanced SEO | | dbfrench0 -
What to do if the wrong page is ranking?
What to do if the wrong page of your website is ranking and you cannot 301 it? Apparently an outsourced company the previous manager hired build anchor text links to the homepage, when those links should have been pointing to a deeper page. As a result, the hompage is now ranking for that term. But I think we can convert a lot more of the visitors if the deeper page is there instead. Obviously, I can't 301 the homepage. What would you do?
Intermediate & Advanced SEO | | andrep0