Hello Beretgz,
Thanks for reaching out but unfortunately, the issue you are experiencing is not clear. Can you please provide some more explanation? Please provide us with screenshots that highlight the issue you are experiencing. You can use any image-sharing service like https://pasteboard.co/, https://snag.gy/, https://imgur.com/, https://snipboard.io/, or even upload the screenshot to your own website. Once you upload it to an image sharing service, please share the link to the image here.
Thanks, Beretgz. It all makes sense now.
Can you also confirm what you have in WordPress > Settings > Reading > Your homepage displays?
We look forward to hearing from you.
I have A static page in WordPress > Settings > Reading > Your homepage displays
Thanks for the feedback.
If you have a static page, then this is expected. rel=next and rel=prev tags are used to tell search engines that certain pages belong to an archive, a so-called paginated archive. A rel=next / prev tag in the header of your site lets search engines know what the previous and the next page in that archive is. However, with the settings you have chosen, yours is not a paginated archive. On your homepage, it will apply if you had set your site to display your latest posts.
You can read more at https://yoast.com/rel-next-prev-paginated-archives/ and
Hi @beretgz,
We’ve been trying to reproduce the problem you reported, but have been unable to do so using a default WordPress theme using a static homepage with pagebreaks.
In order to help us reproduce the problem, would you be able to share which theme you’re using, how you built your home page. and what other plugins are running on your site?
The more information you can provide, the easier it will be for us to figure out what’s happening.
Thanks for your help!
I think I found a reason.
Some of the posts I manually paginate using Gutenberg. On such posts, the Yoast SEO plugin works correctly and adds rel = next and rel = prev tags
And some of my posts are automatically split using the Automatically Paginate Posts plugin https://ww.wp.xz.cn/plugins/automatically-paginate-posts/
And on such pages, the Yoast SEO plugin does not add rel = next and rel = prev tags.
Could you help me?
Thanks for your clarification @beretgz. The issue you’re currently experiencing is specific to the relevant 3rd party paginating plugin that you’re using which has no support for Yoast SEO’s rel="next" and rel="prev", as such you’re not seeing the relevant canonical.
So, you could use the wpseo_prev_rel_link and wpseo_next_rel_link filters to customize the output or return false to disable the output. Some examples can be found here.
Unfortunately, I didn’t succeed.
I am not getting rel = "next" and rel = "prev" tags in my posts paginated with the Automatically Paginate Posts plugin https://ww.wp.xz.cn/plugins/automatically-paginate-posts/
I checked the work of the All in One SEO plugin and it correctly sets the rel = "next" and rel = "prev" tags.
But I don’t like this plugin. I love Yoast. Can developers fix this issue?
As much as we’d like to fix this for everyone, it looks like the relevant 3rd party pagination plugin hasn’t been updated for over a year so far. The relevant plugin page even shows a notice about this as well. So, it doesn’t make sense to add support for a 3rd party plugin that isn’t being developed regularly.
So, the best thing would be to switch to a 3rd party pagination plugin that updates regularly.
So, the best thing would be to switch to a 3rd party pagination plugin that updates regularly.
I would really like this, but this is the only plugin with this functionality. No other choice
Hi,
While we do know that Yoast SEO should work with the default WordPress core pagination functions, for those 3rd party plugins handling their own pagination, especially if they haven’t been updated in quite some time, it would be difficult to integrate and work on a solution here.
You may want to look into using the wpseo_prev_rel_link and wpseo_next_rel_link filters to customize the output or return false to disable the output. Some examples can be found here. Sorry that we couldn’t be of more help to you here.
We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.
