It really depends if you want them connected or not.
In the Hugo example, completely agree. But sometimes it can make sense:
Example.com vs members.example.com vs login.example.com
Example.com can be a static website, while login attempts go to the login domain (which also helps for auth/postback config), and members might be the dynamic content that is viewable once logged in. separates infrastructure in an easy way that has no real impact on SEO
>Note on subdomains: every subdomain, to Google, is a different website. So if your domain is flaviocopes.com, and you create your blog in blog.flaviocopes.com, then that’s a completely new website to Google, and it will have its own ranking separate from the main domain.
So from a SEO perspective it might make sense, if you're running a small blog and traffic is one of your main goals.
These days nobody types an address into the search bar so any TLD that's not country based should be fine. I say that because your home country is a fluid concept.
In the Hugo example, completely agree. But sometimes it can make sense:
Example.com vs members.example.com vs login.example.com
Example.com can be a static website, while login attempts go to the login domain (which also helps for auth/postback config), and members might be the dynamic content that is viewable once logged in. separates infrastructure in an easy way that has no real impact on SEO