Artberri

For a better SEO, it is said that the URLs must give information about the content of the web page. Because of this most people uses pretty URLs in wordpress with the permalink options. But the post slug in the URL is generated from the title of the post, and some times this slug is too long because we don’t remove the stopwords, common words without an important meaning, that don’t add anything significant to the URL.
This plugin removes the stopwords from the URLs for better SEO optimization of your blog and for making better and smaller URLs. You can set the stopwords through the `Plugins’ menu in WordPress wp-admin.
For example:
<ul>
<li>You have set the next stopwords: a, an, the, i, you, he, she, we, they, of</li>
<li>You write a post called: Review of the Google Chrome Browser</li>
<li>The normal post slug would be: review-of-the-google-chrome-browser</li>
<li>But the optimized slug is: review-google-chrome-browser</li>
</ul>
All configuration is done through wp-admin. No code editing is necessary.

Remove Stopwords From Slug

This plugin removes the stopwords from the URLs for better SEO optimization of your blog. You can set the stopwords in the admin panel.

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.

Remove Stopwords From Slug vs Change Core Slugs