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.

Chuck Reynolds

This plugin adds a column to wp-admin “All Posts” and “All Pages” views displaying the URL path and Slug for each one. This will also show the nested path if a page is a child post of a parent. If a post or page is not published we’ll do our best to determine the url path and display that slightly greyed out for quick reference as it’s technically not an official URL path or Slug yet. This should also work for custom post types of type page or post, and furthermore this should now, as of v1.6, also display Multibyte characters in slugs for non-latin languages too.
I initially built this out of necessity to quickly identify pages by their slug/path as sometimes the titles that clients used did’t match up nicely with the URL slug on the front-end of the site; so here’s a fast way to do that. Nothing fancy, just does what it does.
Do you have a feature you’d like or a bug you’ve found? Feel free to <a href="https://github.com/chuckreynolds/Admin-Slug-Column/issues" rel="nofollow ugc">make an issue on the github repo</a>.

Admin Slug Column

Really. It's simple, and that is why it is awesome. Thanks for saving me the work.

It does exactly what it says it does

Still working as of WP 6.0.2. Makes it easy to see post URL's.

Still works, great plugin

So simple but so useful


Simple and works as expected. Saves a lot of time when troubleshooting.


Lifesaver when trying to locate duplicate slugs

Adds a column to admin posts/pages views showing the slug & URL path. Useful when titles are unclear or when many are too similar.

Change Core Slugs vs Admin Slug Column