canonicals for paginated URLs

@snehalvolvoikar29

A common misconception is that the canonical on a paginated page should always point to page 1 in the series. This is not the case. When you do that, you run the risk of search engines not indexing links that appear on page 2, 3 etc. of your archives. Each page within a paginated series should canonicalize to itself, so /page/3/ has a canonical pointing to /page/3/.

If the paginated tags of rel=”next” and rel=”prev” are not appearing as expected this may be the result of another plugin or theme causing a conflict. As our plugin utilizes the built-in WordPress core functions to recognize pagination. Some plugins and theme developers have modified or created their own method of adding pagination. In these cases, custom code may need to be written by a developer to pass information between our plugin and the plugin or theme creating the pagination. Please reach out to the developer of the plugin or theme in question to request information on being compatible with our plugin.

Can you try and gather as much information for us as possible? Please perform the following:

1. Make sure the issue doesn’t persist when Yoast SEO is disabled.
2. Check for conflicts.

I believe that you checked the screenshots attached. So, in my case, the url https://www.example.com/shop/page/3 has a canonical pointing to shop/page/3, similarly,https://www.example.com/shop/page/2 > /shop/page/2, which I think is updated properly by yoast as per your comments. So, is that how yoast works? Let me know if the canonicals are implemented properly for the shop pages : https://gulfissimo.com/shop.

@snehalvolvoikar29 The URL https://www.gulfissimo.com/shop/page/2 has a self referencing canonical pointing to shop/page/2. That’s expected behavior.

Please, refer to this post https://yoast.com/rel-next-prev-paginated-archives/ for more information.

I read the doc you shared. I’m a bit confused, rel=next and rel=prev , if they are required at all. Is it already implemented in yoast or no? If it is there, why can’t I see it in the cource code? Please help!

• This reply was modified 3 years, 11 months ago by Snehal Volvoikar.
• This reply was modified 3 years, 11 months ago by Snehal Volvoikar.

@snehalvolvoikar29 Thanks for your reply.

Yes they should appear in your source code. If they aren’t we’d recommend the following:

1. Make sure the issue doesn’t persist when Yoast SEO is disabled.
2. Check for plugin/theme conflicts. We have a guide on how to do this here: https://yoast.com/help/how-to-check-for-plugin-conflicts/

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.