Create valuable, useful content for your audience and people will be more inclined to link to your website. This content will help you attract more inbound links. We all know that inbound links are a key piece of the ranking puzzle.
This is a simple, yet key strategy to assist any website owner with their SEO efforts.
At the Bing Search Summit, Microsoft alluded to the impact that social networking websites are having on search results. Although acknowledged in the very early stages of implementation, this assessment is key in the next step in the SEO ‘game’.
Bing is using social annotations, like the Facebook “Like”, to become a ranking factor. In time they see this creating a better personalized search results.
This information is solid proof that you shouldn’t overlook Facebook and the other social networking sites when planning your upcoming marketing efforts. As so many marketers, SEOs, and web developers suggest; ignoring social media will get you left in the cold.
I was recently asked by a friend to assist with some troubles on their wordpress.com site regarding embedding video. Now when it comes to embedding video from YouTube, we all know that you have to paste the embed code into “HTML” tab in your WordPress editor. Otherwise WordPress tries to “fix” the copy and will break the embed code. For the number 2 video site on the web, Vimeo, you would like to think the embedding process would be similar. Well unfortunately that thought is wrong!
So let get to it. How do you embed a Vimeo video into a blog post on a wordpress.com hosted blog?
For a wordpress.com hosted blog, the answer is a shortcode.
[vimeo 123456]
Using the above shortcode (replacing 123456 with the actual id of the video) you can embed a Vimeo video into the blog post. The shortcode is not view specific. So you can enter it from the “Visual” or “HTML” tab. A simple solution to a mega problem.
Note: the shortcode is not core functionality in a self hosted WordPress. A plugin and theme alteration would be required for a self hosted install.
A thanks to @DanaMNelson for sparking this conversation point.