[removed]

The SEO Slugs WordPress plugin removes common words like ‘de’, ‘het’, ‘bij’ from post slugs to improve search engine optimization.
For example, when you publish a post with a title like this:
“Vijf Tips Om Hoger In Google Te Scoren”,
WordPress automatically assigns a long filename to your post, called a post slug:
/vijf-tips-om-hoger-in-google-te-scoren
SEO Slugs plugin strips common words like “om”, “in” or “te” out of your post slug to make it more search engine friendly. With SEO Slugs plugin activated, the slug for our example blog post would look like this:
/vijf-tips-hoger-google-scoren
The slug is generated on saving a post (so you get a chance to look at it before publishing, and change it), or on publish. It won’t overwrite an existing slug. You can force a new slug generation by deleting the existing one.

SEO Slugs

Removes common words like 'de', 'het', 'bij' from post slugs to improve SEO.

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.

SEO Slugs vs Change Core Slugs