[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：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"]]
