[[["わかりやすい","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"]],[],[[["\u003cp\u003eGoogle is migrating sites to mobile-first indexing, meaning Googlebot will now primarily use the mobile version of your website for indexing and ranking.\u003c/p\u003e\n"],["\u003cp\u003eMobile-first indexing does not provide a ranking advantage; it focuses on how Google gathers content, while ranking is determined by numerous factors including mobile-friendliness and page speed.\u003c/p\u003e\n"],["\u003cp\u003eWebsite owners will be notified via Search Console if their site is being migrated to mobile-first indexing and may observe increased crawl rate from the Smartphone Googlebot.\u003c/p\u003e\n"],["\u003cp\u003eGoogle encourages webmasters to prioritize mobile-friendly content and fast loading speeds for improved user experience and better performance in search results.\u003c/p\u003e\n"],["\u003cp\u003eSites not yet migrated should not worry; desktop content will still be indexed, but Google recommends adapting to mobile-friendliness as a best practice.\u003c/p\u003e\n"]]],["Google is migrating sites to mobile-first indexing, using the mobile version of pages for indexing and ranking. This does not create a separate index, and being indexed this way has no ranking advantage. Sites migrating will receive notifications and experience increased crawl rates from Smartphone Googlebot. Mobile-friendly and fast-loading content remains beneficial for mobile and desktop performance. Google evaluates all content for mobile-friendliness, and slow-loading content may perform worse in searches.\n"],null,["# Rolling out mobile-first indexing\n\nMonday, March 26, 2018\n| It's been a while since we published this blog post. Some of the information may be outdated (for example, some images may be missing, and some links may not work anymore). Check out our newer [Mobile-first indexing best practices](/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing).\n\n\nToday we're announcing that [after a year and\na half](/search/blog/2016/11/mobile-first-indexing) of careful experimentation and testing, we've started migrating sites that follow the\n[best practices](/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing) for mobile-first indexing.\n\n\nTo recap, our crawling, indexing, and ranking systems have typically used the desktop version of\na page's content, which may cause issues for mobile searchers when that version is vastly\ndifferent from the mobile version. Mobile-first indexing means that we'll use the mobile version\nof the page for indexing and ranking, to better help our -- primarily mobile -- users find what\nthey're looking for.\n\n\nWe continue to have one single index that we use for serving search results. We do not have a\n\"mobile-first index\" that's separate from our main index. Historically, the desktop version was\nindexed, but increasingly, we will be using the mobile versions of content.\n\n\nWe are notifying sites that are\n[migrating to mobile-first indexing](/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing) via\n[Search Console](https://search.google.com/search-console). Site owners will see\nsignificantly increased crawl rate from the\n[Smartphone Googlebot](/search/docs/crawling-indexing/overview-google-crawlers).\nAdditionally, Google will show the mobile version of pages in Search results and\n[Google cached pages](https://support.google.com/websearch/answer/1687222).\n\n\nTo understand more about how we determine the mobile content from a site, see\n[our documentation](/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing). It covers how sites\nusing responsive web design or dynamic serving are generally set for mobile-first indexing. For\nsites that have AMP and non-AMP pages, Google will prefer to index the mobile version of the\nnon-AMP page.\n\n\nSites that are not in this initial wave don't need to panic. Mobile-first indexing is about how\nwe gather content, not about how content is ranked. Content gathered by mobile-first indexing has\nno ranking advantage over mobile content that's not yet gathered this way or desktop content.\nMoreover, if you only have desktop content, you will continue to be represented in our index.\n\n\nHaving said that, we continue to encourage webmasters to make their content mobile-friendly. We\ndo evaluate all content in our index---whether it is desktop or mobile---to determine how\nmobile-friendly it is. [Since 2015](/search/blog/2015/04/rolling-out-mobile-friendly-update),\nthis measure can help mobile-friendly content perform better for those who are searching on mobile.\nRelated, we [recently announced](/search/blog/2018/01/using-page-speed-in-mobile-search)\nthat beginning in July 2018, content that is slow-loading may perform less well for both desktop\nand mobile searchers.\n\n\nTo recap:\n\n- Mobile-indexing is rolling out more broadly. Being indexed this way has no ranking advantage and operates independently from our mobile-friendly assessment.\n- Having mobile-friendly content is still helpful for those looking at ways to perform better in mobile search results.\n- Having fast-loading content is still helpful for those looking at ways to perform better for mobile and desktop users.\n- As always, ranking uses many factors. We may show content to users that's not mobile-friendly or that is slow loading if our many other signals determine it is the most relevant content to show.\n\n\nWe'll continue to monitor and evaluate this change carefully. If you have any questions, please drop by our\n[Webmaster forums](https://support.google.com/webmasters/go/community) or our\n[public events](/search/events).\n\nPosted by [Fan Zhang](/search/blog/authors/fan-zhang), Software Engineer"]]