<p>It doesn’t matter to Craft, but generally I think it’s better to have consistent URLs, so they can be discoverable. For example if you land on /places/place-name, it would be reasonable to assume that you could chop off “place-name” and find an index of all the places at /places/.</p>

CC BY-SA 3.0
2014-07-15T18:03:34.070Z
Yeah the more I think about it, the more I agree with you. Cheers!
Seán O'Grady
CC BY-SA 3.0
2014-07-15T17:12:14.027Z
2014-07-15T17:12:14.027Z
Brandon Kelly
<p>Lets say I have a channel called places, which has the following URL : </p>

<pre><code>http://example.com/places
</code></pre>

<p>The url points to a directory of individual places.</p>

<p>However, when you click into an entry, each entry is a place, so it might make more sense to have each entry's url to be : </p>

<pre><code>http:/example.com/place/place-name
</code></pre>

<p>Am I right in assuming that the best way to go about this would be to use a route for <strong><code>entries</code></strong>? Or is it best practice to keep things the same for consistency?</p>

CC BY-SA 3.0
2014-07-15T17:29:01.090Z
Follow-up question: what is common practice if you decide to keep them the same: `http://example.com/place` & `http:/example.com/place/place-name` or `http://example.com/places` & `http:/example.com/places/place-name`?
carlcs
CC BY-SA 3.0
2014-07-15T17:35:14.093Z
Plural is much more common.
Brandon Kelly
<url><slug>
Should I pluralize a channel's index slug?
# Should I pluralize a channel's index slug?

(Asked by: username_0 on 2014-07-15)

Lets say I have a channel called places, which has the following URL : 
http://example.com/places

The url points to a directory of individual places.
However, when you click into an entry, each entry is a place, so it might make more sense to have each entry's url to be : 
http:/example.com/place/place-name

Am I right in assuming that the best way to go about this would be to use a route for entries? Or is it best practice to keep things the same for consistency?

**Tags:** url, slug
> **Comments:**
> **username_1**: Follow-up question: what is common practice if you decide to keep them the same: `http://example.com/place` & `http:/example.com/place/place-name` or `http://example.com/places` & `http:/example.com/places/place-name`?  
> **username_2**: Plural is much more common.  

---

## 1 answers

### Answer by username_2 on 2014-07-15. Score: 11 | Accepted answer

It doesn’t matter to Craft, but generally I think it’s better to have consistent URLs, so they can be discoverable. For example if you land on /places/place-name, it would be reasonable to assume that you could chop off “place-name” and find an index of all the places at /places/.

> **Comments:**
> **username_0**: Yeah the more I think about it, the more I agree with you. Cheers!  

---

