Itqualityassurance
- Should app be on subdomain?
- Is it better to have subdomain or domain?
- Should API be subdomain or path?
- Why do people use www subdomain?
Should app be on subdomain?
Keep your API on the same subdomain as your app (for now)
For that reason, unless the API is the absolute core of your app (as opposed to just a means to integrate with it), I would recommend keeping it under the same subdomain as your main portal app for your first release.
Is it better to have subdomain or domain?
The subdirectory strategy concentrates your keywords onto a single domain while the subdomain strategy spreads your keywords across multiple distinct domains. In a word, the subdirectory strategy results in better root domain authority.
Should API be subdomain or path?
Your API endpoint is your website
You don't need a subdomain for your API, like api.example.com or a sub-path, like example.com/api . Your endpoint should be the root of your webpage: example.com . This is useful, because as discussed above the URL should be both the identifier as the locator of a single resource.
Why do people use www subdomain?
It is mostly used to separate cookies from the other subdomains. If you are going to use cookies, definitely keep the www. . You can always use an 301 redirect to redirect the short domain to the one with www. , that way your users don't have to type it.
