Which site_name should we have?

Which site_name should we have?


First, there's meta site_name in html:

<meta property="og:site_name" content="BroDude.ru">

Also, you can check the page title:

7 повседневных способов убить свои мозги | BroDude.ru

So I think it makes sense setting site_name to BroDude.ru here.

But it looks like someone won't agree with me, the second template set site_name to BroDude, of course he is going to report me an issue :) Now I'm confused. Since there's no clear rule here. We spent so many time fixing all those hard problems, just don't expect a little thing like site_name take us down.

So I collected some similar issues from other templates.

  1. https://instantview.telegram.org/contest/kurir.rs/template16/issue3/, in this template, site_name is set to domain (kurir.rs) since it's presented in og:site_name.
  2. https://instantview.telegram.org/contest/origo.hu/template28/issue1/, and in this template, site_name is set to short one Origo because although site_name is presented in HTML but with its value http://www.origo.hu/ which is obviously too long to be a site_name, so it makes sense too.
  3. https://instantview.telegram.org/contest/oggitreviso.it/template39/issue1/ in this case, no og:site_name presented, so it's set to Oggitreviso, looks like they get it from title.

So thing become a litter clear then:

  1. When no og:site_name in HTML, we should set it ourself. But this is complex, we could argue a lot like here https://instantview.telegram.org/contest/astera.ru/template21/issue2/
  2. When og:site_name is presented, and it's suitable for site_name in IV, like kurir.rs, then we're ok with it.
  3. When og:site_name is presented, but its value not suitable for site_name, for example http://www.origo.hu, it's a whole domain with http, so it's not suitable. We should again make our decision.


Report Page