LS Staging

Tag: google amp

  • Google AMP team comes up with ‘Render On Idle’ feature

    Google AMP team comes up with ‘Render On Idle’ feature

    Businesses and publishers will welcome the new move by Google AMP team that has launched some new features recently. One such feature is the ‘Render on Idle’ feature. This will load ads faster and lead to higher ad impressions when the browser is in the idle mode. The ads would load 12 viewports in this feature as opposed to 3 in the past. This facilitates better visibility on the ads because they load earlier in the page load lifecycle.

    A look at AMP

    For the uninitiated, Google AMP is an open standard that favours mobile-centric internet browsing and ad serving. An AMP page will have faster page load on mobile devices. In 2016, this technique was also integrated into search engine ranking signals and thus, impacted the SEO fortunes of companies.

    Once the AMP page is created, you can serve ads using the <amp-ad> tag. When the type is DoubleClick or DFP ads, you can turn on the ‘render on idle’ feature and start serving ads even when no other content is being loaded.

    As an outcome, there is a marked increase in the number of impressions with a limited increase in clickable impressions and eventual clicks. This is expected to provide more useful analytics to publishers too. If you are a publisher using DoubleClick AMP Ad tag or any tag that uses FastFetch ad request and rendering, then you would see the tangible effect of this feature in play. Publishers who have used this feature reported a 13% increase in impressions and 0.5% increase in clicks and viewable queries.

    There are two scenarios that will not allow ‘Render on Idle’ to run (as these force delayed Fetch which doesn’t go with this feature):

    1 – Using remote.html

    Rectify this by using Real-Time Config. This facilitates integrations with other technology partners

    2 – Using ‘useSameDomainUntilDepracated’

    Rectify this by removing this attribute from the tags and instead use SafeFrame API

    With this feature, Google and AMP are making it easier for publishers to monetise their businesses and earn potentially more from their ads. If you are on the Delayed Fetch, then you need to move to Fast Fetch for the ‘Idle on Render’ feature to take place.

  • Google’s new AMP testing tool: What you need to know.

    On 13th October, Google announced the launch of a new testing tool for accelerated mobile pages (AMP). The tool works on mobile devices with the help of Google’s ‘live web search infrastructure’ and analyses the AMP pages real-time using Googlebot. The tool helps with testing the validity of structured data and markup on the page.

    It also has links that show a live preview of how the page appears in Google’s search results, and if you find any issues, you can click on them to see the source code and understand where the errors lie. You can check your site here: https://search.google.com/search-console/amp

    Source:

    https://goo.gl/1fhaKw

    https://goo.gl/xYa7wa

  • Google announces Accelerated Mobile Pages (AMP) will trump App Deep Links

    Google announces Accelerated Mobile Pages (AMP) will trump App Deep Links

    Speaking at SMX East, held recently in New York, the head of Global Product Partnership at Google, Adam Greenberg revealed that AMP pages will “override app deep link”. For example, if you are a publisher whose website has AMP (Accelerated Mobile Pages) URLs activated and if you have a mobile app with Google App Indexing, users who download your app will be able to view the AMP URL instead of the deep link to the content contained in your app.

    amp_google_deep_linking

    Google’s Senior Webmaster Trends Analyst John Muller too confirmed this statement by tweeting—

    Recently, Google was in the news for carrying AMP to the core mobile search results. However, the tech giant was quick enough to make notable changes to its project soon after the rollout. As per the changelog, AMP will override app deep links.

    Google has taken several initiatives over the years to promote App Indexing by encouraging app developers to incorporate deep links to their apps along with App Indexing. But presently, if you have deployed both AMP and App Indexing to your website, Google search results will prefer to show the AMP pages above the deep link to your app pages.

    What Made Google Update Its Changelog Soon After the Rollout?

    Reiterating on the immediate and quick update, Google said that they have taken this decision because AMP helps them deliver their services in a better way because of its reliability and speed, besides helping Google enhance the user experience. The tech giant further said that Accelerated Mobile Page uses ten times less data compared to a non-Accelerated Mobile Page. Moreover, AMP utilises smart caching to ensure content and advertorials are displayed flawlessly.

    LogicSpeak:

    As mentioned above, Google believes people like AMP pages as they load pretty fast and consume 10x less data compared to non AMP pages. To provide a faster experience, Google is planning to show your AMP pages over the deep link to the page. In simple terms, if your user has downloaded your app and you have the deep linking in place; at the same time if you have created AMP pages, Google will serve the AMP pages above the deep link to your app pages. This can reduce traffic to your app pages.

Powered by
►
Necessary cookies enable essential site features like secure log-ins and consent preference adjustments. They do not store personal data.
None
►
Functional cookies support features like content sharing on social media, collecting feedback, and enabling third-party tools.
None
►
Analytical cookies track visitor interactions, providing insights on metrics like visitor count, bounce rate, and traffic sources.
None
►
Advertisement cookies deliver personalized ads based on your previous visits and analyze the effectiveness of ad campaigns.
None
Powered by