{"id":24878,"date":"2015-04-21T00:00:00","date_gmt":"2015-04-21T00:00:00","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/faqs-about-the-april-21st-mobile-friendly-update\/"},"modified":"2015-04-21T00:00:00","modified_gmt":"2015-04-21T00:00:00","slug":"faqs-about-the-april-21st-mobile-friendly-update","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/faqs-about-the-april-21st-mobile-friendly-update\/","title":{"rendered":"FAQs about the April 21st mobile-friendly update"},"content":{"rendered":"

Tuesday, April 21, 2015<\/p>\n

\n We’d like to share answers to your frequently asked questions. For background, in February,
\n we announced that the mobile-friendly update<\/a>
\n will boost the rankings of mobile-friendly pages—pages that are legible and usable on mobile
\n devices—in mobile search results worldwide. (Conversely, pages designed for only large
\n screens may see a significant decrease in rankings in mobile search results.) To get us all on the
\n same page, here are the most frequently asked questions:\n<\/p>\n

General FAQs<\/h2>\n

\n 1. Will desktop and\/or tablet ranking also be affected by this change?<\/b>
\n No, this update has no effect on searches from tablets or desktops. It affects searches from
\n mobile devices across all languages and locations.\n<\/p>\n

\n 2. Is it a page-level or site-level mobile ranking boost?<\/b>
\n It’s a page-level change. For instance, if ten of your site’s pages are mobile-friendly, but the
\n rest of your pages aren’t, only the ten mobile-friendly pages can be positively impacted.\n<\/p>\n

\n 3. How do I know if Google thinks a page on my site is mobile-friendly?<\/b>
\n Individual pages can be tested for “mobile-friendliness” using the
\n Mobile-Friendly Test<\/a>.\n<\/p>\n

\"Test<\/p>\n

\n To review site-level information on mobile-friendliness, check out the
\n Mobile Usability report in Webmaster Tools<\/a>.
\n This feature’s data is based on the last time we crawled and indexed your site’s pages.\n<\/p>\n

\"Mobile<\/p>\n

\n 4. Unfortunately, my mobile-friendly pages won’t be ready until after April 21st. How long
\n before they can be considered mobile-friendly in ranking?<\/b>
\n We determine whether a page is mobile-friendly every time it’s crawled and indexed—you don’t
\n have to wait for another update. Once a page is mobile-friendly, you can wait for
\n Googlebot for smartphones<\/a>
\n to naturally (re-)crawl and index the page or you can expedite processing by using
\n Fetch as Google with Submit to Index<\/a>
\n in
\n Webmaster Tools<\/a>. For a large volume of
\n URLs, consider submitting a
\n sitemap<\/a>. In the sitemap, if your mobile
\n content uses pre-existing URLs (such as with
\n Responsive Web Design<\/a>
\n \u0438\u043b\u0438
\n dynamic serving<\/a>),
\n also include the
\n lastmod<\/code> tag<\/a>.\n<\/p>\n

\n 5. Since the mobile ranking change rolls out on April 21st, if I see no drop in traffic on
\n April 22nd, does that mean that my site’s rankings aren’t impacted?<\/b>
\n You won’t be able to definitively determine whether your site’s rankings are impacted by the
\n mobile-friendly update by April 22nd. While we begin rolling out the mobile-friendly update on
\n April 21st, it’ll be a week or so before it makes its way to all pages in the index.\n<\/p>\n

\n 6. I have a great mobile site, but the Mobile-Friendly Test tells me that my pages aren’t
\n mobile-friendly. Why?<\/b>
\n If a page is designed to work well on mobile devices, but it’s not passing the Mobile-Friendly
\n Test, the most common reason is that Googlebot for smartphones is blocked from crawling resources,
\n like CSS and JavaScript, that are critical for determining whether the page is legible and usable
\n on a mobile device (that is, whether it’s mobile-friendly). To remedy:\n<\/p>\n

    \n
  1. \n Check if the
    \n     Mobile-Friendly Test<\/a>
    \n shows blocked resources (often accompanied with a partially rendered image).\n <\/li>\n
  2. \n Allow Googlebot<\/a> to crawl
    \n the necessary files.\n <\/li>\n
  3. Double-check that your page passes the Mobile-Friendly Test.<\/li>\n
  4. \n Use
    \n     Fetch as Google with Submit to Index<\/a>
    \n and
    \n     submit your updated robots.txt to Google<\/a>
    \n to expedite the re-processing of the updated page (or just wait for Google to naturally re-crawl
    \n and index).\n <\/li>\n<\/ol>\n

    <\/p>\n

    \n The most common reason why a mobile page fails the Mobile-Friendly Test is that Googlebot for
    \n smartphones is blocked from crawling resources, like CSS and JavaScript, that are crucial for
    \n understanding the page’s mobile-friendliness.\n<\/p>\n

    \n To reiterate, we recommend that site owners allow Googlebot to crawl all resources for a page
    \n (including CSS, JavaScript, and images), so that we can properly render, index, and in this case,
    \n assess whether the page is mobile-friendly.\n<\/p>\n

    \n 7. What if I link to a site that’s not mobile-friendly?<\/b>
    \n Your page can still be “mobile-friendly” even if it links to a page that’s not mobile-friendly,
    \n such as a page designed for larger screens, like desktops. It’s not the best experience for mobile
    \n visitors to go from a mobile-friendly page to a desktop-only page, but hopefully as more sites
    \n become mobile-friendly, this will become less of a problem.\n<\/p>\n

    \n 8. Does Google give a stronger mobile-friendly ranking to pages using Responsive Web Design
    \n (which uses the same URL and the same HTML for the desktop and mobile versions) vs. hosting a
    \n separate mobile site (like www for desktop and m.example.com for mobile)?<\/b>
    \n No, mobile-friendliness is assessed the same, whether you use
    \n     responsive web design<\/a>
    \n (RWD),
    \n     separate mobile URLs<\/a>,
    \n \u0438\u043b\u0438     dynamic serving<\/a>
    \n for your
    \n     configuration<\/a>. If your site
    \n uses separate mobile URLs or dynamic serving, we recommend reviewing the Mobile SEO guide to make
    \n sure Google is properly crawling and indexing your mobile pages.\n<\/p>\n

    \n 9. Will my site \/ page disappear on mobile search results if it’s not mobile-friendly?<\/b>
    \n While the mobile-friendly change is important, we still use a variety of signals to rank search
    \n results. The intent of the search query is still a very strong signal—so even if a page with
    \n high quality content is not mobile-friendly, it could still rank high if it has great content for
    \n the query.\n<\/p>\n

    Specialized FAQs<\/h2>\n

    \n 10. What if my audience is desktop only? Then there’s no reason to have a mobile site,
    \n right?<\/b>
    \n Not exactly. Statistics show that more people are going “mobile only”—either because they
    \n never had a desktop or because they won’t replace their existing desktop. Additionally, a
    \n non-mobile-friendly site may not see many mobile visitors precisely for that reason.\n<\/p>\n

    \n The mobile-friendly update will apply to mobile searches conducted across all sites, regardless of
    \n the site’s target audiences’ language, region, or proportion of mobile to desktop traffic.\n<\/p>\n

    \n 11. I have pages showing mobile usability errors because they embed a YouTube video. What can I
    \n do?<\/b>
    \n We suggest paying close attention to how the YouTube video is embedded. If you are using the
    \n “old-style” <object><\/code> embeds in the mobile page, convert to
    \n <iframe><\/code> embeds for broader compatibility. YouTube now uses the
    \n     HTML5 player on the web by default<\/a>,
    \n so it’s mobile-friendly to embed videos using the <iframe><\/code> tags from the
    \n “share” feature on the watch page or from the
    \n     YouTube iFrame API<\/a>.
    \n If you have a more complex integration, that should also be mobile-friendly, since it’ll instruct
    \n the device to use the device’s native support.\n<\/p>\n

    \n For Flash content from sites other than YouTube, check if there is an equivalent HTML5 embed tag
    \n or code snippet to avoid using proprietary plugins.\n<\/p>\n

    \n 12. Is there a clear standard for
    \n     sizing tap targets<\/a>?
    \n <\/b>
    \n Yes, we suggest a minimum of 7mm width\/height for primary tap targets and a minimum margin of 5mm
    \n between secondary tap targets. The average width of an adult’s finger pad is 10mm, and these
    \n dimensions can provide a usable interface while making good use of screen real estate.\n<\/p>\n

    \n 13. To become mobile-friendly quickly, we’re thinking of creating a very stripped down version
    \n of our site (separate mobile pages) until our new responsive site is complete. Do you foresee
    \n any problems with this?<\/b>
    \n First, keep in mind that we support
    \n     three mobile configurations<\/a>
    \n and that your website doesn’t have to be responsive to be mobile-friendly. In response to your
    \n question, please be cautious about creating a “stripped down” version of your site. While the page
    \n may be formatted for mobile, if it doesn’t allow your visitors to easily complete their common
    \n tasks or have an overall smooth workflow, it may become frustrating to your visitors and perhaps
    \n not worth the effort. Should a temporary mobile site be created, once the RWD is live, be sure to
    \n     move the site properly<\/a>.
    \n For example, update all links so they no longer reference the separate mobile URLs and
    \n 301<\/code> redirect mobile URLs to their corresponding RWD version.\n<\/p>\n

    Recommendations<\/h2>\n

    \n If you’re totally new to building a mobile-friendly site, it’s not too late! Check out our
    \n     Getting Started guide<\/a> in the
    \n     Mobile-Friendly Websites documentation<\/a>.\n<\/p>\n

    \"Screeshot<\/p>\n

    \n If you already have a mobile site, investigate the
    \n     Mobile Usability report in Webmaster Tools<\/a>
    \n to make sure that Google detects your site’s pages as mobile-friendly.\n<\/p>\n

    \n Still more questions? Please ask below or check out the
    \n     Mobile Websites section of the Webmaster Forum<\/a>.\n<\/p>\n

    \n Written by
    \n     Maile Ohye<\/a>, Developer Programs Tech Lead.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Tuesday, April 21, 2015 We’d like to share answers to your frequently asked questions. For background, in February, we announced that the mobile-friendly update will boost the rankings of mobile-friendly pages—pages that are legible and usable on mobile devices—in mobile search results worldwide. (Conversely, pages designed for only large screens may see a significant decrease […]<\/p>\n","protected":false},"menu_order":83454,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[665],"ar_kb_etiket":[],"class_list":["post-24878","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\/24878","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\/24878\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/27062"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=24878"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=24878"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=24878"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}