If you’re learning Laravel, one thing you’ll quickly notice is that the order in which you define routes matters.
Even small changes can break your application in ways that seem mysterious at first. Let’s break it down with an example.
How Laravel Matches Routes
Laravel checks your routes from top to bottom in your routes/web.php or routes/api.php file. It picks the first route that matches the URL and stops checking further.
This means:
- Specific routes should come first.
- Wildcard or parameterized routes should come after.
- Catch-all routes should always be at the very end.
Example: Route Order in Action
Here’s a complete example showing how route order affects what gets displayed:
<?php
use Illuminate\Support\Facades\Route;
// 1️⃣ Specific route first
Route::get('/user/profile', function () {
return "This is the profile page";
});
// 2️⃣ Parameterized route next
Route::get('/user/{id}', function ($id) {
return "This is user with ID: $id";
});
// 3️⃣ Another parameterized route with multiple segments
Route::get('/post/{slug}', function ($slug) {
return "This is post: $slug";
});
// 4️⃣ Catch-all route at the very end
Route::get('/{any}', function ($any) {
return "This is the catch-all page: $any";
})->where('any', '.*');What happens when you visit different URLs?
| URL | Matched Route | Output |
|---|---|---|
/user/profile | /user/profile | This is the profile page |
/user/42 | /user/{id} | This is user with ID: 42 |
/post/laravel-routing | /post/{slug} | This is post: laravel-routing |
/about | /{any} | This is the catch-all page: about |
/user/profile/edit | /{any} | This is the catch-all page: user/profile/edit |
What if the order is wrong?
If we swap /user/profile and /user/{id}:
Route::get('/user/{id}', function ($id) {
return "User $id";
});
Route::get('/user/profile', function () {
return "Profile page";
});Then visiting /user/profile will match /user/{id} first, so Laravel thinks "profile" is the {id}. The specific route never runs.
Output: User profile ✅ Usually not what you want.
Key Takeaways
- Put specific routes first — these are exact URLs like
/user/profile. - Parameterized routes next — like
/user/{id}or/post/{slug}. - Catch-all routes last — these are routes that match anything else.
- Route order affects request matching, not URL generation.
Laravel’s top-down route matching is simple, but if you forget about it, it can cause confusing bugs. Just remember: specific → parameterized → catch-all. Follow this rule, and your routes will behave exactly as expected.