{"id":25145,"date":"2020-07-22T00:00:00","date_gmt":"2020-07-22T00:00:00","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/prepare-for-mobile-first-indexing-with-a-little-extra-time\/"},"modified":"2020-07-22T00:00:00","modified_gmt":"2020-07-22T00:00:00","slug":"prepare-for-mobile-first-indexing-with-a-little-extra-time","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/prepare-for-mobile-first-indexing-with-a-little-extra-time\/","title":{"rendered":"Prepare for mobile-first indexing (with a little extra time)"},"content":{"rendered":"<p class=\"gargardate\">Wednesday, July 22, 2020<\/p>\n<aside class=\"key-point\"><b>Newer content available<\/b>: This post is outdated. 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    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/mobile-first-indexing-2\/\">Mobile-first indexing<\/a> has been an<br \/>\n    ongoing effort of Google for several years. We&#8217;ve enabled mobile-first indexing for most<br \/>\n    currently crawled sites, and<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/mobile-first-indexing-by-default-for-new-domains\/\">enabled it by default for<br \/>\n    all the new sites<\/a>. Our initial plan was to<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/announcing-mobile-first-indexing-for-the-whole-web\/\">enable mobile-first indexing for all sites in Search<\/a><br \/>\n    in September 2020. We realize that in these uncertain times, it&#8217;s not always easy to focus on<br \/>\n    work as otherwise, so we&#8217;ve decided to extend the timeframe to the end of March 2021. At that<br \/>\n    time, we&#8217;re planning on switching our indexing over to mobile-first indexing.\n  <\/p>\n<p>\n    For the sites that are not yet ready for mobile-first indexing, we&#8217;ve already mentioned some<br \/>\n    issues blocking your sites in<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/mobile-first-indexing-structured-data-images-and-your-site\/\">previous blog posts<\/a>.<br \/>\n    Now that we&#8217;ve done more testing and evaluation, we have seen a few more issues that are worth<br \/>\n    mentioning to <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/mobile-site-and-mobile-first-indexing-best-practices\/\">better prepare your sites<\/a>.\n  <\/p>\n<h2 id=\"make-sure-googlebot-can-see-your-content\" tabindex=\"-1\">\n   Make sure Googlebot can see your content<br \/>\n  <\/h2>\n<p>\n    In mobile-first indexing, we will only get the information of your site from the mobile version,<br \/>\n    so make sure Googlebot can see the full content and all resources there. Here are some things to<br \/>\n    pay attention to:\n  <\/p>\n<h3 id=\"robots-meta-tags-on-mobile-version\" tabindex=\"-1\">\n    Robots <code>meta<\/code> tags on mobile version<br \/>\n  <\/h3>\n<p>\n    You should use the same <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/robots-meta-tag\/\"><span>robots<\/span> <code>meta<\/code> tags<\/a> on the<br \/>\n    mobile version as those on the desktop version. If you use a different one on the mobile version<br \/>\n    (such as <code>noindex<\/code> \u0438\u043b\u0438 <code>nofollow<\/code>), Google<br \/>\n    may fail to index or follow links on your page when your site is enabled for mobile-first<br \/>\n    indexing.\n  <\/p>\n<h3 id=\"lazy-loading-on-mobile-version\" tabindex=\"-1\">\n   Lazy-loading on mobile version<br \/>\n  <\/h3>\n<p>\n    Lazy-loading is more common on mobile than on desktop, especially for loading images and videos.<br \/>\n    We recommend following <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/fix-lazy-loaded-content\/\">lazy-loading best practices<\/a>.<br \/>\n    In particular, avoid lazy-loading your primary content based on user interactions (like swiping,<br \/>\n    clicking, or typing), because Googlebot won&#8217;t trigger these user interactions.\n  <\/p>\n<p>\n    For example, if your page has 10 primary images on the desktop version, and the mobile version<br \/>\n    only has 2 of them, with the other 8 images loaded from the server only when the user clicks the<br \/>\n    <code>+<\/code> button:\n  <\/p>\n<p>\n    <img decoding=\"async\" src=\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-a813865b16b2.png\" loading=\"lazy\"\n         alt=\"desktop version with 10 thumbnails \/ mobile version with 2 thumbnails\"\/>\n  <\/p>\n<p>\n    In this case, Googlebot won&#8217;t click the button to load the 8 images, so Google won&#8217;t see those<br \/>\n    images. The result is that they won&#8217;t be indexed or shown in Google Images. Follow<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/fix-lazy-loaded-content\/\">Google&#8217;s lazy-loading best practices<\/a>, and lazy<br \/>\n    load content automatically based on its visibility in the viewport.\n  <\/p>\n<h3 id=\"be-aware-of-what-you-block\" tabindex=\"-1\">\n    Be aware of what you block<br \/>\n  <\/h3>\n<p>\n    Some resources have different URLs on the mobile version from those on the desktop version,<br \/>\n    sometimes they are served on different hosts. If you want Google to crawl your URLs, make sure<br \/>\n    you&#8217;re not disallowing crawling of them with your<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/robots-txt-intro\/\">robots.txt file<\/a>.\n  <\/p>\n<p>\n    For example, blocking the URLs of <code>.css<\/code> files will prevent Googlebot<br \/>\n    from rendering your pages correctly, which can harm the ranking of your pages in Search.<br \/>\n    Similarly, blocking the URLs of images will make these images disappear from Google Images.\n  <\/p>\n<h2 id=\"make-sure-primary-content-is-the-same-on-desktop-and-mobile\" tabindex=\"-1\">\n    Make sure primary content is the same on desktop and mobile<br \/>\n  <\/h2>\n<p>\n    If your mobile version has less content than your desktop version, you should consider updating<br \/>\n    your mobile version so that its primary content (the content you want to rank with, or the<br \/>\n    reason for users to come to your site) is equivalent. Only the content shown on the mobile<br \/>\n    version will be used for indexing and ranking in Search. If it&#8217;s your intention that the mobile<br \/>\n    version has less content than the desktop version, your site may lose some traffic when Google<br \/>\n    enables mobile-first indexing for your site, since Google won&#8217;t be able to get the full<br \/>\n    information anymore.\n  <\/p>\n<p>\n    Use the same clear and meaningful headings on your mobile version as on the desktop version.<br \/>\n    Missing meaningful headings may negatively affect your page&#8217;s visibility in Search, because we<br \/>\n    might not be able to fully understand the page.\n  <\/p>\n<p>\n    For example, if your desktop version has the following tag for the heading of the page:\n  <\/p>\n<div><\/div>\n<p>\n    Your mobile version should also use the same heading tag with the same words for it, rather than<br \/>\n    using headings like:\n  <\/p>\n<div><\/div>\n<p>(not clear and meaningful)<\/p>\n<div><\/div>\n<p>(not using a heading tag)<\/p>\n<h2 id=\"check-your-images-and-videos\" tabindex=\"-1\">\n    Check your images and videos<br \/>\n  <\/h2>\n<p>\n    Make sure the images and videos on your mobile version follow<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/images-best-practices\/\">image best practices<\/a> and<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/video-search\/\">video best practices<\/a>. In<br \/>\n    particular, we recommend that you perform the following checks:\n  <\/p>\n<h3 id=\"image-quality\" tabindex=\"-1\">\n   Image quality<br \/>\n  <\/h3>\n<p>\n    Don&#8217;t use images that are too small or have a low resolution on the mobile version. Small or<br \/>\n    low-quality images might not be selected for inclusion in Google Images, or shown as favorably<br \/>\n    when indexed.\n  <\/p>\n<p>\n    For example, if your page has 10 primary images on the desktop version, and they are normal,<br \/>\n    good quality images. On the mobile version, a bad practice is to use very small thumbnails for<br \/>\n    these images to make them all fit in the smaller screen:\n  <\/p>\n<p>\n   <img decoding=\"async\" alt=\"desktop version with normal thumbnails \/ mobile version tiny thumbnails\" src=\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-bd56de1b6c81.png\" loading=\"lazy\">\n  <\/p>\n<p>\n    In this case, these thumbnails may be considered &#8220;low quality&#8221; by Google because they are too<br \/>\n    small and in a low resolution.\n  <\/p>\n<h3 id=\"alt-attributes-for-images\" tabindex=\"-1\">\n    Alt attributes for images<br \/>\n  <\/h3>\n<p>\n    As <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/mobile-first-indexing-structured-data-images-and-your-site\/\">previously mentioned<\/a>,<br \/>\n    remember that using less-meaningful alt attributes might negatively affect how your images are<br \/>\n    shown in Google Images.\n  <\/p>\n<p>\n    For example, a good practice is like the following (meaningful alt text):\n  <\/p>\n<div><\/div>\n<p>While bad practices are like the following (empty alt text):<\/p>\n<div><\/div>\n<p>Here&#8217;s an example where the alt text isn&#8217;t meaningful:<\/p>\n<div><\/div>\n<h3 id=\"different-image-urls-between-desktop-and-mobile-version\" tabindex=\"-1\">\n    Different image URLs between desktop and mobile version<br \/>\n  <\/h3>\n<p>\n    If your site uses different image URLs for the desktop and mobile version, you may see a<br \/>\n    temporary traffic loss from Google Images while your site transitions to mobile-first indexing.<br \/>\n    This is because the image URLs on the mobile version are new to the Google indexing system, and<br \/>\n    it takes some time for the new image URLs to be understood appropriately. To minimize a<br \/>\n    temporary traffic loss from search, review whether you can retain the image URLs used by desktop.\n  <\/p>\n<h3 id=\"video-markup\" tabindex=\"-1\">\n    Video markup<br \/>\n  <\/h3>\n<p>\n    If your desktop version uses schema.org&#8217;s<br \/>\n    <code><a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/video-videoobject-clip-broadcastevent-structured-data\/#video-object\">VideoObject structured data<\/a><\/code><br \/>\n    to describe videos, make sure the mobile version also includes the<br \/>\n    <code>VideoObject<\/code>, with equivalent information provided. Otherwise our<br \/>\n    video indexing systems may have trouble getting enough information about your videos, resulting<br \/>\n    in them not being shown as visibly in Search.<\/p>\n<h3 id=\"video-and-image-placement\" tabindex=\"-1\">\n    Video and image placement<br \/>\n  <\/h3>\n<p>\n    Make sure to position videos and images in an easy to find location on the mobile version of<br \/>\n    your pages. Videos or images not placed well could affect user experience on mobile devices,<br \/>\n    making it possible that Google would not show these as visibly in search.\n  <\/p>\n<p>\n    For example, assume you have a video embedded in your content in an easy to find location on desktop:\n  <\/p>\n<p>\n   <img decoding=\"async\" alt=\"easy to find video on desktop\" src=\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-ce332a99171e.png\" loading=\"lazy\">\n  <\/p>\n<p>\n    On mobile, you place an ad near the top of the page which takes up a large part of the page.<br \/>\n    This can result your video being moved off the page, requiring users to scroll down a lot to<br \/>\n    find the video:\n  <\/p>\n<p>\n   <img decoding=\"async\" src=\"https:\/\/developers.google.com\/static\/search\/blog\/images\/import\/248fd61c343805b8035d72303552ea9b.png\"\n        alt=\"video on mobile is much less visible to users\" \/>\n  <\/p>\n<p>\n    In this case, the page might not be deemed a useful video landing page by our algorithms,<br \/>\n    resulting in the video not being shown in Search.\n  <\/p>\n<p>\n    You can find more information and more best practices in our<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/mobile-site-and-mobile-first-indexing-best-practices\/\">developer guide for mobile-first indexing<\/a>.\n  <\/p>\n<p>\n    Mobile-first indexing has come a long way. It&#8217;s great to see how the web has evolved from<br \/>\n    desktop to mobile, and how webmasters have helped to allow crawling and indexing to match how<br \/>\n    users interact with the web! We appreciate all your work over the years, which has helped to<br \/>\n    make this transition fairly smooth. We&#8217;ll continue to monitor and evaluate these changes<br \/>\n    carefully. If you have any questions, please drop by our<br \/>\n    <a href=\"https:\/\/support.google.com\/webmasters\/go\/community\" class=\"external-link\">forums<\/a> or our<br \/>\n    <a href=\"https:\/\/developers.google.com\/search\/events\">public events<\/a>.\n  <\/p>\n<p class=\"byline-author\">\n    Posted by<br \/>\n    <a href=\"https:\/\/www.linkedin.com\/in\/yingxiwu\" class=\"external-link\">Yingxi Wu (\u5434\u8424\u897f)<\/a>,<br \/>\n    Google Mobile-First Indexing team\n  <\/p>\n","protected":false},"excerpt":{"rendered":"<p>Wednesday, July 22, 2020 Newer content available: This post is outdated. Check out our newer Mobile-first indexing best practices. Mobile-first indexing has been an ongoing effort of Google for several years. We&#8217;ve enabled mobile-first indexing for most currently crawled sites, and enabled it by default for all the new sites. Our initial plan was to [&hellip;]<\/p>\n","protected":false},"menu_order":81535,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[665],"ar_kb_etiket":[],"class_list":["post-25145","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\/25145","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\/25145\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/27268"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=25145"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=25145"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=25145"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}