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: feedback and communication </title> <script type='text/javascript'> var newhost = 'https://developers.google.com'; var target_blog_path = '/search/blog' var target_search_path = '/s/results/search/blog/?q=' var pathname = window.location.pathname if (pathname.startsWith('/search/label/')) { pathname = target_search_path.concat(pathname.slice(14)); } else if (pathname.endsWith('.html')) { pathname = target_blog_path.concat(pathname.slice(0, -5)); } else { pathname = target_blog_path; } var redir_target = newhost.concat(pathname); window.location.href = redir_target; </script> <meta content='evCklrdiBeZ3REnk8pXEV6_6iEdNf1ZLgUpwH9XirGg' name='google-site-verification'/> <meta content='width=device-width, height=device-height, minimum-scale=1.0, initial-scale=1.0, user-scalable=0' name='viewport'/> <meta content='IE=Edge' http-equiv='X-UA-Compatible'/> <meta content='Official Google Webmaster Central Blog' property='og:title'/> <meta content='Official news on crawling and indexing sites for the Google index' property='og:description'/> <meta content='en_US' property='og:locale'/> <meta content='https://webmasters.googleblog.com/search/label/feedback%20and%20communication' property='og:url'/> <meta content='Official Google Webmaster Central Blog' property='og:site_name'/>  <meta content='Official Google Webmaster Central Blog' property='og:title'/> <meta content='Official news on crawling and indexing sites for the Google index' property='twitter:description'/> <meta content='summary' name='twitter:card'/> <meta content='@googlewmc' name='twitter:creator'/> <link href='https://fonts.googleapis.com/css?family=Roboto:400italic,400,500,500italic,700,700italic' rel='stylesheet' type='text/css'/> <link href='https://fonts.googleapis.com/icon?family=Material+Icons' rel='stylesheet'/> <script src='https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js' type='text/javascript'></script>  <style id='page-skin-1' type='text/css'></style> <style id='template-skin-1' type='text/css'></style>  <meta content='text/html; charset=UTF-8' http-equiv='Content-Type'/> <meta content='blogger' name='generator'/> <link href='https://webmasters.googleblog.com/favicon.ico' rel='icon' type='image/x-icon'/> <link href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication' rel='canonical'/> <link rel="alternate" type="application/atom+xml" title="Official Google Webmaster Central Blog - Atom" href="https://webmasters.googleblog.com/feeds/posts/default" /> <link rel="alternate" type="application/rss+xml" title="Official Google Webmaster Central Blog - RSS" href="https://webmasters.googleblog.com/feeds/posts/default?alt=rss" /> <link rel="service.post" type="application/atom+xml" title="Official Google Webmaster Central Blog - Atom" href="https://www.blogger.com/feeds/32069983/posts/default" />  <meta content='Official news on crawling and indexing sites for the Google index' name='description'/> <meta content='https://webmasters.googleblog.com/search/label/feedback%20and%20communication' property='og:url'/> <meta content='Official Google Webmaster Central Blog' property='og:title'/> <meta content='Official news on crawling and indexing sites for the Google index' property='og:description'/>  <base target='_self'/> <style> html { font-family: Roboto, sans-serif; -moz-osx-font-smoothing: grayscale; -webkit-font-smoothing: antialiased; } body { padding: 0; /* This ensures that the scroll bar is always present, which is needed */ /* because content render happens after page load; otherwise the header */ /* would "bounce" in-between states. */ min-height: 150%; } h2 { font-size: 16px; } h1, h2, h3, h4, h5 { line-height: 2em; } html, h4, h5, h6 { font-size: 14px; } a, a:visited { color: #4184F3; text-decoration: none; } a:focus, a:hover, a:active { text-decoration: none; } .Header { margin-top: 15px; } .Header h1 { font-size: 32px; font-weight: 300; line-height: 32px; height: 42px; } .header-inner .Header .titlewrapper { padding: 0; margin-top: 30px; } .header-inner .Header .descriptionwrapper { padding: 0; margin: 0; } .cols-wrapper { margin-top: 56px; } .header-outer, .cols-wrapper, .footer-outer, .google-footer-outer { padding: 0 60px; } .header-inner { height: 256px; position: relative; } html, .header-inner a { color: #212121; color: rgba(0,0,0,.87); } .header-inner .google-logo { display: inline-block; background-size: contain; z-index: 1; height: 46px; overflow: hidden; margin-top: 4px; margin-right: 8px; } .header-left { position: absolute; top: 50%; -webkit-transform: translateY(-50%); transform: translateY(-50%); margin-top: 12px; width: 100%; } .google-logo { margin-left: -4px; } #google-footer { position: relative; font-size: 13px; list-style: none; text-align: right; } #google-footer a { color: #444; } #google-footer ul { margin: 0; padding: 0; height: 144px; line-height: 144px; } #google-footer ul li { display: inline; } #google-footer ul li:before { color: #999; content: "\00b7"; font-weight: bold; margin: 5px; } #google-footer ul li:first-child:before { content: ''; } #google-footer .google-logo-dark { left: 0; margin-top: -16px; position: absolute; top: 50%; } /** Sitemap links. **/ .footer-inner-2 { font-size: 14px; padding-top: 42px; padding-bottom: 74px; } .footer-inner-2 .HTML h2 { color: #212121; color: rgba(0,0,0,.87); font-size: 14px; font-weight: 500; padding-left: 0; margin: 10px 0; } .footer-inner-2 .HTML ul { font-weight: normal; list-style: none; padding-left: 0; } .footer-inner-2 .HTML li { line-height: 24px; padding: 0; } .footer-inner-2 li a { color: rgba(65,132,243,.87); } /** Archive widget. **/ .BlogArchive { font-size: 13px; font-weight: normal; } .BlogArchive .widget-content { display: none; } .BlogArchive h2, .Label h2 { color: #4184F3; text-decoration: none; } .BlogArchive .hierarchy li { display: inline-block; } /* Specificity needed here to override widget CSS defaults. */ .BlogArchive #ArchiveList ul li, .BlogArchive #ArchiveList ul ul li { margin: 0; padding-left: 0; text-indent: 0; } .BlogArchive .intervalToggle { cursor: pointer; } .BlogArchive .expanded .intervalToggle .new-toggle { -ms-transform: rotate(180deg); transform: rotate(180deg); } .BlogArchive .new-toggle { float: right; padding-top: 3px; opacity: 0.87; } #ArchiveList { text-transform: uppercase; } #ArchiveList .expanded > ul:last-child { margin-bottom: 16px; } #ArchiveList .archivedate { width: 100%; } /* Months */ .BlogArchive .items { max-width: 150px; margin-left: -4px; } .BlogArchive .expanded .items { margin-bottom: 10px; overflow: hidden; } .BlogArchive .items > ul { float: left; height: 32px; } .BlogArchive .items a { padding: 0 4px; } .Label { font-size: 13px; font-weight: normal; } .sidebar-icon { display: inline-block; width: 24px; height: 24px; vertical-align: middle; margin-right: 12px; margin-top: -1px } .Label a { margin-right: 4px; } .Label .widget-content { display: none; } .FollowByEmail { font-size: 13px; font-weight: normal; } .FollowByEmail h2 { background: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABEAAAALCAYAAACZIGYHAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAUBJREFUeNrMkSGLAlEUhb+ZB4JFi8mx2cz+ApvhRUGTcUCrNqNJDYIi+DO0GUwmQXDK2DSIoGgZcSaIjDrzwrK4ssvChj1w0733O+fdp+m6PozH4yQSCfb7Pa7r8pOi0SjJZBLP8zgej4gAIMvlMuPxmADIYrHger1+C6lUKmo+NJ/NZojb7SZDWiwWo1qtks1msW2bw+HwZdkwDHq9HvV6nel0SqvVYrvdIh6Ph3Qch+VyqRYLhQJSSjRNw7IsfN9XgGKxSLfbJZfL0e/3aTabrFYr7vc7IujLcOh8PqunrNdr0uk0pVKJVCpFJBJRgEajweVyod1uMxgM2O12BAGUgRbU8DV2JpOhVquRz+cRQii3+XxOp9NRN3jVR5LPOp1OjEYjlSL8hclkgmmabDabt4d+m+S30vkD/R/IU4ABAPTZgnZdmG/PAAAAAElFTkSuQmCC"); background-repeat: no-repeat; background-position: 0 50%; text-indent: 30px; } .FollowByEmail .widget-content { display: none; } .searchBox input { border: 1px solid #eee; color: #212121; color: rgba(0,0,0,.87); font-size: 14px; padding: 8px 8px 8px 40px; width: 164px; font-family: Roboto, sans-serif; background: url("https://www.gstatic.com/images/icons/material/system/1x/search_grey600_24dp.png") 8px center no-repeat; } .searchBox ::-webkit-input-placeholder { /* WebKit, Blink, Edge */ color: rgba(0,0,0,.54); } .searchBox :-moz-placeholder { /* Mozilla Firefox 4 to 18 */ color: #000; opacity: 0.54; } .searchBox ::-moz-placeholder { /* Mozilla Firefox 19+ */ color: #000; opacity: 0.54; } .searchBox :-ms-input-placeholder { /* Internet Explorer 10-11 */ color: #757575; } .widget-item-control { margin-top: 0px; } .section { margin: 0; padding: 0; } #sidebar-top { border: 1px solid #eee; } #sidebar-top > div { margin: 16px 0; } .widget ul { line-height: 1.6; } /*main post*/ .post { margin-bottom:30px; } #main .post .title { margin: 0; } #main .post .title a { color: #212121; color: rgba(0,0,0,.87); font-weight: normal; font-size: 24px; } #main .post .title a:hover { text-decoration:none; color:#4184F3; } .message, #main .post .post-header { margin: 0; padding: 0; } #main .post .post-header .caption, #main .post .post-header .labels-caption, #main .post .post-footer .caption, #main .post .post-footer .labels-caption { color: #444; font-weight: 500; } #main .tr-caption-container td { text-align: left; } #main .post .tr-caption { color: #757575; color: rgba(0,0,0,.54); display: block; max-width: 560px; padding-bottom: 20px; } #main .post .tr-caption-container { line-height: 24px; margin: -1px 0 0 0 !important; padding: 4px 0; text-align: left; } #main .post .post-header .published{ font-size:11px; font-weight:bold; } .post-header .publishdate { font-size: 17px; font-weight:normal; color: #757575; color: rgba(0,0,0,.54); } #main .post .post-footer{ font-size:12px; padding-bottom: 21px; } .label-footer { margin-bottom: 12px; margin-top: 12px; } .comment-img { margin-right: 16px; opacity: 0.54; vertical-align: middle; } #main .post .post-header .published { margin-bottom: 40px; margin-top: -2px; } .post .post-content { color: #212121; color: rgba(0,0,0,.87); font-size: 17px; margin: 25px 0 36px 0; line-height: 32px; } .post-body .post-content ul, .post-body .post-content ol { margin: 16px 0; padding: 0 48px; } .post-summary { display: none; } /* Another old-style caption. */ .post-content div i, .post-content div + i { font-size: 14px; font-style: normal; color: #757575; color: rgba(0,0,0,.54); display: block; line-height: 24px; margin-bottom: 16px; text-align: left; } /* Another old-style caption (with link) */ .post-content a > i { color: #4184F3 !important; } /* Old-style captions for images. */ .post-content .separator + div:not(.separator) { margin-top: -16px; } /* Capture section headers. */ .post-content br + br + b, .post-content .space + .space + b, .post-content .separator + b { display: inline-block; margin-bottom: 8px; margin-top: 24px; } .post-content li { line-height: 32px; } /* Override all post images/videos to left align. */ .post-content .separator, .post-content > div { text-align: left; } .post-content .separator > a, .post-content .separator > span { margin-left: 0 !important; } .post-content img { max-width: 100%; height: auto; width: auto; } .post-content .tr-caption-container img { margin-bottom: 12px; } .post-content iframe, .post-content embed { max-width: 100%; } .post-content .carousel-container { margin-bottom: 48px; } #main .post-content b { font-weight: 500; } /* These are the main paragraph spacing tweaks. */ #main .post-content br { content: ' '; display: block; padding: 4px; } .post-content .space { display: block; height: 8px; } .post-content iframe + .space, .post-content iframe + br { padding: 0 !important; } #main .post .jump-link { margin-bottom:10px; } .post-content img, .post-content iframe { margin: 30px 0 20px 0; } .post-content > img:first-child, .post-content > iframe:first-child { margin-top: 0; } .col-right .section { padding: 0 16px; } #aside { background:#fff; border:1px solid #eee; border-top: 0; } #aside .widget { margin:0; } #aside .widget h2, #ArchiveList .toggle + a.post-count-link { color: #212121; color: rgba(0,0,0,.87); font-weight: 400 !important; margin: 0; } #ArchiveList .toggle { float: right; } #ArchiveList .toggle .material-icons { padding-top: 4px; } #sidebar .tab { cursor: pointer; } #sidebar .tab .arrow { display: inline-block; float: right; } #sidebar .tab .icon { display: inline-block; vertical-align: top; height: 24px; width: 24px; margin-right: 13px; margin-left: -1px; margin-top: 1px; color: #757575; color: rgba(0,0,0,.54); } #sidebar .widget-content > :first-child { padding-top: 8px; } #sidebar .active .tab .arrow { -ms-transform: rotate(180deg); transform: rotate(180deg); } #sidebar .arrow { color: #757575; color: rgba(0,0,0,.54); } #sidebar .widget h2 { font-size: 14px; line-height: 24px; display: inline-block; } #sidebar .widget .BlogArchive { padding-bottom: 8px; } #sidebar .widget { border-bottom: 1px solid #eee; box-shadow: 0px 1px 0 white; margin-bottom: 0; padding: 14px 0; min-height: 20px; } #sidebar .widget:last-child { border-bottom: none; box-shadow: none; margin-bottom: 0; } #sidebar ul { margin: 0; padding: 0; } #sidebar ul li { list-style:none; padding:0; } #sidebar ul li a { line-height: 32px; } #sidebar .archive { background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAYCAYAAADzoH0MAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAE1JREFUeNpiNDY23s9AAWBioBCwYBM8c+YMVsUmJibEGYBNMS5DaeMFfDYSZQA2v9I3FrB5AZeriI4FmnrBccCT8mhmGs1MwyAzAQQYAKEWG9zm9QFEAAAAAElFTkSuQmCC"); height: 24px; line-height: 24px; padding-left: 30px; } #sidebar .labels { background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABEAAAARCAYAAAA7bUf6AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAUxJREFUeNpiNDY23s9AAMycOfM7UF05kHkZmzwTMkdSUhKrIcXFxZy3bt3qBjIN8RrS09PDsHnzZjCNDr58+cKQlpbGDjSoHcg1w2oIyAUODg5gARCNzUVIBrUCuVYYhjx//pzhwIEDYAEQDeJjA1CDWIAGNQK59jBxRuSABbkAlwHIgIeHh2HWrFn/1NTU2oDcvSgBS4wBSC5iArqoCsj1YGIgEyAZVMoEchqlBjEB/cZAiUHg2AEGznpKDAImxOeM////B4VLKtBvEUCngZ1ILKivr3/u6+ubBzJAGZQ9gC5aQoqLgAY8BhkAZL4BuQQkxgXE34A4BuiiZEIuAhrwEGhAEZD5DpzYoIaA2UAM4kQADUrHZRDUgAIg8wO2XAwzbQXQa5OweQ1owB10AyA6gS7BgX1u3ry5397eHow3bdo0EyjGi00tQIABANPgyAH1q1eaAAAAAElFTkSuQmCC"); height: 20px; line-height: 20px; padding-left: 30px; } #sidebar .rss a { background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABIAAAASCAYAAABWzo5XAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAX5JREFUeNqsVDGSgkAQHL2rIiIikohIc/EBRkbwAIwuwgfwAXiAD9AHSI7kEkECRCb6AIyINDLx7K0aa6kT7uq0q7YYtnZ7umdnt7darXbr9Zpegeu61DNNc0dvwCcH4/GYJpMJnc9nOhwOVJbl/4hAAokMECZJQtvt9k+kH7qufyEYDAakqqqYxFdRFBqNRmTbNg2HQ0rTlK7XayvR0xqBdDqdkuM4dE/0ULhYLOh4PHYrknG5XGi/31MYhuL/nkwonM1mlGUZ1XXdrsiyLGEDhY7juJEZ1u5tIixDGdYhmYw+B7CAzPP5nDabjdgIAgCksMX1832/3drtdqPT6SQWapomiGEFNkDEdpDMMAzK81ys/7XYy+XyoQgq2WoURSIJ2iIIgp/WZCCTvFm2wgeAU31aI3Q2GhIDMeB53qPYPIcm5VrxXIOIOxsDMStjVawAc1VViRgN22lNBiuQN3GR+SY07hpOoStmFQAKXRRFY93bnpG+fONfedi+BRgAbkS8Fxp7QQIAAAAASUVORK5CYII="); } #sidebar .subscription a { background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABEAAAALCAYAAACZIGYHAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAUBJREFUeNrMkSGLAlEUhb+ZB4JFi8mx2cz+ApvhRUGTcUCrNqNJDYIi+DO0GUwmQXDK2DSIoGgZcSaIjDrzwrK4ssvChj1w0733O+fdp+m6PozH4yQSCfb7Pa7r8pOi0SjJZBLP8zgej4gAIMvlMuPxmADIYrHger1+C6lUKmo+NJ/NZojb7SZDWiwWo1qtks1msW2bw+HwZdkwDHq9HvV6nel0SqvVYrvdIh6Ph3Qch+VyqRYLhQJSSjRNw7IsfN9XgGKxSLfbJZfL0e/3aTabrFYr7vc7IujLcOh8PqunrNdr0uk0pVKJVCpFJBJRgEajweVyod1uMxgM2O12BAGUgRbU8DV2JpOhVquRz+cRQii3+XxOp9NRN3jVR5LPOp1OjEYjlSL8hclkgmmabDabt4d+m+S30vkD/R/IU4ABAPTZgnZdmG/PAAAAAElFTkSuQmCC"); } #sidebar-bottom { background: #f5f5f5; border-top:1px solid #eee; } #sidebar-bottom .widget { border-bottom: 1px solid #e0e0e0; padding: 15px 0; text-align: center; } #sidebar-bottom > div:last-child { border-bottom: 0; } #sidebar-bottom .text { line-height: 20px; } /* Home, forward, and backward pagination. */ .blog-pager { border-top : 1px #e0e0e0 solid; padding-top: 10px; margin-top: 15px; text-align: right !important; } #blog-pager { margin-botom: 0; margin-top: -14px; padding: 16px 0 0 0; } #blog-pager a { display: inline-block; } .blog-pager i.disabled { opacity: 0.2 !important; } .blog-pager i { color: black; margin-left: 16px; opacity: 0.54; } .blog-pager i:hover, .blog-pager i:active { opacity: 0.87; } #blog-pager-older-link, #blog-pager-newer-link { float: none; } .gplus-profile { background-color: #fafafa; border: 1px solid #eee; overflow: hidden; width: 212px; } .gplus-profile-inner { margin-left: -1px; margin-top: -1px; } /* Sidebar follow buttons. */ .followgooglewrapper { padding: 12px 0 0 0; } .loading { visibility: hidden; } .detail-page .post-footer .cmt_iframe_holder { padding-top: 40px !important; } /** Desktop **/ @media (max-width: 900px) { .col-right { display: none; } .col-main { margin-right: 0; min-width: initial; } .footer-outer { display: none; } .cols-wrapper { min-width: initial; } .google-footer-outer { background-color: #f5f5f5; } } /** Tablet **/ @media (max-width: 712px) { .header-outer, .cols-wrapper, .footer-outer, .google-footer-outer { padding: 0 40px; } } /* An extra breakpoint accommodating for long blog titles. */ @media (max-width: 600px) { .header-left { height: 100%; top: inherit; margin-top: 0; -webkit-transform: initial; transform: initial; } .header-title { margin-top: 18px; } .header-inner .google-logo { height: 40px; margin-top: 3px; } .header-inner .google-logo img { height: 42px; } .header-title h2 { font-size: 32px; line-height: 40px; } .header-desc { bottom: 24px; position: absolute; } } /** Mobile/small desktop window; also landscape. **/ @media (max-width: 480px), (max-height: 480px) { .header-outer, .cols-wrapper, .footer-outer, .google-footer-outer { padding: 0 16px; } .cols-wrapper { margin-top: 0; } .post-header .publishdate, .post .post-content { font-size: 16px; } .post .post-content { line-height: 28px; margin-bottom: 30px; } .post { margin-top: 30px; } .byline-author { display: block; font-size: 12px; line-height: 24px; margin-top: 6px; } #main .post .title a { font-weight: 500; color: #4c4c4c; color: rgba(0,0,0,.70); } #main .post .post-header { padding-bottom: 12px; } #main .post .post-header .published { margin-bottom: -8px; margin-top: 3px; } .post .read-more { display: block; margin-top: 14px; } .post .tr-caption { font-size: 12px; } #main .post .title a { font-size: 20px; line-height: 30px; } .post-content iframe { /* iframe won't keep aspect ratio when scaled down. */ max-height: 240px; } .post-content .separator img, .post-content .tr-caption-container img, .post-content iframe { margin-left: -16px; max-width: inherit; width: calc(100% + 32px); } .post-content table, .post-content td { width: 100%; } #blog-pager { margin: 0; padding: 16px 0; } /** List page tweaks. **/ .list-page .post-original { display: none; } .list-page .post-summary { display: block; } .list-page .comment-container { display: none; } .list-page #blog-pager { padding-top: 0; border: 0; margin-top: -8px; } .list-page .label-footer { display: none; } .list-page #main .post .post-footer { border-bottom: 1px solid #eee; margin: -16px 0 0 0; padding: 0 0 20px 0; } .list-page .post .share { display: none; } /** Detail page tweaks. **/ .detail-page .post-footer .cmt_iframe_holder { padding-top: 32px !important; } .detail-page .label-footer { margin-bottom: 0; } .detail-page #main .post .post-footer { padding-bottom: 0; } .detail-page #comments { display: none; } } [data-about-pullquote], [data-is-preview], [data-about-syndication] { display: none; } </style> <noscript> <style> .loading { visibility: visible }</style> </noscript> <script type='text/javascript'> (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) })(window,document,'script','https://www.google-analytics.com/analytics.js','ga'); ga('create', 'UA-18009-4', 'auto', 'blogger'); ga('blogger.send', 'pageview'); </script> <link href='https://www.blogger.com/dyn-css/authorization.css?targetBlogID=32069983&zx=8855dad6-3029-4476-9a6a-423344a04200' media='none' onload='if(media!='all')media='all'' rel='stylesheet'/><noscript><link href='https://www.blogger.com/dyn-css/authorization.css?targetBlogID=32069983&zx=8855dad6-3029-4476-9a6a-423344a04200' rel='stylesheet'/></noscript> <meta name='google-adsense-platform-account' content='ca-host-pub-1556223355139109'/> <meta name='google-adsense-platform-domain' content='blogspot.com'/> </head> <body> <script type='text/javascript'> //<![CDATA[ var axel = Math.random() + ""; var a = axel * 10000000000000; document.write('<iframe src="https://2542116.fls.doubleclick.net/activityi;src=2542116;type=gblog;cat=googl0;ord=ord=' + a + '?" width="1" height="1" frameborder="0" style="display:none"></iframe>'); //]]> </script> <noscript> <img alt='' height='1' src='https://ad.doubleclick.net/ddm/activity/src=2542116;type=gblog;cat=googl0;ord=1?' width='1'/> </noscript>  <div class='header-outer'> <div class='header-inner'> <div class='section' id='header'><div class='widget Header' data-version='1' id='Header1'> <div class='header-left'> <div class='header-title'> <a class='google-logo' href='https://webmasters.googleblog.com/?hl=en'> <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='8563900132998839954' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/09/google-search-news-coming-soon-to.html?hl=en' itemprop='url' title='Google Search News: coming soon to a screen near you'> Google Search News: coming soon to a screen near you </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Friday, September 27, 2019 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p>The world of search is constantly evolving. New tools, opportunities, and features are regularly arriving, sometimes existing things change, and sometimes we say goodbye to some things to make way for the new. To help you stay on top of things, we've started a new YouTube series called <a href="https://www.youtube.com/watch?v=78GFh553Vbc&list=PLKoqnv2vTMUNDpWUa0TaFPSi7VYLBKV03">Google Search News</a>.</p> <p>With Google Search News, we want to give you a regular & short summary of what's been happening around Google Search, specifically for SEOs, publishers, developers, and webmasters. The first episode is out now, so check it out. </p> <iframe width="560" height="315" src="https://www.youtube.com/embed/78GFh553Vbc" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> <p><small>(The first episode, now on your screen)</small></p> <p>In this first episode, we cover:</p> <ul><li>Recent updates to <a href="https://webmasters.googleblog.com/2019/09/goodbye-old-search-console.html">Search Console</a></li> <li>Changes in the <a href="https://www.google.com/webmasters/connect/">webmaster office-hours</a> setup</li> <li>Advances for <a href="https://webmasters.googleblog.com/2019/09/evolving-nofollow-new-ways-to-identify.html">rel=nofollow</a> & related attributes</li> <li>Changes in <a href="https://webmasters.googleblog.com/2019/09/making-review-rich-results-more-helpful.html">review rich results</a></li> <li>New meta-tags & attributes for your <a href="https://webmasters.googleblog.com/2019/09/more-controls-on-search.html">pages' search previews</a></li> <li>Some recent Webmaster Conferences</li></ul> <p>We plan to make these updates regularly, and adjust the format over time as needed. Let us know what you think in the video comments!</p> <span class="byline-author">Posted by <a href="http://twitter.com/johnmu?rel=depends">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>The world of search is constantly evolving. New tools, opportunities, and features are regularly arriving, sometimes existing things change, and sometimes we say goodbye to some things to make way for the new. To help you stay on top of things, we've started a new YouTube series called <a href="https://www.youtube.com/watch?v=78GFh553Vbc&list=PLKoqnv2vTMUNDpWUa0TaFPSi7VYLBKV03">Google Search News</a>.</p> <p>With Google Search News, we want to give you a regular & short summary of what's been happening around Google Search, specifically for SEOs, publishers, developers, and webmasters. The first episode is out now, so check it out. </p> <iframe width="560" height="315" src="https://www.youtube.com/embed/78GFh553Vbc" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> <p><small>(The first episode, now on your screen)</small></p> <p>In this first episode, we cover:</p> <ul><li>Recent updates to <a href="https://webmasters.googleblog.com/2019/09/goodbye-old-search-console.html">Search Console</a></li> <li>Changes in the <a href="https://www.google.com/webmasters/connect/">webmaster office-hours</a> setup</li> <li>Advances for <a href="https://webmasters.googleblog.com/2019/09/evolving-nofollow-new-ways-to-identify.html">rel=nofollow</a> & related attributes</li> <li>Changes in <a href="https://webmasters.googleblog.com/2019/09/making-review-rich-results-more-helpful.html">review rich results</a></li> <li>New meta-tags & attributes for your <a href="https://webmasters.googleblog.com/2019/09/more-controls-on-search.html">pages' search previews</a></li> <li>Some recent Webmaster Conferences</li></ul> <p>We plan to make these updates regularly, and adjust the format over time as needed. Let us know what you think in the video comments!</p> <span class="byline-author">Posted by <a href="http://twitter.com/johnmu?rel=depends">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:Google Search News: coming soon to a screen near you&url=https://webmasters.googleblog.com/2019/09/google-search-news-coming-soon-to.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2019/09/google-search-news-coming-soon-to.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2019/09/google-search-news-coming-soon-to.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/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=en' rel='tag'> structured data </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en' rel='tag'> webmaster community </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en' rel='tag'> webmaster tools </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/youtube%20channel?hl=en' rel='tag'> youtube channel </a> </span> </div> </div> </div> <div class='post' data-id='1124512533213197226' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/08/when-indexing-goes-wrong-how-google.html?hl=en' itemprop='url' title='When indexing goes wrong: how Google Search recovered from indexing issues & lessons learned since.'> When indexing goes wrong: how Google Search recovered from indexing issues & lessons learned since. </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Monday, August 12, 2019 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>Most of the time, our search engine runs properly. Our teams work hard to prevent technical issues that could affect our users who are searching the web, or webmasters whose sites we index and serve to users. Similarly, the underlying systems that we use to power the search engine also run as intended most of the time. When small disruptions happen, they are largely not visible to anyone except our teams who ensure that our products are up and running. However, like all complex systems, sometimes larger outages can occur, which may lead to disruptions for both users and website creators.</p> <p>In the last few months, such a situation occurred with our indexing systems, which had a ripple effect on some other parts of our infrastructure. While we worked as quickly as possible to remedy the situation, we apologize for the disruption, as our goal is to continuously provide high-quality products to our users and to the web ecosystem.</p> <p>Since then, we took a closer, careful look into the situation. In the process, we learned a few lessons that we'd like to share with you today. In this blog post, we will go into more details about what happened, clarify how we plan to communicate better if such things happen in the future, and remind website owners of the channels they can use to communicate with us.</p> <h2>So, what happened a few months ago?</h2> <p>In April, we had several issues related to our index. The Search index is the database that holds the hundreds of billions of web pages that we crawled on the web and that we think could answer some of our users’ queries. When a user enters a query in the Google search engine, our ranking algorithms sort through those pages in our Search index to find the most relevant, useful results in a fraction of a second. Here is more information on what happened.</p> <h3>1. The indexing issue</h3> <p>To start it off, we temporarily lost part of the Search index.<br>Wait... What? What do you mean “lost part of the index?” Is that even possible?</p> <p>Basically, when serving search results to users, to accelerate the speed of the service, the query of the user only “travels” as far as the closest of our data centers supporting the Google Search product, from which the Search Engine Results Page (SERP) is generated. So when there are modifications to the composition of the index (some pages added and removed, documents are merged, or other types of data modification), those modifications need to be reflected in all of those data centers. The consequence is that users all over the world are consistently served pages from the most recent version of the index.</p> <p><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlKmwOg0tP0MH7BMFbVu6haYtqJQE-IBkBpmMfZ3Lj_1p4C9s5fbpd-nYzWBHmSmyg-6pr4GQMLrnxI3R3puqEK40LByTpivFWCOSlnP41xuXE1bPRzwcbFJFpdMekHNTuGnwh/s1600/pasted+image+0.png" imageanchor="1" ><img border="0" data-original-height="333" data-original-width="500" height="266" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlKmwOg0tP0MH7BMFbVu6haYtqJQE-IBkBpmMfZ3Lj_1p4C9s5fbpd-nYzWBHmSmyg-6pr4GQMLrnxI3R3puqEK40LByTpivFWCOSlnP41xuXE1bPRzwcbFJFpdMekHNTuGnwh/s400/pasted+image+0.png" width="400" /></a> <small><br>Google owns and operates data centers (like the one pictured above) around the world, to keep our products running 24 hours a day, 7 days a week - <a href="https://www.google.com/about/datacenters/">source</a></small></p> <p>Keeping the index unified across all those data centers is a non trivial task. For large user-facing services, we may deploy updates by starting in one data center and expand until all relevant data centers are updated. For sensitive pieces of infrastructure, we may extend a rollout over several days, interleaving them across instances in different geographic regions. <a href="https://landing.google.com/sre/sre-book/chapters/release-engineering/">source</a></p> <p>So, as we pushed some planned changes to the Search index, on April 5th parts of the deployment system broke, on a Friday no-less! More specifically: as we were updating the index over some of our data centers, a small number of documents ended up being dropped from the index accidentally. Hence: “we lost part of the index.”</p> <p>Luckily, our <a href="https://landing.google.com/sre/sre-book/chapters/being-on-call/">on-call engineers</a> caught the issue pretty quickly, at the same time as we started picking up chatter on social media (thanks to everyone who notified us over that weekend!). As a result, we were able to start reverting the Search index to its previous stable state in all data centers only a few hours after the issue was uncovered (we keep back-ups of our indexes just in case such events happen).</p> <p>We communicated on Sunday, <a href="https://mobile.twitter.com/searchliaison/status/1114961119699804160">April 7th</a> that we were aware of the issue, and that things were starting to get back to normal. As data centers were progressively reverting back to a stable index, we continued updating on Twitter (on <a href="https://mobile.twitter.com/searchliaison/status/1115342598279913472">April 8th</a>, on <a href="https://mobile.twitter.com/searchliaison/status/1115700559317585920">April 9th</a>), until we were confident that all data centers were fully back to a complete version of the index on <a href="https://mobile.twitter.com/searchliaison/status/1116152155713392640">April 11th</a>.</p> <h3>2. The Search Console issue</h3> <p><a href="https://search.google.com/search-console/about">Search Console</a> is the set of tools and reports any webmaster can use to access data about their website’s performance in Search. For example, it shows how many impressions and clicks a website gets in the organic search results every day, or information on what pages of a website are included and excluded from the Search index.</p> <p>As a consequence of the Search index having the issues we described above, Search Console started to also show inconsistencies. This is because some of the data that surfaces in Search Console originates from the Search index itself:</p> <ul><li>the <a href="https://support.google.com/webmasters/answer/7440203">Index Coverage report</a> depends on the Search index being consistent across data centers.</li> <li>when we store a page in the Search index, we can annotate the entry with key signals about the page, like the fact that the page contains rich results markup for example. Therefore, an issue with the Search index can have an impact on the <a href="https://support.google.com/webmasters/answer/7552505">Rich Results reports</a> in Search Console.</li></ul> <p>Basically, many Search Console individual reports read data from a dedicated database. That database is partially built by using information that comes from the Search index. As we had to revert back to a previous version of the Search index, we also had to pause the updating of the Search Console database. This resulted in plateau-ing data for some reports (and flakiness in others, like the URL inspection tool).</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjkmVWgQhTSSF_Yiv8xxdKD6wbYB2Y8EFyz_iVHRBMULzLJ5HFw7U8wpTxwu11rKikQ3V9WeG__ZwrTgX7GJo9P3LxdLuCBI_QvzV5il3YBa4biPK5aCLcst9P7ssfyjWKjdYkY/s1600/pasted+image+0+%25281%2529.png" imageanchor="1" ><img border="0" data-original-height="266" data-original-width="911" height="117" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjkmVWgQhTSSF_Yiv8xxdKD6wbYB2Y8EFyz_iVHRBMULzLJ5HFw7U8wpTxwu11rKikQ3V9WeG__ZwrTgX7GJo9P3LxdLuCBI_QvzV5il3YBa4biPK5aCLcst9P7ssfyjWKjdYkY/s400/pasted+image+0+%25281%2529.png" width="400" /></a> <small><br>Index coverage report for indexed pages, which shows an example of the data freshness issues in Search Console in April 2019, with a longer time between 2 updates than what is usually observed.</small></p> <p>Because the whole Search index issue took several days to roll back (see explanation above), we were delayed focusing on fixing the Search Console database until a few days later, only after the indexing issues were fixed. We communicated on April 15th - <a href="https://mobile.twitter.com/googlewmc/status/1117739223405211650">tweet</a> - that the Search Console was having troubles and that we were working on fixing it, and we completed our fixes on April 28th (day on which the reports started gathering fresh data again, see graph above). We communicated on Twitter on April 30th that the issue was resolved- <a href="https://mobile.twitter.com/googlewmc/status/1123192022179962880">tweet</a>.</p> <h3>3. Other issues unrelated to the main indexing bug</h3> <p>Google Search relies on a number of systems that work together. While some of those systems can be tightly linked to one another, in some cases different parts of the system experience unrelated problems around the same time.</p> <p>In the present case for example, around the same time as the main indexing bug explained above, we also had brief problems gathering fresh Google News content. Additionally, while rendering pages, certain URLs started to redirect Googlebot to other unrelated pages. These issues were entirely unrelated to the indexing bug, and were quickly resolved (<a href="https://mobile.twitter.com/searchliaison/status/1118237091014385664">tweet 1</a> & <a href="https://mobile.twitter.com/googlewmc/status/1121538876126969859">tweet 2</a>).</p> <h2>Our communication and how we intend on doing better</h2> <p>In addition to communicating on social media (as highlighted above) during those few weeks, we also gave webmasters more details in 2 other channels: Search Console, as well as the Search Console Help Center.</p> <h3>In the Search Console Help Center</h3> <p>We updated our “<a href="https://support.google.com/webmasters/answer/6211453#general">Data anomalies in Search Console</a>” help page after the issue was fully identified. This page is used to communicate information about data disruptions to our Search Console service when the impact affects a large number of website owners.</p> <h3>In Search Console</h3> <p>Because we know that not all our users read social media or the external Help Center page, we also added annotations on Search Console reports, to notify users that the data might not be accurate (see image below). We added this information after the resolution of the bugs. Clicking on “see here for more details” sends users to the “Data Anomalies” page in the Help Center.</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhOEAFlQBbTXgfaS74PG_M5QizdlzXAbcrqjZJtvGbIYTEM9WLdMcRuXQokgb60Pg_OkGtNIMYRRrASePmhGBb-peu_O-12MaMp635lWl2XU5-HXqcfXetm9Ox0ZwLy1vlry00x/s1600/pasted+image+0+%25282%2529.png" imageanchor="1" ><img border="0" data-original-height="266" data-original-width="912" height="117" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhOEAFlQBbTXgfaS74PG_M5QizdlzXAbcrqjZJtvGbIYTEM9WLdMcRuXQokgb60Pg_OkGtNIMYRRrASePmhGBb-peu_O-12MaMp635lWl2XU5-HXqcfXetm9Ox0ZwLy1vlry00x/s400/pasted+image+0+%25282%2529.png" width="400" /></a> <br>Index coverage report for indexed pages, which shows an example of the data annotations that we can include to notify users of specific issues.</p> <h3>Communications going forward</h3> <p>When things break at Google, we have a strong “postmortem” culture: creating a document to debrief on the breakage, and try to avoid it happening next time. The whole process is described in more detail at the <a href="https://landing.google.com/sre/sre-book/chapters/postmortem-culture/">Google Site Reliability Engineering website</a>.</p> <p>In the wake of the April indexing issues, we included in the postmortem how to better communicate with webmasters in case of large system failures. Our key decisions were:</p> <ol><li>Explore ways to more quickly share information within Search Console itself about widespread bugs, and have that information serve as the main point of reference for webmasters to check, in case they are suspecting outages.</li> <li>More promptly post to the Search Console data anomalies page, when relevant (if the disturbance is going to be seen over the long term in Search Console data).</li> <li>Continue tweeting as quickly as we can about such issues to quickly reassure webmasters we’re aware and that the issue is on our end.</li> </ol> <p>Those commitments should make potential future similar situations more transparent for webmasters as a whole.</p> <h3>Putting our resolutions into action: the “new URLs not indexed” case study</h3> <p>On May 22nd, we tested our new communications strategy, as we experienced another issue. Here’s what happened: while processing certain URLs, our duplicate management system ran out of memory after a planned infrastructure upgrade, which caused all incoming URLs to stop processing.</p> <p>Here is a timeline of how we thought about communications, following the 3 points highlighted just above:</p> <ol><li>We noticed the issue (around 5.30am California time, May 22nd)<br>We <a href="https://mobile.twitter.com/googlewmc/status/1131193175652032516">tweeted</a> about the ongoing issue (around 6.40am California time, May 22nd)<br>We <a href="https://mobile.twitter.com/googlewmc/status/1131425970521542656">tweeted</a> about the resolution (around 10pm California time, May 22nd)</li> <li>We evaluated updating the “Data Anomalies” page in the Help Center, but decided against it since we did not expect any long-term impact for the majority of webmasters' Search Console data in the long run.</li> <li>The confusion that this issue created for many confirmed our earlier conclusions that we need a way to signal more clearly in the Search Console itself that there might be a disruption to one of our systems which could impact webmasters. Such a solution might take longer to implement. We will communicate on this topic in the future, as we have more news.</li> </ol> <p>Last week, we also had another indexing issue. As with May 22, we <a href="https://mobile.twitter.com/googlewmc/status/1159380861151797250">tweeted</a> to let people know there was an issue, that we were working to fix it and when the issue was resolved.</p> <h2>How to debug and communicate with us</h2> <p>We hope that this post will bring more clarity to how our systems are complex and can sometimes break, and will also help you understand how we communicate about these matters. But while this post focuses on a widespread breakage of our systems, it’s important to keep in mind that most website indexing issues are caused by an individual website’s configuration, which can create difficulties for Google Search to index that website properly. For those cases, all webmasters can debug issues using <a href="https://search.google.com/search-console">Search Console</a> and our <a href="https://support.google.com/webmasters">Help center</a>. After doing so, if you still think that an issue is not coming from your site or don’t know how to resolve it, come talk to us and our community, we always want to take feedback from our users. Here is how to signal an issue to us:<br><br></p> <ul><li>Check our <a href="https://support.google.com/webmasters/community">Webmaster Community</a>, sometimes other webmasters have highlighted an issue that also impacts your site.</li> <li>In person! We love contact, come and talk to us at events. <a href="https://www.google.com/webmasters/connect/">Calendar</a>.</li> <li>Within our products! The Search Console feedback tool is very useful to our teams.</li> <li><a href="https://mobile.twitter.com/googlewmc">Twitter</a> and <a href="https://www.youtube.com/user/GoogleWebmasterHelp">YouTube</a>!</li></ul> <br> <span class="byline-author">Posted by Vincent Courson, Google Search Outreach</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>Most of the time, our search engine runs properly. Our teams work hard to prevent technical issues that could affect our users who are searching the web, or webmasters whose sites we index and serve to users. Similarly, the underlying systems that we use to power the search engine also run as intended most of the time. When small disruptions happen, they are largely not visible to anyone except our teams who ensure that our products are up and running. However, like all complex systems, sometimes larger outages can occur, which may lead to disruptions for both users and website creators.</p> <p>In the last few months, such a situation occurred with our indexing systems, which had a ripple effect on some other parts of our infrastructure. While we worked as quickly as possible to remedy the situation, we apologize for the disruption, as our goal is to continuously provide high-quality products to our users and to the web ecosystem.</p> <p>Since then, we took a closer, careful look into the situation. In the process, we learned a few lessons that we'd like to share with you today. In this blog post, we will go into more details about what happened, clarify how we plan to communicate better if such things happen in the future, and remind website owners of the channels they can use to communicate with us.</p> <h2>So, what happened a few months ago?</h2> <p>In April, we had several issues related to our index. The Search index is the database that holds the hundreds of billions of web pages that we crawled on the web and that we think could answer some of our users’ queries. When a user enters a query in the Google search engine, our ranking algorithms sort through those pages in our Search index to find the most relevant, useful results in a fraction of a second. Here is more information on what happened.</p> <h3>1. The indexing issue</h3> <p>To start it off, we temporarily lost part of the Search index.<br>Wait... What? What do you mean “lost part of the index?” Is that even possible?</p> <p>Basically, when serving search results to users, to accelerate the speed of the service, the query of the user only “travels” as far as the closest of our data centers supporting the Google Search product, from which the Search Engine Results Page (SERP) is generated. So when there are modifications to the composition of the index (some pages added and removed, documents are merged, or other types of data modification), those modifications need to be reflected in all of those data centers. The consequence is that users all over the world are consistently served pages from the most recent version of the index.</p> <p><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlKmwOg0tP0MH7BMFbVu6haYtqJQE-IBkBpmMfZ3Lj_1p4C9s5fbpd-nYzWBHmSmyg-6pr4GQMLrnxI3R3puqEK40LByTpivFWCOSlnP41xuXE1bPRzwcbFJFpdMekHNTuGnwh/s1600/pasted+image+0.png" imageanchor="1" ><img border="0" data-original-height="333" data-original-width="500" height="266" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlKmwOg0tP0MH7BMFbVu6haYtqJQE-IBkBpmMfZ3Lj_1p4C9s5fbpd-nYzWBHmSmyg-6pr4GQMLrnxI3R3puqEK40LByTpivFWCOSlnP41xuXE1bPRzwcbFJFpdMekHNTuGnwh/s400/pasted+image+0.png" width="400" /></a> <small><br>Google owns and operates data centers (like the one pictured above) around the world, to keep our products running 24 hours a day, 7 days a week - <a href="https://www.google.com/about/datacenters/">source</a></small></p> <p>Keeping the index unified across all those data centers is a non trivial task. For large user-facing services, we may deploy updates by starting in one data center and expand until all relevant data centers are updated. For sensitive pieces of infrastructure, we may extend a rollout over several days, interleaving them across instances in different geographic regions. <a href="https://landing.google.com/sre/sre-book/chapters/release-engineering/">source</a></p> <p>So, as we pushed some planned changes to the Search index, on April 5th parts of the deployment system broke, on a Friday no-less! More specifically: as we were updating the index over some of our data centers, a small number of documents ended up being dropped from the index accidentally. Hence: “we lost part of the index.”</p> <p>Luckily, our <a href="https://landing.google.com/sre/sre-book/chapters/being-on-call/">on-call engineers</a> caught the issue pretty quickly, at the same time as we started picking up chatter on social media (thanks to everyone who notified us over that weekend!). As a result, we were able to start reverting the Search index to its previous stable state in all data centers only a few hours after the issue was uncovered (we keep back-ups of our indexes just in case such events happen).</p> <p>We communicated on Sunday, <a href="https://mobile.twitter.com/searchliaison/status/1114961119699804160">April 7th</a> that we were aware of the issue, and that things were starting to get back to normal. As data centers were progressively reverting back to a stable index, we continued updating on Twitter (on <a href="https://mobile.twitter.com/searchliaison/status/1115342598279913472">April 8th</a>, on <a href="https://mobile.twitter.com/searchliaison/status/1115700559317585920">April 9th</a>), until we were confident that all data centers were fully back to a complete version of the index on <a href="https://mobile.twitter.com/searchliaison/status/1116152155713392640">April 11th</a>.</p> <h3>2. The Search Console issue</h3> <p><a href="https://search.google.com/search-console/about">Search Console</a> is the set of tools and reports any webmaster can use to access data about their website’s performance in Search. For example, it shows how many impressions and clicks a website gets in the organic search results every day, or information on what pages of a website are included and excluded from the Search index.</p> <p>As a consequence of the Search index having the issues we described above, Search Console started to also show inconsistencies. This is because some of the data that surfaces in Search Console originates from the Search index itself:</p> <ul><li>the <a href="https://support.google.com/webmasters/answer/7440203">Index Coverage report</a> depends on the Search index being consistent across data centers.</li> <li>when we store a page in the Search index, we can annotate the entry with key signals about the page, like the fact that the page contains rich results markup for example. Therefore, an issue with the Search index can have an impact on the <a href="https://support.google.com/webmasters/answer/7552505">Rich Results reports</a> in Search Console.</li></ul> <p>Basically, many Search Console individual reports read data from a dedicated database. That database is partially built by using information that comes from the Search index. As we had to revert back to a previous version of the Search index, we also had to pause the updating of the Search Console database. This resulted in plateau-ing data for some reports (and flakiness in others, like the URL inspection tool).</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjkmVWgQhTSSF_Yiv8xxdKD6wbYB2Y8EFyz_iVHRBMULzLJ5HFw7U8wpTxwu11rKikQ3V9WeG__ZwrTgX7GJo9P3LxdLuCBI_QvzV5il3YBa4biPK5aCLcst9P7ssfyjWKjdYkY/s1600/pasted+image+0+%25281%2529.png" imageanchor="1" ><img border="0" data-original-height="266" data-original-width="911" height="117" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjkmVWgQhTSSF_Yiv8xxdKD6wbYB2Y8EFyz_iVHRBMULzLJ5HFw7U8wpTxwu11rKikQ3V9WeG__ZwrTgX7GJo9P3LxdLuCBI_QvzV5il3YBa4biPK5aCLcst9P7ssfyjWKjdYkY/s400/pasted+image+0+%25281%2529.png" width="400" /></a> <small><br>Index coverage report for indexed pages, which shows an example of the data freshness issues in Search Console in April 2019, with a longer time between 2 updates than what is usually observed.</small></p> <p>Because the whole Search index issue took several days to roll back (see explanation above), we were delayed focusing on fixing the Search Console database until a few days later, only after the indexing issues were fixed. We communicated on April 15th - <a href="https://mobile.twitter.com/googlewmc/status/1117739223405211650">tweet</a> - that the Search Console was having troubles and that we were working on fixing it, and we completed our fixes on April 28th (day on which the reports started gathering fresh data again, see graph above). We communicated on Twitter on April 30th that the issue was resolved- <a href="https://mobile.twitter.com/googlewmc/status/1123192022179962880">tweet</a>.</p> <h3>3. Other issues unrelated to the main indexing bug</h3> <p>Google Search relies on a number of systems that work together. While some of those systems can be tightly linked to one another, in some cases different parts of the system experience unrelated problems around the same time.</p> <p>In the present case for example, around the same time as the main indexing bug explained above, we also had brief problems gathering fresh Google News content. Additionally, while rendering pages, certain URLs started to redirect Googlebot to other unrelated pages. These issues were entirely unrelated to the indexing bug, and were quickly resolved (<a href="https://mobile.twitter.com/searchliaison/status/1118237091014385664">tweet 1</a> & <a href="https://mobile.twitter.com/googlewmc/status/1121538876126969859">tweet 2</a>).</p> <h2>Our communication and how we intend on doing better</h2> <p>In addition to communicating on social media (as highlighted above) during those few weeks, we also gave webmasters more details in 2 other channels: Search Console, as well as the Search Console Help Center.</p> <h3>In the Search Console Help Center</h3> <p>We updated our “<a href="https://support.google.com/webmasters/answer/6211453#general">Data anomalies in Search Console</a>” help page after the issue was fully identified. This page is used to communicate information about data disruptions to our Search Console service when the impact affects a large number of website owners.</p> <h3>In Search Console</h3> <p>Because we know that not all our users read social media or the external Help Center page, we also added annotations on Search Console reports, to notify users that the data might not be accurate (see image below). We added this information after the resolution of the bugs. Clicking on “see here for more details” sends users to the “Data Anomalies” page in the Help Center.</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhOEAFlQBbTXgfaS74PG_M5QizdlzXAbcrqjZJtvGbIYTEM9WLdMcRuXQokgb60Pg_OkGtNIMYRRrASePmhGBb-peu_O-12MaMp635lWl2XU5-HXqcfXetm9Ox0ZwLy1vlry00x/s1600/pasted+image+0+%25282%2529.png" imageanchor="1" ><img border="0" data-original-height="266" data-original-width="912" height="117" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhOEAFlQBbTXgfaS74PG_M5QizdlzXAbcrqjZJtvGbIYTEM9WLdMcRuXQokgb60Pg_OkGtNIMYRRrASePmhGBb-peu_O-12MaMp635lWl2XU5-HXqcfXetm9Ox0ZwLy1vlry00x/s400/pasted+image+0+%25282%2529.png" width="400" /></a> <br>Index coverage report for indexed pages, which shows an example of the data annotations that we can include to notify users of specific issues.</p> <h3>Communications going forward</h3> <p>When things break at Google, we have a strong “postmortem” culture: creating a document to debrief on the breakage, and try to avoid it happening next time. The whole process is described in more detail at the <a href="https://landing.google.com/sre/sre-book/chapters/postmortem-culture/">Google Site Reliability Engineering website</a>.</p> <p>In the wake of the April indexing issues, we included in the postmortem how to better communicate with webmasters in case of large system failures. Our key decisions were:</p> <ol><li>Explore ways to more quickly share information within Search Console itself about widespread bugs, and have that information serve as the main point of reference for webmasters to check, in case they are suspecting outages.</li> <li>More promptly post to the Search Console data anomalies page, when relevant (if the disturbance is going to be seen over the long term in Search Console data).</li> <li>Continue tweeting as quickly as we can about such issues to quickly reassure webmasters we’re aware and that the issue is on our end.</li> </ol> <p>Those commitments should make potential future similar situations more transparent for webmasters as a whole.</p> <h3>Putting our resolutions into action: the “new URLs not indexed” case study</h3> <p>On May 22nd, we tested our new communications strategy, as we experienced another issue. Here’s what happened: while processing certain URLs, our duplicate management system ran out of memory after a planned infrastructure upgrade, which caused all incoming URLs to stop processing.</p> <p>Here is a timeline of how we thought about communications, following the 3 points highlighted just above:</p> <ol><li>We noticed the issue (around 5.30am California time, May 22nd)<br>We <a href="https://mobile.twitter.com/googlewmc/status/1131193175652032516">tweeted</a> about the ongoing issue (around 6.40am California time, May 22nd)<br>We <a href="https://mobile.twitter.com/googlewmc/status/1131425970521542656">tweeted</a> about the resolution (around 10pm California time, May 22nd)</li> <li>We evaluated updating the “Data Anomalies” page in the Help Center, but decided against it since we did not expect any long-term impact for the majority of webmasters' Search Console data in the long run.</li> <li>The confusion that this issue created for many confirmed our earlier conclusions that we need a way to signal more clearly in the Search Console itself that there might be a disruption to one of our systems which could impact webmasters. Such a solution might take longer to implement. We will communicate on this topic in the future, as we have more news.</li> </ol> <p>Last week, we also had another indexing issue. As with May 22, we <a href="https://mobile.twitter.com/googlewmc/status/1159380861151797250">tweeted</a> to let people know there was an issue, that we were working to fix it and when the issue was resolved.</p> <h2>How to debug and communicate with us</h2> <p>We hope that this post will bring more clarity to how our systems are complex and can sometimes break, and will also help you understand how we communicate about these matters. But while this post focuses on a widespread breakage of our systems, it’s important to keep in mind that most website indexing issues are caused by an individual website’s configuration, which can create difficulties for Google Search to index that website properly. For those cases, all webmasters can debug issues using <a href="https://search.google.com/search-console">Search Console</a> and our <a href="https://support.google.com/webmasters">Help center</a>. After doing so, if you still think that an issue is not coming from your site or don’t know how to resolve it, come talk to us and our community, we always want to take feedback from our users. Here is how to signal an issue to us:<br><br></p> <ul><li>Check our <a href="https://support.google.com/webmasters/community">Webmaster Community</a>, sometimes other webmasters have highlighted an issue that also impacts your site.</li> <li>In person! We love contact, come and talk to us at events. <a href="https://www.google.com/webmasters/connect/">Calendar</a>.</li> <li>Within our products! The Search Console feedback tool is very useful to our teams.</li> <li><a href="https://mobile.twitter.com/googlewmc">Twitter</a> and <a href="https://www.youtube.com/user/GoogleWebmasterHelp">YouTube</a>!</li></ul> <br> <span class="byline-author">Posted by Vincent Courson, Google Search Outreach</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:When indexing goes wrong: how Google Search recovered from indexing issues & lessons learned since.&url=https://webmasters.googleblog.com/2019/08/when-indexing-goes-wrong-how-google.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2019/08/when-indexing-goes-wrong-how-google.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2019/08/when-indexing-goes-wrong-how-google.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/crawling%20and%20indexing?hl=en' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en' rel='tag'> webmaster community </a> </span> </div> </div> </div> <div class='post' data-id='129647820952699233' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/03/this-year-in-search-spam-webspam-report.html?hl=en' itemprop='url' title='This year in Search Spam - Webspam report 2018'> This year in Search Spam - Webspam report 2018 </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, March 21, 2019 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <div class="separator" style="clear: both; text-align: justify;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjOvkatMgrClA98zzGHPrESp7B_BeKGD9VFnjGZM3df4EKhTlBDHYNVUMkTrsrERpZ71Gm28NukBx3PjPpy5Nj839jv58cCKdRLnFJjZsUKKUJGygPeQtGZELiYha2Iu-9xHdqz/s1600/WebspamReport2018_1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="501" data-original-width="1400" height="228" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjOvkatMgrClA98zzGHPrESp7B_BeKGD9VFnjGZM3df4EKhTlBDHYNVUMkTrsrERpZ71Gm28NukBx3PjPpy5Nj839jv58cCKdRLnFJjZsUKKUJGygPeQtGZELiYha2Iu-9xHdqz/s640/WebspamReport2018_1.png" width="640" /></a></div> <div style="text-align: justify;"> Google aims to provide the highest quality results for any search. As part of this, we take action to prevent what we call “webspam” from degrading the search experience, content and behaviors that violate our <a href="https://support.google.com/webmasters/answer/35769">webmaster guidelines</a>. Our efforts help ensure that well under 1 percent of results visited by users are for spammy pages. Here’s more about how we fought webspam in 2018.</div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <h3 style="text-align: justify;"> Google webspam trends and how we fought webspam in 2018</h3> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> Of the types of spam we fought in 2018, three continue to stand out:</div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <b><u>Spam on hacked websites:</u></b> We <a href="https://webmasters.googleblog.com/2018/06/how-we-fought-webspam-webspam-report.html">reported in 2017</a> that we had seen a substantial reduction of spam from hacked websites in search results. This trend continued in 2018, with faster discovery of hacked web pages before they affect search results or put someone in harm’s way.   While we reduced how spam on hacked sites affects search, hacked websites remain a major security problem affecting the safety of the web. Even though we can’t prevent a website hack from happening, we’re committed to helping webmasters whose websites have been compromised by offering resources to<a href="https://developers.google.com/web/fundamentals/security/hacked/"> help them recover from a hacked website. </a></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <b><u>User-generated spam:</u></b> A particular type of spam known as User-generated spam has been a continued focus for us. User-generated spam includes spammy posts on forums, as well as spammy accounts on free blogs and platforms, none of which are meant to be consumed by human beings, and all of which disrupt conversations while adding no value to users. In 2018, we were able to reduce the impact on search users from this type of spam by more than 80%. While we can’t prevent websites from being exploited, we do want to make it easier for website owners to learn how to protect themselves, which is why we provide resources on <a href="https://support.google.com/webmasters/answer/81749">how to prevent abuse of your site’s public areas.</a></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <b><u>Link spam:</u> </b>We continued to protect the value of authoritative and relevant links as an important ranking signal for Search. We continued to deal swiftly with egregious link spam, and made a number of bad linking practices less effective for manipulating ranking. Above all, we continued to engage with webmasters and SEOs to chip away at the many myths that have emerged over the years relating to linking practices. We continued to remind website owners that if you simply stay away from <a href="https://support.google.com/webmasters/answer/66356?hl=en">building links</a> mainly as an attempt to rank better and focus on creating great content, you should not have to worry about any of the myths or realities. We think that one of the best ways of fighting spam of all types is by encouraging website owners to just create great quality content. Resources such as the <a href="https://support.google.com/webmasters/answer/7451184">SEO starter-guide</a> highlight best practices and bust some common myths and misconceptions related to what it takes to appear well in Google Search results. <a href="https://support.google.com/webmasters/answer/93713?hl=en">Reporting link spam</a> is also a great way to assist us in fighting against this type of abuse and to help preserve fairness in Search ranking.</div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <h3 style="text-align: justify;"> Working with users, webmasters and developers for a better web</h3> <div style="text-align: justify;"> Everyday users continue to help us find spam, malware and other issues in Search that escape our filters and processes by <a href="https://support.google.com/webmasters/answer/93713">reporting spam on search</a>, <a href="https://safebrowsing.google.com/safebrowsing/report_phish/">reporting phishing</a> or  <a href="//www.google.com/safebrowsing/report_badware/">reporting malware</a>. We received over 180,000 search spam user reports and we were able to take action on 64% of the reports we processed. These reports truly make a difference and we’d like to thank all of you who submitted them. </div> <div style="text-align: justify;"> <br /> <br /></div> <div style="text-align: justify;"> We think it’s important to let website owners known when we detect something wrong with their website. In 2018, we generated over 186 million messages to website owners calling out potential improvements, issues and problems that could affect their site’s appearance on Search results. We can only deliver these notifications to site owners that verified their sites in <a href="https://search.google.com/search-console/welcome">Search Console</a>, and we successfully delivered 96 million of those messages. The rest of the messages will be kept linked with the website for as long as they are relevant, so they can be seen when a webmaster successfully registers their site in Search Console. The majority of these messages were welcoming new users to Search Console, and the second largest group was informing registered Search Console users when Mobile-First Indexing became available. Of all messages, slightly over 2%—about 4 million—were related to <a href="https://support.google.com/webmasters/answer/9044175">manual actions</a> resulting from violations of our Webmaster Guidelines. </div> <div style="text-align: justify;"> <br /> <br /></div> <div style="text-align: justify;"> High quality content keeps spam off of search results, and we continued to improve the tools and reports we offer for webmasters that create that content. The <a href="https://search.google.com/search-console/about">Google Search Console </a>was completely rebuilt from the ground up to provide both new and improved reports (<a href="https://support.google.com/webmasters/answer/7576553">Performance</a>, <a href="https://support.google.com/webmasters/answer/7440203">Index Coverage</a>, <a href="https://support.google.com/webmasters/answer/9049606">Links</a>, <a href="https://developers.google.com/search/mobile-sites/">Mobile Usability report</a>), as well as brand new features (<a href="https://webmasters.googleblog.com/2018/06/new-url-inspection-tool-more-in-search.html">URL Inspection Tool</a> and <a href="https://webmasters.googleblog.com/2018/08/collaboration-and-user-management-in.html">Site and User management)</a>. This improved Search Console graduated out of beta in 2018 and is now available generally to all registered website owners.</div> <div style="text-align: justify;"> <br /> <br /></div> <div style="text-align: justify;"> We didn’t forget the front-end developers who make the modern web work, and focused on helping them make their sites great for users and also search-friendly regardless of whether they are on a CMS, roll their own CSS and JS, or build on top of a web framework. With the new <a href="https://webmasters.googleblog.com/2018/02/seo-audit-category-in-lighthouse.html">SEO audit capability</a> in <a href="https://developers.google.com/web/tools/lighthouse/">Lighthouse</a>, the open-source and automated auditing tool for improving the quality of web pages, developers and webmasters can now run actionable <a href="https://chrome.google.com/webstore/detail/lighthouse/blipmdconlkpinefehnmjammfjpmpbjk">SEO health-checks</a> on their pages and quickly identify areas for improvement.</div> <div style="text-align: justify;"> <br /> <br /></div> <div style="text-align: justify;"> We also engage directly with website owners to provide help with thorny issues. Our dedicated team members meet with webmasters around the world regularly, both online and in-person. We delivered more than 190 <a href="https://www.google.com/intl/en/webmasters/connect/#attend-events">online office hours, online events and offline events</a> in more than 76 cities, to audiences totaling over 170,000 including SEOs, developers and online marketers. We hosted four search events in Tokyo, Singapore, Zurich and Osaka as well as an 11-city Search Conference in India. In 2018, we started live office hours in Spanish on top of English, French, German, Hindi and Japanese, where Webmasters can find help, tips and useful discussion on our <a href="https://www.youtube.com/googlewebmasters">Google Webmaster YouTube channel</a>. Product experts continued to help webmasters find solutions through our <a href="//g.co/webmasterforum">official support forums </a>in over a dozen languages. </div> <div style="text-align: justify;"> <br /> <br /></div> <div style="text-align: justify;"> We look forward to continuing our work to deliver a spam-free Search experience to all in 2019!</div> <div style="text-align: justify;"> <br /></div> <div class="separator" style="clear: both; text-align: justify;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhF2Cb72qZBBFVoRF8PRKqsc7xXV3-29vwrqKcjL8jXrGwg1K239czpvbIe_P-N0hz2t7IOaibts6wl8pSgyKVhkujLV5UGCCAOV130sZ3vDD4Yq_FIPoJYdZTLg12arorI3vB2/s1600/WebspamReport2018_2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="501" data-original-width="1400" height="228" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhF2Cb72qZBBFVoRF8PRKqsc7xXV3-29vwrqKcjL8jXrGwg1K239czpvbIe_P-N0hz2t7IOaibts6wl8pSgyKVhkujLV5UGCCAOV130sZ3vDD4Yq_FIPoJYdZTLg12arorI3vB2/s640/WebspamReport2018_2.png" width="640" /></a></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> Posted by Juan Felipe Rincón, Webmaster Outreach, Dublin</div> </div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <div class="separator" style="clear: both; text-align: justify;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjOvkatMgrClA98zzGHPrESp7B_BeKGD9VFnjGZM3df4EKhTlBDHYNVUMkTrsrERpZ71Gm28NukBx3PjPpy5Nj839jv58cCKdRLnFJjZsUKKUJGygPeQtGZELiYha2Iu-9xHdqz/s1600/WebspamReport2018_1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="501" data-original-width="1400" height="228" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjOvkatMgrClA98zzGHPrESp7B_BeKGD9VFnjGZM3df4EKhTlBDHYNVUMkTrsrERpZ71Gm28NukBx3PjPpy5Nj839jv58cCKdRLnFJjZsUKKUJGygPeQtGZELiYha2Iu-9xHdqz/s640/WebspamReport2018_1.png" width="640" /></a></div> <div style="text-align: justify;"> Google aims to provide the highest quality results for any search. As part of this, we take action to prevent what we call “webspam” from degrading the search experience, content and behaviors that violate our <a href="https://support.google.com/webmasters/answer/35769">webmaster guidelines</a>. Our efforts help ensure that well under 1 percent of results visited by users are for spammy pages. Here’s more about how we fought webspam in 2018.</div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <h3 style="text-align: justify;"> Google webspam trends and how we fought webspam in 2018</h3> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> Of the types of spam we fought in 2018, three continue to stand out:</div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <b><u>Spam on hacked websites:</u></b> We <a href="https://webmasters.googleblog.com/2018/06/how-we-fought-webspam-webspam-report.html">reported in 2017</a> that we had seen a substantial reduction of spam from hacked websites in search results. This trend continued in 2018, with faster discovery of hacked web pages before they affect search results or put someone in harm’s way.   While we reduced how spam on hacked sites affects search, hacked websites remain a major security problem affecting the safety of the web. Even though we can’t prevent a website hack from happening, we’re committed to helping webmasters whose websites have been compromised by offering resources to<a href="https://developers.google.com/web/fundamentals/security/hacked/"> help them recover from a hacked website. </a></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <b><u>User-generated spam:</u></b> A particular type of spam known as User-generated spam has been a continued focus for us. User-generated spam includes spammy posts on forums, as well as spammy accounts on free blogs and platforms, none of which are meant to be consumed by human beings, and all of which disrupt conversations while adding no value to users. In 2018, we were able to reduce the impact on search users from this type of spam by more than 80%. While we can’t prevent websites from being exploited, we do want to make it easier for website owners to learn how to protect themselves, which is why we provide resources on <a href="https://support.google.com/webmasters/answer/81749">how to prevent abuse of your site’s public areas.</a></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <b><u>Link spam:</u> </b>We continued to protect the value of authoritative and relevant links as an important ranking signal for Search. We continued to deal swiftly with egregious link spam, and made a number of bad linking practices less effective for manipulating ranking. Above all, we continued to engage with webmasters and SEOs to chip away at the many myths that have emerged over the years relating to linking practices. We continued to remind website owners that if you simply stay away from <a href="https://support.google.com/webmasters/answer/66356?hl=en">building links</a> mainly as an attempt to rank better and focus on creating great content, you should not have to worry about any of the myths or realities. We think that one of the best ways of fighting spam of all types is by encouraging website owners to just create great quality content. Resources such as the <a href="https://support.google.com/webmasters/answer/7451184">SEO starter-guide</a> highlight best practices and bust some common myths and misconceptions related to what it takes to appear well in Google Search results. <a href="https://support.google.com/webmasters/answer/93713?hl=en">Reporting link spam</a> is also a great way to assist us in fighting against this type of abuse and to help preserve fairness in Search ranking.</div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <h3 style="text-align: justify;"> Working with users, webmasters and developers for a better web</h3> <div style="text-align: justify;"> Everyday users continue to help us find spam, malware and other issues in Search that escape our filters and processes by <a href="https://support.google.com/webmasters/answer/93713">reporting spam on search</a>, <a href="https://safebrowsing.google.com/safebrowsing/report_phish/">reporting phishing</a> or  <a href="//www.google.com/safebrowsing/report_badware/">reporting malware</a>. We received over 180,000 search spam user reports and we were able to take action on 64% of the reports we processed. These reports truly make a difference and we’d like to thank all of you who submitted them. </div> <div style="text-align: justify;"> <br /> <br /></div> <div style="text-align: justify;"> We think it’s important to let website owners known when we detect something wrong with their website. In 2018, we generated over 186 million messages to website owners calling out potential improvements, issues and problems that could affect their site’s appearance on Search results. We can only deliver these notifications to site owners that verified their sites in <a href="https://search.google.com/search-console/welcome">Search Console</a>, and we successfully delivered 96 million of those messages. The rest of the messages will be kept linked with the website for as long as they are relevant, so they can be seen when a webmaster successfully registers their site in Search Console. The majority of these messages were welcoming new users to Search Console, and the second largest group was informing registered Search Console users when Mobile-First Indexing became available. Of all messages, slightly over 2%—about 4 million—were related to <a href="https://support.google.com/webmasters/answer/9044175">manual actions</a> resulting from violations of our Webmaster Guidelines. </div> <div style="text-align: justify;"> <br /> <br /></div> <div style="text-align: justify;"> High quality content keeps spam off of search results, and we continued to improve the tools and reports we offer for webmasters that create that content. The <a href="https://search.google.com/search-console/about">Google Search Console </a>was completely rebuilt from the ground up to provide both new and improved reports (<a href="https://support.google.com/webmasters/answer/7576553">Performance</a>, <a href="https://support.google.com/webmasters/answer/7440203">Index Coverage</a>, <a href="https://support.google.com/webmasters/answer/9049606">Links</a>, <a href="https://developers.google.com/search/mobile-sites/">Mobile Usability report</a>), as well as brand new features (<a href="https://webmasters.googleblog.com/2018/06/new-url-inspection-tool-more-in-search.html">URL Inspection Tool</a> and <a href="https://webmasters.googleblog.com/2018/08/collaboration-and-user-management-in.html">Site and User management)</a>. This improved Search Console graduated out of beta in 2018 and is now available generally to all registered website owners.</div> <div style="text-align: justify;"> <br /> <br /></div> <div style="text-align: justify;"> We didn’t forget the front-end developers who make the modern web work, and focused on helping them make their sites great for users and also search-friendly regardless of whether they are on a CMS, roll their own CSS and JS, or build on top of a web framework. With the new <a href="https://webmasters.googleblog.com/2018/02/seo-audit-category-in-lighthouse.html">SEO audit capability</a> in <a href="https://developers.google.com/web/tools/lighthouse/">Lighthouse</a>, the open-source and automated auditing tool for improving the quality of web pages, developers and webmasters can now run actionable <a href="https://chrome.google.com/webstore/detail/lighthouse/blipmdconlkpinefehnmjammfjpmpbjk">SEO health-checks</a> on their pages and quickly identify areas for improvement.</div> <div style="text-align: justify;"> <br /> <br /></div> <div style="text-align: justify;"> We also engage directly with website owners to provide help with thorny issues. Our dedicated team members meet with webmasters around the world regularly, both online and in-person. We delivered more than 190 <a href="https://www.google.com/intl/en/webmasters/connect/#attend-events">online office hours, online events and offline events</a> in more than 76 cities, to audiences totaling over 170,000 including SEOs, developers and online marketers. We hosted four search events in Tokyo, Singapore, Zurich and Osaka as well as an 11-city Search Conference in India. In 2018, we started live office hours in Spanish on top of English, French, German, Hindi and Japanese, where Webmasters can find help, tips and useful discussion on our <a href="https://www.youtube.com/googlewebmasters">Google Webmaster YouTube channel</a>. Product experts continued to help webmasters find solutions through our <a href="//g.co/webmasterforum">official support forums </a>in over a dozen languages. </div> <div style="text-align: justify;"> <br /> <br /></div> <div style="text-align: justify;"> We look forward to continuing our work to deliver a spam-free Search experience to all in 2019!</div> <div style="text-align: justify;"> <br /></div> <div class="separator" style="clear: both; text-align: justify;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhF2Cb72qZBBFVoRF8PRKqsc7xXV3-29vwrqKcjL8jXrGwg1K239czpvbIe_P-N0hz2t7IOaibts6wl8pSgyKVhkujLV5UGCCAOV130sZ3vDD4Yq_FIPoJYdZTLg12arorI3vB2/s1600/WebspamReport2018_2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="501" data-original-width="1400" height="228" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhF2Cb72qZBBFVoRF8PRKqsc7xXV3-29vwrqKcjL8jXrGwg1K239czpvbIe_P-N0hz2t7IOaibts6wl8pSgyKVhkujLV5UGCCAOV130sZ3vDD4Yq_FIPoJYdZTLg12arorI3vB2/s640/WebspamReport2018_2.png" width="640" /></a></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> Posted by Juan Felipe Rincón, Webmaster Outreach, Dublin</div> </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:This year in Search Spam - Webspam report 2018&url=https://webmasters.googleblog.com/2019/03/this-year-in-search-spam-webspam-report.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2019/03/this-year-in-search-spam-webspam-report.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2019/03/this-year-in-search-spam-webspam-report.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/events?hl=en' rel='tag'> events </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/forums?hl=en' rel='tag'> forums </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en' rel='tag'> webmaster community </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines?hl=en' rel='tag'> webmaster guidelines </a> </span> </div> </div> </div> <div class='post' data-id='580074058977886676' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2018/06/how-we-fought-webspam-webspam-report.html?hl=en' itemprop='url' title='How we fought webspam - Webspam Report 2017'> How we fought webspam - Webspam Report 2017 </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, June 28, 2018 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p style="padding:0.8em; border-left: 6px solid #A03; background-color:#FEE; color:#000; line-height:1.5em; font-weight:bold">Note: The information in this post may be outdated. See our latest post about <a href="https://webmasters.googleblog.com/2020/07/how-spam-reports-are-used-at-google.html">reporting spam</a>.</p> <div dir="ltr" style="text-align: left;" trbidi="on"> <img height="215" src="https://lh4.googleusercontent.com/lpMw5N0pkNSPf6i-5HUZSbr_w_I6sCSB1iBqz_ehibY6l_yDl4MNeyaJ4_6rkcVEmxpjzMH44_9W4FbOJzXPXNzr_L2QDzlI8rmm1ccHHLEkN8s0q0g7eD-dFMMtt6Of0p9CtUjR" style="border: none; font-family: Arial; font-size: 11pt; text-align: justify; transform: rotate(0rad); white-space: pre-wrap;" width="602" /><br /> <b style="font-weight: normal;"><br /></b> <br /><div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;"><br />We always want to make sure that when you use Google Search to find information, you get the highest quality results. But, we are aware of many bad actors who are trying to manipulate search ranking and profit from it, which is at odds with our core mission: to organize the world's information and make it universally accessible and useful. Over the years, we've devoted a huge effort toward combating abuse and spam on Search. Here's a look at how we fought abuse in 2017.<br /> <br /><br />We call these various types of abuse that violate the <a href="https://support.google.com/webmasters/answer/35769">webmaster guidelines</a> “spam.” Our evaluation indicated that for many years, less than 1 percent of search results users visited are spammy. In the last couple of years, we’ve managed to further reduce this by half. </span></div> <div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: justify;"> <span style="background-color: transparent; color: black; font-family: Arial; font-style: normal; font-variant: normal; font-weight: 700; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"><br /></span></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: justify;"> <span style="background-color: transparent; color: black; font-family: Arial; font-style: normal; font-variant: normal; font-weight: 700; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"><br /></span></div> <h3 style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: justify;"> <span style="background-color: transparent; color: black; font-family: Arial; font-style: normal; font-variant: normal; font-weight: 700; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Google webspam trends and how we fought webspam in 2017</span></h3> <b style="font-weight: normal;"><br /></b> <div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div> <div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;">As we continued to improve, spammers also evolved. One of the trends in 2017 was an increase in website hacking—both for spamming search ranking and for spreading malware. Hacked websites are serious threats to users because hackers can take complete control of a site, deface homepages, erase relevant content, or insert malware and harmful code. They may also record keystrokes, stealing login credentials for online banking or financial transactions. In 2017 we focused on reducing this threat, and were able to detect and remove from search results more than 80 percent of these sites. But hacking is not just a spam problem for search users—it affects the owners of websites as well. To help website owners keep their websites safe, we created a <a href="https://learnwebtech.withgoogle.com/">hands-on resource to help webmasters strengthen their websites’ security</a> and revamped our <a href="https://developers.google.com/web/fundamentals/security/hacked/">help resources to help webmasters recover from a hacked website</a>. The guides are available in 19 languages.<br /><br /></span></div> <div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;">We’re also recognizing the importance of robust content management systems (CMSs). A large percentage of websites are run on one of several popular CMSs, and subsequently spammers exploited them by finding ways to abuse their provisions for user-generated content, such as posting spam content in comment sections or forums. We’re working closely with many of the providers of popular content management systems like WordPress and Joomla to help them also fight spammers that abuse their forums, comment sections and websites.<br /><br /><br />Another abuse vector is the manipulation of links, which is one of the foundation ranking signals for Search. In 2017 we doubled down our effort in removing <a href="https://support.google.com/webmasters/answer/2604774?hl=en">unnatural links</a> via ranking improvements and scalable manual actions. We have observed a year-over-year reduction of spam links by almost half.<br /> </span></div> <div style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: left;"> <span style="background-color: transparent; color: black; font-style: normal; font-variant: normal; font-weight: 700; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></span></div> <div style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: left;"> <span style="background-color: transparent; color: black; font-style: normal; font-variant: normal; font-weight: 700; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></span></div> <h3 style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: left;"> <span style="background-color: transparent; color: black; font-style: normal; font-variant: normal; font-weight: 700; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"><span style="font-family: Arial, Helvetica, sans-serif;">W</span></span><span style="background-color: transparent; color: black; font-family: Arial; font-style: normal; font-variant: normal; font-weight: 700; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">orking with users and webmasters for a better web</span></h3> <br /> <div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div> <div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;">We’re here to listen: Our automated systems are constantly working to detect and block spam. Still, we always welcome hearing from you when something seems … phishy. Last year, we were able to take action on nearly 90,000 <a href="https://www.google.com/webmasters/tools/spamreport?pli=1">user reports</a> of search spam.</span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div> <div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div> <div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;">Reporting spam, malware and other issues you find helps us protect the site owner and other searchers from this abuse. You can file a <a href="https://support.google.com/webmasters/answer/93713">spam report</a>, a <a href="https://safebrowsing.google.com/safebrowsing/report_phish/">phishing report</a> or a <a href="//www.google.com/safebrowsing/report_badware/">malware report.</a> We very much appreciate these reports—a big THANK YOU to all of you who submitted them.</span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;">We also actively work with webmasters to maintain the health of the web ecosystem. </span><span style="font-family: Arial, Helvetica, sans-serif;">Last year, we sent 45 million messages to registered website owners via <a href="https://www.google.com/webmasters/tools/">Search Console</a> letting them know about issues we identified with their websites. More than 6 million of these messages are related to <a href="https://support.google.com/webmasters/answer/2604824">manual actions,</a> providing transparency to webmasters so they understand why their sites got manual actions and how to resolve the issue.</span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;">Last year, we <a href="https://webmasters.googleblog.com/2017/08/a-sneak-peek-at-two-experimental.html">released a beta version</a> of a new Search Console to a limited number of users and afterwards, to all users of Search Console. We listened to what matters most to the users, and started with popular functionalities such as <a href="https://support.google.com/webmasters/answer/7576553">Search performance</a>, <a href="https://support.google.com/webmasters/answer/7440203">Index Coverage</a> and others. These can help webmasters optimize their websites' Google Search presence more easily.</span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;">Through enhanced <a href="https://safebrowsing.google.com/">Safe Browsing</a> protections, we continue to protect more users from bad actors online. In the last year, we have made significant improvements to our safe browsing protection, such as broadening our <a href="https://security.googleblog.com/2017/03/expanding-protection-for-chrome-users.html">protection of macOS devices</a>, enabling <a href="https://www.blog.google/topics/safety-security/new-security-protections-tailored-you/">predictive phishing protection</a> in Chrome, cracked down on <a href="https://security.googleblog.com/2017/12/additional-protections-by-safe-browsing.html">mobile unwanted software</a>, and launched significant improvements to our ability to protect users from <a href="https://blog.chromium.org/2018/01/further-protecting-users-from-deceptive.html">deceptive Chrome extension installation</a>.</span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;">We have a multitude of channels to engage directly with webmasters. We have dedicated team members who meet with webmasters regularly both online and in-person. We conducted more than 250 <a href="https://www.google.com/intl/en/webmasters/connect/#attend-events">online office hours, online events and offline events</a> around the world in more than 60 cities to audiences totaling over 220,000 website owners, webmasters and digital marketers. In addition, our <a href="//g.co/webmasterforum">official support forum</a> has answered a high volume of questions in many languages. Last year, the forum had 63,000 threads generating over 280,000 contributing posts by 100+ <a href="https://topcontributor.withgoogle.com/profiles">Top Contributors</a> globally. For more details, see this <a href="https://webmasters.googleblog.com/2018/05/helping-webmasters-and-content.html">post</a>. Apart from the <a href="https://productforums.google.com/forum/#!forum/webmasters">forums</a>, <a href="https://webmasters.googleblog.com/">blogs</a> and <a href="https://support.google.com/webmasters/answer/7451184">the SEO starter guide</a>, the <a href="https://www.youtube.com/googlewebmasters">Google Webmaster YouTube channel</a> is another channel to find more tips and insights. We launched a new <a href="https://webmasters.googleblog.com/2017/12/the-seo-snippets-video-series.html">SEO snippets</a> video series to help with short and to-the-point answers to specific questions. Be sure to subscribe to the <a href="https://www.youtube.com/googlewebmasters">channel</a>!</span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;">Despite all these improvements, we know we’re not yet done. We’re relentless in our pursue of an abuse-free user experience, and will keep improving our collaboration with the ecosystem to make it happen.</span></div> <div style="text-align: left;"> <b style="font-weight: normal;"><br /></b></div> <img height="227" src="https://lh5.googleusercontent.com/Pfgdv2iIS4iWz96Qdnj5pONl1vHFYEdMWdRR2I2tfrwk-MjZm6YmnFf3lOvAiBDi5Fa4vIaDFdJoDe0lbGWfy-WoCTBDNdGFk3dOnZOTjBP1URZzM0yNJII3KJbRDjeYBWRROwni" width="640" /><div style="text-align: left;"> <br /></div> <div style="text-align: left;"> <br /></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: justify;"> <span style="background-color: transparent; color: black; font-family: Arial; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Posted by Cody Kwok, Principal Engineer</span></div> </div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p style="padding:0.8em; border-left: 6px solid #A03; background-color:#FEE; color:#000; line-height:1.5em; font-weight:bold">Note: The information in this post may be outdated. See our latest post about <a href="https://webmasters.googleblog.com/2020/07/how-spam-reports-are-used-at-google.html">reporting spam</a>.</p> <div dir="ltr" style="text-align: left;" trbidi="on"> <img height="215" src="https://lh4.googleusercontent.com/lpMw5N0pkNSPf6i-5HUZSbr_w_I6sCSB1iBqz_ehibY6l_yDl4MNeyaJ4_6rkcVEmxpjzMH44_9W4FbOJzXPXNzr_L2QDzlI8rmm1ccHHLEkN8s0q0g7eD-dFMMtt6Of0p9CtUjR" style="border: none; font-family: Arial; font-size: 11pt; text-align: justify; transform: rotate(0rad); white-space: pre-wrap;" width="602" /><br /> <b style="font-weight: normal;"><br /></b> <br /><div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;"><br />We always want to make sure that when you use Google Search to find information, you get the highest quality results. But, we are aware of many bad actors who are trying to manipulate search ranking and profit from it, which is at odds with our core mission: to organize the world's information and make it universally accessible and useful. Over the years, we've devoted a huge effort toward combating abuse and spam on Search. Here's a look at how we fought abuse in 2017.<br /> <br /><br />We call these various types of abuse that violate the <a href="https://support.google.com/webmasters/answer/35769">webmaster guidelines</a> “spam.” Our evaluation indicated that for many years, less than 1 percent of search results users visited are spammy. In the last couple of years, we’ve managed to further reduce this by half. </span></div> <div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: justify;"> <span style="background-color: transparent; color: black; font-family: Arial; font-style: normal; font-variant: normal; font-weight: 700; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"><br /></span></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: justify;"> <span style="background-color: transparent; color: black; font-family: Arial; font-style: normal; font-variant: normal; font-weight: 700; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"><br /></span></div> <h3 style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: justify;"> <span style="background-color: transparent; color: black; font-family: Arial; font-style: normal; font-variant: normal; font-weight: 700; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Google webspam trends and how we fought webspam in 2017</span></h3> <b style="font-weight: normal;"><br /></b> <div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div> <div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;">As we continued to improve, spammers also evolved. One of the trends in 2017 was an increase in website hacking—both for spamming search ranking and for spreading malware. Hacked websites are serious threats to users because hackers can take complete control of a site, deface homepages, erase relevant content, or insert malware and harmful code. They may also record keystrokes, stealing login credentials for online banking or financial transactions. In 2017 we focused on reducing this threat, and were able to detect and remove from search results more than 80 percent of these sites. But hacking is not just a spam problem for search users—it affects the owners of websites as well. To help website owners keep their websites safe, we created a <a href="https://learnwebtech.withgoogle.com/">hands-on resource to help webmasters strengthen their websites’ security</a> and revamped our <a href="https://developers.google.com/web/fundamentals/security/hacked/">help resources to help webmasters recover from a hacked website</a>. The guides are available in 19 languages.<br /><br /></span></div> <div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;">We’re also recognizing the importance of robust content management systems (CMSs). A large percentage of websites are run on one of several popular CMSs, and subsequently spammers exploited them by finding ways to abuse their provisions for user-generated content, such as posting spam content in comment sections or forums. We’re working closely with many of the providers of popular content management systems like WordPress and Joomla to help them also fight spammers that abuse their forums, comment sections and websites.<br /><br /><br />Another abuse vector is the manipulation of links, which is one of the foundation ranking signals for Search. In 2017 we doubled down our effort in removing <a href="https://support.google.com/webmasters/answer/2604774?hl=en">unnatural links</a> via ranking improvements and scalable manual actions. We have observed a year-over-year reduction of spam links by almost half.<br /> </span></div> <div style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: left;"> <span style="background-color: transparent; color: black; font-style: normal; font-variant: normal; font-weight: 700; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></span></div> <div style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: left;"> <span style="background-color: transparent; color: black; font-style: normal; font-variant: normal; font-weight: 700; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></span></div> <h3 style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: left;"> <span style="background-color: transparent; color: black; font-style: normal; font-variant: normal; font-weight: 700; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"><span style="font-family: Arial, Helvetica, sans-serif;">W</span></span><span style="background-color: transparent; color: black; font-family: Arial; font-style: normal; font-variant: normal; font-weight: 700; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">orking with users and webmasters for a better web</span></h3> <br /> <div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div> <div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;">We’re here to listen: Our automated systems are constantly working to detect and block spam. Still, we always welcome hearing from you when something seems … phishy. Last year, we were able to take action on nearly 90,000 <a href="https://www.google.com/webmasters/tools/spamreport?pli=1">user reports</a> of search spam.</span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div> <div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div> <div style="text-align: left;"> <span style="font-family: Arial, Helvetica, sans-serif;">Reporting spam, malware and other issues you find helps us protect the site owner and other searchers from this abuse. You can file a <a href="https://support.google.com/webmasters/answer/93713">spam report</a>, a <a href="https://safebrowsing.google.com/safebrowsing/report_phish/">phishing report</a> or a <a href="//www.google.com/safebrowsing/report_badware/">malware report.</a> We very much appreciate these reports—a big THANK YOU to all of you who submitted them.</span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;">We also actively work with webmasters to maintain the health of the web ecosystem. </span><span style="font-family: Arial, Helvetica, sans-serif;">Last year, we sent 45 million messages to registered website owners via <a href="https://www.google.com/webmasters/tools/">Search Console</a> letting them know about issues we identified with their websites. More than 6 million of these messages are related to <a href="https://support.google.com/webmasters/answer/2604824">manual actions,</a> providing transparency to webmasters so they understand why their sites got manual actions and how to resolve the issue.</span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;">Last year, we <a href="https://webmasters.googleblog.com/2017/08/a-sneak-peek-at-two-experimental.html">released a beta version</a> of a new Search Console to a limited number of users and afterwards, to all users of Search Console. We listened to what matters most to the users, and started with popular functionalities such as <a href="https://support.google.com/webmasters/answer/7576553">Search performance</a>, <a href="https://support.google.com/webmasters/answer/7440203">Index Coverage</a> and others. These can help webmasters optimize their websites' Google Search presence more easily.</span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;">Through enhanced <a href="https://safebrowsing.google.com/">Safe Browsing</a> protections, we continue to protect more users from bad actors online. In the last year, we have made significant improvements to our safe browsing protection, such as broadening our <a href="https://security.googleblog.com/2017/03/expanding-protection-for-chrome-users.html">protection of macOS devices</a>, enabling <a href="https://www.blog.google/topics/safety-security/new-security-protections-tailored-you/">predictive phishing protection</a> in Chrome, cracked down on <a href="https://security.googleblog.com/2017/12/additional-protections-by-safe-browsing.html">mobile unwanted software</a>, and launched significant improvements to our ability to protect users from <a href="https://blog.chromium.org/2018/01/further-protecting-users-from-deceptive.html">deceptive Chrome extension installation</a>.</span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;">We have a multitude of channels to engage directly with webmasters. We have dedicated team members who meet with webmasters regularly both online and in-person. We conducted more than 250 <a href="https://www.google.com/intl/en/webmasters/connect/#attend-events">online office hours, online events and offline events</a> around the world in more than 60 cities to audiences totaling over 220,000 website owners, webmasters and digital marketers. In addition, our <a href="//g.co/webmasterforum">official support forum</a> has answered a high volume of questions in many languages. Last year, the forum had 63,000 threads generating over 280,000 contributing posts by 100+ <a href="https://topcontributor.withgoogle.com/profiles">Top Contributors</a> globally. For more details, see this <a href="https://webmasters.googleblog.com/2018/05/helping-webmasters-and-content.html">post</a>. Apart from the <a href="https://productforums.google.com/forum/#!forum/webmasters">forums</a>, <a href="https://webmasters.googleblog.com/">blogs</a> and <a href="https://support.google.com/webmasters/answer/7451184">the SEO starter guide</a>, the <a href="https://www.youtube.com/googlewebmasters">Google Webmaster YouTube channel</a> is another channel to find more tips and insights. We launched a new <a href="https://webmasters.googleblog.com/2017/12/the-seo-snippets-video-series.html">SEO snippets</a> video series to help with short and to-the-point answers to specific questions. Be sure to subscribe to the <a href="https://www.youtube.com/googlewebmasters">channel</a>!</span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><span style="font-family: Arial, Helvetica, sans-serif;">Despite all these improvements, we know we’re not yet done. We’re relentless in our pursue of an abuse-free user experience, and will keep improving our collaboration with the ecosystem to make it happen.</span></div> <div style="text-align: left;"> <b style="font-weight: normal;"><br /></b></div> <img height="227" src="https://lh5.googleusercontent.com/Pfgdv2iIS4iWz96Qdnj5pONl1vHFYEdMWdRR2I2tfrwk-MjZm6YmnFf3lOvAiBDi5Fa4vIaDFdJoDe0lbGWfy-WoCTBDNdGFk3dOnZOTjBP1URZzM0yNJII3KJbRDjeYBWRROwni" width="640" /><div style="text-align: left;"> <br /></div> <div style="text-align: left;"> <br /></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: justify;"> <span style="background-color: transparent; color: black; font-family: Arial; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Posted by Cody Kwok, Principal Engineer</span></div> </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 we fought webspam - Webspam Report 2017&url=https://webmasters.googleblog.com/2018/06/how-we-fought-webspam-webspam-report.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2018/06/how-we-fought-webspam-webspam-report.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2018/06/how-we-fought-webspam-webspam-report.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/events?hl=en' rel='tag'> events </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/forums?hl=en' rel='tag'> forums </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en' rel='tag'> webmaster community </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines?hl=en' rel='tag'> webmaster guidelines </a> </span> </div> </div> </div> <div class='post' data-id='4569728119316191475' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2018/03/seo-snippets-hindi-video-series.html?hl=en' itemprop='url' title='Introducing the Webmaster Video Series, now in Hindi'> Introducing the Webmaster Video Series, now in Hindi </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, March 08, 2018 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> Google offers a broad range of resources, in multiple languages, to help you better understand your website and improve its performance. The recently released <a href="https://support.google.com/webmasters/answer/7451184" rel="" target="_blank">Search Engine Optimization (SEO) Starter Guide</a>, the <a href="https://support.google.com/webmasters/?hl=en#topic=3309469" target="_blank">Help Center</a>, the <a href="https://productforums.google.com/forum/#!forum/webmasters" target="_blank">Webmaster forums</a> (which are available in 16 languages), and the various Webmaster blogs are just a few of them.<br /> A few months ago, we launched the <a href="https://webmasters.googleblog.com/2017/12/the-seo-snippets-video-series.html" target="_blank">SEO Snippets</a> video series, where the Google team answered some of the webmaster and SEO questions that we regularly see on the Webmaster Central Help Forum. We are now launching a similar series in Hindi, called the <a href="https://www.youtube.com/watch?v=MHUQcTgk8SE&list=PLKoqnv2vTMUO0d7lhi5lpPSHmLqs8pV8J" target="_blank">SEO Snippets in Hindi</a>.<br /> <iframe allow="encrypted-media" allowfullscreen="" frameborder="0" gesture="media" height="315" src="https://www.youtube.com/embed/MHUQcTgk8SE?list=PLKoqnv2vTMUO0d7lhi5lpPSHmLqs8pV8J" width="560"></iframe> <br /> From deciding what language to create content in (Hindi vs. Hinglish) to duplicate content, we’re answering the most frequently asked questions on the <a href="https://productforums.google.com/forum/#!forum/webmaster-hi" target="_blank">Hindi Webmaster forum</a> and the <a href="https://plus.google.com/communities/117770100248014494227" target="_blank">India Webmaster community on Google+</a>, in Hindi.<br /> Check out the links shared in the videos to get more helpful webmaster information, drop by our <a href="https://support.google.com/webmasters/go/community">help forum</a> and subscribe to our <a href="https://www.youtube.com/googlewebmasters">YouTube channel</a> for more tips and insights!<br /> <br /> <span class="byline-author">Posted by Syed Malik, Google Search Outreach</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 offers a broad range of resources, in multiple languages, to help you better understand your website and improve its performance. The recently released <a href="https://support.google.com/webmasters/answer/7451184" rel="" target="_blank">Search Engine Optimization (SEO) Starter Guide</a>, the <a href="https://support.google.com/webmasters/?hl=en#topic=3309469" target="_blank">Help Center</a>, the <a href="https://productforums.google.com/forum/#!forum/webmasters" target="_blank">Webmaster forums</a> (which are available in 16 languages), and the various Webmaster blogs are just a few of them.<br /> A few months ago, we launched the <a href="https://webmasters.googleblog.com/2017/12/the-seo-snippets-video-series.html" target="_blank">SEO Snippets</a> video series, where the Google team answered some of the webmaster and SEO questions that we regularly see on the Webmaster Central Help Forum. We are now launching a similar series in Hindi, called the <a href="https://www.youtube.com/watch?v=MHUQcTgk8SE&list=PLKoqnv2vTMUO0d7lhi5lpPSHmLqs8pV8J" target="_blank">SEO Snippets in Hindi</a>.<br /> <iframe allow="encrypted-media" allowfullscreen="" frameborder="0" gesture="media" height="315" src="https://www.youtube.com/embed/MHUQcTgk8SE?list=PLKoqnv2vTMUO0d7lhi5lpPSHmLqs8pV8J" width="560"></iframe> <br /> From deciding what language to create content in (Hindi vs. Hinglish) to duplicate content, we’re answering the most frequently asked questions on the <a href="https://productforums.google.com/forum/#!forum/webmaster-hi" target="_blank">Hindi Webmaster forum</a> and the <a href="https://plus.google.com/communities/117770100248014494227" target="_blank">India Webmaster community on Google+</a>, in Hindi.<br /> Check out the links shared in the videos to get more helpful webmaster information, drop by our <a href="https://support.google.com/webmasters/go/community">help forum</a> and subscribe to our <a href="https://www.youtube.com/googlewebmasters">YouTube channel</a> for more tips and insights!<br /> <br /> <span class="byline-author">Posted by Syed Malik, Google Search Outreach</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:Introducing the Webmaster Video Series, now in Hindi&url=https://webmasters.googleblog.com/2018/03/seo-snippets-hindi-video-series.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2018/03/seo-snippets-hindi-video-series.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2018/03/seo-snippets-hindi-video-series.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/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/questions?hl=en' rel='tag'> questions </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/video?hl=en' rel='tag'> video </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en' rel='tag'> webmaster community </a> </span> </div> </div> </div> <div class='post' data-id='3604970777135494012' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2018/02/how-listening-to-our-users-helped-us.html?hl=en' itemprop='url' title='How listening to our users helped us build a better Search Console'> How listening to our users helped us build a better Search Console </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, February 06, 2018 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> The new Search Console beta is up and running. We’ve been flexing our listening muscles and finding new ways to incorporate your feedback into the design. In this new release we've initially focused on building features supporting the users’ main goals and we'll be expanding functionality in the months to come. While some changes have been long expected, like refreshing the UI with Material Design, many changes are a result of continuous work with you, the Search Console users.<br /> We’ve used 3 main communication channels to hear what our users are saying: <br /> <ul> <li><strong>Help forum Top Contributors</strong> - <a href="https://topcontributor.withgoogle.com/">Top Contributors</a> in our <a href="https://support.google.com/webmasters/go/community">help forums</a> have been very helpful in bringing up topics seen in the forums. They communicate regularly with Google’s Search teams, and help the large community of Search Console users.</li> <li><strong>Open feedback</strong> - We analyzed open feedback comments about classic Search Console and identified the top requests coming in. Open feedback can be sent via the ‘Submit feedback’ button in Search Console. This open feedback helped us get more context around one of the top requests from the last years: more than 90 days of data in the Search Analytics (Performance) report. We learned of the need to compare to a similar period in the previous year, which confirmed that our decision to include 16 months of data might be on the right track.</li> <li><strong>Search Console panel</strong> - Last year we created a new communication channel by enlisting a group of four hundred randomly selected Search Console users, representing websites of all sizes. The panel members took part in almost every design iteration we had throughout the year, from explorations of new concepts through surveys, interviews and usability tests. The Search Console panel members have been providing valuable feedback which helped us test our assumptions and improve designs.</li> </ul> In one of these rounds we tested the new suggested design for the Performance report. Specifically we wanted to see whether it was clear how to use the ‘compare’ and ‘filter’ functionalities. To create an experience that felt as real as possible, we used a high fidelity prototype connected to real data. The prototype allowed study participants to freely interact with the user interface before even one row of production code had been written.<br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQZ0Jnv7aCSuoHCpzq9r-UijF6UNjIxQlLo73NGkdO9HO45z1NtDN_2ILXhfQ2fMuxd26bhNUAXRc3xiXd2W7Q9-m0XetCIAt0VKIPq9fi9eUMi-6_GMYXRu5HErWp-ChcDKSc/s1600/search-console-performance-gif-100%2525-speed.gif" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="706" data-original-width="1280" height="177" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQZ0Jnv7aCSuoHCpzq9r-UijF6UNjIxQlLo73NGkdO9HO45z1NtDN_2ILXhfQ2fMuxd26bhNUAXRc3xiXd2W7Q9-m0XetCIAt0VKIPq9fi9eUMi-6_GMYXRu5HErWp-ChcDKSc/s640/search-console-performance-gif-100%2525-speed.gif" width="320" /></a></div> In this study we learned that the ‘compare’ functionality was often overlooked. We consequently changed the design with ‘filter’ and ‘compare’ appearing in a unified dialogue box, triggered when the ‘Add new’ chip is clicked. We continue to test this design and others to optimize its usability and usefulness.<br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvSz2GMgRNyrcUTtcDrp7pABWCGtNEMv7p8H3p6h0g4FWz3hSnTe117RuhiH0VkhQHX51fkjf4db9PEH5g6SJIKKC9DVuqEV92vqG75J7rRhEIvRoW8mIweE-OdL4l-3JS-T5G/s1600/search-console-comparison-functionality.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="730" data-original-width="1024" height="228" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvSz2GMgRNyrcUTtcDrp7pABWCGtNEMv7p8H3p6h0g4FWz3hSnTe117RuhiH0VkhQHX51fkjf4db9PEH5g6SJIKKC9DVuqEV92vqG75J7rRhEIvRoW8mIweE-OdL4l-3JS-T5G/s640/search-console-comparison-functionality.png" width="320" /></a></div> We incorporated user feedback not only in practical design details, but also in architectural decisions. For example, user feedback led us to make major changes in the product’s core information architecture influencing the navigation and product structure of the new Search Console. The error and coverage reports were originally separated which could lead to multiple views of the same error. As a result of user feedback we united the error and coverage reporting offering one holistic view.<br /> As the launch date grew closer, we performed several larger scale experiments. We A/B tested some of the new Search Console reports against the existing reports with 30,000 users. We tracked issue fix rates to verify new Search Console drives better results and sent out follow-up surveys to learn about their experience. This most recent feedback confirmed that export functionality was not a nice-to-have, but rather a requirement for many users and helped us tune detailed help pages in the initial release. <br /> We are happy to announce that the new Search Console is now available to all sites. Whether it is through Search Console’s feedback button or through the user panel, we truly value a collaborative design process, where all of our users can help us build the best product.<br /> <a href="https://search.google.com/search-console">Try out the new search console</a>.<br /> We're not finished yet! Which feature would you love to see in the next iteration of Search Console? Let us know below.<br /> <span class="byline-author">Posted by the Search Console UX 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"> The new Search Console beta is up and running. We’ve been flexing our listening muscles and finding new ways to incorporate your feedback into the design. In this new release we've initially focused on building features supporting the users’ main goals and we'll be expanding functionality in the months to come. While some changes have been long expected, like refreshing the UI with Material Design, many changes are a result of continuous work with you, the Search Console users.<br /> We’ve used 3 main communication channels to hear what our users are saying: <br /> <ul> <li><strong>Help forum Top Contributors</strong> - <a href="https://topcontributor.withgoogle.com/">Top Contributors</a> in our <a href="https://support.google.com/webmasters/go/community">help forums</a> have been very helpful in bringing up topics seen in the forums. They communicate regularly with Google’s Search teams, and help the large community of Search Console users.</li> <li><strong>Open feedback</strong> - We analyzed open feedback comments about classic Search Console and identified the top requests coming in. Open feedback can be sent via the ‘Submit feedback’ button in Search Console. This open feedback helped us get more context around one of the top requests from the last years: more than 90 days of data in the Search Analytics (Performance) report. We learned of the need to compare to a similar period in the previous year, which confirmed that our decision to include 16 months of data might be on the right track.</li> <li><strong>Search Console panel</strong> - Last year we created a new communication channel by enlisting a group of four hundred randomly selected Search Console users, representing websites of all sizes. The panel members took part in almost every design iteration we had throughout the year, from explorations of new concepts through surveys, interviews and usability tests. The Search Console panel members have been providing valuable feedback which helped us test our assumptions and improve designs.</li> </ul> In one of these rounds we tested the new suggested design for the Performance report. Specifically we wanted to see whether it was clear how to use the ‘compare’ and ‘filter’ functionalities. To create an experience that felt as real as possible, we used a high fidelity prototype connected to real data. The prototype allowed study participants to freely interact with the user interface before even one row of production code had been written.<br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQZ0Jnv7aCSuoHCpzq9r-UijF6UNjIxQlLo73NGkdO9HO45z1NtDN_2ILXhfQ2fMuxd26bhNUAXRc3xiXd2W7Q9-m0XetCIAt0VKIPq9fi9eUMi-6_GMYXRu5HErWp-ChcDKSc/s1600/search-console-performance-gif-100%2525-speed.gif" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="706" data-original-width="1280" height="177" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQZ0Jnv7aCSuoHCpzq9r-UijF6UNjIxQlLo73NGkdO9HO45z1NtDN_2ILXhfQ2fMuxd26bhNUAXRc3xiXd2W7Q9-m0XetCIAt0VKIPq9fi9eUMi-6_GMYXRu5HErWp-ChcDKSc/s640/search-console-performance-gif-100%2525-speed.gif" width="320" /></a></div> In this study we learned that the ‘compare’ functionality was often overlooked. We consequently changed the design with ‘filter’ and ‘compare’ appearing in a unified dialogue box, triggered when the ‘Add new’ chip is clicked. We continue to test this design and others to optimize its usability and usefulness.<br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvSz2GMgRNyrcUTtcDrp7pABWCGtNEMv7p8H3p6h0g4FWz3hSnTe117RuhiH0VkhQHX51fkjf4db9PEH5g6SJIKKC9DVuqEV92vqG75J7rRhEIvRoW8mIweE-OdL4l-3JS-T5G/s1600/search-console-comparison-functionality.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="730" data-original-width="1024" height="228" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvSz2GMgRNyrcUTtcDrp7pABWCGtNEMv7p8H3p6h0g4FWz3hSnTe117RuhiH0VkhQHX51fkjf4db9PEH5g6SJIKKC9DVuqEV92vqG75J7rRhEIvRoW8mIweE-OdL4l-3JS-T5G/s640/search-console-comparison-functionality.png" width="320" /></a></div> We incorporated user feedback not only in practical design details, but also in architectural decisions. For example, user feedback led us to make major changes in the product’s core information architecture influencing the navigation and product structure of the new Search Console. The error and coverage reports were originally separated which could lead to multiple views of the same error. As a result of user feedback we united the error and coverage reporting offering one holistic view.<br /> As the launch date grew closer, we performed several larger scale experiments. We A/B tested some of the new Search Console reports against the existing reports with 30,000 users. We tracked issue fix rates to verify new Search Console drives better results and sent out follow-up surveys to learn about their experience. This most recent feedback confirmed that export functionality was not a nice-to-have, but rather a requirement for many users and helped us tune detailed help pages in the initial release. <br /> We are happy to announce that the new Search Console is now available to all sites. Whether it is through Search Console’s feedback button or through the user panel, we truly value a collaborative design process, where all of our users can help us build the best product.<br /> <a href="https://search.google.com/search-console">Try out the new search console</a>.<br /> We're not finished yet! Which feature would you love to see in the next iteration of Search Console? Let us know below.<br /> <span class="byline-author">Posted by the Search Console UX 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:How listening to our users helped us build a better Search Console&url=https://webmasters.googleblog.com/2018/02/how-listening-to-our-users-helped-us.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2018/02/how-listening-to-our-users-helped-us.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2018/02/how-listening-to-our-users-helped-us.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/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/UX?hl=en' rel='tag'> UX </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en' rel='tag'> webmaster community </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='4516182304328193300' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/12/the-seo-snippets-video-series.html?hl=en' itemprop='url' title='Introducing the new Webmaster Video Series'> Introducing the new Webmaster Video Series </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, December 21, 2017 </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>Google has a broad range of resources to help you better understand your website and improve its performance. This Webmaster Central Blog, the Help Center, the Webmaster forum, and the recently released <a href="https://support.google.com/webmasters/answer/7451184">Search Engine Optimization (SEO) Starter Guide</a> are just a few. </p> <p>We also have a YouTube channel, for answers to your questions in video format. To help with short & to the point answers to specific questions, we've just launched a new series, which we call <a href="https://www.youtube.com/watch?v=p74HC4x5AUE&list=PLKoqnv2vTMUPhLQ054sMg3vgzy9md9tWg">SEO Snippets.</a></p> <iframe width="560" height="315" src="https://www.youtube.com/embed/p74HC4x5AUE?list=PLKoqnv2vTMUPhLQ054sMg3vgzy9md9tWg" frameborder="0" gesture="media" allow="encrypted-media" allowfullscreen></iframe> <p>In this series of short videos, the Google team will be answering some of the webmaster and SEO questions that we regularly see on the <a href="https://support.google.com/webmasters/go/community">Webmaster Central Help Forum</a>. From 404 errors, how and when crawling works, a site's URL structure, to duplicate content, we'll have something here for you.</p> <p>Check out the links shared in the videos to get more helpful webmaster information, drop by our <a href="https://support.google.com/webmasters/go/community">help forum</a> and subscribe to our <a href="https://www.youtube.com/googlewebmasters">YouTube channel</a> for more tips and insights!</p> <br> <span class="byline-author">Posted by Aurora Morales, Google Search Outreach</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>Google has a broad range of resources to help you better understand your website and improve its performance. This Webmaster Central Blog, the Help Center, the Webmaster forum, and the recently released <a href="https://support.google.com/webmasters/answer/7451184">Search Engine Optimization (SEO) Starter Guide</a> are just a few. </p> <p>We also have a YouTube channel, for answers to your questions in video format. To help with short & to the point answers to specific questions, we've just launched a new series, which we call <a href="https://www.youtube.com/watch?v=p74HC4x5AUE&list=PLKoqnv2vTMUPhLQ054sMg3vgzy9md9tWg">SEO Snippets.</a></p> <iframe width="560" height="315" src="https://www.youtube.com/embed/p74HC4x5AUE?list=PLKoqnv2vTMUPhLQ054sMg3vgzy9md9tWg" frameborder="0" gesture="media" allow="encrypted-media" allowfullscreen></iframe> <p>In this series of short videos, the Google team will be answering some of the webmaster and SEO questions that we regularly see on the <a href="https://support.google.com/webmasters/go/community">Webmaster Central Help Forum</a>. From 404 errors, how and when crawling works, a site's URL structure, to duplicate content, we'll have something here for you.</p> <p>Check out the links shared in the videos to get more helpful webmaster information, drop by our <a href="https://support.google.com/webmasters/go/community">help forum</a> and subscribe to our <a href="https://www.youtube.com/googlewebmasters">YouTube channel</a> for more tips and insights!</p> <br> <span class="byline-author">Posted by Aurora Morales, Google Search Outreach</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:Introducing the new Webmaster Video Series&url=https://webmasters.googleblog.com/2017/12/the-seo-snippets-video-series.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/12/the-seo-snippets-video-series.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/12/the-seo-snippets-video-series.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/beginner?hl=en' rel='tag'> beginner </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/video?hl=en' rel='tag'> video </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en' rel='tag'> webmaster community </a> </span> </div> </div> </div> <div class='post' data-id='3949086383067022203' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/08/a-sneak-peek-at-two-experimental.html?hl=en' itemprop='url' title='The new Search Console: a sneak peek at two experimental features'> The new Search Console: a sneak peek at two experimental features </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, August 01, 2017 </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"> Search Console was <a href="http://sitemaps.blogspot.ch/2005/11/more-stats.html">initially launched</a> with just four reports more than a decade ago. Today, the product includes more than two dozen reports and tools covering AMP, structured data, and live testing tools, all designed to help improve your site's performance on Google Search.<br /> Now we have decided to embark on an extensive redesign to better serve you, our users. Our hope is that this redesign will provide you with:<br /> <ul> <li><strong>More actionable insights</strong> - We will now group the identified issues by what we suspect is the common “root-cause” to help you find where you should fix your code. We organize these issues into tasks that have a state (similar to bug tracking systems) so you can easily see whether the issue is still open, whether Google has detected your fix, and track the progress of re-processing the affected pages. </li> <li><strong>Better support of your organizational workflow</strong> - As we talked to many organizations, we’ve learned that multiple people are typically involved in implementing, diagnosing, and fixing issues. This is why we are introducing sharing functionality that allows you to pick-up an action item and share it with other people in your group, like developers who will get references to the code in question.</li> <li><strong>Faster feedback loops between you and Google</strong> - We’ve built a mechanism to allow you to iterate quickly on your fixes, and not waste time waiting for Google to recrawl your site, only to tell you later that it’s not fixed yet. Rather, we’ll provide on-the-spot testing of fixes and are automatically speeding up crawling once we see things are ok. Similarly, the testing tools will include code snippets and a search preview - so you can quickly see where your issues are, confirm you've fixed them, and see how the pages will look on Search.</li> </ul> </div> In the next few weeks, we're releasing two exciting BETA features from the new Search Console to a small set of users — Index Coverage report and AMP fixing flow.<br /> <h3></h3> The new Index Coverage report shows the count of indexed pages, information about why some pages could not be indexed, along with example pages and tips on how to fix indexing issues. It also enables a simple sitemap submission flow, and the capability to filter all Index Coverage data to any of the submitted sitemaps.<br /> Here’s a peek of our new Index Coverage report:<br /> <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2fRZ-57fe2pPfNWl58UGOQ2rRI0RKvRtIyuy-8PaJAilWgY5YaMKb3iryM6Uv_tLcIT0keukO9Byvq4e9LEoGtT4tbN5hgcOIoi2AT2DufG3A3bDzBIRfsE4WwPpfh0VM4BLF/s1600/New+Search+Console+index+status+report+screenshot.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="913" data-original-width="1007" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2fRZ-57fe2pPfNWl58UGOQ2rRI0RKvRtIyuy-8PaJAilWgY5YaMKb3iryM6Uv_tLcIT0keukO9Byvq4e9LEoGtT4tbN5hgcOIoi2AT2DufG3A3bDzBIRfsE4WwPpfh0VM4BLF/s1600/New+Search+Console+index+status+report+screenshot.png" width="640" /></a></div> <h3>The new AMP fixing flow</h3> The new AMP fixing experience starts with the AMP Issues report. This report shows the current AMP issues affecting your site, grouped by the underlying error. Drill down into an issue to get more details, including sample affected pages. After you fix the underlying issue, click a button to verify your fix, and have Google recrawl the pages affected by that issue. Google will notify you of the progress of the recrawl, and will update the report as your fixes are validated.<br /> <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhfj-6wb8_gLZpAPMk2lF5-3PmYdqlSU2VYpaTQI4z_jjyUsOLbbvQKloPFDm_Dx67ejYcLWnEOUpWiWps8V9NHOLN2afUjWODUDdk6yshyphenhyphenMvbBs50YpsWcQTj5g63HuPBjRTkL/s1600/New+Search+Console+AMP+error+report+screenshot.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="913" data-original-width="1007" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhfj-6wb8_gLZpAPMk2lF5-3PmYdqlSU2VYpaTQI4z_jjyUsOLbbvQKloPFDm_Dx67ejYcLWnEOUpWiWps8V9NHOLN2afUjWODUDdk6yshyphenhyphenMvbBs50YpsWcQTj5g63HuPBjRTkL/s1600/New+Search+Console+AMP+error+report+screenshot.png" width="640" /></a></div> As we start to experiment with these new features, some users will be introduced to the new redesign through the coming weeks.<br /> <span class="byline-author">Posted by John Mueller and the 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> <div dir="ltr" style="text-align: left;" trbidi="on"> Search Console was <a href="http://sitemaps.blogspot.ch/2005/11/more-stats.html">initially launched</a> with just four reports more than a decade ago. Today, the product includes more than two dozen reports and tools covering AMP, structured data, and live testing tools, all designed to help improve your site's performance on Google Search.<br /> Now we have decided to embark on an extensive redesign to better serve you, our users. Our hope is that this redesign will provide you with:<br /> <ul> <li><strong>More actionable insights</strong> - We will now group the identified issues by what we suspect is the common “root-cause” to help you find where you should fix your code. We organize these issues into tasks that have a state (similar to bug tracking systems) so you can easily see whether the issue is still open, whether Google has detected your fix, and track the progress of re-processing the affected pages. </li> <li><strong>Better support of your organizational workflow</strong> - As we talked to many organizations, we’ve learned that multiple people are typically involved in implementing, diagnosing, and fixing issues. This is why we are introducing sharing functionality that allows you to pick-up an action item and share it with other people in your group, like developers who will get references to the code in question.</li> <li><strong>Faster feedback loops between you and Google</strong> - We’ve built a mechanism to allow you to iterate quickly on your fixes, and not waste time waiting for Google to recrawl your site, only to tell you later that it’s not fixed yet. Rather, we’ll provide on-the-spot testing of fixes and are automatically speeding up crawling once we see things are ok. Similarly, the testing tools will include code snippets and a search preview - so you can quickly see where your issues are, confirm you've fixed them, and see how the pages will look on Search.</li> </ul> </div> In the next few weeks, we're releasing two exciting BETA features from the new Search Console to a small set of users — Index Coverage report and AMP fixing flow.<br /> <h3></h3> The new Index Coverage report shows the count of indexed pages, information about why some pages could not be indexed, along with example pages and tips on how to fix indexing issues. It also enables a simple sitemap submission flow, and the capability to filter all Index Coverage data to any of the submitted sitemaps.<br /> Here’s a peek of our new Index Coverage report:<br /> <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2fRZ-57fe2pPfNWl58UGOQ2rRI0RKvRtIyuy-8PaJAilWgY5YaMKb3iryM6Uv_tLcIT0keukO9Byvq4e9LEoGtT4tbN5hgcOIoi2AT2DufG3A3bDzBIRfsE4WwPpfh0VM4BLF/s1600/New+Search+Console+index+status+report+screenshot.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="913" data-original-width="1007" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2fRZ-57fe2pPfNWl58UGOQ2rRI0RKvRtIyuy-8PaJAilWgY5YaMKb3iryM6Uv_tLcIT0keukO9Byvq4e9LEoGtT4tbN5hgcOIoi2AT2DufG3A3bDzBIRfsE4WwPpfh0VM4BLF/s1600/New+Search+Console+index+status+report+screenshot.png" width="640" /></a></div> <h3>The new AMP fixing flow</h3> The new AMP fixing experience starts with the AMP Issues report. This report shows the current AMP issues affecting your site, grouped by the underlying error. Drill down into an issue to get more details, including sample affected pages. After you fix the underlying issue, click a button to verify your fix, and have Google recrawl the pages affected by that issue. Google will notify you of the progress of the recrawl, and will update the report as your fixes are validated.<br /> <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhfj-6wb8_gLZpAPMk2lF5-3PmYdqlSU2VYpaTQI4z_jjyUsOLbbvQKloPFDm_Dx67ejYcLWnEOUpWiWps8V9NHOLN2afUjWODUDdk6yshyphenhyphenMvbBs50YpsWcQTj5g63HuPBjRTkL/s1600/New+Search+Console+AMP+error+report+screenshot.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="913" data-original-width="1007" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhfj-6wb8_gLZpAPMk2lF5-3PmYdqlSU2VYpaTQI4z_jjyUsOLbbvQKloPFDm_Dx67ejYcLWnEOUpWiWps8V9NHOLN2afUjWODUDdk6yshyphenhyphenMvbBs50YpsWcQTj5g63HuPBjRTkL/s1600/New+Search+Console+AMP+error+report+screenshot.png" width="640" /></a></div> As we start to experiment with these new features, some users will be introduced to the new redesign through the coming weeks.<br /> <span class="byline-author">Posted by John Mueller and the 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:The new Search Console: a sneak peek at two experimental features&url=https://webmasters.googleblog.com/2017/08/a-sneak-peek-at-two-experimental.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/08/a-sneak-peek-at-two-experimental.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/08/a-sneak-peek-at-two-experimental.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/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/products%20and%20services?hl=en' rel='tag'> products and services </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en' 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?hl=en' 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?hl=en&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?hl=en'> <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?hl=en' rel='tag'> AMP </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en' rel='tag'> webmaster community </a> </span> </div> </div> </div> <div class='post' data-id='2855633787587942915' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2016/03/an-update-on-webmaster-central-blog.html?hl=en' itemprop='url' title='An update on the Webmaster Central Blog'> An update on the Webmaster Central Blog </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, March 08, 2016 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div style="text-align: left;" trbidi="on"> <div><b>We’ve got a new URL!</b></div> <br /><div> You may have noticed the Google Webmaster Central blog has a new address: <a href="https://webmasters.googleblog.com/">webmasters.googleblog.com</a>. </div> <br /><div> That’s because starting today, Google is moving its blogs to a new domain to help people recognize when they’re reading an official blog from Google. These changes will roll out to all of Google’s blogs over time. </div> <br /><div> The previous address will redirect to the new domain, so your bookmarks and links will continue to work. Unfortunately, as with a custom domain change in Blogger, the <a href="https://support.google.com/blogger/answer/1752748">Google+ comments on the blogs have been reset</a>. </div> <br />Thanks as always for reading—we’ll see you here again soon at <a href="https://webmasters.googleblog.com/">webmasters.googleblog.com</a>!<br /> <img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh0a_hHmjoCYScf7Ryuuferr3yNKFjAnxSEdrCe6g-raeXDvwlHFYiRqZj89044SAha6mMso59qJlRsHLBJtCRFltPqX9gtQ0Hb5GT_o4JpqfROxWZqQQnX19188s_XiDp1bj10/s600/wemoved.png" /> <br /> <span class="byline-author">Posted by <a href="https://plus.google.com/+johnmueller?rel=cousin">John Mueller</a>, Webmaster Trends Analyst, Zürich</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 style="text-align: left;" trbidi="on"> <div><b>We’ve got a new URL!</b></div> <br /><div> You may have noticed the Google Webmaster Central blog has a new address: <a href="https://webmasters.googleblog.com/">webmasters.googleblog.com</a>. </div> <br /><div> That’s because starting today, Google is moving its blogs to a new domain to help people recognize when they’re reading an official blog from Google. These changes will roll out to all of Google’s blogs over time. </div> <br /><div> The previous address will redirect to the new domain, so your bookmarks and links will continue to work. Unfortunately, as with a custom domain change in Blogger, the <a href="https://support.google.com/blogger/answer/1752748">Google+ comments on the blogs have been reset</a>. </div> <br />Thanks as always for reading—we’ll see you here again soon at <a href="https://webmasters.googleblog.com/">webmasters.googleblog.com</a>!<br /> <img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh0a_hHmjoCYScf7Ryuuferr3yNKFjAnxSEdrCe6g-raeXDvwlHFYiRqZj89044SAha6mMso59qJlRsHLBJtCRFltPqX9gtQ0Hb5GT_o4JpqfROxWZqQQnX19188s_XiDp1bj10/s600/wemoved.png" /> <br /> <span class="byline-author">Posted by <a href="https://plus.google.com/+johnmueller?rel=cousin">John Mueller</a>, Webmaster Trends Analyst, Zürich</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 the Webmaster Central Blog&url=https://webmasters.googleblog.com/2016/03/an-update-on-webmaster-central-blog.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2016/03/an-update-on-webmaster-central-blog.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2016/03/an-update-on-webmaster-central-blog.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/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en' rel='tag'> webmaster community </a> </span> </div> </div> </div> <div class='post' data-id='3284461621186009989' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2015/11/tc-summit-2015-celebrating-our.html?hl=en' itemprop='url' title='TC Summit 2015: Celebrating our Webmaster Top Contributors!'> TC Summit 2015: Celebrating our Webmaster Top Contributors! </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Monday, November 09, 2015 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>Two weeks ago, we were extremely lucky to host the 2015 edition of the Top Contributor Summit (<a href="https://twitter.com/search?q=%23tcsummit&src=typd">#TCsummit</a>), in San Francisco and on Google’s campus in Mountain View, California.</p> <p><a href="https://topcontributor.withgoogle.com/">Google Top Contributors</a> are an exceptional group of passionate Google product enthusiasts who share their expertise across our international help forums to support millions of Google users every year. Google’s Top Contributor Summit is an event organised every two years, to celebrate these amazing users. This year we had the pleasure to welcome 526 Top Contributors, from all around the world. </p> <p>Under the motto “Learn, Connect, Celebrate”, Top Contributors had the chance to learn more about our products, get insights on the future of Google, connect with Googlers and Top Contributors from various products and, finally, to celebrate their positive impact on our products and users.</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/Z8GpC8QoxCo" frameborder="0" allowfullscreen></iframe> <p><i>Footage of the 2015 Top Contributor Summit</i></p> <p>We also had the chance to hold Webmaster-specific sessions, which gave Googlers the unique opportunity to meet <a href="https://topcontributor.withgoogle.com/profiles">56 of our Webmaster Top Contributors</a>, representing 20 countries and speaking 14 different languages.</p> <p> <img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEilDQgDPb7EoO2hES-ya65W0W_cjyOF1BXwA6HmM5My2qvkn-yRzZShv0bSGUA2bmGgNVUxJcZhoJ7RQu4ztYif0X0WuGah0H-2iJkZXNknNoAX07C30nRXzQ5CeJPZHsaf9yLB/s500/tcsummit2.jpg" /> <br> <i>Group photo of the Webmaster Top Contributor community and the Google Webmaster Relations team</i></p> <p>Throughout the day, we had in-depth sessions about Google Webmaster guidelines, Search Console and Google Search. We discussed the most common issues that users are bringing up in our international webmaster forums, and listened to the Top Contributors’ feedback regarding our Search tools. We also talked about the Top Contributor program itself and additional opportunities for our users to benefit from both Google and the TCs’ support. Product managers, engineers and search quality Googlers attended the sessions to listen and bring the feedback given by Top Contributors and users on the forum back to their teams. </p> <p> <img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjB7C-DbGnRsDX40g-UZtFlDiCSVft6sm6lSPDCWq4OWBtlXOrwfPq-EYCvUH5eLvWL6N4eSmF2JyC3aKJ5TSMJMKgCAnvZizNRmSbKFDfMD6SeJd7P4rCnWtogvxXCC9ybjri0/s500/tcsummit1.jpg" /> <br> <i>Webmaster Top Contributors during the in-depth sessions about Google Webmaster guidelines, Search Console and Google Search</i></p> <p>At Google, we are grateful to have the incredible opportunity to meet and connect with some of the most insightful members of the webmaster community and get their feedback on such important topics. It helps us be sure that Google keeps focusing on what really matters to webmasters, content creators, and users.</p> <p>To learn more about our Top Contributor Program, or to give us your own feedback, visit our <a href="https://topcontributor.withgoogle.com/">Top Contributor homepage</a> or join our <a href="https://productforums.google.com/forum/#!forum/webmasters">Webmaster help forum</a>.</p> <br> <span class="byline-author">Diogo Botelho and Roberta Remigi, Webmaster Relations 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"> <p>Two weeks ago, we were extremely lucky to host the 2015 edition of the Top Contributor Summit (<a href="https://twitter.com/search?q=%23tcsummit&src=typd">#TCsummit</a>), in San Francisco and on Google’s campus in Mountain View, California.</p> <p><a href="https://topcontributor.withgoogle.com/">Google Top Contributors</a> are an exceptional group of passionate Google product enthusiasts who share their expertise across our international help forums to support millions of Google users every year. Google’s Top Contributor Summit is an event organised every two years, to celebrate these amazing users. This year we had the pleasure to welcome 526 Top Contributors, from all around the world. </p> <p>Under the motto “Learn, Connect, Celebrate”, Top Contributors had the chance to learn more about our products, get insights on the future of Google, connect with Googlers and Top Contributors from various products and, finally, to celebrate their positive impact on our products and users.</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/Z8GpC8QoxCo" frameborder="0" allowfullscreen></iframe> <p><i>Footage of the 2015 Top Contributor Summit</i></p> <p>We also had the chance to hold Webmaster-specific sessions, which gave Googlers the unique opportunity to meet <a href="https://topcontributor.withgoogle.com/profiles">56 of our Webmaster Top Contributors</a>, representing 20 countries and speaking 14 different languages.</p> <p> <img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEilDQgDPb7EoO2hES-ya65W0W_cjyOF1BXwA6HmM5My2qvkn-yRzZShv0bSGUA2bmGgNVUxJcZhoJ7RQu4ztYif0X0WuGah0H-2iJkZXNknNoAX07C30nRXzQ5CeJPZHsaf9yLB/s500/tcsummit2.jpg" /> <br> <i>Group photo of the Webmaster Top Contributor community and the Google Webmaster Relations team</i></p> <p>Throughout the day, we had in-depth sessions about Google Webmaster guidelines, Search Console and Google Search. We discussed the most common issues that users are bringing up in our international webmaster forums, and listened to the Top Contributors’ feedback regarding our Search tools. We also talked about the Top Contributor program itself and additional opportunities for our users to benefit from both Google and the TCs’ support. Product managers, engineers and search quality Googlers attended the sessions to listen and bring the feedback given by Top Contributors and users on the forum back to their teams. </p> <p> <img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjB7C-DbGnRsDX40g-UZtFlDiCSVft6sm6lSPDCWq4OWBtlXOrwfPq-EYCvUH5eLvWL6N4eSmF2JyC3aKJ5TSMJMKgCAnvZizNRmSbKFDfMD6SeJd7P4rCnWtogvxXCC9ybjri0/s500/tcsummit1.jpg" /> <br> <i>Webmaster Top Contributors during the in-depth sessions about Google Webmaster guidelines, Search Console and Google Search</i></p> <p>At Google, we are grateful to have the incredible opportunity to meet and connect with some of the most insightful members of the webmaster community and get their feedback on such important topics. It helps us be sure that Google keeps focusing on what really matters to webmasters, content creators, and users.</p> <p>To learn more about our Top Contributor Program, or to give us your own feedback, visit our <a href="https://topcontributor.withgoogle.com/">Top Contributor homepage</a> or join our <a href="https://productforums.google.com/forum/#!forum/webmasters">Webmaster help forum</a>.</p> <br> <span class="byline-author">Diogo Botelho and Roberta Remigi, Webmaster Relations 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:TC Summit 2015: Celebrating our Webmaster Top Contributors!&url=https://webmasters.googleblog.com/2015/11/tc-summit-2015-celebrating-our.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2015/11/tc-summit-2015-celebrating-our.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2015/11/tc-summit-2015-celebrating-our.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/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en' rel='tag'> webmaster community </a> </span> </div> </div> </div> <div class='post' data-id='4889956120899854939' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2014/12/the-four-steps-to-appiness.html?hl=en' itemprop='url' title='The four steps to appiness '> The four steps to appiness </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, December 09, 2014 </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>Webmaster Level: intermediate to advanced</p> <p><a href="https://developers.google.com/app-indexing/?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">App deep links</a> are the new kid on the block in organic search, and they’re picking up speed faster than you can say “schema.org ViewAction”! For signed-in users, 15% of Google searches on Android now return deep links to apps through App Indexing. And over just the past quarter, we've seen the number of clicks on app deep links jump by 10x.</p> <p>We’ve gotten a lot of feedback from developers and seen a lot of implementations gone right and others that were good learning experiences since we <a href="http://googlewebmastercentral.blogspot.ch/2014/06/android-app-indexing-is-now-open-for.html?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">opened up App Indexing back in June</a>. We’d like to share with you four key steps to monitor app performance and drive user engagement:</p> <h3>1. Give your app developer access to Webmaster Tools</h3> <p>App indexing is a team effort between you (as a webmaster) and your app development team. We show information in Webmaster Tools that is key for your app developers to do their job well. Here’s what’s available right now: <ul> <li>Errors in indexed pages within apps</li> <li>Weekly clicks and impressions from app deep link via Google search</li> <li>Stats on your sitemap (if that’s how you implemented the app deep links)</li> </ul> ...and we plan to add a lot more in the coming months!</p> <p>We’ve noticed that very few developers have access to Webmaster Tools. So if you want your app development team to get all of the information they need to fix app-related issues, it’s essential for them to have access to Webmaster Tools.</p> <p>Any verified site owner can <a href="https://www.google.com/webmasters/tools/user-admin?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">add a new user</a>. Pick restricted or full permissions, depending on the <a href="https://support.google.com/webmasters/answer/2451999?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">level of access</a> you’d like to give:</p> <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjteTh3Tn9xTh5tL0DE5KUqhGavjWV1Ot8j9jJHlAMnukd_AVySXlOLZtJV8UbkDdsyDH-B56r-GsBpBLlwgD_PGC1ujmqbwLFhlnVhKFlM_q55LJ1S8OxTpLQR6nssMhahSkB6/s1600/webmaster+tools+add+user.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjteTh3Tn9xTh5tL0DE5KUqhGavjWV1Ot8j9jJHlAMnukd_AVySXlOLZtJV8UbkDdsyDH-B56r-GsBpBLlwgD_PGC1ujmqbwLFhlnVhKFlM_q55LJ1S8OxTpLQR6nssMhahSkB6/s550/webmaster+tools+add+user.png" /></a></div> <h3>2. Understand how your app is doing in search results</h3> <p>How are users engaging with your app from search results? We’ve introduced two new ways for you to track performance for your app deep links: <ul> <li>We now send a weekly clicks and impressions update to the <a href="https://support.google.com/webmasters/answer/140528?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">Message center</a> in your Webmaster Tools account.</li> <li>You can now track how much traffic app deep links drive to your app using referrer information - specifically, the referrer extra in the <span style="font-family:courier">ACTION_VIEW</span> intent. We're working to integrate this information with Google Analytics for even easier access. Learn <a href="https://developers.google.com/app-indexing/webmasters/referrer?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">how to track referrer information</a> on our Developer site.</li> </ul></p> <h3>3. Make sure key app resources can be crawled</h3> <p>Blocked resources are one of the top reasons for the “content mismatch” errors you see in Webmaster Tools’ <a href="https://www.google.com/webmasters/tools/crawl-errors?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">Crawl Errors report</a>. We need access to all the resources necessary to render your app page. This allows us to assess whether your associated web page has the same content as your app page.</p> <p>To help you find and fix these issues, we now show you the specific resources we can’t access that are critical for rendering your app page. If you see a content mismatch error for your app, look out for the list of blocked resources in “Step 5” of the details dialog:</p> <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh8Z29aZG8jAt8K1C6BBitgZ_HWr0F8WtxA0qVYNKI38TBv8VsYjn9AC4g3SW3Dl-4o_Pt_m55FAC7a1JPX1giOnjv2nG2Ru94403q0Iod5odmHtf7R5ojm55gsmGB16soQtrPU/s1600/apps+roboted+content.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh8Z29aZG8jAt8K1C6BBitgZ_HWr0F8WtxA0qVYNKI38TBv8VsYjn9AC4g3SW3Dl-4o_Pt_m55FAC7a1JPX1giOnjv2nG2Ru94403q0Iod5odmHtf7R5ojm55gsmGB16soQtrPU/s640/apps+roboted+content.png" /></a></div> <h3>4. Watch out for Android App errors</h3> <p>To help you identify errors when indexing your app, we’ll send you messages for all app errors we detect, and will also display most of them in the “Android apps” tab of the <a href="https://www.google.com/webmasters/tools/crawl-errors?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">Crawl errors report</a>.</p> <p>In addition to the currently available “Content mismatch” and “Intent URI not supported” error alerts, we’re introducing three new error types: <ul> <li><strong>APK not found</strong>: we can’t find the package corresponding to the app.</li> <li><strong>No <a href="http://googlewebmastercentral.blogspot.com/2008/10/first-click-free-for-web-search.html?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">first-click free</a></strong>: the link to your app does not lead directly to the content, but requires login to access.</li> <li><strong>Back button violation</strong>: after following the link to your app, the back button did not return to search results.</li> </ul></p> <p>In our experience, the majority of errors are usually caused by a general setting in your app (e.g. a blocked resource, or a region picker that pops up when the user tries to open the app from search). Taking care of that generally resolves it for all involved URIs.</p> <p>Good luck in the pursuit of appiness! As always, if you have questions, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">Webmaster help forum</a>.</p> <span class="byline-author">Posted by <a href="//google.com/+MariyaMoeva?rel=app-indexing-enthusiast">Mariya Moeva</a>, Webmaster Trends Analyst</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>Webmaster Level: intermediate to advanced</p> <p><a href="https://developers.google.com/app-indexing/?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">App deep links</a> are the new kid on the block in organic search, and they’re picking up speed faster than you can say “schema.org ViewAction”! For signed-in users, 15% of Google searches on Android now return deep links to apps through App Indexing. And over just the past quarter, we've seen the number of clicks on app deep links jump by 10x.</p> <p>We’ve gotten a lot of feedback from developers and seen a lot of implementations gone right and others that were good learning experiences since we <a href="http://googlewebmastercentral.blogspot.ch/2014/06/android-app-indexing-is-now-open-for.html?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">opened up App Indexing back in June</a>. We’d like to share with you four key steps to monitor app performance and drive user engagement:</p> <h3>1. Give your app developer access to Webmaster Tools</h3> <p>App indexing is a team effort between you (as a webmaster) and your app development team. We show information in Webmaster Tools that is key for your app developers to do their job well. Here’s what’s available right now: <ul> <li>Errors in indexed pages within apps</li> <li>Weekly clicks and impressions from app deep link via Google search</li> <li>Stats on your sitemap (if that’s how you implemented the app deep links)</li> </ul> ...and we plan to add a lot more in the coming months!</p> <p>We’ve noticed that very few developers have access to Webmaster Tools. So if you want your app development team to get all of the information they need to fix app-related issues, it’s essential for them to have access to Webmaster Tools.</p> <p>Any verified site owner can <a href="https://www.google.com/webmasters/tools/user-admin?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">add a new user</a>. Pick restricted or full permissions, depending on the <a href="https://support.google.com/webmasters/answer/2451999?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">level of access</a> you’d like to give:</p> <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjteTh3Tn9xTh5tL0DE5KUqhGavjWV1Ot8j9jJHlAMnukd_AVySXlOLZtJV8UbkDdsyDH-B56r-GsBpBLlwgD_PGC1ujmqbwLFhlnVhKFlM_q55LJ1S8OxTpLQR6nssMhahSkB6/s1600/webmaster+tools+add+user.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjteTh3Tn9xTh5tL0DE5KUqhGavjWV1Ot8j9jJHlAMnukd_AVySXlOLZtJV8UbkDdsyDH-B56r-GsBpBLlwgD_PGC1ujmqbwLFhlnVhKFlM_q55LJ1S8OxTpLQR6nssMhahSkB6/s550/webmaster+tools+add+user.png" /></a></div> <h3>2. Understand how your app is doing in search results</h3> <p>How are users engaging with your app from search results? We’ve introduced two new ways for you to track performance for your app deep links: <ul> <li>We now send a weekly clicks and impressions update to the <a href="https://support.google.com/webmasters/answer/140528?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">Message center</a> in your Webmaster Tools account.</li> <li>You can now track how much traffic app deep links drive to your app using referrer information - specifically, the referrer extra in the <span style="font-family:courier">ACTION_VIEW</span> intent. We're working to integrate this information with Google Analytics for even easier access. Learn <a href="https://developers.google.com/app-indexing/webmasters/referrer?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">how to track referrer information</a> on our Developer site.</li> </ul></p> <h3>3. Make sure key app resources can be crawled</h3> <p>Blocked resources are one of the top reasons for the “content mismatch” errors you see in Webmaster Tools’ <a href="https://www.google.com/webmasters/tools/crawl-errors?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">Crawl Errors report</a>. We need access to all the resources necessary to render your app page. This allows us to assess whether your associated web page has the same content as your app page.</p> <p>To help you find and fix these issues, we now show you the specific resources we can’t access that are critical for rendering your app page. If you see a content mismatch error for your app, look out for the list of blocked resources in “Step 5” of the details dialog:</p> <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh8Z29aZG8jAt8K1C6BBitgZ_HWr0F8WtxA0qVYNKI38TBv8VsYjn9AC4g3SW3Dl-4o_Pt_m55FAC7a1JPX1giOnjv2nG2Ru94403q0Iod5odmHtf7R5ojm55gsmGB16soQtrPU/s1600/apps+roboted+content.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh8Z29aZG8jAt8K1C6BBitgZ_HWr0F8WtxA0qVYNKI38TBv8VsYjn9AC4g3SW3Dl-4o_Pt_m55FAC7a1JPX1giOnjv2nG2Ru94403q0Iod5odmHtf7R5ojm55gsmGB16soQtrPU/s640/apps+roboted+content.png" /></a></div> <h3>4. Watch out for Android App errors</h3> <p>To help you identify errors when indexing your app, we’ll send you messages for all app errors we detect, and will also display most of them in the “Android apps” tab of the <a href="https://www.google.com/webmasters/tools/crawl-errors?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">Crawl errors report</a>.</p> <p>In addition to the currently available “Content mismatch” and “Intent URI not supported” error alerts, we’re introducing three new error types: <ul> <li><strong>APK not found</strong>: we can’t find the package corresponding to the app.</li> <li><strong>No <a href="http://googlewebmastercentral.blogspot.com/2008/10/first-click-free-for-web-search.html?utm_source=wmc-blog&utm_medium=direct&utm_campaign=appiness-2014-12-09">first-click free</a></strong>: the link to your app does not lead directly to the content, but requires login to access.</li> <li><strong>Back button violation</strong>: after following the link to your app, the back button did not return to search results.</li> </ul></p> <p>In our experience, the majority of errors are usually caused by a general setting in your app (e.g. a blocked resource, or a region picker that pops up when the user tries to open the app from search). Taking care of that generally resolves it for all involved URIs.</p> <p>Good luck in the pursuit of appiness! As always, if you have questions, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">Webmaster help forum</a>.</p> <span class="byline-author">Posted by <a href="//google.com/+MariyaMoeva?rel=app-indexing-enthusiast">Mariya Moeva</a>, Webmaster Trends Analyst</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:The four steps to appiness &url=https://webmasters.googleblog.com/2014/12/the-four-steps-to-appiness.html?hl=en&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/2014/12/the-four-steps-to-appiness.html?hl=en'> <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/2014/12/the-four-steps-to-appiness.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/advanced?hl=en' rel='tag'> advanced </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/apps?hl=en' rel='tag'> apps </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/intermediate?hl=en' rel='tag'> intermediate </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/verification?hl=en' rel='tag'> verification </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='456206210326483590' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2013/03/new-first-stop-for-hacked-site-recovery.html?hl=en' itemprop='url' title='New first stop for hacked site recovery'> New first stop for hacked site recovery </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, March 12, 2013 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> Webmaster Level: All<br><br> We certainly hope you never have to use our new Help for hacked sites informational series. It's a dozen articles and over an hour of videos dedicated to helping webmasters in the unfortunate event that their site is compromised.<br><br> <div style="text-align:center"><iframe width="500" height="281" src="//www.youtube.com/embed/ubklMNgC6x8" frameborder="0" allowfullscreen></iframe><br><em>Overview: How and why sites are hacked</em></div> <br> If you have further interest in why cybercriminals hack sites for spammy purposes, see Tiffany Oberoi’s explanation in <a href="http://support.google.com/webmasters/bin/answer.py?&answer=2600721">Step 5: Assess the damage (hacked with spam)</a>.<br> <div style="text-align:center"><iframe width="500" height="281" src="//www.youtube.com/embed/ckeUfbndHRU" frameborder="0" allowfullscreen></iframe><br><em>Tiffany Oberoi, a Webspam engineer, shares more information about sites hacked with spam</em></div> <br> And if you’re curious about malware, Lucas Ballard from our Safe Browsing team, explains more about the topic in <a href="http://support.google.com/webmasters/bin/answer.py?hl=en&answer=3024274">Step 5: Assess the damage (hacked with malware)</a>. <br> <div style="text-align:center"><iframe width="500" height="281" src="//www.youtube.com/embed/Mh5blIx4vvc" frameborder="0" allowfullscreen></iframe><br><em>Lucas Ballard, a Safe Browsing engineer, and I pretend to have a totally natural conversation about malware</em></div><br> While we attempt to outline the necessary steps in recovery, each task remains fairly difficult for site owners unless they have advanced knowledge of system administrator commands and experience with source code. For helping fellow webmasters through the difficult recovery time, we'd like to thank the <a href="https://sites.google.com/site/webmasterhelpforum/en/bionic-posters">steady members in Webmaster Forum</a>. Specifically, in the subforum <a href="http://productforums.google.com/forum/#!categories/webmasters/malware--hacked-sites">Malware and hacked sites</a>, we'd be remiss not to mention the amazing contributions of <a href="http://aw-snap.info/">Redleg</a> and <a href="http://blog.unmaskparasites.com/">Denis Sinegubko</a>. <br><br> <strong>How to avoid ever needing <em>Help for hacked sites</em></strong><br> Just as you focus on making a site that's good for users and search-engine friendly, keeping your site secure -- for you and your visitors -- is also paramount. When site owners fail to keep their site secure, hackers may exploit the vulnerability. If a hacker exploits a vulnerability, then you might need <em>Help for hacked sites</em>. So, to potentially avoid this scenario:<ul><li>Be vigilant about keeping software updated</li><li>Understand the security practices of all applications, plugins, third-party software, etc., before you install them on your server. A security vulnerability in one software application can affect the safety of your entire site</li><li>Remove unnecessary or unused software</li><li>Enforce creation of strong passwords</li><li>Keep all devices used to log in to your servers secure (updated operating system and browser)</li><li>Make regular, automated backups of your site</li></ul> Help for hacked sites can be found at <a href="//www.google.com/webmasters/hacked">www.google.com/webmasters/hacked</a>. We look forward to not seeing you there! <br><br> <span class="byline-author">Written by <a href="https://plus.google.com/u/0/111983349552187459374?rel=author">Maile Ohye</a>, Developer Programs Tech Lead</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> Webmaster Level: All<br><br> We certainly hope you never have to use our new Help for hacked sites informational series. It's a dozen articles and over an hour of videos dedicated to helping webmasters in the unfortunate event that their site is compromised.<br><br> <div style="text-align:center"><iframe width="500" height="281" src="//www.youtube.com/embed/ubklMNgC6x8" frameborder="0" allowfullscreen></iframe><br><em>Overview: How and why sites are hacked</em></div> <br> If you have further interest in why cybercriminals hack sites for spammy purposes, see Tiffany Oberoi’s explanation in <a href="http://support.google.com/webmasters/bin/answer.py?&answer=2600721">Step 5: Assess the damage (hacked with spam)</a>.<br> <div style="text-align:center"><iframe width="500" height="281" src="//www.youtube.com/embed/ckeUfbndHRU" frameborder="0" allowfullscreen></iframe><br><em>Tiffany Oberoi, a Webspam engineer, shares more information about sites hacked with spam</em></div> <br> And if you’re curious about malware, Lucas Ballard from our Safe Browsing team, explains more about the topic in <a href="http://support.google.com/webmasters/bin/answer.py?hl=en&answer=3024274">Step 5: Assess the damage (hacked with malware)</a>. <br> <div style="text-align:center"><iframe width="500" height="281" src="//www.youtube.com/embed/Mh5blIx4vvc" frameborder="0" allowfullscreen></iframe><br><em>Lucas Ballard, a Safe Browsing engineer, and I pretend to have a totally natural conversation about malware</em></div><br> While we attempt to outline the necessary steps in recovery, each task remains fairly difficult for site owners unless they have advanced knowledge of system administrator commands and experience with source code. For helping fellow webmasters through the difficult recovery time, we'd like to thank the <a href="https://sites.google.com/site/webmasterhelpforum/en/bionic-posters">steady members in Webmaster Forum</a>. Specifically, in the subforum <a href="http://productforums.google.com/forum/#!categories/webmasters/malware--hacked-sites">Malware and hacked sites</a>, we'd be remiss not to mention the amazing contributions of <a href="http://aw-snap.info/">Redleg</a> and <a href="http://blog.unmaskparasites.com/">Denis Sinegubko</a>. <br><br> <strong>How to avoid ever needing <em>Help for hacked sites</em></strong><br> Just as you focus on making a site that's good for users and search-engine friendly, keeping your site secure -- for you and your visitors -- is also paramount. When site owners fail to keep their site secure, hackers may exploit the vulnerability. If a hacker exploits a vulnerability, then you might need <em>Help for hacked sites</em>. So, to potentially avoid this scenario:<ul><li>Be vigilant about keeping software updated</li><li>Understand the security practices of all applications, plugins, third-party software, etc., before you install them on your server. A security vulnerability in one software application can affect the safety of your entire site</li><li>Remove unnecessary or unused software</li><li>Enforce creation of strong passwords</li><li>Keep all devices used to log in to your servers secure (updated operating system and browser)</li><li>Make regular, automated backups of your site</li></ul> Help for hacked sites can be found at <a href="//www.google.com/webmasters/hacked">www.google.com/webmasters/hacked</a>. We look forward to not seeing you there! <br><br> <span class="byline-author">Written by <a href="https://plus.google.com/u/0/111983349552187459374?rel=author">Maile Ohye</a>, Developer Programs Tech Lead</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:New first stop for hacked site recovery&url=https://webmasters.googleblog.com/2013/03/new-first-stop-for-hacked-site-recovery.html?hl=en&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/2013/03/new-first-stop-for-hacked-site-recovery.html?hl=en'> <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/2013/03/new-first-stop-for-hacked-site-recovery.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/advanced?hl=en' rel='tag'> advanced </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/beginner?hl=en' rel='tag'> beginner </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/intermediate?hl=en' rel='tag'> intermediate </a> </span> </div> </div> </div> <div class='post' data-id='5102776702555313635' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2012/07/new-crawl-error-alerts-from-webmaster.html?hl=en' itemprop='url' title='New Crawl Error alerts from Webmaster Tools'> New Crawl Error alerts from Webmaster Tools </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, July 12, 2012 </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"> Webmaster level: All <br /> <br /> Today we’re rolling out Crawl Error alerts to help keep you informed of the state of your site.<br /> <br /> Since Googlebot regularly visits your site, we know when your site exhibits connectivity issues or suddenly spikes in pages returning HTTP error response codes (e.g. 404 File Not Found, 403 Forbidden, 503 Service Unavailable, etc). If your site is timing out or is exhibiting systemic errors when accessed by Googlebot, other visitors to your site might be having the same problem! <br /> <br /> When we see such errors, we may send alerts –- in the form of messages in the Webmaster Tools <a href="https://www.google.com/webmasters/tools/message-list">Message Center</a> –- to let you know what we’ve detected. Hopefully, given this increased communication, you can fix potential issues that may otherwise impact your site’s visitors or your site’s presence in search. <br /> <br /> As we discussed in our <a href="http://googlewebmastercentral.blogspot.com/2012/03/crawl-errors-next-generation.html">blog post</a> announcing the new Webmaster Tools <a href="http://support.google.com/webmasters/bin/answer.py?answer=35120">Crawl Errors</a> feature, we divide crawl errors into two types: Site Errors and URL Errors. <br /> <br /> <h3> Site Error alerts for major site-wide problems</h3> Site Errors represent an inability to connect to your site, and represent systemic issues rather than problems with specific pages. Here are some issues that might cause Site Errors:<br /> <ul> <li>Your DNS server is down or misconfigured. </li> <li>Your web server itself is firewalled off.</li> <li>Your web server is refusing connections from Googlebot.</li> <li>Your web server is overloaded, or down.</li> <li>Your site’s robots.txt is inaccessible.</li> </ul> These errors are global to a site, and in theory should never occur for a well-operating site (and don’t occur for the large majority of the sites we crawl). If Googlebot detects any appreciable number of these Site Errors, regardless of the size of your site, we’ll try to notify you in the form of a message in the <a href="https://www.google.com/webmasters/tools/message-list">Message Center</a>: <br /> <br /> <table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody> <tr><td style="text-align: center;"><a href="//2.bp.blogspot.com/-rvrrBJhlQ2o/T_8wIp5tTLI/AAAAAAAAAXs/ul40pTOzB-c/s1600/Site+Error.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="381" src="//2.bp.blogspot.com/-rvrrBJhlQ2o/T_8wIp5tTLI/AAAAAAAAAXs/ul40pTOzB-c/s400/Site+Error.png" width="400"></a></td></tr> <tr><td class="tr-caption" style="text-align: center;">Example of a Site Error alert</td></tr> </tbody></table> The alert provides the number of errors Googlebot encountered crawling your site, the overall crawl error connection rate for your site, a link to the appropriate section of Webmaster Tools to examine the data more closely, and suggestions as to how to fix the problem. <br /> <br /> If your site shows a 100% error rate in one of these categories, it likely means that your site is either down or misconfigured in some way. If your site has an error rate less than 100% in any of these categories, it could just indicate a transient condition, but it could also mean that your site is overloaded or improperly configured. You may want to investigate these issues further, or ask about them on our <a href="https://groups.google.com/a/googleproductforums.com/forum/#!forum/webmasters">forum</a>. <br /> <br /> We may alert you even if the overall error rate is very low — in our experience a well configured site shouldn’t have any errors in these categories. <br /> <br /> <h3> URL Error anomaly alerts for potentially less critical issues</h3> Whereas any appreciable number of Site Errors could indicate that your site is misconfigured, overloaded, or simply out of service, URL Errors (pages that return a non-200 HTTP code, or incorrectly return an HTTP 200 code in the case of soft 404 errors) may occur on any well-configured site. Because different sites have different numbers of pages and different numbers of external links, a count of errors that indicates a serious problem for a small site might be entirely normal for a large site. <br /> <br /> That’s why for URL Errors we only send alerts when we detect a large spike in the number of errors for any of the five categories of errors (Server error, Soft 404, Access denied, Not found or Not followed). For example, if your site routinely has 100 pages with 404 errors, we won’t alert you if that number fluctuates minimally. However we might notify you when that count reaches a much higher number, say 500 or 1,000. Keep in mind that seeing 404 errors is not always bad, and can be a natural part of a healthy website (see our previous blog post: <a href="http://googlewebmastercentral.blogspot.com/2011/05/do-404s-hurt-my-site.html">Do 404s hurt my site?</a>). <br /> <br /> A large spike in error count could be because something has changed on your site — perhaps a reconfiguration has changed the permissions for a section of your site, or a new version of a script is crashing regularly, or someone accidentally moved or deleted an entire directory, or a reorganization of your site causes external links to no longer work. It could also just be a transient spike, or could be because of external causes (someone has linked to non-existent pages), so there might not even be a problem; but when we see an unusually large number of errors for your site, we’ll let you know so you can investigate: <br /> <br /> <table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody> <tr><td style="text-align: center;"><a href="//1.bp.blogspot.com/-g4TLRxo37Wg/T_8wJDpiAyI/AAAAAAAAAX0/VSvQo48jiiQ/s1600/URL+Error.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="233" src="//1.bp.blogspot.com/-g4TLRxo37Wg/T_8wJDpiAyI/AAAAAAAAAX0/VSvQo48jiiQ/s400/URL+Error.png" width="400"></a></td></tr> <tr><td class="tr-caption" style="text-align: center;">Example of a URL Error anomaly alert</td></tr> </tbody></table> The alert describes the category of web errors for which we’ve detected a spike, gives a link to the appropriate section of Webmaster Tools so that you can see what pages we think are problematic, and offers troubleshooting suggestions. <br /> <br /> <h3> Enable Message forwarding to send alerts to your inbox</h3> We know you’re busy, and that routinely checking <a href="https://www.google.com/webmasters/tools/home">Webmaster Tools</a> just to check for new alerts might be something you forget to do. Consider turning on <a href="https://www.google.com/webmasters/tools/preferences">Message forwarding</a>. We’ll send any Webmaster Tools messages to the email address of your choice. <br /> <br /> Let us know what you think, and if you have any comments or suggestions on our new alerts please visit our <a href="https://groups.google.com/a/googleproductforums.com/forum/#!forum/webmasters">forum</a>. <br /> <br /> <span class="byline-author">Written by <a href="https://plus.google.com/118261217130448099259/about">Brian Malcolm</a>, Webmaster Tools 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"> Webmaster level: All <br /> <br /> Today we’re rolling out Crawl Error alerts to help keep you informed of the state of your site.<br /> <br /> Since Googlebot regularly visits your site, we know when your site exhibits connectivity issues or suddenly spikes in pages returning HTTP error response codes (e.g. 404 File Not Found, 403 Forbidden, 503 Service Unavailable, etc). If your site is timing out or is exhibiting systemic errors when accessed by Googlebot, other visitors to your site might be having the same problem! <br /> <br /> When we see such errors, we may send alerts –- in the form of messages in the Webmaster Tools <a href="https://www.google.com/webmasters/tools/message-list">Message Center</a> –- to let you know what we’ve detected. Hopefully, given this increased communication, you can fix potential issues that may otherwise impact your site’s visitors or your site’s presence in search. <br /> <br /> As we discussed in our <a href="http://googlewebmastercentral.blogspot.com/2012/03/crawl-errors-next-generation.html">blog post</a> announcing the new Webmaster Tools <a href="http://support.google.com/webmasters/bin/answer.py?answer=35120">Crawl Errors</a> feature, we divide crawl errors into two types: Site Errors and URL Errors. <br /> <br /> <h3> Site Error alerts for major site-wide problems</h3> Site Errors represent an inability to connect to your site, and represent systemic issues rather than problems with specific pages. Here are some issues that might cause Site Errors:<br /> <ul> <li>Your DNS server is down or misconfigured. </li> <li>Your web server itself is firewalled off.</li> <li>Your web server is refusing connections from Googlebot.</li> <li>Your web server is overloaded, or down.</li> <li>Your site’s robots.txt is inaccessible.</li> </ul> These errors are global to a site, and in theory should never occur for a well-operating site (and don’t occur for the large majority of the sites we crawl). If Googlebot detects any appreciable number of these Site Errors, regardless of the size of your site, we’ll try to notify you in the form of a message in the <a href="https://www.google.com/webmasters/tools/message-list">Message Center</a>: <br /> <br /> <table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody> <tr><td style="text-align: center;"><a href="//2.bp.blogspot.com/-rvrrBJhlQ2o/T_8wIp5tTLI/AAAAAAAAAXs/ul40pTOzB-c/s1600/Site+Error.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="381" src="//2.bp.blogspot.com/-rvrrBJhlQ2o/T_8wIp5tTLI/AAAAAAAAAXs/ul40pTOzB-c/s400/Site+Error.png" width="400"></a></td></tr> <tr><td class="tr-caption" style="text-align: center;">Example of a Site Error alert</td></tr> </tbody></table> The alert provides the number of errors Googlebot encountered crawling your site, the overall crawl error connection rate for your site, a link to the appropriate section of Webmaster Tools to examine the data more closely, and suggestions as to how to fix the problem. <br /> <br /> If your site shows a 100% error rate in one of these categories, it likely means that your site is either down or misconfigured in some way. If your site has an error rate less than 100% in any of these categories, it could just indicate a transient condition, but it could also mean that your site is overloaded or improperly configured. You may want to investigate these issues further, or ask about them on our <a href="https://groups.google.com/a/googleproductforums.com/forum/#!forum/webmasters">forum</a>. <br /> <br /> We may alert you even if the overall error rate is very low — in our experience a well configured site shouldn’t have any errors in these categories. <br /> <br /> <h3> URL Error anomaly alerts for potentially less critical issues</h3> Whereas any appreciable number of Site Errors could indicate that your site is misconfigured, overloaded, or simply out of service, URL Errors (pages that return a non-200 HTTP code, or incorrectly return an HTTP 200 code in the case of soft 404 errors) may occur on any well-configured site. Because different sites have different numbers of pages and different numbers of external links, a count of errors that indicates a serious problem for a small site might be entirely normal for a large site. <br /> <br /> That’s why for URL Errors we only send alerts when we detect a large spike in the number of errors for any of the five categories of errors (Server error, Soft 404, Access denied, Not found or Not followed). For example, if your site routinely has 100 pages with 404 errors, we won’t alert you if that number fluctuates minimally. However we might notify you when that count reaches a much higher number, say 500 or 1,000. Keep in mind that seeing 404 errors is not always bad, and can be a natural part of a healthy website (see our previous blog post: <a href="http://googlewebmastercentral.blogspot.com/2011/05/do-404s-hurt-my-site.html">Do 404s hurt my site?</a>). <br /> <br /> A large spike in error count could be because something has changed on your site — perhaps a reconfiguration has changed the permissions for a section of your site, or a new version of a script is crashing regularly, or someone accidentally moved or deleted an entire directory, or a reorganization of your site causes external links to no longer work. It could also just be a transient spike, or could be because of external causes (someone has linked to non-existent pages), so there might not even be a problem; but when we see an unusually large number of errors for your site, we’ll let you know so you can investigate: <br /> <br /> <table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody> <tr><td style="text-align: center;"><a href="//1.bp.blogspot.com/-g4TLRxo37Wg/T_8wJDpiAyI/AAAAAAAAAX0/VSvQo48jiiQ/s1600/URL+Error.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="233" src="//1.bp.blogspot.com/-g4TLRxo37Wg/T_8wJDpiAyI/AAAAAAAAAX0/VSvQo48jiiQ/s400/URL+Error.png" width="400"></a></td></tr> <tr><td class="tr-caption" style="text-align: center;">Example of a URL Error anomaly alert</td></tr> </tbody></table> The alert describes the category of web errors for which we’ve detected a spike, gives a link to the appropriate section of Webmaster Tools so that you can see what pages we think are problematic, and offers troubleshooting suggestions. <br /> <br /> <h3> Enable Message forwarding to send alerts to your inbox</h3> We know you’re busy, and that routinely checking <a href="https://www.google.com/webmasters/tools/home">Webmaster Tools</a> just to check for new alerts might be something you forget to do. Consider turning on <a href="https://www.google.com/webmasters/tools/preferences">Message forwarding</a>. We’ll send any Webmaster Tools messages to the email address of your choice. <br /> <br /> Let us know what you think, and if you have any comments or suggestions on our new alerts please visit our <a href="https://groups.google.com/a/googleproductforums.com/forum/#!forum/webmasters">forum</a>. <br /> <br /> <span class="byline-author">Written by <a href="https://plus.google.com/118261217130448099259/about">Brian Malcolm</a>, Webmaster Tools 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:New Crawl Error alerts from Webmaster Tools&url=https://webmasters.googleblog.com/2012/07/new-crawl-error-alerts-from-webmaster.html?hl=en&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/2012/07/new-crawl-error-alerts-from-webmaster.html?hl=en'> <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/2012/07/new-crawl-error-alerts-from-webmaster.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/advanced?hl=en' rel='tag'> advanced </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/beginner?hl=en' rel='tag'> beginner </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/intermediate?hl=en' rel='tag'> intermediate </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='7388399774115860771' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2011/10/webmaster-forums-top-contributors-rock.html?hl=en' itemprop='url' title='Webmaster forums' Top Contributors rock'> Webmaster forums' Top Contributors rock </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, October 05, 2011 </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"> Webmaster level: All<br /> The TC Summit was a blast! As we wrote in our <a href="http://googlewebmastercentral.blogspot.com/2011/09/recognizing-top-contributors-in-googles.html">announcement post</a>, we recently invited more than 250 Top Contributors from all over the world to California to thank them for being so awesome and to give them the opportunity to meet some of our forum guides, engineers and product managers in person.<br /> Our colleagues Adrianne and Brenna already published a <a href="http://googleblog.blogspot.com/2011/09/saying-thanksin-personto-our-google-top.html">recap post</a> on the Official Google Blog. As for us, the search folks at Google, there's not much left to say except that we enjoyed the event and meeting Top Contributors in real life, many of them for the first time. We got the feeling you guys had a great time, too. Let’s quote a few of the folks who make a huge difference on a daily basis:<br /> Sasch Mayer <a href="https://plus.google.com/u/0/108942877395886428909/posts">on Google+</a> (Webmaster TC in English): <br /> <blockquote style="font-style: italic;"> "For a number of reasons this event does hold a special place for me, and always will. It's not because I was one of comparatively few people to be invited for a Jolly at the ‘Plex, but because this trip offered the world's TCs a unique opportunity to finally meet each other in person."</blockquote> <br /> Herbert Sulzer, a.k.a. Luzie <a href="https://plus.google.com/u/0/117648168533284905994/posts">on Google+</a> (Webmaster TC in English, German and Spanish): <br /> <blockquote style="font-style: italic;"> “Hehehe! Fun, fun fun, this was all fun :D Huhhh”</blockquote> <br /> Aygul Zagidullina <a href="https://plus.google.com/101697775213251991950/posts">on Google+</a> (Web Search TC in English): <br /> <blockquote style="font-style: italic;"> “It was a truly fantastic, amazing, and unforgettable experience meeting so many other TCs across product forums and having the chance to talk to and hear from so many Googlers across so many products!”</blockquote> <br /> Of course we did receive lots of constructive feedback, too. Transparency and communication were on top of the list, and we're looking into increasing our outreach efforts via <a href="//www.google.com/webmasters/tools/">Webmaster Tools</a>, so stay tuned! By the way, if you haven’t done so yet, please remember to use the <a href="//www.google.com/support/webmasters/bin/answer.py?answer=140528">forwarding option in the Webmaster Tools Message Center</a> to get the messages straight to your email inbox. In the meantime please keep an eye on our Webmaster Central Blog, and of course keep on contributing to discussions in the <a href="//www.google.com/support/forum/p/Webmasters?hl=en">Google Webmaster Forum</a>.<br /> On behalf of all Google guides who participated in the 2011 Summit we want to thank you. You guys rock! :)<br /> <div class="separator" style="clear: both; text-align: center;"> <a href="//4.bp.blogspot.com/-Cr9AsYrchvU/ToyRccLIWLI/AAAAAAAAAIA/cn-b75sfpNY/s1600/map.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="301" src="//4.bp.blogspot.com/-Cr9AsYrchvU/ToyRccLIWLI/AAAAAAAAAIA/cn-b75sfpNY/s400/map.JPG" width="400"></a> </div> That’s right, TCs & Google Guides came from all over the world to convene in California.<br /> <br /> <div class="separator" style="clear: both; text-align: center;"> <a href="//4.bp.blogspot.com/-F0OYji7ZCvk/ToyRlH7dffI/AAAAAAAAAII/veDHdscb7Z8/s1600/group1.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="301" src="//4.bp.blogspot.com/-F0OYji7ZCvk/ToyRlH7dffI/AAAAAAAAAII/veDHdscb7Z8/s400/group1.JPG" width="400"></a> </div> TCs & Google Guides from Webmaster Central and Search forums after one of the sessions.<br /> <br /> <div class="separator" style="clear: both; text-align: center;"> <a href="//4.bp.blogspot.com/-g5KfX6RQimk/ToyR10Kae-I/AAAAAAAAAIQ/fFvIqdTbRL4/s1600/lunch.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="300" src="//4.bp.blogspot.com/-g5KfX6RQimk/ToyR10Kae-I/AAAAAAAAAIQ/fFvIqdTbRL4/s400/lunch.JPG" width="400"></a> </div> After a day packed with presentations and breakout sessions...<br /> <br /> <div class="separator" style="clear: both; text-align: center;"> <a href="//1.bp.blogspot.com/-OVjmWIeHWCY/ToyR7NDWEBI/AAAAAAAAAIY/wieeecuixXk/s1600/dj.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="300" src="//1.bp.blogspot.com/-OVjmWIeHWCY/ToyR7NDWEBI/AAAAAAAAAIY/wieeecuixXk/s400/dj.JPG" width="400"></a> </div> ...we did what we actually came for...<br /> <br /> <div class="separator" style="clear: both; text-align: center;"> <a href="//4.bp.blogspot.com/-uheEKXL4-3I/ToySDEq52bI/AAAAAAAAAIg/hC1_aMtdA8Y/s1600/android.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="300" src="//4.bp.blogspot.com/-uheEKXL4-3I/ToySDEq52bI/AAAAAAAAAIg/hC1_aMtdA8Y/s400/android.JPG" width="400"></a> </div> ...enjoyed a party, celebrated and had a great time together.<br /> <br /> <span class="byline-author">Posted by <a href="https://plus.google.com/116454053076386107961/about" rel="author">Esperanza Navas</a>, <a href="https://plus.google.com/102575132391459963731/about" rel="author">Yves Taquet</a>, <a href="https://plus.google.com/100370036835775851472/about" rel="author">Uli Lutz</a>, & <a href="https://plus.google.com/105501965108087246894/about" rel="author">Kaspar Szymanski</a>, Google Search Quality</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"> Webmaster level: All<br /> The TC Summit was a blast! As we wrote in our <a href="http://googlewebmastercentral.blogspot.com/2011/09/recognizing-top-contributors-in-googles.html">announcement post</a>, we recently invited more than 250 Top Contributors from all over the world to California to thank them for being so awesome and to give them the opportunity to meet some of our forum guides, engineers and product managers in person.<br /> Our colleagues Adrianne and Brenna already published a <a href="http://googleblog.blogspot.com/2011/09/saying-thanksin-personto-our-google-top.html">recap post</a> on the Official Google Blog. As for us, the search folks at Google, there's not much left to say except that we enjoyed the event and meeting Top Contributors in real life, many of them for the first time. We got the feeling you guys had a great time, too. Let’s quote a few of the folks who make a huge difference on a daily basis:<br /> Sasch Mayer <a href="https://plus.google.com/u/0/108942877395886428909/posts">on Google+</a> (Webmaster TC in English): <br /> <blockquote style="font-style: italic;"> "For a number of reasons this event does hold a special place for me, and always will. It's not because I was one of comparatively few people to be invited for a Jolly at the ‘Plex, but because this trip offered the world's TCs a unique opportunity to finally meet each other in person."</blockquote> <br /> Herbert Sulzer, a.k.a. Luzie <a href="https://plus.google.com/u/0/117648168533284905994/posts">on Google+</a> (Webmaster TC in English, German and Spanish): <br /> <blockquote style="font-style: italic;"> “Hehehe! Fun, fun fun, this was all fun :D Huhhh”</blockquote> <br /> Aygul Zagidullina <a href="https://plus.google.com/101697775213251991950/posts">on Google+</a> (Web Search TC in English): <br /> <blockquote style="font-style: italic;"> “It was a truly fantastic, amazing, and unforgettable experience meeting so many other TCs across product forums and having the chance to talk to and hear from so many Googlers across so many products!”</blockquote> <br /> Of course we did receive lots of constructive feedback, too. Transparency and communication were on top of the list, and we're looking into increasing our outreach efforts via <a href="//www.google.com/webmasters/tools/">Webmaster Tools</a>, so stay tuned! By the way, if you haven’t done so yet, please remember to use the <a href="//www.google.com/support/webmasters/bin/answer.py?answer=140528">forwarding option in the Webmaster Tools Message Center</a> to get the messages straight to your email inbox. In the meantime please keep an eye on our Webmaster Central Blog, and of course keep on contributing to discussions in the <a href="//www.google.com/support/forum/p/Webmasters?hl=en">Google Webmaster Forum</a>.<br /> On behalf of all Google guides who participated in the 2011 Summit we want to thank you. You guys rock! :)<br /> <div class="separator" style="clear: both; text-align: center;"> <a href="//4.bp.blogspot.com/-Cr9AsYrchvU/ToyRccLIWLI/AAAAAAAAAIA/cn-b75sfpNY/s1600/map.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="301" src="//4.bp.blogspot.com/-Cr9AsYrchvU/ToyRccLIWLI/AAAAAAAAAIA/cn-b75sfpNY/s400/map.JPG" width="400"></a> </div> That’s right, TCs & Google Guides came from all over the world to convene in California.<br /> <br /> <div class="separator" style="clear: both; text-align: center;"> <a href="//4.bp.blogspot.com/-F0OYji7ZCvk/ToyRlH7dffI/AAAAAAAAAII/veDHdscb7Z8/s1600/group1.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="301" src="//4.bp.blogspot.com/-F0OYji7ZCvk/ToyRlH7dffI/AAAAAAAAAII/veDHdscb7Z8/s400/group1.JPG" width="400"></a> </div> TCs & Google Guides from Webmaster Central and Search forums after one of the sessions.<br /> <br /> <div class="separator" style="clear: both; text-align: center;"> <a href="//4.bp.blogspot.com/-g5KfX6RQimk/ToyR10Kae-I/AAAAAAAAAIQ/fFvIqdTbRL4/s1600/lunch.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="300" src="//4.bp.blogspot.com/-g5KfX6RQimk/ToyR10Kae-I/AAAAAAAAAIQ/fFvIqdTbRL4/s400/lunch.JPG" width="400"></a> </div> After a day packed with presentations and breakout sessions...<br /> <br /> <div class="separator" style="clear: both; text-align: center;"> <a href="//1.bp.blogspot.com/-OVjmWIeHWCY/ToyR7NDWEBI/AAAAAAAAAIY/wieeecuixXk/s1600/dj.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="300" src="//1.bp.blogspot.com/-OVjmWIeHWCY/ToyR7NDWEBI/AAAAAAAAAIY/wieeecuixXk/s400/dj.JPG" width="400"></a> </div> ...we did what we actually came for...<br /> <br /> <div class="separator" style="clear: both; text-align: center;"> <a href="//4.bp.blogspot.com/-uheEKXL4-3I/ToySDEq52bI/AAAAAAAAAIg/hC1_aMtdA8Y/s1600/android.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="300" src="//4.bp.blogspot.com/-uheEKXL4-3I/ToySDEq52bI/AAAAAAAAAIg/hC1_aMtdA8Y/s400/android.JPG" width="400"></a> </div> ...enjoyed a party, celebrated and had a great time together.<br /> <br /> <span class="byline-author">Posted by <a href="https://plus.google.com/116454053076386107961/about" rel="author">Esperanza Navas</a>, <a href="https://plus.google.com/102575132391459963731/about" rel="author">Yves Taquet</a>, <a href="https://plus.google.com/100370036835775851472/about" rel="author">Uli Lutz</a>, & <a href="https://plus.google.com/105501965108087246894/about" rel="author">Kaspar Szymanski</a>, Google Search Quality</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 Contributors rock&url=https://webmasters.googleblog.com/2011/10/webmaster-forums-top-contributors-rock.html?hl=en&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/2011/10/webmaster-forums-top-contributors-rock.html?hl=en'> <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/2011/10/webmaster-forums-top-contributors-rock.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/advanced?hl=en' rel='tag'> advanced </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/beginner?hl=en' rel='tag'> beginner </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/events?hl=en' rel='tag'> events </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/intermediate?hl=en' rel='tag'> intermediate </a> </span> </div> </div> </div> <div class='post' data-id='1522578317916163061' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2011/09/reconsideration-requests-get-more.html?hl=en' itemprop='url' title='Reconsideration requests get more transparent'> Reconsideration requests get more transparent </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, September 15, 2011 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <div> Webmaster level: All</div> <div> <br /></div> <div> If your site isn't appearing in Google search results, or it's performing more poorly than it once did (and you believe that it does not violate our <a href="//www.google.com/support/webmasters/bin/answer.py?answer=35769">Webmaster Guidelines</a>), you can ask Google to reconsider your site. Over time, we’ve worked to improve the reconsideration process for webmasters. A couple of years ago, in addition to <a href="http://googlewebmastercentral.blogspot.com/2009/06/reconsideration-requests-now-with.html">confirming that we had received the request</a>, we started sending a second message to webmasters confirming that we had processed their request. This was a huge step for webmasters who were anxiously awaiting results. Since then, we’ve received feedback that webmasters wanted to know the outcome of their requests. Earlier this year, we started experimenting with sending more detailed reconsideration request responses and the feedback we’ve gotten has been very positive!</div> <div> <br /></div> <div> Now, if your site is affected by a manual spam action, we may let you know if we were able to revoke that manual action based on your reconsideration request. Or, we could tell you if your site is still in violation of our guidelines. This might be a discouraging thing to hear, but once you know that there is still a problem, it will help you diagnose the issue.</div> <div> <br /></div> <div> If your site is not actually affected by any manual action (this is the most common scenario), we may let you know that as well. Perhaps your site isn’t being ranked highly by our algorithms, in which case our systems will respond to improvements on the site as changes are made, without your needing to submit a reconsideration request. Or maybe your site has access issues that are preventing Googlebot from crawling and indexing it. For more help debugging ranking issues, read <a href="//www.google.com/support/webmasters/bin/answer.py?answer=34444">our article about why a site may not be showing up in Google search results</a>.</div> <div> <br /></div> We’ve made a lot of progress on making the entire reconsideration request process more transparent. We aren’t able to reply to individual requests with specific feedback, but now many webmasters will be able to find out if their site has been affected by a manual action and they’ll know the outcome of the reconsideration review. In an ideal world, Google could be completely transparent about how every part of our rankings work. However, we have to maintain a delicate balance: trying to give as much information to webmasters as we can without letting spammers probe how to do more harm to users. We're happy that Google has set the standard on tools, transparency, and communication with site owners, but we'll keep looking for ways to do even better.<br /> <div> <br /> <span class="byline-author">Posted by Tiffany Oberoi and <a href="https://plus.google.com/107122646256015117642/about" rel="author">Michael Wyszomierski</a>, Search Quality Team</span></div> </div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <div> Webmaster level: All</div> <div> <br /></div> <div> If your site isn't appearing in Google search results, or it's performing more poorly than it once did (and you believe that it does not violate our <a href="//www.google.com/support/webmasters/bin/answer.py?answer=35769">Webmaster Guidelines</a>), you can ask Google to reconsider your site. Over time, we’ve worked to improve the reconsideration process for webmasters. A couple of years ago, in addition to <a href="http://googlewebmastercentral.blogspot.com/2009/06/reconsideration-requests-now-with.html">confirming that we had received the request</a>, we started sending a second message to webmasters confirming that we had processed their request. This was a huge step for webmasters who were anxiously awaiting results. Since then, we’ve received feedback that webmasters wanted to know the outcome of their requests. Earlier this year, we started experimenting with sending more detailed reconsideration request responses and the feedback we’ve gotten has been very positive!</div> <div> <br /></div> <div> Now, if your site is affected by a manual spam action, we may let you know if we were able to revoke that manual action based on your reconsideration request. Or, we could tell you if your site is still in violation of our guidelines. This might be a discouraging thing to hear, but once you know that there is still a problem, it will help you diagnose the issue.</div> <div> <br /></div> <div> If your site is not actually affected by any manual action (this is the most common scenario), we may let you know that as well. Perhaps your site isn’t being ranked highly by our algorithms, in which case our systems will respond to improvements on the site as changes are made, without your needing to submit a reconsideration request. Or maybe your site has access issues that are preventing Googlebot from crawling and indexing it. For more help debugging ranking issues, read <a href="//www.google.com/support/webmasters/bin/answer.py?answer=34444">our article about why a site may not be showing up in Google search results</a>.</div> <div> <br /></div> We’ve made a lot of progress on making the entire reconsideration request process more transparent. We aren’t able to reply to individual requests with specific feedback, but now many webmasters will be able to find out if their site has been affected by a manual action and they’ll know the outcome of the reconsideration review. In an ideal world, Google could be completely transparent about how every part of our rankings work. However, we have to maintain a delicate balance: trying to give as much information to webmasters as we can without letting spammers probe how to do more harm to users. We're happy that Google has set the standard on tools, transparency, and communication with site owners, but we'll keep looking for ways to do even better.<br /> <div> <br /> <span class="byline-author">Posted by Tiffany Oberoi and <a href="https://plus.google.com/107122646256015117642/about" rel="author">Michael Wyszomierski</a>, Search Quality Team</span></div> </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:Reconsideration requests get more transparent&url=https://webmasters.googleblog.com/2011/09/reconsideration-requests-get-more.html?hl=en&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/2011/09/reconsideration-requests-get-more.html?hl=en'> <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/2011/09/reconsideration-requests-get-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/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines?hl=en' rel='tag'> webmaster guidelines </a> </span> </div> </div> </div> <div class='post' data-id='6512999431727083845' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2011/08/help-us-improve-google-search.html?hl=en' itemprop='url' title='Help us improve Google Search'> Help us improve Google Search </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, August 23, 2011 </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"> Webmaster level: Advanced <br /> <br /> Yes, we're looking for help improving Google search—but this time we're not asking you to submit more spam reports. Although we still appreciate receiving quality spam reports, today we've got a different opportunity for you to improve Google Search: how about YOU join our team and do the webspam fighting yourself? <br /> <br /> Interested? Here's what we're looking for: open-minded academic graduates willing to work in a multinational environment in our Dublin office. Looking at a site's source code should not scare you. You should be excited about search engines and the Internet. It’s also essential that you share our aversion to webspam and the drive to make high-quality content accessible. PlayStation or foosball skills are a plus. <br /> <br /> <div style="text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg23hyiB6a9E-ewJoysvlG6I3D_COGanqxw4-FiHz-LIj48Ws4jvDOmxB34lpxb33UEz2-IAQ6sKHuAEI4kZgn-dK66iYo7aZqifMKussbWdYcMWh0cIPWbyHpRs4vCmhnsyPTT/s1600/DSCN0040.JPG" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5644094664958291810" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg23hyiB6a9E-ewJoysvlG6I3D_COGanqxw4-FiHz-LIj48Ws4jvDOmxB34lpxb33UEz2-IAQ6sKHuAEI4kZgn-dK66iYo7aZqifMKussbWdYcMWh0cIPWbyHpRs4vCmhnsyPTT/s400/DSCN0040.JPG" style="cursor: hand; cursor: pointer; height: 300px; width: 400px;" /></a> <br /> <i>This is an actual work environment photo taken at the Dublin Google office.</i> </div> <br /> <br /> If you'd like to know more about the positions available, here's the full list of <a href="http://www.google.ie/intl/en/jobs/dublin/adsales/techops/search-quality-associate-multiple-languages-available-eu-headquarters/index.html">requirements and responsibilities</a>. Great candidates should be able to email the recruiter directly. <br /> <br /> <span class="byline-author">Posted by <a href="https://plus.google.com/105501965108087246894/about" rel="author">Kaspar Szymanski</a>, Search Quality</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"> Webmaster level: Advanced <br /> <br /> Yes, we're looking for help improving Google search—but this time we're not asking you to submit more spam reports. Although we still appreciate receiving quality spam reports, today we've got a different opportunity for you to improve Google Search: how about YOU join our team and do the webspam fighting yourself? <br /> <br /> Interested? Here's what we're looking for: open-minded academic graduates willing to work in a multinational environment in our Dublin office. Looking at a site's source code should not scare you. You should be excited about search engines and the Internet. It’s also essential that you share our aversion to webspam and the drive to make high-quality content accessible. PlayStation or foosball skills are a plus. <br /> <br /> <div style="text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg23hyiB6a9E-ewJoysvlG6I3D_COGanqxw4-FiHz-LIj48Ws4jvDOmxB34lpxb33UEz2-IAQ6sKHuAEI4kZgn-dK66iYo7aZqifMKussbWdYcMWh0cIPWbyHpRs4vCmhnsyPTT/s1600/DSCN0040.JPG" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5644094664958291810" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg23hyiB6a9E-ewJoysvlG6I3D_COGanqxw4-FiHz-LIj48Ws4jvDOmxB34lpxb33UEz2-IAQ6sKHuAEI4kZgn-dK66iYo7aZqifMKussbWdYcMWh0cIPWbyHpRs4vCmhnsyPTT/s400/DSCN0040.JPG" style="cursor: hand; cursor: pointer; height: 300px; width: 400px;" /></a> <br /> <i>This is an actual work environment photo taken at the Dublin Google office.</i> </div> <br /> <br /> If you'd like to know more about the positions available, here's the full list of <a href="http://www.google.ie/intl/en/jobs/dublin/adsales/techops/search-quality-associate-multiple-languages-available-eu-headquarters/index.html">requirements and responsibilities</a>. Great candidates should be able to email the recruiter directly. <br /> <br /> <span class="byline-author">Posted by <a href="https://plus.google.com/105501965108087246894/about" rel="author">Kaspar Szymanski</a>, Search Quality</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:Help us improve Google Search&url=https://webmasters.googleblog.com/2011/08/help-us-improve-google-search.html?hl=en&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/2011/08/help-us-improve-google-search.html?hl=en'> <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/2011/08/help-us-improve-google-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/advanced?hl=en' rel='tag'> advanced </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> </span> </div> </div> </div> <div class='blog-pager' id='blog-pager'> <a class='home-link' href='https://webmasters.googleblog.com/?hl=en'> <i class='material-icons'>  </i> </a> <i class='material-icons disabled'>  </i> <span id='blog-pager-older-link'> <a class='blog-pager-older-link' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?updated-max=2011-08-23T12:10:00-07:00&max-results=20&start=17&by-date=false&hl=en' id='Blog1_blog-pager-older-link' title='Older Posts'> <i class='material-icons'>  </i> </a> </span> </div> <div class='clear'></div> </div></div> </div> </div> <div class='col-right'> <div class='section' id='sidebar-top'><div class='widget HTML' data-version='1' id='HTML9'> <div class='widget-content'> <a href="https://www.google.com/webmasters/tools/mobile-friendly/?utm_source=wmc-blog&utm_medium=referral&utm_campaign=blog-nav"><img src="https://lh3.googleusercontent.com/-osGJupx0-HY/VQta1nmaAPI/AAAAAAAACfs/UdMPzubsXFk/w80-h1368-no/blog%2Bpromo.png" align="left" width="80" /></a> Hey! <a href="https://search.google.com/test/mobile-friendly">Check here if your site is mobile-friendly.</a> </div> <div class='clear'></div> </div><div class='widget HTML' data-version='1' id='HTML10'> <div class='widget-content'> <div class='searchBox'> <input type='text' title='Search This Blog' placeholder='Search blog ...' /> </div> </div> <div class='clear'></div> </div></div> <div id='aside'> <div class='section' id='sidebar'><div class='widget Label' data-version='1' id='Label1'> <div class='tab'> <img class='sidebar-icon' src='data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAYpJREFUeNrs2aFuwzAQBmAvKRkMKRjZA4QMDJaWFgyMjuzFRg37DIUlA3uFkoGQSaWzJU+tpri5O9+l/zSfdFJlpe59yTmyVedq1PjfcZMZ70NuQnaF8w8htyE/rABtpviXkLcK88c5HhLkMBfgVan43zfFBNGMjHVGT/s55KP2pAvidbGHd+nzKt1RKSLG3rKF1iPFv6UWiPke8i7kEqGdGsI1O+LYVdqJAjgirwkKYD0ytkJBUNbAMvX8V3q9PhUsYvU1sWD8SO/sQvx2ahxOiNoJCSBCoAHYCEQAC4EKICOQASQEOmAS8RcAFxFN5hiIiugpgC3wk9hQAHH/70EBHXUN7IER5EWMiBgo2+nzOKQv9SCAeEM/OQAkhE/ncccFICB87qzQMia5FsJfOui0zMnmRvipU1ormHQuxGTxUsAcCFLxJQBLBLn4UoAFglW8BkATwS5eC6CBEBWvCShBiIvXBkgQRcVbADiI4uKtABSESvGWgB9EzHt3+tNwyO0qa9SoIYtvAQYAqDJhaWWeMecAAAAASUVORK5CYII='/> <h2> Labels </h2> <i class='material-icons arrow'>  </i> </div> <div class='widget-content list-label-widget-content'> <ul> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/accessibility?hl=en'> accessibility </a> <span dir='ltr'> 10 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/advanced?hl=en'> advanced </a> <span dir='ltr'> 195 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/AMP?hl=en'> AMP </a> <span dir='ltr'> 13 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Android?hl=en'> Android </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/API?hl=en'> API </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/apps?hl=en'> apps </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/autocomplete?hl=en'> autocomplete </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/beginner?hl=en'> beginner </a> <span dir='ltr'> 173 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/CAPTCHA?hl=en'> CAPTCHA </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Chrome?hl=en'> Chrome </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/cms?hl=en'> cms </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en'> crawling and indexing </a> <span dir='ltr'> 158 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/encryption?hl=en'> encryption </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/events?hl=en'> events </a> <span dir='ltr'> 51 </span> </li> <li> <span dir='ltr'> feedback and communication </span> <span dir='ltr'> 83 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/forums?hl=en'> forums </a> <span dir='ltr'> 5 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/general%20tips?hl=en'> general tips </a> <span dir='ltr'> 90 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/geotargeting?hl=en'> geotargeting </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20Assistant?hl=en'> Google Assistant </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20I%2FO?hl=en'> Google I/O </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20Images?hl=en'> Google Images </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20News?hl=en'> Google News </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hacked%20sites?hl=en'> hacked sites </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hangout?hl=en'> hangout </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hreflang?hl=en'> hreflang </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/https?hl=en'> https </a> <span dir='ltr'> 5 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/images?hl=en'> images </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/intermediate?hl=en'> intermediate </a> <span dir='ltr'> 205 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/interstitials?hl=en'> interstitials </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/javascript?hl=en'> javascript </a> <span dir='ltr'> 8 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/job%20search?hl=en'> job search </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/localization?hl=en'> localization </a> <span dir='ltr'> 21 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/malware?hl=en'> malware </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/mobile?hl=en'> mobile </a> <span dir='ltr'> 63 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en'> mobile-friendly </a> <span dir='ltr'> 14 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/nohacked?hl=en'> nohacked </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/performance?hl=en'> performance </a> <span dir='ltr'> 17 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/product%20expert?hl=en'> product expert </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/product%20experts?hl=en'> product experts </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/products%20and%20services?hl=en'> products and services </a> <span dir='ltr'> 63 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/questions?hl=en'> questions </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/ranking?hl=en'> ranking </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/recipes?hl=en'> recipes </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rendering?hl=en'> rendering </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Responsive%20Web%20Design?hl=en'> Responsive Web Design </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rich%20cards?hl=en'> rich cards </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rich%20results?hl=en'> rich results </a> <span dir='ltr'> 10 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en'> search console </a> <span dir='ltr'> 35 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20for%20beginners?hl=en'> search for beginners </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20queries?hl=en'> search queries </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en'> search results </a> <span dir='ltr'> 140 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/security?hl=en'> security </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/seo?hl=en'> seo </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/sitemaps?hl=en'> sitemaps </a> <span dir='ltr'> 46 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/speed?hl=en'> speed </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=en'> structured data </a> <span dir='ltr'> 33 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/summit?hl=en'> summit </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/TLDs?hl=en'> TLDs </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/url%20removals?hl=en'> url removals </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/UX?hl=en'> UX </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/verification?hl=en'> verification </a> <span dir='ltr'> 8 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/video?hl=en'> video </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en'> webmaster community </a> <span dir='ltr'> 24 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20forum?hl=en'> webmaster forum </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines?hl=en'> webmaster guidelines </a> <span dir='ltr'> 57 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en'> webmaster tools </a> <span dir='ltr'> 177 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmasters?hl=en'> webmasters </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/youtube%20channel?hl=en'> youtube channel </a> <span dir='ltr'> 6 </span> </li> </ul> <div class='clear'></div> </div> </div><div class='widget BlogArchive' data-version='1' id='BlogArchive1'> <div class='tab'> <i class='material-icons icon'>  </i> <h2> Archive </h2> <i class='material-icons arrow'>  </i> </div> <div class='widget-content'> <div id='ArchiveList'> <div id='BlogArchive1_ArchiveList'> <ul class='hierarchy'> <li class='archivedate expanded'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy toggle-open'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/?hl=en'> 2020 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate expanded'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/?hl=en'> 2019 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/?hl=en'> 2018 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/?hl=en'> 2017 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/?hl=en'> 2016 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/?hl=en'> 2015 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/?hl=en'> 2014 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/?hl=en'> 2013 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/?hl=en'> 2012 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/?hl=en'> 2011 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/?hl=en'> 2010 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/?hl=en'> 2009 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/?hl=en'> 2008 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/?hl=en'> 2007 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/?hl=en'> 2006 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/08/?hl=en'> 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'] = 'AOuZoY46-fP9bsB9WP9l7bMFBnDyzud49g:1732430107758';_WidgetManager._Init('//www.blogger.com/rearrange?blogID\x3d32069983','//webmasters.googleblog.com/search/label/feedback%20and%20communication?hl\x3den','32069983'); _WidgetManager._SetDataContext([{'name': 'blog', 'data': {'blogId': '32069983', 'title': 'Official Google Webmaster Central Blog', 'url': 'https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl\x3den', 'canonicalUrl': 'https://webmasters.googleblog.com/search/label/feedback%20and%20communication', 'homepageUrl': 'https://webmasters.googleblog.com/?hl\x3den', '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': 'index', 'searchLabel': 'feedback and communication', 'pageName': 'feedback and communication', 'pageTitle': 'Official Google Webmaster Central Blog: feedback and communication', 'metaDescription': 'Official news on crawling and indexing sites for the Google index'}}, {'name': 'features', 'data': {}}, {'name': 'messages', 'data': {'edit': 'Edit', 'linkCopiedToClipboard': 'Link copied to clipboard!', 'ok': 'Ok', 'postLink': 'Post Link'}}, {'name': 'template', 'data': {'name': 'custom', 'localizedName': 'Custom', 'isResponsive': false, 'isAlternateRendering': false, 'isCustom': true}}, {'name': 'view', 'data': {'classic': {'name': 'classic', 'url': '?view\x3dclassic'}, 'flipcard': {'name': 'flipcard', 'url': '?view\x3dflipcard'}, 'magazine': {'name': 'magazine', 'url': '?view\x3dmagazine'}, 'mosaic': {'name': 'mosaic', 'url': '?view\x3dmosaic'}, 'sidebar': {'name': 'sidebar', 'url': '?view\x3dsidebar'}, 'snapshot': {'name': 'snapshot', 'url': '?view\x3dsnapshot'}, 'timeslide': {'name': 'timeslide', 'url': '?view\x3dtimeslide'}, 'isMobile': false, 'title': 'Official Google Webmaster Central Blog', 'description': 'Official news on crawling and indexing sites for the Google index', 'url': 'https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl\x3den', 'type': 'feed', 'isSingleItem': false, 'isMultipleItems': true, 'isError': false, 'isPage': false, 'isPost': false, 'isHomepage': false, 'isArchive': false, 'isSearch': true, 'isLabelSearch': true, 'search': {'label': 'feedback and communication', 'resultsMessage': 'Showing posts with the label feedback and communication', 'resultsMessageHtml': 'Showing posts with the label \x3cspan class\x3d\x27search-label\x27\x3efeedback and communication\x3c/span\x3e'}}}]); _WidgetManager._RegisterWidget('_HeaderView', new _WidgetInfo('Header1', 'header', document.getElementById('Header1'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_BlogView', new _WidgetInfo('Blog1', 'main', document.getElementById('Blog1'), {'cmtInteractionsEnabled': false, 'navMessage': 'Showing posts with label \x3cb\x3efeedback and communication\x3c/b\x3e. \x3ca href\x3d\x22https://webmasters.googleblog.com/\x22\x3eShow all posts\x3c/a\x3e'}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML9', 'sidebar-top', document.getElementById('HTML9'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML10', 'sidebar-top', document.getElementById('HTML10'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_LabelView', new _WidgetInfo('Label1', 'sidebar', document.getElementById('Label1'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_BlogArchiveView', new _WidgetInfo('BlogArchive1', 'sidebar', document.getElementById('BlogArchive1'), {'languageDirection': 'ltr', 'loadingMessage': 'Loading\x26hellip;'}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML6', 'sidebar', document.getElementById('HTML6'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML5', 'sidebar-bottom', document.getElementById('HTML5'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML1', 'sidebar-bottom', document.getElementById('HTML1'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML8', 'sidebar-bottom', document.getElementById('HTML8'), {}, 'displayModeFull')); </script> </body> </html>