Hi there, Thanks for submitting this request. A company's knowledgebase represents an investment in user-support and is an opportunity for search engine positioning if implemented well. The contents and style would also be unique to the personality of your company. Our time might be better spent implementing new functionality in the core product vs. writing knowledgebase articles which you can do yourself.
What would the scope of the articles cover? As WHMCS can be used to sell just about anything, it is not realistic for us to provide documentation on every product in existence. We could potentially include some English language articles which describe common usage of the WHMCS client area?
Conversely a potential downside of implementing this might be that if every WHMCS installation contained the exact same knowledgebase content, it might penalise your SE positioning due to the duplicated content.
I'd be interested to hear user's thoughts on those points.
1 Comment
Login to post a comment.
Thanks for submitting this request. A company's knowledgebase represents an investment in user-support and is an opportunity for search engine positioning if implemented well. The contents and style would also be unique to the personality of your company. Our time might be better spent implementing new functionality in the core product vs. writing knowledgebase articles which you can do yourself.
What would the scope of the articles cover? As WHMCS can be used to sell just about anything, it is not realistic for us to provide documentation on every product in existence. We could potentially include some English language articles which describe common usage of the WHMCS client area?
Conversely a potential downside of implementing this might be that if every WHMCS installation contained the exact same knowledgebase content, it might penalise your SE positioning due to the duplicated content.
I'd be interested to hear user's thoughts on those points.