Toro_Unit (Hiroshi Urabe)

Slug Automator automatically generates slugs from WordPress post titles using the <a href="https://make.wordpress.org/core/2026/03/24/introducing-the-ai-client-in-wordpress-7-0/" rel="nofollow ugc">AI Client</a> introduced in WordPress 7.0.
Writing post titles in Japanese or any other non-English language? Slug Automator uses AI to translate them into clean, English URL-friendly slugs — no manual input required. Automatic generation runs on publish only when the slug field is empty, so any slug you set yourself is never overwritten. You can also generate or regenerate a slug on demand with the “Generate Slug” button in the block editor.
Because it relies on the WordPress AI Client, it works with any AI provider configured on your site (Anthropic, Google, OpenAI, and more).
Github: <a href="https://github.com/torounit/slug-automator" rel="nofollow ugc">https://github.com/torounit/slug-automator</a>
<h3>Features</h3>
<ul>
<li>Automatically generates slugs from post titles via AI</li>
<li>Provider-agnostic — uses whichever AI provider is configured in WordPress</li>
<li>Works directly in the block editor</li>
</ul>

Slug Automator

Automatically generates URL-friendly slugs from post titles using the WordPress AI Client.

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.

Slug Automator vs Change Core Slugs