Support » Plugin: Yoast SEO » rel=next/prev Issue

  • Resolved kkow



    I’m seeing a strange issue where our development and staging environments are correctly showing rel next/prev links for our archives, but then the production version does not. Is there anything that could be causing this? They are all using the same version of code.

    Thank you!

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Md Mazedul Islam Khan


    This issue typically occurs when Yoast SEO has the old data in the Indexables tables and migrations. To clear the cache, you’ll need to reset the Yoast SEO Indexables tables and migrations by following the steps given below:

    • Install and activate Yoast Test Helper plugin;
    • Go to Tools → Yoast Test → Yoast SEO → Reset indexables tables & migrations options to reset it;
    • Run SEO data optimization from the SEO → Tools page.

    Let us know whether the issue persists after performing the above steps.

    Thread Starter kkow


    Hmm, the issue does seem to be persisting after performing those steps. Any other suggestions? Thanks again!

    Plugin Support devnihil


    @kkow Thanks for your reply, and we’re sorry to hear that didn’t resolve the issue for you.

    Can you please confirm you are using the most recent release of Yoast SEO version 17.1? You can learn more about updating here:

    Also, can you confirm you are using WordPress 5.8.1? You can check by clicking on the W in the top left and selecting About. If you need to update, please check with your host provider. Please know that if you are using an older version of WordPress Core you may experience unexpected behavior with Yoast. This guide explains more:

    If you update to the most current version of WordPress and Yoast SEO, does this resolve the issue?

    If you have confirmed both WordPress, Yoast SEO, and all of your site’s other plugins and themes are up to date and the problem is still occurring, we would next recommend performing a conflict check. A plugin or theme conflict can sometimes cause functionality problems, errors, or unexpected behavior from the plugin. If you are unfamiliar with checking for conflicts, we have a step by step guide on how to check for conflicts available here: How to check for plugin conflicts.

    Test this on your development or staging site, if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin allows you to run a conflict check without affecting normal visitors to your site.

    Can you please confirm you have performed a complete conflict check by disabling other plugins, and resetting the theme to a default such as TwentyTwentyOne and let us know the results?

    If you do not feel comfortable to do this yourself or if this does not solve your issue, our Yoast SEO Premium plugin comes with one year of (technical) support.

    Thread Starter kkow



    Yes we are currently running the current versions of both Yoast and WordPress. I am unable to test a different theme as the custom taxonomy that this effects is defined in that theme. Strangely enough though, our development and staging sites use the same setup, versions, plugins, etc. and do not have this issue.

    Thread Starter kkow


    Update: I did use the Health Check Tool to test the production site with only what was needed: The theme, Yoast SEO, and ACF. Everything else was disabled and the issues persists. I also noticed there is no canonical URL being output either

    Plugin Support Suwash Kunwar



    Could you please make sure that your theme implements default WordPress pagination method to break the content into pages? If it implements custom pagination method, it makes our plugin not detect your paginated content.

    If that’s the case, please reach out to the developers of the plugin or theme you are using to confirm further.

    Regarding no canonical tag output, the Yoast plugin automatically removes the canonical tag from pages that have been noindexed. Please check if the page is set to ‘index’.

    Plugin Support Michael Tina



    This thread has been marked as resolved due to a lack of activity.

    You’re always welcome to re-open this topic. Please read this post before opening a new request.

    Thanks for understanding!

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.