Facebook, Reddit, Telegram, Gab, Twitter, LinkedIn, Instagram, WhatsApp are just a few of the hundreds of platforms which features consumers who businesses try to connect with.
This article explores why SEO is not enough to drive traffic to many websites, lays out the goals of using social media to drive traffic, and discusses an approach we are adding into our Web Data Platform shortly.
Utopia means, no such place. For any company selling goods and services online, their "no such place" is to be number 1 on Google and to have a high conversion of paying happy customers that visits their website.
This article is not about using SEO to get ranked on Google, but our experience shows us that;
There are some tricks to improve your SEO rankings, but we don't want to focus on that - indeed, tricks can result in blacklisting from Search Engine Providers.
Our one effort we try to do is to add content and articles which discusses topics we think will interest potential customers.
It is our strong opinion that Google won't help many businesses increase revenue, even if paying. Please look at Seth Godins explanation on why pay per pick (ppc) advertising can be incredibly expensive.
A Social Media Platform attracts users wanting to interact with other users. SMPs create a specific type of user experience where they engage in a particular way. Contrast the Facebook wall versus the twitter thread. Other SMPs focus more on visuals, to create a vibe. There are professional platforms. We have started to look at technology platforms to try and interact with other users for collaborative purposes. Even GitHub is a social media platform.
The one thing that really stands out with most of these platforms is they are a point in time platform. They stream new information constantly, to drive interaction. This engagement is what produces data to give these platforms insights that they can sell. What happened a week ago on Twitter no longer matters, what happened ten minutes ago on signal won't be seen. Instagram and Pinterest encourages users to look around a bit more, but largely, these are point in time platforms.
Websites on the other hand are more about providing quick access to most facets of an organisation. It is expected that many users may read large parts of your website to understand more about your organisation. Websites move slower and are more reflective, users absorb content to support their decision making process.
LinkedIn does seem to achieve a balance between the point in time versus reflective platforms.
We see it that two things have to happen for social media to be effective for a company wishing for their online presence to drive customers to their website.
We have a cyclical need. Ideally, highlights of important publications should be accessible on any platform and easy to access. Which is why a company who publishes a lot of content on a Social Media Platform may benefit by having a neat summary page of this information on their own website.
Some SMPs provide ways to plug content from your own SMP account into your website, but still, they may not be sufficient to give a quality overview.
Imagine you are a business who sells tickets, ideally, your customers should be able to understand the events that were put on previously. Your current ticket availability should be present on all platforms. Perhaps the performers themselves, when discussing attending your event should appear within your website.
In most situations there will be many systems and functions;
Whilst not exhaustive, there will be lots of duplication of effort. Significant expenditure will be made linking these systems up.
There is an easier way.
Nobody can state with certainty what the right way to drive paying customers to a website should be. The one challenge we see is that social media can become a big burden to businesses, especially when on several platforms. A lack of engagement and new publications can make your customers think you aren't active.
We are keen to add this Social Media capability into our platform, but are interested in knowing what you think.
Written with StackEdit.