Is it better to have product documentation for users at subdomain <http://docs.pagename.com|docs.pagename.com> or rather at route <http://pagename.com/docs|pagename.com/docs> ?

All Questions

Is it better to have product documentation for users at subdomain http://docs.pagename.com|docs.pagename.com or rather at route http://pagename.com/docs|pagename.com/docs ?

author Dobroslav Radosavljevič

Reply

9 Answers

Doesn’t really matter as far as I can tell. The SEO stuff is the same for subdomains as normal domains

writen by Iain Cambridge

I’m asking because everyone doing it differently 😊 So I’m not sure, what to pick

writen by Dobroslav Radosavljevič

I think people only put it on a sub domain because their docs are a separate repo and it’s easier.

writen by Iain Cambridge

> The SEO stuff is the same for subdomains as normal domains I’m not sure about this though

writen by Daniel Nguyen

See this: https://www.unrvld.com/viewpoint/subdomains-vs-subfolders-and-cctlds-vs-tlds-for-seo

And I got advice from multiple people suggest to put it on TLD

writen by Daniel Nguyen

Interesting article! Thanks

writen by Dobroslav Radosavljevič

Doesn’t matter, but I would do this as a subdomain, because then I can put it on a different server or use a different technology to serve documentation, than the SaaS itself.

writen by Aidas Bendoraitis

I#ve done both. I have http://getparthenon.com|getparthenon.com for blog/docs then customers.parthenon.cloud for the Parthenon management stuff.

But then for http://repohealth.io|repohealth.io I used nginx reverse proxy to proxy a subdomain to the docusauraus install

writen by Iain Cambridge

Daniel Nguyen Never thought about this from a SEO perspective. Maybe that’s my mistake with the 1st things 1st.

writen by Aidas Bendoraitis

Do you want to ask a question?

Related Questions