3

Subdomains do make it a little clearer for users which part of the site they're on (apart from breadcrumbs). For example, compare: answers.example.com with: example.com/answers/ With Google, you won't see any advantage in SEO with one over the other as of late. See this for more about that: Subdomains vs. subdirectories for SEO: No SERP benefits for ...


1

If ad revenue used to work, but isn't anymore, and you don't want to charge visitors an access fee, then the next most typical model is to sell the user data to someone interested in your user's demographics. But that would assume that you have some (probably somewhat private) information about your users. Other ways that are less tested, but possible ...


1

If this is not a SaaS you can prob do it like so: Make sure the community app folder is named "community" and lives inside the folder that your TLD is pointing to. Goto mysite.com/community and see if it works. If it doesn't, change the configs/settings in the community app to use the new URL scheme. Once its all linked and loaded, make a 301 redirect to ...


Only top voted, non community-wiki answers of a minimum length are eligible