Skip Navigation


Reported for: WPML Multilingual CMS 3.3.6

Resolved in: 4.2.5

Overview of the issue

The ‘Strip the category base (usually /category/) from the category URL.’ from Yoast SEO plugin does not work with WPML.

strip category base WP SEO

When you activate this option in Yoast SEO plugin (Strip the category base (usually /category/) from the category URL.), the categories in other language give 404 errors.


Disable that option in Yoast SEO plugin and use this plugin instead

33 Responses to “Yoast SEO - Strip the category base does not work in the second language”

  1. Hi, sorry, but can you please elaborate some more? do you mean because of the ‘strip category’ issue, or any other issue you have between WPML and Yoast SEO ?

    • Hi there,

      We have tested again everything seems to be working as expected, with the default theme and also with some premium themes. Can you please make sure you are not affected by some caching happening ? If you still can not resolve please open a ticket in our support forums.

  2. I was also struggling few hours (!) to make this work, it worked in default language but not in others. I fiddled with settings, saving permalinks, keeping or removing “category” slug in SEO Yoast, activating default theme, deactivating plugins, searching everything across web for solution…
    Finally I got it working after installing this plugin

    • Sorry for that but every plugin that messes up with the URL structure is very complex to handle. I am happy you found out the solution at the end.

  3. The process you described above is not working. If you add ‘.’ to the category base it shows a 404 error. The only workaround is to manually redirect each one of them to category page.

    What can we do if we don’t want to install the plugin?

          • Please release the fix. I tried with earlier version and it was working fine. But when I am switching to new version the problem creeps up.

            It’s showing lots of not found errors. And this is hurting our rankings

            Please release

  4. We have just released a beta version that resolves this issue, please if you can give it a try – important note! – it’s a beta so I do not recommend using it on production without running it first on a test server.