Hello,
We understand that you have removed category prefix and recently there have been unwanted redirects from the category page. For instance, we can confirm a 301 redirect from https://bestellipticalmachinehut.com/category/spin-bike-reviews/under-300/ to https://bestellipticalmachinehut.com/spin-bike-reviews/ and also from https://bestellipticalmachinehut.com/category/spin-bike-reviews/under-300/ to https://bestellipticalmachinehut.com/spin-bike-reviews/under-300/
In some cases, removing the category prefix conflicts with other plugin or theme features. Just to be sure, we would like to rule out any plugin or theme conflicts that may occur. The fastest way to do this is to deactivate all non-Yoast plugins and switch to a standard theme like Twenty Nineteen.
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.
As we can imagine that 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 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.
Thank you
Thread Starter
shss
(@shss)
I think you didn’t understand the issue here?
Your plugin changed my permalink, brought the prefix “category” in the URL and then removed it and created a redirect. What is there to do to resolve this????
If you are willing to find a solution rather than blaming the theme or selling me your plugin, let me know. Otherwise don’t waste my time.
Since a couple of months back I started receiving Yoast notification giving false notice about change in permalink structure, over and over.
(Because of a change in your permalink structure, some of your SEO data needs to be reprocessed)
Using Yoast was a mistake and I swear if I could afford I would have sued you for changing permalinks on a live website. This has ruined my website and years of my hard work.
Hello,
Let’s clarify how the feature works. The 301 redirect lets search engines know that the /category/ category-name URL is now located in /category-name/. And that’s the way the feature has always worked. We suspect that you have been using a very old version of the plugin and recently updated it.
In essence, the 301 redirects have always been on your site; you probably didn’t know how it worked. Removing the slug changes the old permalink structure. And the correct way to handle URL structure changes is through a 301 redirect. That’s why the plugin creates the 301.
Thank you.
Thread Starter
shss
(@shss)
I never published one article with the category slug in the URL because, on the very first day, I enabled the Yoast option to remove the category. So, no post was ever published on my website with the slug “category”.
Somehow it was added and then removed with a 301 redirect and the only plugin that has the ability to do that is the Yoast. Several times, I remember getting notification from Yoast that the permalink has changed and I thought it was false but in the end it was actually Yoast that dropped the ball (brought back the category slug in the URL and then removed it again).
Since your “remove category slug” is unreliable, you should have removed this option. This way, I would have found a different way to do this.
Hi,
The ‘remove the categories prefix’ has always worked with a 301 redirect from /category/category-name/ to /category-name/. Based on the links you’ve provided, the feature is working as expected.
While the feature is available and makes your links look relatively cleaner by stripping the /category/ prefix, it can cause unexpected URL behavior depending on the other themes and plugins on your website and is also something that should preferably be tested on a staging site, if possible, before implementing it on a live site — https://yoast.com/help/how-to-remove-the-categories-prefix/
We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.
