Skip to content
This repository has been archived by the owner on Apr 13, 2021. It is now read-only.

URL best practices #1

Open
gregersrygg opened this issue Sep 7, 2015 · 4 comments
Open

URL best practices #1

gregersrygg opened this issue Sep 7, 2015 · 4 comments

Comments

@gregersrygg
Copy link

We should document a best practice for how we build up URLs at FINN.no. As a start, we should list the different topics this should cover:

  • Casing - snake_case or lowercase? not camelCase
  • Readable/memorizable
    • Should ID be part of the path or a query-parameter?
    • SEO
  • Avoid adblock easylist
  • Norwegian? What about æøå or other characters?
  • Other?

Other URL guidelines:
https://support.google.com/webmasters/answer/76329?hl=en
https://moz.com/blog/11-best-practices-for-urls
http://www.raisedeyebrow.com/blog/2014/06/url-structure-best-practices

@hzr
Copy link
Contributor

hzr commented Sep 7, 2015

Casing - snake_case or lowercase? not camelCase

with-dashes

@ivarconr
Copy link

ivarconr commented Sep 7, 2015

yes, hyphens!

We recommend that you use hyphens (-) instead of underscores (_) in your URLs.

https://support.google.com/webmasters/answer/76329

@twidero
Copy link

twidero commented Sep 15, 2015

Når vi først skal gjøre noe med URL'ene bør vi også strebe etter like url'er i web og app, slik at det er enklere å analysere bruken på tvers av medier, og gjøre de mer søkemotorvennlige, som f.eks. at det bør hete eiendom/bolig i stedet for realestate/homes.

@whirlwin
Copy link

I think it's useful to have Norwegian URLs, as the content of the pages are primarily in Norwegian. Think about it, in an article, you wouldn't use a different language in a headline and the content below the headline.

Also: http://stackoverflow.com/questions/2742852/unicode-characters-in-urls

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants