Canonical error – without updating canonical tag

Hi @ayazfudugo

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.

You can read more about it here: https://kb.yoast.com/kb/is-the-plugin-compatible-with-paginated-content/

Closed. No further questions.

My apologies as I was busy discussing with the developers about this issue and see if it was coming from the theme or some other plugin as you suggested.

the issue is not in custom pagination or theme as they are using WordPress default pagination.

The issue is with canonical tags not being removed from the page source code when they are removed from Yoast plugin backend. I had first set up canonicals which I later removed, but while they were removed from the plugin, they are still visible in the source code and not removed from there.

Any solutions on how I can get the updated instructions to reflect in the source code where once I remove the canonical from plugin the same is reflected in the front end of the website.

Example screenshots below –

source code – https://prntscr.com/n4i31u
backend – https://prntscr.com/n4i45f

• This reply was modified 5 years, 11 months ago by ayazfudugo.

Yoast SEO will output pagination tags when a post or page uses a page break tag in the default WordPress content area to divide the post/page into multiple pages.

Reviewing the source code of the Highlights page, it does not appear that the page uses a page break. Please use the wpseo_canonical, wpseo_prev_rel_link and wpseo_next_rel_link filters to add change the paginated tags. Example code snippets for these filters can be found here:
https://gist.github.com/amboutwe/66c583d2ef4015a8a244ee3e0e8cd1a0
https://gist.github.com/amboutwe/2aa7dcc9a38986e11fac68c7306cc091

Typically code snippets are added to your theme’s functions.php file. If you’re not familiar with using code snippets, these articles have wonderful advice:
https://www.wpbeginner.com/plugins/how-to-easily-add-custom-code-in-wordpress-without-breaking-your-site/
https://www.wpbeginner.com/beginners-guide/beginners-guide-to-pasting-snippets-from-the-web-into-wordpress/

Thanks for the reply. As I mentioned in my previous post, it is not only with paginated pages.

Even on another instance where the website has events section and for each day the event repeats a new URL generates. To avoid duplication, I had set up canonical on the main events page to point to itself. However, later when I removed it, the canonical was removed from the plugin but not from source code.

The major concern is still that Yoast SEO does not remove canonical tags from source code when it is removed from the plugin in the backend.

Ayaz

That is indeed strange and I haven’t been able to reproduce that behavior in our test environments for posts or pages. I added a page with a page break then added a custom canonical. Checked the source code of the three pages. They all had the custom canonical as expected with the prev/next tag to the prev/next URL with page number. After removing the custom canonical, the canonical of each page matches the permalink, including the page number on the second and following pages.

This may be a plugin or theme conflict. Please disable all plugins except Yoast SEO, and use one of the default (Twenty*) themes. If the problem goes away, enable plugins one by one to identify the source of your troubles.

If you can install plugins, the Health Check & Troubleshooting plugin offers a troubleshooting mode that will disable all plugins and change the theme for you, while you’re still logged in, without affecting normal visitors to your site. Once in the troubleshooting mode, please activate only Yoast SEO and attempt to reproduce the issue you described.

If you are 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

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

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

Thanks for understanding!