{"id":24997,"date":"2017-12-18T00:00:00","date_gmt":"2017-12-18T00:00:00","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/getting-your-site-ready-for-mobile-first-indexing\/"},"modified":"2017-12-18T00:00:00","modified_gmt":"2017-12-18T00:00:00","slug":"getting-your-site-ready-for-mobile-first-indexing","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/getting-your-site-ready-for-mobile-first-indexing\/","title":{"rendered":"Getting your site ready for mobile-first indexing"},"content":{"rendered":"<p class=\"gargardate\">Monday, December 18, 2017<\/p>\n<aside class=\"key-point\">It&#8217;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<br \/>\n<a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/mobile-site-and-mobile-first-indexing-best-practices\/\">Mobile-first indexing best practices<\/a>.<\/aside>\n<p>\n  When we <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/mobile-first-indexing-2\/\">announced<\/a> almost a year ago that<br \/>\n  we&#8217;re experimenting with mobile-first indexing, we said we&#8217;d update publishers about our progress,<br \/>\n  something that we&#8217;ve done the past few months through public talks in<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/submit-a-question-idea-for-google-seo-office-hours\/\">office hours<\/a> and at conferences like<br \/>\n  <a href=\"https:\/\/www.google.com\/search?q=mobile+first+indexing+pubcon\" class=\"external-link\">Pubcon<\/a>.\n<\/p>\n<p>\n  To recap, currently our crawling, indexing, and ranking systems typically look at the desktop<br \/>\n  version of a page&#8217;s content, which may cause issues for mobile searchers when that version is<br \/>\n  vastly different from the mobile version. Mobile-first indexing means that we&#8217;ll use the mobile<br \/>\n  version of the content for indexing and ranking, to better help our&mdash;primarily mobile&mdash;users<br \/>\n  find what they&#8217;re looking for. Webmasters will see significantly increased crawling by<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/google-crawlers\/\">Smartphone Googlebot<\/a>, and<br \/>\n  the snippets in the results, as well as the content on the<br \/>\n  <a href=\"https:\/\/support.google.com\/websearch\/answer\/1687222\" class=\"external-link\">Google cache pages<\/a>,<br \/>\n  will be from the mobile version of the pages.\n<\/p>\n<p>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/mobile-first-indexing-2\/\">As we said<\/a>, sites that make use of<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/mobile-site-and-mobile-first-indexing-best-practices\/#responsive-design\">responsive web design<\/a><br \/>\n  and correctly implement<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/mobile-site-and-mobile-first-indexing-best-practices\/\">dynamic serving<\/a><br \/>\n  (that include all of the desktop content and markup) generally don&#8217;t have to do anything. Here are<br \/>\n  some extra tips that help ensure a site is ready for mobile-first indexing:\n<\/p>\n<ul>\n<li>\n    Make sure the mobile version of the site also has the important, high-quality content. This<br \/>\n    includes text, images (with <code>alt<\/code> attributes), and videos &#8211; in the usual crawlable<br \/>\n    and indexable formats.\n  <\/li>\n<li>\n    Structured data is important for indexing and search features that users love: it should be<br \/>\n    both on the mobile and desktop version of the site. Ensure URLs within the structured data are<br \/>\n    updated to the mobile version on the mobile pages.\n  <\/li>\n<li>\n    Metadata should be present on both versions of the site. It provides hints about the content on<br \/>\n    a page for indexing and serving. For example, make sure that titles and meta descriptions are<br \/>\n    equivalent across both versions of all pages on the site.\n  <\/li>\n<li>\n    No changes are necessary for interlinking with separate mobile URLs (m.-dot sites). For<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/mobile-site-and-mobile-first-indexing-best-practices\/#separate-urls\">sites using separate mobile URLs<\/a>,<br \/>\n    keep the existing <code>link<\/code> <code>rel=canonical<\/code> and <code>link<\/code><br \/>\n    <code>rel=alternate<\/code> elements between these versions.\n  <\/li>\n<li>\n    Check hreflang links on separate mobile URLs. When using<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/localized-versions\/\"><code>link<\/code> <code>rel=hreflang<\/code><\/a><br \/>\n    tags for<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/managing-multi-regional-and-multilingual-sites\/\">internationalization<\/a>,<br \/>\n    link between mobile and desktop URLs separately. Your mobile URLs&#8217; hreflang should point to the<br \/>\n    other language\/region versions on other mobile URLs, and similarly link desktop with other<br \/>\n    desktop URLs using <code>hreflang<\/code> <code>link<\/code> elements there.\n  <\/li>\n<li>\n    Ensure the servers hosting the site have enough capacity to handle potentially increased<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/what-crawl-budget-means-for-googlebot\/\">crawl rate<\/a>. This<br \/>\n    doesn&#8217;t affect sites that use responsive web design and dynamic serving, only sites where the<br \/>\n    mobile version is on a separate host, such as m.example.com.\n  <\/li>\n<\/ul>\n<p>\n  We will be evaluating sites independently on their readiness for mobile-first indexing based on<br \/>\n  the above criteria and transitioning them when ready. This process has already started for a<br \/>\n  handful of sites and is closely being monitored by the search team.\n<\/p>\n<p>\n  We continue to be cautious with rolling out mobile-first indexing. We believe taking this slowly<br \/>\n  will help site owners get their sites ready for mobile users, and because of that, we currently<br \/>\n  don&#8217;t have a timeline for when it&#8217;s going to be completed. If you have any questions, drop by our<br \/>\n  <a href=\"https:\/\/support.google.com\/webmasters\/go\/community\" class=\"external-link\">Webmaster forums<\/a><br \/>\n  or our <a href=\"https:\/\/developers.google.com\/search\/events\">public events<\/a>.\n<\/p>\n<p class=\"byline-author\">\n  Posted by <a href=\"https:\/\/garyillyes.com\/+\" class=\"external-link\">Gary Illyes<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Monday, December 18, 2017 It&#8217;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. When we announced almost a year ago that we&#8217;re experimenting with mobile-first [&hellip;]<\/p>\n","protected":false},"menu_order":82482,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[665],"ar_kb_etiket":[],"class_list":["post-24997","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-blog"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24997","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":0,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24997\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/27150"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=24997"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=24997"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=24997"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}