智慧型手機搜尋結果中的排名變更
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
2014年2月24日星期一
原文:
Changes in rankings of smartphone search results
作者:Yoshikiyo Kato, Software Engineer;
Pierre Far
, Webmaster Trends Analyst
在網際網路使用者當中,智慧型手機使用者已然成為值得重視且蓬勃成長的族群。Google 希望所有智慧型手機使用者,都能夠充分體驗網路上的豐富內容。為了對改善行動網路盡一分力,我們提出了一些
建議事項
,並說明
最常見的設定錯誤
。
如果您能避免這些錯誤,那麼您的訪客便能充分體驗您的網站,也能讓使用者更快搜尋到所需資訊。為了提供智慧型手機使用者更好的搜尋環境,並解決最令他們困擾的一些問題,我們計劃在近期逐步變更幾項網站排名機制,以便因應某些網站並未正確設定智慧型手機瀏覽環境的情況。
以下將說明兩種最常見的錯誤及其修正方式。
重新導向錯誤
部分網站為電腦使用者和智慧型手機使用者提供不同的網址。這類網站有時會將使用智慧型手機瀏覽網頁的訪客,從電腦版網頁重新導向到專為智慧型手機最佳化的網站,但目標網頁卻與使用者的要求毫不相關,這種情況就屬於重新導向錯誤。常見的範例是,不論智慧型手機使用者瀏覽的是電腦版網站上的哪一個網頁,全部都會被重新導向到行動版網站的首頁。如下圖所示,紅色箭號即表示錯誤的重新導向方式:
這種重新導向方式會中斷使用者正常瀏覽網站的過程,並且可能會造成他們不再使用該網站,而選擇其他網站。即便使用者並未離開該網站,他們仍需費盡心思去處理不相關的重新導向;如果他們使用速度緩慢的行動網路,則更是徒增困擾。無論使用者要搜尋網頁、影片或其他內容,這些錯誤重新導向都會對使用者造成不便,而我們的排名變更將會影響許多種的搜尋類型。
要避免不相關的重新導向非常簡單:只需將智慧型手機使用者從電腦版網頁重新導向至內容相對應、且專為智慧型手機最佳化的網頁即可。如果網頁內容並沒有適用於智慧型手機的版本,顯示電腦版內容也比重新導向至不相關的網頁要來得更合適。
智慧型手機才會發生的錯誤
對於某些網站而言,當使用者存取某個網址時,可以在電腦上看到正確的網頁內容,但在智慧型手機上卻會看到錯誤的內容。有許多錯誤情形都只有智慧型手機才會發生,部分常見範例如下:
-
如果您偵測到使用者是在行動裝置上造訪電腦版網頁,而適用於智慧型手機的相對應網頁位於不同的網址,系統會將使用者重新導向至 404 網頁或
Soft 404 網頁
。
-
請確認適用於智慧型手機的網頁本身並非錯誤網頁。如果您的網頁內容並未提供適用於智慧型手機的版本,請改為提供電腦版網頁。顯示使用者所尋找的內容比顯示錯誤網頁要好得多了。
-
並未正確處理 Googlebot-Mobile。常見的錯誤是,網站將適用於智慧型手機的 Googlebot-Mobile 重新導向至
專為功能型手機最佳化的版本,
然後該網頁再將適用於智慧型手機的 Googlebot-Mobile 重新導向至電腦版網頁。這樣會導致無盡的重新導向迴圈,我們將這種情況認定為錯誤。
-
想要避免這種錯誤很簡單:
Googlebot-Mobile 使用者代理程式
會將自己標示為特定的行動裝置,這表示您應該以回應這類行動裝置的方式,來處理這些 Googlebot 使用者代理程式的要求。舉例來說,適用於智慧型手機的 Googlebot-Mobile 目前會將自己標示為 iPhone 手機,這表示您應該向該使用者代理程式提供與 iPhone 使用者相同的回應。
-
影片在智慧型手機上無法播放。許多網站所嵌入的影片可在電腦上正常觀看,卻無法在智慧型手機裝置上播放。舉例來說,如果內容需要安裝 Adobe Flash,就無法在 iPhone 或 Android 4.1 或更新版本上播放。
雖然我們僅在這裡提及了兩種錯誤,但網站管理員仍需審慎避免所有常見的智慧型手機網站
錯誤設定
。請盡可能在各種不同的裝置和作業系統 (或其模擬器) 上測試您的網站,包括測試網站上所提供的影片。這些測試將有助於改善行動網路環境、造福使用者,並讓搜尋者能夠充分體驗您的網站內容。
和往常一樣,如果您有任何問題,歡迎前往我們的
論壇
發問。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2014-02-01 (世界標準時間)。
[null,null,["上次更新時間:2014-02-01 (世界標準時間)。"],[[["\u003cp\u003eGoogle will implement ranking changes to improve mobile search and address issues with sites misconfigured for smartphone users.\u003c/p\u003e\n"],["\u003cp\u003eWebsites with separate URLs for desktop and mobile should ensure that redirects are to equivalent pages, not just the mobile homepage, to enhance user experience.\u003c/p\u003e\n"],["\u003cp\u003eSites should avoid smartphone-only errors like 404s, soft 404s, or unplayable content by ensuring mobile users can access content or are redirected appropriately.\u003c/p\u003e\n"],["\u003cp\u003eWebmasters should test their sites across different mobile devices and operating systems to ensure proper functionality and avoid common mobile misconfigurations.\u003c/p\u003e\n"],["\u003cp\u003eGoogle encourages webmasters to focus on providing a seamless mobile experience to enhance user satisfaction and search performance.\u003c/p\u003e\n"]]],["Google aims to improve the mobile web experience by addressing common smartphone site misconfigurations. Key actions include avoiding faulty redirects, where desktop pages redirect smartphone users to irrelevant mobile pages. Instead, redirect to equivalent mobile pages or show desktop content if no mobile version exists. Another issue is smartphone-only errors, such as serving error pages to mobile users instead of desktop content or redirecting Googlebot-Mobile incorrectly. Sites are advised to test on various mobile devices and operating systems.\n"],null,["# Changes in rankings of smartphone search results\n\nTuesday, June 11, 2013\n\n\nSmartphone users are a significant and fast growing segment of Internet users, and at Google we\nwant them to experience the full richness of the web. As part of our efforts to improve the mobile\nweb, we published our [recommendations](/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing) and the most\n[common configuration mistakes](/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing).\n\n\nAvoiding these mistakes helps your smartphone users engage with your site fully and helps\nsearchers find what they're looking for faster. To improve the search experience for smartphone\nusers and address their pain points, we plan to roll out several ranking changes in the near\nfuture that address sites that are misconfigured for smartphone users.\n\nLet's now look at two of the most common mistakes and how to fix them.\n\nFaulty redirects\n----------------\n\n\nSome websites use separate URLs to serve desktop and smartphone users. A faulty redirect is when a\ndesktop page redirects smartphone users to an irrelevant page on the smartphone-optimized website.\nA typical example is when all pages on the desktop site redirect smartphone users to the home page\nof the smartphone-optimized site. For example, in the figure below, the redirects shown as red\narrows are considered faulty:\n\n\nThis kind of redirect disrupts a user's workflow and may lead them to stop using the site and go\nelsewhere. Even if the user doesn't abandon the site, irrelevant redirects add more work for them\nto handle, which is particularly troublesome when they're on slow mobile networks. These faulty\nredirects frustrate users whether they're looking for a webpage, video, or something else, and our\nranking changes will affect many types of searches.\n\n\nAvoiding irrelevant redirects is very easy: Simply redirect smartphone users from a desktop page\nto its equivalent smartphone-optimized page. If the content doesn't exist in a smartphone-friendly\nformat, showing the desktop content is better than redirecting to an irrelevant page.\n\n\nWe have more\n[tips about redirects](/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing), and be sure to\nread our recommendations for having\n[separate URLs](/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing#separate-urls) for desktop and\nsmartphone users.\n\nSmartphone-only errors\n----------------------\n\n\nSome sites serve content to desktop users accessing a URL but show an error page to smartphone\nusers. There are many scenarios where smartphone-only errors are seen. Some common ones are:\n\n-\n If you recognize a user is visiting a desktop page from a mobile device and you have an\n equivalent smartphone-friendly page at a different URL, redirect them to that URL instead of\n serving a `404` or a\n [`soft 404` page](/search/docs/advanced/crawling/soft-404-errors).\n\n-\n Make sure that the smartphone-friendly page itself is not an error page. If your content is\n not available in a smartphone-friendly format, serve the desktop page instead. Showing the\n content the user was looking for is a much better experience than showing an error page.\n\n-\n Incorrectly handling Googlebot-Mobile. A typical mistake is when Googlebot-Mobile for\n smartphones is incorrectly redirected to the website\n [optimized for feature phones](/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing) which, in turn,\n redirects Googlebot-Mobile for smartphones back to desktop site. This results in infinite\n redirect loop, which we recognize as error.\n\n\n Avoiding this mistake is easy: All\n [Googlebot-Mobile user agents](/search/docs/crawling-indexing/googlebot) identify\n themselves as specific mobile devices, and you should treat these Googlebot user agents\n exactly like you would treat these devices. For example, Googlebot Mobile for smartphones\n currently identifies itself as an iPhone and you should serve it the same response an iPhone\n user would get.\n- Unplayable videos on smartphone devices. Many websites embed videos in a way that works well on desktops but is unplayable on smartphone devices. For example, if content requires Adobe Flash, it won't be playable on an iPhone or on Android versions 4.1 and higher.\n\n\nAlthough we covered only two types of mistakes here, it's important for webmasters to focus on\navoiding all of the common smartphone website\n[misconfigurations](/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing). Try to test your\nsite on as many different mobile devices and operating systems, or their emulators, as possible,\nincluding testing the videos included on your site. Doing so will improve the mobile web, make\nyour users happy, and allow searchers to experience your content fully.\n\n\nAs always, please ask in our\n[forums](https://support.google.com/webmasters/threads?hl=en&thread_filter=(category:crawling_indexing_ranking))\nif you have any questions.\n\n\nBy Yoshikiyo Kato, Software Engineer, on behalf of Mobile Search team, and\n[Pierre Far](/search/blog/authors/pierre-far),\nWebmaster Trends Analyst"]]