Making the Mobile Web a Better Place: Outbrain and Google AMP

Over the past few months, Outbrain has been working with Google AMP project to address what’s always been a singular focus for this company: improving the user experience with content and how it’s discovered.

AMP has been around awhile and stands for “Accelerated Mobile Pages.” As the name suggests, it’s an open source initiative to build a faster, more beautiful open web – one that is sorely needed for audiences, advertisers and publishers who have shifted to mobile.

We know that the mobile user experience can often be clunky, slow and frustrating. AMP can largely put those days behind us, enabling publishers to create mobile-friendly content that loads instantly for consumers on any screen.

But for the publishing industry at large, AMP is also a chance to redeem some of the missteps that, if we’re honest, have led to an ugly advertising ecosystem that often pits audiences against publishers and advertisers.

A large part of our desire in working with AMP and adapting our network to its standards boils down to this redemption story.

How can we create an ecosystem where the interests of aforementioned constituents are aligned?

Where the assets publishers need to thrive are as beautiful as the content it compliments? How can we scale content distribution to eliminate any barriers to programming optimal experiences for audiences, with greater efficiency?

AMP is a major step toward that future, and by delivering Google AMP-powered recommendations for publishers, we’re proud to aid that step. Here’s a look at how Outbrain is incorporating publisher recommendations into the AMP standard:

Just a quick note to say that the code snippet above includes smart quotes. Those smart quotes will break an amp implementation if copied directly to a site. If you use the code above be sure to replace the smart quotes.