Milan Dinić

Change Core Slugs is a plugin that allows you to set custom permalink slugs instead of default ones that are provided with WordPress core. This functionality is already available in WordPress, however it can be used by manually setting new configuration in the code. What this plugin does is that it provides friendly user interface where all site admins can change default slugs.
You can change:
<ul>
<li><code>author</code> base in authors archives</li>
<li><code>search</code> base in searches archives</li>
<li><code>page</code> base in pagination pages of archives or in single posts</li>
<li><code>comments-page</code> base in pagination pages of single posts comments</li>
<li><code>comments</code> base in comments feeds</li>
<li><code>feed</code> base in feeds</li>
</ul>
When you change any slug, you will not get redirection from the pages that used old slug. Same goes if you again change any slug. If you want redirection, you must set it through server rules or with other plugins.
If you disable this plugin, old, default slugs will be restored and URLs with new slugs will stop working. The only way to keep new slugs is by manually setting them in the code.
NOTE: because of two bugs in WordPress core, in some cases setting custom slugs will not work properly. These cases are when <code>page</code> or <code>comments-page</code> include any non-ASCII character (ticket <a href="https://core.trac.wordpress.org/ticket/41891" rel="nofollow ugc">#41891</a>), or when <code>feed</code> or <code>comments</code> bases are set (ticket <a href="https://core.trac.wordpress.org/ticket/43274" rel="nofollow ugc">#43274</a>). Until these two bugs are fixed, you can use <a href="https://github.com/dimadin/redirect-canonical-fix" rel="nofollow ugc">temporary plugin</a> that includes fixes. You do not need that plugin if you do not use features that trigger bugs from above.
And it’s on <a href="https://github.com/dimadin/change-core-slugs" rel="nofollow ugc">GitHub</a>.
<h3>Usage</h3>
Got to Settings > Change Core Slugs page.

Change Core Slugs

Set custom permalink slugs instead of default ones.

sungraizfaryad

Remove Taxonomy URL strips the base slug (<code>/genre/</code>, <code>/topic/</code>, etc.) from your custom taxonomy term URLs so visitors and search engines see clean, short permalinks.
What 3.0 adds:
<ul>
<li>301 redirect old URLs — old <code>/taxonomy/term/</code> URLs redirect permanently to the new <code>/term/</code> URL so SEO equity is preserved when you turn the plugin on.</li>
<li>Hierarchical term URLs — nested taxonomies resolve correctly. <code>/parent/child/</code> reaches the child term instead of returning 404.</li>
<li>Pagination support — <code>/term/page/2/</code> works after the base slug is removed, no more pagination 404s.</li>
<li>Slug-collision detection — warns you (without blocking the save) when a term slug clashes with a page, post, or another taxonomy’s term, so you don’t accidentally break a URL.</li>
<li>Health Check tab — run a full audit of all selected taxonomies on demand.</li>
</ul>
All 3.0 features default to OFF on upgrade so your existing site behavior is preserved until you opt in.

Remove Taxonomy URL

Strip custom taxonomy slugs from URLs. Optional 301 redirects, hierarchical terms, pagination support, and slug-collision detection.

Change Core Slugs vs Remove Taxonomy URL