Sounds great right? There is only one small problem: caching doesn’t work properly since Server Push is not aware of previous visits and will not check cached resources. Server Push always tells the browser that it is should receive the files from the server, whatever happened before.
During the past few months Baidu has been busy with copying Google’s AMP (Accelerated Mobile Pages Project) and late August they launched MIP, also known as Mobile Instant Pages.
The concept of MIP is basically the same as Google AMP: create an additional page while using only specific HTML markup, hosted JS libraries and a just a predefined set of elements are allowed in combination with local caching. This creates a better user experience due to faster loading content. It is not known yet when Baidu is going to put MIP results into all their search engine result pages: this will probably take another few weeks since they just launched and almost no websites have created MIP pages yet. For some queries, like Olympic Games related keywords, MIP results do show up (link) Another item on the massive to do list next to building AMP pages for many content driven organisations. Example via Dragonmetrics blog:
Why MIP next to AMP?
Censorship: it is likely most users can’t access Google’s servers that host AMP versions.
The biggest change to the Hypertext Transfer Protocol in years (since 1999) has been accepted and finalized earlier this year. Currently is it being implemented by many servers and hosting companies because it can truly save a lot of loading time for the average website. With HTTP/2 a multiplexing feature allows it to make lots of request at the same time so page load will not be blocked by CSS or JS files based on a maximum number of connections a browser can make. If you want to know what changed in comparison to the old HTTP protocol, have a look at the following slidedeck by Daniel Stenberg, network hacker at Mozilla:
Since April this year, Google now shows app install buttons and app deeplinks in the search engine result pages for Android users. They already showed it to users of specific apps but will now add apps if users haven’t installed it yet or are not logged in. Google has already indexed over 30 billion links directly pointing to content within apps and now uses App Indexing as a ranking signal for all Android users. A very logical step, since Google is now officially getting more searches from mobile compared to desktop users (source). Adding direct links to apps will contribute to a more positive user experience for their users.
Today Yandex’s head of search, Alexander Sadovsky, announced they will start using paid links as a negative ranking signal. Official announcement: Новый этап в борьбе со ссылочным спамом from today. After discounting links in a few specific niches and areas around Moscow last year, they now decide to turn it around and use paid links as a negative signal.
Paid links are still massively used in the Russian search market, after removing links from their algorithm they expected SEO would start using different ways of getting links. Nothing changed at all. 70% of the links in popular, commercial interesting niches, are still consider Paid Links by Yandex. Yandex found the SEO market to be stubborn (what a surprise!), the number of paid links being used in those niches dropped just 16% last year. Links will be back in their main algorithm, but now can have a positive, neutral or negative effect on a website’s performance in the search engine result pages. Yandex is quite confident their machine learning algorithms are good enough to detect paid links at the moment.
The rollout of this updated algorithm will start in May. Personally I really like the research and efforts of the Yandex research department. Comparing to the other major search engines, they publicly try to battle the amount of crappy SEO spam, good job!