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
-
Why is my home page ranking much higher than my collection page?
Hi everyone, Why is my client's home page ranking high for a certain keyword phrase rather than a collection page I have which is well optimised for this keyword? The collection page is on the 10th SERPs page. I did see there were keywords used in the footer of page and the keyword was also used in some intro text on the home page so I removed the keyword from these two places nearly 2 weeks ago and requested google to reindex both the collection page and home page and I've not seen any improvement of the collection page's ranking in SERPs. I also changed the meta description and meta title as the ctr was poor but there wasn''t that many impressions either. It is a competitive keyword organically so maybe the collection page's authority is just not good enough compared to the competitors hence why they are choosing the home page as it has higher page authority however this still is not helpful to searchers who land on home page. Does anyone have any ideas of what else I can do to get google to rank the ocllection page higher for the keyword instead of home page?
Intermediate & Advanced SEO | | TZ19820 -
Why does Google display the home page rather than a page which is better optimised to answer the query?
I have a page which (I believe) is well optimised for a specific keyword (URL, title tag, meta description, H1, etc). yet Google chooses to display the home page instead of the page more suited to the search query. Why is Google doing this and what can I do to stop it?
Intermediate & Advanced SEO | | muzzmoz0 -
Prioritise a page in Google/why is a well-optimised page not ranking
Hello I'm new to Moz Forums and was wondering if anyone out there could help with a query. My client has an ecommerce site selling a range of pet products, most of which have multiple items in the range for difference size animals i.e. [Product name] for small dog
Intermediate & Advanced SEO | | LauraSorrelle
[Product name] for medium dog
[Product name] for large dog
[Product name] for extra large dog I've got some really great rankings (top 3) for many keyword searches such as
'[product name] for dogs'
'[product name]' But these rankings are for individual product pages, meaning the user is taken to a small dog product page when they might have a large dog or visa versa. I felt it would be better for the users (and for conversions and bounce rates), if there was a group page which showed all products in the range which I could target keywords '[product name]', '[product name] for dogs'. The page would link through the the individual product pages. I created some group pages in autumn last year to trial this and, although they are well-optimised (score of 98 on Moz's optimisation tool), they are not ranking well. They are indexed, but way down the SERPs. The same group page format has been used for the PPC campaign and the difference to the retention/conversion of visitors is significant. Why are my group pages not ranking? Is it because my client's site already has good rankings for the target term and Google does not want to show another page of the site and muddy results?
Is there a way to prioritise the group page in Google's eyes? Or bring it to Google's attention? Any suggestions/advice welcome. Thanks in advance Laura0 -
Google displaying a content box above the listing link for top ranking listing in SERPs
Hi, In the attached Google SERP example the first listing below the paid search ads has a large box with a snippet of content from the relevant page then followed by the standard link. Does anyone know how you get Google to display a box like this in their SERPs? I checked the code on the page and there doesn't appear to be anything special about it such as any schema markup. It uses standard list code. Does this only appear for particular types of content or sites, such as medical content in this case? Is the content more likely to appear for lists? Does it only appear for high authority sites that Google has selected? We have a similar medical information based site and it would be great to try to get Google to display a similar box of content for some of our pages. Thanks. Damien ZmPJVSl.png
Intermediate & Advanced SEO | | james.harris0 -
Better UX or more Dedicated Pages (and page views)?
Hi, I'm building a new e-commerce site and I'm conflicting about what to do in my category pages. If we take for example a computer store.
Intermediate & Advanced SEO | | BeytzNet
I have a category of laptops and inside there are filters by brand (Samsung, HP, etc.). I have two options - either having the brand choice open a new dedicated page -
i.e. Samsung-Laptops.aspx or simply do a JQuery filter which gives a better and faster user experience (immediate, animated and with no refresh). **Which should I use? (or does it depend on the keyword it might target)? **
Samsung laptops / dell laptops / hp laptops - are a great keyword on there own! By the way, splitting Laptops.aspx to many sub category physical pages might also help by providing the site with many actual pages dealing with laptops altogether.0 -
What to with an event page that is over?
Hi, We participated in an event and it is now over and therefore it has to be removed now. I was thinking of writing a blog post about the event and place a 301 redirect on the page enlisting the event's detail and registration process. Would it be a good idea or should I do something else? Regards,
Intermediate & Advanced SEO | | IM_Learner0 -
404 Error on Blog Pages that Look Like Loading Fine
There was recently a huge increase in 404 errors on Yandex Webmasters corresponding with a drop in rankings. Most of the pages seem to be from my blog (which was updated around the same time). When I click on the links from Yandex the page looks like it is loading normal, expect that it has the following message from the Facebook plugin I am using for commenting Any ideas about what the problem is or how to fix it? Critical Errors That Must Be Fixed | Bad Response Code: | URL returned a bad HTTP response code. | Open Graph Warnings That Should Be Fixed | Inferred Property: | The 'og:url' property should be explicitly provided, even if a value can be inferred from other tags. |
Intermediate & Advanced SEO | | theLotter
| Inferred Property: | The 'og:title' property should be explicitly provided, even if a value can be inferred from other tags. |
| Small og:image: | All the images referenced by og:image should be at least 200px in both dimensions. Please check all the images with tag og:image in the given url and ensure that it meets the recommended specification. |0 -
Rel Canonical Syntax
My IT department is getting ready to setup the rel canonical tag, finally. I took a look at the code on our test server and see that they are using a single quote in the tag syntax (see code block below). Should I be concerned? Will Google read those lines the same? <link rel='canonical' href='[http://www.wholesalecostumeclub.com/easter-costumes/bunny-suits](view-source:http://www.wholesalecostumeclub.com/easter-costumes/bunny-suits)' />VS. **versus** <link rel="canonical" href="[http://www.wholesalecostumeclub.com/easter-costumes/bunny-suits](view-source:http://www.wholesalecostumeclub.com/easter-costumes/bunny-suits)" />
Intermediate & Advanced SEO | | costume0