Uses AJAX and Java Script scrolling
Posted: Sun Feb 02, 2025 9:34 am
You've probably encountered a situation where you have to endlessly scroll through the assortment in online stores. To load products, you have to constantly scroll them to the bottom of the screen. Although this is a good option to improve the usability of the site, it also needs to be used wisely.
It is better to make sure that the product bank email list range does not load automatically when scrolling. It is better to place the "Show N more products" button under the last product items.
Often, when using rel=«prev»/«next» attributes on pagination pages, there may be parameters that do not change the content:
session variables;
sorting;
change the number of elements per page.
Read also!
"Canonical Link: How to Install Correctly, Errors When Using"
Read more
In this case, the content is duplicated. The combination of rel=«prev»/«next» and rel=«canonical» allows you to solve the problem.
To do this, first of all, you need to make sure that all pagination pages with rel=“prev”/“next” use the same parameter. In addition, for each URL with a parameter, you should specify its canonical page without this parameter. Let's say we have the same 4 pagination pages and use the session ID sessionid=55 to track visitors:
Session ID sessionid=55
It is also important to use filters and rel=«prev»/«next» correctly. Let's say you use parameters by which the site is able to provide unique content, and it is important for you that such filtered pages are present in the index. For example, you have a category with sneakers and you intend to create landing pages for search results with different brands, using parameters in the URL.
In this case:
there is no need to apply rel="canonical" to the main category due to unique content;
For each brand it is necessary to form its own unique chains, the basis for which will be rel=«prev»/«next»:
create unique and relevant title, description along with category description text for each filter.
So, we recommend solving the pagination problem in the following way: if technically possible, create a "View all" page. Provided that such pages load quickly and are not very large, you can use this option, since Google recommends it, and Yandex understands the rel="canonical" directive.
But most often it is wiser to use a combination of attributes rel=“next/prev” (understood by Google) and meta tag robots=“noindex,follow” (both Google and Yandex).
It is better to make sure that the product bank email list range does not load automatically when scrolling. It is better to place the "Show N more products" button under the last product items.
Often, when using rel=«prev»/«next» attributes on pagination pages, there may be parameters that do not change the content:
session variables;
sorting;
change the number of elements per page.
Read also!
"Canonical Link: How to Install Correctly, Errors When Using"
Read more
In this case, the content is duplicated. The combination of rel=«prev»/«next» and rel=«canonical» allows you to solve the problem.
To do this, first of all, you need to make sure that all pagination pages with rel=“prev”/“next” use the same parameter. In addition, for each URL with a parameter, you should specify its canonical page without this parameter. Let's say we have the same 4 pagination pages and use the session ID sessionid=55 to track visitors:
Session ID sessionid=55
It is also important to use filters and rel=«prev»/«next» correctly. Let's say you use parameters by which the site is able to provide unique content, and it is important for you that such filtered pages are present in the index. For example, you have a category with sneakers and you intend to create landing pages for search results with different brands, using parameters in the URL.
In this case:
there is no need to apply rel="canonical" to the main category due to unique content;
For each brand it is necessary to form its own unique chains, the basis for which will be rel=«prev»/«next»:
create unique and relevant title, description along with category description text for each filter.
So, we recommend solving the pagination problem in the following way: if technically possible, create a "View all" page. Provided that such pages load quickly and are not very large, you can use this option, since Google recommends it, and Yandex understands the rel="canonical" directive.
But most often it is wiser to use a combination of attributes rel=“next/prev” (understood by Google) and meta tag robots=“noindex,follow” (both Google and Yandex).