# Why does the logo navigate to Discourse home not main site home

**URL:** <https://meta.discourse.org/t/why-does-the-logo-navigate-to-discourse-home-not-main-site-home/316187>\
**Category:** UX\
**Created:** [July 13, 2024, 6:10pm UTC](https://meta.discourse.org/t/why-does-the-logo-navigate-to-discourse-home-not-main-site-home/316187 "2024-07-13T18:10:17Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![gilgongo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gilgongo/32/330356_2.png) [@gilgongo](https://meta.discourse.org/u/gilgongo)\
**Post date:** [July 13, 2024, 6:10pm UTC](https://meta.discourse.org/t/why-does-the-logo-navigate-to-discourse-home-not-main-site-home/316187/1 "2024-07-13T18:10:17Z")

</div>

_I’m not sure if this is UX or Support, but will try here._

Is there a reason why the Discourse navigation assumes it’s the only host on a domain?

I ask because the vast majority of Discourse deployments are subordinate to a “parent” site (eg [www.domain.com](http://www.domain.com)) and have to put their Discourse site on another subdomain (eg [support.domain.com](http://support.domain.com)). So the Discourse UI “home” link goes to the top of the subdomain that _Discourse_ is on, not the _parent_ site (which is the convention in all other web contexts).

The UX of this always trips up new users with a sort of “lobster pot” effect when they want to return to the parent. Most resort to mashing on the back button to get back, hacking the URL in their browser, or abandoning and trying to get back by searching (again in most cases) on Google.

There could be a few approaches to mitigate this, and obviously this issue isn’t unique to Discourse. But since Discourse is the best web discussion system in the world, I thought I’d ask here first.

---

_[View the full topic](https://meta.discourse.org/t/why-does-the-logo-navigate-to-discourse-home-not-main-site-home/316187)._
