CINXE.COM

<!DOCTYPE html> <html class='v2 list-page' dir='ltr' itemscope='' itemtype='http://schema.org/Blog' lang='en' 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: 2016 </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/2016/' 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/2016/' 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/2016/' 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/'> <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='7970184783064897090' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/12/enhancing-property-sets-to-cover-more.html' itemprop='url' title='Enhancing property sets to cover more reports in Search Console'> Enhancing property sets to cover more reports in Search Console </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Monday, December 12, 2016 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p>Since initially <a href="https://webmasters.googleblog.com/2016/05/tie-your-sites-together-with-property.html">announcing property sets</a> earlier this year, one of the most popular requests has been to expand this functionality to more sections of Search Console. Thanks to your feedback, we're now expanding property sets to more features!</p> <p><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgSHhtp0MfOxSjgKvUvyllVOScGwpB13Vjqx1oP1qdSIO5NBTYFm5hQaVasBqCidtu3rf27cvAAIEl4i7BKY6xAU0tplaSFLhOgu-UWP1MNm3vHHvz8ubIxGv5aCRVxQG_jdkRF/s1600/pasted+pastrami.png" imageanchor="1" ><img border="0" height="294" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgSHhtp0MfOxSjgKvUvyllVOScGwpB13Vjqx1oP1qdSIO5NBTYFm5hQaVasBqCidtu3rf27cvAAIEl4i7BKY6xAU0tplaSFLhOgu-UWP1MNm3vHHvz8ubIxGv5aCRVxQG_jdkRF/s400/pasted+pastrami.png" width="400" /></a></p> <p><a href="https://support.google.com/webmasters/answer/6338828">Property sets</a> help to show how your business is seen by Google across separate websites or apps. For example, if you have multiple international or brand-specific websites, and perhaps even an Android app, it can be useful to see changes of the whole set over time: are things headed in the expected direction? are there any outliers that you'd want to drill down into? Similarly, you could monitor your site's hreflang setup across different versions of the same website during a planned transition, such as when you <a href="https://support.google.com/webmasters/answer/6073543">move from HTTP to HTTPS</a>, or <a href="https://support.google.com/webmasters/answer/6033049">change domains</a>.</p> <p>With <a href="https://support.google.com/webmasters/answer/6338828">Search Console's property sets</a>, you can now just add any verified properties to a set, let the data collect, and then check out features like the <a href="https://support.google.com/webmasters/answer/6101188">mobile usability report</a>, review your <a href="https://support.google.com/webmasters/answer/6328309">AMP implementation</a>, double-check <a href="https://support.google.com/webmasters/answer/6381755">rich cards</a>, or <a href="https://support.google.com/webmasters/answer/6059209">hreflang / internationalization markup</a>, and more.</p> <br><p>We hope these changes make it easier to understand your properties in Search Console. Should you have any questions - or if you just want to help others, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">Webmaster Help Forums</a>.</p> <br> <span class="byline-author">Posted by <a href="https://google.me/+johnmueller?rel=author">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>Since initially <a href="https://webmasters.googleblog.com/2016/05/tie-your-sites-together-with-property.html">announcing property sets</a> earlier this year, one of the most popular requests has been to expand this functionality to more sections of Search Console. Thanks to your feedback, we're now expanding property sets to more features!</p> <p><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgSHhtp0MfOxSjgKvUvyllVOScGwpB13Vjqx1oP1qdSIO5NBTYFm5hQaVasBqCidtu3rf27cvAAIEl4i7BKY6xAU0tplaSFLhOgu-UWP1MNm3vHHvz8ubIxGv5aCRVxQG_jdkRF/s1600/pasted+pastrami.png" imageanchor="1" ><img border="0" height="294" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgSHhtp0MfOxSjgKvUvyllVOScGwpB13Vjqx1oP1qdSIO5NBTYFm5hQaVasBqCidtu3rf27cvAAIEl4i7BKY6xAU0tplaSFLhOgu-UWP1MNm3vHHvz8ubIxGv5aCRVxQG_jdkRF/s400/pasted+pastrami.png" width="400" /></a></p> <p><a href="https://support.google.com/webmasters/answer/6338828">Property sets</a> help to show how your business is seen by Google across separate websites or apps. For example, if you have multiple international or brand-specific websites, and perhaps even an Android app, it can be useful to see changes of the whole set over time: are things headed in the expected direction? are there any outliers that you'd want to drill down into? Similarly, you could monitor your site's hreflang setup across different versions of the same website during a planned transition, such as when you <a href="https://support.google.com/webmasters/answer/6073543">move from HTTP to HTTPS</a>, or <a href="https://support.google.com/webmasters/answer/6033049">change domains</a>.</p> <p>With <a href="https://support.google.com/webmasters/answer/6338828">Search Console's property sets</a>, you can now just add any verified properties to a set, let the data collect, and then check out features like the <a href="https://support.google.com/webmasters/answer/6101188">mobile usability report</a>, review your <a href="https://support.google.com/webmasters/answer/6328309">AMP implementation</a>, double-check <a href="https://support.google.com/webmasters/answer/6381755">rich cards</a>, or <a href="https://support.google.com/webmasters/answer/6059209">hreflang / internationalization markup</a>, and more.</p> <br><p>We hope these changes make it easier to understand your properties in Search Console. Should you have any questions - or if you just want to help others, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">Webmaster Help Forums</a>.</p> <br> <span class="byline-author">Posted by <a href="https://google.me/+johnmueller?rel=author">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:Enhancing property sets to cover more reports in Search Console&url=https://webmasters.googleblog.com/2016/12/enhancing-property-sets-to-cover-more.html&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/12/enhancing-property-sets-to-cover-more.html'> <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/12/enhancing-property-sets-to-cover-more.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/general%20tips' rel='tag'> general tips </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/https' rel='tag'> https </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console' rel='tag'> search console </a> </span> </div> </div> </div> <div class='post' data-id='9148735357724833140' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/11/an-update-on-googles-feature-phone.html' itemprop='url' title='An update on Google's feature-phone crawling & indexing'> An update on Google's feature-phone crawling & indexing </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, November 30, 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>Limited mobile devices, "<a href="https://www.google.com/search?q=wap+OR+wml+feature+phones&source=lnms&tbm=isch">feature-phones</a>", require a special form of markup or a transcoder for web content. Most websites don't provide feature-phone-compatible content in WAP/WML any more. Given these developments, we've made changes in how we crawl feature-phone content (note: these changes don't affect smartphone content):</p> <p><strong>1. We've retired the feature-phone Googlebot</strong></p> <p>We won't be using the feature-phone user-agents for crawling for search going forward. </p> <p><strong>2. Use "handheld" link annotations for dynamic serving of feature-phone content.</strong></p> <p>Some sites provide content for feature-phones through dynamic serving, based on the user's user-agent. To understand this configuration, make sure your desktop and smartphone pages have a self-referential alternate URL link for handheld (feature-phone) devices:</p> <p><pre><link rel="alternate" media="handheld" href="[current page URL]" /></pre></p> <p>This is a change from our previous guidance of only using the "vary: user-agent" HTTP header. We've updated our documentation on <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/other-devices?hl=en#feature-phones">making feature-phone pages</a> accordingly. We hope adding this link element is possible on your side, and thank you for your help in this regard. We'll continue to show feature-phone URLs in search when we can recognize them, and when they're appropriate for users.</p> <p><strong>3. We're retiring feature-phone tools in Search Console</strong></p> <p>Without the feature-phone Googlebot, special sitemaps extensions for feature-phone, the Fetch as Google feature-phone options, and feature-phone crawl errors are no longer needed. We continue to support <a href="http://sitemaps.org/">sitemaps</a> and other sitemaps extensions (such as for <a href="https://developers.google.com/webmasters/videosearch/sitemaps">videos</a> or <a href="https://support.google.com/news/publisher/answer/74288">Google News</a>), as well as the other <a href="https://support.google.com/webmasters/answer/6066468">Fetch as Google</a> options in <a href="https://www.google.com/webmasters/tools">Search Console</a>. </p> <br><p>We've worked to make these changes as minimal as possible. Most websites don't serve feature-phone content, and wouldn't be affected. If your site has been providing feature-phone content, we thank you for your help in bringing the Internet to feature-phone users worldwide!</p> <p>For any questions, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">Webmaster Help Forums</a>!</p> <span class="byline-author">Posted by <a href="https://google.me/+johnmueller?rel=theauthor">John Mueller</a>, Webmaster Trends Analyst, Google Switzerland</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>Limited mobile devices, "<a href="https://www.google.com/search?q=wap+OR+wml+feature+phones&source=lnms&tbm=isch">feature-phones</a>", require a special form of markup or a transcoder for web content. Most websites don't provide feature-phone-compatible content in WAP/WML any more. Given these developments, we've made changes in how we crawl feature-phone content (note: these changes don't affect smartphone content):</p> <p><strong>1. We've retired the feature-phone Googlebot</strong></p> <p>We won't be using the feature-phone user-agents for crawling for search going forward. </p> <p><strong>2. Use "handheld" link annotations for dynamic serving of feature-phone content.</strong></p> <p>Some sites provide content for feature-phones through dynamic serving, based on the user's user-agent. To understand this configuration, make sure your desktop and smartphone pages have a self-referential alternate URL link for handheld (feature-phone) devices:</p> <p><pre><link rel="alternate" media="handheld" href="[current page URL]" /></pre></p> <p>This is a change from our previous guidance of only using the "vary: user-agent" HTTP header. We've updated our documentation on <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/other-devices?hl=en#feature-phones">making feature-phone pages</a> accordingly. We hope adding this link element is possible on your side, and thank you for your help in this regard. We'll continue to show feature-phone URLs in search when we can recognize them, and when they're appropriate for users.</p> <p><strong>3. We're retiring feature-phone tools in Search Console</strong></p> <p>Without the feature-phone Googlebot, special sitemaps extensions for feature-phone, the Fetch as Google feature-phone options, and feature-phone crawl errors are no longer needed. We continue to support <a href="http://sitemaps.org/">sitemaps</a> and other sitemaps extensions (such as for <a href="https://developers.google.com/webmasters/videosearch/sitemaps">videos</a> or <a href="https://support.google.com/news/publisher/answer/74288">Google News</a>), as well as the other <a href="https://support.google.com/webmasters/answer/6066468">Fetch as Google</a> options in <a href="https://www.google.com/webmasters/tools">Search Console</a>. </p> <br><p>We've worked to make these changes as minimal as possible. Most websites don't serve feature-phone content, and wouldn't be affected. If your site has been providing feature-phone content, we thank you for your help in bringing the Internet to feature-phone users worldwide!</p> <p>For any questions, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">Webmaster Help Forums</a>!</p> <span class="byline-author">Posted by <a href="https://google.me/+johnmueller?rel=theauthor">John Mueller</a>, Webmaster Trends Analyst, Google Switzerland</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:An update on Google's feature-phone crawling & indexing&url=https://webmasters.googleblog.com/2016/11/an-update-on-googles-feature-phone.html&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/an-update-on-googles-feature-phone.html'> <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/an-update-on-googles-feature-phone.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' rel='tag'> advanced </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile' rel='tag'> mobile </a> </span> </div> </div> </div> <div class='post' data-id='2460482850417793814' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/11/saying-goodbye-to-content-keywords.html' itemprop='url' title='Saying goodbye to Content Keywords'> Saying goodbye to Content Keywords </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, November 29, 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>In the early days - back when <a href="https://www.google.com/webmasters/tools">Search Console</a> was still called Webmaster Tools - the content keywords feature was the only way to see what Googlebot found when it crawled a website. It was useful to see that Google was able to crawl your pages at all, or if your site was hacked. </p> <p>In the meantime, you can easily check any page on your website and <a href="https://support.google.com/webmasters/answer/6066468">see how Googlebot fetches</a> it immediately, <a href="https://support.google.com/webmasters/answer/6155685">Search Analytics</a> shows you which keywords we've shown your site in search for, and Google informs you of many kinds of hacks automatically. Additionally, users were often confused about the keywords listed in content keywords. And so, the time has come to retire the Content Keywords feature in Search Console. </p> <p>The words on your pages, the keywords if you will, are still important for Google's (and your users') understanding of your pages. While our systems have gotten better, they can't read your mind: be clear about what your site is about, and what you'd like to be found for. Tell visitors what makes your site, your products and services, special!</p> <p>What was your most surprising, or favorite, keyword shown? Let us know in the comments!</p> <span class="byline-author">Posted by <a href="https://google.me/+johnmueller?rel=arthur">John Mueller</a>, Webmaster Trends Analyst, Google Switzerland</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>In the early days - back when <a href="https://www.google.com/webmasters/tools">Search Console</a> was still called Webmaster Tools - the content keywords feature was the only way to see what Googlebot found when it crawled a website. It was useful to see that Google was able to crawl your pages at all, or if your site was hacked. </p> <p>In the meantime, you can easily check any page on your website and <a href="https://support.google.com/webmasters/answer/6066468">see how Googlebot fetches</a> it immediately, <a href="https://support.google.com/webmasters/answer/6155685">Search Analytics</a> shows you which keywords we've shown your site in search for, and Google informs you of many kinds of hacks automatically. Additionally, users were often confused about the keywords listed in content keywords. And so, the time has come to retire the Content Keywords feature in Search Console. </p> <p>The words on your pages, the keywords if you will, are still important for Google's (and your users') understanding of your pages. While our systems have gotten better, they can't read your mind: be clear about what your site is about, and what you'd like to be found for. Tell visitors what makes your site, your products and services, special!</p> <p>What was your most surprising, or favorite, keyword shown? Let us know in the comments!</p> <span class="byline-author">Posted by <a href="https://google.me/+johnmueller?rel=arthur">John Mueller</a>, Webmaster Trends Analyst, Google Switzerland</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:Saying goodbye to Content Keywords&url=https://webmasters.googleblog.com/2016/11/saying-goodbye-to-content-keywords.html&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/saying-goodbye-to-content-keywords.html'> <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/saying-goodbye-to-content-keywords.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/search%20console' rel='tag'> search console </a> </span> </div> </div> </div> <div class='post' data-id='2168173033727260447' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/11/rich-cards-expands-to-more-verticals.html' itemprop='url' title='Rich Cards expands to more verticals'> Rich Cards expands to more verticals </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Monday, November 21, 2016 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p>At Google I/O in May, we <a href="https://webmasters.googleblog.com/2016/05/introducing-rich-cards.html">launched Rich Cards</a> for Movies and Recipes, creating a new way for site owners to present previews of their content on the Search results page. Today, we’re expanding to two new verticals for US-based sites: <a href="https://developers.google.com/search/docs/data-types/local-businesses#restaurant-lists">Local restaurants</a> and <a href="https://developers.google.com/search/docs/data-types/courses">Online courses</a>. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEihjaSDbFTfa7RuXyHlDOr9Vg2_ugYCjI1aITyRiFebh0C_E3ZSWmGinDmclOnNI5znhnbI3FL2edckpZSCUe1pLpWtnxRMQQXQs-sFW8RcEqkjkWRSOYqS106SaOckhO3SQsmV/s1600/card-numero-one.png" imageanchor="1" ><img border="0" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEihjaSDbFTfa7RuXyHlDOr9Vg2_ugYCjI1aITyRiFebh0C_E3ZSWmGinDmclOnNI5znhnbI3FL2edckpZSCUe1pLpWtnxRMQQXQs-sFW8RcEqkjkWRSOYqS106SaOckhO3SQsmV/s400/card1.png" width="230" /></a> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgFB5f6Al5cqAsqTD0w3eFrwOtL5JO3Kc0AMflOwcFMG4p4GCLF7WVGVoRcsm1ljX1EovSyGvXwPYYwY1U7re6eN6gDsZVwkznr3xU8mTSwL77zdheC-qsWIlEynXBxA3va6c_w/s1600/a-card-too.png" imageanchor="1" ><img border="0" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgFB5f6Al5cqAsqTD0w3eFrwOtL5JO3Kc0AMflOwcFMG4p4GCLF7WVGVoRcsm1ljX1EovSyGvXwPYYwY1U7re6eN6gDsZVwkznr3xU8mTSwL77zdheC-qsWIlEynXBxA3va6c_w/s400/card2.png" width="231" /></a> </p> <p>Evolution of search results for queries like [best New Orleans restaurants] and [leadership courses]: with rich cards, results are presented in new UIs, like carousels that are easy to browse by scrolling left and right, or a vertical three-pack that displays more individual courses</p> <p>By building Rich Cards, you have a new opportunity to attract more engaged users to your page. Users can swipe through restaurant recommendations from sites like TripAdvisor, Thrillist, Time Out, Eater, and 10Best. In addition to food, users can browse through courses from sites like Coursera, LinkedIn Learning, EdX, Harvard, Udacity, FutureLearn, Edureka, Open University, Udemy, Canvas Network, and NPTEL.</p> <p>If you have a site that contains local restaurant information or offers online courses, check out our developer docs to start building Rich Cards in the <a href="https://developers.google.com/search/docs/data-types/local-businesses#restaurant-lists">Local restaurant</a> and <a href="https://developers.google.com/search/docs/data-types/courses">Online courses</a> verticals.</p> <p>While AMP HTML is not required for <a href="https://developers.google.com/search/docs/data-types/local-businesses#restaurant-lists">Local restaurant</a> pages and Online Courses rich cards, AMP provides Google Search users with a consistently fast experience, so we recommend that you create AMP pages to further engage users. Users consuming AMP’d content will be able to swipe near instantly from restaurant to restaurant or from recipe to recipe within your site. </p> <p> <img border="0" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjKjj0-R0Op4x_vuzIg9bCEdZ9gwgf0gjS4-bZEx1qrVYpk78hEjI_ZR8tiIi7NQZygJD85euwOCmCRfQCS99-jF5h6B-PwnrLlMh3mmJOwvqzTqI2LoWvI_b5qKeuA4n4xderC/s400/card-swoop-swoop.gif" width="226" /> </p> <p>Users who tap on your Rich Card will be taken near instantly to your AMP page, and be able to swipe between pages within your site. </p> <p>Check out our <a href="https://developers.google.com/search/docs/guides/use-AMP-HTML">developer site</a> for implementation details. </p> <p>To make it easier for you to create Rich Cards, we made some changes in our tools:</p> <ul><li>The <a href="https://search.google.com/structured-data/testing-tool/u/0/">Structured Data Testing Tool</a> displays markup errors and a preview card for Local restaurant content as it might appear on Search. </li> <li>The <a href="https://www.google.com/webmasters/tools/rich-cards">Rich Cards report</a> in Search Console shows which cards across verticals contain errors, and which ones could be enhanced with more markup. </li> <li>The <a href="https://search.google.com/search-console/amp">AMP Test</a> helps validate AMP pages as well as mark up on the page.</li></ul> <p><b>What’s next?</b></p> <p>We are actively experimenting with new verticals globally to provide more opportunities for you to display richer previews of your content. </p> <p>If you have questions, find us in the <a href="https://productforums.google.com/forum/#!categories/webmasters/structured-data">dedicated Structured data section</a> of our forum, <a href="https://twitter.com/googlewmc">on Twitter</a> or <a href="https://plus.google.com/+GoogleWebmasters/">on Google+</a>.</p> <br> <span class="byline-author">Post by Stacie Chan, Global Product Partnerships</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p>At Google I/O in May, we <a href="https://webmasters.googleblog.com/2016/05/introducing-rich-cards.html">launched Rich Cards</a> for Movies and Recipes, creating a new way for site owners to present previews of their content on the Search results page. Today, we’re expanding to two new verticals for US-based sites: <a href="https://developers.google.com/search/docs/data-types/local-businesses#restaurant-lists">Local restaurants</a> and <a href="https://developers.google.com/search/docs/data-types/courses">Online courses</a>. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEihjaSDbFTfa7RuXyHlDOr9Vg2_ugYCjI1aITyRiFebh0C_E3ZSWmGinDmclOnNI5znhnbI3FL2edckpZSCUe1pLpWtnxRMQQXQs-sFW8RcEqkjkWRSOYqS106SaOckhO3SQsmV/s1600/card-numero-one.png" imageanchor="1" ><img border="0" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEihjaSDbFTfa7RuXyHlDOr9Vg2_ugYCjI1aITyRiFebh0C_E3ZSWmGinDmclOnNI5znhnbI3FL2edckpZSCUe1pLpWtnxRMQQXQs-sFW8RcEqkjkWRSOYqS106SaOckhO3SQsmV/s400/card1.png" width="230" /></a> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgFB5f6Al5cqAsqTD0w3eFrwOtL5JO3Kc0AMflOwcFMG4p4GCLF7WVGVoRcsm1ljX1EovSyGvXwPYYwY1U7re6eN6gDsZVwkznr3xU8mTSwL77zdheC-qsWIlEynXBxA3va6c_w/s1600/a-card-too.png" imageanchor="1" ><img border="0" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgFB5f6Al5cqAsqTD0w3eFrwOtL5JO3Kc0AMflOwcFMG4p4GCLF7WVGVoRcsm1ljX1EovSyGvXwPYYwY1U7re6eN6gDsZVwkznr3xU8mTSwL77zdheC-qsWIlEynXBxA3va6c_w/s400/card2.png" width="231" /></a> </p> <p>Evolution of search results for queries like [best New Orleans restaurants] and [leadership courses]: with rich cards, results are presented in new UIs, like carousels that are easy to browse by scrolling left and right, or a vertical three-pack that displays more individual courses</p> <p>By building Rich Cards, you have a new opportunity to attract more engaged users to your page. Users can swipe through restaurant recommendations from sites like TripAdvisor, Thrillist, Time Out, Eater, and 10Best. In addition to food, users can browse through courses from sites like Coursera, LinkedIn Learning, EdX, Harvard, Udacity, FutureLearn, Edureka, Open University, Udemy, Canvas Network, and NPTEL.</p> <p>If you have a site that contains local restaurant information or offers online courses, check out our developer docs to start building Rich Cards in the <a href="https://developers.google.com/search/docs/data-types/local-businesses#restaurant-lists">Local restaurant</a> and <a href="https://developers.google.com/search/docs/data-types/courses">Online courses</a> verticals.</p> <p>While AMP HTML is not required for <a href="https://developers.google.com/search/docs/data-types/local-businesses#restaurant-lists">Local restaurant</a> pages and Online Courses rich cards, AMP provides Google Search users with a consistently fast experience, so we recommend that you create AMP pages to further engage users. Users consuming AMP’d content will be able to swipe near instantly from restaurant to restaurant or from recipe to recipe within your site. </p> <p> <img border="0" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjKjj0-R0Op4x_vuzIg9bCEdZ9gwgf0gjS4-bZEx1qrVYpk78hEjI_ZR8tiIi7NQZygJD85euwOCmCRfQCS99-jF5h6B-PwnrLlMh3mmJOwvqzTqI2LoWvI_b5qKeuA4n4xderC/s400/card-swoop-swoop.gif" width="226" /> </p> <p>Users who tap on your Rich Card will be taken near instantly to your AMP page, and be able to swipe between pages within your site. </p> <p>Check out our <a href="https://developers.google.com/search/docs/guides/use-AMP-HTML">developer site</a> for implementation details. </p> <p>To make it easier for you to create Rich Cards, we made some changes in our tools:</p> <ul><li>The <a href="https://search.google.com/structured-data/testing-tool/u/0/">Structured Data Testing Tool</a> displays markup errors and a preview card for Local restaurant content as it might appear on Search. </li> <li>The <a href="https://www.google.com/webmasters/tools/rich-cards">Rich Cards report</a> in Search Console shows which cards across verticals contain errors, and which ones could be enhanced with more markup. </li> <li>The <a href="https://search.google.com/search-console/amp">AMP Test</a> helps validate AMP pages as well as mark up on the page.</li></ul> <p><b>What’s next?</b></p> <p>We are actively experimenting with new verticals globally to provide more opportunities for you to display richer previews of your content. </p> <p>If you have questions, find us in the <a href="https://productforums.google.com/forum/#!categories/webmasters/structured-data">dedicated Structured data section</a> of our forum, <a href="https://twitter.com/googlewmc">on Twitter</a> or <a href="https://plus.google.com/+GoogleWebmasters/">on Google+</a>.</p> <br> <span class="byline-author">Post by Stacie Chan, Global Product Partnerships</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:Rich Cards expands to more verticals&url=https://webmasters.googleblog.com/2016/11/rich-cards-expands-to-more-verticals.html&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/rich-cards-expands-to-more-verticals.html'> <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/rich-cards-expands-to-more-verticals.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' rel='tag'> AMP </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/rich%20cards' rel='tag'> rich cards </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data' rel='tag'> structured data </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' 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&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'> <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' rel='tag'> advanced </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/general%20tips' rel='tag'> general tips </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly' rel='tag'> mobile-friendly </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/performance' 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' 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&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'> <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' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly' rel='tag'> mobile-friendly </a> </span> </div> </div> </div> <div class='post' data-id='2085203645066083301' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/11/heres-to-more-https-on-web.html' itemprop='url' title='Here’s to more HTTPS on the web!'> Here’s to more HTTPS on the web! </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"> Cross-posted from the <a href="https://security.googleblog.com/2016/11/heres-to-more-https-on-web.html">Google Security Blog</a>.<br /><br /> Security has always been critical to the web, but challenges involved in site migration have inhibited HTTPS adoption for several years. In the interest of a safer web for all, at Google we’ve worked alongside many others across the online ecosystem to better understand and address these challenges, resulting in real change. A web with ubiquitous HTTPS is not the distant future. It’s happening now, with secure browsing becoming standard for users of Chrome.<br /> <br /> Today, we’re adding a <a href="https://www.google.com/transparencyreport/https/metrics/?hl=en">new section to the HTTPS Report Card in our Transparency Report</a> that includes data about how HTTPS usage has been increasing over time. More than half of pages loaded and two-thirds of total time spent by Chrome desktop users occur via HTTPS, and we expect these metrics to continue their strong upward trajectory.<br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEimdGbAU_gF-Lyn6xsLriLQROOnH-puq-TcgBW55OfvcA419x2RRAGGBG8nhKHNVY3u_fzdqgglmgof8_wnuamDtnVuaSqi0ABInFaMHGwqNe2oMlclbvTEG4a0_MgB5WhyphenhyphennOaZ4w/s1600/chart.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="436" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEimdGbAU_gF-Lyn6xsLriLQROOnH-puq-TcgBW55OfvcA419x2RRAGGBG8nhKHNVY3u_fzdqgglmgof8_wnuamDtnVuaSqi0ABInFaMHGwqNe2oMlclbvTEG4a0_MgB5WhyphenhyphennOaZ4w/s640/chart.png" width="640" /></a></div> <div class="separator" style="clear: both; text-align: center;"> Percentage of pages loaded over HTTPS in Chrome</div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> As the remainder of the web transitions to HTTPS, we’ll continue working to ensure that migrating to HTTPS is a no-brainer, providing business benefit beyond increased security. HTTPS currently enables the <a href="https://istlsfastyet.com/">best</a> <a href="https://blog.chromium.org/2013/11/making-web-faster-with-spdy-and-http2.html">performance</a> the web offers and powerful features that <a href="https://developers.google.com/web/showcase/">benefit</a> site conversions, including both new features such as <a href="https://developers.google.com/web/fundamentals/getting-started/primers/service-workers">service workers</a> for offline support and <a href="https://www.mobify.com/insights/google-web-push-notifications-case-study/">web push notifications</a>, and existing features such as <a href="https://developers.google.com/web/updates/2015/06/checkout-faster-with-autofill">credit card autofill</a> and the <a href="https://developers.google.com/web/updates/2016/04/geolocation-on-secure-contexts-only">HTML5 geolocation API</a> that are <a href="https://www.chromium.org/Home/chromium-security/deprecating-powerful-features-on-insecure-origins">too powerful to be used</a> over non-secure HTTP. As with all major site migrations, there are certain steps webmasters should take to ensure that search ranking transitions are smooth when moving to HTTPS. To help with this, we’ve posted <a href="https://plus.google.com/+JohnMueller/posts/PY1xCWbeDVC">two</a> <a href="https://plus.google.com/+GoogleWebmasters/posts/eYmUYvNNT5J">FAQs</a> to help sites transition correctly, and will continue to improve our <a href="https://developers.google.com/web/fundamentals/security/encrypt-in-transit/why-https">web fundamentals guidance</a>.</div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> We’ve seen many sites successfully transition with negligible effect on their search ranking and traffic. Brian Wood, Director of Marketing SEO at Wayfair, a large retail site, commented: “We were able to migrate Wayfair.com to HTTPS with no meaningful impact to Google rankings or Google organic search traffic. We are very pleased to say that all Wayfair sites are now fully HTTPS.” CNET, a large tech news site, had a similar experience: “We successfully completed our move of CNET.com to HTTPS last month,” said John Sherwood, Vice President of Engineering & Technology at CNET. “Since then, there has been no change in our Google rankings or Google organic search traffic.”</div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> Webmasters that include ads on their sites also should carefully monitor ad performance and revenue during large site migrations. The portion of Google ad traffic served over HTTPS has <a href="https://g.co/https">increased dramatically</a> over the past 3 years. All ads that come from any Google source always support HTTPS, including AdWords, AdSense, or DoubleClick Ad Exchange; ads sold directly, such as those through DoubleClick for Publishers, still need to be designed to be HTTPS-friendly. This means there will be no change to the Google-sourced ads that appear on a site after migrating to HTTPS. Many publishing partners have seen this in practice after a successful HTTPS transition. Jason Tollestrup, Director of Programmatic Advertising for the <a href="https://developer.washingtonpost.com/pb/blog/post/2015/12/10/moving-the-washington-post-to-https/">Washington Post</a>, “saw no material impact to AdX revenue with the transition to SSL.”</div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> As migrating to HTTPS becomes even easier, <a href="https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html">we’ll continue</a> working towards a web that’s secure by default. Don’t hesitate to start planning your HTTPS migration today!</div> <br /> <span class="byline-author">Posted by Adrienne Porter Felt and Emily Schechter, Chrome Security Team</span><br /> </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"> Cross-posted from the <a href="https://security.googleblog.com/2016/11/heres-to-more-https-on-web.html">Google Security Blog</a>.<br /><br /> Security has always been critical to the web, but challenges involved in site migration have inhibited HTTPS adoption for several years. In the interest of a safer web for all, at Google we’ve worked alongside many others across the online ecosystem to better understand and address these challenges, resulting in real change. A web with ubiquitous HTTPS is not the distant future. It’s happening now, with secure browsing becoming standard for users of Chrome.<br /> <br /> Today, we’re adding a <a href="https://www.google.com/transparencyreport/https/metrics/?hl=en">new section to the HTTPS Report Card in our Transparency Report</a> that includes data about how HTTPS usage has been increasing over time. More than half of pages loaded and two-thirds of total time spent by Chrome desktop users occur via HTTPS, and we expect these metrics to continue their strong upward trajectory.<br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEimdGbAU_gF-Lyn6xsLriLQROOnH-puq-TcgBW55OfvcA419x2RRAGGBG8nhKHNVY3u_fzdqgglmgof8_wnuamDtnVuaSqi0ABInFaMHGwqNe2oMlclbvTEG4a0_MgB5WhyphenhyphennOaZ4w/s1600/chart.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="436" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEimdGbAU_gF-Lyn6xsLriLQROOnH-puq-TcgBW55OfvcA419x2RRAGGBG8nhKHNVY3u_fzdqgglmgof8_wnuamDtnVuaSqi0ABInFaMHGwqNe2oMlclbvTEG4a0_MgB5WhyphenhyphennOaZ4w/s640/chart.png" width="640" /></a></div> <div class="separator" style="clear: both; text-align: center;"> Percentage of pages loaded over HTTPS in Chrome</div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> As the remainder of the web transitions to HTTPS, we’ll continue working to ensure that migrating to HTTPS is a no-brainer, providing business benefit beyond increased security. HTTPS currently enables the <a href="https://istlsfastyet.com/">best</a> <a href="https://blog.chromium.org/2013/11/making-web-faster-with-spdy-and-http2.html">performance</a> the web offers and powerful features that <a href="https://developers.google.com/web/showcase/">benefit</a> site conversions, including both new features such as <a href="https://developers.google.com/web/fundamentals/getting-started/primers/service-workers">service workers</a> for offline support and <a href="https://www.mobify.com/insights/google-web-push-notifications-case-study/">web push notifications</a>, and existing features such as <a href="https://developers.google.com/web/updates/2015/06/checkout-faster-with-autofill">credit card autofill</a> and the <a href="https://developers.google.com/web/updates/2016/04/geolocation-on-secure-contexts-only">HTML5 geolocation API</a> that are <a href="https://www.chromium.org/Home/chromium-security/deprecating-powerful-features-on-insecure-origins">too powerful to be used</a> over non-secure HTTP. As with all major site migrations, there are certain steps webmasters should take to ensure that search ranking transitions are smooth when moving to HTTPS. To help with this, we’ve posted <a href="https://plus.google.com/+JohnMueller/posts/PY1xCWbeDVC">two</a> <a href="https://plus.google.com/+GoogleWebmasters/posts/eYmUYvNNT5J">FAQs</a> to help sites transition correctly, and will continue to improve our <a href="https://developers.google.com/web/fundamentals/security/encrypt-in-transit/why-https">web fundamentals guidance</a>.</div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> We’ve seen many sites successfully transition with negligible effect on their search ranking and traffic. Brian Wood, Director of Marketing SEO at Wayfair, a large retail site, commented: “We were able to migrate Wayfair.com to HTTPS with no meaningful impact to Google rankings or Google organic search traffic. We are very pleased to say that all Wayfair sites are now fully HTTPS.” CNET, a large tech news site, had a similar experience: “We successfully completed our move of CNET.com to HTTPS last month,” said John Sherwood, Vice President of Engineering & Technology at CNET. “Since then, there has been no change in our Google rankings or Google organic search traffic.”</div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> Webmasters that include ads on their sites also should carefully monitor ad performance and revenue during large site migrations. The portion of Google ad traffic served over HTTPS has <a href="https://g.co/https">increased dramatically</a> over the past 3 years. All ads that come from any Google source always support HTTPS, including AdWords, AdSense, or DoubleClick Ad Exchange; ads sold directly, such as those through DoubleClick for Publishers, still need to be designed to be HTTPS-friendly. This means there will be no change to the Google-sourced ads that appear on a site after migrating to HTTPS. Many publishing partners have seen this in practice after a successful HTTPS transition. Jason Tollestrup, Director of Programmatic Advertising for the <a href="https://developer.washingtonpost.com/pb/blog/post/2015/12/10/moving-the-washington-post-to-https/">Washington Post</a>, “saw no material impact to AdX revenue with the transition to SSL.”</div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> <br /></div> <div class="separator" style="clear: both; text-align: left;"> As migrating to HTTPS becomes even easier, <a href="https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html">we’ll continue</a> working towards a web that’s secure by default. Don’t hesitate to start planning your HTTPS migration today!</div> <br /> <span class="byline-author">Posted by Adrienne Porter Felt and Emily Schechter, Chrome Security Team</span><br /> </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:Here’s to more HTTPS on the web!&url=https://webmasters.googleblog.com/2016/11/heres-to-more-https-on-web.html&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/heres-to-more-https-on-web.html'> <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/heres-to-more-https-on-web.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/security' rel='tag'> security </a> </span> </div> </div> </div> <div class='post' data-id='7218176545813550464' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/10/using-amp-try-our-new-webpage-tester.html' itemprop='url' title='Using AMP? Try our new webpage tester'> Using AMP? Try our new webpage tester </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, October 13, 2016 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p><a href="https://www.ampproject.org/">Accelerated Mobile Pages</a> (AMP) is a great way to make content on your website accessible in an extremely fast way. To help ensure that your AMP implementation is working as expected , <a href="https://www.google.com/webmasters/tools">Search Console</a> now has an enhanced <a href="https://search.google.com/search-console/amp">AMP testing tool</a>. </p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjjOrFFZUVwKJ97VfFzR-VbA6xUubFvKQ8Lq6vh8NqrO2jomFZokV94DHiQPoa9K8ySoWzD4p9vYfunlCpKuSn9rKtq6SAqBpeFs8BvHAUjy5goD_1BX8vj_Ii7fSBniplLCVLR/s1600/curl-amp-volume-9.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjjOrFFZUVwKJ97VfFzR-VbA6xUubFvKQ8Lq6vh8NqrO2jomFZokV94DHiQPoa9K8ySoWzD4p9vYfunlCpKuSn9rKtq6SAqBpeFs8BvHAUjy5goD_1BX8vj_Ii7fSBniplLCVLR/s640/curl-amp-volume-9.png" width="640" /></a> <p>This testing tool is mobile-friendly and uses Google's <a href="https://support.google.com/webmasters/answer/182072">live web-search infrastructure</a> to analyze the AMP page with the real Googlebot. The tool tests the validity of the AMP markup as well as any structured data on the page. If issues are found, click on them to see details, and to have the line in the source-code highlighted. For valid AMP pages, we may also provide a link to a live preview of how this page may appear in Google's search results. </p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj4GBxxavWzbh6bl-IrQ_d6ss1mlYPwveVZ-bnU7a_CGnFKRIY4jg6beLczfPdYQjHCO0qTVFCJdbbVEoC6RXCt1BCzNN1UYHVBZHl0SBgNRvTJtm9_wolJnxftTQM2pHTMhgCc/s1600/curl-amp-volume-11.png" imageanchor="1" ><img border="0" height="420" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj4GBxxavWzbh6bl-IrQ_d6ss1mlYPwveVZ-bnU7a_CGnFKRIY4jg6beLczfPdYQjHCO0qTVFCJdbbVEoC6RXCt1BCzNN1UYHVBZHl0SBgNRvTJtm9_wolJnxftTQM2pHTMhgCc/s420/curl-amp-volume-11.png" /></a> <p>With the share button on the bottom right, you can now share a snapshot of the results that you're currently seeing with others. This makes it easier to discuss issues with your team, whether they're regular occurrences or one-time quirks that you need to iron out. Just click the share button and pass on the URL for this test snapshot. This share feature is now also available in the <a href="https://search.google.com/search-console/mobile-friendly">mobile-friendly testing tool</a>.</p> <p>We hope this tool makes it easier to create great AMP’d content while finding and resolving issues that may appear on your AMP pages. For any questions, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">webmaster's help forum</a>. </p> <br> <br> <span class="byline-author">Posted by Ofir Roval & 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><a href="https://www.ampproject.org/">Accelerated Mobile Pages</a> (AMP) is a great way to make content on your website accessible in an extremely fast way. To help ensure that your AMP implementation is working as expected , <a href="https://www.google.com/webmasters/tools">Search Console</a> now has an enhanced <a href="https://search.google.com/search-console/amp">AMP testing tool</a>. </p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjjOrFFZUVwKJ97VfFzR-VbA6xUubFvKQ8Lq6vh8NqrO2jomFZokV94DHiQPoa9K8ySoWzD4p9vYfunlCpKuSn9rKtq6SAqBpeFs8BvHAUjy5goD_1BX8vj_Ii7fSBniplLCVLR/s1600/curl-amp-volume-9.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjjOrFFZUVwKJ97VfFzR-VbA6xUubFvKQ8Lq6vh8NqrO2jomFZokV94DHiQPoa9K8ySoWzD4p9vYfunlCpKuSn9rKtq6SAqBpeFs8BvHAUjy5goD_1BX8vj_Ii7fSBniplLCVLR/s640/curl-amp-volume-9.png" width="640" /></a> <p>This testing tool is mobile-friendly and uses Google's <a href="https://support.google.com/webmasters/answer/182072">live web-search infrastructure</a> to analyze the AMP page with the real Googlebot. The tool tests the validity of the AMP markup as well as any structured data on the page. If issues are found, click on them to see details, and to have the line in the source-code highlighted. For valid AMP pages, we may also provide a link to a live preview of how this page may appear in Google's search results. </p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj4GBxxavWzbh6bl-IrQ_d6ss1mlYPwveVZ-bnU7a_CGnFKRIY4jg6beLczfPdYQjHCO0qTVFCJdbbVEoC6RXCt1BCzNN1UYHVBZHl0SBgNRvTJtm9_wolJnxftTQM2pHTMhgCc/s1600/curl-amp-volume-11.png" imageanchor="1" ><img border="0" height="420" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj4GBxxavWzbh6bl-IrQ_d6ss1mlYPwveVZ-bnU7a_CGnFKRIY4jg6beLczfPdYQjHCO0qTVFCJdbbVEoC6RXCt1BCzNN1UYHVBZHl0SBgNRvTJtm9_wolJnxftTQM2pHTMhgCc/s420/curl-amp-volume-11.png" /></a> <p>With the share button on the bottom right, you can now share a snapshot of the results that you're currently seeing with others. This makes it easier to discuss issues with your team, whether they're regular occurrences or one-time quirks that you need to iron out. Just click the share button and pass on the URL for this test snapshot. This share feature is now also available in the <a href="https://search.google.com/search-console/mobile-friendly">mobile-friendly testing tool</a>.</p> <p>We hope this tool makes it easier to create great AMP’d content while finding and resolving issues that may appear on your AMP pages. For any questions, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">webmaster's help forum</a>. </p> <br> <br> <span class="byline-author">Posted by Ofir Roval & 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:Using AMP? Try our new webpage tester&url=https://webmasters.googleblog.com/2016/10/using-amp-try-our-new-webpage-tester.html&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/10/using-amp-try-our-new-webpage-tester.html'> <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/10/using-amp-try-our-new-webpage-tester.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' rel='tag'> AMP </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console' rel='tag'> search console </a> </span> </div> </div> </div> <div class='post' data-id='1749279497457474392' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/09/webmaster-forums-top-amp-questions.html' itemprop='url' title='Webmaster Forums Top AMP Questions'> Webmaster Forums Top AMP Questions </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Friday, September 30, 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> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgrvNGzPVwbDTaFEleqBkUhoU5KYRoeGNGfwsT49215oR_zHQMKddqyBFy-GIylcKGxxaGvXxIMjpyWHEqLGSDjNmIEW7El2LvGadgfGPvqejAWkAR82V5ATvb8QovRHC5aOdJW/s1600/AMP-forum.jpg" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgrvNGzPVwbDTaFEleqBkUhoU5KYRoeGNGfwsT49215oR_zHQMKddqyBFy-GIylcKGxxaGvXxIMjpyWHEqLGSDjNmIEW7El2LvGadgfGPvqejAWkAR82V5ATvb8QovRHC5aOdJW/s640/AMP-forum.jpg" width="640" /></a> </p> <p>It has been busy here at Google Webmaster Central over the last few weeks, covering a lot of details about <a href="//goo.gl/mKg0Xw">Accelerated Mobile Pages</a> that we hope you have found useful. The topics have included:</p> <ul><li><a href="https://goo.gl/OMxKSP">What is AMP?</a></li> <li><a href="https://goo.gl/tEI6uQ">How to get started with Accelerated Mobile Pages</a></li> <li><a href="https://goo.gl/qHrzHm">How can Google Search Console help you AMPlify your site</a></li> <li><a href="https://goo.gl/XZUVPs">How to best evaluate issues with your Accelerated Mobile Pages</a></li> <li><a href="https://goo.gl/pouJ6M">Top 8 things to consider when you AMPlify a site</a></li> <li><a href="https://goo.gl/UQKvfs">How to set up Analytics on your AMP page</a></li> <li><a href="https://goo.gl/dyH0GF">How to set up Ads on your AMP page</a></li></ul> <p>We’ve also been seeing a few AMP questions coming to the Webmaster forums about getting started using AMP on Google Search. To help, we’ve compiled some of the most common questions we’ve seen:</p> <p style="font-weight:bold">Q: I’m considering creating AMP pages for my website. What is the benefit? What types of sites and pages is AMP for?</p> <p>Users love content that loads fast and without any fuss - using the AMP format may make it more compelling for people to consume and engage with your content on mobile devices. Research has shown that <a href="//goo.gl/xpKotK">40% of users</a> abandon a site that takes more than three seconds to load. <a href="//goo.gl/YTUcqQ">The Washington Post</a> observed an 88% decrease in article loading time and a 23% increase in returning users from mobile search from adopting AMP. </p> <p>The AMP format is great for all types of static web content such as news, recipes, movie listings, product pages, reviews, videos, blogs and more.</p> <p style="font-weight:bold">Q: We are getting errors logged in Search Console for AMP pages; however, we already fixed these issues. Why are we still seeing errors?</p> <p>The short answer is that changes to your AMP pages take about a week to be updated in Search Console. For a more in-depth answer on why, Google’s Webmaster Trends Analyst John Mueller shared a <a href="//goo.gl/MSv01u">detailed post</a> on Search Console latency challenges.</p> <p style="font-weight:bold">Q: Our AMP pages are not showing up on Google Search. What should we do?</p> <p>Only valid AMP pages will be eligible to show on Google Search. Check the validity of your  AMP pages by using the <a href="//goo.gl/aRjB32">AMP HTML Web Validator</a>, the <a href="//goo.gl/v84TOQ">Chrome</a> or <a href="//goo.gl/MEIwkd">Opera</a> Extension or through a more automated process such as a cron job to make sure all new content is valid.</p> <p>While it’s good practise overall to include <a href="//goo.gl/GB6Fvl">schema.org</a> structured data in your AMP pages (we recommend JSON-LD), it's especially important for news publishers. News content that includes <a href="//goo.gl/dYFFzd">valid markup properties</a> are eligible to be shown within the Top Stories section in Google Search results. To test your structured data, try using the <a href="//goo.gl/omN9l9">structured data testing tool</a>.</p> <p>If you have more questions that are not answered here, share your feedback in the comments below or on our <a href="//goo.gl/0UdXCN">Google Webmasters Google+ page</a>. Or as usual, feel free to post in our <a href="//goo.gl/OK9EhD">Webmasters Help Forum</a>.</p> <span class="byline-author">Posted by Tomo Taylor, AMP Community 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> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgrvNGzPVwbDTaFEleqBkUhoU5KYRoeGNGfwsT49215oR_zHQMKddqyBFy-GIylcKGxxaGvXxIMjpyWHEqLGSDjNmIEW7El2LvGadgfGPvqejAWkAR82V5ATvb8QovRHC5aOdJW/s1600/AMP-forum.jpg" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgrvNGzPVwbDTaFEleqBkUhoU5KYRoeGNGfwsT49215oR_zHQMKddqyBFy-GIylcKGxxaGvXxIMjpyWHEqLGSDjNmIEW7El2LvGadgfGPvqejAWkAR82V5ATvb8QovRHC5aOdJW/s640/AMP-forum.jpg" width="640" /></a> </p> <p>It has been busy here at Google Webmaster Central over the last few weeks, covering a lot of details about <a href="//goo.gl/mKg0Xw">Accelerated Mobile Pages</a> that we hope you have found useful. The topics have included:</p> <ul><li><a href="https://goo.gl/OMxKSP">What is AMP?</a></li> <li><a href="https://goo.gl/tEI6uQ">How to get started with Accelerated Mobile Pages</a></li> <li><a href="https://goo.gl/qHrzHm">How can Google Search Console help you AMPlify your site</a></li> <li><a href="https://goo.gl/XZUVPs">How to best evaluate issues with your Accelerated Mobile Pages</a></li> <li><a href="https://goo.gl/pouJ6M">Top 8 things to consider when you AMPlify a site</a></li> <li><a href="https://goo.gl/UQKvfs">How to set up Analytics on your AMP page</a></li> <li><a href="https://goo.gl/dyH0GF">How to set up Ads on your AMP page</a></li></ul> <p>We’ve also been seeing a few AMP questions coming to the Webmaster forums about getting started using AMP on Google Search. To help, we’ve compiled some of the most common questions we’ve seen:</p> <p style="font-weight:bold">Q: I’m considering creating AMP pages for my website. What is the benefit? What types of sites and pages is AMP for?</p> <p>Users love content that loads fast and without any fuss - using the AMP format may make it more compelling for people to consume and engage with your content on mobile devices. Research has shown that <a href="//goo.gl/xpKotK">40% of users</a> abandon a site that takes more than three seconds to load. <a href="//goo.gl/YTUcqQ">The Washington Post</a> observed an 88% decrease in article loading time and a 23% increase in returning users from mobile search from adopting AMP. </p> <p>The AMP format is great for all types of static web content such as news, recipes, movie listings, product pages, reviews, videos, blogs and more.</p> <p style="font-weight:bold">Q: We are getting errors logged in Search Console for AMP pages; however, we already fixed these issues. Why are we still seeing errors?</p> <p>The short answer is that changes to your AMP pages take about a week to be updated in Search Console. For a more in-depth answer on why, Google’s Webmaster Trends Analyst John Mueller shared a <a href="//goo.gl/MSv01u">detailed post</a> on Search Console latency challenges.</p> <p style="font-weight:bold">Q: Our AMP pages are not showing up on Google Search. What should we do?</p> <p>Only valid AMP pages will be eligible to show on Google Search. Check the validity of your  AMP pages by using the <a href="//goo.gl/aRjB32">AMP HTML Web Validator</a>, the <a href="//goo.gl/v84TOQ">Chrome</a> or <a href="//goo.gl/MEIwkd">Opera</a> Extension or through a more automated process such as a cron job to make sure all new content is valid.</p> <p>While it’s good practise overall to include <a href="//goo.gl/GB6Fvl">schema.org</a> structured data in your AMP pages (we recommend JSON-LD), it's especially important for news publishers. News content that includes <a href="//goo.gl/dYFFzd">valid markup properties</a> are eligible to be shown within the Top Stories section in Google Search results. To test your structured data, try using the <a href="//goo.gl/omN9l9">structured data testing tool</a>.</p> <p>If you have more questions that are not answered here, share your feedback in the comments below or on our <a href="//goo.gl/0UdXCN">Google Webmasters Google+ page</a>. Or as usual, feel free to post in our <a href="//goo.gl/OK9EhD">Webmasters Help Forum</a>.</p> <span class="byline-author">Posted by Tomo Taylor, AMP Community 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:Webmaster Forums Top AMP Questions&url=https://webmasters.googleblog.com/2016/09/webmaster-forums-top-amp-questions.html&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/webmaster-forums-top-amp-questions.html'> <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/webmaster-forums-top-amp-questions.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' rel='tag'> AMP </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community' rel='tag'> webmaster community </a> </span> </div> </div> </div> <div class='post' data-id='607455802790213955' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/09/penguin-is-now-part-of-our-core.html' itemprop='url' title='Penguin is now part of our core algorithm'> Penguin is now part of our core algorithm </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Friday, September 23, 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"> Google's algorithms rely on more than 200 unique signals or "clues" that make it possible to surface what you might be looking for. These signals include things like the specific words that appear on websites, the freshness of content, your region and PageRank. One specific signal of the algorithms is called <a href="https://webmasters.googleblog.com/2012/04/another-step-to-reward-high-quality.html" target="_blank">Penguin</a>, which was first launched in 2012 and today has an update.<br /> <br /> After a period of development and testing, we are now rolling out an update to the Penguin algorithm in all languages. Here are the key changes you'll see, which were also among webmasters' top requests to us:<br /> <br /> <ul style="text-align: left;"> <li><b>Penguin is now real-time.</b> Historically, the list of sites affected by Penguin was periodically refreshed at the same time. Once a webmaster considerably improved their site and its presence on the internet, many of Google's algorithms would take that into consideration very fast, but others, like Penguin, needed to be refreshed. With this change, Penguin's data is refreshed in real time, so changes will be visible much faster, typically taking effect shortly after we recrawl and reindex a page. It also means we're not going to comment on future refreshes.</li> <li><b>Penguin is now more granular.</b> Penguin now devalues spam by adjusting ranking based on spam signals, rather than affecting ranking of the whole site. </li> </ul> <br /> The web has significantly changed over the years, but as we said in our <a href="https://webmasters.googleblog.com/2012/04/another-step-to-reward-high-quality.html" target="_blank">original post</a>, webmasters should be free to focus on creating amazing, compelling websites. It's also important to remember that updates like Penguin are just one of more than 200 signals we use to determine rank.<br /> <br /> As always, if you have feedback, you can reach us on our <a href="https://support.google.com/webmasters/go/community" target="_blank">forums</a>, <a href="https://twitter.com/googlewmc" target="_blank">Twitter</a> and <a href="https://plus.google.com/+GoogleWebmasters" target="_blank">Google+</a>.<br /> <br /> <span class="byline-author">Posted by <a href="https://twitter.com/methode?rel=author" target="_blank">Gary Illyes</a>, Google Search Ranking Team</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"> Google's algorithms rely on more than 200 unique signals or "clues" that make it possible to surface what you might be looking for. These signals include things like the specific words that appear on websites, the freshness of content, your region and PageRank. One specific signal of the algorithms is called <a href="https://webmasters.googleblog.com/2012/04/another-step-to-reward-high-quality.html" target="_blank">Penguin</a>, which was first launched in 2012 and today has an update.<br /> <br /> After a period of development and testing, we are now rolling out an update to the Penguin algorithm in all languages. Here are the key changes you'll see, which were also among webmasters' top requests to us:<br /> <br /> <ul style="text-align: left;"> <li><b>Penguin is now real-time.</b> Historically, the list of sites affected by Penguin was periodically refreshed at the same time. Once a webmaster considerably improved their site and its presence on the internet, many of Google's algorithms would take that into consideration very fast, but others, like Penguin, needed to be refreshed. With this change, Penguin's data is refreshed in real time, so changes will be visible much faster, typically taking effect shortly after we recrawl and reindex a page. It also means we're not going to comment on future refreshes.</li> <li><b>Penguin is now more granular.</b> Penguin now devalues spam by adjusting ranking based on spam signals, rather than affecting ranking of the whole site. </li> </ul> <br /> The web has significantly changed over the years, but as we said in our <a href="https://webmasters.googleblog.com/2012/04/another-step-to-reward-high-quality.html" target="_blank">original post</a>, webmasters should be free to focus on creating amazing, compelling websites. It's also important to remember that updates like Penguin are just one of more than 200 signals we use to determine rank.<br /> <br /> As always, if you have feedback, you can reach us on our <a href="https://support.google.com/webmasters/go/community" target="_blank">forums</a>, <a href="https://twitter.com/googlewmc" target="_blank">Twitter</a> and <a href="https://plus.google.com/+GoogleWebmasters" target="_blank">Google+</a>.<br /> <br /> <span class="byline-author">Posted by <a href="https://twitter.com/methode?rel=author" target="_blank">Gary Illyes</a>, Google Search Ranking Team</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:Penguin is now part of our core algorithm&url=https://webmasters.googleblog.com/2016/09/penguin-is-now-part-of-our-core.html&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/penguin-is-now-part-of-our-core.html'> <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/penguin-is-now-part-of-our-core.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/search%20results' rel='tag'> search results </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' 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&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'> <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' rel='tag'> AMP </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly' rel='tag'> mobile-friendly </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results' rel='tag'> search results </a> </span> </div> </div> </div> <div class='post' data-id='8072541624946998941' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/09/how-to-best-evaluate-issues-with-your.html' itemprop='url' title='How to best evaluate issues with your Accelerated Mobile Pages'> How to best evaluate issues with your Accelerated Mobile Pages </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Monday, September 19, 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"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiFAkp0dsTx3dDGR5QYekMCtnV_UxVz3lGJQXjZDbJy-Gvt7NGD3yj8hQhLAxMAS0uR2KFRoXe3qFzApVWYUp19q105BCNpL9ZGwcy5ZD4Dd_Wzy99OBnVYtS2VPSHwmBqLrQPH/s1600/pasted+image+0+%25282%2529.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiFAkp0dsTx3dDGR5QYekMCtnV_UxVz3lGJQXjZDbJy-Gvt7NGD3yj8hQhLAxMAS0uR2KFRoXe3qFzApVWYUp19q105BCNpL9ZGwcy5ZD4Dd_Wzy99OBnVYtS2VPSHwmBqLrQPH/s640/pasted+image+0+%25282%2529.png" width="640" /></a> <p>As you #AMPlify your site with <a href="https://goo.gl/XSBxRm">Accelerated Mobile Pages</a>, it’s important to keep an eye periodically on the validation status of your pages, as only valid AMP pages are eligible to show on Google Search.</p> <p>When implementing AMP, sometimes pages will contain <a href="//goo.gl/vl1hSE">errors</a> causing them to not be indexed by Google Search. Pages may also contain warnings that are elements that are not best practice or are going to become errors in the future.</p> <p><a href="//goo.gl/nnDYHR">Google Search Console</a> is a free service that lets you check which of your AMP pages Google has <a href="//goo.gl/vV7tCS">identified as having errors</a>. Once you know which URLs are running into issues, there are a few handy tools that can make checking the validation error details easier.</p> <h3>1. Browser Developer Tools</h3> <p>To use Developer Tools for validation:</p> <ol><li>Open your AMP page in your browser</li> <li>Append "#development=1" to the URL, for example, http://localhost:8000/released.amp.html#development=1.</li> <li>Open the <a href="//goo.gl/GKPq1S">Chrome DevTools console</a> and check for validation errors.</li> </ol><br><p>Developer Console errors will look similar to this:</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgzZJv0vXmU9rRVKRKUmW3GA3VEgNJGbzZlmh_g5HwDrsyB_qmYMupeQAhfFAJtk9AeFoNr1Z0mmLfypZjPbTwMLOoagGs6XLhYywj_CSjbQiX0mM0o91r50jWdZYSnuwZuUhTK/s1600/validator_errors.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgzZJv0vXmU9rRVKRKUmW3GA3VEgNJGbzZlmh_g5HwDrsyB_qmYMupeQAhfFAJtk9AeFoNr1Z0mmLfypZjPbTwMLOoagGs6XLhYywj_CSjbQiX0mM0o91r50jWdZYSnuwZuUhTK/s640/validator_errors.png" width="640" /></a> <h3>2. AMP Browser Extensions</h3> <p>With the AMP Browser Extensions (available for <a href="//goo.gl/5kH1Vf">Chrome</a> and <a href="//goo.gl/x4vLI5">Opera</a>), you can quickly identify and debug invalid AMP pages. As you browse your site, the extension will evaluate each AMP page visited and give an indication of the validity of the page. </p> <table><colgroup><col width="50"><col width="568"></colgroup><tbody><tr><td><p><img alt="Red AMP icon indicating invalid AMP document." height="27" src="https://lh6.googleusercontent.com/sI5san0EGxe_23SdC4nTMy58bwp9LIJGd6_o7bIe1c93_91DfratFNJPcQf0e5f8VcwHAqk4sliu5Odld2Dqr-bPTVT9MeRTXzRwignifBkhhPugXiHJSV3uIct27bqmuy2N3A0K" width="27"></p> </td><td><p>When there are errors within an AMP page, the extension’s icon shows in a red color and displays the number of errors encountered.</p> </td></tr><tr><td><p><img alt="Green AMP icon indicating valid AMP document." height="27" src="https://lh4.googleusercontent.com/fGn3GXb-Kko-l6p_e2h2PjxfgPGWuL1sEUhLEFuuS_4_eghx-LXDXv6KGQo6WigTZBPEGUFPP2DnRJQ0FmrAyQvNCQz7mQwiwk32rdqZoupWDM4_niWAWaVJT6_B0AK9sGdgqzw4" width="27"></p> </td><td><p>When there are no errors within an AMP page, the icon shows in a green color and displays the number of warnings, if any exist.</p> </td></tr><tr><td><p><img alt="Blue AMP icon indicating AMP HTML variant if clicked." height="27" src="https://lh4.googleusercontent.com/LbO9LgDg_yxksFMrz6JgVocgP2MilOSjvPhoFTcsdTfVYbQTpdWkMD2wTrsV3ursT1evwSW45qyuEbFMK7goYgZlfbU_q469gSGqeC5uKxk5JM5wFjqt4jSIvzdzcY6vWSjrbCxJ" width="27"></p> </td><td><p>When the page isn’t AMP but the page indicates that an AMP version is available, the icon shows in a blue color with a link icon, and clicking on the extension will redirect the browser to the AMP version.</p> </td></tr></tbody></table> <p>Using the extensions means you can see what errors or warnings the page has by clicking on the extension icon. Every issue will list the source line, source column, and a message indicating what is wrong. When a more detailed description of the issue exists, a “Learn more” link will take you to the relevant page on <a href="https://ampproject.org/">ampproject.org</a>.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjRQLvZ9iFLdQ7efQLGX60V0m0nPUhTeE6rP3990Q8xwOF0cH5W-x8jxfQmytowqCXfZggpHr0eUajOOUwSe4DwvANuP5Yxd1OcKOeZxJzBAE0NPMadnxZSQMQ8Wah9AwSxuEci/s1600/screenshot.png-w%253D660.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjRQLvZ9iFLdQ7efQLGX60V0m0nPUhTeE6rP3990Q8xwOF0cH5W-x8jxfQmytowqCXfZggpHr0eUajOOUwSe4DwvANuP5Yxd1OcKOeZxJzBAE0NPMadnxZSQMQ8Wah9AwSxuEci/s640/screenshot.png-w%253D660.png" width="640" /></a> <h3>3. AMP Web Validator</h3> <p>The AMP Web Validator, available at <a href="//goo.gl/q5RH1y">validator.ampproject.org</a>, provides a simple web UI to test the validity of your AMP pages.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh2j2CtFMv5DwOhuMPSIi1otSngc7idF5LWfqhGt08Q3zIobT6XF5OF0dU6QZS8jNeXp9dLUe_frkFtNyJcR4AAGL2HodrPXGfpj3zdR7spFaz3_569jAtCASuxNfpsiIUoqOUQ/s1600/validator-web-ui-dance-dance-dance-dance.png-w%253D660.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh2j2CtFMv5DwOhuMPSIi1otSngc7idF5LWfqhGt08Q3zIobT6XF5OF0dU6QZS8jNeXp9dLUe_frkFtNyJcR4AAGL2HodrPXGfpj3zdR7spFaz3_569jAtCASuxNfpsiIUoqOUQ/s640/validator-web-ui-dance-dance-dance.png-w%253D660.png" width="640" /></a> <p>To use the tool, you enter an AMP URL, or copy/paste your source code, and the web validator displays error messages between the lines. You can make edits directly in the web validator which will trigger revalidation, letting you know if your proposed tweaks will fix the problem. </p> <p>What's your favourite way to check the status of your AMP Pages? Share your feedback in the comments below or on our <a href="//goo.gl/nOSQab">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/MH4Klu">Webmasters Help Forum</a>.</p> <br> <span class="byline-author">Posted by Tomo Taylor, AMP Community 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"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiFAkp0dsTx3dDGR5QYekMCtnV_UxVz3lGJQXjZDbJy-Gvt7NGD3yj8hQhLAxMAS0uR2KFRoXe3qFzApVWYUp19q105BCNpL9ZGwcy5ZD4Dd_Wzy99OBnVYtS2VPSHwmBqLrQPH/s1600/pasted+image+0+%25282%2529.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiFAkp0dsTx3dDGR5QYekMCtnV_UxVz3lGJQXjZDbJy-Gvt7NGD3yj8hQhLAxMAS0uR2KFRoXe3qFzApVWYUp19q105BCNpL9ZGwcy5ZD4Dd_Wzy99OBnVYtS2VPSHwmBqLrQPH/s640/pasted+image+0+%25282%2529.png" width="640" /></a> <p>As you #AMPlify your site with <a href="https://goo.gl/XSBxRm">Accelerated Mobile Pages</a>, it’s important to keep an eye periodically on the validation status of your pages, as only valid AMP pages are eligible to show on Google Search.</p> <p>When implementing AMP, sometimes pages will contain <a href="//goo.gl/vl1hSE">errors</a> causing them to not be indexed by Google Search. Pages may also contain warnings that are elements that are not best practice or are going to become errors in the future.</p> <p><a href="//goo.gl/nnDYHR">Google Search Console</a> is a free service that lets you check which of your AMP pages Google has <a href="//goo.gl/vV7tCS">identified as having errors</a>. Once you know which URLs are running into issues, there are a few handy tools that can make checking the validation error details easier.</p> <h3>1. Browser Developer Tools</h3> <p>To use Developer Tools for validation:</p> <ol><li>Open your AMP page in your browser</li> <li>Append "#development=1" to the URL, for example, http://localhost:8000/released.amp.html#development=1.</li> <li>Open the <a href="//goo.gl/GKPq1S">Chrome DevTools console</a> and check for validation errors.</li> </ol><br><p>Developer Console errors will look similar to this:</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgzZJv0vXmU9rRVKRKUmW3GA3VEgNJGbzZlmh_g5HwDrsyB_qmYMupeQAhfFAJtk9AeFoNr1Z0mmLfypZjPbTwMLOoagGs6XLhYywj_CSjbQiX0mM0o91r50jWdZYSnuwZuUhTK/s1600/validator_errors.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgzZJv0vXmU9rRVKRKUmW3GA3VEgNJGbzZlmh_g5HwDrsyB_qmYMupeQAhfFAJtk9AeFoNr1Z0mmLfypZjPbTwMLOoagGs6XLhYywj_CSjbQiX0mM0o91r50jWdZYSnuwZuUhTK/s640/validator_errors.png" width="640" /></a> <h3>2. AMP Browser Extensions</h3> <p>With the AMP Browser Extensions (available for <a href="//goo.gl/5kH1Vf">Chrome</a> and <a href="//goo.gl/x4vLI5">Opera</a>), you can quickly identify and debug invalid AMP pages. As you browse your site, the extension will evaluate each AMP page visited and give an indication of the validity of the page. </p> <table><colgroup><col width="50"><col width="568"></colgroup><tbody><tr><td><p><img alt="Red AMP icon indicating invalid AMP document." height="27" src="https://lh6.googleusercontent.com/sI5san0EGxe_23SdC4nTMy58bwp9LIJGd6_o7bIe1c93_91DfratFNJPcQf0e5f8VcwHAqk4sliu5Odld2Dqr-bPTVT9MeRTXzRwignifBkhhPugXiHJSV3uIct27bqmuy2N3A0K" width="27"></p> </td><td><p>When there are errors within an AMP page, the extension’s icon shows in a red color and displays the number of errors encountered.</p> </td></tr><tr><td><p><img alt="Green AMP icon indicating valid AMP document." height="27" src="https://lh4.googleusercontent.com/fGn3GXb-Kko-l6p_e2h2PjxfgPGWuL1sEUhLEFuuS_4_eghx-LXDXv6KGQo6WigTZBPEGUFPP2DnRJQ0FmrAyQvNCQz7mQwiwk32rdqZoupWDM4_niWAWaVJT6_B0AK9sGdgqzw4" width="27"></p> </td><td><p>When there are no errors within an AMP page, the icon shows in a green color and displays the number of warnings, if any exist.</p> </td></tr><tr><td><p><img alt="Blue AMP icon indicating AMP HTML variant if clicked." height="27" src="https://lh4.googleusercontent.com/LbO9LgDg_yxksFMrz6JgVocgP2MilOSjvPhoFTcsdTfVYbQTpdWkMD2wTrsV3ursT1evwSW45qyuEbFMK7goYgZlfbU_q469gSGqeC5uKxk5JM5wFjqt4jSIvzdzcY6vWSjrbCxJ" width="27"></p> </td><td><p>When the page isn’t AMP but the page indicates that an AMP version is available, the icon shows in a blue color with a link icon, and clicking on the extension will redirect the browser to the AMP version.</p> </td></tr></tbody></table> <p>Using the extensions means you can see what errors or warnings the page has by clicking on the extension icon. Every issue will list the source line, source column, and a message indicating what is wrong. When a more detailed description of the issue exists, a “Learn more” link will take you to the relevant page on <a href="https://ampproject.org/">ampproject.org</a>.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjRQLvZ9iFLdQ7efQLGX60V0m0nPUhTeE6rP3990Q8xwOF0cH5W-x8jxfQmytowqCXfZggpHr0eUajOOUwSe4DwvANuP5Yxd1OcKOeZxJzBAE0NPMadnxZSQMQ8Wah9AwSxuEci/s1600/screenshot.png-w%253D660.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjRQLvZ9iFLdQ7efQLGX60V0m0nPUhTeE6rP3990Q8xwOF0cH5W-x8jxfQmytowqCXfZggpHr0eUajOOUwSe4DwvANuP5Yxd1OcKOeZxJzBAE0NPMadnxZSQMQ8Wah9AwSxuEci/s640/screenshot.png-w%253D660.png" width="640" /></a> <h3>3. AMP Web Validator</h3> <p>The AMP Web Validator, available at <a href="//goo.gl/q5RH1y">validator.ampproject.org</a>, provides a simple web UI to test the validity of your AMP pages.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh2j2CtFMv5DwOhuMPSIi1otSngc7idF5LWfqhGt08Q3zIobT6XF5OF0dU6QZS8jNeXp9dLUe_frkFtNyJcR4AAGL2HodrPXGfpj3zdR7spFaz3_569jAtCASuxNfpsiIUoqOUQ/s1600/validator-web-ui-dance-dance-dance-dance.png-w%253D660.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh2j2CtFMv5DwOhuMPSIi1otSngc7idF5LWfqhGt08Q3zIobT6XF5OF0dU6QZS8jNeXp9dLUe_frkFtNyJcR4AAGL2HodrPXGfpj3zdR7spFaz3_569jAtCASuxNfpsiIUoqOUQ/s640/validator-web-ui-dance-dance-dance.png-w%253D660.png" width="640" /></a> <p>To use the tool, you enter an AMP URL, or copy/paste your source code, and the web validator displays error messages between the lines. You can make edits directly in the web validator which will trigger revalidation, letting you know if your proposed tweaks will fix the problem. </p> <p>What's your favourite way to check the status of your AMP Pages? Share your feedback in the comments below or on our <a href="//goo.gl/nOSQab">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/MH4Klu">Webmasters Help Forum</a>.</p> <br> <span class="byline-author">Posted by Tomo Taylor, AMP Community 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:How to best evaluate issues with your Accelerated Mobile Pages&url=https://webmasters.googleblog.com/2016/09/how-to-best-evaluate-issues-with-your.html&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-to-best-evaluate-issues-with-your.html'> <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-to-best-evaluate-issues-with-your.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' rel='tag'> AMP </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results' 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' 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&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'> <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' rel='tag'> AMP </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly' rel='tag'> mobile-friendly </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results' rel='tag'> search results </a> </span> </div> </div> </div> <div class='post' data-id='5927428095221050985' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/09/interested-in-accelerated-mobile-pages.html' itemprop='url' title='How to get started with Accelerated Mobile Pages'> How to get started with Accelerated Mobile Pages </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, September 14, 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/AVvXsEibHhzS0LA2aq11__tgqieW4VL-U5GzwTCtfN1Ix8tp-JvIHtJ6vO_AwqBVTK1zcmJv-olnVIpmG5JYLQ9ImRnKotSBVhMXlZsiv8e4xwPQRAjrQe5XbvH7BknNwr3Qp2OgvpV4/s1600/AMP-3.jpg" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEibHhzS0LA2aq11__tgqieW4VL-U5GzwTCtfN1Ix8tp-JvIHtJ6vO_AwqBVTK1zcmJv-olnVIpmG5JYLQ9ImRnKotSBVhMXlZsiv8e4xwPQRAjrQe5XbvH7BknNwr3Qp2OgvpV4/s640/AMP-3.jpg" width="640" /></a> <p>Interested in <a href="//goo.gl/NzEdct">Accelerated Mobile Pages</a> but not sure how to get started? AMPlifying your site for lightning speed might be easier than you think.</p> <p>If you use a Content Management System (CMS) like <a href="//goo.gl/d4FXBE">WordPress</a>, <a href="//goo.gl/41feAj">Drupal</a>, or <a href="//goo.gl/tYc0Q8">Hatena</a>, getting set up on AMP is as simple as installing and activating a plug-in. Each CMS has a slightly different approach to AMPlifying pages, so it’s worth checking with your provider on how to get started.</p> <p>On the other hand, if your site uses custom HTML, or you want to learn how AMP works under the hood, then check out the <a href="//goo.gl/4uUnY8">AMP Codelab</a> for a guided, hands-on coding experience designed to take you through the process of developing your first pages. The Codelab covers the fundamentals:</p> <ul><li>How AMP improves the user experience of the mobile web</li> <li>The foundations of an AMP page</li> <li>AMP limitations</li> <li>How AMP web components solve common problems</li> <li>How to validate your AMP pages</li> <li>How to prepare your AMP pages for Google Search</li></ul> <p>Once you are done with the basics, why not geek out with the <a href="https://goo.gl/7nDJA6">Advanced Concepts</a> Codelab?</p> <p>Have you tried the Codelabs or added an AMP plugin to your site? Share your feedback in the comments below or on our <a href="//goo.gl/c3m2Rl">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/rLGnyj">Webmasters Help Forum</a>.</p> <br> <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/AVvXsEibHhzS0LA2aq11__tgqieW4VL-U5GzwTCtfN1Ix8tp-JvIHtJ6vO_AwqBVTK1zcmJv-olnVIpmG5JYLQ9ImRnKotSBVhMXlZsiv8e4xwPQRAjrQe5XbvH7BknNwr3Qp2OgvpV4/s1600/AMP-3.jpg" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEibHhzS0LA2aq11__tgqieW4VL-U5GzwTCtfN1Ix8tp-JvIHtJ6vO_AwqBVTK1zcmJv-olnVIpmG5JYLQ9ImRnKotSBVhMXlZsiv8e4xwPQRAjrQe5XbvH7BknNwr3Qp2OgvpV4/s640/AMP-3.jpg" width="640" /></a> <p>Interested in <a href="//goo.gl/NzEdct">Accelerated Mobile Pages</a> but not sure how to get started? AMPlifying your site for lightning speed might be easier than you think.</p> <p>If you use a Content Management System (CMS) like <a href="//goo.gl/d4FXBE">WordPress</a>, <a href="//goo.gl/41feAj">Drupal</a>, or <a href="//goo.gl/tYc0Q8">Hatena</a>, getting set up on AMP is as simple as installing and activating a plug-in. Each CMS has a slightly different approach to AMPlifying pages, so it’s worth checking with your provider on how to get started.</p> <p>On the other hand, if your site uses custom HTML, or you want to learn how AMP works under the hood, then check out the <a href="//goo.gl/4uUnY8">AMP Codelab</a> for a guided, hands-on coding experience designed to take you through the process of developing your first pages. The Codelab covers the fundamentals:</p> <ul><li>How AMP improves the user experience of the mobile web</li> <li>The foundations of an AMP page</li> <li>AMP limitations</li> <li>How AMP web components solve common problems</li> <li>How to validate your AMP pages</li> <li>How to prepare your AMP pages for Google Search</li></ul> <p>Once you are done with the basics, why not geek out with the <a href="https://goo.gl/7nDJA6">Advanced Concepts</a> Codelab?</p> <p>Have you tried the Codelabs or added an AMP plugin to your site? Share your feedback in the comments below or on our <a href="//goo.gl/c3m2Rl">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/rLGnyj">Webmasters Help Forum</a>.</p> <br> <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:How to get started with Accelerated Mobile Pages&url=https://webmasters.googleblog.com/2016/09/interested-in-accelerated-mobile-pages.html&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/interested-in-accelerated-mobile-pages.html'> <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/interested-in-accelerated-mobile-pages.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/cms' rel='tag'> cms </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results' rel='tag'> search results </a> </span> </div> </div> </div> <div class='post' data-id='7758022644301167160' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/09/what-is-amp.html' itemprop='url' title='What is AMP?'> What is AMP? </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Monday, September 12, 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"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhj2OIFCTSKUAeq4r4RVEiKTECZukC0jLdPoUX64RZ9X0vsqgpl3NNcgjZ_IUteg9mKy5GhSduvXfUoH9l4j6HHbb2i60qBD8_0Bmr1aftg2j_TgHeTx8sTyLGLoAYrWhgrk1Qf/s1600/pasted+image+0.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhj2OIFCTSKUAeq4r4RVEiKTECZukC0jLdPoUX64RZ9X0vsqgpl3NNcgjZ_IUteg9mKy5GhSduvXfUoH9l4j6HHbb2i60qBD8_0Bmr1aftg2j_TgHeTx8sTyLGLoAYrWhgrk1Qf/s640/pasted+image+0.png" width="640" /></a> <p>Users today expect mobile websites to load super fast. The reality is that it can often take several seconds. It is no surprise that <a href="//goo.gl/XQ9Onc">40% of people abandon a website that takes more than 3 seconds to load</a>. To reduce the time content takes to get to a user’s mobile device <a href="//goo.gl/cH33ff">we started working</a> on the <a href="//goo.gl/DqimcE">Accelerated Mobile Pages Project</a>, an open source initiative to improve the mobile web experience for everyone.</p> <br><p>Accelerated Mobile Pages are HTML pages that take advantage of <a href="//goo.gl/bewQO0">various technical approaches</a> to prioritize speed and a faster experience for users by loading content almost instantaneously. </p> <p>Later this year, all types of sites that create AMP pages will have <a href="//goo.gl/ZLR2jG">expanded exposure</a> across the entire Google Mobile Search results page, like e-commerce, entertainment, travel, recipe sites and many more. Visit the <a href="//goo.gl/ulnXqD">“Who” page</a> on AMPProject.org for a flavour of some of the sites already creating AMP content and try the demo at (<a href="https://g.co/ampdemo">g.co/ampdemo</a>) to see AMP versions of pages labeled with <img alt="The AMP Logo" height="18" src="https://lh6.googleusercontent.com/6-1RhJIelZVssBenhLIKYeU10obKDjMtaP-SxG768BetsOqheMQxX4XFUcJ5cypwPgT2PoTJdaY1Xgy4ybbTNJXYY3BiELLxF9wDg2i6jKLX4mxtHny-DEafEcWIm-jufOHoFhUt" style="margin:0" width="50">. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhGdDOHw-Yqn-EYntbFiPoQEv7ah-hNY9dsrbataxwsvROBU8pObPbr_iUZ42WySeI66cgSCHhz_DJLcVlf4ExIdz88tn1uEXvznswF6BhPPOcktKWyYrM6LlTeomsSCpCqf_3g/s1600/ampexample1.gif" imageanchor="1" ><img border="0" height="640" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhGdDOHw-Yqn-EYntbFiPoQEv7ah-hNY9dsrbataxwsvROBU8pObPbr_iUZ42WySeI66cgSCHhz_DJLcVlf4ExIdz88tn1uEXvznswF6BhPPOcktKWyYrM6LlTeomsSCpCqf_3g/s640/ampexample1.gif" width="188" /></a> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLLujlzK_n8zFm1r5qYZBrXvrRod-fR_OcsMyOoEYWNpIphp1SJfVoLTB79pIx20OTu93SicGFAEOjsM20VwVtwF4Uoh_FzUmo5an1akvRhEEdn63YRjuOMh8KlLOVCmUXLu3Q/s1600/ampexample2.gif" imageanchor="1" ><img border="0" height="640" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLLujlzK_n8zFm1r5qYZBrXvrRod-fR_OcsMyOoEYWNpIphp1SJfVoLTB79pIx20OTu93SicGFAEOjsM20VwVtwF4Uoh_FzUmo5an1akvRhEEdn63YRjuOMh8KlLOVCmUXLu3Q/s640/ampexample2.gif" width="188" /></a> </p> <p>In advance of AMP expanding in Google Search, over the next few weeks we’ll be posting pointers to help you #AMPlify your site. Follow along with the #AMPlify hashtag on <a href="//goo.gl/hXNBQK">G+</a> and <a href="//goo.gl/GVmcXv">Twitter</a>.</p> <br><p>Have you already built AMP pages for your site? Share your feedback in the comments below or on our <a href="//goo.gl/8MHxZ8">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/KDuMw2">Webmasters Help Forum</a>.</p> <span class="byline-author">Posted by Tomo Taylor, AMP Community 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"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhj2OIFCTSKUAeq4r4RVEiKTECZukC0jLdPoUX64RZ9X0vsqgpl3NNcgjZ_IUteg9mKy5GhSduvXfUoH9l4j6HHbb2i60qBD8_0Bmr1aftg2j_TgHeTx8sTyLGLoAYrWhgrk1Qf/s1600/pasted+image+0.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhj2OIFCTSKUAeq4r4RVEiKTECZukC0jLdPoUX64RZ9X0vsqgpl3NNcgjZ_IUteg9mKy5GhSduvXfUoH9l4j6HHbb2i60qBD8_0Bmr1aftg2j_TgHeTx8sTyLGLoAYrWhgrk1Qf/s640/pasted+image+0.png" width="640" /></a> <p>Users today expect mobile websites to load super fast. The reality is that it can often take several seconds. It is no surprise that <a href="//goo.gl/XQ9Onc">40% of people abandon a website that takes more than 3 seconds to load</a>. To reduce the time content takes to get to a user’s mobile device <a href="//goo.gl/cH33ff">we started working</a> on the <a href="//goo.gl/DqimcE">Accelerated Mobile Pages Project</a>, an open source initiative to improve the mobile web experience for everyone.</p> <br><p>Accelerated Mobile Pages are HTML pages that take advantage of <a href="//goo.gl/bewQO0">various technical approaches</a> to prioritize speed and a faster experience for users by loading content almost instantaneously. </p> <p>Later this year, all types of sites that create AMP pages will have <a href="//goo.gl/ZLR2jG">expanded exposure</a> across the entire Google Mobile Search results page, like e-commerce, entertainment, travel, recipe sites and many more. Visit the <a href="//goo.gl/ulnXqD">“Who” page</a> on AMPProject.org for a flavour of some of the sites already creating AMP content and try the demo at (<a href="https://g.co/ampdemo">g.co/ampdemo</a>) to see AMP versions of pages labeled with <img alt="The AMP Logo" height="18" src="https://lh6.googleusercontent.com/6-1RhJIelZVssBenhLIKYeU10obKDjMtaP-SxG768BetsOqheMQxX4XFUcJ5cypwPgT2PoTJdaY1Xgy4ybbTNJXYY3BiELLxF9wDg2i6jKLX4mxtHny-DEafEcWIm-jufOHoFhUt" style="margin:0" width="50">. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhGdDOHw-Yqn-EYntbFiPoQEv7ah-hNY9dsrbataxwsvROBU8pObPbr_iUZ42WySeI66cgSCHhz_DJLcVlf4ExIdz88tn1uEXvznswF6BhPPOcktKWyYrM6LlTeomsSCpCqf_3g/s1600/ampexample1.gif" imageanchor="1" ><img border="0" height="640" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhGdDOHw-Yqn-EYntbFiPoQEv7ah-hNY9dsrbataxwsvROBU8pObPbr_iUZ42WySeI66cgSCHhz_DJLcVlf4ExIdz88tn1uEXvznswF6BhPPOcktKWyYrM6LlTeomsSCpCqf_3g/s640/ampexample1.gif" width="188" /></a> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLLujlzK_n8zFm1r5qYZBrXvrRod-fR_OcsMyOoEYWNpIphp1SJfVoLTB79pIx20OTu93SicGFAEOjsM20VwVtwF4Uoh_FzUmo5an1akvRhEEdn63YRjuOMh8KlLOVCmUXLu3Q/s1600/ampexample2.gif" imageanchor="1" ><img border="0" height="640" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLLujlzK_n8zFm1r5qYZBrXvrRod-fR_OcsMyOoEYWNpIphp1SJfVoLTB79pIx20OTu93SicGFAEOjsM20VwVtwF4Uoh_FzUmo5an1akvRhEEdn63YRjuOMh8KlLOVCmUXLu3Q/s640/ampexample2.gif" width="188" /></a> </p> <p>In advance of AMP expanding in Google Search, over the next few weeks we’ll be posting pointers to help you #AMPlify your site. Follow along with the #AMPlify hashtag on <a href="//goo.gl/hXNBQK">G+</a> and <a href="//goo.gl/GVmcXv">Twitter</a>.</p> <br><p>Have you already built AMP pages for your site? Share your feedback in the comments below or on our <a href="//goo.gl/8MHxZ8">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/KDuMw2">Webmasters Help Forum</a>.</p> <span class="byline-author">Posted by Tomo Taylor, AMP Community 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:What is AMP?&url=https://webmasters.googleblog.com/2016/09/what-is-amp.html&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/what-is-amp.html'> <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/what-is-amp.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' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results' rel='tag'> search results </a> </span> </div> </div> </div> <div class='post' data-id='4167734948893950297' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/09/a-reminder-about-widget-links.html' itemprop='url' title='A reminder about widget links'> A reminder about widget links </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, September 08, 2016 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p>Google has long taken a <a href="https://webmasters.googleblog.com/2013/02/a-reminder-about-selling-links.html">strong stance</a> <a href="https://webmasters.googleblog.com/2012/07/new-notifications-about-inbound-links.html">against links</a> <a href="https://webmasters.googleblog.com/2008/10/linking-out-often-its-just-applying.html">that manipulate a site’s PageRank</a>. Today we would like to reiterate our policy on the creation of keyword-rich, hidden or low-quality links embedded in widgets that are distributed across various sites.</p> <p>Widgets can help website owners enrich the experience of their site and engage users. However, some widgets add links to a site that a webmaster did not editorially place and contain anchor text that the webmaster does not control. Because these links are not naturally placed, they're considered a violation of Google Webmaster Guidelines.</p> <p>Below you can find the examples of widgets which contain links that violate Google Webmaster Guidelines:</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgrgQ2xUDZpY4U0I-N-7HXWGGrDUNCfe3czMpEsALfBR-6Ml80LmYv0-QuENid6nrovIGKnX9ZB72b5n_B3VIFdhkSId9MnAnKtW-DzywQSqfbNXOxomj4r0T4NFsyZBJYZbGZh/s1600/awesomewidgetwinwin.png" imageanchor="1" ><img border="0" height="306" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgrgQ2xUDZpY4U0I-N-7HXWGGrDUNCfe3czMpEsALfBR-6Ml80LmYv0-QuENid6nrovIGKnX9ZB72b5n_B3VIFdhkSId9MnAnKtW-DzywQSqfbNXOxomj4r0T4NFsyZBJYZbGZh/s320/awesomewidgetwinwin.png" width="320" /></a> <br> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjrqZvlLvufF-TQOyouKn5Wy2_cJNukCWdSf-E7HgUTNovSZLlUHUcJRy9M5xd9nQGAwZ0hblyoKkYGBH7vjP17dxUjZYq_tgtzL30mZbeuA6wB8OumAa5du9OnDwQnVYNZZs7A/s1600/somanyvisitorssuchwow.png" imageanchor="1" ><img border="0" height="174" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjrqZvlLvufF-TQOyouKn5Wy2_cJNukCWdSf-E7HgUTNovSZLlUHUcJRy9M5xd9nQGAwZ0hblyoKkYGBH7vjP17dxUjZYq_tgtzL30mZbeuA6wB8OumAa5du9OnDwQnVYNZZs7A/s320/somanyvisitorssuchwow.png" width="320" /></a> <br> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjDMX81HID7LiNbA6L_P3H0avJfT6OPRS3zxG1qOJOGZY3demomvDEswDMJIbSY47jGkab9QqtjH6nXEyG-BQQ9r9KpCU6squgYrCKwcERfbRRV9nl4MwQRTM8OgPA7FmdMupwk/s1600/nevergonnaletyoudownnevergonnagiveyoucatvideos.png" imageanchor="1" ><img border="0" height="290" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjDMX81HID7LiNbA6L_P3H0avJfT6OPRS3zxG1qOJOGZY3demomvDEswDMJIbSY47jGkab9QqtjH6nXEyG-BQQ9r9KpCU6squgYrCKwcERfbRRV9nl4MwQRTM8OgPA7FmdMupwk/s320/nevergonnaletyoudownnevergonnagiveyoucatvideos.png" width="320" /></a> </p> <p>Google's webspam team may take <a href="https://support.google.com/webmasters/answer/2604824">manual actions</a> on <a href="https://support.google.com/webmasters/answer/66356">unnatural links</a>. When a manual action is taken, Google will notify the site owners through <a href="https://www.google.com/webmasters/tools/">Search Console</a>. If you receive such a warning for unnatural links to your site and you use links in widgets to promote your site, we recommend resolving these issues and requesting reconsideration. </p> <p>You can resolve issues with unnatural links by making sure they don't pass PageRank. To do this, add a rel="nofollow" attribute on the widget links or remove the links entirely. After fixing or removing widget links and any other unnatural links to your site, let Google know about your change by <a href="https://www.google.com/webmasters/tools/reconsideration">submitting a reconsideration request in Search Console</a>. Once the request has been reviewed, you'll get a notification about whether the reconsideration request was successful or not.</p> <p>Also, we would like to remind webmasters who use widgets on their sites to check those widgets for any unnatural links. Add a rel="nofollow" attribute on those unnatural links or remove the links entirely from the widget.</p> <p>For more information, please watch our <a href="https://www.youtube.com/watch?v=chuhSmwsL7s">video about widget links</a> and refer to our <a href="https://support.google.com/webmasters/answer/66356">Webmaster Guidelines on Link Schemes</a>. Additionally, feel free to ask questions in our <a href="https://support.google.com/webmasters/go/community">Webmaster Help Forums</a>, where a community of webmasters can help with their experience.</p> <br> <span class="byline-author">Posted by Agnieszka Łata, Trust & Safety Search Team and Eric Kuan, Webmaster Relations Specialist</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p>Google has long taken a <a href="https://webmasters.googleblog.com/2013/02/a-reminder-about-selling-links.html">strong stance</a> <a href="https://webmasters.googleblog.com/2012/07/new-notifications-about-inbound-links.html">against links</a> <a href="https://webmasters.googleblog.com/2008/10/linking-out-often-its-just-applying.html">that manipulate a site’s PageRank</a>. Today we would like to reiterate our policy on the creation of keyword-rich, hidden or low-quality links embedded in widgets that are distributed across various sites.</p> <p>Widgets can help website owners enrich the experience of their site and engage users. However, some widgets add links to a site that a webmaster did not editorially place and contain anchor text that the webmaster does not control. Because these links are not naturally placed, they're considered a violation of Google Webmaster Guidelines.</p> <p>Below you can find the examples of widgets which contain links that violate Google Webmaster Guidelines:</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgrgQ2xUDZpY4U0I-N-7HXWGGrDUNCfe3czMpEsALfBR-6Ml80LmYv0-QuENid6nrovIGKnX9ZB72b5n_B3VIFdhkSId9MnAnKtW-DzywQSqfbNXOxomj4r0T4NFsyZBJYZbGZh/s1600/awesomewidgetwinwin.png" imageanchor="1" ><img border="0" height="306" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgrgQ2xUDZpY4U0I-N-7HXWGGrDUNCfe3czMpEsALfBR-6Ml80LmYv0-QuENid6nrovIGKnX9ZB72b5n_B3VIFdhkSId9MnAnKtW-DzywQSqfbNXOxomj4r0T4NFsyZBJYZbGZh/s320/awesomewidgetwinwin.png" width="320" /></a> <br> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjrqZvlLvufF-TQOyouKn5Wy2_cJNukCWdSf-E7HgUTNovSZLlUHUcJRy9M5xd9nQGAwZ0hblyoKkYGBH7vjP17dxUjZYq_tgtzL30mZbeuA6wB8OumAa5du9OnDwQnVYNZZs7A/s1600/somanyvisitorssuchwow.png" imageanchor="1" ><img border="0" height="174" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjrqZvlLvufF-TQOyouKn5Wy2_cJNukCWdSf-E7HgUTNovSZLlUHUcJRy9M5xd9nQGAwZ0hblyoKkYGBH7vjP17dxUjZYq_tgtzL30mZbeuA6wB8OumAa5du9OnDwQnVYNZZs7A/s320/somanyvisitorssuchwow.png" width="320" /></a> <br> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjDMX81HID7LiNbA6L_P3H0avJfT6OPRS3zxG1qOJOGZY3demomvDEswDMJIbSY47jGkab9QqtjH6nXEyG-BQQ9r9KpCU6squgYrCKwcERfbRRV9nl4MwQRTM8OgPA7FmdMupwk/s1600/nevergonnaletyoudownnevergonnagiveyoucatvideos.png" imageanchor="1" ><img border="0" height="290" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjDMX81HID7LiNbA6L_P3H0avJfT6OPRS3zxG1qOJOGZY3demomvDEswDMJIbSY47jGkab9QqtjH6nXEyG-BQQ9r9KpCU6squgYrCKwcERfbRRV9nl4MwQRTM8OgPA7FmdMupwk/s320/nevergonnaletyoudownnevergonnagiveyoucatvideos.png" width="320" /></a> </p> <p>Google's webspam team may take <a href="https://support.google.com/webmasters/answer/2604824">manual actions</a> on <a href="https://support.google.com/webmasters/answer/66356">unnatural links</a>. When a manual action is taken, Google will notify the site owners through <a href="https://www.google.com/webmasters/tools/">Search Console</a>. If you receive such a warning for unnatural links to your site and you use links in widgets to promote your site, we recommend resolving these issues and requesting reconsideration. </p> <p>You can resolve issues with unnatural links by making sure they don't pass PageRank. To do this, add a rel="nofollow" attribute on the widget links or remove the links entirely. After fixing or removing widget links and any other unnatural links to your site, let Google know about your change by <a href="https://www.google.com/webmasters/tools/reconsideration">submitting a reconsideration request in Search Console</a>. Once the request has been reviewed, you'll get a notification about whether the reconsideration request was successful or not.</p> <p>Also, we would like to remind webmasters who use widgets on their sites to check those widgets for any unnatural links. Add a rel="nofollow" attribute on those unnatural links or remove the links entirely from the widget.</p> <p>For more information, please watch our <a href="https://www.youtube.com/watch?v=chuhSmwsL7s">video about widget links</a> and refer to our <a href="https://support.google.com/webmasters/answer/66356">Webmaster Guidelines on Link Schemes</a>. Additionally, feel free to ask questions in our <a href="https://support.google.com/webmasters/go/community">Webmaster Help Forums</a>, where a community of webmasters can help with their experience.</p> <br> <span class="byline-author">Posted by Agnieszka Łata, Trust & Safety Search Team and Eric Kuan, Webmaster Relations Specialist</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 reminder about widget links&url=https://webmasters.googleblog.com/2016/09/a-reminder-about-widget-links.html&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/a-reminder-about-widget-links.html'> <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/a-reminder-about-widget-links.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/search%20console' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines' rel='tag'> webmaster guidelines </a> </span> </div> </div> </div> <div class='post' data-id='7076517119196509645' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/09/showcase-your-sites-reviews-in-search.html' itemprop='url' title='Showcase your site’s reviews in Search'> Showcase your site’s reviews in Search </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, September 07, 2016 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> Today, we’re introducing Reviews from the web to local Knowledge Panels, to accompany our <a href="https://search.googleblog.com/2016/08/never-miss-must-try-with-google-search.html">recently launched</a> best-of lists and critic reviews features. Whether your site publishes editorial critic reviews, best-of places lists, or aggregates user ratings, this content can be featured in local Knowledge Panels when users are looking for places to go. <br /> <br /> <b>Reviews from the web</b><br /> Available globally on mobile and desktop, Reviews from the web brings aggregated user ratings of up to three review sites to Knowledge Panels for local places across many verticals including shops, restaurants, parks and more. <br /> <br /> By implementing <a href="https://developers.google.com/search/docs/data-types/reviews#type_definitions">review snippet markup</a> and meeting <a href="https://developers.google.com/search/docs/data-types/reviews#review-snippet-guidelines">our criteria</a>, your site’s user-generated composite ratings will be eligible for inclusion. Add the <a href="https://developers.google.com/search/docs/data-types/reviews#review-subject-properties">Local Business markup</a> to help Google match reviews to the right review subject and help grow your site’s coverage. For more information on the guidelines for the Reviews from the web, critic review and top places lists features, check out our <a href="https://developers.google.com/">developer site</a>.<br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://2.bp.blogspot.com/-3bXXtw28IbI/V9AbgNA0pBI/AAAAAAAAehg/5992LxULzMUYFVl8HKXZIYfomFqho4zfACLcB/s1600/local2.png" imageanchor="1" ><img border="0" height="640" src="https://2.bp.blogspot.com/-3bXXtw28IbI/V9AbgNA0pBI/AAAAAAAAehg/5992LxULzMUYFVl8HKXZIYfomFqho4zfACLcB/s640/local2.png" width="316" /></a> </div> <b>Critic reviews</b><br /> In the U.S. on mobile and desktop, qualifying publishers can participate in the <a href="https://webmasters.googleblog.com/2016/08/promote-your-local-businesses-reviews.html">critic review feature</a> in local Knowledge Panels. Critic reviews possess an editorial tone of voice and have an opinionated position on the local business, coming from an editor or on-the-ground expert. For more information on how to participate, see the details in our <a href="https://developers.google.com/search/docs/data-types/reviews#critic-reviews">critic reviews page</a>. <br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEivfl4yc6B9RR8m4bjJH78pvVpj2_Yh52pi4vcDjnstJtTaQO-yOE1WMiBB4eNZNCIeuBMoxz0BjJ5mpnXaQP0KBgKBTPhTsGJ2JQhbi6qwvDa_59YqqRozI_lgSHWpcANRvLe0_A/s1600/local2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="640" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEivfl4yc6B9RR8m4bjJH78pvVpj2_Yh52pi4vcDjnstJtTaQO-yOE1WMiBB4eNZNCIeuBMoxz0BjJ5mpnXaQP0KBgKBTPhTsGJ2JQhbi6qwvDa_59YqqRozI_lgSHWpcANRvLe0_A/s640/local2.png" width="316" /></a></div> The local information across Google Search helps millions of people, every day, discover and share great places. If you have any questions, please visit our <a href="https://support.google.com/webmasters/go/community">webmaster forums</a>.<br /> <br /> <span class="byline-author">Posted by Ronnie Falcon, Product Manager </span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> Today, we’re introducing Reviews from the web to local Knowledge Panels, to accompany our <a href="https://search.googleblog.com/2016/08/never-miss-must-try-with-google-search.html">recently launched</a> best-of lists and critic reviews features. Whether your site publishes editorial critic reviews, best-of places lists, or aggregates user ratings, this content can be featured in local Knowledge Panels when users are looking for places to go. <br /> <br /> <b>Reviews from the web</b><br /> Available globally on mobile and desktop, Reviews from the web brings aggregated user ratings of up to three review sites to Knowledge Panels for local places across many verticals including shops, restaurants, parks and more. <br /> <br /> By implementing <a href="https://developers.google.com/search/docs/data-types/reviews#type_definitions">review snippet markup</a> and meeting <a href="https://developers.google.com/search/docs/data-types/reviews#review-snippet-guidelines">our criteria</a>, your site’s user-generated composite ratings will be eligible for inclusion. Add the <a href="https://developers.google.com/search/docs/data-types/reviews#review-subject-properties">Local Business markup</a> to help Google match reviews to the right review subject and help grow your site’s coverage. For more information on the guidelines for the Reviews from the web, critic review and top places lists features, check out our <a href="https://developers.google.com/">developer site</a>.<br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://2.bp.blogspot.com/-3bXXtw28IbI/V9AbgNA0pBI/AAAAAAAAehg/5992LxULzMUYFVl8HKXZIYfomFqho4zfACLcB/s1600/local2.png" imageanchor="1" ><img border="0" height="640" src="https://2.bp.blogspot.com/-3bXXtw28IbI/V9AbgNA0pBI/AAAAAAAAehg/5992LxULzMUYFVl8HKXZIYfomFqho4zfACLcB/s640/local2.png" width="316" /></a> </div> <b>Critic reviews</b><br /> In the U.S. on mobile and desktop, qualifying publishers can participate in the <a href="https://webmasters.googleblog.com/2016/08/promote-your-local-businesses-reviews.html">critic review feature</a> in local Knowledge Panels. Critic reviews possess an editorial tone of voice and have an opinionated position on the local business, coming from an editor or on-the-ground expert. For more information on how to participate, see the details in our <a href="https://developers.google.com/search/docs/data-types/reviews#critic-reviews">critic reviews page</a>. <br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEivfl4yc6B9RR8m4bjJH78pvVpj2_Yh52pi4vcDjnstJtTaQO-yOE1WMiBB4eNZNCIeuBMoxz0BjJ5mpnXaQP0KBgKBTPhTsGJ2JQhbi6qwvDa_59YqqRozI_lgSHWpcANRvLe0_A/s1600/local2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="640" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEivfl4yc6B9RR8m4bjJH78pvVpj2_Yh52pi4vcDjnstJtTaQO-yOE1WMiBB4eNZNCIeuBMoxz0BjJ5mpnXaQP0KBgKBTPhTsGJ2JQhbi6qwvDa_59YqqRozI_lgSHWpcANRvLe0_A/s640/local2.png" width="316" /></a></div> The local information across Google Search helps millions of people, every day, discover and share great places. If you have any questions, please visit our <a href="https://support.google.com/webmasters/go/community">webmaster forums</a>.<br /> <br /> <span class="byline-author">Posted by Ronnie Falcon, Product 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:Showcase your site’s reviews in Search&url=https://webmasters.googleblog.com/2016/09/showcase-your-sites-reviews-in-search.html&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/showcase-your-sites-reviews-in-search.html'> <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/showcase-your-sites-reviews-in-search.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/search%20results' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data' rel='tag'> structured data </a> </span> </div> </div> </div> <div class='post' data-id='4567342074701691164' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/09/more-safe-browsing-help-for-webmasters.html' itemprop='url' title='More Safe Browsing Help for Webmasters'> More Safe Browsing Help for Webmasters </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, September 07, 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"> (Crossposted from the <a href="https://security.googleblog.com/2016/09/more-safe-browsing-help-for-webmasters.html">Google Security Blog</a>.) <br /> For more than <a href="https://webmasters.googleblog.com/2007/08/malware-reviews-via-webmaster-tools.html">nine years</a>, Safe Browsing has helped webmasters via Search Console with information about how to fix security issues with their sites. This includes relevant Help Center articles, example URLs to assist in diagnosing the presence of harmful content, and a process for webmasters to request reviews of their site after security issues are addressed. Over time, Safe Browsing has expanded its protection to cover additional threats to user safety such as <a href="https://security.googleblog.com/2015/11/safe-browsing-protection-from-even-more.html">Deceptive Sites</a> and <a href="https://security.googleblog.com/2015/02/more-protection-from-unwanted-software.html">Unwanted Software</a>.<br /> <br /> To help webmasters be even more successful in resolving issues, we’re happy to announce that we’ve updated the information available in Search Console in the Security Issues report.<br /> <br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhx1F0SR3iTk-xx04A-hptdaXos48AMMHl13dxL2iTBkpuJyVHnuQ4hhmPpEUg4A-3men87Yb4cFSsCcvawoHjjCEWRv2NnkLLJjhoWhZ6jNRmaTVHqEHZs8tM6l6mH-SBCHA7e/s1600/Screen+Shot+2016-08-26+at+1.04.29+PM.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhx1F0SR3iTk-xx04A-hptdaXos48AMMHl13dxL2iTBkpuJyVHnuQ4hhmPpEUg4A-3men87Yb4cFSsCcvawoHjjCEWRv2NnkLLJjhoWhZ6jNRmaTVHqEHZs8tM6l6mH-SBCHA7e/s640/Screen+Shot+2016-08-26+at+1.04.29+PM.png" width="640" /></a> </div> <div class="separator" style="clear: both; text-align: center;"> <br /></div> The updated information provides more specific explanations of six different security issues detected by Safe Browsing, including <a href="https://developers.google.com/webmasters/hacked/">malware</a>, <a href="https://support.google.com/webmasters/answer/6350487">deceptive pages</a>, <a href="https://support.google.com/webmasters/answer/3258249">harmful downloads</a>, and <a href="https://support.google.com/webmasters/answer/3258249#if_uncommon">uncommon downloads</a>. These explanations give webmasters more context and detail about what Safe Browsing found. We also offer tailored recommendations for each type of issue, including sample URLs that webmasters can check to identify the source of the issue, as well as specific remediation actions webmasters can take to resolve the issue.<br /> <br /> We on the Safe Browsing team definitely recommend <a href="https://support.google.com/webmasters/topic/4564315">registering</a> your site in Search Console even if it is not currently experiencing a security issue. We send notifications through Search Console so webmasters can address any issues that appear <a href="http://research.google.com/pubs/pub44924.html">as quickly as possible</a>.<br /> <br /> Our goal is to help webmasters provide a safe and secure browsing experience for their users. We welcome any questions or feedback about the new features on the <a href="https://support.google.com/webmasters/go/community">Google Webmaster Help Forum</a>, where <a href="https://topcontributor.withgoogle.com/">Top Contributors</a> and Google employees are available to help.<br /> <br /> For more information about Safe Browsing’s ongoing work to shine light on the state of web security and encourage safer web security practices, check out our summary of trends and findings on the <a href="https://www.google.com/transparencyreport/safebrowsing/">Safe Browsing Transparency Report</a>. If you’re interested in the tools Google provides for webmasters and developers dealing with hacked sites, this <a href="https://www.youtube.com/watch?v=mbJvL61DOZg">video</a> provides a great overview. <br /> <span class="byline-author">Posted by Kelly Hope Harrington, Safe Browsing Team</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"> (Crossposted from the <a href="https://security.googleblog.com/2016/09/more-safe-browsing-help-for-webmasters.html">Google Security Blog</a>.) <br /> For more than <a href="https://webmasters.googleblog.com/2007/08/malware-reviews-via-webmaster-tools.html">nine years</a>, Safe Browsing has helped webmasters via Search Console with information about how to fix security issues with their sites. This includes relevant Help Center articles, example URLs to assist in diagnosing the presence of harmful content, and a process for webmasters to request reviews of their site after security issues are addressed. Over time, Safe Browsing has expanded its protection to cover additional threats to user safety such as <a href="https://security.googleblog.com/2015/11/safe-browsing-protection-from-even-more.html">Deceptive Sites</a> and <a href="https://security.googleblog.com/2015/02/more-protection-from-unwanted-software.html">Unwanted Software</a>.<br /> <br /> To help webmasters be even more successful in resolving issues, we’re happy to announce that we’ve updated the information available in Search Console in the Security Issues report.<br /> <br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhx1F0SR3iTk-xx04A-hptdaXos48AMMHl13dxL2iTBkpuJyVHnuQ4hhmPpEUg4A-3men87Yb4cFSsCcvawoHjjCEWRv2NnkLLJjhoWhZ6jNRmaTVHqEHZs8tM6l6mH-SBCHA7e/s1600/Screen+Shot+2016-08-26+at+1.04.29+PM.png" imageanchor="1" ><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhx1F0SR3iTk-xx04A-hptdaXos48AMMHl13dxL2iTBkpuJyVHnuQ4hhmPpEUg4A-3men87Yb4cFSsCcvawoHjjCEWRv2NnkLLJjhoWhZ6jNRmaTVHqEHZs8tM6l6mH-SBCHA7e/s640/Screen+Shot+2016-08-26+at+1.04.29+PM.png" width="640" /></a> </div> <div class="separator" style="clear: both; text-align: center;"> <br /></div> The updated information provides more specific explanations of six different security issues detected by Safe Browsing, including <a href="https://developers.google.com/webmasters/hacked/">malware</a>, <a href="https://support.google.com/webmasters/answer/6350487">deceptive pages</a>, <a href="https://support.google.com/webmasters/answer/3258249">harmful downloads</a>, and <a href="https://support.google.com/webmasters/answer/3258249#if_uncommon">uncommon downloads</a>. These explanations give webmasters more context and detail about what Safe Browsing found. We also offer tailored recommendations for each type of issue, including sample URLs that webmasters can check to identify the source of the issue, as well as specific remediation actions webmasters can take to resolve the issue.<br /> <br /> We on the Safe Browsing team definitely recommend <a href="https://support.google.com/webmasters/topic/4564315">registering</a> your site in Search Console even if it is not currently experiencing a security issue. We send notifications through Search Console so webmasters can address any issues that appear <a href="http://research.google.com/pubs/pub44924.html">as quickly as possible</a>.<br /> <br /> Our goal is to help webmasters provide a safe and secure browsing experience for their users. We welcome any questions or feedback about the new features on the <a href="https://support.google.com/webmasters/go/community">Google Webmaster Help Forum</a>, where <a href="https://topcontributor.withgoogle.com/">Top Contributors</a> and Google employees are available to help.<br /> <br /> For more information about Safe Browsing’s ongoing work to shine light on the state of web security and encourage safer web security practices, check out our summary of trends and findings on the <a href="https://www.google.com/transparencyreport/safebrowsing/">Safe Browsing Transparency Report</a>. If you’re interested in the tools Google provides for webmasters and developers dealing with hacked sites, this <a href="https://www.youtube.com/watch?v=mbJvL61DOZg">video</a> provides a great overview. <br /> <span class="byline-author">Posted by Kelly Hope Harrington, Safe Browsing Team</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:More Safe Browsing Help for Webmasters&url=https://webmasters.googleblog.com/2016/09/more-safe-browsing-help-for-webmasters.html&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/more-safe-browsing-help-for-webmasters.html'> <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/more-safe-browsing-help-for-webmasters.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/hacked%20sites' rel='tag'> hacked sites </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/malware' rel='tag'> malware </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/security' rel='tag'> security </a> </span> </div> </div> </div> <div class='post' data-id='6671989203026825778' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/08/helping-users-easily-access-content-on.html' itemprop='url' title='Helping users easily access content on mobile'> Helping users easily access content on mobile </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, August 23, 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><i><b>January 10, 2017 update</b>: Starting today, pages where content is not easily accessible to a user on the transition from the mobile search results may not rank as high. As we said, this new signal is just one of hundreds of signals that are used in ranking and the intent of the search query is still a very strong signal, so a page may still rank highly if it has great, relevant content. Please head to the <a href="https://g.co/webmasterhelpforum">webmaster forums</a> if you have any questions. </i></p> <hr> <p>In Google Search, our goal is to help users quickly find the best answers to their questions, regardless of the device they’re using. Today, we’re announcing two upcoming changes to mobile search results that make finding content easier for users.</p> <h3>Simplifying mobile search results</h3> <p>Two years ago, we added a <a href="https://webmasters.googleblog.com/2014/11/helping-users-find-mobile-friendly-pages.html">mobile-friendly label</a> to help users find pages where the text and content was readable without zooming and the tap targets were appropriately spaced. Since then, we’ve seen the ecosystem evolve and we recently found that 85% of all pages in the mobile search results now meet this criteria and show the mobile-friendly label. To keep search results uncluttered, we’ll be removing the label, although the mobile-friendly criteria will continue to be a ranking signal. We’ll continue providing the <a href="https://www.google.com/webmasters/tools/mobile-usability">mobile usability report</a> in Search Console and the <a href="https://www.google.com/webmasters/tools/mobile-friendly/">mobile-friendly test</a> to help webmasters evaluate the effect of the mobile-friendly signal on their pages.</p> <h3>Helping users find the content they’re looking for</h3> <p>Although the majority of pages now have text and content on the page that is readable without zooming, we’ve recently seen many examples where these pages show intrusive interstitials to users. While the underlying content is present on the page and available to be indexed by Google, content may be visually obscured by an interstitial. This can frustrate users because they are unable to easily access the content that they were expecting when they tapped on the search result. </p> <p>Pages that show intrusive interstitials provide a poorer experience to users than other pages where content is immediately accessible. This can be problematic on mobile devices where screens are often smaller. To improve the mobile search experience, after January 10, 2017, pages where content is not easily accessible to a user on the transition from the mobile search results may not rank as highly. </p> <p>Here are some examples of techniques that make content less accessible to a user:</p> <ul><li>Showing a popup that covers the main content, either immediately after the user navigates to a page from the search results, or while they are looking through the page.</li></ul> <ul><li>Displaying a standalone interstitial that the user has to dismiss before accessing the main content.</li> <li>Using a layout where the above-the-fold portion of the page appears similar to a standalone interstitial, but the original content has been inlined underneath the fold. </li></ul> <h3>Examples of interstitials that make content less accessible</h3> <div style="float:left; width:180px"> <a href="https://2.bp.blogspot.com/-dqV7ahVFcOk/V7xvnb0DIQI/AAAAAAAAeS4/E610UnF-Np0CXRAkkdbbzDLjfbzjBf98QCLcB/s1600/t1i1.png" imageanchor="1" ><img border="0" height="320" src="https://2.bp.blogspot.com/-dqV7ahVFcOk/V7xvnb0DIQI/AAAAAAAAeS4/E610UnF-Np0CXRAkkdbbzDLjfbzjBf98QCLcB/s320/t1i1.png" width="176" /></a> <br>An example of an intrusive popup </div> <div style="float:left; width:180px"> <a href="https://2.bp.blogspot.com/-R4dBJmw3NFU/V7xvoLqiHLI/AAAAAAAAeTA/ELJtmkGIpnoWF1OqDzNFinbJPzlP2-X5wCLcB/s1600/t1i2.png" imageanchor="1" ><img border="0" height="320" src="https://2.bp.blogspot.com/-R4dBJmw3NFU/V7xvoLqiHLI/AAAAAAAAeTA/ELJtmkGIpnoWF1OqDzNFinbJPzlP2-X5wCLcB/s320/t1i2.png" width="176" /></a> <br>An example of an intrusive standalone interstitial </div> <div style="float:left; width:180px"> <a href="https://1.bp.blogspot.com/-Vr20lkcZVd8/V7xvnvEE0lI/AAAAAAAAeS8/fjFhiWO2RIodGAdL__CJfCxWG61gyI9FACLcB/s1600/t1i3.png" imageanchor="1" ><img border="0" height="320" src="https://1.bp.blogspot.com/-Vr20lkcZVd8/V7xvnvEE0lI/AAAAAAAAeS8/fjFhiWO2RIodGAdL__CJfCxWG61gyI9FACLcB/s320/t1i3.png" width="176" /></a> <br>Another example of an intrusive standalone interstitial </div> <p style="clear:both;"> </p> <p>By contrast, here are some examples of techniques that, used responsibly, would not be affected by the new signal:</p> <ul><li>Interstitials that appear to be in response to a legal obligation, such as for cookie usage or for age verification.</li> <li>Login dialogs on sites where content is not publicly indexable. For example, this would include private content such as email or unindexable content that is behind a paywall.</li> <li>Banners that use a reasonable amount of screen space and are easily dismissible. For example, the app install banners provided by Safari and Chrome are examples of banners that use a reasonable amount of screen space.</li></ul> <h3>Examples of interstitials that would not be affected by the new signal, if used responsibly</h3> <div style="float:left; width:180px"> <a href="https://3.bp.blogspot.com/-zp6z9z_I3-A/V7xxn1KfQZI/AAAAAAAAeTM/h4pHYwbKTFMzb4lfWrh5iLf_ULqOa4yqgCLcB/s1600/t2i1.png" imageanchor="1" ><img border="0" height="320" src="https://3.bp.blogspot.com/-zp6z9z_I3-A/V7xxn1KfQZI/AAAAAAAAeTM/h4pHYwbKTFMzb4lfWrh5iLf_ULqOa4yqgCLcB/s320/t2i1.png" width="176" /></a> <br>An example of an interstitial for cookie usage </div> <div style="float:left; width:180px"> <a href="https://3.bp.blogspot.com/-gjgfeSOqXfQ/V7xxoOUpG4I/AAAAAAAAeTU/tv8H7xfg1xYuWioihQtuYLVhDuw57ptQwCLcB/s1600/t2i2.png" imageanchor="1" ><img border="0" height="320" src="https://3.bp.blogspot.com/-gjgfeSOqXfQ/V7xxoOUpG4I/AAAAAAAAeTU/tv8H7xfg1xYuWioihQtuYLVhDuw57ptQwCLcB/s320/t2i2.png" width="176" /></a> <br>An example of an interstitial for age verification </div> <div style="float:left; width:180px"> <a href="https://1.bp.blogspot.com/-VB85oWnMAi8/V7xxoMTEmTI/AAAAAAAAeTQ/GpH1f2RX14I17MW6OAreKRd4v9TuF0R-wCLcB/s1600/t2i3.png" imageanchor="1" ><img border="0" height="320" src="https://1.bp.blogspot.com/-VB85oWnMAi8/V7xxoMTEmTI/AAAAAAAAeTQ/GpH1f2RX14I17MW6OAreKRd4v9TuF0R-wCLcB/s320/t2i3.png" width="176" /></a> <br>An example of a banner that uses a reasonable amount of screen space </div> <p style="clear:both;"> </p> <p>We previously explored a signal that checked for interstitials that ask a user to install a mobile app. As we continued our development efforts, we saw the need to broaden our focus to interstitials more generally. Accordingly, to avoid duplication in our signals, we've removed the check for app-install interstitials from the mobile-friendly test and have incorporated it into this new signal in Search.</p> <p>Remember, this new signal is just one of hundreds of signals that are used in ranking. The intent of the search query is still a very strong signal, so a page may still rank highly if it has great, relevant content. As always, if you have any questions or feedback, please visit our <a href="https://support.google.com/webmasters/go/community">webmaster forums</a>. </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><i><b>January 10, 2017 update</b>: Starting today, pages where content is not easily accessible to a user on the transition from the mobile search results may not rank as high. As we said, this new signal is just one of hundreds of signals that are used in ranking and the intent of the search query is still a very strong signal, so a page may still rank highly if it has great, relevant content. Please head to the <a href="https://g.co/webmasterhelpforum">webmaster forums</a> if you have any questions. </i></p> <hr> <p>In Google Search, our goal is to help users quickly find the best answers to their questions, regardless of the device they’re using. Today, we’re announcing two upcoming changes to mobile search results that make finding content easier for users.</p> <h3>Simplifying mobile search results</h3> <p>Two years ago, we added a <a href="https://webmasters.googleblog.com/2014/11/helping-users-find-mobile-friendly-pages.html">mobile-friendly label</a> to help users find pages where the text and content was readable without zooming and the tap targets were appropriately spaced. Since then, we’ve seen the ecosystem evolve and we recently found that 85% of all pages in the mobile search results now meet this criteria and show the mobile-friendly label. To keep search results uncluttered, we’ll be removing the label, although the mobile-friendly criteria will continue to be a ranking signal. We’ll continue providing the <a href="https://www.google.com/webmasters/tools/mobile-usability">mobile usability report</a> in Search Console and the <a href="https://www.google.com/webmasters/tools/mobile-friendly/">mobile-friendly test</a> to help webmasters evaluate the effect of the mobile-friendly signal on their pages.</p> <h3>Helping users find the content they’re looking for</h3> <p>Although the majority of pages now have text and content on the page that is readable without zooming, we’ve recently seen many examples where these pages show intrusive interstitials to users. While the underlying content is present on the page and available to be indexed by Google, content may be visually obscured by an interstitial. This can frustrate users because they are unable to easily access the content that they were expecting when they tapped on the search result. </p> <p>Pages that show intrusive interstitials provide a poorer experience to users than other pages where content is immediately accessible. This can be problematic on mobile devices where screens are often smaller. To improve the mobile search experience, after January 10, 2017, pages where content is not easily accessible to a user on the transition from the mobile search results may not rank as highly. </p> <p>Here are some examples of techniques that make content less accessible to a user:</p> <ul><li>Showing a popup that covers the main content, either immediately after the user navigates to a page from the search results, or while they are looking through the page.</li></ul> <ul><li>Displaying a standalone interstitial that the user has to dismiss before accessing the main content.</li> <li>Using a layout where the above-the-fold portion of the page appears similar to a standalone interstitial, but the original content has been inlined underneath the fold. </li></ul> <h3>Examples of interstitials that make content less accessible</h3> <div style="float:left; width:180px"> <a href="https://2.bp.blogspot.com/-dqV7ahVFcOk/V7xvnb0DIQI/AAAAAAAAeS4/E610UnF-Np0CXRAkkdbbzDLjfbzjBf98QCLcB/s1600/t1i1.png" imageanchor="1" ><img border="0" height="320" src="https://2.bp.blogspot.com/-dqV7ahVFcOk/V7xvnb0DIQI/AAAAAAAAeS4/E610UnF-Np0CXRAkkdbbzDLjfbzjBf98QCLcB/s320/t1i1.png" width="176" /></a> <br>An example of an intrusive popup </div> <div style="float:left; width:180px"> <a href="https://2.bp.blogspot.com/-R4dBJmw3NFU/V7xvoLqiHLI/AAAAAAAAeTA/ELJtmkGIpnoWF1OqDzNFinbJPzlP2-X5wCLcB/s1600/t1i2.png" imageanchor="1" ><img border="0" height="320" src="https://2.bp.blogspot.com/-R4dBJmw3NFU/V7xvoLqiHLI/AAAAAAAAeTA/ELJtmkGIpnoWF1OqDzNFinbJPzlP2-X5wCLcB/s320/t1i2.png" width="176" /></a> <br>An example of an intrusive standalone interstitial </div> <div style="float:left; width:180px"> <a href="https://1.bp.blogspot.com/-Vr20lkcZVd8/V7xvnvEE0lI/AAAAAAAAeS8/fjFhiWO2RIodGAdL__CJfCxWG61gyI9FACLcB/s1600/t1i3.png" imageanchor="1" ><img border="0" height="320" src="https://1.bp.blogspot.com/-Vr20lkcZVd8/V7xvnvEE0lI/AAAAAAAAeS8/fjFhiWO2RIodGAdL__CJfCxWG61gyI9FACLcB/s320/t1i3.png" width="176" /></a> <br>Another example of an intrusive standalone interstitial </div> <p style="clear:both;"> </p> <p>By contrast, here are some examples of techniques that, used responsibly, would not be affected by the new signal:</p> <ul><li>Interstitials that appear to be in response to a legal obligation, such as for cookie usage or for age verification.</li> <li>Login dialogs on sites where content is not publicly indexable. For example, this would include private content such as email or unindexable content that is behind a paywall.</li> <li>Banners that use a reasonable amount of screen space and are easily dismissible. For example, the app install banners provided by Safari and Chrome are examples of banners that use a reasonable amount of screen space.</li></ul> <h3>Examples of interstitials that would not be affected by the new signal, if used responsibly</h3> <div style="float:left; width:180px"> <a href="https://3.bp.blogspot.com/-zp6z9z_I3-A/V7xxn1KfQZI/AAAAAAAAeTM/h4pHYwbKTFMzb4lfWrh5iLf_ULqOa4yqgCLcB/s1600/t2i1.png" imageanchor="1" ><img border="0" height="320" src="https://3.bp.blogspot.com/-zp6z9z_I3-A/V7xxn1KfQZI/AAAAAAAAeTM/h4pHYwbKTFMzb4lfWrh5iLf_ULqOa4yqgCLcB/s320/t2i1.png" width="176" /></a> <br>An example of an interstitial for cookie usage </div> <div style="float:left; width:180px"> <a href="https://3.bp.blogspot.com/-gjgfeSOqXfQ/V7xxoOUpG4I/AAAAAAAAeTU/tv8H7xfg1xYuWioihQtuYLVhDuw57ptQwCLcB/s1600/t2i2.png" imageanchor="1" ><img border="0" height="320" src="https://3.bp.blogspot.com/-gjgfeSOqXfQ/V7xxoOUpG4I/AAAAAAAAeTU/tv8H7xfg1xYuWioihQtuYLVhDuw57ptQwCLcB/s320/t2i2.png" width="176" /></a> <br>An example of an interstitial for age verification </div> <div style="float:left; width:180px"> <a href="https://1.bp.blogspot.com/-VB85oWnMAi8/V7xxoMTEmTI/AAAAAAAAeTQ/GpH1f2RX14I17MW6OAreKRd4v9TuF0R-wCLcB/s1600/t2i3.png" imageanchor="1" ><img border="0" height="320" src="https://1.bp.blogspot.com/-VB85oWnMAi8/V7xxoMTEmTI/AAAAAAAAeTQ/GpH1f2RX14I17MW6OAreKRd4v9TuF0R-wCLcB/s320/t2i3.png" width="176" /></a> <br>An example of a banner that uses a reasonable amount of screen space </div> <p style="clear:both;"> </p> <p>We previously explored a signal that checked for interstitials that ask a user to install a mobile app. As we continued our development efforts, we saw the need to broaden our focus to interstitials more generally. Accordingly, to avoid duplication in our signals, we've removed the check for app-install interstitials from the mobile-friendly test and have incorporated it into this new signal in Search.</p> <p>Remember, this new signal is just one of hundreds of signals that are used in ranking. The intent of the search query is still a very strong signal, so a page may still rank highly if it has great, relevant content. As always, if you have any questions or feedback, please visit our <a href="https://support.google.com/webmasters/go/community">webmaster forums</a>. </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:Helping users easily access content on mobile&url=https://webmasters.googleblog.com/2016/08/helping-users-easily-access-content-on.html&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/08/helping-users-easily-access-content-on.html'> <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/08/helping-users-easily-access-content-on.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> </div> </div> </div> <div class='post' data-id='7806613617944687352' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/08/promote-your-local-businesses-reviews.html' itemprop='url' title='Promote your local businesses reviews with schema.org markup '> Promote your local businesses reviews with schema.org markup </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Friday, August 12, 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"> Since the launch of <a href="https://developers.googleblog.com/2015/08/using-schemaorg-markup-to-promote-your.html">critic reviews</a> last year, we have been focused on supporting more types of reviews, like restaurant reviews, cafes, or any other type of a local business. Recently we’ve <a href="https://search.googleblog.com/2016/08/never-miss-must-try-with-google-search.html">announced</a> the availability of critic reviews for local businesses. By incorporating structured data to their sites, publishers can promote their content on <a href="https://www.google.com/search?q=per%20se%20restaurant&hl=en&gl=us">local Knowledge Graph cards</a> and users can enjoy a range of reviews and opinions. </p> <p>Critic reviews are available across mobile, tablet and desktop, allowing publishers to increase the visibility of their reviews and expose their reviews to new audiences, whenever a local Knowledge Graph card is surfaced. English reviews for businesses in the US are already supported and we’ll very soon support many other languages and countries.</p> <div style="text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh1D-_GPBWmFncW43iSsBsEkm3IVA6djXP7UbCpoQjhdm2NsvvOS6y3hBoZ-9w2HiqMpT_fML-eI8ZZXJKLOoqaZuYXuIDop_rzuHI9ZhCBwVNf6Byy-s9uCgu338flGvPV-9dV/s1600/critic-reviews.png" imageanchor="1"><img border="0" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh1D-_GPBWmFncW43iSsBsEkm3IVA6djXP7UbCpoQjhdm2NsvvOS6y3hBoZ-9w2HiqMpT_fML-eI8ZZXJKLOoqaZuYXuIDop_rzuHI9ZhCBwVNf6Byy-s9uCgu338flGvPV-9dV/s480/critic-reviews.png" /></a></div> <p>Publishers with critic reviews for local entities can get up and running by selecting snippets of reviews from their sites and annotating them and the associated business with schema.org markup. This process, detailed in our <a href="https://developers.google.com/search/docs/data-types/reviews">critic reviews markup instructions</a>, allows publishers to communicate to Google which snippet they prefer, what URL is associated with the review and other metadata about the local business that allows us to ensure that we’re showing the right review for the right entity.</p> <p>Google can understand a variety of markup formats, including the JSON-LD data format, which makes it easier than ever to incorporate structured data about reviews into webpages! Publishers can get started <a href="https://developers.google.com/search/docs/data-types/reviews">here</a>. And as always, if you have any questions, please visit our <a href="https://support.google.com/webmasters/go/community">webmaster forums</a>. </p> <span class="byline-author">Posted by Jaeho Kang, 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"> Since the launch of <a href="https://developers.googleblog.com/2015/08/using-schemaorg-markup-to-promote-your.html">critic reviews</a> last year, we have been focused on supporting more types of reviews, like restaurant reviews, cafes, or any other type of a local business. Recently we’ve <a href="https://search.googleblog.com/2016/08/never-miss-must-try-with-google-search.html">announced</a> the availability of critic reviews for local businesses. By incorporating structured data to their sites, publishers can promote their content on <a href="https://www.google.com/search?q=per%20se%20restaurant&hl=en&gl=us">local Knowledge Graph cards</a> and users can enjoy a range of reviews and opinions. </p> <p>Critic reviews are available across mobile, tablet and desktop, allowing publishers to increase the visibility of their reviews and expose their reviews to new audiences, whenever a local Knowledge Graph card is surfaced. English reviews for businesses in the US are already supported and we’ll very soon support many other languages and countries.</p> <div style="text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh1D-_GPBWmFncW43iSsBsEkm3IVA6djXP7UbCpoQjhdm2NsvvOS6y3hBoZ-9w2HiqMpT_fML-eI8ZZXJKLOoqaZuYXuIDop_rzuHI9ZhCBwVNf6Byy-s9uCgu338flGvPV-9dV/s1600/critic-reviews.png" imageanchor="1"><img border="0" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh1D-_GPBWmFncW43iSsBsEkm3IVA6djXP7UbCpoQjhdm2NsvvOS6y3hBoZ-9w2HiqMpT_fML-eI8ZZXJKLOoqaZuYXuIDop_rzuHI9ZhCBwVNf6Byy-s9uCgu338flGvPV-9dV/s480/critic-reviews.png" /></a></div> <p>Publishers with critic reviews for local entities can get up and running by selecting snippets of reviews from their sites and annotating them and the associated business with schema.org markup. This process, detailed in our <a href="https://developers.google.com/search/docs/data-types/reviews">critic reviews markup instructions</a>, allows publishers to communicate to Google which snippet they prefer, what URL is associated with the review and other metadata about the local business that allows us to ensure that we’re showing the right review for the right entity.</p> <p>Google can understand a variety of markup formats, including the JSON-LD data format, which makes it easier than ever to incorporate structured data about reviews into webpages! Publishers can get started <a href="https://developers.google.com/search/docs/data-types/reviews">here</a>. And as always, if you have any questions, please visit our <a href="https://support.google.com/webmasters/go/community">webmaster forums</a>. </p> <span class="byline-author">Posted by Jaeho Kang, 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:Promote your local businesses reviews with schema.org markup &url=https://webmasters.googleblog.com/2016/08/promote-your-local-businesses-reviews.html&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/08/promote-your-local-businesses-reviews.html'> <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/08/promote-your-local-businesses-reviews.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/search%20results' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data' rel='tag'> structured data </a> </span> </div> </div> </div> <div class='post' data-id='4196026901062674440' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/08/amp-your-content-preview-of-amped.html' itemprop='url' title='AMP your content - A Preview of AMP'ed results in Search'> AMP your content - A Preview of AMP'ed results in Search </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, August 02, 2016 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p>It's 2016 and it's hard to believe that browsing the web on a mobile phone can still feel so slow with users abandoning sites that just don't load quickly. To us — and many in the industry — it was clear that something needed to change. That was why <a href="https://googleblog.blogspot.com/2015/10/introducing-accelerated-mobile-pages.html">we started working</a> with the <a href="https://www.ampproject.org">Accelerated Mobile Pages Project</a>, an open source initiative to improve the mobile web experience for everyone. </p> <p>Less than <a href="https://googleblog.blogspot.com/2016/02/amping-up-in-mobile-search.html">six months ago</a>, we started sending people to AMP pages in the “Top stories” section of the Google Search Results page on mobile phones. Since then, we’ve seen incredible global adoption of AMP that has gone beyond the news industry to include e-commerce, entertainment, travel, recipe sites and so on. To date we have more than 150 million AMP docs in our index, with over 4 million new ones being added every week. As a result, today we’re sharing an <a href="//g.co/ampdemo">early preview</a> of our expanded AMP support across the entire search results page --not just the “Top stories” section.</p> <p>To clarify, this is not a ranking change for sites. As a result of the growth of AMP beyond publishers, we wanted to make it easier for people to access this faster experience. The preview shows an experience where web results that that have AMP versions are labeled with <img alt="The AMP Logo" border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEixZiCHY8U0wLJOh0Kcejee5TAFx6nseFi7k_Xl2MB6-3uvpjRtM4xZ-_S0Xh8udC7B-Dal0TnROfl31eoTJoSFHZgPEw0GgZrPqdamgJzsKH5pTd3JBFyTo_SdNO7O1KvxxNKb/s1600/AMP_logo.png" style="margin:0" />. When you tap on these results, you will be directed to the corresponding AMP page within the AMP viewer. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjEfKjUpdO_wKTYjGPMt0RfxERI7NOlvk2oTw91Z20-fqrmsMM3szacoKtwDaLG7YBWarailh5Cbuc441L3IpV6ZbAKH6HB8vWuimuLh25S16K1G1fcXnVyQbpX9mtSFrmGN6bZ/s1600/ampexample1.gif" imageanchor="1" ><img border="0" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjEfKjUpdO_wKTYjGPMt0RfxERI7NOlvk2oTw91Z20-fqrmsMM3szacoKtwDaLG7YBWarailh5Cbuc441L3IpV6ZbAKH6HB8vWuimuLh25S16K1G1fcXnVyQbpX9mtSFrmGN6bZ/s480/ampexample1.gif" style="margin:0" /></a> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhrVpfkLMoy-kjkMbqt0WsF7sHHuCLekDBwEfYfC6_Px1g0GTcdr2MMQl4CFv1itfR_zkbVvegahd6TIQyao1MRzySpSJ9G0dlBBWb8EmD19ZKWZrVtrRqL0ecAxjo08ZgiXaiO/s1600/ampexample2.gif" imageanchor="1" ><img border="0" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhrVpfkLMoy-kjkMbqt0WsF7sHHuCLekDBwEfYfC6_Px1g0GTcdr2MMQl4CFv1itfR_zkbVvegahd6TIQyao1MRzySpSJ9G0dlBBWb8EmD19ZKWZrVtrRqL0ecAxjo08ZgiXaiO/s480/ampexample2.gif" style="margin:0" /></a> <br> <i>AMP in Search Preview</i> </p> <p>Try it out for yourself on your mobile device by navigating to <a href="//g.co/ampdemo">g.co/ampdemo</a>. Once you’re in the demo, search for something like “french toast recipe” or music lyrics by your favorite artist to experience how AMP can provide a speedier reading experience on the mobile web. <a href="https://ampproject.org/who">The “Who” page</a> on AMPProject.org has a flavor of some of the sites already creating AMP content.</p> <p>We’re starting with a preview to get feedback from users, developers and sites so that we can create a better Search experience when we make this feature more broadly available later this year. In addition, we want to give everyone who might be interested in “AMPing up” their content enough time to learn <a href="https://support.google.com/webmasters/answer/6340290">how to implement AMP</a> and to see how their content appears in the demo. And beyond developing AMP pages, we invite everyone to <a href="https://github.com/ampproject/amphtml">get involved</a> and contribute to the AMP Project.</p> <p>We can’t wait to hear from you as we work together to speed up the web. And as always, if you have any questions, please visit our <a href="https://support.google.com/webmasters/go/community">webmaster forums</a>. </p> <br> <span class="byline-author">Posted by Nick Zukoski, Software Engineer</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p>It's 2016 and it's hard to believe that browsing the web on a mobile phone can still feel so slow with users abandoning sites that just don't load quickly. To us — and many in the industry — it was clear that something needed to change. That was why <a href="https://googleblog.blogspot.com/2015/10/introducing-accelerated-mobile-pages.html">we started working</a> with the <a href="https://www.ampproject.org">Accelerated Mobile Pages Project</a>, an open source initiative to improve the mobile web experience for everyone. </p> <p>Less than <a href="https://googleblog.blogspot.com/2016/02/amping-up-in-mobile-search.html">six months ago</a>, we started sending people to AMP pages in the “Top stories” section of the Google Search Results page on mobile phones. Since then, we’ve seen incredible global adoption of AMP that has gone beyond the news industry to include e-commerce, entertainment, travel, recipe sites and so on. To date we have more than 150 million AMP docs in our index, with over 4 million new ones being added every week. As a result, today we’re sharing an <a href="//g.co/ampdemo">early preview</a> of our expanded AMP support across the entire search results page --not just the “Top stories” section.</p> <p>To clarify, this is not a ranking change for sites. As a result of the growth of AMP beyond publishers, we wanted to make it easier for people to access this faster experience. The preview shows an experience where web results that that have AMP versions are labeled with <img alt="The AMP Logo" border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEixZiCHY8U0wLJOh0Kcejee5TAFx6nseFi7k_Xl2MB6-3uvpjRtM4xZ-_S0Xh8udC7B-Dal0TnROfl31eoTJoSFHZgPEw0GgZrPqdamgJzsKH5pTd3JBFyTo_SdNO7O1KvxxNKb/s1600/AMP_logo.png" style="margin:0" />. When you tap on these results, you will be directed to the corresponding AMP page within the AMP viewer. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjEfKjUpdO_wKTYjGPMt0RfxERI7NOlvk2oTw91Z20-fqrmsMM3szacoKtwDaLG7YBWarailh5Cbuc441L3IpV6ZbAKH6HB8vWuimuLh25S16K1G1fcXnVyQbpX9mtSFrmGN6bZ/s1600/ampexample1.gif" imageanchor="1" ><img border="0" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjEfKjUpdO_wKTYjGPMt0RfxERI7NOlvk2oTw91Z20-fqrmsMM3szacoKtwDaLG7YBWarailh5Cbuc441L3IpV6ZbAKH6HB8vWuimuLh25S16K1G1fcXnVyQbpX9mtSFrmGN6bZ/s480/ampexample1.gif" style="margin:0" /></a> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhrVpfkLMoy-kjkMbqt0WsF7sHHuCLekDBwEfYfC6_Px1g0GTcdr2MMQl4CFv1itfR_zkbVvegahd6TIQyao1MRzySpSJ9G0dlBBWb8EmD19ZKWZrVtrRqL0ecAxjo08ZgiXaiO/s1600/ampexample2.gif" imageanchor="1" ><img border="0" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhrVpfkLMoy-kjkMbqt0WsF7sHHuCLekDBwEfYfC6_Px1g0GTcdr2MMQl4CFv1itfR_zkbVvegahd6TIQyao1MRzySpSJ9G0dlBBWb8EmD19ZKWZrVtrRqL0ecAxjo08ZgiXaiO/s480/ampexample2.gif" style="margin:0" /></a> <br> <i>AMP in Search Preview</i> </p> <p>Try it out for yourself on your mobile device by navigating to <a href="//g.co/ampdemo">g.co/ampdemo</a>. Once you’re in the demo, search for something like “french toast recipe” or music lyrics by your favorite artist to experience how AMP can provide a speedier reading experience on the mobile web. <a href="https://ampproject.org/who">The “Who” page</a> on AMPProject.org has a flavor of some of the sites already creating AMP content.</p> <p>We’re starting with a preview to get feedback from users, developers and sites so that we can create a better Search experience when we make this feature more broadly available later this year. In addition, we want to give everyone who might be interested in “AMPing up” their content enough time to learn <a href="https://support.google.com/webmasters/answer/6340290">how to implement AMP</a> and to see how their content appears in the demo. And beyond developing AMP pages, we invite everyone to <a href="https://github.com/ampproject/amphtml">get involved</a> and contribute to the AMP Project.</p> <p>We can’t wait to hear from you as we work together to speed up the web. And as always, if you have any questions, please visit our <a href="https://support.google.com/webmasters/go/community">webmaster forums</a>. </p> <br> <span class="byline-author">Posted by Nick Zukoski, Software Engineer</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:AMP your content - A Preview of AMP'ed results in Search&url=https://webmasters.googleblog.com/2016/08/amp-your-content-preview-of-amped.html&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/08/amp-your-content-preview-of-amped.html'> <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/08/amp-your-content-preview-of-amped.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' rel='tag'> AMP </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results' rel='tag'> search results </a> </span> </div> </div> </div> <div class='blog-pager' id='blog-pager'> <a class='home-link' href='https://webmasters.googleblog.com/'> <i class='material-icons'>  </i> </a> <span id='blog-pager-newer-link'> <a class='blog-pager-newer-link' href='https://webmasters.googleblog.com/search?updated-max=2017-04-18T03:48:00-07:00&max-results=7&reverse-paginate=true' id='Blog1_blog-pager-newer-link' title='Newer Posts'> <i class='material-icons'>  </i> </a> </span> <span id='blog-pager-older-link'> <a class='blog-pager-older-link' href='https://webmasters.googleblog.com/search?updated-max=2016-08-02T10:07:00-07:00&max-results=7' 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'> accessibility </a> <span dir='ltr'> 10 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/advanced'> advanced </a> <span dir='ltr'> 195 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/AMP'> AMP </a> <span dir='ltr'> 13 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Android'> Android </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/API'> API </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/apps'> apps </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/autocomplete'> autocomplete </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/beginner'> beginner </a> <span dir='ltr'> 173 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/CAPTCHA'> CAPTCHA </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Chrome'> Chrome </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/cms'> cms </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing'> crawling and indexing </a> <span dir='ltr'> 158 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/encryption'> encryption </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/events'> events </a> <span dir='ltr'> 51 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication'> feedback and communication </a> <span dir='ltr'> 83 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/forums'> forums </a> <span dir='ltr'> 5 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/general%20tips'> general tips </a> <span dir='ltr'> 90 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/geotargeting'> geotargeting </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20Assistant'> Google Assistant </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20I%2FO'> Google I/O </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20Images'> Google Images </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20News'> Google News </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hacked%20sites'> hacked sites </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hangout'> hangout </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hreflang'> hreflang </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/https'> https </a> <span dir='ltr'> 5 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/images'> images </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/intermediate'> intermediate </a> <span dir='ltr'> 205 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/interstitials'> interstitials </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/javascript'> javascript </a> <span dir='ltr'> 8 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/job%20search'> job search </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/localization'> localization </a> <span dir='ltr'> 21 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/malware'> malware </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/mobile'> mobile </a> <span dir='ltr'> 63 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/mobile-friendly'> mobile-friendly </a> <span dir='ltr'> 14 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/nohacked'> nohacked </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/performance'> performance </a> <span dir='ltr'> 17 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/product%20expert'> product expert </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/product%20experts'> product experts </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/products%20and%20services'> products and services </a> <span dir='ltr'> 63 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/questions'> questions </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/ranking'> ranking </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/recipes'> recipes </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rendering'> rendering </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Responsive%20Web%20Design'> Responsive Web Design </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rich%20cards'> rich cards </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rich%20results'> rich results </a> <span dir='ltr'> 10 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20console'> search console </a> <span dir='ltr'> 35 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20for%20beginners'> search for beginners </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20queries'> search queries </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20results'> search results </a> <span dir='ltr'> 140 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/security'> security </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/seo'> seo </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/sitemaps'> sitemaps </a> <span dir='ltr'> 46 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/speed'> speed </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/structured%20data'> structured data </a> <span dir='ltr'> 33 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/summit'> summit </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/TLDs'> TLDs </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/url%20removals'> url removals </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/UX'> UX </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/verification'> verification </a> <span dir='ltr'> 8 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/video'> video </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20community'> webmaster community </a> <span dir='ltr'> 24 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20forum'> webmaster forum </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines'> webmaster guidelines </a> <span dir='ltr'> 57 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20tools'> webmaster tools </a> <span dir='ltr'> 177 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmasters'> webmasters </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/youtube%20channel'> 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 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/2020/'> 2020 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/11/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <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/2016/'> 2016 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate expanded'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/12/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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/'> 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'] = 'AOuZoY6C8LKYo6CeK2ZxD0qBqVhzcEdc7w:1732429933303';_WidgetManager._Init('//www.blogger.com/rearrange?blogID\x3d32069983','//webmasters.googleblog.com/2016/','32069983'); _WidgetManager._SetDataContext([{'name': 'blog', 'data': {'blogId': '32069983', 'title': 'Official Google Webmaster Central Blog', 'url': 'https://webmasters.googleblog.com/2016/', 'canonicalUrl': 'https://webmasters.googleblog.com/2016/', 'homepageUrl': 'https://webmasters.googleblog.com/', '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', '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': 'archive', 'pageName': '2016', 'pageTitle': 'Official Google Webmaster Central Blog: 2016', '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/2016/', 'type': 'feed', 'isSingleItem': false, 'isMultipleItems': true, 'isError': false, 'isPage': false, 'isPost': false, 'isHomepage': false, 'isArchive': true, 'isLabelSearch': false, 'archive': {'year': 2016, 'rangeMessage': 'Showing posts from 2016'}}}]); _WidgetManager._RegisterWidget('_HeaderView', new _WidgetInfo('Header1', 'header', document.getElementById('Header1'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_BlogView', new _WidgetInfo('Blog1', 'main', document.getElementById('Blog1'), {'cmtInteractionsEnabled': false}, '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>