• Resolved alexbbonzer

    (@alexbbonzer)


    Continued from another thread that was closed due to inactivity.

    We’d like to update the canonical URL so it matches the current browser url.
    So when you’re on a page like
    /shovels/page/2/
    then the canonical should likewise say <link rel=”canonical” href=”https://www.example.com/shovels/page/2/&#8221; />

    Currently with Yoast, it only seems to refer to the first page in the paginated sequence.

    What’s the recommended action here, to get the paginated pages to have a self-referencing canonical?

    I followed the instructions of

    1. Install & activate the Yoast Test Helper plugin
    2. Go to Tools > Yoast Test
    3. Locate the Yoast SEO section and click on the ‘Reset indexables tables & migrations’, ‘Reset Prominent words calculation’, and ‘Reset Internal link counter’ buttons. After each click, the page will reload to confirm that the specific reset was successful.
    4. Go to SEO > Tools, and under SEO data, click the “Start SEO data optimization” button to allow Yoast to rescan your content.

    And this didn’t change the canonical tag, so after doing this, the canonical still points to the first page in the paginated sequence

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support Maybellyne

    (@maybellyne)

    Hello @alexbbonzer

    Thanks for reaching out about the rel="next" and rel="prev" tags for your paginated content. When I checked https://www.cardrop.com/blog/3/, these tags were not present and the canonical refers to the blog page.

    Yoast SEO adds rel="next" and rel="prev" tags that let search engines know they are on a paginated archive series. 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.

    Can you temporarily disable all plugins except Yoast SEO and switch to a default WordPress theme? Do the tags appear?

    If yes, in this case, 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.

    The wpseo_prev_rel_link and wpseo_next_rel_link filters can customize the output or return false to disable the output. Some examples can be found here.

    Thread Starter alexbbonzer

    (@alexbbonzer)

    I’m not sure if we can just disable all plugins and change the theme out of nowhere since it’s a business that’s heavily reliant on the website.

    I think that the first thing I’ll do, is reach out to the website owner and hear if they have a way to contact the developer, since he ought to know if he made a function like this.
    Then if they give the green light, we can try the theme and plugin disabling troubleshooting.

    Thread Starter alexbbonzer

    (@alexbbonzer)

    Also, just for clarification, Google doesn’t consider rel=”next” and rel=”prev” as indexing signals anymore , I’m strictly talking about canonical tags, not rel=”next” rel=”prev”.

    just to be sure we’re not miscommunicating ??

    Plugin Support Maybellyne

    (@maybellyne)

    Disabling plugins and switching themes is not an option on a business website. We’ll recommend using the Health Check & Troubleshooting plugin. This plugin has a troubleshooting mode, which does not affect normal visitors to your site.

    If you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process: How to check for plugin conflicts

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

    Thread Starter alexbbonzer

    (@alexbbonzer)

    Alright, I tried installing the health Check & Troupleshooting plugin, this just resulted in whenever we enabled troubleshooting mode, that the entire site would crash – the front-end looked fine when visiting the site on an incognito browser – but while logged in I just got the error message that “There has been a critical error on this website. Please check your site admin email inbox for instructions. Learn more about troubleshooting wordpress”

    Hey @alexbbonzer,

    Thank you for your reply, sorry to hear that.

    It seems that the troubleshooting mode doesn’t really work well on your site, that’s odd. However, if that is not working, I’d recommend doing the previously shared steps not on the live site, but on a staging site.

    Thread Starter alexbbonzer

    (@alexbbonzer)

    Which previous steps are you thinking here?

    I did the steps related to the yoast test helper on the live site if that’s the ones you’re thinking of.

    Hey @alexbbonzer,

    Thank you for your reply.

    Sorry that my previous reply was confusing. I was referring to the conflict check steps.

    We checked your blog page once again, and we see in the page source that this is actually a “real” page instead of a blog archive. It looks like this page is built with Elementor and some templates – rather than using a real blog archive. It’s pretty custom and we don’t have a good solution for this. One way I was thinking to fix this manually is to customize our plugin and use our API to do so. You can find more information here: https://developer.yoast.com/features/seo-tags/canonical-urls/api/

    This thread was marked resolved due to a lack of activity, but you’re always welcome to re-open the topic. Please read this post before opening a new request.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Canonical doesn’t include pagination’ is closed to new replies.