I am interested on thoughts about URL structure for city landing pages.
Essentially best practice and reasons for implementing format (a) over (b):
(a) example.com/chicago
(b) example.com/?_city=chicago
Asked
Active
Viewed 57 times
-2
unor
- 92,415
- 26
- 211
- 360
redmacgirl
- 13
- 3
-
2I voted to close this question because it is not a programming question and it is off-topic on Stack Overflow. Non-programming questions about your website should be asked on [webmasters.se]. In this case the question has already been asked and answered there: [Is a URL with a query string better or worse for SEO then one without one?](https://webmasters.stackexchange.com/questions/15393/is-a-url-with-a-query-string-better-or-worse-for-seo-then-one-without-one) – Stephen Ostermiller Feb 19 '22 at 09:49
1 Answers
-1
Using the path instead of the query component is typically considered to be more user-friendly. So go with (a):
/chicago
If you want to represent (in the URL) that it’s about cities (what (b) does), you can do this in the path, too:
/cities/chicago
This allows you to provide browsable URLs, i.e., offering a list of all cities at:
/cities
