Posts tagged change
Inbound Marketing & SEO – Seize Opportunity or Resist Change – Search Engine Watch
Mar 16th
 SEOmoz (blog) |
Inbound Marketing & SEO – Seize Opportunity or Resist Change
Search Engine Watch by Andy Betts, March 16, 2012 Comments Much has been written lately about SEO and its convergence with social media, content marketing, and other inbound marketing techniques. While many people in the SEO field embrace the convergence of social, … Investing in SEO and the Myth of Working Dollars Ten steps to a successful inbound marketing strategy |
View full post on SEO – Google News
SEO Positive Reviews Impact Of Google Privacy Policy Change – PR Web (press release)
Mar 4th
|
SEO Positive Reviews Impact Of Google Privacy Policy Change
PR Web (press release) In order to continue to provide its clients with a cutting-edge service, SEO Positive, like many other professional SEO companies in the UK, has announced that it will be researching the ways in which the executed changes to Google's privacy policy … |
View full post on SEO – Google News
Attorney Says Pinterest Needs To Change It Digital Copyright Policy
Feb 27th
Questions continue to mount about Pinterest’s uneasy relationship with copyright law, with one attorney (and avid Pinterest user) saying the company needs to upgrade its Digital Millenium Copyright Act policies or risk being shut down.
Connie Mableson, an attorney in Phoenix, offers a point-by-point breakdown of where Pinterest’s DMCA policy could get the increasingly popular social network into trouble. The problems range from simple clerical errors, like forgetting to update its registered designated agent as required by the act, to more serious problems, like failing to include “repeat infringer” language in the policy as required by federal digital copyright law.
Sponsor
“A few simple changes will make this DMCA lawyer much more comfortable knowing her pins will not suddenly disappear one day when Pinterest is out of business due to paying other lawyers exorbitant amounts of money to defend it against claims of copyright infringement,” Mableson wrote.
We’ve asked Pinterest to respond to Mableson’s blog psot and will update when they get back to us.
Mableson’s post was published on the same weekend that Flickr confirmed that its site upgrade included code that prevents Pinterest users from pinning copyrighted images. The move is significant, as Flickr is the third most popular site for Pinterest content.
“Flickr has implemented the tag and it appears on all non-public/non-safe pages, as well as when a member has disabled sharing of their Flickr content,” a Flickr representative told VentureBeat Friday. “This means only content that is ‘safe,’ ‘public’ and has the sharing button enabled can be pinned to Pinterest.”
To date, Pinterest has been relatively quiet on its copyright policies, and copyright attorneys have been divided on what liability users have when they share content on the site. While the DMCA allows publishers to avoid liability for content posted by users, the flaws pointed out by Mableson could nullify those protections.
View full post on ReadWriteWeb
BloomReach to Change SEO Technology? – Practical Ecommerce
Feb 24th
|
BloomReach to Change SEO Technology?
Practical Ecommerce That's the purpose of SEO platforms. They attempt to make search engine optimization more scalable, effective and efficient — across thousands of products and hundreds of thousands of search terms. Many measure different SEO metrics — such as raw … |
View full post on SEO – Google News
Add Change Tracking to Online Text Editing with Ice.js
Feb 8th
If you’re looking to add change tracking to a Web app, you might want to take a look at Ice from the CMS group at the New York Times.
Ice (or Ice.js) is an implementation of change tracking for any content-editable element on the Web. It can track changes (inserts, deletes) from multiple users, and has some optional plugins for converting “smart” quotes and creating em-dashes.
Sponsor
Hands-on experience is probably the best way to get an idea what Ice.js can do. The current demo shows a plain content-editable element with Ice.js as well as a TinyMCE instance using Ice.js as a plugin. The TinyMCE demo includes buttons for accept, accept all, reject and reject all.
Ice.js also has an API, so you could use it as the basis for your own custom editor or integrate it into an editor like TinyMCE. At some point, Ice.js should include code to integrate it with WordPress.
Ice.js looks pretty good so far, but the project is still in early days and the developer is calling for other folks to get involved adding features, plugins and documentation. The licensing for Ice may be a problem for some projects, however. The trend these days seems to be using MIT or BSD style licenses which do not require reciprocity, but Ice is GPLv2 only. This means that some projects won’t be able to adopt Ice due to their own licensing.
Change tracking is something that I’d like to see integrated in just about everything, so I’m hoping this takes off. Any other change tracking projects worth noting?
View full post on ReadWriteWeb
Do I Change My Site In The UK To Comply With New Cookie Laws?
Feb 7th
People are generally vaguely aware that debates have been taking place in Europe over new legislation which principally affects the use of “Cookies”. European legislation is inevitably more complex than elsewhere because of the way it is drafted by the European Commission and then…
Please visit Search Engine Land for the full article.
View full post on Search Engine Land: News & Info About SEO, PPC, SEM, Search Engines & Search Marketing
Future of SEO: Change, Convergence, Collaboration
Feb 7th
The way you work, the tools you use, and your approach to SEO has changed. Be open to changing the way you think about SEO and willing to change the way you view the search world. Take advantage of these opportunities, tools, and platforms.
View full post on Search Engine Watch – Latest
Future of SEO: Change, Convergence, Collaboration – Search Engine Watch
Feb 7th
 King of How To News |
Future of SEO: Change, Convergence, Collaboration
Search Engine Watch Like it or not, SEO has changed and its future relies upon a complex relationship with content marketing, social media, and collaborative technology. The end result is a whole new way of thinking about utilizing SEO and social media strategy and … Oylist Announce New Next Generation SEO Profit By Search, The Leading SEO Services India Reaches A Record Achievement … The SEO Copywriter and Search Engine Optimization |
View full post on SEO – Google News
Netflix’ Daniel Jacobson: Letting APIs Change Everything
Feb 3rd
What we today call the “mobile app” could, in a very short period of time, become known as the portable app, or just the “app.” It tends to use such a simple and straightforward model of interaction that people are starting to prefer using their smartphones for certain tasks, even when their PCs are right in front of them. By this time next year, portable apps originally designed for use on smartphones and tablets may be running on laptops.
The extent to which this changes everything is a topic that no one, not even ReadWriteWeb, has fully fathomed. The Web as we have come to know it will be affected significantly. What users have come to know as Web sites will be willingly and eagerly substituted with Web apps. In Part 2 of our interview with the co-author of APIs: A Strategy Guide, Netflix lead API engineer Daniel Jacobson tells us the one huge difference between an app and a site involves the extent to which they rely on an API. It is part of every app’s DNA.
Sponsor
The First, Painful Steps Toward Multi-Platform
In 2002, as you learned from part 1 of our RWW interview last week, when Jacobson was with NPR, he helped make a critical decision about its information infrastructure, the implications of which his team had not foreseen: “Literally the first thing that we did,” he tells RWW, “is, we built the API and we put the Web site on top of it. So the Web site runs off the API. It’s a little bit of a different interaction model; it doesn’t have to go through the authentication and whatever else, in the same way that external apps do.”
That API later gave NPR the freedom to build apps that run outside the browser, and that use that same API in different ways. So when mobile apps were invented, NPR was among the first publishers to be ready for them. When Netflix saw it needed an architecture that enabled it to reach all its users without it being dependent upon the usage model for any one device, including the Web browser, it hired Jacobson to build it.
A 2005 Netflix demo at a Microsoft convention featured one of that company’s program managers at the time, Darryn Dieken, showing then-President Jim Allchin the prospects of using one underlying technology as the foundation for developing a unified product line across different devices. The technology at the time was code-named “Avalon,” and evolved into what we now call Silverlight.
After showing how a Netflix product selector ran outside the browser but through the Web, in a way people had never seen before at that time, Dieken showed essentially the same selector running inside Windows Vista on a tablet PC. From there, he proceeded to show where else folks would eventually find Netflix.
The demo took the audience inside Windows Media Center, which had just been released for Windows XP and was being vastly updated for Vista. The Media Center plug-in used many of the same presentation techniques and concepts as the stand-alone version, demonstrating the benefits of code reuse.
But when the demo turned its attention to Netflix on a Windows Mobile phone, it became painfully obvious that the benefits of client-side code reuse could only go so far. Yes, there was communication taking place between all these different clients and the server. But the way these interactions were happening were based on leveraging Web site-oriented, forms-based submissions that at one level could be described as an API, but failed to be uniform – one API for many platforms.
The goal of any modern API, Dan Jacobson emphasizes, is “to treat any presentation layer the same. So if you have multiple Web sites, like NPR does (they have NPR Music as well as NPR.org), both of those sites run off of the same interaction model through the API. They’re just presentation layers, the same way as mobile app or Google TV or [NPR] Infinite Radio. Users are going to consume new material in any way that they want to, wherever, whenever; and your goal as publisher is to make sure that you have a presentation layer that serves them wherever that is. And in doing so, the easiest way, the most effective way to date is to leverage APIs, and invest a little bit on having the right talent surrounding it.”
“Publish Everywhere” Doesn’t Have to Be Homogenous
Because presentation layers are so different from one another, he goes on, a business can and should nurture teams of developers with the exclusive skillsets that each of those layers needs – for example, Objective-C developers for iPhone apps. There’s no reason why certain teams can’t specialize. Having a single API that addresses each layer in a standard way, he says, provides all your teams with the flexibility they require to take advantage of the platforms on which they’re focused.
This allowance for specialization tends to work itself away from the “one Web” way of thinking, the belief that everything will inevitably merge into HTML5. In professing that API design should not be centered around any one single mode of presentation, lest it eventually become obsolete (among other reasons), Jacobson advises that API designers focus on finding ways to symbolize and encode business interactions, the things that businesses do, not the things that Web sites do. Your goal is not to make the browser more efficient or the user experience more immersive. Leave that to the UX designers. As the API engineer, your goal is to enable business.
“That kind of thinking is fundamentally different than, ‘How do I want to structure my content? Do I need to think about what resources can be broken up in which ways and made available in different ways?’” says Jacobson. “For NPR, for example, there are stories, there are assets, different kinds of things in that system. For Netflix, there are users, catalog items. How do you want to structure that material, both in terms of the resource level as well as items underneath it? What are the rights management concerns that go into this, legal constraints internally about what can be published? For Netflix, what can I show users in Latin America that I can’t show to people in Canada? For NPR, it’s, I’m publishing AP photos; whom can’t I present that to, and whom can I? Those kinds of things are really business-oriented decisions that you can’t just flip a switch and say, ‘Make it happen.’ You need to be very thoughtful about what you’re exposing and to whom, and how you’re going to do it so you can get the maximum effectiveness out of it.”
It is this concept which may outmode, or render obsolete, the traditional notion of the Web site, the notion that something that’s created once and published everywhere (COPE) must always be the same thing. Done properly, Jacobson says, it can and should be integrated with the uniqueness of each device.
“When Web APIs started out, they tended to be more about publishing on all kinds of different platforms. Now I think it’s very much about aggregation, and merging others’ API experiences,” says the Netflix engineer. “One of the interesting things with Netflix, for example: We have branded apps on a wide range of platforms, and if you look at something like AppleTV or Roku or Xbox, or any of these other devices, we’re not the only ones there. There is an aggregation of services where Netflix creates an experience on that platform. We actually integrate with their systems, we’re creating an experience on that site, and then people can access our experience in the way they expect it to be presented.”
Next Time: A Lesson From the Entertainment Industry, “Know Your Audience”
View full post on ReadWriteWeb
How Social Media & Social TV Will Change Super Bowl 2012
Feb 3rd
This year’s Super Bowl will be more social than ever before.
With the rise of social TV and the first-ever 2,800-square-foot social media command center, fans who have trekked down to Indianapolis and people at Super Bowl parties across the country can now opt to have a super-connected experience.
This marks the first time that the NFL has partnered with a Super Bowl host city. Like a Midwestern truck stop that’s got a restaurant, convenience store, bathrooms, random coin-operated claw games (that you can’t ever win) and gas, the Super Bowl social media command center seeks to be all things to all football fans. Receive mobile updates about navigating the city. The Super Bowl Social Media Command center will answer your Twitter (@superbowl2012) and Facebook questions. Follow the blog here. It’s the customer service center of your Friday Night Lights dreams.
Sponsor
Tons of fans are already busy on social media. According to research from Nielsen and NM Incite, a Nielsen/McKinsey company, the Patriots’ website is beating the Giants’ website in terms of unique visitors. Giants fans, however, tend to spend more time on their team’s site – and they also view more pages. Giants fans are also talking more on social media about their quarterback, Tom Brady.
The Super Bowl is a Social TV Event
Various social TV apps are already available for Facebook. Entertainment social network GetGlue gives users an opportunity to check-in to sports events. ConnecTV is another free social platform that serves as a “second screen,” which means users can talk to friends while watching the Super Bowl. Users can sync shows, and then watch them with their friends while chatting in real-time.
The Super Bowl seems to be making up for the lack of social media at the London 2012 Olympics. In fact, not one of the Olympic volunteers can make a comment about the games without permission, according to Sysomos. At Super Bowl 2012, expect the exact opposite.
View full post on ReadWriteWeb
