This PR adds first-party support for automatic slug generation on Eloquent models via a simple #[Sluggable] attribute.

Getting Started

To make an existing model sluggable, run the make:sluggable Artisan command:

php artisan make:sluggable Post

This command adds the #[Sluggable] attribute to your model and generates a migration for the slug column. It introspects the model's table to guess the source column (name, title, headline, or subject):

+#[Sluggable(from: 'title')]
class Post extends Model
{
    //
}

That's it. After running php artisan migrate, when a Post is created, a slug will be automatically generated and stored in the slug column:

$post = Post::create(['title' => 'Hello World']);
$post->slug; // "hello-world"

The command also accepts --from and --to options:

php artisan make:sluggable Post --from=headline --to=url_slug

Configuration

Every aspect of slug generation can be customized directly on the attribute.

Important: The generated migration creates a simple, unique string column. You may need to tweak it depending on your slug configuration — for example, removing the unique() constraint if unique: false, or when using scope. The same goes when adding the #[Sluggable] attribute to a model with existing data — you may need to backfill slugs before applying a unique constraint.

from

By default, the slug is generated from the name column. You may customize this using the from parameter:

#[Sluggable(from: 'title')]

Slugs may also be generated from multiple columns by passing an array:

#[Sluggable(from: ['first_name', 'last_name'])]
class Author extends Model
{
    //
}

$author = Author::create(['first_name' => 'John', 'last_name' => 'Doe']);
$author->slug; // "john-doe"

to

By default, the slug is stored in the slug column. You may customize this using the to parameter:

#[Sluggable(from: 'title', to: 'url_slug')]

scope

When slugs should be unique within a scope (e.g., per team or per locale), you may provide one or more scope columns:

#[Sluggable(scope: 'team_id')]

Multiple scope columns are also supported:

#[Sluggable(scope: ['team_id', 'locale'])]

onUpdating, separator, unique, maxLength, etc.

The attribute accepts several other options to fine-tune slug generation behavior. By default, slugs are generated on creation but not on update, use - as a separator, enforce uniqueness with up to 100 attempts, and have no maximum length:

#[Sluggable(onUpdating: false, separator: '-', unique: true, maxAttempts: 100, maxLength: 60)]

When onUpdating is enabled, the slug is regenerated whenever the source column changes. When a slug value is manually provided, it is always preserved — both on creation and on update.

errorKey

When slug generation fails, a CouldNotGenerateSlugException is thrown. In HTTP contexts, this exception automatically renders as a 422 validation error response — just like a failed validation rule. The error is attached to the first source column by default:

This works auto-magically in blade, livewire, inertia, etc

{
    "errors": {
        "name": ["The name cannot be converted into a valid slug."]
    }
}

You may customize the error key using the errorKey parameter:

#[Sluggable(errorKey: 'input_name')]

The error messages may be customized by publishing and modifying the validation.slug_required and validation.slug_unique translation keys in your application's language files. Both keys receive
:attribute and slug replacements:

// lang/en/validation.php
'slug_required' => 'The :attribute cannot be converted into a valid :slug.',
'slug_unique' => 'Too many :slug entries exist for the given :attribute. Please try a different value.',

Since it extends ValidationException, the exception is not reported to the application log — consistent with how Laravel handles ModelNotFoundException and other eloquent exceptions.

Slug Generation

The slug generation pipeline transliterates Unicode characters (including CJK scripts) into their Latin equivalents, preserves dots (useful for domain-like values such as laravel.com), and converts special characters into clean separators.

Here are a few examples of what the pipeline handles:

• Basic text: Hello World → hello-world
• Accented characters: Café Résumé → cafe-resume
• German: Straße → strasse
• Chinese: 如何安装 Laravel → ru-he-an-zhuang-laravel
• Japanese: こんにちは → konnichiha
• Korean: 안녕하세요 → annyeonghaseyo
• Russian: Привет Мир → privet-mir
• Dot preservation: laravel.com → laravel.com
• Subdomains: sub.domain.example.com → sub.domain.example.com
• File extensions: document.final.pdf → document.final.pdf
• Unicode with dots: über.straße → uber.strasse
• Special characters as separators: Example/Path → example-path
• Typography: Hello — World → hello-world
• Emojis: 🎉 Hello 🌟 World 🚀 → hello-world
• Mixed real-world input: [2024] Annual Report (Final) → 2024-annual-report-final