CINXE.COM

<!DOCTYPE html> <html class='v2 list-page' dir='ltr' itemscope='' itemtype='http://schema.org/Blog' lang='en-US' xmlns='http://www.w3.org/1999/xhtml' xmlns:b='http://www.google.com/2005/gml/b' xmlns:data='http://www.google.com/2005/gml/data' xmlns:expr='http://www.google.com/2005/gml/expr'> <head> <link href='https://www.blogger.com/static/v1/widgets/3566091532-css_bundle_v2.css' rel='stylesheet' type='text/css'/> <title> Official Google Webmaster Central Blog: mobile-friendly </title> <script type='text/javascript'> var newhost = 'https://developers.google.com'; var target_blog_path = '/search/blog' var target_search_path = '/s/results/search/blog/?q=' var pathname = window.location.pathname if (pathname.startsWith('/search/label/')) { pathname = target_search_path.concat(pathname.slice(14)); } else if (pathname.endsWith('.html')) { pathname = target_blog_path.concat(pathname.slice(0, -5)); } else { pathname = target_blog_path; } var redir_target = newhost.concat(pathname); window.location.href = redir_target; </script> <meta content='evCklrdiBeZ3REnk8pXEV6_6iEdNf1ZLgUpwH9XirGg' name='google-site-verification'/> <meta content='width=device-width, height=device-height, minimum-scale=1.0, initial-scale=1.0, user-scalable=0' name='viewport'/> <meta content='IE=Edge' http-equiv='X-UA-Compatible'/> <meta content='Official Google Webmaster Central Blog' property='og:title'/> <meta content='Official news on crawling and indexing sites for the Google index' property='og:description'/> <meta content='en_US' property='og:locale'/> <meta content='https://webmasters.googleblog.com/search/label/mobile-friendly' property='og:url'/> <meta content='Official Google Webmaster Central Blog' property='og:site_name'/>  <meta content='Official Google Webmaster Central Blog' property='og:title'/> <meta content='Official news on crawling and indexing sites for the Google index' property='twitter:description'/> <meta content='summary' name='twitter:card'/> <meta content='@googlewmc' name='twitter:creator'/> <link href='https://fonts.googleapis.com/css?family=Roboto:400italic,400,500,500italic,700,700italic' rel='stylesheet' type='text/css'/> <link href='https://fonts.googleapis.com/icon?family=Material+Icons' rel='stylesheet'/> <script src='https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js' type='text/javascript'></script>  <style id='page-skin-1' type='text/css'></style> <style id='template-skin-1' type='text/css'></style>  <meta content='text/html; charset=UTF-8' http-equiv='Content-Type'/> <meta content='blogger' name='generator'/> <link href='https://webmasters.googleblog.com/favicon.ico' rel='icon' type='image/x-icon'/> <link href='https://webmasters.googleblog.com/search/label/mobile-friendly' rel='canonical'/> <link rel="alternate" type="application/atom+xml" title="Official Google Webmaster Central Blog - Atom" href="https://webmasters.googleblog.com/feeds/posts/default" /> <link rel="alternate" type="application/rss+xml" title="Official Google Webmaster Central Blog - RSS" href="https://webmasters.googleblog.com/feeds/posts/default?alt=rss" /> <link rel="service.post" type="application/atom+xml" title="Official Google Webmaster Central Blog - Atom" href="https://www.blogger.com/feeds/32069983/posts/default" />  <meta content='Official news on crawling and indexing sites for the Google index' name='description'/> <meta content='https://webmasters.googleblog.com/search/label/mobile-friendly' property='og:url'/> <meta content='Official Google Webmaster Central Blog' property='og:title'/> <meta content='Official news on crawling and indexing sites for the Google index' property='og:description'/>  <base target='_self'/> <style> html { font-family: Roboto, sans-serif; -moz-osx-font-smoothing: grayscale; -webkit-font-smoothing: antialiased; } body { padding: 0; /* This ensures that the scroll bar is always present, which is needed */ /* because content render happens after page load; otherwise the header */ /* would "bounce" in-between states. */ min-height: 150%; } h2 { font-size: 16px; } h1, h2, h3, h4, h5 { line-height: 2em; } html, h4, h5, h6 { font-size: 14px; } a, a:visited { color: #4184F3; text-decoration: none; } a:focus, a:hover, a:active { text-decoration: none; } .Header { margin-top: 15px; } .Header h1 { font-size: 32px; font-weight: 300; line-height: 32px; height: 42px; } .header-inner .Header .titlewrapper { padding: 0; margin-top: 30px; } .header-inner .Header .descriptionwrapper { padding: 0; margin: 0; } .cols-wrapper { margin-top: 56px; } .header-outer, .cols-wrapper, .footer-outer, .google-footer-outer { padding: 0 60px; } .header-inner { height: 256px; position: relative; } html, .header-inner a { color: #212121; color: rgba(0,0,0,.87); } .header-inner .google-logo { display: inline-block; background-size: contain; z-index: 1; height: 46px; overflow: hidden; margin-top: 4px; margin-right: 8px; } .header-left { position: absolute; top: 50%; -webkit-transform: translateY(-50%); transform: translateY(-50%); margin-top: 12px; width: 100%; } .google-logo { margin-left: -4px; } #google-footer { position: relative; font-size: 13px; list-style: none; text-align: right; } #google-footer a { color: #444; } #google-footer ul { margin: 0; padding: 0; height: 144px; line-height: 144px; } #google-footer ul li { display: inline; } #google-footer ul li:before { color: #999; content: "\00b7"; font-weight: bold; margin: 5px; } #google-footer ul li:first-child:before { content: ''; } #google-footer .google-logo-dark { left: 0; margin-top: -16px; position: absolute; top: 50%; } /** Sitemap links. **/ .footer-inner-2 { font-size: 14px; padding-top: 42px; padding-bottom: 74px; } .footer-inner-2 .HTML h2 { color: #212121; color: rgba(0,0,0,.87); font-size: 14px; font-weight: 500; padding-left: 0; margin: 10px 0; } .footer-inner-2 .HTML ul { font-weight: normal; list-style: none; padding-left: 0; } .footer-inner-2 .HTML li { line-height: 24px; padding: 0; } .footer-inner-2 li a { color: rgba(65,132,243,.87); } /** Archive widget. **/ .BlogArchive { font-size: 13px; font-weight: normal; } .BlogArchive .widget-content { display: none; } .BlogArchive h2, .Label h2 { color: #4184F3; text-decoration: none; } .BlogArchive .hierarchy li { display: inline-block; } /* Specificity needed here to override widget CSS defaults. */ .BlogArchive #ArchiveList ul li, .BlogArchive #ArchiveList ul ul li { margin: 0; padding-left: 0; text-indent: 0; } .BlogArchive .intervalToggle { cursor: pointer; } .BlogArchive .expanded .intervalToggle .new-toggle { -ms-transform: rotate(180deg); transform: rotate(180deg); } .BlogArchive .new-toggle { float: right; padding-top: 3px; opacity: 0.87; } #ArchiveList { text-transform: uppercase; } #ArchiveList .expanded > ul:last-child { margin-bottom: 16px; } #ArchiveList .archivedate { width: 100%; } /* Months */ .BlogArchive .items { max-width: 150px; margin-left: -4px; } .BlogArchive .expanded .items { margin-bottom: 10px; overflow: hidden; } .BlogArchive .items > ul { float: left; height: 32px; } .BlogArchive .items a { padding: 0 4px; } .Label { font-size: 13px; font-weight: normal; } .sidebar-icon { display: inline-block; width: 24px; height: 24px; vertical-align: middle; margin-right: 12px; margin-top: -1px } .Label a { margin-right: 4px; } .Label .widget-content { display: none; } .FollowByEmail { font-size: 13px; font-weight: normal; } .FollowByEmail h2 { background: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABEAAAALCAYAAACZIGYHAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAUBJREFUeNrMkSGLAlEUhb+ZB4JFi8mx2cz+ApvhRUGTcUCrNqNJDYIi+DO0GUwmQXDK2DSIoGgZcSaIjDrzwrK4ssvChj1w0733O+fdp+m6PozH4yQSCfb7Pa7r8pOi0SjJZBLP8zgej4gAIMvlMuPxmADIYrHger1+C6lUKmo+NJ/NZojb7SZDWiwWo1qtks1msW2bw+HwZdkwDHq9HvV6nel0SqvVYrvdIh6Ph3Qch+VyqRYLhQJSSjRNw7IsfN9XgGKxSLfbJZfL0e/3aTabrFYr7vc7IujLcOh8PqunrNdr0uk0pVKJVCpFJBJRgEajweVyod1uMxgM2O12BAGUgRbU8DV2JpOhVquRz+cRQii3+XxOp9NRN3jVR5LPOp1OjEYjlSL8hclkgmmabDabt4d+m+S30vkD/R/IU4ABAPTZgnZdmG/PAAAAAElFTkSuQmCC"); background-repeat: no-repeat; background-position: 0 50%; text-indent: 30px; } .FollowByEmail .widget-content { display: none; } .searchBox input { border: 1px solid #eee; color: #212121; color: rgba(0,0,0,.87); font-size: 14px; padding: 8px 8px 8px 40px; width: 164px; font-family: Roboto, sans-serif; background: url("https://www.gstatic.com/images/icons/material/system/1x/search_grey600_24dp.png") 8px center no-repeat; } .searchBox ::-webkit-input-placeholder { /* WebKit, Blink, Edge */ color: rgba(0,0,0,.54); } .searchBox :-moz-placeholder { /* Mozilla Firefox 4 to 18 */ color: #000; opacity: 0.54; } .searchBox ::-moz-placeholder { /* Mozilla Firefox 19+ */ color: #000; opacity: 0.54; } .searchBox :-ms-input-placeholder { /* Internet Explorer 10-11 */ color: #757575; } .widget-item-control { margin-top: 0px; } .section { margin: 0; padding: 0; } #sidebar-top { border: 1px solid #eee; } #sidebar-top > div { margin: 16px 0; } .widget ul { line-height: 1.6; } /*main post*/ .post { margin-bottom:30px; } #main .post .title { margin: 0; } #main .post .title a { color: #212121; color: rgba(0,0,0,.87); font-weight: normal; font-size: 24px; } #main .post .title a:hover { text-decoration:none; color:#4184F3; } .message, #main .post .post-header { margin: 0; padding: 0; } #main .post .post-header .caption, #main .post .post-header .labels-caption, #main .post .post-footer .caption, #main .post .post-footer .labels-caption { color: #444; font-weight: 500; } #main .tr-caption-container td { text-align: left; } #main .post .tr-caption { color: #757575; color: rgba(0,0,0,.54); display: block; max-width: 560px; padding-bottom: 20px; } #main .post .tr-caption-container { line-height: 24px; margin: -1px 0 0 0 !important; padding: 4px 0; text-align: left; } #main .post .post-header .published{ font-size:11px; font-weight:bold; } .post-header .publishdate { font-size: 17px; font-weight:normal; color: #757575; color: rgba(0,0,0,.54); } #main .post .post-footer{ font-size:12px; padding-bottom: 21px; } .label-footer { margin-bottom: 12px; margin-top: 12px; } .comment-img { margin-right: 16px; opacity: 0.54; vertical-align: middle; } #main .post .post-header .published { margin-bottom: 40px; margin-top: -2px; } .post .post-content { color: #212121; color: rgba(0,0,0,.87); font-size: 17px; margin: 25px 0 36px 0; line-height: 32px; } .post-body .post-content ul, .post-body .post-content ol { margin: 16px 0; padding: 0 48px; } .post-summary { display: none; } /* Another old-style caption. */ .post-content div i, .post-content div + i { font-size: 14px; font-style: normal; color: #757575; color: rgba(0,0,0,.54); display: block; line-height: 24px; margin-bottom: 16px; text-align: left; } /* Another old-style caption (with link) */ .post-content a > i { color: #4184F3 !important; } /* Old-style captions for images. */ .post-content .separator + div:not(.separator) { margin-top: -16px; } /* Capture section headers. */ .post-content br + br + b, .post-content .space + .space + b, .post-content .separator + b { display: inline-block; margin-bottom: 8px; margin-top: 24px; } .post-content li { line-height: 32px; } /* Override all post images/videos to left align. */ .post-content .separator, .post-content > div { text-align: left; } .post-content .separator > a, .post-content .separator > span { margin-left: 0 !important; } .post-content img { max-width: 100%; height: auto; width: auto; } .post-content .tr-caption-container img { margin-bottom: 12px; } .post-content iframe, .post-content embed { max-width: 100%; } .post-content .carousel-container { margin-bottom: 48px; } #main .post-content b { font-weight: 500; } /* These are the main paragraph spacing tweaks. */ #main .post-content br { content: ' '; display: block; padding: 4px; } .post-content .space { display: block; height: 8px; } .post-content iframe + .space, .post-content iframe + br { padding: 0 !important; } #main .post .jump-link { margin-bottom:10px; } .post-content img, .post-content iframe { margin: 30px 0 20px 0; } .post-content > img:first-child, .post-content > iframe:first-child { margin-top: 0; } .col-right .section { padding: 0 16px; } #aside { background:#fff; border:1px solid #eee; border-top: 0; } #aside .widget { margin:0; } #aside .widget h2, #ArchiveList .toggle + a.post-count-link { color: #212121; color: rgba(0,0,0,.87); font-weight: 400 !important; margin: 0; } #ArchiveList .toggle { float: right; } #ArchiveList .toggle .material-icons { padding-top: 4px; } #sidebar .tab { cursor: pointer; } #sidebar .tab .arrow { display: inline-block; float: right; } #sidebar .tab .icon { display: inline-block; vertical-align: top; height: 24px; width: 24px; margin-right: 13px; margin-left: -1px; margin-top: 1px; color: #757575; color: rgba(0,0,0,.54); } #sidebar .widget-content > :first-child { padding-top: 8px; } #sidebar .active .tab .arrow { -ms-transform: rotate(180deg); transform: rotate(180deg); } #sidebar .arrow { color: #757575; color: rgba(0,0,0,.54); } #sidebar .widget h2 { font-size: 14px; line-height: 24px; display: inline-block; } #sidebar .widget .BlogArchive { padding-bottom: 8px; } #sidebar .widget { border-bottom: 1px solid #eee; box-shadow: 0px 1px 0 white; margin-bottom: 0; padding: 14px 0; min-height: 20px; } #sidebar .widget:last-child { border-bottom: none; box-shadow: none; margin-bottom: 0; } #sidebar ul { margin: 0; padding: 0; } #sidebar ul li { list-style:none; padding:0; } #sidebar ul li a { line-height: 32px; } #sidebar .archive { background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAYCAYAAADzoH0MAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAE1JREFUeNpiNDY23s9AAWBioBCwYBM8c+YMVsUmJibEGYBNMS5DaeMFfDYSZQA2v9I3FrB5AZeriI4FmnrBccCT8mhmGs1MwyAzAQQYAKEWG9zm9QFEAAAAAElFTkSuQmCC"); height: 24px; line-height: 24px; padding-left: 30px; } #sidebar .labels { background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABEAAAARCAYAAAA7bUf6AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAUxJREFUeNpiNDY23s9AAMycOfM7UF05kHkZmzwTMkdSUhKrIcXFxZy3bt3qBjIN8RrS09PDsHnzZjCNDr58+cKQlpbGDjSoHcg1w2oIyAUODg5gARCNzUVIBrUCuVYYhjx//pzhwIEDYAEQDeJjA1CDWIAGNQK59jBxRuSABbkAlwHIgIeHh2HWrFn/1NTU2oDcvSgBS4wBSC5iArqoCsj1YGIgEyAZVMoEchqlBjEB/cZAiUHg2AEGznpKDAImxOeM////B4VLKtBvEUCngZ1ILKivr3/u6+ubBzJAGZQ9gC5aQoqLgAY8BhkAZL4BuQQkxgXE34A4BuiiZEIuAhrwEGhAEZD5DpzYoIaA2UAM4kQADUrHZRDUgAIg8wO2XAwzbQXQa5OweQ1owB10AyA6gS7BgX1u3ry5397eHow3bdo0EyjGi00tQIABANPgyAH1q1eaAAAAAElFTkSuQmCC"); height: 20px; line-height: 20px; padding-left: 30px; } #sidebar .rss a { background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABIAAAASCAYAAABWzo5XAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAX5JREFUeNqsVDGSgkAQHL2rIiIikohIc/EBRkbwAIwuwgfwAXiAD9AHSI7kEkECRCb6AIyINDLx7K0aa6kT7uq0q7YYtnZ7umdnt7darXbr9Zpegeu61DNNc0dvwCcH4/GYJpMJnc9nOhwOVJbl/4hAAokMECZJQtvt9k+kH7qufyEYDAakqqqYxFdRFBqNRmTbNg2HQ0rTlK7XayvR0xqBdDqdkuM4dE/0ULhYLOh4PHYrknG5XGi/31MYhuL/nkwonM1mlGUZ1XXdrsiyLGEDhY7juJEZ1u5tIixDGdYhmYw+B7CAzPP5nDabjdgIAgCksMX1832/3drtdqPT6SQWapomiGEFNkDEdpDMMAzK81ys/7XYy+XyoQgq2WoURSIJ2iIIgp/WZCCTvFm2wgeAU31aI3Q2GhIDMeB53qPYPIcm5VrxXIOIOxsDMStjVawAc1VViRgN22lNBiuQN3GR+SY07hpOoStmFQAKXRRFY93bnpG+fONfedi+BRgAbkS8Fxp7QQIAAAAASUVORK5CYII="); } #sidebar .subscription a { background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABEAAAALCAYAAACZIGYHAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAUBJREFUeNrMkSGLAlEUhb+ZB4JFi8mx2cz+ApvhRUGTcUCrNqNJDYIi+DO0GUwmQXDK2DSIoGgZcSaIjDrzwrK4ssvChj1w0733O+fdp+m6PozH4yQSCfb7Pa7r8pOi0SjJZBLP8zgej4gAIMvlMuPxmADIYrHger1+C6lUKmo+NJ/NZojb7SZDWiwWo1qtks1msW2bw+HwZdkwDHq9HvV6nel0SqvVYrvdIh6Ph3Qch+VyqRYLhQJSSjRNw7IsfN9XgGKxSLfbJZfL0e/3aTabrFYr7vc7IujLcOh8PqunrNdr0uk0pVKJVCpFJBJRgEajweVyod1uMxgM2O12BAGUgRbU8DV2JpOhVquRz+cRQii3+XxOp9NRN3jVR5LPOp1OjEYjlSL8hclkgmmabDabt4d+m+S30vkD/R/IU4ABAPTZgnZdmG/PAAAAAElFTkSuQmCC"); } #sidebar-bottom { background: #f5f5f5; border-top:1px solid #eee; } #sidebar-bottom .widget { border-bottom: 1px solid #e0e0e0; padding: 15px 0; text-align: center; } #sidebar-bottom > div:last-child { border-bottom: 0; } #sidebar-bottom .text { line-height: 20px; } /* Home, forward, and backward pagination. */ .blog-pager { border-top : 1px #e0e0e0 solid; padding-top: 10px; margin-top: 15px; text-align: right !important; } #blog-pager { margin-botom: 0; margin-top: -14px; padding: 16px 0 0 0; } #blog-pager a { display: inline-block; } .blog-pager i.disabled { opacity: 0.2 !important; } .blog-pager i { color: black; margin-left: 16px; opacity: 0.54; } .blog-pager i:hover, .blog-pager i:active { opacity: 0.87; } #blog-pager-older-link, #blog-pager-newer-link { float: none; } .gplus-profile { background-color: #fafafa; border: 1px solid #eee; overflow: hidden; width: 212px; } .gplus-profile-inner { margin-left: -1px; margin-top: -1px; } /* Sidebar follow buttons. */ .followgooglewrapper { padding: 12px 0 0 0; } .loading { visibility: hidden; } .detail-page .post-footer .cmt_iframe_holder { padding-top: 40px !important; } /** Desktop **/ @media (max-width: 900px) { .col-right { display: none; } .col-main { margin-right: 0; min-width: initial; } .footer-outer { display: none; } .cols-wrapper { min-width: initial; } .google-footer-outer { background-color: #f5f5f5; } } /** Tablet **/ @media (max-width: 712px) { .header-outer, .cols-wrapper, .footer-outer, .google-footer-outer { padding: 0 40px; } } /* An extra breakpoint accommodating for long blog titles. */ @media (max-width: 600px) { .header-left { height: 100%; top: inherit; margin-top: 0; -webkit-transform: initial; transform: initial; } .header-title { margin-top: 18px; } .header-inner .google-logo { height: 40px; margin-top: 3px; } .header-inner .google-logo img { height: 42px; } .header-title h2 { font-size: 32px; line-height: 40px; } .header-desc { bottom: 24px; position: absolute; } } /** Mobile/small desktop window; also landscape. **/ @media (max-width: 480px), (max-height: 480px) { .header-outer, .cols-wrapper, .footer-outer, .google-footer-outer { padding: 0 16px; } .cols-wrapper { margin-top: 0; } .post-header .publishdate, .post .post-content { font-size: 16px; } .post .post-content { line-height: 28px; margin-bottom: 30px; } .post { margin-top: 30px; } .byline-author { display: block; font-size: 12px; line-height: 24px; margin-top: 6px; } #main .post .title a { font-weight: 500; color: #4c4c4c; color: rgba(0,0,0,.70); } #main .post .post-header { padding-bottom: 12px; } #main .post .post-header .published { margin-bottom: -8px; margin-top: 3px; } .post .read-more { display: block; margin-top: 14px; } .post .tr-caption { font-size: 12px; } #main .post .title a { font-size: 20px; line-height: 30px; } .post-content iframe { /* iframe won't keep aspect ratio when scaled down. */ max-height: 240px; } .post-content .separator img, .post-content .tr-caption-container img, .post-content iframe { margin-left: -16px; max-width: inherit; width: calc(100% + 32px); } .post-content table, .post-content td { width: 100%; } #blog-pager { margin: 0; padding: 16px 0; } /** List page tweaks. **/ .list-page .post-original { display: none; } .list-page .post-summary { display: block; } .list-page .comment-container { display: none; } .list-page #blog-pager { padding-top: 0; border: 0; margin-top: -8px; } .list-page .label-footer { display: none; } .list-page #main .post .post-footer { border-bottom: 1px solid #eee; margin: -16px 0 0 0; padding: 0 0 20px 0; } .list-page .post .share { display: none; } /** Detail page tweaks. **/ .detail-page .post-footer .cmt_iframe_holder { padding-top: 32px !important; } .detail-page .label-footer { margin-bottom: 0; } .detail-page #main .post .post-footer { padding-bottom: 0; } .detail-page #comments { display: none; } } [data-about-pullquote], [data-is-preview], [data-about-syndication] { display: none; } </style> <noscript> <style> .loading { visibility: visible }</style> </noscript> <script type='text/javascript'> (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) })(window,document,'script','https://www.google-analytics.com/analytics.js','ga'); ga('create', 'UA-18009-4', 'auto', 'blogger'); ga('blogger.send', 'pageview'); </script> <link href='https://www.blogger.com/dyn-css/authorization.css?targetBlogID=32069983&zx=8855dad6-3029-4476-9a6a-423344a04200' media='none' onload='if(media!='all')media='all'' rel='stylesheet'/><noscript><link href='https://www.blogger.com/dyn-css/authorization.css?targetBlogID=32069983&zx=8855dad6-3029-4476-9a6a-423344a04200' rel='stylesheet'/></noscript> <meta name='google-adsense-platform-account' content='ca-host-pub-1556223355139109'/> <meta name='google-adsense-platform-domain' content='blogspot.com'/> </head> <body> <script type='text/javascript'> //<![CDATA[ var axel = Math.random() + ""; var a = axel * 10000000000000; document.write('<iframe src="https://2542116.fls.doubleclick.net/activityi;src=2542116;type=gblog;cat=googl0;ord=ord=' + a + '?" width="1" height="1" frameborder="0" style="display:none"></iframe>'); //]]> </script> <noscript> <img alt='' height='1' src='https://ad.doubleclick.net/ddm/activity/src=2542116;type=gblog;cat=googl0;ord=1?' width='1'/> </noscript>  <div class='header-outer'> <div class='header-inner'> <div class='section' id='header'><div class='widget Header' data-version='1' id='Header1'> <div class='header-left'> <div class='header-title'> <a class='google-logo' href='https://webmasters.googleblog.com/?hl=en_US'> <img height='50' src='https://www.gstatic.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png'/> </a> <a href='/'> <h2> Webmaster Central Blog </h2> </a> </div> <div class='header-desc'> Official news on crawling and indexing sites for the Google index </div> </div> </div></div> </div> </div>  <div class='cols-wrapper loading'> <div class='col-main-wrapper'> <div class='col-main'> <div class='section' id='main'><div class='widget Blog' data-version='1' id='Blog1'> <div class='post' data-id='632882555274287029' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/08/you-askgooglewebmasters-we-answer.html?hl=en_US' itemprop='url' title='You #AskGoogleWebmasters, we answer'> You #AskGoogleWebmasters, we answer </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, August 15, 2019 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p>We love to help folks make awesome websites. For a while now, we've been answering questions from developers, site-owners, webmasters, and of course SEOs in our office hours hangouts, in the help forums, and at events. Recently, we've (re-)started answering your questions in a video series called <a href="https://www.youtube.com/watch?v=_SDIN0KiQp4&list=PLKoqnv2vTMUM9wKeb-Gvm8bgpFM72yiXw">#AskGoogleWebmasters</a> on our <a href="https://youtube.com/googlewebmasters?sub_confirmation=1">YouTube channel</a>. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgBRovRvfRFyZFq50-pNMizcAeiEN85ogPZC90n-dmcd1Q-XPVcHxyEMn7wjPjwKn7N_0atLRjsLHTL0epKWKH7PeuBa0fx6CjBYAw418vpl-FBjxxIMwY-tIs0i4BuKI3aCRxV/s1600/Screenshot+from+2019-08-15+14-02-37.png" imageanchor="1" ><img border="0" data-original-height="618" data-original-width="827" height="299" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgBRovRvfRFyZFq50-pNMizcAeiEN85ogPZC90n-dmcd1Q-XPVcHxyEMn7wjPjwKn7N_0atLRjsLHTL0epKWKH7PeuBa0fx6CjBYAw418vpl-FBjxxIMwY-tIs0i4BuKI3aCRxV/s400/Screenshot+from+2019-08-15+14-02-37.png" width="400" /></a> <br><small>(At Google, behind the scenes, during the recording of one of the episodes.)</small>  </p> <p>When we started with the <a href="https://www.google.com/webmasters/connect/">webmaster office-hours</a> back in 2012, we thought we'd be able to get through all questions within a few months, or perhaps a year. Well ... the questions still haven't stopped -- it's great to see such engagement when it comes to making great websites! </p> <p>To help make it a bit easier to find answers, we've started producing shorter videos answering individual questions. Some of the questions may seem fairly trivial to you, others don't always have simple answers, but all of them are worth answering.</p> <p>Curious about the first episodes? Check out the videos below and the playlist for all episodes!</p> <iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/_SDIN0KiQp4?list=PLKoqnv2vTMUM9wKeb-Gvm8bgpFM72yiXw" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> <p>To ask a question, just use the hashtag <a href="https://twitter.com/hashtag/AskGoogleWebmasters">#AskGoogleWebmasters</a> on Twitter. While we can't get to all submissions, we regularly pick up the questions there to use in future episodes. We pick questions primarily about websites & websearch, which are relevant to many sites. Want to stay in the loop? Make sure to <a href="https://www.youtube.com/googlewebmasters?sub_confirmation=1">subscribe to our channel</a>. If you'd like to discuss the questions or other important webmaster topics, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">webmaster help forums</a> and chat with the awesome experts there. </p> <br> <span class="byline-author">Posted by <a href="https://twitter.com/johnmu#hashtag">John Mueller</a>, Google Switzerland</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p>We love to help folks make awesome websites. For a while now, we've been answering questions from developers, site-owners, webmasters, and of course SEOs in our office hours hangouts, in the help forums, and at events. Recently, we've (re-)started answering your questions in a video series called <a href="https://www.youtube.com/watch?v=_SDIN0KiQp4&list=PLKoqnv2vTMUM9wKeb-Gvm8bgpFM72yiXw">#AskGoogleWebmasters</a> on our <a href="https://youtube.com/googlewebmasters?sub_confirmation=1">YouTube channel</a>. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgBRovRvfRFyZFq50-pNMizcAeiEN85ogPZC90n-dmcd1Q-XPVcHxyEMn7wjPjwKn7N_0atLRjsLHTL0epKWKH7PeuBa0fx6CjBYAw418vpl-FBjxxIMwY-tIs0i4BuKI3aCRxV/s1600/Screenshot+from+2019-08-15+14-02-37.png" imageanchor="1" ><img border="0" data-original-height="618" data-original-width="827" height="299" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgBRovRvfRFyZFq50-pNMizcAeiEN85ogPZC90n-dmcd1Q-XPVcHxyEMn7wjPjwKn7N_0atLRjsLHTL0epKWKH7PeuBa0fx6CjBYAw418vpl-FBjxxIMwY-tIs0i4BuKI3aCRxV/s400/Screenshot+from+2019-08-15+14-02-37.png" width="400" /></a> <br><small>(At Google, behind the scenes, during the recording of one of the episodes.)</small>  </p> <p>When we started with the <a href="https://www.google.com/webmasters/connect/">webmaster office-hours</a> back in 2012, we thought we'd be able to get through all questions within a few months, or perhaps a year. Well ... the questions still haven't stopped -- it's great to see such engagement when it comes to making great websites! </p> <p>To help make it a bit easier to find answers, we've started producing shorter videos answering individual questions. Some of the questions may seem fairly trivial to you, others don't always have simple answers, but all of them are worth answering.</p> <p>Curious about the first episodes? Check out the videos below and the playlist for all episodes!</p> <iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/_SDIN0KiQp4?list=PLKoqnv2vTMUM9wKeb-Gvm8bgpFM72yiXw" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> <p>To ask a question, just use the hashtag <a href="https://twitter.com/hashtag/AskGoogleWebmasters">#AskGoogleWebmasters</a> on Twitter. While we can't get to all submissions, we regularly pick up the questions there to use in future episodes. We pick questions primarily about websites & websearch, which are relevant to many sites. Want to stay in the loop? Make sure to <a href="https://www.youtube.com/googlewebmasters?sub_confirmation=1">subscribe to our channel</a>. If you'd like to discuss the questions or other important webmaster topics, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">webmaster help forums</a> and chat with the awesome experts there. </p> <br> <span class="byline-author">Posted by <a href="https://twitter.com/johnmu#hashtag">John Mueller</a>, Google Switzerland</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:You #AskGoogleWebmasters, we answer&url=https://webmasters.googleblog.com/2019/08/you-askgooglewebmasters-we-answer.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2019/08/you-askgooglewebmasters-we-answer.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2019/08/you-askgooglewebmasters-we-answer.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/encryption?hl=en_US' rel='tag'> encryption </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US' rel='tag'> mobile-friendly </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en_US' rel='tag'> webmaster community </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/youtube%20channel?hl=en_US' rel='tag'> youtube channel </a> </span> </div> </div> </div> <div class='post' data-id='9103369277615781852' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/08/evergreen-googlebot-in-testing-tools.html?hl=en_US' itemprop='url' title='Googlebot evergreen rendering in our testing tools'> Googlebot evergreen rendering in our testing tools </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, August 07, 2019 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <div style="text-align: left;"> Today we updated most of <a href="https://developers.google.com/search/tools/">our testing tools</a> so they are using the evergreen Chromium renderer. This affects our testing tools like the mobile-friendly test or the URL inspection tool in Search Console. In this post we look into what this means and what went into making this update happen.<br /> <br /></div> <h3 style="text-align: left;"> The evergreen Chromium renderer</h3> At Google I/O this year we were happy to announce <a href="https://www.youtube.com/watch/ufcijo46LCU?t=10m43s">the new evergreen Googlebot</a>.<br /> <br /> At its core the update is a switch from Chrome 41 as the rendering engine to the latest stable Chromium. Googlebot is now using the latest stable Chromium to run JavaScript and render pages. We will continue to update Googlebot along with the stable Chromium, hence we call it "evergreen".<br /> <br /> <table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody> <tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhKTeQjcclgL-R4Yg6BME-esMUCeenEONvb-bucdqTx8Bb1wngzalAsQau4hkmQWuZfz9HxkVH2utbNtBXbPCx7k8WXOspGvwfI-SV3GgGIaWkf1ggyz7-HJiVLI6fFKoH3Fo8s/s1600/wrs-comparison.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img alt="Comparison between the rendering of a JS-powered website in the old and new Googlebot" border="0" data-original-height="800" data-original-width="1600" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhKTeQjcclgL-R4Yg6BME-esMUCeenEONvb-bucdqTx8Bb1wngzalAsQau4hkmQWuZfz9HxkVH2utbNtBXbPCx7k8WXOspGvwfI-SV3GgGIaWkf1ggyz7-HJiVLI6fFKoH3Fo8s/s640/wrs-comparison.png" title="" width="640" /></a></td></tr> <tr><td class="tr-caption" style="text-align: center;">A JavaScript-powered demo website staying blank in the old Googlebot but working fine in the new Googlebot.</td></tr> </tbody></table> <h3 style="text-align: left;"> What this means for your websites</h3> We are very happy to bring the latest features of the web platform not only to Googlebot but to the tools that let you see what Googlebot sees as well. This means websites using ES6+, Web Components and <a href="https://chromereleases.googleblog.com/">1000+ new web platform features</a> are now rendered with the latest stable Chromium, both in Googlebot and our testing tools.<br /> <table cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody> <tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgeComtJVJKvd38CoFfHKz1hpU308gKNJjAsjwR-MaxdOA9Any-47vEy8y6CpaCHJeEYLaWn2D-J-tURtUOCdSYW-Bww7b4iKcKZjiyj55yr6NnHQq7NgATL70z7wMxYVuS_sAQ/s1600/mft-comparison.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img alt="A comparison showing the old and the new mobile-friendly test. The old mobile-friendly test rendered a blank page and the new one renders the page correctly" border="0" data-original-height="315" data-original-width="1024" height="193" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgeComtJVJKvd38CoFfHKz1hpU308gKNJjAsjwR-MaxdOA9Any-47vEy8y6CpaCHJeEYLaWn2D-J-tURtUOCdSYW-Bww7b4iKcKZjiyj55yr6NnHQq7NgATL70z7wMxYVuS_sAQ/s640/mft-comparison.png" title="" width="640" /></a></td></tr> <tr><td class="tr-caption" style="text-align: center;"><span id="docs-internal-guid-d6ec87e8-7fff-8e15-e97e-c3fd046f0639"><span style="font-size: 11pt; vertical-align: baseline; white-space: pre-wrap;">While the previous version of the mobile-friendly test doesn't show the page content, the new version does.</span></span></td></tr> </tbody></table> <h3 style="text-align: left;"> What the update changes in our testing tools</h3> Our testing tools reflect how Googlebot processes your pages as closely as possible. With the update to the new Googlebot, we had to update them to use the same renderer as Googlebot.<br /> <br /> The change will affect the rendering within the following tools:<br /> <ul style="text-align: left;"> <li><a href="https://g.co/searchconsole">Search Console</a>'s URL inspection tool </li> <li><a href="https://g.co/mobile-friendly">Mobile-friendly test</a></li> <li><a href="https://search.google.com/test/rich-results">Rich results test</a></li> <li><a href="https://search.google.com/test/amp">AMP test</a></li> </ul> We tested these updates and based on the feedback we have switched the tools listed previously to the new evergreen Googlebot. A lot of the feedback came from Googlers and the community. <a href="https://productexperts.withgoogle.com/">Product Experts</a> and <a href="https://developers.google.com/community/experts/">Google Developer Experts</a> helped us make sure the update works well.<br /> <br /> Note: The new Googlebot still uses the same <a href="https://support.google.com/webmasters/answer/1061943?hl=en">user agent</a> as before the update. There will be more information about an update to the user agent in the near future. For now, Googlebot's user agent and the user agent used in the testing tools does not change.<br /> <br /> We are excited about this update and are looking forward to your feedback and questions on <a href="https://twitter.com/googlewmc">Twitter</a>, the <a href="https://support.google.com/webmasters/community?hl=en">webmaster forum</a> or in our <a href="//google.com/webmasters/connect">webmaster office hours</a>.<br /> <br /> <span class="byline-author">Posted by Zoe Clifford, Software Engineer in the Web Rendering Service team & Martin Splitt, friendly internet fairy at Google WTA</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <div style="text-align: left;"> Today we updated most of <a href="https://developers.google.com/search/tools/">our testing tools</a> so they are using the evergreen Chromium renderer. This affects our testing tools like the mobile-friendly test or the URL inspection tool in Search Console. In this post we look into what this means and what went into making this update happen.<br /> <br /></div> <h3 style="text-align: left;"> The evergreen Chromium renderer</h3> At Google I/O this year we were happy to announce <a href="https://www.youtube.com/watch/ufcijo46LCU?t=10m43s">the new evergreen Googlebot</a>.<br /> <br /> At its core the update is a switch from Chrome 41 as the rendering engine to the latest stable Chromium. Googlebot is now using the latest stable Chromium to run JavaScript and render pages. We will continue to update Googlebot along with the stable Chromium, hence we call it "evergreen".<br /> <br /> <table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody> <tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhKTeQjcclgL-R4Yg6BME-esMUCeenEONvb-bucdqTx8Bb1wngzalAsQau4hkmQWuZfz9HxkVH2utbNtBXbPCx7k8WXOspGvwfI-SV3GgGIaWkf1ggyz7-HJiVLI6fFKoH3Fo8s/s1600/wrs-comparison.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img alt="Comparison between the rendering of a JS-powered website in the old and new Googlebot" border="0" data-original-height="800" data-original-width="1600" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhKTeQjcclgL-R4Yg6BME-esMUCeenEONvb-bucdqTx8Bb1wngzalAsQau4hkmQWuZfz9HxkVH2utbNtBXbPCx7k8WXOspGvwfI-SV3GgGIaWkf1ggyz7-HJiVLI6fFKoH3Fo8s/s640/wrs-comparison.png" title="" width="640" /></a></td></tr> <tr><td class="tr-caption" style="text-align: center;">A JavaScript-powered demo website staying blank in the old Googlebot but working fine in the new Googlebot.</td></tr> </tbody></table> <h3 style="text-align: left;"> What this means for your websites</h3> We are very happy to bring the latest features of the web platform not only to Googlebot but to the tools that let you see what Googlebot sees as well. This means websites using ES6+, Web Components and <a href="https://chromereleases.googleblog.com/">1000+ new web platform features</a> are now rendered with the latest stable Chromium, both in Googlebot and our testing tools.<br /> <table cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody> <tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgeComtJVJKvd38CoFfHKz1hpU308gKNJjAsjwR-MaxdOA9Any-47vEy8y6CpaCHJeEYLaWn2D-J-tURtUOCdSYW-Bww7b4iKcKZjiyj55yr6NnHQq7NgATL70z7wMxYVuS_sAQ/s1600/mft-comparison.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img alt="A comparison showing the old and the new mobile-friendly test. The old mobile-friendly test rendered a blank page and the new one renders the page correctly" border="0" data-original-height="315" data-original-width="1024" height="193" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgeComtJVJKvd38CoFfHKz1hpU308gKNJjAsjwR-MaxdOA9Any-47vEy8y6CpaCHJeEYLaWn2D-J-tURtUOCdSYW-Bww7b4iKcKZjiyj55yr6NnHQq7NgATL70z7wMxYVuS_sAQ/s640/mft-comparison.png" title="" width="640" /></a></td></tr> <tr><td class="tr-caption" style="text-align: center;"><span id="docs-internal-guid-d6ec87e8-7fff-8e15-e97e-c3fd046f0639"><span style="font-size: 11pt; vertical-align: baseline; white-space: pre-wrap;">While the previous version of the mobile-friendly test doesn't show the page content, the new version does.</span></span></td></tr> </tbody></table> <h3 style="text-align: left;"> What the update changes in our testing tools</h3> Our testing tools reflect how Googlebot processes your pages as closely as possible. With the update to the new Googlebot, we had to update them to use the same renderer as Googlebot.<br /> <br /> The change will affect the rendering within the following tools:<br /> <ul style="text-align: left;"> <li><a href="https://g.co/searchconsole">Search Console</a>'s URL inspection tool </li> <li><a href="https://g.co/mobile-friendly">Mobile-friendly test</a></li> <li><a href="https://search.google.com/test/rich-results">Rich results test</a></li> <li><a href="https://search.google.com/test/amp">AMP test</a></li> </ul> We tested these updates and based on the feedback we have switched the tools listed previously to the new evergreen Googlebot. A lot of the feedback came from Googlers and the community. <a href="https://productexperts.withgoogle.com/">Product Experts</a> and <a href="https://developers.google.com/community/experts/">Google Developer Experts</a> helped us make sure the update works well.<br /> <br /> Note: The new Googlebot still uses the same <a href="https://support.google.com/webmasters/answer/1061943?hl=en">user agent</a> as before the update. There will be more information about an update to the user agent in the near future. For now, Googlebot's user agent and the user agent used in the testing tools does not change.<br /> <br /> We are excited about this update and are looking forward to your feedback and questions on <a href="https://twitter.com/googlewmc">Twitter</a>, the <a href="https://support.google.com/webmasters/community?hl=en">webmaster forum</a> or in our <a href="//google.com/webmasters/connect">webmaster office hours</a>.<br /> <br /> <span class="byline-author">Posted by Zoe Clifford, Software Engineer in the Web Rendering Service team & Martin Splitt, friendly internet fairy at Google WTA</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Googlebot evergreen rendering in our testing tools&url=https://webmasters.googleblog.com/2019/08/evergreen-googlebot-in-testing-tools.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2019/08/evergreen-googlebot-in-testing-tools.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2019/08/evergreen-googlebot-in-testing-tools.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/javascript?hl=en_US' rel='tag'> javascript </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US' rel='tag'> mobile-friendly </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/rendering?hl=en_US' rel='tag'> rendering </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='4784551626083621006' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/04/user-experience-improvements-with-page.html?hl=en_US' itemprop='url' title='User experience improvements with page speed in mobile search'> User experience improvements with page speed in mobile search </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, April 04, 2019 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p>To help users find the answers to their questions faster, we included <a href="https://webmasters.googleblog.com/2018/01/using-page-speed-in-mobile-search.html">page speed</a> as a ranking factor for mobile searches in 2018. Since then, we've observed improvements on many pages across the web. We want to recognize the performance improvements webmasters have made over the past year. A few highlights:</p> <ul><li>For the slowest one-third of traffic, we saw <a href="https://developers.google.com/web/fundamentals/performance/user-centric-performance-metrics">user-centric performance metrics</a> improve by 15% to 20% in 2018. As a comparison, no improvement was seen in 2017.</li> <li>We observed improvements across the whole web ecosystem. On a per country basis, more than 95% of countries had improved speeds.</li> <li>When a page is slow to load, users are more likely to abandon the navigation. Thanks to these speed improvements, we've observed a 20% reduction in abandonment rate for navigations initiated from Search, a metric that site owners can now also measure via the <a href="https://w3c.github.io/network-error-logging/">Network Error Logging API</a> available <a href="https://developers.google.com/web/updates/2018/09/reportingapi#nel">in Chrome</a>.</li> <li>In 2018, developers ran over a billion <a href="https://developers.google.com/speed/pagespeed/insights/">PageSpeed Insights</a> audits to identify performance optimization opportunities for over 200 million unique urls.</li></ul> <p>Great work and thank you! We encourage all webmasters to optimize their sites’ user experience. If you're unsure how your pages are performing, the following tools and documents can be useful:</p> <ol><li><a href="https://developers.google.com/speed/pagespeed/insights/">PageSpeed Insights</a> provides page analysis and optimization recommendations.</li> <li>Google <a href="https://developers.google.com/web/tools/chrome-user-experience-report/">Chrome User Experience Report</a> provides the user experience metrics for how real-world Chrome users experience popular destinations on the web.</li> <li>Documentation on <a href="https://developers.google.com/web/fundamentals/performance/why-performance-matters/">performance on Web Fundamentals</a>. </li> </ol> <p>For any questions, feel free to drop by our help forums (like the <a href="https://support.google.com/webmasters/community">webmaster community</a>) to chat with other experts.</p> <br> <span class="byline-author">Posted by Genqing Wu and Doantam Phan</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p>To help users find the answers to their questions faster, we included <a href="https://webmasters.googleblog.com/2018/01/using-page-speed-in-mobile-search.html">page speed</a> as a ranking factor for mobile searches in 2018. Since then, we've observed improvements on many pages across the web. We want to recognize the performance improvements webmasters have made over the past year. A few highlights:</p> <ul><li>For the slowest one-third of traffic, we saw <a href="https://developers.google.com/web/fundamentals/performance/user-centric-performance-metrics">user-centric performance metrics</a> improve by 15% to 20% in 2018. As a comparison, no improvement was seen in 2017.</li> <li>We observed improvements across the whole web ecosystem. On a per country basis, more than 95% of countries had improved speeds.</li> <li>When a page is slow to load, users are more likely to abandon the navigation. Thanks to these speed improvements, we've observed a 20% reduction in abandonment rate for navigations initiated from Search, a metric that site owners can now also measure via the <a href="https://w3c.github.io/network-error-logging/">Network Error Logging API</a> available <a href="https://developers.google.com/web/updates/2018/09/reportingapi#nel">in Chrome</a>.</li> <li>In 2018, developers ran over a billion <a href="https://developers.google.com/speed/pagespeed/insights/">PageSpeed Insights</a> audits to identify performance optimization opportunities for over 200 million unique urls.</li></ul> <p>Great work and thank you! We encourage all webmasters to optimize their sites’ user experience. If you're unsure how your pages are performing, the following tools and documents can be useful:</p> <ol><li><a href="https://developers.google.com/speed/pagespeed/insights/">PageSpeed Insights</a> provides page analysis and optimization recommendations.</li> <li>Google <a href="https://developers.google.com/web/tools/chrome-user-experience-report/">Chrome User Experience Report</a> provides the user experience metrics for how real-world Chrome users experience popular destinations on the web.</li> <li>Documentation on <a href="https://developers.google.com/web/fundamentals/performance/why-performance-matters/">performance on Web Fundamentals</a>. </li> </ol> <p>For any questions, feel free to drop by our help forums (like the <a href="https://support.google.com/webmasters/community">webmaster community</a>) to chat with other experts.</p> <br> <span class="byline-author">Posted by Genqing Wu and Doantam Phan</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:User experience improvements with page speed in mobile search&url=https://webmasters.googleblog.com/2019/04/user-experience-improvements-with-page.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2019/04/user-experience-improvements-with-page.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2019/04/user-experience-improvements-with-page.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/mobile?hl=en_US' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US' rel='tag'> mobile-friendly </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/performance?hl=en_US' rel='tag'> performance </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/speed?hl=en_US' rel='tag'> speed </a> </span> </div> </div> </div> <div class='post' data-id='728567517365270219' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2018/08/links-mobile-usability-and-site.html?hl=en_US' itemprop='url' title='Links, Mobile Usability, and site management in the new Search Console'> Links, Mobile Usability, and site management in the new Search Console </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, August 21, 2018 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>More features are coming to the <a href="https://webmasters.googleblog.com/2018/01/introducing-new-search-console.html">new Search Console</a>. This time we've focused on importing existing popular features from the old Search Console to the new product.</p> <h3>Links Report</h3> <p>Search Console users value the ability to see links to and within their site, as Google Search sees them. Today, we are rolling out the new <a href="https://support.google.com/webmasters/answer/9049606">Links</a> report, which combines the functionality of the “Links to your site” and “Internal Links” reports on the old Search Console. We hope you find this useful!</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEidC0Z8YyXmOMc0EusA6gsvlf5kTu-VkZKS9IeT2lkNb18gMEPb-pZXAHFeA0rd18NSU5l7cdwRicKPID2FSr-zXXrKKwBUoQnVHxDTH7s6GthIqDUPSxxgxELjDkL43qT7KQRh/s1600/image01.png" imageanchor="1" ><img border="0" data-original-height="1266" data-original-width="1084" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEidC0Z8YyXmOMc0EusA6gsvlf5kTu-VkZKS9IeT2lkNb18gMEPb-pZXAHFeA0rd18NSU5l7cdwRicKPID2FSr-zXXrKKwBUoQnVHxDTH7s6GthIqDUPSxxgxELjDkL43qT7KQRh/s400/image01.png" width="342" /></a> </p> <h3>Mobile Usability report</h3> <p><a href="https://developers.google.com/search/mobile-sites/">Mobile Usability</a> is an important priority for all site owners. In order to help site owners with fixing mobile usability issues, we launched the Mobile Usability report on the new Search Console. Issue names are the same as in the old report but we now allow users to submit a validation and reindexing request when an issue is fixed, similar to other reports in the new Search Console. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjjTDY73T3OUo7Af1Mn9o0207VwXtzRgn09hdgpRs24B0myv3_jsX2hw1WTtK8mUn7aAoMTpSSK8fsmMm6Y8iXCTxkEWXU3XjQQY2rsvJWFjD4e4CNTp0KOYEkE_UbXnS8ljPNr/s1600/image02.png" imageanchor="1" ><img border="0" data-original-height="1262" data-original-width="1086" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjjTDY73T3OUo7Af1Mn9o0207VwXtzRgn09hdgpRs24B0myv3_jsX2hw1WTtK8mUn7aAoMTpSSK8fsmMm6Y8iXCTxkEWXU3XjQQY2rsvJWFjD4e4CNTp0KOYEkE_UbXnS8ljPNr/s400/image02.png" width="344" /></a> </p> <h3>Site and user management</h3> <p>To make the new Search Console feel more like home, we’ve added the ability to add and verify new sites, and manage your property's users and permissions, directly in new Search Console using our newly added <a href="https://support.google.com/webmasters/answer/7687465">settings</a> page. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjzcG-07EbfT8litkW2iV5syOSrPBkbN7hKytuycE-PnWzo9c9I4UF4S1TJEyatDYvS2-HMKvr2Lmx2U2q4DZIS_MLdzfiu2t4z14s4xawR4M9DhCHKRXeLrmfyr5mN7LMUbPX0/s1600/image03.png" imageanchor="1" ><img border="0" data-original-height="1274" data-original-width="1090" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjzcG-07EbfT8litkW2iV5syOSrPBkbN7hKytuycE-PnWzo9c9I4UF4S1TJEyatDYvS2-HMKvr2Lmx2U2q4DZIS_MLdzfiu2t4z14s4xawR4M9DhCHKRXeLrmfyr5mN7LMUbPX0/s400/image03.png" width="342" /></a> </p> <h3>Keep sending feedback</h3> <p>As always, we would love to get your feedback through the tools directly and our <a href="https://support.google.com/webmasters/go/community">help forums</a> so please share and let us know how we're doing.</p> <br> <span class="byline-author">Posted by Ariel Kroszynski and Roman Kecher - Search Console engineers</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>More features are coming to the <a href="https://webmasters.googleblog.com/2018/01/introducing-new-search-console.html">new Search Console</a>. This time we've focused on importing existing popular features from the old Search Console to the new product.</p> <h3>Links Report</h3> <p>Search Console users value the ability to see links to and within their site, as Google Search sees them. Today, we are rolling out the new <a href="https://support.google.com/webmasters/answer/9049606">Links</a> report, which combines the functionality of the “Links to your site” and “Internal Links” reports on the old Search Console. We hope you find this useful!</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEidC0Z8YyXmOMc0EusA6gsvlf5kTu-VkZKS9IeT2lkNb18gMEPb-pZXAHFeA0rd18NSU5l7cdwRicKPID2FSr-zXXrKKwBUoQnVHxDTH7s6GthIqDUPSxxgxELjDkL43qT7KQRh/s1600/image01.png" imageanchor="1" ><img border="0" data-original-height="1266" data-original-width="1084" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEidC0Z8YyXmOMc0EusA6gsvlf5kTu-VkZKS9IeT2lkNb18gMEPb-pZXAHFeA0rd18NSU5l7cdwRicKPID2FSr-zXXrKKwBUoQnVHxDTH7s6GthIqDUPSxxgxELjDkL43qT7KQRh/s400/image01.png" width="342" /></a> </p> <h3>Mobile Usability report</h3> <p><a href="https://developers.google.com/search/mobile-sites/">Mobile Usability</a> is an important priority for all site owners. In order to help site owners with fixing mobile usability issues, we launched the Mobile Usability report on the new Search Console. Issue names are the same as in the old report but we now allow users to submit a validation and reindexing request when an issue is fixed, similar to other reports in the new Search Console. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjjTDY73T3OUo7Af1Mn9o0207VwXtzRgn09hdgpRs24B0myv3_jsX2hw1WTtK8mUn7aAoMTpSSK8fsmMm6Y8iXCTxkEWXU3XjQQY2rsvJWFjD4e4CNTp0KOYEkE_UbXnS8ljPNr/s1600/image02.png" imageanchor="1" ><img border="0" data-original-height="1262" data-original-width="1086" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjjTDY73T3OUo7Af1Mn9o0207VwXtzRgn09hdgpRs24B0myv3_jsX2hw1WTtK8mUn7aAoMTpSSK8fsmMm6Y8iXCTxkEWXU3XjQQY2rsvJWFjD4e4CNTp0KOYEkE_UbXnS8ljPNr/s400/image02.png" width="344" /></a> </p> <h3>Site and user management</h3> <p>To make the new Search Console feel more like home, we’ve added the ability to add and verify new sites, and manage your property's users and permissions, directly in new Search Console using our newly added <a href="https://support.google.com/webmasters/answer/7687465">settings</a> page. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjzcG-07EbfT8litkW2iV5syOSrPBkbN7hKytuycE-PnWzo9c9I4UF4S1TJEyatDYvS2-HMKvr2Lmx2U2q4DZIS_MLdzfiu2t4z14s4xawR4M9DhCHKRXeLrmfyr5mN7LMUbPX0/s1600/image03.png" imageanchor="1" ><img border="0" data-original-height="1274" data-original-width="1090" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjzcG-07EbfT8litkW2iV5syOSrPBkbN7hKytuycE-PnWzo9c9I4UF4S1TJEyatDYvS2-HMKvr2Lmx2U2q4DZIS_MLdzfiu2t4z14s4xawR4M9DhCHKRXeLrmfyr5mN7LMUbPX0/s400/image03.png" width="342" /></a> </p> <h3>Keep sending feedback</h3> <p>As always, we would love to get your feedback through the tools directly and our <a href="https://support.google.com/webmasters/go/community">help forums</a> so please share and let us know how we're doing.</p> <br> <span class="byline-author">Posted by Ariel Kroszynski and Roman Kecher - Search Console engineers</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Links, Mobile Usability, and site management in the new Search Console&url=https://webmasters.googleblog.com/2018/08/links-mobile-usability-and-site.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2018/08/links-mobile-usability-and-site.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2018/08/links-mobile-usability-and-site.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/mobile?hl=en_US' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US' rel='tag'> mobile-friendly </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='4979588601097027732' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/01/introducing-mobile-friendly-test-api.html?hl=en_US' itemprop='url' title='Introducing the Mobile-Friendly Test API'> Introducing the Mobile-Friendly Test API </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, January 31, 2017 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p>With so many users on mobile devices, having a mobile-friendly web is important to us all. The <a href="https://search.google.com/search-console/mobile-friendly">Mobile-Friendly Test</a> is a great way to check individual pages manually. We're happy to announce that this test is now available via API as well. </p> <p>The <a href="https://developers.google.com/webmaster-tools/search-console-api/">Mobile-Friendly Test API</a> lets you test URLs using automated tools. For example, you could use it to monitor important pages in your website in order to prevent accidental regressions in templates that you use. The <a href="https://developers.google.com/webmaster-tools/search-console-api/reference/rest/v1/urlTestingTools.mobileFriendlyTest/run">API method</a> runs all tests, and returns the same information - including a list of the blocked URLs - as the manual test. The documentation includes simple samples to help get you started quickly.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhU-VimIdGOxKuF7ZRJOcFXJq0ADWfpHxeeFyecQuwasQJx6FcDYQ4rAliNBAL-dRX2Kh9AuQ7HOdwYDA-BZij8wWKJ0xQWemVqJHWJ_NIcFyMayM-awRBdy4t6ejt8aBDS785e/s1600/key%253Dchicken.png" imageanchor="1" ><img border="0" height="226" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhU-VimIdGOxKuF7ZRJOcFXJq0ADWfpHxeeFyecQuwasQJx6FcDYQ4rAliNBAL-dRX2Kh9AuQ7HOdwYDA-BZij8wWKJ0xQWemVqJHWJ_NIcFyMayM-awRBdy4t6ejt8aBDS785e/s400/key%253Dchicken.png" width="400" /></a> <p>We hope this API makes it easier to check your pages for mobile-friendliness and to get any such issues resolved faster. We'd love to hear how you use the API -- leave us a comment here, and feel free to link to any code or implementation that you've set up! As always, if you have any questions, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">webmaster help forum</a>.</p> <br> <span class="byline-author">Posted by <a href="https://google.com/+johnmueller" rel="the author of this post">John Mueller</a>, Webmaster Trends Analyst, Google Switzerland</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p>With so many users on mobile devices, having a mobile-friendly web is important to us all. The <a href="https://search.google.com/search-console/mobile-friendly">Mobile-Friendly Test</a> is a great way to check individual pages manually. We're happy to announce that this test is now available via API as well. </p> <p>The <a href="https://developers.google.com/webmaster-tools/search-console-api/">Mobile-Friendly Test API</a> lets you test URLs using automated tools. For example, you could use it to monitor important pages in your website in order to prevent accidental regressions in templates that you use. The <a href="https://developers.google.com/webmaster-tools/search-console-api/reference/rest/v1/urlTestingTools.mobileFriendlyTest/run">API method</a> runs all tests, and returns the same information - including a list of the blocked URLs - as the manual test. The documentation includes simple samples to help get you started quickly.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhU-VimIdGOxKuF7ZRJOcFXJq0ADWfpHxeeFyecQuwasQJx6FcDYQ4rAliNBAL-dRX2Kh9AuQ7HOdwYDA-BZij8wWKJ0xQWemVqJHWJ_NIcFyMayM-awRBdy4t6ejt8aBDS785e/s1600/key%253Dchicken.png" imageanchor="1" ><img border="0" height="226" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhU-VimIdGOxKuF7ZRJOcFXJq0ADWfpHxeeFyecQuwasQJx6FcDYQ4rAliNBAL-dRX2Kh9AuQ7HOdwYDA-BZij8wWKJ0xQWemVqJHWJ_NIcFyMayM-awRBdy4t6ejt8aBDS785e/s400/key%253Dchicken.png" width="400" /></a> <p>We hope this API makes it easier to check your pages for mobile-friendliness and to get any such issues resolved faster. We'd love to hear how you use the API -- leave us a comment here, and feel free to link to any code or implementation that you've set up! As always, if you have any questions, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">webmaster help forum</a>.</p> <br> <span class="byline-author">Posted by <a href="https://google.com/+johnmueller" rel="the author of this post">John Mueller</a>, Webmaster Trends Analyst, Google Switzerland</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Introducing the Mobile-Friendly Test API&url=https://webmasters.googleblog.com/2017/01/introducing-mobile-friendly-test-api.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/01/introducing-mobile-friendly-test-api.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/01/introducing-mobile-friendly-test-api.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/API?hl=en_US' rel='tag'> API </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile?hl=en_US' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US' rel='tag'> mobile-friendly </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> </span> </div> </div> </div> <div class='post' data-id='156979147313381852' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/11/building-indexable-progressive-web-apps.html?hl=en_US' itemprop='url' title='Building Indexable Progressive Web Apps'> Building Indexable Progressive Web Apps </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, November 09, 2016 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p><a href="https://developers.google.com/web/progressive-web-apps/">Progressive Web Apps</a> (PWAs) are taking advantage of new technologies to bring the best of mobile sites and native applications to users -- and they’re one of the most exciting new ideas on the web. But to truly have an impact, it's important that they’re indexable and linkable. Every recommendation presented in this article is an existing best practice for indexability -- regardless of whether you're building a Progressive Web App or a simple static website. Nonetheless, we have collated these best practices to provide a checklist to guide you:</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgVgVKTQB5hnuptyyfnJ8YRWMJk_CXL0Vn86oYlbVeLDI1tE68GM71kiK6izDCUdzwLhP-q301t-IhnZNrjrDGqvnhpxPon62wyCZXM2Gj00kN6sy8qP9uLk7raNh9CQrHcssG1/s1600/pwa_roadshow_summit.JPG" imageanchor="1" ><img border="0" height="300" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgVgVKTQB5hnuptyyfnJ8YRWMJk_CXL0Vn86oYlbVeLDI1tE68GM71kiK6izDCUdzwLhP-q301t-IhnZNrjrDGqvnhpxPon62wyCZXM2Gj00kN6sy8qP9uLk7raNh9CQrHcssG1/s400/pwa_roadshow_summit.JPG" width="400" /></a> <h3>Make Your Content Crawlable</h3> <p><b>Why?</b> Historically, websites would always generate or render their HTML on the server which is the simplest way to ensure your content is directly linkable. Web applications popularised the concept of client-side rendering in which content is updated dynamically on the page as the users navigates without requiring the page to be reloaded.</p> <p>The modern approach is hybrid rendering, in which server-side rendering is used when a user navigates directly to a URL and client-side rendering is used after the initial page load for subsequent navigation and asynchronous requests.</p> <p>Our <a href="https://server-dot-indexable-pwa.appspot.com">server-side PWA sample</a> demonstrates pure server-side rendering, while our <a href="https://hybrid-dot-indexable-pwa.appspot.com">hybrid PWA sample</a> demonstrates the combined approach.</p> <p>If you are unfamiliar with the <b>server-side</b> and <b>client-side</b> rendering terminology, check out these articles on the web read <a href="http://openmymind.net/2012/5/30/Client-Side-vs-Server-Side-Rendering/">here</a> and <a href="https://www.smashingmagazine.com/2016/03/server-side-rendering-react-node-express/">here.</a></p> <style> .boxbox { width: 100%; word-wrap:break-word; padding: 0.2em; } .badbox { background-color: #eba; } .goodbox { background-color: #ded; } .avoidbox { background-color: #ffd; } .boxbox h5 { font-size: 1em; font-weight: bold; margin: 0;} .boxbox p { margin-top: 0.6em; margin-bottom: 0.6em; } br.endboxen { clear: both; } h3.subhead { margin-top: 2em; } </style>   <div class="boxbox goodbox"> <h5 class="subhead">Best Practice:</h5> <p>Use server-side or hybrid rendering so users receive the content in the initial payload of their web request.</p> <p>Always ensure your URLs are independently accessible:</p> <p>https://www.example.com/product/25/</p> <p>The above should deep link to that particular resource.</p> <p>If you can’t support server-side or hybrid rendering for your Progressive Web App and you decide to use client-side rendering, we recommend using the Google Search Console “Fetch as Google tool” to verify your content successfully renders for our search crawler.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>Don't redirect users accessing deep links back to your web app's homepage.</p> <p>Additionally, serving an error page to users instead of deep linking should also be avoided.</p> </div> <br class="endboxen" /> <h3 class="subhead">Provide Clean URLs</h3> <p><b>Why?</b> Fragment identifiers (#user/24601/ or #!user/24601/) were an effective workaround for browsers to AJAX new content from a server without reloading the page. This design is known as client-side rendering.</p> <p>However, the fragment identifier syntax isn’t compatible with some web tools, frameworks and protocols such as <a href="http://ogp.me/">Facebook’s Open Graph protocol</a>.</p> <p>The <a href="https://developer.mozilla.org/en-US/docs/Web/API/History_API">History API</a> enables us to update the URL without fragment identifiers while still fetching resources asynchronously and therefore avoiding page reloads -- it’s the best of both worlds. The AJAX crawling scheme (with its #! / escaped-fragment URLs) made sense at its time, but is now no longer recommended. </p> <p>Our <a href="https://hybrid-dot-indexable-pwa.appspot.com">hybrid PWA</a> and <a href="https://client-dot-indexable-pwa.appspot.com">client-side PWA samples</a> demonstrate the History API.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Provide clean URLs without fragment identifiers (# or #!) such as:</p> <p>https://www.example.com/product/25/</p> <p>If using client-side or hybrid rendering be sure to support browser navigation with the History API.</p> </div> <div class="boxbox avoidbox"> <h5>Avoid:</h5> <p>Using the #! URL structure to drive unique URLs is discouraged:</p> <p>https://www.example.com/#!product/25/</p> <p>It was introduced as a workaround before the advent of the History API. It is considered a separate pattern to the purely # URL structure.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>Using the # URL structure without the accompanying ! symbol is unsupported:</p> <p>https://www.example.com/#product/25/</p> <p>This URL structure is already a concept in the web and relates to deep linking into content on a particular page.</p> </div> <br class="endboxen" /> <h3 class="subhead">Specify Canonical URLs</h3> <p><b>Why?</b> The best way to eliminate confusion for indexing when the same content is available under multiple URLs (be it the same or different domains) is to mark one page as the canonical, and all other pages that duplicate that content to refer to it.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Include the following tag across all pages mirroring a particular piece of content:</p> <p><pre><link rel="canonical" href="https://www.example.com/your-url/" /></pre></p> <p>If you are supporting Accelerated Mobile Pages be sure to correctly use its counterpart rel=”amphtml” instruction as well.</p> </div> <div class="boxbox avoidbox"> <h5>Avoid:</h5> <p>Avoid purposely duplicating content across multiple URLs and not using the rel="canonical" link element.</p> <p>For example, the rel="canonical" link element can reduce ambiguity for URLs with tracking parameters.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>Avoid creating conflicting canonical references between your pages.</p> </div> <br class="endboxen" /> <h3 class="subhead">Design for Multiple Devices</h3> <p><b>Why?</b> It’s important that all your users get the best experience possible when viewing your website, regardless of their device. </p> <p>Make your site <a href="https://developers.google.com/web/fundamentals/design-and-ui/responsive/fundamentals/?hl=en">responsive in its design</a> -- fonts, margins, paddings, buttons and general design of your site should scale dynamically based on screen resolutions and device viewports. </p> <p>Small images scaled up for desktop or tablet devices give a poor experience. Conversely, super high resolution images take a long time to download on mobile phones and may impact mobile scroll performance.</p> <p>Read more <a href="https://medium.com/@owencm/designing-great-uis-for-progressive-web-apps-dd38c1d20f7#.c0avg96qb">UX for PWAs here</a>.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Use <a href="https://developers.google.com/web/fundamentals/design-and-ui/media/images/images-in-markup?hl=en">“srcset” attribute</a> to fetch different resolution images for different density screens to avoid downloading images larger than the device’s screen is capable of displaying.</p> <p>Scale your font size and line height to ensure your text is legible no matter the size of the device. Similarly ensure the padding and margins of elements also scale sensibly.</p> <p>Test <a href="https://developers.google.com/web/tools/chrome-devtools/iterate/device-mode/emulate-mobile-viewports?hl=en">various screen resolutions</a> using the <a href="https://developers.google.com/web/tools/chrome-devtools/iterate/device-mode/?hl=en">Chrome Developer Tool’s Device Mode</a> feature and <a href="https://search.google.com/search-console/mobile-friendly">Mobile Friendly Test tool</a>.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>Don't show different content to users than you show to Google. If you use <a href="https://support.google.com/webmasters/answer/2604723?hl=en">redirects or user agent detection</a> (a.k.a. browser sniffing or <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/dynamic-serving?hl=en">dynamic serving</a>) to alter the design of your site for different devices it’s important that the content itself remains the same.</p> <p>Use the Search Console “Fetch as Google” tool to verify the content fetched by Google matches the content a user sees.</p> <p>For usability reasons, avoid using fixed-size fonts.</p> </div> <br style="clear: both" /> <h3 class="subhead">Develop Iteratively</h3> <p><b>Why?</b> One of the safest paths to take when adding features to a web application is to make changes iteratively. If you add features one at a time you can observe the impact of each individual change.</p> <p>Alternatively many developers prefer to view their progressive web application as an opportunity to overhaul their mobile site in one fell swoop -- developing the new web app in an isolated environment and swapping it with their existing mobile site once ready.</p> <p>When developing features iteratively try to break the changes into separate pieces. For example, if you intend to move from server-side rendering to hybrid rendering then tackle that as a single iteration -- rather than in combination with other features.</p> <p>Both approaches have their own pros and cons. Iterating reduces the complexity of dealing with search indexability as the transition is continuous. However, iterating might result in a slower development process and potentially a less innovative overhaul if development is not starting from scratch.</p> <p>In either case, the most sensitive areas to keep an eye on are your canonical URLs and your site’s robots.txt configuration.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Iterate on your website incrementally by adding new features piece by piece.</p> <p>For example, if don’t support HTTPS yet then start by migrating to a secure site.</p> </div> <div class="boxbox avoidbox"> <h5>Avoid:</h5> <p>If you’ve developed your progressive web app in an isolated environment, then avoid launching it without checking the rel-canonical links and robots.txt are setup appropriately.</p> <p>Ensure your rel-canonical links point to the real site and that your robots.txt configuration allows crawlers to crawl your new site.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>It’s logical to prevent crawlers from indexing your in-development site before launch but don’t forget to unblock crawlers from accessing your new site when you launch.</p> </div> <br class="endboxen" /> <h3 class="subhead">Use Progressive Enhancement</h3> <p><b>Why?</b> Wherever possible it’s important to detect browser features before using them. Feature detection is also better than testing for browsers that you believe support a given feature.</p> <p>A common bad practice in the past was to enable or disable features by testing which browser the user had. However, as browsers are constantly evolving with features this technique is strongly discouraged.</p> <p>Service Worker is a relatively new technology and it’s important to not break compatibility in the pursuit of progress -- it's a perfect example of when to use progressive enhancement.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Before registering a Service Worker check for the availability of its API:</p> <p><pre>if ('serviceWorker' in navigator) { ... </pre> <p>Use per API detection method for all your website’s features.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>Never use the browser’s user agent to enable or disable features in your web app. Always check whether the feature’s API is available and gracefully degrade if unavailable.</p> <p>Avoid updating or launching your site without testing across multiple browsers! Check your site analytics to learn which browsers are most popular among your user base.</p> </div> <br class="endboxen" /> <h3 class="subhead">Test with Search Console</h3> <p><b>Why?</b> It’s important to understand how Google Search views your site’s content. You can use <a href="https://www.google.com/webmasters/tools/home?hl=en">Search Console</a> to <a href="https://support.google.com/webmasters/answer/6066468?hl=en">fetch individual URLs from your site</a> and see how Google Search views them using the “Crawl > Fetch as Google“ feature. Search Console will process your JavaScript and render the page when that option is selected; otherwise only the raw HTML response is shown </p> <p>Google Search Console also analyses the content on your page in a variety of ways including detecting the presence of Structured Data, Rich Cards, Sitelinks & Accelerated Mobile Pages.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Monitor your site using Search Console and explore its features including “Fetch as Google”.</p> <p>Provide a Sitemap via Search Console “Crawl > Sitemaps” It can be an effective way to ensure Google Search is aware of all your site’s pages.</p> </div> <br class="endboxen" /> <h3 class="subhead">Annotate with Schema.org structured data</h3> <p><b>Why?</b> <a href="https://schema.org/">Schema.org</a> structured data is a flexible vocabulary for summarizing the most important parts of your page as machine-processable data. This can be as general as simply saying that a page is a NewsArticle, or as specific as detailing the location, band name, venue and ticket vendor for a touring band, or summarizing the ingredients and steps for a recipe.</p> <p>The use of this metadata may not make sense for every page on your web application but it’s recommended where it’s sensible. Google extracts it after the page is rendered.</p> <p>There are a variety of data types including “NewsArticle”, “Recipe” & “Product” to name a few. Explore all the <a href="https://developers.google.com/search/docs/data-types/data-type-selector">supported data types here</a>.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Verify that your Schema.org meta data is correct using Google’s <a href="https://search.google.com/structured-data/testing-tool/">Structured Data Testing Tool</a>.</p> <p>Check that the data you provided is appearing and there are no errors present.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>Avoid using a data type that doesn’t match your page’s actual content. For example don’t use “Recipe” for a T-Shirt you’re selling -- use “Product” instead.</p> </div> <br class="endboxen" /> <h3 class="subhead">Annotate with Open Graph & Twitter Cards</h3> <p><b>Why?</b> In addition to the Schema.org metadata it can be helpful to add support for Facebook’s Open Graph protocol and Twitter rich cards as well.</p> <p>These metadata formats improve the user experience when your content is shared on their corresponding social networks.</p> <p>If your existing site or web application utilises these formats it’s important to ensure they are included in your progressive web application as well for optimal virality.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Test your Open Graph markup with the <a href="https://developers.facebook.com/tools/debug/">Facebook Object Debugger Tool</a>.</p> <p>Familiarise yourself with <a href="https://dev.twitter.com/cards/overview">Twitter’s metadata format</a>.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>Don’t forget to include these formats if your existing site supports them.</p> </div> <br class="endboxen" /> <h3 class="subhead">Test with Multiple Browsers</h3> <p><b>Why?</b> Clearly from a user perspective it’s important that a website behaviors the same across all browsers. While the experience might adapt for different screen sizes we all expect a mobile site to work the same on similarly sized devices whether it’s an iPhone or an Android mobile phone.</p> <p>While the web can be perceived as fragmented due to number of browsers in use around the world, this variety and competition is part of what makes the web such an innovative platform. Thankfully, web standards have never been more mature than they are now and modern tools enable developers to build rich, cross browser compatible websites with confidence.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Use cross browser testing tools such as <a href="https://www.browserstack.com/">BrowserStack.com</a>, <a href="https://www.browserling.com/">Browserling.com</a> or <a href="http://browsershots.org/">BrowserShots.org</a> to ensure your PWA is cross browser compatible.</p> </div> <br class="endboxen" /> <h3 class="subhead">Measure Page Load Performance</h3> <p><b>Why?</b> The faster a website loads for a user the better their user experience will be. Optimizing for page speed is already a well known focus in web development but sometimes when developing a new version of a site the necessary optimizations are not considered a high priority.</p> <p>When developing a progressive web application we recommend measuring the performance of your page load speed and optimizing before launching the site for the best results. </p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Use tools such as <a href="https://developers.google.com/speed/pagespeed/insights/">Page Speed Insights</a> and <a href="http://webpagetest.org">Web Page Test</a> to measure the page load performance of your site. While Googlebot has a bit more patience in rendering, <a href="https://www.thinkwithgoogle.com/articles/mobile-page-speed-load-time.html">research has shown</a> that 40% of consumers will leave a page that takes longer than three seconds to load..</p> <p>Read more about our web page performance recommendations and the <a href="https://developers.google.com/web/fundamentals/performance/critical-rendering-path/">critical rendering path here</a>.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>Avoid leaving optimization as a post-launch step. If your website’s content loads quickly before migrating to a new progressive web application then it’s important to not regress in your optimizations.</p> </div> <br class="endboxen" /> <p>We hope that the above checklist is useful and provides the right guidance to help you develop your Progressive Web Applications with indexability in mind. </p> <p>As you get started, be sure to check out our <a href="https://github.com/google/indexable-pwa-samples">Progressive Web App indexability samples</a> that demonstrate <a href="https://server-dot-indexable-pwa.appspot.com">server-side</a>, <a href="https://client-dot-indexable-pwa.appspot.com">client-side</a> and <a href="https://hybrid-dot-indexable-pwa.appspot.com">hybrid</a> rendering. As always, if you have any questions, please reach out on our <a href="https://support.google.com/webmasters/go/community">Webmaster Forums</a>. </p> <br> <span class="byline-author">Posted by Tom Greenaway, Developer Advocate</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p><a href="https://developers.google.com/web/progressive-web-apps/">Progressive Web Apps</a> (PWAs) are taking advantage of new technologies to bring the best of mobile sites and native applications to users -- and they’re one of the most exciting new ideas on the web. But to truly have an impact, it's important that they’re indexable and linkable. Every recommendation presented in this article is an existing best practice for indexability -- regardless of whether you're building a Progressive Web App or a simple static website. Nonetheless, we have collated these best practices to provide a checklist to guide you:</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgVgVKTQB5hnuptyyfnJ8YRWMJk_CXL0Vn86oYlbVeLDI1tE68GM71kiK6izDCUdzwLhP-q301t-IhnZNrjrDGqvnhpxPon62wyCZXM2Gj00kN6sy8qP9uLk7raNh9CQrHcssG1/s1600/pwa_roadshow_summit.JPG" imageanchor="1" ><img border="0" height="300" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgVgVKTQB5hnuptyyfnJ8YRWMJk_CXL0Vn86oYlbVeLDI1tE68GM71kiK6izDCUdzwLhP-q301t-IhnZNrjrDGqvnhpxPon62wyCZXM2Gj00kN6sy8qP9uLk7raNh9CQrHcssG1/s400/pwa_roadshow_summit.JPG" width="400" /></a> <h3>Make Your Content Crawlable</h3> <p><b>Why?</b> Historically, websites would always generate or render their HTML on the server which is the simplest way to ensure your content is directly linkable. Web applications popularised the concept of client-side rendering in which content is updated dynamically on the page as the users navigates without requiring the page to be reloaded.</p> <p>The modern approach is hybrid rendering, in which server-side rendering is used when a user navigates directly to a URL and client-side rendering is used after the initial page load for subsequent navigation and asynchronous requests.</p> <p>Our <a href="https://server-dot-indexable-pwa.appspot.com">server-side PWA sample</a> demonstrates pure server-side rendering, while our <a href="https://hybrid-dot-indexable-pwa.appspot.com">hybrid PWA sample</a> demonstrates the combined approach.</p> <p>If you are unfamiliar with the <b>server-side</b> and <b>client-side</b> rendering terminology, check out these articles on the web read <a href="http://openmymind.net/2012/5/30/Client-Side-vs-Server-Side-Rendering/">here</a> and <a href="https://www.smashingmagazine.com/2016/03/server-side-rendering-react-node-express/">here.</a></p> <style> .boxbox { width: 100%; word-wrap:break-word; padding: 0.2em; } .badbox { background-color: #eba; } .goodbox { background-color: #ded; } .avoidbox { background-color: #ffd; } .boxbox h5 { font-size: 1em; font-weight: bold; margin: 0;} .boxbox p { margin-top: 0.6em; margin-bottom: 0.6em; } br.endboxen { clear: both; } h3.subhead { margin-top: 2em; } </style>   <div class="boxbox goodbox"> <h5 class="subhead">Best Practice:</h5> <p>Use server-side or hybrid rendering so users receive the content in the initial payload of their web request.</p> <p>Always ensure your URLs are independently accessible:</p> <p>https://www.example.com/product/25/</p> <p>The above should deep link to that particular resource.</p> <p>If you can’t support server-side or hybrid rendering for your Progressive Web App and you decide to use client-side rendering, we recommend using the Google Search Console “Fetch as Google tool” to verify your content successfully renders for our search crawler.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>Don't redirect users accessing deep links back to your web app's homepage.</p> <p>Additionally, serving an error page to users instead of deep linking should also be avoided.</p> </div> <br class="endboxen" /> <h3 class="subhead">Provide Clean URLs</h3> <p><b>Why?</b> Fragment identifiers (#user/24601/ or #!user/24601/) were an effective workaround for browsers to AJAX new content from a server without reloading the page. This design is known as client-side rendering.</p> <p>However, the fragment identifier syntax isn’t compatible with some web tools, frameworks and protocols such as <a href="http://ogp.me/">Facebook’s Open Graph protocol</a>.</p> <p>The <a href="https://developer.mozilla.org/en-US/docs/Web/API/History_API">History API</a> enables us to update the URL without fragment identifiers while still fetching resources asynchronously and therefore avoiding page reloads -- it’s the best of both worlds. The AJAX crawling scheme (with its #! / escaped-fragment URLs) made sense at its time, but is now no longer recommended. </p> <p>Our <a href="https://hybrid-dot-indexable-pwa.appspot.com">hybrid PWA</a> and <a href="https://client-dot-indexable-pwa.appspot.com">client-side PWA samples</a> demonstrate the History API.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Provide clean URLs without fragment identifiers (# or #!) such as:</p> <p>https://www.example.com/product/25/</p> <p>If using client-side or hybrid rendering be sure to support browser navigation with the History API.</p> </div> <div class="boxbox avoidbox"> <h5>Avoid:</h5> <p>Using the #! URL structure to drive unique URLs is discouraged:</p> <p>https://www.example.com/#!product/25/</p> <p>It was introduced as a workaround before the advent of the History API. It is considered a separate pattern to the purely # URL structure.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>Using the # URL structure without the accompanying ! symbol is unsupported:</p> <p>https://www.example.com/#product/25/</p> <p>This URL structure is already a concept in the web and relates to deep linking into content on a particular page.</p> </div> <br class="endboxen" /> <h3 class="subhead">Specify Canonical URLs</h3> <p><b>Why?</b> The best way to eliminate confusion for indexing when the same content is available under multiple URLs (be it the same or different domains) is to mark one page as the canonical, and all other pages that duplicate that content to refer to it.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Include the following tag across all pages mirroring a particular piece of content:</p> <p><pre><link rel="canonical" href="https://www.example.com/your-url/" /></pre></p> <p>If you are supporting Accelerated Mobile Pages be sure to correctly use its counterpart rel=”amphtml” instruction as well.</p> </div> <div class="boxbox avoidbox"> <h5>Avoid:</h5> <p>Avoid purposely duplicating content across multiple URLs and not using the rel="canonical" link element.</p> <p>For example, the rel="canonical" link element can reduce ambiguity for URLs with tracking parameters.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>Avoid creating conflicting canonical references between your pages.</p> </div> <br class="endboxen" /> <h3 class="subhead">Design for Multiple Devices</h3> <p><b>Why?</b> It’s important that all your users get the best experience possible when viewing your website, regardless of their device. </p> <p>Make your site <a href="https://developers.google.com/web/fundamentals/design-and-ui/responsive/fundamentals/?hl=en">responsive in its design</a> -- fonts, margins, paddings, buttons and general design of your site should scale dynamically based on screen resolutions and device viewports. </p> <p>Small images scaled up for desktop or tablet devices give a poor experience. Conversely, super high resolution images take a long time to download on mobile phones and may impact mobile scroll performance.</p> <p>Read more <a href="https://medium.com/@owencm/designing-great-uis-for-progressive-web-apps-dd38c1d20f7#.c0avg96qb">UX for PWAs here</a>.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Use <a href="https://developers.google.com/web/fundamentals/design-and-ui/media/images/images-in-markup?hl=en">“srcset” attribute</a> to fetch different resolution images for different density screens to avoid downloading images larger than the device’s screen is capable of displaying.</p> <p>Scale your font size and line height to ensure your text is legible no matter the size of the device. Similarly ensure the padding and margins of elements also scale sensibly.</p> <p>Test <a href="https://developers.google.com/web/tools/chrome-devtools/iterate/device-mode/emulate-mobile-viewports?hl=en">various screen resolutions</a> using the <a href="https://developers.google.com/web/tools/chrome-devtools/iterate/device-mode/?hl=en">Chrome Developer Tool’s Device Mode</a> feature and <a href="https://search.google.com/search-console/mobile-friendly">Mobile Friendly Test tool</a>.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>Don't show different content to users than you show to Google. If you use <a href="https://support.google.com/webmasters/answer/2604723?hl=en">redirects or user agent detection</a> (a.k.a. browser sniffing or <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/dynamic-serving?hl=en">dynamic serving</a>) to alter the design of your site for different devices it’s important that the content itself remains the same.</p> <p>Use the Search Console “Fetch as Google” tool to verify the content fetched by Google matches the content a user sees.</p> <p>For usability reasons, avoid using fixed-size fonts.</p> </div> <br style="clear: both" /> <h3 class="subhead">Develop Iteratively</h3> <p><b>Why?</b> One of the safest paths to take when adding features to a web application is to make changes iteratively. If you add features one at a time you can observe the impact of each individual change.</p> <p>Alternatively many developers prefer to view their progressive web application as an opportunity to overhaul their mobile site in one fell swoop -- developing the new web app in an isolated environment and swapping it with their existing mobile site once ready.</p> <p>When developing features iteratively try to break the changes into separate pieces. For example, if you intend to move from server-side rendering to hybrid rendering then tackle that as a single iteration -- rather than in combination with other features.</p> <p>Both approaches have their own pros and cons. Iterating reduces the complexity of dealing with search indexability as the transition is continuous. However, iterating might result in a slower development process and potentially a less innovative overhaul if development is not starting from scratch.</p> <p>In either case, the most sensitive areas to keep an eye on are your canonical URLs and your site’s robots.txt configuration.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Iterate on your website incrementally by adding new features piece by piece.</p> <p>For example, if don’t support HTTPS yet then start by migrating to a secure site.</p> </div> <div class="boxbox avoidbox"> <h5>Avoid:</h5> <p>If you’ve developed your progressive web app in an isolated environment, then avoid launching it without checking the rel-canonical links and robots.txt are setup appropriately.</p> <p>Ensure your rel-canonical links point to the real site and that your robots.txt configuration allows crawlers to crawl your new site.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>It’s logical to prevent crawlers from indexing your in-development site before launch but don’t forget to unblock crawlers from accessing your new site when you launch.</p> </div> <br class="endboxen" /> <h3 class="subhead">Use Progressive Enhancement</h3> <p><b>Why?</b> Wherever possible it’s important to detect browser features before using them. Feature detection is also better than testing for browsers that you believe support a given feature.</p> <p>A common bad practice in the past was to enable or disable features by testing which browser the user had. However, as browsers are constantly evolving with features this technique is strongly discouraged.</p> <p>Service Worker is a relatively new technology and it’s important to not break compatibility in the pursuit of progress -- it's a perfect example of when to use progressive enhancement.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Before registering a Service Worker check for the availability of its API:</p> <p><pre>if ('serviceWorker' in navigator) { ... </pre> <p>Use per API detection method for all your website’s features.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>Never use the browser’s user agent to enable or disable features in your web app. Always check whether the feature’s API is available and gracefully degrade if unavailable.</p> <p>Avoid updating or launching your site without testing across multiple browsers! Check your site analytics to learn which browsers are most popular among your user base.</p> </div> <br class="endboxen" /> <h3 class="subhead">Test with Search Console</h3> <p><b>Why?</b> It’s important to understand how Google Search views your site’s content. You can use <a href="https://www.google.com/webmasters/tools/home?hl=en">Search Console</a> to <a href="https://support.google.com/webmasters/answer/6066468?hl=en">fetch individual URLs from your site</a> and see how Google Search views them using the “Crawl > Fetch as Google“ feature. Search Console will process your JavaScript and render the page when that option is selected; otherwise only the raw HTML response is shown </p> <p>Google Search Console also analyses the content on your page in a variety of ways including detecting the presence of Structured Data, Rich Cards, Sitelinks & Accelerated Mobile Pages.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Monitor your site using Search Console and explore its features including “Fetch as Google”.</p> <p>Provide a Sitemap via Search Console “Crawl > Sitemaps” It can be an effective way to ensure Google Search is aware of all your site’s pages.</p> </div> <br class="endboxen" /> <h3 class="subhead">Annotate with Schema.org structured data</h3> <p><b>Why?</b> <a href="https://schema.org/">Schema.org</a> structured data is a flexible vocabulary for summarizing the most important parts of your page as machine-processable data. This can be as general as simply saying that a page is a NewsArticle, or as specific as detailing the location, band name, venue and ticket vendor for a touring band, or summarizing the ingredients and steps for a recipe.</p> <p>The use of this metadata may not make sense for every page on your web application but it’s recommended where it’s sensible. Google extracts it after the page is rendered.</p> <p>There are a variety of data types including “NewsArticle”, “Recipe” & “Product” to name a few. Explore all the <a href="https://developers.google.com/search/docs/data-types/data-type-selector">supported data types here</a>.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Verify that your Schema.org meta data is correct using Google’s <a href="https://search.google.com/structured-data/testing-tool/">Structured Data Testing Tool</a>.</p> <p>Check that the data you provided is appearing and there are no errors present.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>Avoid using a data type that doesn’t match your page’s actual content. For example don’t use “Recipe” for a T-Shirt you’re selling -- use “Product” instead.</p> </div> <br class="endboxen" /> <h3 class="subhead">Annotate with Open Graph & Twitter Cards</h3> <p><b>Why?</b> In addition to the Schema.org metadata it can be helpful to add support for Facebook’s Open Graph protocol and Twitter rich cards as well.</p> <p>These metadata formats improve the user experience when your content is shared on their corresponding social networks.</p> <p>If your existing site or web application utilises these formats it’s important to ensure they are included in your progressive web application as well for optimal virality.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Test your Open Graph markup with the <a href="https://developers.facebook.com/tools/debug/">Facebook Object Debugger Tool</a>.</p> <p>Familiarise yourself with <a href="https://dev.twitter.com/cards/overview">Twitter’s metadata format</a>.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>Don’t forget to include these formats if your existing site supports them.</p> </div> <br class="endboxen" /> <h3 class="subhead">Test with Multiple Browsers</h3> <p><b>Why?</b> Clearly from a user perspective it’s important that a website behaviors the same across all browsers. While the experience might adapt for different screen sizes we all expect a mobile site to work the same on similarly sized devices whether it’s an iPhone or an Android mobile phone.</p> <p>While the web can be perceived as fragmented due to number of browsers in use around the world, this variety and competition is part of what makes the web such an innovative platform. Thankfully, web standards have never been more mature than they are now and modern tools enable developers to build rich, cross browser compatible websites with confidence.</p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Use cross browser testing tools such as <a href="https://www.browserstack.com/">BrowserStack.com</a>, <a href="https://www.browserling.com/">Browserling.com</a> or <a href="http://browsershots.org/">BrowserShots.org</a> to ensure your PWA is cross browser compatible.</p> </div> <br class="endboxen" /> <h3 class="subhead">Measure Page Load Performance</h3> <p><b>Why?</b> The faster a website loads for a user the better their user experience will be. Optimizing for page speed is already a well known focus in web development but sometimes when developing a new version of a site the necessary optimizations are not considered a high priority.</p> <p>When developing a progressive web application we recommend measuring the performance of your page load speed and optimizing before launching the site for the best results. </p> <div class="boxbox goodbox"> <h5>Best Practice:</h5> <p>Use tools such as <a href="https://developers.google.com/speed/pagespeed/insights/">Page Speed Insights</a> and <a href="http://webpagetest.org">Web Page Test</a> to measure the page load performance of your site. While Googlebot has a bit more patience in rendering, <a href="https://www.thinkwithgoogle.com/articles/mobile-page-speed-load-time.html">research has shown</a> that 40% of consumers will leave a page that takes longer than three seconds to load..</p> <p>Read more about our web page performance recommendations and the <a href="https://developers.google.com/web/fundamentals/performance/critical-rendering-path/">critical rendering path here</a>.</p> </div> <div class="boxbox badbox"> <h5>Don’t:</h5> <p>Avoid leaving optimization as a post-launch step. If your website’s content loads quickly before migrating to a new progressive web application then it’s important to not regress in your optimizations.</p> </div> <br class="endboxen" /> <p>We hope that the above checklist is useful and provides the right guidance to help you develop your Progressive Web Applications with indexability in mind. </p> <p>As you get started, be sure to check out our <a href="https://github.com/google/indexable-pwa-samples">Progressive Web App indexability samples</a> that demonstrate <a href="https://server-dot-indexable-pwa.appspot.com">server-side</a>, <a href="https://client-dot-indexable-pwa.appspot.com">client-side</a> and <a href="https://hybrid-dot-indexable-pwa.appspot.com">hybrid</a> rendering. As always, if you have any questions, please reach out on our <a href="https://support.google.com/webmasters/go/community">Webmaster Forums</a>. </p> <br> <span class="byline-author">Posted by Tom Greenaway, Developer Advocate</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Building Indexable Progressive Web Apps&url=https://webmasters.googleblog.com/2016/11/building-indexable-progressive-web-apps.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2016/11/building-indexable-progressive-web-apps.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2016/11/building-indexable-progressive-web-apps.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/advanced?hl=en_US' rel='tag'> advanced </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/general%20tips?hl=en_US' rel='tag'> general tips </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US' rel='tag'> mobile-friendly </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/performance?hl=en_US' rel='tag'> performance </a> </span> </div> </div> </div> <div class='post' data-id='8066851462433051833' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/11/mobile-first-indexing.html?hl=en_US' itemprop='url' title='Mobile-first Indexing'> Mobile-first Indexing </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Friday, November 04, 2016 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>Today, most people are searching on Google using a mobile device. However, our ranking systems still typically look at the desktop version of a page’s content to evaluate its relevance to the user. This can cause issues when the mobile page has less content than the desktop page because our algorithms are not evaluating the actual page that is seen by a mobile searcher.</p> <p>To make our results more useful, we’ve begun experiments to make our index mobile-first. Although our search index will continue to be a single index of websites and apps, our algorithms will eventually primarily use the mobile version of a site’s content to rank pages from that site, to understand structured data, and to show snippets from those pages in our results. Of course, while our index will be built from mobile documents, we're going to continue to build a great search experience for all users, whether they come from mobile or desktop devices.</p> <p>We understand this is an important shift in our indexing and it’s one we take seriously. We’ll continue to carefully experiment over the coming months on a small scale and we’ll ramp up this change when we’re confident that we have a great user experience. Though we’re only beginning this process, here are a few recommendations to help webmasters prepare as we move towards a more mobile-focused index.</p> <ul style="padding:0 1em"><li>If you have a <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/responsive-design">responsive site</a> or a <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/dynamic-serving">dynamic serving site</a> where the primary content and markup is equivalent across mobile and desktop, you shouldn’t have to change anything.</li> <li>If you have a <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/">site configuration</a> where the primary content and markup is different across mobile and desktop, you should consider making some changes to your site.</li> <ul style="padding:0 1em"><li>Make sure to serve structured markup for both the desktop and mobile version.<br><br> Sites can verify the equivalence of their structured markup across desktop and mobile by typing the URLs of both versions into the <a href="https://search.google.com/structured-data/testing-tool">Structured Data Testing Tool</a> and comparing the output. <br><br> When adding structured data to a mobile site, avoid adding large amounts of markup that isn’t relevant to the specific information content of each document.</li> <li>Use the <a href="https://support.google.com/webmasters/answer/6062598">robots.txt testing tool</a> to verify that your mobile version is accessible to Googlebot. </li> <li>Sites do not have to make changes to their <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/separate-urls">canonical links</a>; we’ll continue to use these links as guides to serve the appropriate results to a user searching on desktop or mobile.</li></ul> <li>If you are a site owner who has only verified their desktop site in Search Console, <a href="https://support.google.com/webmasters/answer/35179">please add and verify your mobile version</a>.</li> <li>If you only have a desktop site, we'll continue to index your desktop site just fine, even if we're using a mobile user agent to view your site.<br><br> If you are building a mobile version of your site, keep in mind that a functional desktop-oriented site can be better than a broken or incomplete mobile version of the site. It's better for you to build up your mobile site and launch it when ready.  </li> </ul> <p>If you have any questions, feel free to contact us via the <a href="https://support.google.com/webmasters/go/community">Webmaster forums</a> or our <a href="https://www.google.com/webmasters/connect/">public events</a>. We anticipate this change will take some time and we’ll update you as we make progress on migrating our systems. </p> <br> <span class="byline-author">Posted by Doantam Phan, Product Manager</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>Today, most people are searching on Google using a mobile device. However, our ranking systems still typically look at the desktop version of a page’s content to evaluate its relevance to the user. This can cause issues when the mobile page has less content than the desktop page because our algorithms are not evaluating the actual page that is seen by a mobile searcher.</p> <p>To make our results more useful, we’ve begun experiments to make our index mobile-first. Although our search index will continue to be a single index of websites and apps, our algorithms will eventually primarily use the mobile version of a site’s content to rank pages from that site, to understand structured data, and to show snippets from those pages in our results. Of course, while our index will be built from mobile documents, we're going to continue to build a great search experience for all users, whether they come from mobile or desktop devices.</p> <p>We understand this is an important shift in our indexing and it’s one we take seriously. We’ll continue to carefully experiment over the coming months on a small scale and we’ll ramp up this change when we’re confident that we have a great user experience. Though we’re only beginning this process, here are a few recommendations to help webmasters prepare as we move towards a more mobile-focused index.</p> <ul style="padding:0 1em"><li>If you have a <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/responsive-design">responsive site</a> or a <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/dynamic-serving">dynamic serving site</a> where the primary content and markup is equivalent across mobile and desktop, you shouldn’t have to change anything.</li> <li>If you have a <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/">site configuration</a> where the primary content and markup is different across mobile and desktop, you should consider making some changes to your site.</li> <ul style="padding:0 1em"><li>Make sure to serve structured markup for both the desktop and mobile version.<br><br> Sites can verify the equivalence of their structured markup across desktop and mobile by typing the URLs of both versions into the <a href="https://search.google.com/structured-data/testing-tool">Structured Data Testing Tool</a> and comparing the output. <br><br> When adding structured data to a mobile site, avoid adding large amounts of markup that isn’t relevant to the specific information content of each document.</li> <li>Use the <a href="https://support.google.com/webmasters/answer/6062598">robots.txt testing tool</a> to verify that your mobile version is accessible to Googlebot. </li> <li>Sites do not have to make changes to their <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/separate-urls">canonical links</a>; we’ll continue to use these links as guides to serve the appropriate results to a user searching on desktop or mobile.</li></ul> <li>If you are a site owner who has only verified their desktop site in Search Console, <a href="https://support.google.com/webmasters/answer/35179">please add and verify your mobile version</a>.</li> <li>If you only have a desktop site, we'll continue to index your desktop site just fine, even if we're using a mobile user agent to view your site.<br><br> If you are building a mobile version of your site, keep in mind that a functional desktop-oriented site can be better than a broken or incomplete mobile version of the site. It's better for you to build up your mobile site and launch it when ready.  </li> </ul> <p>If you have any questions, feel free to contact us via the <a href="https://support.google.com/webmasters/go/community">Webmaster forums</a> or our <a href="https://www.google.com/webmasters/connect/">public events</a>. We anticipate this change will take some time and we’ll update you as we make progress on migrating our systems. </p> <br> <span class="byline-author">Posted by Doantam Phan, Product Manager</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Mobile-first Indexing&url=https://webmasters.googleblog.com/2016/11/mobile-first-indexing.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2016/11/mobile-first-indexing.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2016/11/mobile-first-indexing.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/mobile?hl=en_US' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US' rel='tag'> mobile-friendly </a> </span> </div> </div> </div> <div class='post' data-id='8416579939940062577' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/09/8-tips-to-amplify-your-clients.html?hl=en_US' itemprop='url' title='8 tips to AMPlify your clients'> 8 tips to AMPlify your clients </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, September 21, 2016 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjUyFT8DwZdnJ-rtiLk8iY5aJyWc08IGCtc2lbPf874cJUJ6T1ypi6MQkXlcRbjzgJCtWpMhWC7Zdt4C5WBe3-5GuCRwK2Q9gFbFX7c_M89Q8WXd6iZkm28Z_QpnNBVxmDMsJT_/s1600/BLOG+5-agency-rockin.jpg" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjUyFT8DwZdnJ-rtiLk8iY5aJyWc08IGCtc2lbPf874cJUJ6T1ypi6MQkXlcRbjzgJCtWpMhWC7Zdt4C5WBe3-5GuCRwK2Q9gFbFX7c_M89Q8WXd6iZkm28Z_QpnNBVxmDMsJT_/s640/BLOG+5-agency-rockin.jpg" width="640" /></a> <p>Here is our list of the top 8 things to consider when helping your clients AMPlify their websites (and staying ahead of their curiosity!) after our <a href="https://goo.gl/af7Psy">announcement</a> to expand support for <a href="//goo.gl/v6mxsL">Accelerated Mobile Pages</a>. </p> <ol><li style="font-weight:bold">Getting started can be simple</li> </ol><p>If a site uses a popular <a href="//goo.gl/1YjGUg">Content Management System (CMS)</a>, getting AMP pages up and running is as straightforward as installing a plug-in. Sites that use custom HTML or that are built from scratch will require additional development resources.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjSs_YvmFe87FmWVe5cman0DilH4AZOHKxgxHFyBot-FfHVL9xy5xBghyphenhyphenqVQoNCMeON4SZYBuOqDBR7DVt8ElNW8S0r4kXYLapU-Kgcs5p2yC4W8rCRldl9EdCwmkMYIy0CkZPa/s1600/AMP-Result-v3-CellPhoneCase.gif" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjSs_YvmFe87FmWVe5cman0DilH4AZOHKxgxHFyBot-FfHVL9xy5xBghyphenhyphenqVQoNCMeON4SZYBuOqDBR7DVt8ElNW8S0r4kXYLapU-Kgcs5p2yC4W8rCRldl9EdCwmkMYIy0CkZPa/s480/AMP-Result-v3-turned-to-11.gif" width="480" /></a> <ol start="2"><li style="font-weight:bold">Not all types of sites are suitable</li> </ol><p>AMP is great for all types of static web content such as news, recipes, movie listings, product pages, reviews, videos, blogs and more. AMP is less useful for single-page apps that are heavy on dynamic or interactive features, such as route mapping, email or social networks.</p> <ol start="3"><li style="font-weight:bold">You don’t have to #AMPlify the whole site</li> </ol><p>Add AMP to a client's existing site progressively by starting with simple, static content pages like articles, products, or blog posts. These are the “leaf” pages that users access through platforms and search results, and could be simple changes that also bring the benefits of AMP to the website. This approach allows you to keep the homepage and other “browser” pages that might require advanced, non-AMP dynamic functionality.</p> <p>If you're creating a new, content-heavy website from scratch, consider building the whole site with AMP from the start. To begin with, check out the <a href="//goo.gl/eeR7Li">getting started guidelines</a>.</p> <ol start="4"><li style="font-weight:bold">The AMP Project is open source and still evolving</li> </ol><p>If a site's use case is not supported in the AMP format yet, consider filing a <a href="//goo.gl/JxKTJw">feature request on GitHub</a>, or you could <a href="//goo.gl/CDnW2m">even design a component yourself</a>.</p> <ol start="5"><li style="font-weight:bold">AMP pages might need to meet additional requirements to show up in certain places</li> </ol><p>In order to appear in Google’s search results, AMP pages need only be <a href="//goo.gl/nxnGd2">valid</a> AMP HTML. Some products integrating AMP might have further requirements than the AMP validation. For example, you'll need to mark up your AMP pages as <a href="//goo.gl/FMeQ3s">Article markup</a> with <a href="//goo.gl/dPs7Na">Structured Data</a> to make them eligible for the Google Top Stories section.</p> <ol start="6"><li style="font-weight:bold">There is no ranking change on Search</li> </ol><p>Whether a page or site has valid and eligible AMP pages has no bearing on the site’s ranking on the Search results page. The difference is that web results that have AMP versions will be labeled with an <img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjQxRjYoVYwIEearbjyzR9-ArYS4VS5BqybGT0KmOKgQ6-ZeWMmuhckhekUN0ovjGF3X7Hc_9n5jXSAc_y81qNDp7LFYdBBSjyuiYgP7ZvWlUrICIkAVS0Mwe2ixHUAVmXMRgih/s240/pasted+image+0+%25283%2529.png" style="height:1em;margin:0" /> icon.</p> <ol start="7"><li style="font-weight:bold">AMP on Google is expanding globally</li> </ol><p>AMP search results on Google will be rolling out worldwide when it launches in the coming weeks. The <a href="//goo.gl/FMeQ3s">Top Stories carousel</a> which shows newsy and fresh AMP content is already available in a number of countries and languages.</p> <ol start="8"><li style="font-weight:bold">Help is on hand</li> </ol><p>There’s a whole host of useful resources that will help if you have any questions:</p> <p><a href="//goo.gl/Z6qscF">Webmasters Help Forum</a>: Ask questions about AMP and Google’s implementation of AMP<br> <a href="//goo.gl/FBgXKA">Stack Overflow</a>: Ask technical questions about AMP<br> <a href="//goo.gl/5UtZww">GitHub</a>: Submit a feature request or contribute<br> <p>What are your top tips to #AMPlify pages? Let us know in the comments below or on our <a href="//goo.gl/a4jxns">Google Webmasters Google+ page</a>. Or as usual, if you have any questions or need help, feel free to post in our <a href="//goo.gl/EyF09h">Webmasters Help Forum</a>.</p> <span class="byline-author">Posted by Tomo Taylor, AMP Community Manager </span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjUyFT8DwZdnJ-rtiLk8iY5aJyWc08IGCtc2lbPf874cJUJ6T1ypi6MQkXlcRbjzgJCtWpMhWC7Zdt4C5WBe3-5GuCRwK2Q9gFbFX7c_M89Q8WXd6iZkm28Z_QpnNBVxmDMsJT_/s1600/BLOG+5-agency-rockin.jpg" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjUyFT8DwZdnJ-rtiLk8iY5aJyWc08IGCtc2lbPf874cJUJ6T1ypi6MQkXlcRbjzgJCtWpMhWC7Zdt4C5WBe3-5GuCRwK2Q9gFbFX7c_M89Q8WXd6iZkm28Z_QpnNBVxmDMsJT_/s640/BLOG+5-agency-rockin.jpg" width="640" /></a> <p>Here is our list of the top 8 things to consider when helping your clients AMPlify their websites (and staying ahead of their curiosity!) after our <a href="https://goo.gl/af7Psy">announcement</a> to expand support for <a href="//goo.gl/v6mxsL">Accelerated Mobile Pages</a>. </p> <ol><li style="font-weight:bold">Getting started can be simple</li> </ol><p>If a site uses a popular <a href="//goo.gl/1YjGUg">Content Management System (CMS)</a>, getting AMP pages up and running is as straightforward as installing a plug-in. Sites that use custom HTML or that are built from scratch will require additional development resources.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjSs_YvmFe87FmWVe5cman0DilH4AZOHKxgxHFyBot-FfHVL9xy5xBghyphenhyphenqVQoNCMeON4SZYBuOqDBR7DVt8ElNW8S0r4kXYLapU-Kgcs5p2yC4W8rCRldl9EdCwmkMYIy0CkZPa/s1600/AMP-Result-v3-CellPhoneCase.gif" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjSs_YvmFe87FmWVe5cman0DilH4AZOHKxgxHFyBot-FfHVL9xy5xBghyphenhyphenqVQoNCMeON4SZYBuOqDBR7DVt8ElNW8S0r4kXYLapU-Kgcs5p2yC4W8rCRldl9EdCwmkMYIy0CkZPa/s480/AMP-Result-v3-turned-to-11.gif" width="480" /></a> <ol start="2"><li style="font-weight:bold">Not all types of sites are suitable</li> </ol><p>AMP is great for all types of static web content such as news, recipes, movie listings, product pages, reviews, videos, blogs and more. AMP is less useful for single-page apps that are heavy on dynamic or interactive features, such as route mapping, email or social networks.</p> <ol start="3"><li style="font-weight:bold">You don’t have to #AMPlify the whole site</li> </ol><p>Add AMP to a client's existing site progressively by starting with simple, static content pages like articles, products, or blog posts. These are the “leaf” pages that users access through platforms and search results, and could be simple changes that also bring the benefits of AMP to the website. This approach allows you to keep the homepage and other “browser” pages that might require advanced, non-AMP dynamic functionality.</p> <p>If you're creating a new, content-heavy website from scratch, consider building the whole site with AMP from the start. To begin with, check out the <a href="//goo.gl/eeR7Li">getting started guidelines</a>.</p> <ol start="4"><li style="font-weight:bold">The AMP Project is open source and still evolving</li> </ol><p>If a site's use case is not supported in the AMP format yet, consider filing a <a href="//goo.gl/JxKTJw">feature request on GitHub</a>, or you could <a href="//goo.gl/CDnW2m">even design a component yourself</a>.</p> <ol start="5"><li style="font-weight:bold">AMP pages might need to meet additional requirements to show up in certain places</li> </ol><p>In order to appear in Google’s search results, AMP pages need only be <a href="//goo.gl/nxnGd2">valid</a> AMP HTML. Some products integrating AMP might have further requirements than the AMP validation. For example, you'll need to mark up your AMP pages as <a href="//goo.gl/FMeQ3s">Article markup</a> with <a href="//goo.gl/dPs7Na">Structured Data</a> to make them eligible for the Google Top Stories section.</p> <ol start="6"><li style="font-weight:bold">There is no ranking change on Search</li> </ol><p>Whether a page or site has valid and eligible AMP pages has no bearing on the site’s ranking on the Search results page. The difference is that web results that have AMP versions will be labeled with an <img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjQxRjYoVYwIEearbjyzR9-ArYS4VS5BqybGT0KmOKgQ6-ZeWMmuhckhekUN0ovjGF3X7Hc_9n5jXSAc_y81qNDp7LFYdBBSjyuiYgP7ZvWlUrICIkAVS0Mwe2ixHUAVmXMRgih/s240/pasted+image+0+%25283%2529.png" style="height:1em;margin:0" /> icon.</p> <ol start="7"><li style="font-weight:bold">AMP on Google is expanding globally</li> </ol><p>AMP search results on Google will be rolling out worldwide when it launches in the coming weeks. The <a href="//goo.gl/FMeQ3s">Top Stories carousel</a> which shows newsy and fresh AMP content is already available in a number of countries and languages.</p> <ol start="8"><li style="font-weight:bold">Help is on hand</li> </ol><p>There’s a whole host of useful resources that will help if you have any questions:</p> <p><a href="//goo.gl/Z6qscF">Webmasters Help Forum</a>: Ask questions about AMP and Google’s implementation of AMP<br> <a href="//goo.gl/FBgXKA">Stack Overflow</a>: Ask technical questions about AMP<br> <a href="//goo.gl/5UtZww">GitHub</a>: Submit a feature request or contribute<br> <p>What are your top tips to #AMPlify pages? Let us know in the comments below or on our <a href="//goo.gl/a4jxns">Google Webmasters Google+ page</a>. Or as usual, if you have any questions or need help, feel free to post in our <a href="//goo.gl/EyF09h">Webmasters Help Forum</a>.</p> <span class="byline-author">Posted by Tomo Taylor, AMP Community Manager </span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:8 tips to AMPlify your clients&url=https://webmasters.googleblog.com/2016/09/8-tips-to-amplify-your-clients.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2016/09/8-tips-to-amplify-your-clients.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2016/09/8-tips-to-amplify-your-clients.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/AMP?hl=en_US' rel='tag'> AMP </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile?hl=en_US' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US' rel='tag'> mobile-friendly </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en_US' rel='tag'> search results </a> </span> </div> </div> </div> <div class='post' data-id='4231421905482559125' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/09/how-can-google-search-console-help-you.html?hl=en_US' itemprop='url' title='How can Google Search Console help you AMPlify your site?'> How can Google Search Console help you AMPlify your site? </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Friday, September 16, 2016 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjfhIIKD18cQzJXCW2cCvxIHNvOCkX78cEwUWOnX_sAAeypECBVUEtor1UMV9MrpQbtM6aG_FJZrSsoG64iO3tNDVlZWuoZocozxPs85zuw6-Tb_tFLjNEs5J-P6n7Rs0apbGvM/s1600/AMP-searchConsole.jpg" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjfhIIKD18cQzJXCW2cCvxIHNvOCkX78cEwUWOnX_sAAeypECBVUEtor1UMV9MrpQbtM6aG_FJZrSsoG64iO3tNDVlZWuoZocozxPs85zuw6-Tb_tFLjNEs5J-P6n7Rs0apbGvM/s640/AMP-searchConsole.jpg" width="640" /></a> <p>If you have recently implemented <a href="//goo.gl/VBlulY">Accelerated Mobile Pages</a> on your site, it’s a great time to check which of your AMP pages Google has found and indexed by using <a href="//goo.gl/yIjCCt">Search Console</a>. </p> <p>Search Console is a free service that helps you monitor and maintain your site's presence in Google Search, including any Accelerated Mobile Pages. You don't have to sign up for Search Console for your AMP pages to be included in Google Search results, but doing so can help you understand which of your AMP pages are eligible to show in search results.</p> <p>To get started with Search Console, create a free account or sign in <a href="//goo.gl/yIjCCt">here</a> and <a href="//goo.gl/WcW67l">validate the ownership of your sites</a>. </p> <p>Once you have your site set up on Search Console, open the <a href="//goo.gl/JXTLf7">Accelerated Mobile Pages report</a> under Search Appearance > Accelerated Mobile Pages to see which AMP pages Google has found and indexed on your site, as shown here: </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjreeP7CjJMeotbv-v1gn60E35spoI-ShUpIFHCAae1WCZ4BIe8Kcdcy2dcEJt_iQLEzQSwXJY8-H1rSN8iZAOExOWohV_CFpx8b3f6pglgF1zb-UXwQx8__WsDRcayhMM9jL1O/s1600/Screen+Shot+2016-09-15+at+2.53.21+PM.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjreeP7CjJMeotbv-v1gn60E35spoI-ShUpIFHCAae1WCZ4BIe8Kcdcy2dcEJt_iQLEzQSwXJY8-H1rSN8iZAOExOWohV_CFpx8b3f6pglgF1zb-UXwQx8__WsDRcayhMM9jL1O/s640/Screen+Shot+2016-09-15+at+2.53.21+PM.png" width="640" /></a> </p> <p>The report lists AMP-related issues for AMP pages that are not indexed, so that you can identify and address them.</p> <p>Search Console also lets you monitor the performance of your AMP pages on Google Search in the <a href="https://goo.gl/yDNWtq">Search Analytics report</a>. This report tells you which queries show your AMP pages in Search results, lets you compare how their metrics stack against your other results and see how the visibility of your AMP pages has changed over time. </p> <p>To view your AMP page metrics, such as clicks or impressions, select Search Appearance > Search Analytics > Filter by AMP.</p> <p>(Note: if you’ve only just created your Search Console account or set up your AMP pages and they have not been detected yet, remember that Google crawls pages only periodically. You can wait for the scheduled regular recrawl, or you can <a href="//goo.gl/FhLexR">request a recrawl</a>.)</p> <p>Have you been using Search Console to monitor your AMP pages? Give us feedback in the comments below or on our <a href="//goo.gl/z7H09v">Google Webmasters Google+ page</a>. Or as usual, if you have any questions or need help, feel free to post in our <a href="//goo.gl/849dzr">Webmasters Help Forum</a>.</p> <p><b>UPDATE</b>: To help ensure that your AMP implementation is working as expected, Search Console now has an <a href="https://search.google.com/search-console/amp">enhanced AMP testing tool</a>.</p> <span class="byline-author">Posted by Tom Taylor, AMP Community Manager </span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjfhIIKD18cQzJXCW2cCvxIHNvOCkX78cEwUWOnX_sAAeypECBVUEtor1UMV9MrpQbtM6aG_FJZrSsoG64iO3tNDVlZWuoZocozxPs85zuw6-Tb_tFLjNEs5J-P6n7Rs0apbGvM/s1600/AMP-searchConsole.jpg" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjfhIIKD18cQzJXCW2cCvxIHNvOCkX78cEwUWOnX_sAAeypECBVUEtor1UMV9MrpQbtM6aG_FJZrSsoG64iO3tNDVlZWuoZocozxPs85zuw6-Tb_tFLjNEs5J-P6n7Rs0apbGvM/s640/AMP-searchConsole.jpg" width="640" /></a> <p>If you have recently implemented <a href="//goo.gl/VBlulY">Accelerated Mobile Pages</a> on your site, it’s a great time to check which of your AMP pages Google has found and indexed by using <a href="//goo.gl/yIjCCt">Search Console</a>. </p> <p>Search Console is a free service that helps you monitor and maintain your site's presence in Google Search, including any Accelerated Mobile Pages. You don't have to sign up for Search Console for your AMP pages to be included in Google Search results, but doing so can help you understand which of your AMP pages are eligible to show in search results.</p> <p>To get started with Search Console, create a free account or sign in <a href="//goo.gl/yIjCCt">here</a> and <a href="//goo.gl/WcW67l">validate the ownership of your sites</a>. </p> <p>Once you have your site set up on Search Console, open the <a href="//goo.gl/JXTLf7">Accelerated Mobile Pages report</a> under Search Appearance > Accelerated Mobile Pages to see which AMP pages Google has found and indexed on your site, as shown here: </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjreeP7CjJMeotbv-v1gn60E35spoI-ShUpIFHCAae1WCZ4BIe8Kcdcy2dcEJt_iQLEzQSwXJY8-H1rSN8iZAOExOWohV_CFpx8b3f6pglgF1zb-UXwQx8__WsDRcayhMM9jL1O/s1600/Screen+Shot+2016-09-15+at+2.53.21+PM.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjreeP7CjJMeotbv-v1gn60E35spoI-ShUpIFHCAae1WCZ4BIe8Kcdcy2dcEJt_iQLEzQSwXJY8-H1rSN8iZAOExOWohV_CFpx8b3f6pglgF1zb-UXwQx8__WsDRcayhMM9jL1O/s640/Screen+Shot+2016-09-15+at+2.53.21+PM.png" width="640" /></a> </p> <p>The report lists AMP-related issues for AMP pages that are not indexed, so that you can identify and address them.</p> <p>Search Console also lets you monitor the performance of your AMP pages on Google Search in the <a href="https://goo.gl/yDNWtq">Search Analytics report</a>. This report tells you which queries show your AMP pages in Search results, lets you compare how their metrics stack against your other results and see how the visibility of your AMP pages has changed over time. </p> <p>To view your AMP page metrics, such as clicks or impressions, select Search Appearance > Search Analytics > Filter by AMP.</p> <p>(Note: if you’ve only just created your Search Console account or set up your AMP pages and they have not been detected yet, remember that Google crawls pages only periodically. You can wait for the scheduled regular recrawl, or you can <a href="//goo.gl/FhLexR">request a recrawl</a>.)</p> <p>Have you been using Search Console to monitor your AMP pages? Give us feedback in the comments below or on our <a href="//goo.gl/z7H09v">Google Webmasters Google+ page</a>. Or as usual, if you have any questions or need help, feel free to post in our <a href="//goo.gl/849dzr">Webmasters Help Forum</a>.</p> <p><b>UPDATE</b>: To help ensure that your AMP implementation is working as expected, Search Console now has an <a href="https://search.google.com/search-console/amp">enhanced AMP testing tool</a>.</p> <span class="byline-author">Posted by Tom Taylor, AMP Community Manager </span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:How can Google Search Console help you AMPlify your site?&url=https://webmasters.googleblog.com/2016/09/how-can-google-search-console-help-you.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2016/09/how-can-google-search-console-help-you.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2016/09/how-can-google-search-console-help-you.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/AMP?hl=en_US' rel='tag'> AMP </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile?hl=en_US' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US' rel='tag'> mobile-friendly </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en_US' rel='tag'> search results </a> </span> </div> </div> </div> <div class='post' data-id='5012439023690252987' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/05/a-new-mobile-friendly-testing-tool.html?hl=en_US' itemprop='url' title='A new mobile friendly testing tool'> A new mobile friendly testing tool </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, May 17, 2016 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p>Mobile is close to our heart - we love seeing more and more sites make their content available in useful & accessible ways for mobile users. To help keep the ball rolling, we've now launched a new Mobile Friendly Test. </p> <p>The new tool is linked from Search Console's <a href="https://support.google.com/webmasters/answer/6101188">mobile usability report</a> or available directly at <a href="https://search.google.com/search-console/mobile-friendly">https://search.google.com/search-console/mobile-friendly</a> </p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgzDTLLzJ-KNEGMj_bzC3Z14vNtt3G4wQyArKclD9qyP2pqwvNbx9eDL0RuVCM3cgV37GeOivcv9ulW9y5N-GibozZnjKfu-myV8LtRB8hEZOW5IQJB5OzBzcmSsO2WIPycH8zw/s1600/Screen+Shot+2016-04-15+at+12.04.30+AM.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgzDTLLzJ-KNEGMj_bzC3Z14vNtt3G4wQyArKclD9qyP2pqwvNbx9eDL0RuVCM3cgV37GeOivcv9ulW9y5N-GibozZnjKfu-myV8LtRB8hEZOW5IQJB5OzBzcmSsO2WIPycH8zw/s400/Screen+Shot+2016-04-15+at+12.04.30+AM.png" /></a> <p>The updated tool provides us with room to continue to improve on its functionality, and over time, we expect it to replace the previous Mobile Friendly Test. Additionally, of course this tool also works well on your smartphone, if you need to double-check something there!</p> <p>We'd like to invite you to take it for a spin, try your website and other sites that you're curious about! Let us know how you like it - either here in the comments or in our <a href="https://g.co/webmasterhelpforum">webmaster help forums</a>.</p> <span class="byline-author">Posted by Yaniv Loewenstein, Search Console Team</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p>Mobile is close to our heart - we love seeing more and more sites make their content available in useful & accessible ways for mobile users. To help keep the ball rolling, we've now launched a new Mobile Friendly Test. </p> <p>The new tool is linked from Search Console's <a href="https://support.google.com/webmasters/answer/6101188">mobile usability report</a> or available directly at <a href="https://search.google.com/search-console/mobile-friendly">https://search.google.com/search-console/mobile-friendly</a> </p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgzDTLLzJ-KNEGMj_bzC3Z14vNtt3G4wQyArKclD9qyP2pqwvNbx9eDL0RuVCM3cgV37GeOivcv9ulW9y5N-GibozZnjKfu-myV8LtRB8hEZOW5IQJB5OzBzcmSsO2WIPycH8zw/s1600/Screen+Shot+2016-04-15+at+12.04.30+AM.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgzDTLLzJ-KNEGMj_bzC3Z14vNtt3G4wQyArKclD9qyP2pqwvNbx9eDL0RuVCM3cgV37GeOivcv9ulW9y5N-GibozZnjKfu-myV8LtRB8hEZOW5IQJB5OzBzcmSsO2WIPycH8zw/s400/Screen+Shot+2016-04-15+at+12.04.30+AM.png" /></a> <p>The updated tool provides us with room to continue to improve on its functionality, and over time, we expect it to replace the previous Mobile Friendly Test. Additionally, of course this tool also works well on your smartphone, if you need to double-check something there!</p> <p>We'd like to invite you to take it for a spin, try your website and other sites that you're curious about! Let us know how you like it - either here in the comments or in our <a href="https://g.co/webmasterhelpforum">webmaster help forums</a>.</p> <span class="byline-author">Posted by Yaniv Loewenstein, Search Console Team</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:A new mobile friendly testing tool&url=https://webmasters.googleblog.com/2016/05/a-new-mobile-friendly-testing-tool.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2016/05/a-new-mobile-friendly-testing-tool.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2016/05/a-new-mobile-friendly-testing-tool.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/mobile?hl=en_US' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US' rel='tag'> mobile-friendly </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> </span> </div> </div> </div> <div class='post' data-id='8727389347193005305' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/03/continuing-to-make-web-more-mobile.html?hl=en_US' itemprop='url' title='Continuing to make the web more mobile friendly'> Continuing to make the web more mobile friendly </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, March 16, 2016 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> Getting good, relevant answers when you search shouldn’t depend on what device you’re using. You should get the best answer possible, whether you’re on a phone, desktop or tablet. <a href="https://webmasters.googleblog.com/2015/04/rolling-out-mobile-friendly-update.html">Last year</a>, we started using mobile-friendliness as a ranking signal on mobile searches. Today we’re announcing that beginning in May, we’ll start rolling out an update to mobile search results that increases the effect of the ranking signal to help our users find even more pages that are relevant and mobile-friendly.<br /> <br /> If you've already made your site mobile-friendly, you will not be impacted by this update. If you need support with your mobile-friendly site, we recommend checking out the <a href="https://www.google.com/webmasters/tools/mobile-friendly/">Mobile-Friendly Test</a> and the <a href="https://developers.google.com/webmasters/mobile-sites/">Webmaster Mobile Guide</a>, both of which provide guidance on how to improve your mobile site. And remember, the intent of the search query is still a very strong signal — so even if a page with high quality content is not mobile-friendly, it could still rank well if it has great, relevant content. <br /> <br /> If you have any questions, please go to the <a href="https://g.co/webmasterhelpforum">Webmaster help forum</a>. <br /> <br /> <span class="byline-author">Posted by Klemen Kloboves, Software Engineer </span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> Getting good, relevant answers when you search shouldn’t depend on what device you’re using. You should get the best answer possible, whether you’re on a phone, desktop or tablet. <a href="https://webmasters.googleblog.com/2015/04/rolling-out-mobile-friendly-update.html">Last year</a>, we started using mobile-friendliness as a ranking signal on mobile searches. Today we’re announcing that beginning in May, we’ll start rolling out an update to mobile search results that increases the effect of the ranking signal to help our users find even more pages that are relevant and mobile-friendly.<br /> <br /> If you've already made your site mobile-friendly, you will not be impacted by this update. If you need support with your mobile-friendly site, we recommend checking out the <a href="https://www.google.com/webmasters/tools/mobile-friendly/">Mobile-Friendly Test</a> and the <a href="https://developers.google.com/webmasters/mobile-sites/">Webmaster Mobile Guide</a>, both of which provide guidance on how to improve your mobile site. And remember, the intent of the search query is still a very strong signal — so even if a page with high quality content is not mobile-friendly, it could still rank well if it has great, relevant content. <br /> <br /> If you have any questions, please go to the <a href="https://g.co/webmasterhelpforum">Webmaster help forum</a>. <br /> <br /> <span class="byline-author">Posted by Klemen Kloboves, Software Engineer </span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Continuing to make the web more mobile friendly&url=https://webmasters.googleblog.com/2016/03/continuing-to-make-web-more-mobile.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2016/03/continuing-to-make-web-more-mobile.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2016/03/continuing-to-make-web-more-mobile.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/mobile?hl=en_US' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US' rel='tag'> mobile-friendly </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en_US' rel='tag'> search results </a> </span> </div> </div> </div> <div class='post' data-id='5416555108434952031' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2015/09/mobile-friendly-web-pages-using-app.html?hl=en_US' itemprop='url' title='Mobile-friendly web pages using app banners'> Mobile-friendly web pages using app banners </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, September 01, 2015 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> When it comes to search on mobile devices, users should get the most relevant answers, no matter if the answer lives in an app or a web page. We’ve recently made it easier for users to <a href="http://insidesearch.blogspot.com/2015/06/find-app-content-straight-from-google.html">find and discover apps</a> and <a href="http://googlewebmastercentral.blogspot.com/2015/02/finding-more-mobile-friendly-search.html">mobile-friendly web pages</a>. However, sometimes a user may tap on a search result on a mobile device and see an app install interstitial that hides a significant amount of content and prompts the user to install an app. Our analysis shows that it is not a good search experience and can be frustrating for users because they are expecting to see the content of the web page.<br /> Starting today, we’ll be updating the <a href="https://www.google.com/webmasters/tools/mobile-friendly/">Mobile-Friendly Test</a> to indicate that sites should avoid showing app install interstitials that hide a significant amount of content on the transition from the search result page. The <a href="https://www.google.com/webmasters/tools/mobile-usability?utm_source=appinterstitialspost&utm_medium=blog&utm_campaign=appinterstitials&pli=1">Mobile Usability report</a> in Search Console will show webmasters the number of pages across their site that have this issue.<br /> After November 1, mobile web pages that show an app install interstitial that hides a significant amount of content on the transition from the search result page will no longer be considered mobile-friendly. This does not affect other types of interstitials. As an alternative to app install interstitials, browsers provide ways to promote an app that are more user-friendly.<br /> <div> <div style="float: left; min-width: 200px; width: 49%;"> <img src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhqbu1kOG_ZL9Nne7F9MpIcboP9xvzispFibu-DcfWxx8_Jk5t3MkI-VrMNwRs4p7-Weo0AeWO5RgysFGhr1cUVMguQWuSI7DsP0cBmIpUHqAYQISp2GyfSTmD8YFDU-3kb-_vC/s320/06_Device.png" width="95%" /> <br /> <i>App install interstitials that hide a significant amount of content provide a bad search experience</i> </div> <div style="float: left; min-width: 200px; width: 49%;"> <img src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjYySft9NyMD5dat_OZTNaYhc4eVkC2_DtWLuo4kZPxDJbLYLgAvvbT3WG4XlCTvwXuIb7jdozgH5HToXaeTlYS7bmddc02h0R21m24R7wcJvMStJ02s4zPQ8FEeMC0U3gnFhJs/s320/07_Device.png" width="95%" /> <br /> <i>App install banners are less intrusive and preferred</i> </div> </div> <br style="clear: both;" /> App install banners are supported by Safari (as <a href="https://developer.apple.com/library/mac/documentation/AppleApplications/Reference/SafariWebContent/PromotingAppswithAppBanners/PromotingAppswithAppBanners.html">Smart Banners</a>) and Chrome (as <a data-blogger-escaped-target="_blank" href="https://developers.google.com/web/updates/2015/03/increasing-engagement-with-app-install-banners-in-chrome-for-android#native">Native App Install Banners</a>). Banners provide a consistent user interface for promoting an app and provide the user with the ability to control their browsing experience. Webmasters can also use their own implementations of app install banners as long as they don’t block searchers from viewing the page’s content.<br /> If you have any questions, we’re always happy to chat in the <a href="https://productforums.google.com/forum/#!categories/webmasters/mobile">Webmaster Central Forum</a>.<br /> Posted by Daniel Bathgate, Software Engineer, Google Search.</div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> When it comes to search on mobile devices, users should get the most relevant answers, no matter if the answer lives in an app or a web page. We’ve recently made it easier for users to <a href="http://insidesearch.blogspot.com/2015/06/find-app-content-straight-from-google.html">find and discover apps</a> and <a href="http://googlewebmastercentral.blogspot.com/2015/02/finding-more-mobile-friendly-search.html">mobile-friendly web pages</a>. However, sometimes a user may tap on a search result on a mobile device and see an app install interstitial that hides a significant amount of content and prompts the user to install an app. Our analysis shows that it is not a good search experience and can be frustrating for users because they are expecting to see the content of the web page.<br /> Starting today, we’ll be updating the <a href="https://www.google.com/webmasters/tools/mobile-friendly/">Mobile-Friendly Test</a> to indicate that sites should avoid showing app install interstitials that hide a significant amount of content on the transition from the search result page. The <a href="https://www.google.com/webmasters/tools/mobile-usability?utm_source=appinterstitialspost&utm_medium=blog&utm_campaign=appinterstitials&pli=1">Mobile Usability report</a> in Search Console will show webmasters the number of pages across their site that have this issue.<br /> After November 1, mobile web pages that show an app install interstitial that hides a significant amount of content on the transition from the search result page will no longer be considered mobile-friendly. This does not affect other types of interstitials. As an alternative to app install interstitials, browsers provide ways to promote an app that are more user-friendly.<br /> <div> <div style="float: left; min-width: 200px; width: 49%;"> <img src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhqbu1kOG_ZL9Nne7F9MpIcboP9xvzispFibu-DcfWxx8_Jk5t3MkI-VrMNwRs4p7-Weo0AeWO5RgysFGhr1cUVMguQWuSI7DsP0cBmIpUHqAYQISp2GyfSTmD8YFDU-3kb-_vC/s320/06_Device.png" width="95%" /> <br /> <i>App install interstitials that hide a significant amount of content provide a bad search experience</i> </div> <div style="float: left; min-width: 200px; width: 49%;"> <img src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjYySft9NyMD5dat_OZTNaYhc4eVkC2_DtWLuo4kZPxDJbLYLgAvvbT3WG4XlCTvwXuIb7jdozgH5HToXaeTlYS7bmddc02h0R21m24R7wcJvMStJ02s4zPQ8FEeMC0U3gnFhJs/s320/07_Device.png" width="95%" /> <br /> <i>App install banners are less intrusive and preferred</i> </div> </div> <br style="clear: both;" /> App install banners are supported by Safari (as <a href="https://developer.apple.com/library/mac/documentation/AppleApplications/Reference/SafariWebContent/PromotingAppswithAppBanners/PromotingAppswithAppBanners.html">Smart Banners</a>) and Chrome (as <a data-blogger-escaped-target="_blank" href="https://developers.google.com/web/updates/2015/03/increasing-engagement-with-app-install-banners-in-chrome-for-android#native">Native App Install Banners</a>). Banners provide a consistent user interface for promoting an app and provide the user with the ability to control their browsing experience. Webmasters can also use their own implementations of app install banners as long as they don’t block searchers from viewing the page’s content.<br /> If you have any questions, we’re always happy to chat in the <a href="https://productforums.google.com/forum/#!categories/webmasters/mobile">Webmaster Central Forum</a>.<br /> Posted by Daniel Bathgate, Software Engineer, Google Search.</div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Mobile-friendly web pages using app banners&url=https://webmasters.googleblog.com/2015/09/mobile-friendly-web-pages-using-app.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2015/09/mobile-friendly-web-pages-using-app.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2015/09/mobile-friendly-web-pages-using-app.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/mobile?hl=en_US' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US' rel='tag'> mobile-friendly </a> </span> </div> </div> </div> <div class='post' data-id='1450226588797460780' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2015/04/rolling-out-mobile-friendly-update.html?hl=en_US' itemprop='url' title='Rolling out the mobile-friendly update'> Rolling out the mobile-friendly update </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, April 21, 2015 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> As <a href="http://googlewebmastercentral.blogspot.com/2015/02/finding-more-mobile-friendly-search.html" target="_blank">we noted earlier this year</a>, today’s the day we begin globally rolling out our mobile-friendly update. We’re boosting the ranking of mobile-friendly pages on mobile search results. Now searchers can more easily find high-quality and relevant results where text is readable without tapping or zooming, tap targets are spaced appropriately, and the page avoids unplayable content or horizontal scrolling.<br /> <div> <br /></div> <div style="text-align: center;"> <span id="docs-internal-guid-c26b5801-dade-c346-2239-37ab71b6e496"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"><img alt="Screen Shot 2015-04-07 at 2.20.01 AM.png" height="474px;" src="https://lh6.googleusercontent.com/3Lyi07zgZzWl0U7Gq0ZwmqgEqsv2ir8-o3ky6eijHDFMzCoYFSqMFQoF4ozjPhZAlGul5YtHbSxjunwwJs-GT-BV4dDap6VA0HS971eIBCNriASMtMzh1vOE9kHvkvF5SH2siag" style="-webkit-transform: rotate(0.00rad); border: none; transform: rotate(0.00rad);" width="505px;" /></span></span></div> <div style="text-align: center;"> <span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span></div> <div style="text-align: center;"> <span style="font-family: Arial; font-size: x-small;"><span style="white-space: pre-wrap;"><i>April 21st’s mobile-friendly update boosts mobile search rankings for pages that are legible and usable on mobile devices.</i></span></span></div> <div style="text-align: left;"> <br /></div> <div style="text-align: left;"> <div> This update:</div> <div> <ul style="text-align: left;"> <li>Affects only search rankings on mobile devices</li> <li>Affects search results in all languages globally </li> <li>Applies to individual pages, not entire websites</li> </ul> </div> <div> <br /></div> <div> <div> While the mobile-friendly change is important, we still use a variety of signals to rank search results. The intent of the search query is still a very strong signal -- so even if a page with high quality content is not mobile-friendly, it could still rank high if it has great content for the query. </div> </div> <div> <br /></div> <div> <div> To check if your site is mobile-friendly, you can examine individual pages with the <a href="https://www.google.com/webmasters/tools/mobile-friendly/?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Mobile-Friendly Test</a> or check the status of your entire site through the <a href="https://www.google.com/webmasters/tools/mobile-usability?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Mobile Usability report in Webmaster Tools</a>. If your site’s pages aren’t mobile-friendly, there may be a significant decrease in mobile traffic from Google Search. But have no fear, once your site <a href="https://developers.google.com/webmasters/mobile-sites/?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">becomes mobile-friendly</a>, we will automatically re-process (i.e., crawl and index) your pages.  You can also expedite the process by using <a href="https://support.google.com/webmasters/answer/6065812" target="_blank">Fetch as Google with Submit to Index</a>, and then your pages can be treated as mobile-friendly in ranking.</div> </div> <div> <br /></div> <div> <div> Questions? See <a href="http://googlewebmastercentral.blogspot.com/2015/04/faqs-april-21st-mobile-friendly.html" target="_blank">our FAQ</a> or ask on the <a href="https://productforums.google.com/forum/#!categories/webmasters/mobile" target="_blank">Mobile Websites section of the Webmaster Forum</a>. </div> </div> <div> <br /></div> <div> <br /></div> </div> <span class="byline-author">Posted by Takaki Makino and Doantam Phan</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> As <a href="http://googlewebmastercentral.blogspot.com/2015/02/finding-more-mobile-friendly-search.html" target="_blank">we noted earlier this year</a>, today’s the day we begin globally rolling out our mobile-friendly update. We’re boosting the ranking of mobile-friendly pages on mobile search results. Now searchers can more easily find high-quality and relevant results where text is readable without tapping or zooming, tap targets are spaced appropriately, and the page avoids unplayable content or horizontal scrolling.<br /> <div> <br /></div> <div style="text-align: center;"> <span id="docs-internal-guid-c26b5801-dade-c346-2239-37ab71b6e496"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"><img alt="Screen Shot 2015-04-07 at 2.20.01 AM.png" height="474px;" src="https://lh6.googleusercontent.com/3Lyi07zgZzWl0U7Gq0ZwmqgEqsv2ir8-o3ky6eijHDFMzCoYFSqMFQoF4ozjPhZAlGul5YtHbSxjunwwJs-GT-BV4dDap6VA0HS971eIBCNriASMtMzh1vOE9kHvkvF5SH2siag" style="-webkit-transform: rotate(0.00rad); border: none; transform: rotate(0.00rad);" width="505px;" /></span></span></div> <div style="text-align: center;"> <span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span></div> <div style="text-align: center;"> <span style="font-family: Arial; font-size: x-small;"><span style="white-space: pre-wrap;"><i>April 21st’s mobile-friendly update boosts mobile search rankings for pages that are legible and usable on mobile devices.</i></span></span></div> <div style="text-align: left;"> <br /></div> <div style="text-align: left;"> <div> This update:</div> <div> <ul style="text-align: left;"> <li>Affects only search rankings on mobile devices</li> <li>Affects search results in all languages globally </li> <li>Applies to individual pages, not entire websites</li> </ul> </div> <div> <br /></div> <div> <div> While the mobile-friendly change is important, we still use a variety of signals to rank search results. The intent of the search query is still a very strong signal -- so even if a page with high quality content is not mobile-friendly, it could still rank high if it has great content for the query. </div> </div> <div> <br /></div> <div> <div> To check if your site is mobile-friendly, you can examine individual pages with the <a href="https://www.google.com/webmasters/tools/mobile-friendly/?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Mobile-Friendly Test</a> or check the status of your entire site through the <a href="https://www.google.com/webmasters/tools/mobile-usability?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Mobile Usability report in Webmaster Tools</a>. If your site’s pages aren’t mobile-friendly, there may be a significant decrease in mobile traffic from Google Search. But have no fear, once your site <a href="https://developers.google.com/webmasters/mobile-sites/?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">becomes mobile-friendly</a>, we will automatically re-process (i.e., crawl and index) your pages.  You can also expedite the process by using <a href="https://support.google.com/webmasters/answer/6065812" target="_blank">Fetch as Google with Submit to Index</a>, and then your pages can be treated as mobile-friendly in ranking.</div> </div> <div> <br /></div> <div> <div> Questions? See <a href="http://googlewebmastercentral.blogspot.com/2015/04/faqs-april-21st-mobile-friendly.html" target="_blank">our FAQ</a> or ask on the <a href="https://productforums.google.com/forum/#!categories/webmasters/mobile" target="_blank">Mobile Websites section of the Webmaster Forum</a>. </div> </div> <div> <br /></div> <div> <br /></div> </div> <span class="byline-author">Posted by Takaki Makino and Doantam Phan</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Rolling out the mobile-friendly update&url=https://webmasters.googleblog.com/2015/04/rolling-out-mobile-friendly-update.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2015/04/rolling-out-mobile-friendly-update.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2015/04/rolling-out-mobile-friendly-update.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/mobile?hl=en_US' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US' rel='tag'> mobile-friendly </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en_US' rel='tag'> webmaster community </a> </span> </div> </div> </div> <div class='post' data-id='2230493274911537995' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2015/04/faqs-april-21st-mobile-friendly.html?hl=en_US' itemprop='url' title='FAQs about the April 21st mobile-friendly update '> FAQs about the April 21st mobile-friendly update </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, April 21, 2015 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> We’d like to share answers to your frequently asked questions. For background, in February, <a href="http://googlewebmastercentral.blogspot.com/2015/02/finding-more-mobile-friendly-search.html" target="_blank">we announced that the mobile-friendly update </a>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 in rankings in mobile search results.) To get us all on the same page, here are the most frequently asked questions:<br /> <br /> <h2 style="text-align: left;"> General FAQs</h2> <div> <br /></div> <i><b>1. Will desktop and/or tablet ranking also be affected by this change?</b></i><br /> <br /> <div style="text-align: left;"> No, this update has no effect on searches from tablets or desktops. It affects searches from mobile devices across all languages and locations.</div> <br /> <br /> <i><b>2. Is it a page-level or site-level mobile ranking boost? </b></i><br /> <br /> It’s a page-level change. For instance, if ten of your site’s pages are mobile-friendly, but the rest of your pages aren’t, only the ten mobile-friendly pages can be positively impacted.<br /> <br /> <br /> <i><b>3. How do I know if Google thinks a page on my site is mobile-friendly?</b></i><br /> <br /> Individual pages can be tested for “mobile-friendliness” using the <a href="https://www.google.com/webmasters/tools/mobile-friendly?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Mobile-Friendly Test</a>.<br /> <br /> <div style="text-align: center;"> <span id="docs-internal-guid-74be34dd-dad6-2acb-48eb-8578143d9fd5"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"><img alt="Screen Shot 2015-04-08 at 5.41.16 PM.png" height="308px;" src="https://lh6.googleusercontent.com/lgRhY4O6dT1kT69QvaiH3-TFB2u9eXdzYaM2pDfrwxHEkVDRr30Yb3owhFzv7nSjnOTUwBf4Sc7AtV5GlerBNv5DS-LFRlYUz60KaFScKKTOeO-2UHrd1Du3EKV-Q3RAAl6-JEw" style="-webkit-transform: rotate(0.00rad); border: 3px solid #d9d9d9; transform: rotate(0.00rad);" width="469px;" /></span></span></div> <div style="text-align: center;"> <span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span></div> <div style="text-align: center;"> <span style="font-family: Arial; font-size: x-small;"><span style="white-space: pre-wrap;"><i>Test individual URLs in real-time with the Mobile-Friendly Test.</i></span></span></div> <div style="text-align: center;"> <br /></div> <div style="text-align: left;"> To review site-level information on mobile-friendliness, check out the <a href="https://www.google.com/webmasters/tools/mobile-usability?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Mobile Usability report in Webmaster Tools</a>. This feature’s data is based on the last time we crawled and indexed your site’s pages.</div> <div style="text-align: left;"> <br /></div> <div style="text-align: center;"> <span id="docs-internal-guid-74be34dd-dad5-d729-9202-140fcde09d95"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"><img alt="Screen Shot 2015-04-08 at 5.39.24 PM.png" height="346px;" src="https://lh6.googleusercontent.com/egGhk2N72zSgS5Ckl4MFocJoOCOvdBLK0rgfEmDN3L0IwIubceKDuYdUPj_r-fBC9rrOu2BkyljJLwmH8-CPIBuGphgvL7vQmS9ZFSSqTpfTye1xUISA_pVrOU47F_mthPr2sVo" style="-webkit-transform: rotate(0.00rad); border: 3px solid #d9d9d9; transform: rotate(0.00rad);" width="475px;" /></span></span></div> <div style="text-align: center;"> <span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span></div> <div style="text-align: center;"> <span style="font-family: Arial; font-size: x-small;"><span style="white-space: pre-wrap;"><i>Mobile Usability in Webmaster Tools provides a snapshot of your entire site’s mobile-friendliness.</i></span></span></div> <div style="text-align: center;"> <br /></div> <div style="text-align: center;"> <span id="docs-internal-guid-74be34dd-dad2-a9fc-57e7-13e555429583"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span></span></div> <br /> <br /> <div> <i><b>4. Unfortunately, my mobile-friendly pages won’t be ready until after April 21st. How long before they can be considered mobile-friendly in ranking?</b></i></div> <div> <br /></div> <div> We determine whether a page is mobile-friendly every time it’s crawled and indexed -- you don’t have to wait for another update. Once a page is mobile-friendly, you can wait for <a href="http://googlewebmastercentral.blogspot.ch/2014/01/a-new-googlebot-user-agent-for-crawling.html" target="_blank">Googlebot for smartphones </a>to naturally (re-)crawl and index the page or you can expedite processing by using <a href="https://support.google.com/webmasters/answer/6065812" target="_blank">Fetch as Google with Submit to Index</a> in <a href="https://www.google.com/webmasters/tools?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Webmaster Tools</a>. For a large volume of URLs, consider submitting a <a href="https://support.google.com/webmasters/answer/156184" target="_blank">sitemap</a>. In the sitemap, if your mobile content uses pre-existing URLs (such as with <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/configurations/responsive-design?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Responsive Web Design</a> or <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/configurations/dynamic-serving?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">dynamic serving</a>), also include the <a href="http://www.sitemaps.org/protocol.html#lastmoddef" target="_blank">lastmod tag</a>.</div> <div> <br /> <br /></div> <div> <i><b>5. Since the mobile ranking change rolls out on April 21st, if I see no drop in traffic on April 22nd, does that mean that my site’s rankings aren't impacted?</b></i></div> <div> <br /></div> <div> You won't be able to definitively determine whether your site’s rankings are impacted by the mobile-friendly update by April 22nd. While we begin rolling out the mobile-friendly update on April 21st, it’ll be a week or so before it makes its way to all pages in the index. </div> <div> <br /> <br /></div> <div> <i><b>6. I have a great mobile site, but the Mobile-Friendly Test tells me that my pages aren't mobile-friendly. Why?</b></i></div> <div> <br /></div> <div> If a page is designed to work well on mobile devices, but it’s not passing the Mobile-Friendly Test, the most common reason is that Googlebot for smartphones is blocked from crawling resources, like CSS and JavaScript, that are critical for determining whether the page is legible and usable on a mobile device (i.e., whether it’s mobile-friendly). To remedy:</div> <div> <ol style="text-align: left;"> <li>Check if the <a href="https://www.google.com/webmasters/tools/mobile-friendly/?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Mobile-Friendly Test</a> shows blocked resources (often accompanied with a partially rendered image).</li> <li><a href="https://support.google.com/webmasters/answer/1061943" target="_blank">Allow Googlebot</a> to crawl the necessary files.</li> <li>Double-check that your page passes the Mobile-Friendly Test.</li> <li>Use <a href="https://support.google.com/webmasters/answer/6065812" target="_blank">Fetch as Google with Submit to Index</a> and <a href="https://support.google.com/webmasters/answer/6078399" target="_blank">submit your updated robots.txt to Google</a> to expedite the re-processing of the updated page (or just wait for Google to naturally re-crawl and index).</li> </ol> <div style="text-align: center;"> <span id="docs-internal-guid-74be34dd-dad4-36f3-1383-61e8ca870e67"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"><img alt="Screen Shot 2015-04-08 at 8.27.58 PM.png" height="337px;" src="https://lh4.googleusercontent.com/wBSGXuIza8Gl2NrZgOkwXX7DVjAI0maA8dNqxNz8o6O08Xi-ZMWWehnFElV46r1J8txW2uoLs-xTj9Fr045ctVVjNLD_3MMNTmasCzhDOY6DuJD-8ukSwaCF2XTpUjx_iHVHiII" style="-webkit-transform: rotate(0rad); border: 3px solid rgb(217, 217, 217); transform: rotate(0rad);" width="406px;" /></span></span></div> </div> <div style="text-align: center;"> <span style="vertical-align: baseline; white-space: pre-wrap;"><span style="font-family: Arial; font-size: x-small;"><i>The most common reason why a mobile page fails the Mobile-Friendly Test is that Googlebot for smartphones is blocked from crawling resources, like CSS and JavaScript, that are crucial for understanding the page’s mobile-friendliness. </i></span></span></div> <div style="text-align: center;"> <span style="font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"><span style="font-family: Arial;"><br /></span></span></div> <div style="text-align: center;"> <span style="font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"><span style="font-family: Arial;"><br /></span></span></div> <div style="text-align: center;"> <span id="docs-internal-guid-74be34dd-dac9-6db4-a684-b8e802117fb9"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span></span></div> <div> <div> To reiterate, we recommend that site owners allow Googlebot to crawl all resources for a page (including CSS, JavaScript, and images), so that we can properly render, index, and in this case, assess whether the page is mobile-friendly.</div> <div> <br /> <br /></div> <div> <i><b>7. What if I link to a site that’s not mobile-friendly?</b></i></div> <div> <br /></div> <div> Your page can still be “mobile-friendly” even if it links to a page that’s not mobile-friendly, such as a page designed for larger screens, like desktops. It’s not the best experience for mobile visitors to go from a mobile-friendly page to a desktop-only page, but hopefully as more sites become mobile-friendly, this will become less of a problem.</div> <div> <br /> <br /></div> <div> <i><b>8. Does Google give a stronger mobile-friendly ranking to pages using Responsive Web Design (which uses the same URL and the same HTML for the desktop and mobile versions) vs. hosting a separate mobile site (like www for desktop and m.example.com for mobile)?</b></i></div> <div> <br /></div> <div> No, mobile-friendliness is assessed the same, whether you use <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/configurations/responsive-design?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">responsive web design</a> (RWD), <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/configurations/separate-urls?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">separate mobile URLs</a>, or <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/configurations/dynamic-serving?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">dynamic serving</a> for your <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/overview/select-config?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">configuration</a>. If your site uses separate mobile URLs or dynamic serving, we recommend reviewing the Mobile SEO guide to make sure Google is properly crawling and indexing your mobile pages.<br /> <br /></div> <div> <br /></div> <div> <i><b>9. Will my site / page disappear on mobile search results if it's not mobile-friendly?</b></i></div> <div> <br /></div> <div> While the mobile-friendly change is important, we still use a variety of signals to rank search results. The intent of the search query is still a very strong signal -- so even if a page with high quality content is not mobile-friendly, it could still rank high if it has great content for the query.</div> </div> <div> <br /> <br /></div> <div> <h2 style="text-align: left;"> Specialized FAQs</h2> <div> <br /></div> <div> <i><b>10. What if my audience is desktop only? Then there’s no reason to have a mobile site, right?</b></i></div> <div> <br /></div> <div> Not exactly. Statistics show that more people are going “mobile only” -- either because they never had a desktop or because they won’t replace their existing desktop. Additionally, a non-mobile-friendly site may not see many mobile visitors precisely for that reason. </div> <div> <br /></div> <div> The mobile-friendly update will apply to mobile searches conducted across all sites, regardless of the site’s target audiences’ language, region, or proportion of mobile to desktop traffic.</div> <div> <br /> <br /></div> <div> <i><b>11. I have pages showing mobile usability errors because they embed a YouTube video. What can I do?</b></i></div> <div> <br /></div> <div> We suggest paying close attention to how the YouTube video is embedded. If you are using the “old-style” <object> embeds in the mobile page, convert to <iframe> embeds for broader compatibility. YouTube now uses the <a href="http://youtube-eng.blogspot.com/2015/01/youtube-now-defaults-to-html5_27.html" target="_blank">HTML5 player on the web by default</a>, so it’s mobile-friendly to embed videos using the <iframe> tags from the “share” feature on the watch page or from the <a href="https://developers.google.com/youtube/iframe_api_reference" target="_blank">YouTube iFrame API</a>. If you have a more complex integration, that should also be mobile-friendly, since it’ll instruct the device to use the device’s native support. </div> <div> <br /></div> <div> For Flash content from sites other than YouTube, check if there is an equivalent HTML5 embed tag or code snippet to avoid using proprietary plugins.</div> <div> <br /> <br /></div> <div> <i><b>12. Is there a clear standard for <a href="https://developers.google.com/speed/docs/insights/SizeTapTargetsAppropriately" target="_blank">sizing tap targets</a>?</b></i></div> <div> <br /></div> <div> Yes, we suggest a minimum of 7mm width/height for primary tap targets and a minimum margin of 5mm between secondary tap targets. The average width of an adult's finger pad is 10mm, and these dimensions can provide a usable interface while making good use of screen real estate.</div> <div> <br /> <br /></div> <div> <i><b>13. To become mobile-friendly quickly, we’re thinking of creating a very stripped down version of our site (separate mobile pages) until our new responsive site is complete. Do you foresee any problems with this?</b></i></div> <div> <br /></div> <div> First, keep in mind that we support <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/overview/select-config?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">three mobile configurations</a> and that your website doesn't have to be responsive to be mobile-friendly. In response to your question, please be cautious about creating a “stripped down” version of your site. While the page may be formatted for mobile, if it doesn’t allow your visitors to easily complete their common tasks or have an overall smooth workflow, it may become frustrating to your visitors and perhaps not worth the effort. Should a temporary mobile site be created, once the RWD is live, be sure to <a href="https://support.google.com/webmasters/answer/6033049?ref_topic=6033084&rd=1" target="_blank">move the site properly</a>. For example, update all links so they no longer reference the separate mobile URLs and 301 redirect mobile URLs to their corresponding RWD version.</div> </div> <div> <br /></div> <div> <h2 style="text-align: left;"> Recommendations</h2> <div> <br /></div> <div> If you’re totally new to building a mobile-friendly site, it’s not too late! Check out our <a href="https://developers.google.com/webmasters/mobile-sites/get-started/?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Getting Started guide</a> in the <a href="https://developers.google.com/webmasters/mobile-sites/?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Mobile-Friendly Websites documentation</a>.</div> </div> <div> <br /></div> <div style="text-align: center;"> <span id="docs-internal-guid-74be34dd-dad5-3fcc-fc0b-53be3634fb14"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"><img alt="Screen Shot 2015-04-08 at 8.53.30 PM.png" height="358px;" src="https://lh4.googleusercontent.com/aKKLszTF1d590fW0smgqSHzcoH_66S56xtasHTkoEesbBYLgf0UmG-bO_LPsP2MOkJ9xehUFbj11Sv5aa1At855XHpC2gB9MdX5LmkhLMCGh-tY8vDL3XDSz-0_VXG_rfhST6yk" style="-webkit-transform: rotate(0.00rad); border: 3px solid #d9d9d9; transform: rotate(0.00rad);" width="458px;" /></span></span></div> <div style="text-align: center;"> <div> <span style="font-family: Arial; vertical-align: baseline; white-space: pre-wrap;"><span style="font-size: x-small;"><i>Get started on your mobile site at https://developers.google.com/webmasters/mobile-sites/.</i></span></span></div> <br /></div> <br /> <div> If you already have a mobile site, investigate the <a href="https://www.google.com/webmasters/tools/mobile-usability?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Mobile Usability report in Webmaster Tools</a> to make sure that Google detects your site’s pages as mobile-friendly. </div> <div> <br /></div> <div> Still more questions? Please ask below or check out the <a href="https://productforums.google.com/forum/#!categories/webmasters/mobile" target="_blank">Mobile Websites section of the Webmaster Forum</a>. </div> <div> <br /></div> <div> <br /></div> <span class="byline-author">Written by <a href="https://plus.google.com/u/0/+MaileOhye/" target="_blank">Maile Ohye</a>, Developer Programs Tech Lead.</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> We’d like to share answers to your frequently asked questions. For background, in February, <a href="http://googlewebmastercentral.blogspot.com/2015/02/finding-more-mobile-friendly-search.html" target="_blank">we announced that the mobile-friendly update </a>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 in rankings in mobile search results.) To get us all on the same page, here are the most frequently asked questions:<br /> <br /> <h2 style="text-align: left;"> General FAQs</h2> <div> <br /></div> <i><b>1. Will desktop and/or tablet ranking also be affected by this change?</b></i><br /> <br /> <div style="text-align: left;"> No, this update has no effect on searches from tablets or desktops. It affects searches from mobile devices across all languages and locations.</div> <br /> <br /> <i><b>2. Is it a page-level or site-level mobile ranking boost? </b></i><br /> <br /> It’s a page-level change. For instance, if ten of your site’s pages are mobile-friendly, but the rest of your pages aren’t, only the ten mobile-friendly pages can be positively impacted.<br /> <br /> <br /> <i><b>3. How do I know if Google thinks a page on my site is mobile-friendly?</b></i><br /> <br /> Individual pages can be tested for “mobile-friendliness” using the <a href="https://www.google.com/webmasters/tools/mobile-friendly?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Mobile-Friendly Test</a>.<br /> <br /> <div style="text-align: center;"> <span id="docs-internal-guid-74be34dd-dad6-2acb-48eb-8578143d9fd5"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"><img alt="Screen Shot 2015-04-08 at 5.41.16 PM.png" height="308px;" src="https://lh6.googleusercontent.com/lgRhY4O6dT1kT69QvaiH3-TFB2u9eXdzYaM2pDfrwxHEkVDRr30Yb3owhFzv7nSjnOTUwBf4Sc7AtV5GlerBNv5DS-LFRlYUz60KaFScKKTOeO-2UHrd1Du3EKV-Q3RAAl6-JEw" style="-webkit-transform: rotate(0.00rad); border: 3px solid #d9d9d9; transform: rotate(0.00rad);" width="469px;" /></span></span></div> <div style="text-align: center;"> <span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span></div> <div style="text-align: center;"> <span style="font-family: Arial; font-size: x-small;"><span style="white-space: pre-wrap;"><i>Test individual URLs in real-time with the Mobile-Friendly Test.</i></span></span></div> <div style="text-align: center;"> <br /></div> <div style="text-align: left;"> To review site-level information on mobile-friendliness, check out the <a href="https://www.google.com/webmasters/tools/mobile-usability?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Mobile Usability report in Webmaster Tools</a>. This feature’s data is based on the last time we crawled and indexed your site’s pages.</div> <div style="text-align: left;"> <br /></div> <div style="text-align: center;"> <span id="docs-internal-guid-74be34dd-dad5-d729-9202-140fcde09d95"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"><img alt="Screen Shot 2015-04-08 at 5.39.24 PM.png" height="346px;" src="https://lh6.googleusercontent.com/egGhk2N72zSgS5Ckl4MFocJoOCOvdBLK0rgfEmDN3L0IwIubceKDuYdUPj_r-fBC9rrOu2BkyljJLwmH8-CPIBuGphgvL7vQmS9ZFSSqTpfTye1xUISA_pVrOU47F_mthPr2sVo" style="-webkit-transform: rotate(0.00rad); border: 3px solid #d9d9d9; transform: rotate(0.00rad);" width="475px;" /></span></span></div> <div style="text-align: center;"> <span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span></div> <div style="text-align: center;"> <span style="font-family: Arial; font-size: x-small;"><span style="white-space: pre-wrap;"><i>Mobile Usability in Webmaster Tools provides a snapshot of your entire site’s mobile-friendliness.</i></span></span></div> <div style="text-align: center;"> <br /></div> <div style="text-align: center;"> <span id="docs-internal-guid-74be34dd-dad2-a9fc-57e7-13e555429583"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span></span></div> <br /> <br /> <div> <i><b>4. Unfortunately, my mobile-friendly pages won’t be ready until after April 21st. How long before they can be considered mobile-friendly in ranking?</b></i></div> <div> <br /></div> <div> We determine whether a page is mobile-friendly every time it’s crawled and indexed -- you don’t have to wait for another update. Once a page is mobile-friendly, you can wait for <a href="http://googlewebmastercentral.blogspot.ch/2014/01/a-new-googlebot-user-agent-for-crawling.html" target="_blank">Googlebot for smartphones </a>to naturally (re-)crawl and index the page or you can expedite processing by using <a href="https://support.google.com/webmasters/answer/6065812" target="_blank">Fetch as Google with Submit to Index</a> in <a href="https://www.google.com/webmasters/tools?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Webmaster Tools</a>. For a large volume of URLs, consider submitting a <a href="https://support.google.com/webmasters/answer/156184" target="_blank">sitemap</a>. In the sitemap, if your mobile content uses pre-existing URLs (such as with <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/configurations/responsive-design?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Responsive Web Design</a> or <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/configurations/dynamic-serving?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">dynamic serving</a>), also include the <a href="http://www.sitemaps.org/protocol.html#lastmoddef" target="_blank">lastmod tag</a>.</div> <div> <br /> <br /></div> <div> <i><b>5. Since the mobile ranking change rolls out on April 21st, if I see no drop in traffic on April 22nd, does that mean that my site’s rankings aren't impacted?</b></i></div> <div> <br /></div> <div> You won't be able to definitively determine whether your site’s rankings are impacted by the mobile-friendly update by April 22nd. While we begin rolling out the mobile-friendly update on April 21st, it’ll be a week or so before it makes its way to all pages in the index. </div> <div> <br /> <br /></div> <div> <i><b>6. I have a great mobile site, but the Mobile-Friendly Test tells me that my pages aren't mobile-friendly. Why?</b></i></div> <div> <br /></div> <div> If a page is designed to work well on mobile devices, but it’s not passing the Mobile-Friendly Test, the most common reason is that Googlebot for smartphones is blocked from crawling resources, like CSS and JavaScript, that are critical for determining whether the page is legible and usable on a mobile device (i.e., whether it’s mobile-friendly). To remedy:</div> <div> <ol style="text-align: left;"> <li>Check if the <a href="https://www.google.com/webmasters/tools/mobile-friendly/?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Mobile-Friendly Test</a> shows blocked resources (often accompanied with a partially rendered image).</li> <li><a href="https://support.google.com/webmasters/answer/1061943" target="_blank">Allow Googlebot</a> to crawl the necessary files.</li> <li>Double-check that your page passes the Mobile-Friendly Test.</li> <li>Use <a href="https://support.google.com/webmasters/answer/6065812" target="_blank">Fetch as Google with Submit to Index</a> and <a href="https://support.google.com/webmasters/answer/6078399" target="_blank">submit your updated robots.txt to Google</a> to expedite the re-processing of the updated page (or just wait for Google to naturally re-crawl and index).</li> </ol> <div style="text-align: center;"> <span id="docs-internal-guid-74be34dd-dad4-36f3-1383-61e8ca870e67"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"><img alt="Screen Shot 2015-04-08 at 8.27.58 PM.png" height="337px;" src="https://lh4.googleusercontent.com/wBSGXuIza8Gl2NrZgOkwXX7DVjAI0maA8dNqxNz8o6O08Xi-ZMWWehnFElV46r1J8txW2uoLs-xTj9Fr045ctVVjNLD_3MMNTmasCzhDOY6DuJD-8ukSwaCF2XTpUjx_iHVHiII" style="-webkit-transform: rotate(0rad); border: 3px solid rgb(217, 217, 217); transform: rotate(0rad);" width="406px;" /></span></span></div> </div> <div style="text-align: center;"> <span style="vertical-align: baseline; white-space: pre-wrap;"><span style="font-family: Arial; font-size: x-small;"><i>The most common reason why a mobile page fails the Mobile-Friendly Test is that Googlebot for smartphones is blocked from crawling resources, like CSS and JavaScript, that are crucial for understanding the page’s mobile-friendliness. </i></span></span></div> <div style="text-align: center;"> <span style="font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"><span style="font-family: Arial;"><br /></span></span></div> <div style="text-align: center;"> <span style="font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"><span style="font-family: Arial;"><br /></span></span></div> <div style="text-align: center;"> <span id="docs-internal-guid-74be34dd-dac9-6db4-a684-b8e802117fb9"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span></span></div> <div> <div> To reiterate, we recommend that site owners allow Googlebot to crawl all resources for a page (including CSS, JavaScript, and images), so that we can properly render, index, and in this case, assess whether the page is mobile-friendly.</div> <div> <br /> <br /></div> <div> <i><b>7. What if I link to a site that’s not mobile-friendly?</b></i></div> <div> <br /></div> <div> Your page can still be “mobile-friendly” even if it links to a page that’s not mobile-friendly, such as a page designed for larger screens, like desktops. It’s not the best experience for mobile visitors to go from a mobile-friendly page to a desktop-only page, but hopefully as more sites become mobile-friendly, this will become less of a problem.</div> <div> <br /> <br /></div> <div> <i><b>8. Does Google give a stronger mobile-friendly ranking to pages using Responsive Web Design (which uses the same URL and the same HTML for the desktop and mobile versions) vs. hosting a separate mobile site (like www for desktop and m.example.com for mobile)?</b></i></div> <div> <br /></div> <div> No, mobile-friendliness is assessed the same, whether you use <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/configurations/responsive-design?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">responsive web design</a> (RWD), <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/configurations/separate-urls?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">separate mobile URLs</a>, or <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/configurations/dynamic-serving?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">dynamic serving</a> for your <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/overview/select-config?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">configuration</a>. If your site uses separate mobile URLs or dynamic serving, we recommend reviewing the Mobile SEO guide to make sure Google is properly crawling and indexing your mobile pages.<br /> <br /></div> <div> <br /></div> <div> <i><b>9. Will my site / page disappear on mobile search results if it's not mobile-friendly?</b></i></div> <div> <br /></div> <div> While the mobile-friendly change is important, we still use a variety of signals to rank search results. The intent of the search query is still a very strong signal -- so even if a page with high quality content is not mobile-friendly, it could still rank high if it has great content for the query.</div> </div> <div> <br /> <br /></div> <div> <h2 style="text-align: left;"> Specialized FAQs</h2> <div> <br /></div> <div> <i><b>10. What if my audience is desktop only? Then there’s no reason to have a mobile site, right?</b></i></div> <div> <br /></div> <div> Not exactly. Statistics show that more people are going “mobile only” -- either because they never had a desktop or because they won’t replace their existing desktop. Additionally, a non-mobile-friendly site may not see many mobile visitors precisely for that reason. </div> <div> <br /></div> <div> The mobile-friendly update will apply to mobile searches conducted across all sites, regardless of the site’s target audiences’ language, region, or proportion of mobile to desktop traffic.</div> <div> <br /> <br /></div> <div> <i><b>11. I have pages showing mobile usability errors because they embed a YouTube video. What can I do?</b></i></div> <div> <br /></div> <div> We suggest paying close attention to how the YouTube video is embedded. If you are using the “old-style” <object> embeds in the mobile page, convert to <iframe> embeds for broader compatibility. YouTube now uses the <a href="http://youtube-eng.blogspot.com/2015/01/youtube-now-defaults-to-html5_27.html" target="_blank">HTML5 player on the web by default</a>, so it’s mobile-friendly to embed videos using the <iframe> tags from the “share” feature on the watch page or from the <a href="https://developers.google.com/youtube/iframe_api_reference" target="_blank">YouTube iFrame API</a>. If you have a more complex integration, that should also be mobile-friendly, since it’ll instruct the device to use the device’s native support. </div> <div> <br /></div> <div> For Flash content from sites other than YouTube, check if there is an equivalent HTML5 embed tag or code snippet to avoid using proprietary plugins.</div> <div> <br /> <br /></div> <div> <i><b>12. Is there a clear standard for <a href="https://developers.google.com/speed/docs/insights/SizeTapTargetsAppropriately" target="_blank">sizing tap targets</a>?</b></i></div> <div> <br /></div> <div> Yes, we suggest a minimum of 7mm width/height for primary tap targets and a minimum margin of 5mm between secondary tap targets. The average width of an adult's finger pad is 10mm, and these dimensions can provide a usable interface while making good use of screen real estate.</div> <div> <br /> <br /></div> <div> <i><b>13. To become mobile-friendly quickly, we’re thinking of creating a very stripped down version of our site (separate mobile pages) until our new responsive site is complete. Do you foresee any problems with this?</b></i></div> <div> <br /></div> <div> First, keep in mind that we support <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/overview/select-config?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">three mobile configurations</a> and that your website doesn't have to be responsive to be mobile-friendly. In response to your question, please be cautious about creating a “stripped down” version of your site. While the page may be formatted for mobile, if it doesn’t allow your visitors to easily complete their common tasks or have an overall smooth workflow, it may become frustrating to your visitors and perhaps not worth the effort. Should a temporary mobile site be created, once the RWD is live, be sure to <a href="https://support.google.com/webmasters/answer/6033049?ref_topic=6033084&rd=1" target="_blank">move the site properly</a>. For example, update all links so they no longer reference the separate mobile URLs and 301 redirect mobile URLs to their corresponding RWD version.</div> </div> <div> <br /></div> <div> <h2 style="text-align: left;"> Recommendations</h2> <div> <br /></div> <div> If you’re totally new to building a mobile-friendly site, it’s not too late! Check out our <a href="https://developers.google.com/webmasters/mobile-sites/get-started/?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Getting Started guide</a> in the <a href="https://developers.google.com/webmasters/mobile-sites/?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Mobile-Friendly Websites documentation</a>.</div> </div> <div> <br /></div> <div style="text-align: center;"> <span id="docs-internal-guid-74be34dd-dad5-3fcc-fc0b-53be3634fb14"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"><img alt="Screen Shot 2015-04-08 at 8.53.30 PM.png" height="358px;" src="https://lh4.googleusercontent.com/aKKLszTF1d590fW0smgqSHzcoH_66S56xtasHTkoEesbBYLgf0UmG-bO_LPsP2MOkJ9xehUFbj11Sv5aa1At855XHpC2gB9MdX5LmkhLMCGh-tY8vDL3XDSz-0_VXG_rfhST6yk" style="-webkit-transform: rotate(0.00rad); border: 3px solid #d9d9d9; transform: rotate(0.00rad);" width="458px;" /></span></span></div> <div style="text-align: center;"> <div> <span style="font-family: Arial; vertical-align: baseline; white-space: pre-wrap;"><span style="font-size: x-small;"><i>Get started on your mobile site at https://developers.google.com/webmasters/mobile-sites/.</i></span></span></div> <br /></div> <br /> <div> If you already have a mobile site, investigate the <a href="https://www.google.com/webmasters/tools/mobile-usability?utm_source=wmc-blog&utm_medium=referral&utm_campaign=mobile-friendly" target="_blank">Mobile Usability report in Webmaster Tools</a> to make sure that Google detects your site’s pages as mobile-friendly. </div> <div> <br /></div> <div> Still more questions? Please ask below or check out the <a href="https://productforums.google.com/forum/#!categories/webmasters/mobile" target="_blank">Mobile Websites section of the Webmaster Forum</a>. </div> <div> <br /></div> <div> <br /></div> <span class="byline-author">Written by <a href="https://plus.google.com/u/0/+MaileOhye/" target="_blank">Maile Ohye</a>, Developer Programs Tech Lead.</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:FAQs about the April 21st mobile-friendly update &url=https://webmasters.googleblog.com/2015/04/faqs-april-21st-mobile-friendly.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2015/04/faqs-april-21st-mobile-friendly.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2015/04/faqs-april-21st-mobile-friendly.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/mobile?hl=en_US' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US' rel='tag'> mobile-friendly </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en_US' rel='tag'> webmaster community </a> </span> </div> </div> </div> <div class='blog-pager' id='blog-pager'> <a class='home-link' href='https://webmasters.googleblog.com/?hl=en_US'> <i class='material-icons'>  </i> </a> <i class='material-icons disabled'>  </i> <span id='blog-pager-older-link'> <a class='blog-pager-older-link' href='https://webmasters.googleblog.com/search/label/mobile-friendly?updated-max=2015-04-21T06:59:00-07:00&max-results=20&start=20&by-date=false&hl=en_US' id='Blog1_blog-pager-older-link' title='Older Posts'> <i class='material-icons'>  </i> </a> </span> </div> <div class='clear'></div> </div></div> </div> </div> <div class='col-right'> <div class='section' id='sidebar-top'><div class='widget HTML' data-version='1' id='HTML9'> <div class='widget-content'> <a href="https://www.google.com/webmasters/tools/mobile-friendly/?utm_source=wmc-blog&utm_medium=referral&utm_campaign=blog-nav"><img src="https://lh3.googleusercontent.com/-osGJupx0-HY/VQta1nmaAPI/AAAAAAAACfs/UdMPzubsXFk/w80-h1368-no/blog%2Bpromo.png" align="left" width="80" /></a> Hey! <a href="https://search.google.com/test/mobile-friendly">Check here if your site is mobile-friendly.</a> </div> <div class='clear'></div> </div><div class='widget HTML' data-version='1' id='HTML10'> <div class='widget-content'> <div class='searchBox'> <input type='text' title='Search This Blog' placeholder='Search blog ...' /> </div> </div> <div class='clear'></div> </div></div> <div id='aside'> <div class='section' id='sidebar'><div class='widget Label' data-version='1' id='Label1'> <div class='tab'> <img class='sidebar-icon' src='data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAYpJREFUeNrs2aFuwzAQBmAvKRkMKRjZA4QMDJaWFgyMjuzFRg37DIUlA3uFkoGQSaWzJU+tpri5O9+l/zSfdFJlpe59yTmyVedq1PjfcZMZ70NuQnaF8w8htyE/rABtpviXkLcK88c5HhLkMBfgVan43zfFBNGMjHVGT/s55KP2pAvidbGHd+nzKt1RKSLG3rKF1iPFv6UWiPke8i7kEqGdGsI1O+LYVdqJAjgirwkKYD0ytkJBUNbAMvX8V3q9PhUsYvU1sWD8SO/sQvx2ahxOiNoJCSBCoAHYCEQAC4EKICOQASQEOmAS8RcAFxFN5hiIiugpgC3wk9hQAHH/70EBHXUN7IER5EWMiBgo2+nzOKQv9SCAeEM/OQAkhE/ncccFICB87qzQMia5FsJfOui0zMnmRvipU1ormHQuxGTxUsAcCFLxJQBLBLn4UoAFglW8BkATwS5eC6CBEBWvCShBiIvXBkgQRcVbADiI4uKtABSESvGWgB9EzHt3+tNwyO0qa9SoIYtvAQYAqDJhaWWeMecAAAAASUVORK5CYII='/> <h2> Labels </h2> <i class='material-icons arrow'>  </i> </div> <div class='widget-content list-label-widget-content'> <ul> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/accessibility?hl=en_US'> accessibility </a> <span dir='ltr'> 10 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/advanced?hl=en_US'> advanced </a> <span dir='ltr'> 195 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/AMP?hl=en_US'> AMP </a> <span dir='ltr'> 13 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Android?hl=en_US'> Android </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/API?hl=en_US'> API </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/apps?hl=en_US'> apps </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/autocomplete?hl=en_US'> autocomplete </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/beginner?hl=en_US'> beginner </a> <span dir='ltr'> 173 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/CAPTCHA?hl=en_US'> CAPTCHA </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Chrome?hl=en_US'> Chrome </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/cms?hl=en_US'> cms </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en_US'> crawling and indexing </a> <span dir='ltr'> 158 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/encryption?hl=en_US'> encryption </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/events?hl=en_US'> events </a> <span dir='ltr'> 51 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=en_US'> feedback and communication </a> <span dir='ltr'> 83 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/forums?hl=en_US'> forums </a> <span dir='ltr'> 5 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/general%20tips?hl=en_US'> general tips </a> <span dir='ltr'> 90 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/geotargeting?hl=en_US'> geotargeting </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20Assistant?hl=en_US'> Google Assistant </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20I%2FO?hl=en_US'> Google I/O </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20Images?hl=en_US'> Google Images </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20News?hl=en_US'> Google News </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hacked%20sites?hl=en_US'> hacked sites </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hangout?hl=en_US'> hangout </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hreflang?hl=en_US'> hreflang </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/https?hl=en_US'> https </a> <span dir='ltr'> 5 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/images?hl=en_US'> images </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/intermediate?hl=en_US'> intermediate </a> <span dir='ltr'> 205 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/interstitials?hl=en_US'> interstitials </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/javascript?hl=en_US'> javascript </a> <span dir='ltr'> 8 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/job%20search?hl=en_US'> job search </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/localization?hl=en_US'> localization </a> <span dir='ltr'> 21 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/malware?hl=en_US'> malware </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/mobile?hl=en_US'> mobile </a> <span dir='ltr'> 63 </span> </li> <li> <span dir='ltr'> mobile-friendly </span> <span dir='ltr'> 14 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/nohacked?hl=en_US'> nohacked </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/performance?hl=en_US'> performance </a> <span dir='ltr'> 17 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/product%20expert?hl=en_US'> product expert </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/product%20experts?hl=en_US'> product experts </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/products%20and%20services?hl=en_US'> products and services </a> <span dir='ltr'> 63 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/questions?hl=en_US'> questions </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/ranking?hl=en_US'> ranking </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/recipes?hl=en_US'> recipes </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rendering?hl=en_US'> rendering </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Responsive%20Web%20Design?hl=en_US'> Responsive Web Design </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rich%20cards?hl=en_US'> rich cards </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rich%20results?hl=en_US'> rich results </a> <span dir='ltr'> 10 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US'> search console </a> <span dir='ltr'> 35 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20for%20beginners?hl=en_US'> search for beginners </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20queries?hl=en_US'> search queries </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en_US'> search results </a> <span dir='ltr'> 140 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/security?hl=en_US'> security </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/seo?hl=en_US'> seo </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/sitemaps?hl=en_US'> sitemaps </a> <span dir='ltr'> 46 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/speed?hl=en_US'> speed </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=en_US'> structured data </a> <span dir='ltr'> 33 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/summit?hl=en_US'> summit </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/TLDs?hl=en_US'> TLDs </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/url%20removals?hl=en_US'> url removals </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/UX?hl=en_US'> UX </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/verification?hl=en_US'> verification </a> <span dir='ltr'> 8 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/video?hl=en_US'> video </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en_US'> webmaster community </a> <span dir='ltr'> 24 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20forum?hl=en_US'> webmaster forum </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines?hl=en_US'> webmaster guidelines </a> <span dir='ltr'> 57 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US'> webmaster tools </a> <span dir='ltr'> 177 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmasters?hl=en_US'> webmasters </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/youtube%20channel?hl=en_US'> youtube channel </a> <span dir='ltr'> 6 </span> </li> </ul> <div class='clear'></div> </div> </div><div class='widget BlogArchive' data-version='1' id='BlogArchive1'> <div class='tab'> <i class='material-icons icon'>  </i> <h2> Archive </h2> <i class='material-icons arrow'>  </i> </div> <div class='widget-content'> <div id='ArchiveList'> <div id='BlogArchive1_ArchiveList'> <ul class='hierarchy'> <li class='archivedate expanded'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy toggle-open'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/?hl=en_US'> 2020 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate expanded'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/?hl=en_US'> 2019 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/?hl=en_US'> 2018 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/?hl=en_US'> 2017 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/?hl=en_US'> 2016 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/?hl=en_US'> 2015 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/?hl=en_US'> 2014 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/?hl=en_US'> 2013 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/?hl=en_US'> 2012 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/?hl=en_US'> 2011 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/?hl=en_US'> 2010 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/?hl=en_US'> 2009 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/?hl=en_US'> 2008 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/?hl=en_US'> 2007 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/?hl=en_US'> 2006 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> </div> </div> <div class='clear'></div> </div> </div><div class='widget HTML' data-version='1' id='HTML6'> <div class='widget-content'> <a href="https://googlewebmastercentral.blogspot.com/atom.xml"> <img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAihJREFUeNrsWa9Pw0AU7viRMDFRBAkzJDMIBIhJJhCzk7NILIqMv4AEhdz+BCY3OYssAlGBoAJREpZwAlHEBO8lr8nSvNeVbu1dyX3JlzTrXfa+u/e9d7c5joWFhYVO1Fa8PwH2gK6m+BRwAvSlAdsrgr8E1jUuMH73GTAEzrkBWymTewZlihhLmgDXIAFuHgGVQOUF7OSYM1p6PgTuA1vAZlUEvAnPdapcMY0VICECekQ0XRfYrqoHsAGNgXfAoMomRiFDEhOZkkL3S88hMaB2LwXp0bj+ps2edpToZpjfoIDQtBeU+xjoDzP2G/gCPKZ5f8WsCAFJoJgOCcFdWSTeL9YQMSvTA1h9BkI5jaiXhLpSCL/8mVZY0UpyJ9ZdOkniu1dmJ96BpzQu9w6s28gcOq9j6pwLdR8/36NK5CQKwJSMrb2MhhSglBpt4UjsrdsnNu0B3J0HCozbCc4TjyY2srEgos/4RQljCzNxl4ireQD8FOq+T+W0mTB2g7njhlR+Sy2jsXFvU658U8YTbeaGpdIu7mWkEAq5ZtIjIhFZdtfX7QHckSvB2B6zC3VdAkZk0kAQwaXTk/CzTXK3wjIExCs6ZJpTnE4uY1KV+KzFzA3KTiFPENHJkOPcsfpLhwe4btoSuvUqAR+6TOxlCE6ZfKUsJLgsqGW8OpqAGx2X+sLxrwUog+JUeQRMDBIwyXOcnlPtPnL0/UsT/8LnOxYWFhZG4leAAQAAQHEaYuzHbAAAAABJRU5ErkJggg==" class="sidebar-icon" /> <h2>Feed</h2> </a> </div> <div class='clear'></div> </div></div> <div class='section' id='sidebar-bottom'><div class='widget HTML' data-version='1' id='HTML5'> <div class='widget-content'> <div class='followgooglewrapper'> <script src="https://apis.google.com/js/plusone.js"></script></div> <div class="g-ytsubscribe class='followgooglewrapper'" data-channel="GoogleWebmasterHelp" data-layout="full"></div> <div class="share followgooglewrapper"> <button data-href="https://twitter.com/intent/follow?original_referer=https://googlewebmastercentral.blogspot.com/&screen_name=googlewmc" onclick='sharingPopup(this);' id='twitter-share'><span class="twitter-follow">Follow @googlewmc</span></button> <script> function sharingPopup (button) { var url = button.getAttribute("data-href"); window.open( url,'popUpWindow','height=500,width=500,left=10,top=10,resizable=yes,scrollbars=yes,toolbar=yes,menubar=no,location=no,directories=no,status=yes'); } </script> </div> </div> <div class='clear'></div> </div><div class='widget HTML' data-version='1' id='HTML1'> <div class='widget-content'> Give us feedback in our <a href="https://support.google.com/webmasters/go/community">Product Forums</a>. </div> <div class='clear'></div> </div><div class='widget HTML' data-version='1' id='HTML8'> <h2 class='title'> Subscribe via email </h2> <div class='widget-content'> <form #nsubmit="window.open('https://www.feedburner.com/fb/a/emailverifySubmit?feedId=1092589', 'popupwindow', 'scrollbars=yes,width=550,height=520');return true" action="https://www.feedburner.com/fb/a/emailverify" style="border:1px solid #ccc;padding:3px;text-align:center;" target="popupwindow" method="post"><p>Enter your email address:</p><p><input style="width:140px" name="email" type="text"/></p><input value="https://feeds.feedburner.com/~e?ffid=1092589" name="url" type="hidden"/><input value="Official Google Webmaster Central Blog" name="title" type="hidden"/><input value="en_US" name="loc" type="hidden"/><input value="Subscribe" type="submit"/><p>Delivered by <a href="https://www.feedburner.com" target="_blank">FeedBurner</a></p></form> </div> <div class='clear'></div> </div></div> </div> </div> <div style='clear:both;'></div> </div>  <div class='google-footer-outer loading'> <div id='google-footer'> <a href='//www.google.com/'> <img class='google-logo-dark' height='36' src='data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAALgAAABICAYAAABFoT/eAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAACLVJREFUeNrsXd+L20YQ3vOprdLqiMXFXE2qB7dcwEcTSB7ykIc+9A/PQx/yEMq1TWhNuYIpJriNr7XpmZ5IxFEvmW2EKs3Ornb1w50PxIFP0kiz387OzM6uhGAwGAxGP3Ho+f7x7ri1O7LdccPqZjSNA4dEHsLfaHcEFedJom93x9Xu2OyOFTcBo6sED3fHZHeMEELrkAHJF0B8Rr+gDFsZ5n0luLTQ95AXs4W06D/tjpR50xtM4CjD0y48YGB4rnyZxNOzyA7zBHr+nLnDaJLg0mo/ALekCasg3Z4XbM0ZdTEgnDPeHY8bIne+Qz2GvwyGNwsuyT218KWvIIBMcwGpLiipcolecjMxfBDchNyS1EvxLiOSIecp31q6IJ/C3yrIrMqMm4jhg+AxkdwbIO3aUO4KjqqMjCT3uaazMBhWBJfuxH3CtRfiXf66DhSRZWbmlMnNaILgZxrXJQO/eO3wORZwvwm4JUxuhheCjzVBYAbW1ces45YDSoZrFNOEE835M8FT6oyeEnws8Fz3QnBxFKPHBMem4GU+m6fPGb0leCTwWcM5B36MPgeZI01gudyDdw3hPeXfo8L/rmCUWnuMMdqUL2WqWeRbhf+twfVsO7YagZGNC79fw7OthEVtkiJ4jJzTd3KPwf3CRqhhiTu23AP5sl0/0xiwISQXpNwLIJK87mHF+U8ddzzdmgKlGzlPYjyxGJQouIhNT4k9AqWEFkqfguIvagTWbcq3KW1WE3xS3m8NtA9WS451xofwjKT5kkDoK/b6mDk5FfXr1lWDL4BofZEv2/SRsK/EHGlGdBdu8QNRb8HMCFwt7Yy3DDI/QP7fx5z3VLhdlJEIs4rKNuXXJXdxZPdB7kfCzWqwCO4V1LHgLjInX3tQ1KzCR52Cz+vDj1dydeRuS74rcvs2Pi6fT5H8OaaUQPQPYcWwRSGXyhhscn5dpAnEFMkuEZetbfkTAnlSuH4DxisE+aMGeJAQ3lFl7C4LJE6QWCaCd583ORQ1jYAwjFctal7nOs2ZZvicwvlZx+RHGrcoAwKUVX8uwcc/9TT65INeDOr5shL9LDRB6QTeIy3zwfdh3WOi6axLCEhSjXU7F3h6LqggUtvyJxpynwu8tDkD98fXApOxRj8zoZ9MnGveYVIVZKaGrkBXCY65BCYNN9NkjpKOyQ81Q79JgdxS+Jn3SDTEXRI7SWzaiSTB32oI3nU3BvMfM0urhOVYgwKhuiAfc4tM07wXwm1ZRoQYSl2NUwiu01fEAHVcpixd745FvVz4dzUUc0o8rwoLy8ZSwU6CyFx1RP5II9+1bFPEFs9HWbNLiimDXE+vCm7u1CS47cofzD3aEhVY57mxRo5zlqdt+RFC1JUH2S7bcVXg4liTMakaBZZVxiTICRoivcn1sEUBlk24JmaC6kxUbYmWoqvyfck2xZGGnDFYa9MMzkYQ1ijkCX6qidybrgePiQ0QIQqoi6qRLeqQfIoRsEHaQJLBdHOnLGetSdm/IPcymJuS1PAnbQPH0MOw/39C1vL11DiLOqIsbDI8QcHvGiLnySi2qUXBicaqUSxN5LEB0g7Jt3ENXJLPJ5S1tnaZBoWbpRqrmjRE7qHmpSmNHdQcYrEUadoh+TbBnc9ri7iycI1kzPeNcLDIvbiqXpez9Tmdq6zGREPuzECBoxrPMiI2WtvyNwhJba2wy3JZ6ky5dD1lSvmZS3e4SPA1wcf1VTFHKX+cGwZzdUYcqpvUtvwrD/InDttVlyZeAKlNN5MKbAiurHhKIPlUuJvlTCCiDjSKSCsUmCFWbGLZwCESfK07JB8LvMYWVtw0D00JEHV8Mq2HkqPbE0oHLvvK2g0o8ETg+4cfwTlZDT9JDoWygu4uQQE/ivIvtcnfPkaCqhiupz7jWOAzqL/vjtcdkv9G4MVMt+EaylfuImiPAXEUjRF3pjjaHiPPZ6If9TGGAO4ZY0am6jOCb+DQ+ZCqLkIpOIPrdNfIjnFPY6nyFut7TS/fanrziOBOKMupKw94WaLMtuVnSFt9CPrWWdJE6PeltCX432DEBoh+5Dv8RRhdis8YAv9uyq4/JAwtlEApgBe9Cw9xDD3tdk4Jn0MDfiHwPHcRPxBePCMER3GuIx7kGlv9fkZ4V9lolx2Uv4X7hEj7qJ3LDoAMGbTRMRibu4L2xQ8bgt8AyU+Q+x7nYrvDnH4iuO5LxKsYwPVbkPMvKF9Zky9wXzRfVWizi62r9X5VHf55h+WHhDjGBZ4WRhyTr6z5SlCoLMxLSpBZFsQ9F80uQFbF/6aFWi+Ev51vzzsuX+msyzuQXXjUz8zEBy+zpq9yweXAoxJW4JbYrDS6gYDqGHxPl+TKeiBfxj9/EBIElPYeOA4y8/qRQfknjvSzgRgtq0Pw/M1eQeMdOSb2Bnrhr6Led+1vcp2x7oTFHMnedFW+Ivlty062BUt74oHgSj+vHepnhunn0JJAMtBZgDI/qmGtMujRv8DDpo47zBJ8UtPOuAR/7rKn8t9AJ0tBdmBAmJ/Fu71yxp4I3qh+DhyRqbi5Y1ShVPlSb8X7bRNcfgZFl+WRGYo7uecrWq1r8X5bhmzP5OdlDwsGRm1suSxkg5rYm7ConyGQ3Zl+DgSD8V/kPwrWBMG9YcBtyShBnTLdTiHgttw7qAW7cqh/ZnmPKr/6ignOaKsdyxbsToT5UkPsW00bJjijDXficcX/JsLs6w2BwGtherdckH3w/kNXRPVI0OqJQoHX42/66IMfMj/2huRjxIidgKV/W0JS+bsstDoTeAHcrI8E5zTh/sDkqxL5rZup55/3USlswfcHf4IrQplVDgW9XFlOqnwr6pVPMMEZTuC60EttvdzbLbaZ4PsFVa3nohhO+vW+yn/ZB2fUhpysmQrzBcTSai9EszuZMcEZ1lCFVrp9zGXhm69iLyY4oxFIa178lPe12I/P2DAYDAaDwWAwGAwGg8FgMBgMBoPBYDD2Cf8IMADDRGoQTe+E9AAAAABJRU5ErkJggg==' style='margin-top: -16px;' width='92'/> </a> <ul> <li> <a href='//www.google.com/'> Google </a> </li> <li> <a href='//www.google.com/policies/privacy/'> Privacy </a> </li> <li> <a href='//www.google.com/policies/terms/'> Terms </a> </li> </ul> </div> </div> <script type='text/javascript'> //<![CDATA[ // Social sharing popups. var postEl = document.getElementsByClassName('social-wrapper'); var postCount = postEl.length; for(i=0; i<postCount;i++){ postEl[i].addEventListener("click", function(event){ var postUrl = this.getAttribute("data-href"); window.open( postUrl,'popUpWindow','height=500,width=500,left=10,top=10,resizable=yes,scrollbars=yes,toolbar=yes,menubar=no,location=no,directories=no,status=yes'); });} //]]> </script> <script type='text/javascript'> //<![CDATA[ var BreakpointHandler = function() { this.initted = false; this.isHomePage = false; this.isMobile = false; }; BreakpointHandler.prototype.finalizeSummary = function(summaryHtml, lastNode) { // Use $.trim for IE8 compatibility summaryHtml = $.trim(summaryHtml).replace(/(<br>|\s)+$/,''); if (lastNode.nodeType == 3) { var lastChar = summaryHtml.slice(-1); if (!lastChar.match(/[.”"?]/)) { if (!lastChar.match(/[A-Za-z]/)) { summaryHtml = summaryHtml.slice(0, -1); } summaryHtml += ' ...'; } } else if (lastNode.nodeType == 1 && (lastNode.nodeName == 'I' || lastNode.nodeName == 'A')) { summaryHtml += ' ...'; } return summaryHtml; }; BreakpointHandler.prototype.generateSummaryFromContent = function(content, numWords) { var seenWords = 0; var summaryHtml = ''; for (var i=0; i < content.childNodes.length; i++) { var node = content.childNodes[i]; var nodeText; if (node.nodeType == 1) { if (node.hasAttribute('data-about-pullquote')) { continue; } nodeText = node.textContent; if (nodeText === undefined) { // innerText for IE8 nodeText = node.innerText; } if (node.nodeName == 'DIV' || node.nodeName == 'B') { // Don't end early if we haven't seen enough words. if (seenWords < 10) { continue; } if (i > 0) { summaryHtml = this.finalizeSummary(summaryHtml, content.childNodes[i-1]); } break; } summaryHtml += node.outerHTML; } else if (node.nodeType == 3) { nodeText = node.nodeValue; summaryHtml += nodeText + ' '; } var words = nodeText.match(/\S+\s*/g); if (!words) { continue; } var remain = numWords - seenWords; if (words.length >= remain) { summaryHtml = this.finalizeSummary(summaryHtml, node); break; } seenWords += words.length; } return summaryHtml; }; BreakpointHandler.prototype.detect = function() { var match, pl = /\+/g, search = /([^&=]+)=?([^&]*)/g, decode = function (s) { return decodeURIComponent(s.replace(pl, " ")); }, query = window.location.search.substring(1); var urlParams = {}; while (match = search.exec(query)) urlParams[decode(match[1])] = decode(match[2]); this.isListPage = $('html').hasClass('list-page'); this.isMobile = urlParams['m'] === '1'; this.isHomePage = window.location.pathname == '/'; }; BreakpointHandler.prototype.initContent = function() { var self = this; $('.post').each(function(index) { var body = $(this).children('.post-body')[0]; var content = $(body).children('.post-content')[0]; $(content).addClass('post-original'); var data = $(content).children('script').html(); data = self.rewriteForSSL(data); // If exists, extract specified editor's preview. var match = data.match(/([\s\S]+?)<div data-is-preview.+?>([\s\S]+)<\/div>/m); if (match) { data = match[1]; } // Prevent big images from loading when they aren't needed. // This must be done as a pre-injection step, since image loading can't be // canceled once embedded into the DOM. if (self.isListPage && self.isMobile) { data = data.replace(/<(img|iframe) .+?>/g, ''); } // Insert template to be rendered as nodes. content.innerHTML = data; if (self.isListPage) { var summary = document.createElement('div'); $(summary).addClass('post-content'); $(summary).addClass('post-summary'); body.insertBefore(summary, content); if (match) { // Use provided summary. summary.innerHTML = match[2]; } else { // Generate a summary. // Summary generation relies on DOM, so it must occur after content is // inserted into the page. summary.innerHTML = self.generateSummaryFromContent(content, 30); } // Add read more link to summary. var titleAnchor = $(this).find('.title a')[0]; var link = titleAnchor.cloneNode(true); link.innerHTML = 'Read More'; $(link).addClass('read-more'); summary.appendChild(link); } }); // Firefox does not allow for proper styling of BR. if (navigator.userAgent.indexOf('Firefox') > -1) { $('.post-content br').replaceWith('<span class="space"></span>'); } $('.loading').removeClass('loading'); }; BreakpointHandler.prototype.process = function() { if (!this.initted) { var makeInsecureImageRegex = function(hosts) { var whitelist = hosts.join('|').replace(/\./g,'\\.'); // Normal image tags, plus input images (yes, this is possible!) return new RegExp('(<(img|input)[^>]+?src=("|\'))http:\/\/(' + whitelist +')', 'g'); }; this.sslImageRegex = makeInsecureImageRegex(BreakpointHandler.KNOWN_HTTPS_HOSTS); this.sslImageCurrentDomainRegex = makeInsecureImageRegex([window.location.hostname]); this.detect(); this.initContent(); this.initted = true; } }; BreakpointHandler.KNOWN_HTTPS_HOSTS = [ "www.google.org", "www.google.com", "services.google.com", "blogger.com", "draft.blogger.com", "www.blogger.com", "photos1.blogger.com", "photos2.blogger.com", "photos3.blogger.com", "blogblog.com", "img1.blogblog.com", "img2.blogblog.com", "www.blogblog.com", "www1.blogblog.com", "www2.blogblog.com", "0.bp.blogspot.com", "1.bp.blogspot.com", "2.bp.blogspot.com", "3.bp.blogspot.com", "4.bp.blogspot.com", "lh3.googleusercontent.com", "lh4.googleusercontent.com", "lh5.googleusercontent.com", "lh6.googleusercontent.com", "themes.googleusercontent.com", ]; BreakpointHandler.prototype.rewriteForSSL = function(html) { // Handle HTTP -> HTTPS source replacement of images, movies, and other embedded content. return html.replace(this.sslImageRegex, '$1https://$4') .replace(this.sslImageCurrentDomainRegex, '$1//$4') .replace(/(<(embed|iframe)[^>]+?src=("|'))http:\/\/([^"']*?(youtube|picasaweb\.google)\.com)/g, '$1https://$4') // Slideshow SWF takes a image host, so we need to rewrite that parameter. .replace(/(<embed[^>]+?feed=http(?=[^s]))/g, '$1s'); }; $(document).ready(function() { var handler = new BreakpointHandler(); handler.process(); // Top-level navigation. $(".BlogArchive .tab").click(function(ev) { ev.preventDefault(); $(this).parent().toggleClass('active'); $(this).siblings().slideToggle(300); }); $(".Label .tab").click(function(ev) { ev.preventDefault(); $(this).parent().toggleClass('active'); $(this).siblings().slideToggle(300); }); // Blog archive year expansion. $('.BlogArchive .intervalToggle').click(function(ev) { ev.preventDefault(); if ($(this).parent().hasClass('collapsed')) { $(this).parent().removeClass('collapsed'); $(this).parent().addClass('expanded'); } else { $(this).parent().removeClass('expanded'); $(this).parent().addClass('collapsed'); } }); // Reverse order of months. $('.BlogArchive .intervalToggle + div').each(function(_, items) { var year = $(this); year.children().each(function(_, month) { year.prepend(month); }); }); // Set anchors to open in new tab. $('.post-content img').parent().each(function(_, node) { if (node.nodeName == 'A') { $(this).attr('target', '_blank'); } }); // Process search requests. $('.searchBox input').on("keypress", function(ev) { if (ev.which == 13) { window.location.href = 'https://www.google.com/search?q=site%3A' + window.location.hostname + '%20' + encodeURIComponent ($(this).val()); } }); }); //]]> </script> <script type="text/javascript" src="https://www.blogger.com/static/v1/widgets/984859869-widgets.js"></script> <script type='text/javascript'> window['__wavt'] = 'AOuZoY7YGAXyDWANCRt-Ax-Yt3YAF80vuQ:1732431278398';_WidgetManager._Init('//www.blogger.com/rearrange?blogID\x3d32069983','//webmasters.googleblog.com/search/label/mobile-friendly?hl\x3den_US','32069983'); _WidgetManager._SetDataContext([{'name': 'blog', 'data': {'blogId': '32069983', 'title': 'Official Google Webmaster Central Blog', 'url': 'https://webmasters.googleblog.com/search/label/mobile-friendly?hl\x3den_US', 'canonicalUrl': 'https://webmasters.googleblog.com/search/label/mobile-friendly', 'homepageUrl': 'https://webmasters.googleblog.com/?hl\x3den_US', 'searchUrl': 'https://webmasters.googleblog.com/search', 'canonicalHomepageUrl': 'https://webmasters.googleblog.com/', 'blogspotFaviconUrl': 'https://webmasters.googleblog.com/favicon.ico', 'bloggerUrl': 'https://www.blogger.com', 'hasCustomDomain': true, 'httpsEnabled': true, 'enabledCommentProfileImages': false, 'gPlusViewType': 'FILTERED_POSTMOD', 'adultContent': false, 'analyticsAccountNumber': 'UA-18009-4', 'encoding': 'UTF-8', 'locale': 'en-US', 'localeUnderscoreDelimited': 'en', 'languageDirection': 'ltr', 'isPrivate': false, 'isMobile': false, 'isMobileRequest': false, 'mobileClass': '', 'isPrivateBlog': false, 'isDynamicViewsAvailable': true, 'feedLinks': '\x3clink rel\x3d\x22alternate\x22 type\x3d\x22application/atom+xml\x22 title\x3d\x22Official Google Webmaster Central Blog - Atom\x22 href\x3d\x22https://webmasters.googleblog.com/feeds/posts/default\x22 /\x3e\n\x3clink rel\x3d\x22alternate\x22 type\x3d\x22application/rss+xml\x22 title\x3d\x22Official Google Webmaster Central Blog - RSS\x22 href\x3d\x22https://webmasters.googleblog.com/feeds/posts/default?alt\x3drss\x22 /\x3e\n\x3clink rel\x3d\x22service.post\x22 type\x3d\x22application/atom+xml\x22 title\x3d\x22Official Google Webmaster Central Blog - Atom\x22 href\x3d\x22https://www.blogger.com/feeds/32069983/posts/default\x22 /\x3e\n', 'meTag': '', 'adsenseHostId': 'ca-host-pub-1556223355139109', 'adsenseHasAds': false, 'adsenseAutoAds': false, 'boqCommentIframeForm': true, 'loginRedirectParam': '', 'view': '', 'dynamicViewsCommentsSrc': '//www.blogblog.com/dynamicviews/4224c15c4e7c9321/js/comments.js', 'dynamicViewsScriptSrc': '//www.blogblog.com/dynamicviews/d78375fb222d99b3', 'plusOneApiSrc': 'https://apis.google.com/js/platform.js', 'disableGComments': true, 'interstitialAccepted': false, 'sharing': {'platforms': [{'name': 'Get link', 'key': 'link', 'shareMessage': 'Get link', 'target': ''}, {'name': 'Facebook', 'key': 'facebook', 'shareMessage': 'Share to Facebook', 'target': 'facebook'}, {'name': 'BlogThis!', 'key': 'blogThis', 'shareMessage': 'BlogThis!', 'target': 'blog'}, {'name': 'X', 'key': 'twitter', 'shareMessage': 'Share to X', 'target': 'twitter'}, {'name': 'Pinterest', 'key': 'pinterest', 'shareMessage': 'Share to Pinterest', 'target': 'pinterest'}, {'name': 'Email', 'key': 'email', 'shareMessage': 'Email', 'target': 'email'}], 'disableGooglePlus': true, 'googlePlusShareButtonWidth': 0, 'googlePlusBootstrap': '\x3cscript type\x3d\x22text/javascript\x22\x3ewindow.___gcfg \x3d {\x27lang\x27: \x27en\x27};\x3c/script\x3e'}, 'hasCustomJumpLinkMessage': false, 'jumpLinkMessage': 'Read more', 'pageType': 'index', 'searchLabel': 'mobile-friendly', 'pageName': 'mobile-friendly', 'pageTitle': 'Official Google Webmaster Central Blog: mobile-friendly', 'metaDescription': 'Official news on crawling and indexing sites for the Google index'}}, {'name': 'features', 'data': {}}, {'name': 'messages', 'data': {'edit': 'Edit', 'linkCopiedToClipboard': 'Link copied to clipboard!', 'ok': 'Ok', 'postLink': 'Post Link'}}, {'name': 'template', 'data': {'name': 'custom', 'localizedName': 'Custom', 'isResponsive': false, 'isAlternateRendering': false, 'isCustom': true}}, {'name': 'view', 'data': {'classic': {'name': 'classic', 'url': '?view\x3dclassic'}, 'flipcard': {'name': 'flipcard', 'url': '?view\x3dflipcard'}, 'magazine': {'name': 'magazine', 'url': '?view\x3dmagazine'}, 'mosaic': {'name': 'mosaic', 'url': '?view\x3dmosaic'}, 'sidebar': {'name': 'sidebar', 'url': '?view\x3dsidebar'}, 'snapshot': {'name': 'snapshot', 'url': '?view\x3dsnapshot'}, 'timeslide': {'name': 'timeslide', 'url': '?view\x3dtimeslide'}, 'isMobile': false, 'title': 'Official Google Webmaster Central Blog', 'description': 'Official news on crawling and indexing sites for the Google index', 'url': 'https://webmasters.googleblog.com/search/label/mobile-friendly?hl\x3den_US', 'type': 'feed', 'isSingleItem': false, 'isMultipleItems': true, 'isError': false, 'isPage': false, 'isPost': false, 'isHomepage': false, 'isArchive': false, 'isSearch': true, 'isLabelSearch': true, 'search': {'label': 'mobile-friendly', 'resultsMessage': 'Showing posts with the label mobile-friendly', 'resultsMessageHtml': 'Showing posts with the label \x3cspan class\x3d\x27search-label\x27\x3emobile-friendly\x3c/span\x3e'}}}]); _WidgetManager._RegisterWidget('_HeaderView', new _WidgetInfo('Header1', 'header', document.getElementById('Header1'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_BlogView', new _WidgetInfo('Blog1', 'main', document.getElementById('Blog1'), {'cmtInteractionsEnabled': false, 'navMessage': 'Showing posts with label \x3cb\x3emobile-friendly\x3c/b\x3e. \x3ca href\x3d\x22https://webmasters.googleblog.com/\x22\x3eShow all posts\x3c/a\x3e'}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML9', 'sidebar-top', document.getElementById('HTML9'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML10', 'sidebar-top', document.getElementById('HTML10'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_LabelView', new _WidgetInfo('Label1', 'sidebar', document.getElementById('Label1'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_BlogArchiveView', new _WidgetInfo('BlogArchive1', 'sidebar', document.getElementById('BlogArchive1'), {'languageDirection': 'ltr', 'loadingMessage': 'Loading\x26hellip;'}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML6', 'sidebar', document.getElementById('HTML6'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML5', 'sidebar-bottom', document.getElementById('HTML5'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML1', 'sidebar-bottom', document.getElementById('HTML1'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML8', 'sidebar-bottom', document.getElementById('HTML8'), {}, 'displayModeFull')); </script> </body> </html>