Answers
Aug 30, 2017 - 05:32 PM
Hi Fadi,
I would recommend doing it the other way around -- host your 'blog' and marketing content on the root, and then host your app in a sub directory for example:
web app: example.com/app/*********
marketing website: example.com/example-page
Not sure how technical you are, but this type of setup can be accomplished with nginx or haproxy.
It's also fine to place your web app under a sub-domain. I'm assuming people will need to log into your app, so Google won't see the inside of your app anyways. If you think there's a UX benefit to 'clean' URLs then something like https://app.example.com/ is a pretty common practice.
In general, you want to avoid splitting up your website into multiple sub-domains as much as possible, because people will inevitably link to you, and it's useful to keep all the power in the root domain.
Let me know if you have any further questions or anything I can elaborate on, I'm happy to help.
I would recommend doing it the other way around -- host your 'blog' and marketing content on the root, and then host your app in a sub directory for example:
web app: example.com/app/*********
marketing website: example.com/example-page
Not sure how technical you are, but this type of setup can be accomplished with nginx or haproxy.
It's also fine to place your web app under a sub-domain. I'm assuming people will need to log into your app, so Google won't see the inside of your app anyways. If you think there's a UX benefit to 'clean' URLs then something like https://app.example.com/ is a pretty common practice.
In general, you want to avoid splitting up your website into multiple sub-domains as much as possible, because people will inevitably link to you, and it's useful to keep all the power in the root domain.
Let me know if you have any further questions or anything I can elaborate on, I'm happy to help.
Aug 31, 2017 - 12:45 PM
Hmmh, interesting Hayk. Are sub-domains treated as independent domains for SEO purposes? I thought sub.root.com is treated as part of root.com? Or does its power from back links get discounted since it is not on root proper?
We have the Q&As on capitalandgrowth.org and the investor interviews on blog.capitalandgrowth.org and for certain landing pages that use Unbounce.com we have them on info.capitalandgrowth.org since Unbounce needs a ‘virgin’ subdomain.
You think we should have everything on the root for long term SEO purposes?
We have the Q&As on capitalandgrowth.org and the investor interviews on blog.capitalandgrowth.org and for certain landing pages that use Unbounce.com we have them on info.capitalandgrowth.org since Unbounce needs a ‘virgin’ subdomain.
You think we should have everything on the root for long term SEO purposes?
Sep 19, 2017 - 01:35 PM
Yes, @Jasper Kuria different subdomains are treated as separate sites. Quite often there are technology issues, which will force a subdomain (for example blog.root.com because they can't run a WP instance on the root, or your Unbounce example).
If you're looking at it in the long term perspective, then yes merging the subdomains is best. If you look at this case study (scroll down to website architecture) they spell out how merging subdomains and adding subdirectories had a big impact. There are definitely instances where subdomains make sense, like the StackeExchange network's use of subdomains (finance is different from religion, and should be viewed a separate sites), but for a single domain, unless your goal is to hinder the performance of a specific section (or hide it in some way), subdomains should be avoided.
If you're looking at it in the long term perspective, then yes merging the subdomains is best. If you look at this case study (scroll down to website architecture) they spell out how merging subdomains and adding subdirectories had a big impact. There are definitely instances where subdomains make sense, like the StackeExchange network's use of subdomains (finance is different from religion, and should be viewed a separate sites), but for a single domain, unless your goal is to hinder the performance of a specific section (or hide it in some way), subdomains should be avoided.
Add New Comment