: Shall I add hreflang on pagination sites which are using rel="prev" and rel="next"? At the moment I am using the current solution for pagination (without the view-all solution): <link rel="prev"
At the moment I am using the current solution for pagination (without the view-all solution):
<link rel="prev" href="http://www.example.com/category/blablabla/page/2" />
<link rel="next" href="http://www.example.com/category/blablabla/page/4" />
Recently I've also added the hreflang attribute for multiple websites:
<link rel="alternate" hreflang="en-US" href="http://www.example.com/category/blablabla/page/3">
<link rel="alternate" hreflang="sv-SE" href="http://www.example.com/kategori/blablabla-in-swedish/sida/3">
By the way the hreflang code I have created is generated on all sites, not only in the pagination site.
Do I need to add hreflang in a pagination site? If yes, then this might also be harder because all websites might not have the same amount of pages.
More posts by @Ann8826881
1 Comments
Sorted by latest first Latest Oldest Best
I think you should not do this (unless each English pagination page contains the same items like the Swedish pagination page with the same number).
alternate+hreflang should only be used for translations. But if your English page 3 could contain the items {A, B, C, D} and your Swedish page 3 could contain the items {B, D, E, F}, they aren’t really translations of each other. It wouldn’t make sense for a user to switch from English p. 3 to Swedish p. 3, because it could list totally different items (e.g., most of the items the user already saw on the English p. 2), and so it wouldn’t make sense for search engines to understand or show them as translations.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.