With it, the browser has permission to serve that content and will attribute it to the publisher. Now, a publisher can sign an HTTP request-response pair that corresponds with their domain. The idea is that it can determine who the original publisher was, no matter where the document initially came from. Signed exchanges are a technology that gives publishers a way to prove the authenticity of a web document. The signed exchange functions as a solution to this problem, allowing brands to publish their content using their own domain, while still reaping the benefits of AMP page treatment.Īccording to Google, the signed exchange allows publishers to use Google AMP while “still keeping the content’s integrity and attribution.” In the past, Google required users to submit content through the platform’s cache, stating that this allowed them to ensure that content was trustworthy and that it didn’t violate user privacy without their consent. Which, as you might imagine, could compromise the neutrality of the search results. Opting into AMP meant attaching a Google URL to your website’s content, in exchange for preferential treatment. Those articles are served up from the Google cache, inside the Google search results, with a Google URL. In an open letter to Google, digital publishers stated that they don’t have a problem with AMP as a concept, but had concerns over Google using the platform as a ranking factor to drive adoption among content creators.Īccording to the article, AMP articles get the top spot in the search results and a lighting icon that indicates speed. Publishers felt that AMP was forcing them to give up control over their distribution to Google, as AMP users were forced to distribute content under Google’s domain. However, web publishers have long had concerns about the implications the initiative might have on the future of the internet. The URL Problem With Google AMPĪt a glance, Google’s AMP seems like an improvement to the mobile web, which still doesn’t provide a consistently good experience. Until recently, AMP pages served up from Google’s AMP cache have turned up URLs that look like this. Google AMP Cache, which serves up AMP pages in the search results.AMP JS, responsible for fast load times.AMP HTML, which refers to the actual code.The benefit is we’ll likely see the format develop faster than it would in a closed system-plus publishers can adjust the code to their own specifications.ĪMP code is made up of three core components: Anyone can contribute to the code or make modifications as they see fit. While AMP was initiated by Google, the project is open-source and compatible with other platforms like Firefox and Bing. Meaning, when you click a link, you don’t have to wait for the article to load because it’s already been pre-loaded in the app. The idea is to provide a universal standard for mobile, where pages load quickly and consistently.ĪMP HTML cuts out surplus code and features that contribute to lags. The simplest explanation is that AMP is a pared-down version of HTML designed for mobile web pages, though it’s worth noting that it works on desktop, too. So, What Exactly, Is Google AMP?ĪMP has been a hot topic for quite some time now, yet there’s still some confusion as to how the speed-delivery system actually works. Google responded to this issue by rolling out a way to connect your own domain to the AMP web results, through a process called signed exchanges. Which, if you’re sharing URLs on multiple platforms, presents a problem. Until recently, those AMP-ed up results came with a Google-branded URL instead of the publisher’s original domain. Google offers more visibility to those publishers using AMP than those who have yet to hop on the bandwagon. The key benefit of using Google’s AMP is that it speeds up webpage load times – we’re talking less than a second – which results in fewer visitors abandoning ship due to impatience.ĪMP content also gets special treatment when it comes to the SERPs. Today, thousands of websites are publishing AMP content across millions of webpages, delivering preloaded content to users in under a second.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |