Title: Pagination problem Last modified: October 19, 2021 --- # Pagination problem * Resolved [RezaY](https://wordpress.org/support/users/mohammad983/) * (@mohammad983) * [4 years, 6 months ago](https://wordpress.org/support/topic/pagination-problem-104/) * I want to no-index the Pagination category and tags. and just main categories and tags index on google. On rank math, there is an option for it to set for all cats and tags. but in Yoast I have to set one by one! could you recommend any plugin or function code that does it besides Yoast? Viewing 6 replies - 1 through 6 (of 6 total) * Plugin Support [Maybellyne](https://wordpress.org/support/users/maybellyne/) * (@maybellyne) * [4 years, 6 months ago](https://wordpress.org/support/topic/pagination-problem-104/#post-14985132) * Hello RezaY, * Thanks for reaching out regarding your paginated archives. * Unfortunately, there is no option in the plugin to add `noindex` to paginated archives. According to Google, adding `noindex` on a page long-term will lead to them not following links on that page. More recent statements imply that if a page isn’t in their index, the links on it and from it can’t be evaluated at all. So with that, we do not recommend adding `noindex` to page 2 and further on paginated archives. * However, if you still want to `noindex` paginated archive pages, you can use the filter located [here](https://github.com/Yoast/wordpress-seo/issues/6310#issuecomment-268838291). You or your developer can customize it depending on your needs. * Thread Starter [RezaY](https://wordpress.org/support/users/mohammad983/) * (@mohammad983) * [4 years, 6 months ago](https://wordpress.org/support/topic/pagination-problem-104/#post-14986410) * thanks for your replay I don’t want to add a no-index. I want to add a canonical reel to all paginated archives to the first cat or tag page. * Plugin Support [Maybellyne](https://wordpress.org/support/users/maybellyne/) * (@maybellyne) * [4 years, 6 months ago](https://wordpress.org/support/topic/pagination-problem-104/#post-14988070) * Hello RezaY, * Thanks for following up. * The Yoast SEO plugin adds the `rel="prev"` & `rel="next"` tags to help deal with [paginated content](https://yoast.com/help/is-the-plugin-compatible-with-paginated-content/), as well as the [canonical URL](https://yoast.com/help/canonical-urls-in-wordpress-seo/). Google is very clear; each page within a paginated series should canonicalize to itself, so /page/2/ has a canonical pointing to /page/2/ and so on. You can read more about that here: [https://yoast.com/pagination-seo-best-practices/](https://yoast.com/pagination-seo-best-practices/). * So if this is not the case with your website, you may want to share the affected URLs so we can investigate further. * We look forward to hearing from you. * Thread Starter [RezaY](https://wordpress.org/support/users/mohammad983/) * (@mohammad983) * [4 years, 6 months ago](https://wordpress.org/support/topic/pagination-problem-104/#post-14988203) * my problem is instead of the category page, google index category, or tag is paginated. for example site.com/cat/page3 indexed instead of site.com/cat and I have this problem on a website that uses Yoast. and on the others that I used rank math just main cat pages indexed. * so I have to canonicalize cats to themselves. one by one on the cat edit page in the Yoast setting * Plugin Support [Michael Tiña](https://wordpress.org/support/users/mikes41720/) * (@mikes41720) * [4 years, 6 months ago](https://wordpress.org/support/topic/pagination-problem-104/#post-14994885) * Hi [@mohammad983](https://wordpress.org/support/users/mohammad983/) * For a while, SEOs thought it might be a good idea to add a noindex robots meta tag to page 2 and further of a paginated archive. This would prevent people from finding page 2 and further in the search results. The idea was that the search engine would still follow all these links, so all the linked pages would still be properly indexed. * The problem is that in late 2017, Google said something that caught our attention: long-term noindex on a page will lead to them not following links on that page. More recent statements imply that if a page isn’t in their index, the links on/ from it can’t be evaluated at all – their indexing of pages is tied to their processing of pages. * This makes adding noindex to page 2 and further of paginated archives a bad idea, as it might lead to your articles no longer getting the internal links they need. * Because of what Google said about long-term noindex, in Yoast SEO 6.3 we removed the option to add noindex to subpages of archives. * This is why we recommend that each category subpage (/page/2/ and onwards) canonicalizes to itself instead of referring to the main category page without the subpage. * You can learn more about it here – [https://yoast.com/pagination-seo-best-practices/](https://yoast.com/pagination-seo-best-practices/) * [devnihil](https://wordpress.org/support/users/devnihil/) * (@devnihil) * [4 years, 6 months ago](https://wordpress.org/support/topic/pagination-problem-104/#post-15021645) * We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue. Viewing 6 replies - 1 through 6 (of 6 total) The topic ‘Pagination problem’ is closed to new replies. * ![](https://ps.w.org/wordpress-seo/assets/icon-256x256.gif?rev=3419908) * [Yoast SEO - Advanced SEO with real-time guidance and built-in AI](https://wordpress.org/plugins/wordpress-seo/) * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-seo/#faq) * [Support Threads](https://wordpress.org/support/plugin/wordpress-seo/) * [Active Topics](https://wordpress.org/support/plugin/wordpress-seo/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-seo/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wordpress-seo/reviews/) * 6 replies * 4 participants * Last reply from: [devnihil](https://wordpress.org/support/users/devnihil/) * Last activity: [4 years, 6 months ago](https://wordpress.org/support/topic/pagination-problem-104/#post-15021645) * Status: resolved