I'm trying to ensure google indexes the pages on paginated views. Rankmath has functionality for this, but they are saying toolset views don't use the is_paged() function. Is there a way for toolset views to use the is_paged() function?
Thank You for your time.
Hi,
Thank you for contacting us and I'd be happy to assist.
From the description, I understand that the RankMath SEO plugin uses the 'is_paged' function to detect the next/previous pages or posts.
But the case of views is unique, because, technically the pagination is not for the pages or posts where the view is placed on. It is for the views query that is loaded as the part of the page/post.
If your view is set to update the pagination results without AJAX, you can set it to use AJAX. This way, the page won't reload when pagination is used and you won't need the rel=next and rel=prev tags.
regards,
Waqar
Thank You Waqar. I hope you are having a great day.
The page is using ajax for pagination already. The paginated pages of the view are not getting indexed since there is no adjacent link meta data generated by rankmath since toolset doesn't use is_paged function. Using ajax or full page reload, Google still needs the adjacent link meta data to index the paginated pages properly. Can toolset be configured to use is_paged function?
Thanks for writing back.
I've performed some testing and research and I'm afraid, in the context of the Toolset views, the 'is_paged' function can't be leveraged.
That function is designed to work with the main WordPress query (i.e. which page or post is being viewed). But to show the list of posts, the views use a secondary query, within the page/post that they are used on.
Unfortunately, I can't think of any workaround or custom code approach, where it can be made to work.
Thank You for looking into it. This is a huge issue for our project. If only the main page gets indexed our entire project is pointless. I find it hard to believe that toolset is ok with only the first page of any view getting indexed. There has to be a workaround.
In the past, the idea to implement the rel=next and rel=prev tags for the views pagination was dropped because it would result in serious performance cost. Those tags were expected to be added in the head of the page, which would mean extra queries to detect the presence or existence of the next and previous pagination links.
Additionally, it turns out that Google no longer uses those tags either. Here is a note from Google's own article on this topic at:
lien caché
In the past, Google used <link rel="next" href="..."> and <link rel="prev" href="..."> to identify next page and previous page relationships. Google no longer uses these tags, although these links may still be used by other search engines.
As per this article, as long as your pagination links are accessible by the Googlebot, they should be covered for the indexing.
I hope this information helps and let me know if you have any follow-up questions.
