3

Stack Overflow continues to get a decent number of Salesforce questions, probably because it is better known. For example, there have been over a dozen new questions just this week. Some are getting answered, but the vast majority have 0 votes and 0 answers. The [Salesforce] tag description on SO includes a link to this site, but how many users read tag descriptions when writing a question?

This question has been asked here before back during Beta, but this site has been out of Beta and producing many high-quality questions and answers for years.

Should we try to steer that traffic here? If so, what can we do about it?

1 Answer 1

4

The more I think about this, the more I believe we shouldn't steer them here.

When we were in beta it made sense because most people didn't know about Salesforce SE, so there was an education process required, and there wasn't as much content to find via a web search.

You've got to ask yourself why they're posting on SO rather than here.

To me, it's got to be because they're not trying to find an answer before posting their question. This is exactly what we don't want. Steering them here will create more duplicate and/or low quality questions, requiring moderation and making it hard to find authoritive answers.

They will find Salesforce SE if they actually search, because whatever question they have will have been asked in some form before. It's usually just variations that people get stuck on these days. Even if it's not a variation, there is so much Salesforce specific content on here that any web search for Salesforce questions nearly always has Salesforce SE as a search result.

If we were to steer them here, I believe it would be counter productive to just send them to the Salesforce SE home page. It would only work if we sent them to the relevant answer to their question, which is a lot more work than just a quick comment on their question pointing them to Salesforce SE.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .