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
-
Duplicate Page getting indexed and not the main page!
Main Page: www.domain.com/service
Intermediate & Advanced SEO | | Ishrat-Khan
Duplicate Page: www.domain.com/products-handler.php/?cat=service 1. My page was getting indexed properly in 2015 as: www.domain.com/service
2. Redesigning done in Aug 2016, a new URL pattern surfaced for my pages with parameter "products-handler"
3. One of my product landing pages had got 301-permanent redirected on the "products-handler" page
MAIN PAGE: www.domain.com/service GETTING REDIRECTED TO: www.domain.com/products-handler.php/?cat=service
4. This redirection was appearing until Nov 2016.
5. I took over the website in 2017, the main page was getting indexed and deindexed on and off.
6. This June it suddenly started showing an index of this page "domain.com/products-handler.php/?cat=service"
7. These "products-handler.php" pages were creating sitewide internal duplicacy, hence I blocked them in robots.
8. Then my page (Main Page: www.domain.com/service) got totally off the Google index Q1) What could be the possible reasons for the creation of these pages?
Q2) How can 301 get placed from main to duplicate URL?
Q3) When I have submitted my main URL multiple times in Search Console, why it doesn't get indexed?
Q4) How can I make Google understand that these URLs are not my preferred URLs?
Q5) How can I permanently remove these (products-handler.php) URLs? All the suggestions and discussions are welcome! Thanks in advance! 🙂0 -
How do we decide which pages to index/de-index? Help for a 250k page site
At Siftery (siftery.com) we have about 250k pages, most of them reflected in our sitemap. Though after submitting a sitemap we started seeing an increase in the number of pages Google indexed, in the past few weeks progress has slowed to a crawl at about 80k pages, and in fact has been coming down very marginally. Due to the nature of the site, a lot of the pages on the site likely look very similar to search engines. We've also broken down our sitemap into an index, so we know that most of the indexation problems are coming from a particular type of page (company profiles). Given these facts below, what do you recommend we do? Should we de-index all of the pages that are not being picked up by the Google index (and are therefore likely seen as low quality)? There seems to be a school of thought that de-indexing "thin" pages improves the ranking potential of the indexed pages. We have plans for enriching and differentiating the pages that are being picked up as thin (Moz itself picks them up as 'duplicate' pages even though they're not. Thanks for sharing your thoughts and experiences!
Intermediate & Advanced SEO | | ggiaco-siftery0 -
Adding Copy on Inventory Listing Pages
Hi All, We manage a number of auto dealer websites which have their new & used inventory listed on them. There's a separate page for new, used, and CPO inventory, and on most web platforms any filtered inventory subpages are canonicalized back to one of the main inventory pages. Our question is - should we install unique copy on these to-level inventory pages? We're already installing unique meta and H1s and feel like copy could help these rank for more searches but we have a couple hesitations: Most big retailers like Amazon, Zappos, etc don't have copy on these types of pages. Putting the copy above the inventory would distract from shopping behavior, but installing it at the bottom of the page would hurt relevance. We'd appreciate anyone's insight or past experience here! Is it worth taking the time to write unique copy for these pages? Thanks everyone.
Intermediate & Advanced SEO | | ReunionMarketing0 -
Pages with Duplicate Page Content (with and without www)
How can we resolve pages with duplicate page content? With and without www?
Intermediate & Advanced SEO | | directiq
Thanks in advance.0 -
Value in adding rel=next prev when page 2-n are "noindex, follow"?
Category A spans over 20 pages (not possible to create a "view all" because page would get too long). So I have page 1 - 20. Page 1 has unique content whereas page 2-20 of the series does not. I have "noindex, follow" on page 2-20. I also have rel=next prev on the series. Question: Since page 2-20 is "noindex, follow" doesn't that defeat the purpose of rel=next prev? Don't I run the risk of Google thinking "hmmm….this is odd. This website has noindexed page 2-20, yet using rel=next prev." Even though I do not run the risk, what is my upset in keeping rel=next prev when, again, the pages 2-20 are noindex, follow. thank you
Intermediate & Advanced SEO | | khi50 -
Guest blogging??
Hi all! I heard that Google comes down on guest blogging. I did a search here on Moz with the terms "Guest Blogging" and not much comes up, as it relates to my question. So I'm asking: I have a website with specific content where I can implement a "team blog" (stackideas - easyblog), and have industry professionals submit a blog article (once a month on their respective industry focus), and add Google Authorship (link to/from their Google+ profile contributors section), but not allow ANY follow links back to their site. There will be about 10 different blog categories, and there will potentially be several different authors in each category who will be writing specific focused content per category. Any potential Panda (or any other animal 😉 problems with that? Thanks all! BB
Intermediate & Advanced SEO | | BBuck0 -
Redirecting thin content city pages to the state page, 404s or 301s?
I have a large number of thin content city-level pages (possibly 20,000+) that I recently removed from a site. Currently, I have it set up to send a 404 header when any of these removed city-level pages are accessed. But I'm not sending the visitor (or search engine) to a site-wide 404 page. Instead, I'm using PHP to redirect the visitor to the corresponding state-level page for that removed city-level page. Something like: if (this city page should be removed) { header("HTTP/1.0 404 Not Found");
Intermediate & Advanced SEO | | rriot
header("Location:http://example.com/state-level-page")
exit();
} Is it problematic to send a 404 header and still redirect to a category-level page like this? By doing this, I'm sending any visitors to removed pages to the next most relevant page. Does it make more sense to 301 all the removed city-level pages to the state-level page? Also, these removed city-level pages collectively have very little to none inbound links from other sites. I suspect that any inbound links to these removed pages are from low quality scraper-type sites anyway. Thanks in advance!2 -
Duplicate Page Title/Content Issues on Product Review Submission Pages
Hi Everyone, I'm very green to SEO. I have a Volusion-based storefront and recently decided to dedicate more time and effort into improving my online presence. Admittedly, I'm mostly a lurker in the Q&A forum but I couldn't find any pre-existing info regarding my situation. It could be out there. But again, I'm a noob... So, in my recent SEOmoz report I noticed that over 1,000 Duplicate Content Errors and Duplicate Page Title Errors have been found since my last crawl. I can see that every error is tied to a product in my inventory - specifically each product page has an option to write a review. It looks like the subsequent page where a visitor can fill out their review is the stem of the problem. All of my products are shown to have the same issue: Duplicate Page Title - Review:New Duplicate Page Content - the form is already partially filled out with the corresponding product My first question - It makes sense that a page containing a submission form would have the same title and content. But why is it being indexed, or crawled (or both for that matter) under every parameter in which it could be accessed (product A, B, C, etc)? My second question (an obvious one) - What can I do to begin to resolve this? As far as I know, I haven't touched this option included in Volusion other than to simply implement it. If I'm missing any key information, please point me in the right direction and I'll respond with any additional relevant information on my end. Many thanks in advance!
Intermediate & Advanced SEO | | DakotahW0