Yandex and Google homepage widgets

    In order to attract additional traffic for one of his projects, he created a widget on the main and competing platforms of the Russian Internet.
    In this topic, widgets are simple HTML and Javascript applications that are embedded on the main Google and Yandex pages, respectively. Each of the vendors provides a fairly simple API for writing such applications.

    I would like to dwell on the differences in approaches that I noticed in the course of my work.

    Minimal file set


    For Google, I limited myself to two files. One xml file contains information with a widget description, a title, custom options, and client-side javascript code. This code, using API calls and taking into account client parameters, takes the xml that is generated on my server and displays it in the assigned iframe already. The second file is engaged in the formation of this xml.
    With Yandex, it's almost the same. But since the "stand-alone" approach for my case did not work, the displayed html is formed completely on my server. And accordingly, the client code remains on my side, and only meta descriptions of the widget are uploaded to Yandex.

    Caching


    By default, when using the Google APIs, my server does not access my data every time. Instead, my server’s xml response is cached and pushed to the widget at runtime. This greatly increases the speed and reliability of widget execution, as relieves of unnecessary dns-resolving, reduces the load on my server and relieves me of unnecessary hiccups during shutdown of my server. Yandex does not provide this.

    Internationalization


    The Google API allows you to implement a widget for various language locales through the use of textual substitutions. True, I had problems with the internationalization of the settings page. Yandex works exclusively in a monolingual environment.

    After the widget is ready


    Once the widget is ready, it should be placed in the appropriate directories and made available to users. Any developer can add to the Google directory. I will say that removing from the directory turned out to be more difficult than adding. The previous version hangs in the catalog, although it confidently gives 404 errors. :).
    Yandex is formally taken to the Yandex catalog only if your widget has more than 150 users, but my widget (at the initiative of the catalog moderators) was taken without this bar. Yandex also has a regional program, that is, if your widget provides access to any geographically relevant information, then you can specify this and get some advantage for the target audience.
    And after that, it would be nice for us to have feedback with our users. And here, too, the conditions are different. On the widget page in the Google directory, the user has the opportunity to rate the widget on a five-star system, leave a review and even contact the author. Here we can observe an estimate of the number of widget users. However, in my case, this assessment is very concise - it just says <100 users.
    Yandex does not provide any feedback options. But the information on the number of users gives accurate to the user.

    And also?


    And Google also allows webmasters to embed widgets on third-party pages, that is, the scope of widgets is not limited to a personalized Google page. Yandex and so far does not turn around.
    The conclusion is simple: while Google provides more opportunities for widget writers, but, it seems to me, the audience for widgets on Yandex (Russian-speaking) is more extensive. And the prospects will depend on how they evaluate this direction in Google and Yandex, respectively, because finishing and combing is still required here decently.
    That's actually all that I wanted to tell about widgets. I hope this information will be useful to someone. Success in promoting your projects with widgets.
    PS. I have not yet evaluated traffic from widgets.

    Also popular now: