Toro_Unit (Hiroshi Urabe)

<p>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.</p>
<p>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.</p>
<p>Because it relies on the WordPress AI Client, it works with any AI provider configured on your site (Anthropic, Google, OpenAI, and more).</p>
<p>Github: <a href="https://github.com/torounit/slug-automator" rel="nofollow ugc">https://github.com/torounit/slug-automator</a></p>
<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.

Redwoodcity

<p>When a post title contains multi-byte characters (such as Japanese), WordPress generates a URL-encoded slug like <code>%e3%81%82...</code>, which results in a long and unreadable permalink.</p>
<p>This plugin replaces such auto-generated slugs with <code>{post_type}-{post_ID}</code> (e.g. <code>post-123</code>). A multi-byte slug is kept as-is when the user has explicitly specified it.</p>
<h4>Usage</h4>
<ol>
<li>Go to “Settings” -> “Default Permalink” in the WordPress admin.</li>
<li>Check “Enable” and save changes.</li>
</ol>


Default Permalink

Prevents multi-byte (URL-encoded) slugs in the default permalink. Multi-byte URL can still be used when the user explicitly specifies it.

Slug Automator vs Default Permalink