Consistency and predictability Most APIs, CMSs, and web frameworks use plural resource names: /users/123, /posts/42, /articles/hello-world, /profiles/gabohbeaumont.
This makes routes consistent and easy to guess.

Hierarchical clarity The path reads naturally as “inside the collection of profiles, find the one called gabohbeaumont.”
This matches how routing and file systems are structured.

Scalability You can easily extend the pattern: /profiles/ → list all profiles /profiles/new → create a new profile /profiles/{id} → view or edit one profile
No need to invent exceptions later.

SEO and crawling Search engines interpret plural directories as category containers, such as /articles/ or /products/.
This improves crawlability and clarity of structure.

Convention over configuration Using the same convention as most frameworks (Next.js, Rails, Django, Laravel, etc.) means automatic compatibility. For example, /profiles/ often maps directly to a profiles controller or folder.