CINXE.COM

<!DOCTYPE html> <html class='v2 list-page' dir='ltr' itemscope='' itemtype='http://schema.org/Blog' lang='en-US' xmlns='http://www.w3.org/1999/xhtml' xmlns:b='http://www.google.com/2005/gml/b' xmlns:data='http://www.google.com/2005/gml/data' xmlns:expr='http://www.google.com/2005/gml/expr'> <head> <link href='https://www.blogger.com/static/v1/widgets/3566091532-css_bundle_v2.css' rel='stylesheet' type='text/css'/> <title> Official Google Webmaster Central Blog: search console </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/search%20console' 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/search%20console' 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/search%20console' property='og:url'/> <meta content='Official Google Webmaster Central Blog' property='og:title'/> <meta content='Official news on crawling and indexing sites for the Google index' property='og:description'/>  <base target='_self'/> <style> html { font-family: Roboto, sans-serif; -moz-osx-font-smoothing: grayscale; -webkit-font-smoothing: antialiased; } body { padding: 0; /* This ensures that the scroll bar is always present, which is needed */ /* because content render happens after page load; otherwise the header */ /* would "bounce" in-between states. */ min-height: 150%; } h2 { font-size: 16px; } h1, h2, h3, h4, h5 { line-height: 2em; } html, h4, h5, h6 { font-size: 14px; } a, a:visited { color: #4184F3; text-decoration: none; } a:focus, a:hover, a:active { text-decoration: none; } .Header { margin-top: 15px; } .Header h1 { font-size: 32px; font-weight: 300; line-height: 32px; height: 42px; } .header-inner .Header .titlewrapper { padding: 0; margin-top: 30px; } .header-inner .Header .descriptionwrapper { padding: 0; margin: 0; } .cols-wrapper { margin-top: 56px; } .header-outer, .cols-wrapper, .footer-outer, .google-footer-outer { padding: 0 60px; } .header-inner { height: 256px; position: relative; } html, .header-inner a { color: #212121; color: rgba(0,0,0,.87); } .header-inner .google-logo { display: inline-block; background-size: contain; z-index: 1; height: 46px; overflow: hidden; margin-top: 4px; margin-right: 8px; } .header-left { position: absolute; top: 50%; -webkit-transform: translateY(-50%); transform: translateY(-50%); margin-top: 12px; width: 100%; } .google-logo { margin-left: -4px; } #google-footer { position: relative; font-size: 13px; list-style: none; text-align: right; } #google-footer a { color: #444; } #google-footer ul { margin: 0; padding: 0; height: 144px; line-height: 144px; } #google-footer ul li { display: inline; } #google-footer ul li:before { color: #999; content: "\00b7"; font-weight: bold; margin: 5px; } #google-footer ul li:first-child:before { content: ''; } #google-footer .google-logo-dark { left: 0; margin-top: -16px; position: absolute; top: 50%; } /** Sitemap links. **/ .footer-inner-2 { font-size: 14px; padding-top: 42px; padding-bottom: 74px; } .footer-inner-2 .HTML h2 { color: #212121; color: rgba(0,0,0,.87); font-size: 14px; font-weight: 500; padding-left: 0; margin: 10px 0; } .footer-inner-2 .HTML ul { font-weight: normal; list-style: none; padding-left: 0; } .footer-inner-2 .HTML li { line-height: 24px; padding: 0; } .footer-inner-2 li a { color: rgba(65,132,243,.87); } /** Archive widget. **/ .BlogArchive { font-size: 13px; font-weight: normal; } .BlogArchive .widget-content { display: none; } .BlogArchive h2, .Label h2 { color: #4184F3; text-decoration: none; } .BlogArchive .hierarchy li { display: inline-block; } /* Specificity needed here to override widget CSS defaults. */ .BlogArchive #ArchiveList ul li, .BlogArchive #ArchiveList ul ul li { margin: 0; padding-left: 0; text-indent: 0; } .BlogArchive .intervalToggle { cursor: pointer; } .BlogArchive .expanded .intervalToggle .new-toggle { -ms-transform: rotate(180deg); transform: rotate(180deg); } .BlogArchive .new-toggle { float: right; padding-top: 3px; opacity: 0.87; } #ArchiveList { text-transform: uppercase; } #ArchiveList .expanded > ul:last-child { margin-bottom: 16px; } #ArchiveList .archivedate { width: 100%; } /* Months */ .BlogArchive .items { max-width: 150px; margin-left: -4px; } .BlogArchive .expanded .items { margin-bottom: 10px; overflow: hidden; } .BlogArchive .items > ul { float: left; height: 32px; } .BlogArchive .items a { padding: 0 4px; } .Label { font-size: 13px; font-weight: normal; } .sidebar-icon { display: inline-block; width: 24px; height: 24px; vertical-align: middle; margin-right: 12px; margin-top: -1px } .Label a { margin-right: 4px; } .Label .widget-content { display: none; } .FollowByEmail { font-size: 13px; font-weight: normal; } .FollowByEmail h2 { background: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABEAAAALCAYAAACZIGYHAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAUBJREFUeNrMkSGLAlEUhb+ZB4JFi8mx2cz+ApvhRUGTcUCrNqNJDYIi+DO0GUwmQXDK2DSIoGgZcSaIjDrzwrK4ssvChj1w0733O+fdp+m6PozH4yQSCfb7Pa7r8pOi0SjJZBLP8zgej4gAIMvlMuPxmADIYrHger1+C6lUKmo+NJ/NZojb7SZDWiwWo1qtks1msW2bw+HwZdkwDHq9HvV6nel0SqvVYrvdIh6Ph3Qch+VyqRYLhQJSSjRNw7IsfN9XgGKxSLfbJZfL0e/3aTabrFYr7vc7IujLcOh8PqunrNdr0uk0pVKJVCpFJBJRgEajweVyod1uMxgM2O12BAGUgRbU8DV2JpOhVquRz+cRQii3+XxOp9NRN3jVR5LPOp1OjEYjlSL8hclkgmmabDabt4d+m+S30vkD/R/IU4ABAPTZgnZdmG/PAAAAAElFTkSuQmCC"); background-repeat: no-repeat; background-position: 0 50%; text-indent: 30px; } .FollowByEmail .widget-content { display: none; } .searchBox input { border: 1px solid #eee; color: #212121; color: rgba(0,0,0,.87); font-size: 14px; padding: 8px 8px 8px 40px; width: 164px; font-family: Roboto, sans-serif; background: url("https://www.gstatic.com/images/icons/material/system/1x/search_grey600_24dp.png") 8px center no-repeat; } .searchBox ::-webkit-input-placeholder { /* WebKit, Blink, Edge */ color: rgba(0,0,0,.54); } .searchBox :-moz-placeholder { /* Mozilla Firefox 4 to 18 */ color: #000; opacity: 0.54; } .searchBox ::-moz-placeholder { /* Mozilla Firefox 19+ */ color: #000; opacity: 0.54; } .searchBox :-ms-input-placeholder { /* Internet Explorer 10-11 */ color: #757575; } .widget-item-control { margin-top: 0px; } .section { margin: 0; padding: 0; } #sidebar-top { border: 1px solid #eee; } #sidebar-top > div { margin: 16px 0; } .widget ul { line-height: 1.6; } /*main post*/ .post { margin-bottom:30px; } #main .post .title { margin: 0; } #main .post .title a { color: #212121; color: rgba(0,0,0,.87); font-weight: normal; font-size: 24px; } #main .post .title a:hover { text-decoration:none; color:#4184F3; } .message, #main .post .post-header { margin: 0; padding: 0; } #main .post .post-header .caption, #main .post .post-header .labels-caption, #main .post .post-footer .caption, #main .post .post-footer .labels-caption { color: #444; font-weight: 500; } #main .tr-caption-container td { text-align: left; } #main .post .tr-caption { color: #757575; color: rgba(0,0,0,.54); display: block; max-width: 560px; padding-bottom: 20px; } #main .post .tr-caption-container { line-height: 24px; margin: -1px 0 0 0 !important; padding: 4px 0; text-align: left; } #main .post .post-header .published{ font-size:11px; font-weight:bold; } .post-header .publishdate { font-size: 17px; font-weight:normal; color: #757575; color: rgba(0,0,0,.54); } #main .post .post-footer{ font-size:12px; padding-bottom: 21px; } .label-footer { margin-bottom: 12px; margin-top: 12px; } .comment-img { margin-right: 16px; opacity: 0.54; vertical-align: middle; } #main .post .post-header .published { margin-bottom: 40px; margin-top: -2px; } .post .post-content { color: #212121; color: rgba(0,0,0,.87); font-size: 17px; margin: 25px 0 36px 0; line-height: 32px; } .post-body .post-content ul, .post-body .post-content ol { margin: 16px 0; padding: 0 48px; } .post-summary { display: none; } /* Another old-style caption. */ .post-content div i, .post-content div + i { font-size: 14px; font-style: normal; color: #757575; color: rgba(0,0,0,.54); display: block; line-height: 24px; margin-bottom: 16px; text-align: left; } /* Another old-style caption (with link) */ .post-content a > i { color: #4184F3 !important; } /* Old-style captions for images. */ .post-content .separator + div:not(.separator) { margin-top: -16px; } /* Capture section headers. */ .post-content br + br + b, .post-content .space + .space + b, .post-content .separator + b { display: inline-block; margin-bottom: 8px; margin-top: 24px; } .post-content li { line-height: 32px; } /* Override all post images/videos to left align. */ .post-content .separator, .post-content > div { text-align: left; } .post-content .separator > a, .post-content .separator > span { margin-left: 0 !important; } .post-content img { max-width: 100%; height: auto; width: auto; } .post-content .tr-caption-container img { margin-bottom: 12px; } .post-content iframe, .post-content embed { max-width: 100%; } .post-content .carousel-container { margin-bottom: 48px; } #main .post-content b { font-weight: 500; } /* These are the main paragraph spacing tweaks. */ #main .post-content br { content: ' '; display: block; padding: 4px; } .post-content .space { display: block; height: 8px; } .post-content iframe + .space, .post-content iframe + br { padding: 0 !important; } #main .post .jump-link { margin-bottom:10px; } .post-content img, .post-content iframe { margin: 30px 0 20px 0; } .post-content > img:first-child, .post-content > iframe:first-child { margin-top: 0; } .col-right .section { padding: 0 16px; } #aside { background:#fff; border:1px solid #eee; border-top: 0; } #aside .widget { margin:0; } #aside .widget h2, #ArchiveList .toggle + a.post-count-link { color: #212121; color: rgba(0,0,0,.87); font-weight: 400 !important; margin: 0; } #ArchiveList .toggle { float: right; } #ArchiveList .toggle .material-icons { padding-top: 4px; } #sidebar .tab { cursor: pointer; } #sidebar .tab .arrow { display: inline-block; float: right; } #sidebar .tab .icon { display: inline-block; vertical-align: top; height: 24px; width: 24px; margin-right: 13px; margin-left: -1px; margin-top: 1px; color: #757575; color: rgba(0,0,0,.54); } #sidebar .widget-content > :first-child { padding-top: 8px; } #sidebar .active .tab .arrow { -ms-transform: rotate(180deg); transform: rotate(180deg); } #sidebar .arrow { color: #757575; color: rgba(0,0,0,.54); } #sidebar .widget h2 { font-size: 14px; line-height: 24px; display: inline-block; } #sidebar .widget .BlogArchive { padding-bottom: 8px; } #sidebar .widget { border-bottom: 1px solid #eee; box-shadow: 0px 1px 0 white; margin-bottom: 0; padding: 14px 0; min-height: 20px; } #sidebar .widget:last-child { border-bottom: none; box-shadow: none; margin-bottom: 0; } #sidebar ul { margin: 0; padding: 0; } #sidebar ul li { list-style:none; padding:0; } #sidebar ul li a { line-height: 32px; } #sidebar .archive { background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAYCAYAAADzoH0MAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAE1JREFUeNpiNDY23s9AAWBioBCwYBM8c+YMVsUmJibEGYBNMS5DaeMFfDYSZQA2v9I3FrB5AZeriI4FmnrBccCT8mhmGs1MwyAzAQQYAKEWG9zm9QFEAAAAAElFTkSuQmCC"); height: 24px; line-height: 24px; padding-left: 30px; } #sidebar .labels { background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABEAAAARCAYAAAA7bUf6AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAUxJREFUeNpiNDY23s9AAMycOfM7UF05kHkZmzwTMkdSUhKrIcXFxZy3bt3qBjIN8RrS09PDsHnzZjCNDr58+cKQlpbGDjSoHcg1w2oIyAUODg5gARCNzUVIBrUCuVYYhjx//pzhwIEDYAEQDeJjA1CDWIAGNQK59jBxRuSABbkAlwHIgIeHh2HWrFn/1NTU2oDcvSgBS4wBSC5iArqoCsj1YGIgEyAZVMoEchqlBjEB/cZAiUHg2AEGznpKDAImxOeM////B4VLKtBvEUCngZ1ILKivr3/u6+ubBzJAGZQ9gC5aQoqLgAY8BhkAZL4BuQQkxgXE34A4BuiiZEIuAhrwEGhAEZD5DpzYoIaA2UAM4kQADUrHZRDUgAIg8wO2XAwzbQXQa5OweQ1owB10AyA6gS7BgX1u3ry5397eHow3bdo0EyjGi00tQIABANPgyAH1q1eaAAAAAElFTkSuQmCC"); height: 20px; line-height: 20px; padding-left: 30px; } #sidebar .rss a { background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABIAAAASCAYAAABWzo5XAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAX5JREFUeNqsVDGSgkAQHL2rIiIikohIc/EBRkbwAIwuwgfwAXiAD9AHSI7kEkECRCb6AIyINDLx7K0aa6kT7uq0q7YYtnZ7umdnt7darXbr9Zpegeu61DNNc0dvwCcH4/GYJpMJnc9nOhwOVJbl/4hAAokMECZJQtvt9k+kH7qufyEYDAakqqqYxFdRFBqNRmTbNg2HQ0rTlK7XayvR0xqBdDqdkuM4dE/0ULhYLOh4PHYrknG5XGi/31MYhuL/nkwonM1mlGUZ1XXdrsiyLGEDhY7juJEZ1u5tIixDGdYhmYw+B7CAzPP5nDabjdgIAgCksMX1832/3drtdqPT6SQWapomiGEFNkDEdpDMMAzK81ys/7XYy+XyoQgq2WoURSIJ2iIIgp/WZCCTvFm2wgeAU31aI3Q2GhIDMeB53qPYPIcm5VrxXIOIOxsDMStjVawAc1VViRgN22lNBiuQN3GR+SY07hpOoStmFQAKXRRFY93bnpG+fONfedi+BRgAbkS8Fxp7QQIAAAAASUVORK5CYII="); } #sidebar .subscription a { background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABEAAAALCAYAAACZIGYHAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAUBJREFUeNrMkSGLAlEUhb+ZB4JFi8mx2cz+ApvhRUGTcUCrNqNJDYIi+DO0GUwmQXDK2DSIoGgZcSaIjDrzwrK4ssvChj1w0733O+fdp+m6PozH4yQSCfb7Pa7r8pOi0SjJZBLP8zgej4gAIMvlMuPxmADIYrHger1+C6lUKmo+NJ/NZojb7SZDWiwWo1qtks1msW2bw+HwZdkwDHq9HvV6nel0SqvVYrvdIh6Ph3Qch+VyqRYLhQJSSjRNw7IsfN9XgGKxSLfbJZfL0e/3aTabrFYr7vc7IujLcOh8PqunrNdr0uk0pVKJVCpFJBJRgEajweVyod1uMxgM2O12BAGUgRbU8DV2JpOhVquRz+cRQii3+XxOp9NRN3jVR5LPOp1OjEYjlSL8hclkgmmabDabt4d+m+S30vkD/R/IU4ABAPTZgnZdmG/PAAAAAElFTkSuQmCC"); } #sidebar-bottom { background: #f5f5f5; border-top:1px solid #eee; } #sidebar-bottom .widget { border-bottom: 1px solid #e0e0e0; padding: 15px 0; text-align: center; } #sidebar-bottom > div:last-child { border-bottom: 0; } #sidebar-bottom .text { line-height: 20px; } /* Home, forward, and backward pagination. */ .blog-pager { border-top : 1px #e0e0e0 solid; padding-top: 10px; margin-top: 15px; text-align: right !important; } #blog-pager { margin-botom: 0; margin-top: -14px; padding: 16px 0 0 0; } #blog-pager a { display: inline-block; } .blog-pager i.disabled { opacity: 0.2 !important; } .blog-pager i { color: black; margin-left: 16px; opacity: 0.54; } .blog-pager i:hover, .blog-pager i:active { opacity: 0.87; } #blog-pager-older-link, #blog-pager-newer-link { float: none; } .gplus-profile { background-color: #fafafa; border: 1px solid #eee; overflow: hidden; width: 212px; } .gplus-profile-inner { margin-left: -1px; margin-top: -1px; } /* Sidebar follow buttons. */ .followgooglewrapper { padding: 12px 0 0 0; } .loading { visibility: hidden; } .detail-page .post-footer .cmt_iframe_holder { padding-top: 40px !important; } /** Desktop **/ @media (max-width: 900px) { .col-right { display: none; } .col-main { margin-right: 0; min-width: initial; } .footer-outer { display: none; } .cols-wrapper { min-width: initial; } .google-footer-outer { background-color: #f5f5f5; } } /** Tablet **/ @media (max-width: 712px) { .header-outer, .cols-wrapper, .footer-outer, .google-footer-outer { padding: 0 40px; } } /* An extra breakpoint accommodating for long blog titles. */ @media (max-width: 600px) { .header-left { height: 100%; top: inherit; margin-top: 0; -webkit-transform: initial; transform: initial; } .header-title { margin-top: 18px; } .header-inner .google-logo { height: 40px; margin-top: 3px; } .header-inner .google-logo img { height: 42px; } .header-title h2 { font-size: 32px; line-height: 40px; } .header-desc { bottom: 24px; position: absolute; } } /** Mobile/small desktop window; also landscape. **/ @media (max-width: 480px), (max-height: 480px) { .header-outer, .cols-wrapper, .footer-outer, .google-footer-outer { padding: 0 16px; } .cols-wrapper { margin-top: 0; } .post-header .publishdate, .post .post-content { font-size: 16px; } .post .post-content { line-height: 28px; margin-bottom: 30px; } .post { margin-top: 30px; } .byline-author { display: block; font-size: 12px; line-height: 24px; margin-top: 6px; } #main .post .title a { font-weight: 500; color: #4c4c4c; color: rgba(0,0,0,.70); } #main .post .post-header { padding-bottom: 12px; } #main .post .post-header .published { margin-bottom: -8px; margin-top: 3px; } .post .read-more { display: block; margin-top: 14px; } .post .tr-caption { font-size: 12px; } #main .post .title a { font-size: 20px; line-height: 30px; } .post-content iframe { /* iframe won't keep aspect ratio when scaled down. */ max-height: 240px; } .post-content .separator img, .post-content .tr-caption-container img, .post-content iframe { margin-left: -16px; max-width: inherit; width: calc(100% + 32px); } .post-content table, .post-content td { width: 100%; } #blog-pager { margin: 0; padding: 16px 0; } /** List page tweaks. **/ .list-page .post-original { display: none; } .list-page .post-summary { display: block; } .list-page .comment-container { display: none; } .list-page #blog-pager { padding-top: 0; border: 0; margin-top: -8px; } .list-page .label-footer { display: none; } .list-page #main .post .post-footer { border-bottom: 1px solid #eee; margin: -16px 0 0 0; padding: 0 0 20px 0; } .list-page .post .share { display: none; } /** Detail page tweaks. **/ .detail-page .post-footer .cmt_iframe_holder { padding-top: 32px !important; } .detail-page .label-footer { margin-bottom: 0; } .detail-page #main .post .post-footer { padding-bottom: 0; } .detail-page #comments { display: none; } } [data-about-pullquote], [data-is-preview], [data-about-syndication] { display: none; } </style> <noscript> <style> .loading { visibility: visible }</style> </noscript> <script type='text/javascript'> (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) })(window,document,'script','https://www.google-analytics.com/analytics.js','ga'); ga('create', 'UA-18009-4', 'auto', 'blogger'); ga('blogger.send', 'pageview'); </script> <link href='https://www.blogger.com/dyn-css/authorization.css?targetBlogID=32069983&zx=8855dad6-3029-4476-9a6a-423344a04200' media='none' onload='if(media!='all')media='all'' rel='stylesheet'/><noscript><link href='https://www.blogger.com/dyn-css/authorization.css?targetBlogID=32069983&zx=8855dad6-3029-4476-9a6a-423344a04200' rel='stylesheet'/></noscript> <meta name='google-adsense-platform-account' content='ca-host-pub-1556223355139109'/> <meta name='google-adsense-platform-domain' content='blogspot.com'/> </head> <body> <script type='text/javascript'> //<![CDATA[ var axel = Math.random() + ""; var a = axel * 10000000000000; document.write('<iframe src="https://2542116.fls.doubleclick.net/activityi;src=2542116;type=gblog;cat=googl0;ord=ord=' + a + '?" width="1" height="1" frameborder="0" style="display:none"></iframe>'); //]]> </script> <noscript> <img alt='' height='1' src='https://ad.doubleclick.net/ddm/activity/src=2542116;type=gblog;cat=googl0;ord=1?' width='1'/> </noscript>  <div class='header-outer'> <div class='header-inner'> <div class='section' id='header'><div class='widget Header' data-version='1' id='Header1'> <div class='header-left'> <div class='header-title'> <a class='google-logo' href='https://webmasters.googleblog.com/?hl=en_US'> <img height='50' src='https://www.gstatic.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png'/> </a> <a href='/'> <h2> Webmaster Central Blog </h2> </a> </div> <div class='header-desc'> Official news on crawling and indexing sites for the Google index </div> </div> </div></div> </div> </div>  <div class='cols-wrapper loading'> <div class='col-main-wrapper'> <div class='col-main'> <div class='section' id='main'><div class='widget Blog' data-version='1' id='Blog1'> <div class='post' data-id='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_US' 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_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2019/09/google-search-news-coming-soon-to.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2019/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_US' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en_US' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=en_US' rel='tag'> structured data </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en_US' rel='tag'> webmaster community </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/youtube%20channel?hl=en_US' rel='tag'> youtube channel </a> </span> </div> </div> </div> <div class='post' data-id='6521970912333793298' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/08/minor-cleaning-up-in-search-console-api.html?hl=en_US' itemprop='url' title='Minor cleaning up in the Search Console API'> Minor cleaning up in the Search Console API </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Monday, August 26, 2019 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p>With the move to the <a href="https://support.google.com/webmasters/answer/7451491?hl=en">new Search Console</a>, we've decided to clean up some parts of the Search Console API as well. In the <a href="https://developers.google.com/webmaster-tools/search-console-api-original/v3/searchanalytics">Search Analytics API</a>, going forward we'll no longer support these Android app search appearance types:</p> <ul><li>Is Install</li> <li>Is App Universal</li> <li>Is Opened</li></ul> <p>Since these appearance types are no longer used in the UI, they haven't been populated with data recently. Going forward, we won't be showing these types at all through the API. </p> <p>Additionally, for the <a href="https://developers.google.com/webmaster-tools/search-console-api-original/v3/sitemaps">Sitemaps API</a>, we're no longer populating data on indexing status of submitted sitemap files in the "Indexed" field.</p> <p>We're still committed to the Search Console API. In particular, we're working on updating the Search Console API to the new Search Console. We don't have any specific timeframes to share at the moment, but stay tuned to find out more!</p> <br> <span class="byline-author">Posted by Ziv Hodak, Search Console product manager</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p>With the move to the <a href="https://support.google.com/webmasters/answer/7451491?hl=en">new Search Console</a>, we've decided to clean up some parts of the Search Console API as well. In the <a href="https://developers.google.com/webmaster-tools/search-console-api-original/v3/searchanalytics">Search Analytics API</a>, going forward we'll no longer support these Android app search appearance types:</p> <ul><li>Is Install</li> <li>Is App Universal</li> <li>Is Opened</li></ul> <p>Since these appearance types are no longer used in the UI, they haven't been populated with data recently. Going forward, we won't be showing these types at all through the API. </p> <p>Additionally, for the <a href="https://developers.google.com/webmaster-tools/search-console-api-original/v3/sitemaps">Sitemaps API</a>, we're no longer populating data on indexing status of submitted sitemap files in the "Indexed" field.</p> <p>We're still committed to the Search Console API. In particular, we're working on updating the Search Console API to the new Search Console. We don't have any specific timeframes to share at the moment, but stay tuned to find out more!</p> <br> <span class="byline-author">Posted by Ziv Hodak, Search Console product manager</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Minor cleaning up in the Search Console API&url=https://webmasters.googleblog.com/2019/08/minor-cleaning-up-in-search-console-api.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2019/08/minor-cleaning-up-in-search-console-api.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2019/08/minor-cleaning-up-in-search-console-api.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/Android?hl=en_US' rel='tag'> Android </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/API?hl=en_US' rel='tag'> API </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/sitemaps?hl=en_US' rel='tag'> sitemaps </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='9103369277615781852' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/08/evergreen-googlebot-in-testing-tools.html?hl=en_US' itemprop='url' title='Googlebot evergreen rendering in our testing tools'> Googlebot evergreen rendering in our testing tools </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, August 07, 2019 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <div style="text-align: left;"> Today we updated most of <a href="https://developers.google.com/search/tools/">our testing tools</a> so they are using the evergreen Chromium renderer. This affects our testing tools like the mobile-friendly test or the URL inspection tool in Search Console. In this post we look into what this means and what went into making this update happen.<br /> <br /></div> <h3 style="text-align: left;"> The evergreen Chromium renderer</h3> At Google I/O this year we were happy to announce <a href="https://www.youtube.com/watch/ufcijo46LCU?t=10m43s">the new evergreen Googlebot</a>.<br /> <br /> At its core the update is a switch from Chrome 41 as the rendering engine to the latest stable Chromium. Googlebot is now using the latest stable Chromium to run JavaScript and render pages. We will continue to update Googlebot along with the stable Chromium, hence we call it "evergreen".<br /> <br /> <table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody> <tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhKTeQjcclgL-R4Yg6BME-esMUCeenEONvb-bucdqTx8Bb1wngzalAsQau4hkmQWuZfz9HxkVH2utbNtBXbPCx7k8WXOspGvwfI-SV3GgGIaWkf1ggyz7-HJiVLI6fFKoH3Fo8s/s1600/wrs-comparison.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img alt="Comparison between the rendering of a JS-powered website in the old and new Googlebot" border="0" data-original-height="800" data-original-width="1600" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhKTeQjcclgL-R4Yg6BME-esMUCeenEONvb-bucdqTx8Bb1wngzalAsQau4hkmQWuZfz9HxkVH2utbNtBXbPCx7k8WXOspGvwfI-SV3GgGIaWkf1ggyz7-HJiVLI6fFKoH3Fo8s/s640/wrs-comparison.png" title="" width="640" /></a></td></tr> <tr><td class="tr-caption" style="text-align: center;">A JavaScript-powered demo website staying blank in the old Googlebot but working fine in the new Googlebot.</td></tr> </tbody></table> <h3 style="text-align: left;"> What this means for your websites</h3> We are very happy to bring the latest features of the web platform not only to Googlebot but to the tools that let you see what Googlebot sees as well. This means websites using ES6+, Web Components and <a href="https://chromereleases.googleblog.com/">1000+ new web platform features</a> are now rendered with the latest stable Chromium, both in Googlebot and our testing tools.<br /> <table cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody> <tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgeComtJVJKvd38CoFfHKz1hpU308gKNJjAsjwR-MaxdOA9Any-47vEy8y6CpaCHJeEYLaWn2D-J-tURtUOCdSYW-Bww7b4iKcKZjiyj55yr6NnHQq7NgATL70z7wMxYVuS_sAQ/s1600/mft-comparison.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img alt="A comparison showing the old and the new mobile-friendly test. The old mobile-friendly test rendered a blank page and the new one renders the page correctly" border="0" data-original-height="315" data-original-width="1024" height="193" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgeComtJVJKvd38CoFfHKz1hpU308gKNJjAsjwR-MaxdOA9Any-47vEy8y6CpaCHJeEYLaWn2D-J-tURtUOCdSYW-Bww7b4iKcKZjiyj55yr6NnHQq7NgATL70z7wMxYVuS_sAQ/s640/mft-comparison.png" title="" width="640" /></a></td></tr> <tr><td class="tr-caption" style="text-align: center;"><span id="docs-internal-guid-d6ec87e8-7fff-8e15-e97e-c3fd046f0639"><span style="font-size: 11pt; vertical-align: baseline; white-space: pre-wrap;">While the previous version of the mobile-friendly test doesn't show the page content, the new version does.</span></span></td></tr> </tbody></table> <h3 style="text-align: left;"> What the update changes in our testing tools</h3> Our testing tools reflect how Googlebot processes your pages as closely as possible. With the update to the new Googlebot, we had to update them to use the same renderer as Googlebot.<br /> <br /> The change will affect the rendering within the following tools:<br /> <ul style="text-align: left;"> <li><a href="https://g.co/searchconsole">Search Console</a>'s URL inspection tool </li> <li><a href="https://g.co/mobile-friendly">Mobile-friendly test</a></li> <li><a href="https://search.google.com/test/rich-results">Rich results test</a></li> <li><a href="https://search.google.com/test/amp">AMP test</a></li> </ul> We tested these updates and based on the feedback we have switched the tools listed previously to the new evergreen Googlebot. A lot of the feedback came from Googlers and the community. <a href="https://productexperts.withgoogle.com/">Product Experts</a> and <a href="https://developers.google.com/community/experts/">Google Developer Experts</a> helped us make sure the update works well.<br /> <br /> Note: The new Googlebot still uses the same <a href="https://support.google.com/webmasters/answer/1061943?hl=en">user agent</a> as before the update. There will be more information about an update to the user agent in the near future. For now, Googlebot's user agent and the user agent used in the testing tools does not change.<br /> <br /> We are excited about this update and are looking forward to your feedback and questions on <a href="https://twitter.com/googlewmc">Twitter</a>, the <a href="https://support.google.com/webmasters/community?hl=en">webmaster forum</a> or in our <a href="//google.com/webmasters/connect">webmaster office hours</a>.<br /> <br /> <span class="byline-author">Posted by Zoe Clifford, Software Engineer in the Web Rendering Service team & Martin Splitt, friendly internet fairy at Google WTA</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <div style="text-align: left;"> Today we updated most of <a href="https://developers.google.com/search/tools/">our testing tools</a> so they are using the evergreen Chromium renderer. This affects our testing tools like the mobile-friendly test or the URL inspection tool in Search Console. In this post we look into what this means and what went into making this update happen.<br /> <br /></div> <h3 style="text-align: left;"> The evergreen Chromium renderer</h3> At Google I/O this year we were happy to announce <a href="https://www.youtube.com/watch/ufcijo46LCU?t=10m43s">the new evergreen Googlebot</a>.<br /> <br /> At its core the update is a switch from Chrome 41 as the rendering engine to the latest stable Chromium. Googlebot is now using the latest stable Chromium to run JavaScript and render pages. We will continue to update Googlebot along with the stable Chromium, hence we call it "evergreen".<br /> <br /> <table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody> <tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhKTeQjcclgL-R4Yg6BME-esMUCeenEONvb-bucdqTx8Bb1wngzalAsQau4hkmQWuZfz9HxkVH2utbNtBXbPCx7k8WXOspGvwfI-SV3GgGIaWkf1ggyz7-HJiVLI6fFKoH3Fo8s/s1600/wrs-comparison.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img alt="Comparison between the rendering of a JS-powered website in the old and new Googlebot" border="0" data-original-height="800" data-original-width="1600" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhKTeQjcclgL-R4Yg6BME-esMUCeenEONvb-bucdqTx8Bb1wngzalAsQau4hkmQWuZfz9HxkVH2utbNtBXbPCx7k8WXOspGvwfI-SV3GgGIaWkf1ggyz7-HJiVLI6fFKoH3Fo8s/s640/wrs-comparison.png" title="" width="640" /></a></td></tr> <tr><td class="tr-caption" style="text-align: center;">A JavaScript-powered demo website staying blank in the old Googlebot but working fine in the new Googlebot.</td></tr> </tbody></table> <h3 style="text-align: left;"> What this means for your websites</h3> We are very happy to bring the latest features of the web platform not only to Googlebot but to the tools that let you see what Googlebot sees as well. This means websites using ES6+, Web Components and <a href="https://chromereleases.googleblog.com/">1000+ new web platform features</a> are now rendered with the latest stable Chromium, both in Googlebot and our testing tools.<br /> <table cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody> <tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgeComtJVJKvd38CoFfHKz1hpU308gKNJjAsjwR-MaxdOA9Any-47vEy8y6CpaCHJeEYLaWn2D-J-tURtUOCdSYW-Bww7b4iKcKZjiyj55yr6NnHQq7NgATL70z7wMxYVuS_sAQ/s1600/mft-comparison.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img alt="A comparison showing the old and the new mobile-friendly test. The old mobile-friendly test rendered a blank page and the new one renders the page correctly" border="0" data-original-height="315" data-original-width="1024" height="193" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgeComtJVJKvd38CoFfHKz1hpU308gKNJjAsjwR-MaxdOA9Any-47vEy8y6CpaCHJeEYLaWn2D-J-tURtUOCdSYW-Bww7b4iKcKZjiyj55yr6NnHQq7NgATL70z7wMxYVuS_sAQ/s640/mft-comparison.png" title="" width="640" /></a></td></tr> <tr><td class="tr-caption" style="text-align: center;"><span id="docs-internal-guid-d6ec87e8-7fff-8e15-e97e-c3fd046f0639"><span style="font-size: 11pt; vertical-align: baseline; white-space: pre-wrap;">While the previous version of the mobile-friendly test doesn't show the page content, the new version does.</span></span></td></tr> </tbody></table> <h3 style="text-align: left;"> What the update changes in our testing tools</h3> Our testing tools reflect how Googlebot processes your pages as closely as possible. With the update to the new Googlebot, we had to update them to use the same renderer as Googlebot.<br /> <br /> The change will affect the rendering within the following tools:<br /> <ul style="text-align: left;"> <li><a href="https://g.co/searchconsole">Search Console</a>'s URL inspection tool </li> <li><a href="https://g.co/mobile-friendly">Mobile-friendly test</a></li> <li><a href="https://search.google.com/test/rich-results">Rich results test</a></li> <li><a href="https://search.google.com/test/amp">AMP test</a></li> </ul> We tested these updates and based on the feedback we have switched the tools listed previously to the new evergreen Googlebot. A lot of the feedback came from Googlers and the community. <a href="https://productexperts.withgoogle.com/">Product Experts</a> and <a href="https://developers.google.com/community/experts/">Google Developer Experts</a> helped us make sure the update works well.<br /> <br /> Note: The new Googlebot still uses the same <a href="https://support.google.com/webmasters/answer/1061943?hl=en">user agent</a> as before the update. There will be more information about an update to the user agent in the near future. For now, Googlebot's user agent and the user agent used in the testing tools does not change.<br /> <br /> We are excited about this update and are looking forward to your feedback and questions on <a href="https://twitter.com/googlewmc">Twitter</a>, the <a href="https://support.google.com/webmasters/community?hl=en">webmaster forum</a> or in our <a href="//google.com/webmasters/connect">webmaster office hours</a>.<br /> <br /> <span class="byline-author">Posted by Zoe Clifford, Software Engineer in the Web Rendering Service team & Martin Splitt, friendly internet fairy at Google WTA</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Googlebot evergreen rendering in our testing tools&url=https://webmasters.googleblog.com/2019/08/evergreen-googlebot-in-testing-tools.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2019/08/evergreen-googlebot-in-testing-tools.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2019/08/evergreen-googlebot-in-testing-tools.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/javascript?hl=en_US' rel='tag'> javascript </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US' rel='tag'> mobile-friendly </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/rendering?hl=en_US' rel='tag'> rendering </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='8373544720210697535' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/05/search-at-google-io-2019.html?hl=en_US' itemprop='url' title='Search at Google I/O 2019'> Search at Google I/O 2019 </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, May 16, 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"> <a href="https://events.google.com/io/">Google I/O</a> is our yearly developer conference where we have the pleasure of announcing some exciting new Search-related features and capabilities. A good place to start is Google Search: State of the Union, which explains how to take advantage of the latest capabilities in Google Search: <br /> <iframe allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" frameborder="0" height="315" src="https://www.youtube.com/embed/ufcijo46LCU" width="560"></iframe> <br /> We also gave more details on how JavaScript and Google Search work together and what you can do to make sure your JavaScript site performs well in Search. <br /> <iframe allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" frameborder="0" height="315" src="https://www.youtube.com/embed/Ey0N1Ry0BPM" width="560"></iframe> <br /> <h2> Try out new features today</h2> Here are some of the new features, codelabs, and documentation that you can try out today: <br /> <ul> <li><strong>Googlebot now runs the latest Chromium rendering engine</strong>: This means Googebot now supports new features, like ES6, IntersectionObserver for lazy-loading, and Web Components v1 APIs. Googlebot will regularly update it's rendering engine. Learn more about the update in our <a href="https://youtu.be/ufcijo46LCU?t=640">Google Search and JavaScript talk</a>, <a href="https://webmasters.googleblog.com/2019/05/the-new-evergreen-googlebot.html">blog post</a>, and updated our guidance on how to <a href="https://developers.google.com/search/docs/guides/fix-search-javascript">fix JavaScript issues for Google Search</a>. </li> <li><strong>How-to & FAQ launched on Google Search and the Assistant</strong>: You can get started today by following the developer documentation: <a href="https://developers.google.com/search/docs/data-types/how-to">How-to</a> and <a href="https://developers.google.com/search/docs/data-types/faqpage">FAQ</a>. We also launched supporting <a href="https://support.google.com/webmasters/answer/7552505?hl=en">Search Console reports</a>. Learn more about How-to and FAQ in our <a href="https://youtu.be/GR1j2ADyGvA?t=399">structured data talk</a>. </li> <li><strong>Find and listen to podcasts in Search</strong>: Last week, we launched the ability to listen to podcasts directly on Google Search when you search for a certain show. In the coming months, we'll start surfacing podcasts in search results based on the content of the podcast, and let users save episodes for listening later. To enable your podcast in Search, follow the <a href="https://developers.google.com/search/docs/data-types/podcast">Podcast developer documentation</a>. </li> <li><strong>Try our new codelabs</strong>: Check out our new codelabs about how to <a href="https://codelabs.developers.google.com/codelabs/structured-data/index.html#0">add structured data</a>, <a href="https://codelabs.developers.google.com/codelabs/making-a-single-page-app-search-friendly/index.html#0">fix a Single Page App for Search</a>, and implement <a href="https://codelabs.developers.google.com/codelabs/dynamic-rendering/index.html#0">Dynamic Rendering with Rendertron</a>.</li> </ul> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWeXS03r_T5_Wj7VdzKz72yK3YnOKUHYAeqFuZAAJB2wJqEhDlVP9siM7AH1vBTb_K3oO_a29La8L6z3GYua-kBx11ZmDy87wFwVVTiJChMjUgUSq5McKaTNosobfZ0hpcXMqM/s1600/google-io-shoreline-sign.jpg" imageanchor="1"><img alt="The Google I/O sign at Shoreline Amphitheatre at Mountain View, CA" border="0" data-original-height="1256" data-original-width="1600" height="502" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWeXS03r_T5_Wj7VdzKz72yK3YnOKUHYAeqFuZAAJB2wJqEhDlVP9siM7AH1vBTb_K3oO_a29La8L6z3GYua-kBx11ZmDy87wFwVVTiJChMjUgUSq5McKaTNosobfZ0hpcXMqM/s640/google-io-shoreline-sign.jpg" width="640" /></a></div> <div class="separator" style="clear: both; text-align: center;"> <br /></div> <h2> Be among the first to test new features</h2> Your help is invaluable to making sure our products work for everyone. We shared some new features that we're still testing and would love your feedback and participation. <br /> <ul> <li><strong>Speed report</strong>: We're currently piloting the new Speed report in Search Console. <a href="https://docs.google.com/forms/d/e/1FAIpQLSfCpmZbF7t0lZbyXuc6rsB8CiB3ySifqe4Vn-58A9pCbFTGfw/viewform">Sign up to be a beta tester</a>. </li> <li><strong>Mini-apps</strong>: <a href="https://www.youtube.com/watch?v=0Hyt7gjHYO4">We announced Mini-apps</a>, which engage users with interactive workflows and live content directly on Search and the Assistant. <a href="https://docs.google.com/forms/d/e/1FAIpQLScVL3nlBtruZv0aE0V_lf0Y9obrb-Uh8yhHxYrZO_eAU_Owsg/viewform">Submit your idea</a> for the Mini-app Early Adopters Program.</li> </ul> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjrBQ6InZBuf9wMPuJTTXcFkYV_Sm9BUMwVTjFr2ieGXNKp_jWulkqg7RVzM-s-ABnZd9EWcmUElIJ54wI5-gpDzCVR2LeBVy5oaLxU-URwzwPtCNYUDoyS67T8mWQZhsG5p8bd/s1600/IO_19_Tues_Afternoon_3804.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="A large crowd at Google I/O" border="0" data-original-height="1068" data-original-width="1600" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjrBQ6InZBuf9wMPuJTTXcFkYV_Sm9BUMwVTjFr2ieGXNKp_jWulkqg7RVzM-s-ABnZd9EWcmUElIJ54wI5-gpDzCVR2LeBVy5oaLxU-URwzwPtCNYUDoyS67T8mWQZhsG5p8bd/s640/IO_19_Tues_Afternoon_3804.jpg" width="640" /></a></div> <h2> Learn more about what's coming soon</h2> I/O is a place where we get to showcase new Search features, so we're excited to give you a heads up on what's next on the horizon: <br /> <ul> <li><strong>High-resolution images</strong>: In the future, you'll be able to <a href="https://youtu.be/ufcijo46LCU?t=1528">opt in to highlight your high-resolution images</a> for your users. Stay tuned for details. </li> <li><strong>3D and AR in Search</strong>: We are working with partners to bring 3D models and AR content to Google Search. <a href="https://youtu.be/ufcijo46LCU?t=1728">Check out what it might look like</a> and stay tuned for more details.</li> </ul> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg-6CRpawmJqT6DIL8qYnpF1EAaTpM8RiHgrGO1A8r3IDwPmeFK-WxFkQknyax9peB8S8Hvuw9A44Lh4QIp64hr9OLhmmIj7bPMcTqbYK_Ih-WD-fCnCDgdZQ08nK8GkfalhuVa/s1600/google-io-heart.gif" imageanchor="1"><img alt="Two people posing for a photo at Google I/O, forming a heart with their arms" border="0" data-original-height="480" data-original-width="640" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg-6CRpawmJqT6DIL8qYnpF1EAaTpM8RiHgrGO1A8r3IDwPmeFK-WxFkQknyax9peB8S8Hvuw9A44Lh4QIp64hr9OLhmmIj7bPMcTqbYK_Ih-WD-fCnCDgdZQ08nK8GkfalhuVa/s640/google-io-heart.gif" width="640" /></a></div> <br /> We hope these cool announcements help & inspire you to create even better websites that work well in Search. Should you have any questions, feel free to post in our <a href="https://support.google.com/webmasters/go/community">webmaster help forums</a>, <a href="https://twitter.com/googlewmc">contact us on Twitter</a>, or reach out to us at any of the <a href="https://www.google.com/webmasters/connect/">next events we're at</a>. <br /> <br /> <span class="byline-author">Posted by <a href="https://twitter.com/LizziHarvey">Lizzi Harvey</a>, Technical Writer</span> </div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <a href="https://events.google.com/io/">Google I/O</a> is our yearly developer conference where we have the pleasure of announcing some exciting new Search-related features and capabilities. A good place to start is Google Search: State of the Union, which explains how to take advantage of the latest capabilities in Google Search: <br /> <iframe allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" frameborder="0" height="315" src="https://www.youtube.com/embed/ufcijo46LCU" width="560"></iframe> <br /> We also gave more details on how JavaScript and Google Search work together and what you can do to make sure your JavaScript site performs well in Search. <br /> <iframe allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" frameborder="0" height="315" src="https://www.youtube.com/embed/Ey0N1Ry0BPM" width="560"></iframe> <br /> <h2> Try out new features today</h2> Here are some of the new features, codelabs, and documentation that you can try out today: <br /> <ul> <li><strong>Googlebot now runs the latest Chromium rendering engine</strong>: This means Googebot now supports new features, like ES6, IntersectionObserver for lazy-loading, and Web Components v1 APIs. Googlebot will regularly update it's rendering engine. Learn more about the update in our <a href="https://youtu.be/ufcijo46LCU?t=640">Google Search and JavaScript talk</a>, <a href="https://webmasters.googleblog.com/2019/05/the-new-evergreen-googlebot.html">blog post</a>, and updated our guidance on how to <a href="https://developers.google.com/search/docs/guides/fix-search-javascript">fix JavaScript issues for Google Search</a>. </li> <li><strong>How-to & FAQ launched on Google Search and the Assistant</strong>: You can get started today by following the developer documentation: <a href="https://developers.google.com/search/docs/data-types/how-to">How-to</a> and <a href="https://developers.google.com/search/docs/data-types/faqpage">FAQ</a>. We also launched supporting <a href="https://support.google.com/webmasters/answer/7552505?hl=en">Search Console reports</a>. Learn more about How-to and FAQ in our <a href="https://youtu.be/GR1j2ADyGvA?t=399">structured data talk</a>. </li> <li><strong>Find and listen to podcasts in Search</strong>: Last week, we launched the ability to listen to podcasts directly on Google Search when you search for a certain show. In the coming months, we'll start surfacing podcasts in search results based on the content of the podcast, and let users save episodes for listening later. To enable your podcast in Search, follow the <a href="https://developers.google.com/search/docs/data-types/podcast">Podcast developer documentation</a>. </li> <li><strong>Try our new codelabs</strong>: Check out our new codelabs about how to <a href="https://codelabs.developers.google.com/codelabs/structured-data/index.html#0">add structured data</a>, <a href="https://codelabs.developers.google.com/codelabs/making-a-single-page-app-search-friendly/index.html#0">fix a Single Page App for Search</a>, and implement <a href="https://codelabs.developers.google.com/codelabs/dynamic-rendering/index.html#0">Dynamic Rendering with Rendertron</a>.</li> </ul> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWeXS03r_T5_Wj7VdzKz72yK3YnOKUHYAeqFuZAAJB2wJqEhDlVP9siM7AH1vBTb_K3oO_a29La8L6z3GYua-kBx11ZmDy87wFwVVTiJChMjUgUSq5McKaTNosobfZ0hpcXMqM/s1600/google-io-shoreline-sign.jpg" imageanchor="1"><img alt="The Google I/O sign at Shoreline Amphitheatre at Mountain View, CA" border="0" data-original-height="1256" data-original-width="1600" height="502" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWeXS03r_T5_Wj7VdzKz72yK3YnOKUHYAeqFuZAAJB2wJqEhDlVP9siM7AH1vBTb_K3oO_a29La8L6z3GYua-kBx11ZmDy87wFwVVTiJChMjUgUSq5McKaTNosobfZ0hpcXMqM/s640/google-io-shoreline-sign.jpg" width="640" /></a></div> <div class="separator" style="clear: both; text-align: center;"> <br /></div> <h2> Be among the first to test new features</h2> Your help is invaluable to making sure our products work for everyone. We shared some new features that we're still testing and would love your feedback and participation. <br /> <ul> <li><strong>Speed report</strong>: We're currently piloting the new Speed report in Search Console. <a href="https://docs.google.com/forms/d/e/1FAIpQLSfCpmZbF7t0lZbyXuc6rsB8CiB3ySifqe4Vn-58A9pCbFTGfw/viewform">Sign up to be a beta tester</a>. </li> <li><strong>Mini-apps</strong>: <a href="https://www.youtube.com/watch?v=0Hyt7gjHYO4">We announced Mini-apps</a>, which engage users with interactive workflows and live content directly on Search and the Assistant. <a href="https://docs.google.com/forms/d/e/1FAIpQLScVL3nlBtruZv0aE0V_lf0Y9obrb-Uh8yhHxYrZO_eAU_Owsg/viewform">Submit your idea</a> for the Mini-app Early Adopters Program.</li> </ul> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjrBQ6InZBuf9wMPuJTTXcFkYV_Sm9BUMwVTjFr2ieGXNKp_jWulkqg7RVzM-s-ABnZd9EWcmUElIJ54wI5-gpDzCVR2LeBVy5oaLxU-URwzwPtCNYUDoyS67T8mWQZhsG5p8bd/s1600/IO_19_Tues_Afternoon_3804.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="A large crowd at Google I/O" border="0" data-original-height="1068" data-original-width="1600" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjrBQ6InZBuf9wMPuJTTXcFkYV_Sm9BUMwVTjFr2ieGXNKp_jWulkqg7RVzM-s-ABnZd9EWcmUElIJ54wI5-gpDzCVR2LeBVy5oaLxU-URwzwPtCNYUDoyS67T8mWQZhsG5p8bd/s640/IO_19_Tues_Afternoon_3804.jpg" width="640" /></a></div> <h2> Learn more about what's coming soon</h2> I/O is a place where we get to showcase new Search features, so we're excited to give you a heads up on what's next on the horizon: <br /> <ul> <li><strong>High-resolution images</strong>: In the future, you'll be able to <a href="https://youtu.be/ufcijo46LCU?t=1528">opt in to highlight your high-resolution images</a> for your users. Stay tuned for details. </li> <li><strong>3D and AR in Search</strong>: We are working with partners to bring 3D models and AR content to Google Search. <a href="https://youtu.be/ufcijo46LCU?t=1728">Check out what it might look like</a> and stay tuned for more details.</li> </ul> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg-6CRpawmJqT6DIL8qYnpF1EAaTpM8RiHgrGO1A8r3IDwPmeFK-WxFkQknyax9peB8S8Hvuw9A44Lh4QIp64hr9OLhmmIj7bPMcTqbYK_Ih-WD-fCnCDgdZQ08nK8GkfalhuVa/s1600/google-io-heart.gif" imageanchor="1"><img alt="Two people posing for a photo at Google I/O, forming a heart with their arms" border="0" data-original-height="480" data-original-width="640" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg-6CRpawmJqT6DIL8qYnpF1EAaTpM8RiHgrGO1A8r3IDwPmeFK-WxFkQknyax9peB8S8Hvuw9A44Lh4QIp64hr9OLhmmIj7bPMcTqbYK_Ih-WD-fCnCDgdZQ08nK8GkfalhuVa/s640/google-io-heart.gif" width="640" /></a></div> <br /> We hope these cool announcements help & inspire you to create even better websites that work well in Search. Should you have any questions, feel free to post in our <a href="https://support.google.com/webmasters/go/community">webmaster help forums</a>, <a href="https://twitter.com/googlewmc">contact us on Twitter</a>, or reach out to us at any of the <a href="https://www.google.com/webmasters/connect/">next events we're at</a>. <br /> <br /> <span class="byline-author">Posted by <a href="https://twitter.com/LizziHarvey">Lizzi Harvey</a>, Technical Writer</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:Search at Google I/O 2019&url=https://webmasters.googleblog.com/2019/05/search-at-google-io-2019.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2019/05/search-at-google-io-2019.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2019/05/search-at-google-io-2019.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/Google%20Assistant?hl=en_US' rel='tag'> Google Assistant </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/Google%20I%2FO?hl=en_US' rel='tag'> Google I/O </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/Google%20Images?hl=en_US' rel='tag'> Google Images </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/javascript?hl=en_US' rel='tag'> javascript </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/rich%20results?hl=en_US' rel='tag'> rich results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> </span> </div> </div> </div> <div class='post' data-id='528055121435577411' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/04/search-console-reporting-for-your-sites.html?hl=en_US' itemprop='url' title='Search Console reporting for your site's Discover performance data'> Search Console reporting for your site's Discover performance data </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, April 10, 2019 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p>Discover is a popular way for users to stay up-to-date on all their favorite topics, even when they’re not searching. To provide publishers and sites visibility into their Discover traffic, we're adding a new report in Google Search Console to share relevant statistics and help answer questions such as: </p> <ul><li>How often is my site shown in users' Discover? How large is my traffic?</li> <li>Which pieces of content perform well in Discover?</li> <li>How does my content perform differently in Discover compared to traditional search results?</li></ul> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh-1YvsZ_nSc4lbLLZXhv9LE8S5BC5zTDhy65C2dahljhntQ88HsNgVsn-W0XwOOIJhrWsiAtCF74Pdz6qKYlOvNlX4soJb4Q3k7t_qD9XxZga7d7cIM7X3x95gdULhl0LfgN9D/s1600/discover.gif" imageanchor="1" ><img border="0" data-original-height="859" data-original-width="426" height="573" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh-1YvsZ_nSc4lbLLZXhv9LE8S5BC5zTDhy65C2dahljhntQ88HsNgVsn-W0XwOOIJhrWsiAtCF74Pdz6qKYlOvNlX4soJb4Q3k7t_qD9XxZga7d7cIM7X3x95gdULhl0LfgN9D/s573/discover.gif" width="284" /></a> <h3>A quick reminder: What is Discover?</h3> <p>Discover is a feature within Google Search that helps users stay up-to-date on all their favorite topics, without needing a query. Users get to their Discover experience in the Google app, on the Google.com mobile homepage, and by swiping right from the homescreen on Pixel phones. It has grown significantly since launching in 2017 and now helps more than <a href="https://www.blog.google/products/search/introducing-google-discover/">800M monthly active</a> users get inspired and explore new information by surfacing articles, videos, and other content on topics they care most about. Users have the ability to follow topics directly or let Google know if they’d like to see more or less of a specific topic. In addition, Discover isn’t limited to what’s new. It surfaces the best of the web regardless of publication date, from recipes and human interest stories, to fashion videos and more. Here is our <a href="https://support.google.com/webmasters/answer/9046777">guide</a> on how you can optimize your site for Discover.</p> <h3>Discover in Search Console</h3> <p>The new Discover report is shown to websites that have accumulated meaningful visibility in Discover, with the data shown back to March 2019. We hope this report is helpful in thinking about how you might optimize your content strategy to help users discover engaging information-- both new and evergreen.</p> <p>For questions or comments on the report, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">webmaster help forums</a>, or contact us through <a href="https://www.google.com/webmasters/connect/">our other channels</a>.</p> <span class="byline-author">Posted by Michael Huzman, Ariel Kroszynski</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p>Discover is a popular way for users to stay up-to-date on all their favorite topics, even when they’re not searching. To provide publishers and sites visibility into their Discover traffic, we're adding a new report in Google Search Console to share relevant statistics and help answer questions such as: </p> <ul><li>How often is my site shown in users' Discover? How large is my traffic?</li> <li>Which pieces of content perform well in Discover?</li> <li>How does my content perform differently in Discover compared to traditional search results?</li></ul> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh-1YvsZ_nSc4lbLLZXhv9LE8S5BC5zTDhy65C2dahljhntQ88HsNgVsn-W0XwOOIJhrWsiAtCF74Pdz6qKYlOvNlX4soJb4Q3k7t_qD9XxZga7d7cIM7X3x95gdULhl0LfgN9D/s1600/discover.gif" imageanchor="1" ><img border="0" data-original-height="859" data-original-width="426" height="573" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh-1YvsZ_nSc4lbLLZXhv9LE8S5BC5zTDhy65C2dahljhntQ88HsNgVsn-W0XwOOIJhrWsiAtCF74Pdz6qKYlOvNlX4soJb4Q3k7t_qD9XxZga7d7cIM7X3x95gdULhl0LfgN9D/s573/discover.gif" width="284" /></a> <h3>A quick reminder: What is Discover?</h3> <p>Discover is a feature within Google Search that helps users stay up-to-date on all their favorite topics, without needing a query. Users get to their Discover experience in the Google app, on the Google.com mobile homepage, and by swiping right from the homescreen on Pixel phones. It has grown significantly since launching in 2017 and now helps more than <a href="https://www.blog.google/products/search/introducing-google-discover/">800M monthly active</a> users get inspired and explore new information by surfacing articles, videos, and other content on topics they care most about. Users have the ability to follow topics directly or let Google know if they’d like to see more or less of a specific topic. In addition, Discover isn’t limited to what’s new. It surfaces the best of the web regardless of publication date, from recipes and human interest stories, to fashion videos and more. Here is our <a href="https://support.google.com/webmasters/answer/9046777">guide</a> on how you can optimize your site for Discover.</p> <h3>Discover in Search Console</h3> <p>The new Discover report is shown to websites that have accumulated meaningful visibility in Discover, with the data shown back to March 2019. We hope this report is helpful in thinking about how you might optimize your content strategy to help users discover engaging information-- both new and evergreen.</p> <p>For questions or comments on the report, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">webmaster help forums</a>, or contact us through <a href="https://www.google.com/webmasters/connect/">our other channels</a>.</p> <span class="byline-author">Posted by Michael Huzman, Ariel Kroszynski</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:Search Console reporting for your site's Discover performance data&url=https://webmasters.googleblog.com/2019/04/search-console-reporting-for-your-sites.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2019/04/search-console-reporting-for-your-sites.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2019/04/search-console-reporting-for-your-sites.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en_US' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='2772770620723261015' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/03/how-to-discover-suggest-google-selected.html?hl=en_US' itemprop='url' title='How to discover & suggest Google-selected canonical URLs for your pages'> How to discover & suggest Google-selected canonical URLs for your pages </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, March 26, 2019 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p>Sometimes a web page can be reached by using more than one URL. In such cases, Google tries to determine the best URL to display in search and to use in other ways. We call this the “canonical URL.” There are ways site owners can help us better determine what should be the canonical URLs for their content.</p> <p>If you suspect we’ve not selected the best canonical URL for your content, you can check by entering your page’s address into the <a href="https://support.google.com/webmasters/answer/9012289">URL Inspection tool</a> within <a href="https://search.google.com/search-console/about">Search Console</a>. It will show you the <a href="https://support.google.com/webmasters/answer/9012289#google-selected-canonical">Google-selected canonical</a>. If you believe there’s a better canonical that should be used, follow the steps on our <a href="https://support.google.com/webmasters/answer/139066">duplicate URLs</a> help page on how to suggest a preferred choice for consideration.</p> <p>Please be aware that if you search using the site: or inurl: commands, you will be shown the domain you specified in those, even if these aren’t the Google-selected canonical. This happens because we’re fulfilling the exact request entered. Behind-the-scenes, we still use the Google-selected canonical, including for when people see pages without using the site: or inurl: commands.</p> <p>We’ve also changed URL Inspection tool so that it will display any Google-selected canonical for a URL, not just those for properties you manage in Search Console. With this change, we’re also retiring the info: command. This was an alternative way of discovering canonicals. It was relatively underused, and URL Inspection tool provides a more comprehensive solution to help publishers with URLs.</p> <br> <span class="byline-author">Posted by <a href="https://twitter.com/johnmu" rel="author next">John Mueller</a>, Google Switzerland</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p>Sometimes a web page can be reached by using more than one URL. In such cases, Google tries to determine the best URL to display in search and to use in other ways. We call this the “canonical URL.” There are ways site owners can help us better determine what should be the canonical URLs for their content.</p> <p>If you suspect we’ve not selected the best canonical URL for your content, you can check by entering your page’s address into the <a href="https://support.google.com/webmasters/answer/9012289">URL Inspection tool</a> within <a href="https://search.google.com/search-console/about">Search Console</a>. It will show you the <a href="https://support.google.com/webmasters/answer/9012289#google-selected-canonical">Google-selected canonical</a>. If you believe there’s a better canonical that should be used, follow the steps on our <a href="https://support.google.com/webmasters/answer/139066">duplicate URLs</a> help page on how to suggest a preferred choice for consideration.</p> <p>Please be aware that if you search using the site: or inurl: commands, you will be shown the domain you specified in those, even if these aren’t the Google-selected canonical. This happens because we’re fulfilling the exact request entered. Behind-the-scenes, we still use the Google-selected canonical, including for when people see pages without using the site: or inurl: commands.</p> <p>We’ve also changed URL Inspection tool so that it will display any Google-selected canonical for a URL, not just those for properties you manage in Search Console. With this change, we’re also retiring the info: command. This was an alternative way of discovering canonicals. It was relatively underused, and URL Inspection tool provides a more comprehensive solution to help publishers with URLs.</p> <br> <span class="byline-author">Posted by <a href="https://twitter.com/johnmu" rel="author next">John Mueller</a>, Google Switzerland</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:How to discover & suggest Google-selected canonical URLs for your pages&url=https://webmasters.googleblog.com/2019/03/how-to-discover-suggest-google-selected.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2019/03/how-to-discover-suggest-google-selected.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2019/03/how-to-discover-suggest-google-selected.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_US' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20queries?hl=en_US' rel='tag'> search queries </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en_US' rel='tag'> search results </a> </span> </div> </div> </div> <div class='post' data-id='6721730806088263388' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/02/announcing-domain-wide-data-in-search.html?hl=en_US' itemprop='url' title='Announcing domain-wide data in Search Console'> Announcing domain-wide data in Search Console </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, February 27, 2019 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p>Google recommends verifying all versions of a website -- http, https, www, and non-www -- in order to get the most comprehensive view of your site in <a href="https://search.google.com/search-console">Google Search Console</a>. Unfortunately, many separate listings can make it hard for webmasters to understand the full picture of how Google “sees” their domain as a whole. To make this easier, today we're announcing "<a href="https://support.google.com/webmasters/answer/34592">domain properties</a>" in Search Console, a way of verifying and seeing the data from Google Search for a whole domain.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjg3OGGs8bkdkuTOnXcd24h-r8J3XR_zxclkc15hoRLPwRSsrCvSFUHTtk0xVDV7yS8NRbuJvoAuUOEoYgVu_tBsswzYeKkp-t__buwlKd7KhBz_3s7T95JckACcAaQo7QhhUY3/s1600/welcome_816.png" imageanchor="1" ><img border="0" data-original-height="836" data-original-width="816" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjg3OGGs8bkdkuTOnXcd24h-r8J3XR_zxclkc15hoRLPwRSsrCvSFUHTtk0xVDV7yS8NRbuJvoAuUOEoYgVu_tBsswzYeKkp-t__buwlKd7KhBz_3s7T95JckACcAaQo7QhhUY3/s400/welcome_816.png" width="390" /></a> <p>Domain properties show data for all URLs under the domain name, including all protocols, subdomains, and paths. They give you a complete view of your website across Search Console, reducing the need to manually combine data. So regardless of whether you use m-dot URLs for mobile pages, or are (finally) getting the <a href="https://support.google.com/webmasters/answer/6073543">migration to HTTPS</a> set up, Search Console will be able to help with a complete view of your site's data with regards to how Google Search sees it. </p> <p> If you already have DNS verification set up, Search Console will automatically create new domain properties for you over the next few weeks, with data over all reports. Otherwise, to add a new domain property, go to the property selector, <a href="https://support.google.com/webmasters/answer/34592">add a new domain property</a>, and use <a href="https://support.google.com/webmasters/answer/9008080">DNS verification</a>.We recommend using domain properties where possible going forward. </p> <p>Domain properties were built based on your feedback; thank you again for everything you've sent our way over the years! We hope this makes it easier to manage your site, and to get a complete overview without having to manually combine data. Should you have any questions, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">help forums</a>, or leave us a <a href="https://twitter.com/googlewmc">comment on Twitter</a>. And as always, you can also use the feedback feature built in to <a href="https://search.google.com/search-console">Search Console</a> as well. </p> <br> <span class="byline-author">Posted by Erez Bixon, Search Console Team</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p>Google recommends verifying all versions of a website -- http, https, www, and non-www -- in order to get the most comprehensive view of your site in <a href="https://search.google.com/search-console">Google Search Console</a>. Unfortunately, many separate listings can make it hard for webmasters to understand the full picture of how Google “sees” their domain as a whole. To make this easier, today we're announcing "<a href="https://support.google.com/webmasters/answer/34592">domain properties</a>" in Search Console, a way of verifying and seeing the data from Google Search for a whole domain.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjg3OGGs8bkdkuTOnXcd24h-r8J3XR_zxclkc15hoRLPwRSsrCvSFUHTtk0xVDV7yS8NRbuJvoAuUOEoYgVu_tBsswzYeKkp-t__buwlKd7KhBz_3s7T95JckACcAaQo7QhhUY3/s1600/welcome_816.png" imageanchor="1" ><img border="0" data-original-height="836" data-original-width="816" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjg3OGGs8bkdkuTOnXcd24h-r8J3XR_zxclkc15hoRLPwRSsrCvSFUHTtk0xVDV7yS8NRbuJvoAuUOEoYgVu_tBsswzYeKkp-t__buwlKd7KhBz_3s7T95JckACcAaQo7QhhUY3/s400/welcome_816.png" width="390" /></a> <p>Domain properties show data for all URLs under the domain name, including all protocols, subdomains, and paths. They give you a complete view of your website across Search Console, reducing the need to manually combine data. So regardless of whether you use m-dot URLs for mobile pages, or are (finally) getting the <a href="https://support.google.com/webmasters/answer/6073543">migration to HTTPS</a> set up, Search Console will be able to help with a complete view of your site's data with regards to how Google Search sees it. </p> <p> If you already have DNS verification set up, Search Console will automatically create new domain properties for you over the next few weeks, with data over all reports. Otherwise, to add a new domain property, go to the property selector, <a href="https://support.google.com/webmasters/answer/34592">add a new domain property</a>, and use <a href="https://support.google.com/webmasters/answer/9008080">DNS verification</a>.We recommend using domain properties where possible going forward. </p> <p>Domain properties were built based on your feedback; thank you again for everything you've sent our way over the years! We hope this makes it easier to manage your site, and to get a complete overview without having to manually combine data. Should you have any questions, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">help forums</a>, or leave us a <a href="https://twitter.com/googlewmc">comment on Twitter</a>. And as always, you can also use the feedback feature built in to <a href="https://search.google.com/search-console">Search Console</a> as well. </p> <br> <span class="byline-author">Posted by Erez Bixon, 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:Announcing domain-wide data in Search Console&url=https://webmasters.googleblog.com/2019/02/announcing-domain-wide-data-in-search.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2019/02/announcing-domain-wide-data-in-search.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2019/02/announcing-domain-wide-data-in-search.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/verification?hl=en_US' rel='tag'> verification </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='631430052124727539' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/02/help-customers-discover-your-products.html?hl=en_US' itemprop='url' title='Help customers discover your products on Google'> Help customers discover your products on Google </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Friday, February 22, 2019 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p>People come to Google to discover new brands and products throughout their shopping journey. On Search and Google Images, shoppers are provided with rich snippets like product description, ratings, and price to help guide purchase decisions.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgyHI-9vk31tpK1GI-YtqJYERzw4AnBkazDh8x6388e6ee4_5fNnsikXRomSdDHxJUhUmgi6thrnFDeqPq0va9EoaccR_NsnGddkSpzjnn7bv_sK4-uNUzi_2v3-zdKpc_DDft1/s1600/image1.png" imageanchor="1" ><img border="0" data-original-height="540" data-original-width="960" height="225" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgyHI-9vk31tpK1GI-YtqJYERzw4AnBkazDh8x6388e6ee4_5fNnsikXRomSdDHxJUhUmgi6thrnFDeqPq0va9EoaccR_NsnGddkSpzjnn7bv_sK4-uNUzi_2v3-zdKpc_DDft1/s400/image1.png" width="400" /></a> <p>Connecting potential customers with up-to-date and accurate product information is key to successful shopping journeys on Google, so today, we’re introducing new ways for merchants to provide this information to improve results for shoppers.</p> <ol><li><b>Search Console</b> <p>Many retailers and brands add structured data markup to their websites to ensure Google understands the products they sell. A new report for <a href="https://developers.google.com/search/docs/data-types/product">‘Products’</a> is now available in Search Console for sites that use <a href="https://developers.google.com/search/docs/data-types/product">schema.org structured data markup</a> to annotate product information. The report allows you to see any pending issues for markup on your site. Once an issue is fixed, you can use the report to validate if your issues were resolved by re-crawling your affected pages. <a href="https://support.google.com/webmasters/answer/7552505">Learn more about the rich result status reports</a></p></li></ol> <ol start="2"><li><b>Merchant Center</b> <p>While structured data markup helps Google properly display your product information when we crawl your site, we are expanding capabilities for all retailers to directly provide up-to-date product information to Google in real-time. Product data feeds uploaded to <a href="https://www.google.com/retail/solutions/merchant-center/#?modal_active=none">Google Merchant Center</a> will now be eligible for display in results on surfaces like Search and Google Images. This product information will be ranked based only on relevance to users’ queries, and no payment is required or accepted for eligibility. We’re starting with the expansion in the US, and support for other countries will be announced later in the year. </p> <p><b>Get started</b></p> <p>You don’t need a Google Ads campaign to participate. If you don’t have an existing account and sell your products in the US, <a href="http://merchants.google.com">create a Merchant Center account</a> and <a href="https://support.google.com/merchants/answer/9199328">upload a product data feed</a>.</p> </li></ol> <ol start="3"><li><b>Manufacturer Center</b> <p>We’re also rolling out new features to improve your brand’s visibility and help customers find your products on Google by providing authoritative and up-to-date product information through <a href="https://www.google.com/retail/solutions/manufacturer-center/">Google Manufacturer Center</a>. This information includes product description, variants, and rich content, such as high-quality images and videos that can show on the product’s knowledge panel.</p> </li></ol> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjQRipNJMUXgzypAWvWZKJ_zAJalLKNZIQ5X4gx8IG4GG2_CcRqlFEHD1LxuJSL3MV0UHCOte-3IAjxjyTEN7NJB-SxsQ5CVcQcECo5DBUw23SfPT23iMpH9ERiIEkHDOjRQP6F/s1600/image2.png" imageanchor="1" ><img border="0" data-original-height="540" data-original-width="960" height="225" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjQRipNJMUXgzypAWvWZKJ_zAJalLKNZIQ5X4gx8IG4GG2_CcRqlFEHD1LxuJSL3MV0UHCOte-3IAjxjyTEN7NJB-SxsQ5CVcQcECo5DBUw23SfPT23iMpH9ERiIEkHDOjRQP6F/s400/image2.png" width="400" /></a> <p>These solutions give you multiple options to better reach and inform potential customers about your products as they shop across Google. </p> <p>If you have any questions, be sure to post in our <a href="https://support.google.com/webmasters/go/community">forum</a>.</p> <span class="byline-author">Posted by Bernhard Schindlholzer, Product Manager for Google Merchant Tools</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p>People come to Google to discover new brands and products throughout their shopping journey. On Search and Google Images, shoppers are provided with rich snippets like product description, ratings, and price to help guide purchase decisions.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgyHI-9vk31tpK1GI-YtqJYERzw4AnBkazDh8x6388e6ee4_5fNnsikXRomSdDHxJUhUmgi6thrnFDeqPq0va9EoaccR_NsnGddkSpzjnn7bv_sK4-uNUzi_2v3-zdKpc_DDft1/s1600/image1.png" imageanchor="1" ><img border="0" data-original-height="540" data-original-width="960" height="225" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgyHI-9vk31tpK1GI-YtqJYERzw4AnBkazDh8x6388e6ee4_5fNnsikXRomSdDHxJUhUmgi6thrnFDeqPq0va9EoaccR_NsnGddkSpzjnn7bv_sK4-uNUzi_2v3-zdKpc_DDft1/s400/image1.png" width="400" /></a> <p>Connecting potential customers with up-to-date and accurate product information is key to successful shopping journeys on Google, so today, we’re introducing new ways for merchants to provide this information to improve results for shoppers.</p> <ol><li><b>Search Console</b> <p>Many retailers and brands add structured data markup to their websites to ensure Google understands the products they sell. A new report for <a href="https://developers.google.com/search/docs/data-types/product">‘Products’</a> is now available in Search Console for sites that use <a href="https://developers.google.com/search/docs/data-types/product">schema.org structured data markup</a> to annotate product information. The report allows you to see any pending issues for markup on your site. Once an issue is fixed, you can use the report to validate if your issues were resolved by re-crawling your affected pages. <a href="https://support.google.com/webmasters/answer/7552505">Learn more about the rich result status reports</a></p></li></ol> <ol start="2"><li><b>Merchant Center</b> <p>While structured data markup helps Google properly display your product information when we crawl your site, we are expanding capabilities for all retailers to directly provide up-to-date product information to Google in real-time. Product data feeds uploaded to <a href="https://www.google.com/retail/solutions/merchant-center/#?modal_active=none">Google Merchant Center</a> will now be eligible for display in results on surfaces like Search and Google Images. This product information will be ranked based only on relevance to users’ queries, and no payment is required or accepted for eligibility. We’re starting with the expansion in the US, and support for other countries will be announced later in the year. </p> <p><b>Get started</b></p> <p>You don’t need a Google Ads campaign to participate. If you don’t have an existing account and sell your products in the US, <a href="http://merchants.google.com">create a Merchant Center account</a> and <a href="https://support.google.com/merchants/answer/9199328">upload a product data feed</a>.</p> </li></ol> <ol start="3"><li><b>Manufacturer Center</b> <p>We’re also rolling out new features to improve your brand’s visibility and help customers find your products on Google by providing authoritative and up-to-date product information through <a href="https://www.google.com/retail/solutions/manufacturer-center/">Google Manufacturer Center</a>. This information includes product description, variants, and rich content, such as high-quality images and videos that can show on the product’s knowledge panel.</p> </li></ol> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjQRipNJMUXgzypAWvWZKJ_zAJalLKNZIQ5X4gx8IG4GG2_CcRqlFEHD1LxuJSL3MV0UHCOte-3IAjxjyTEN7NJB-SxsQ5CVcQcECo5DBUw23SfPT23iMpH9ERiIEkHDOjRQP6F/s1600/image2.png" imageanchor="1" ><img border="0" data-original-height="540" data-original-width="960" height="225" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjQRipNJMUXgzypAWvWZKJ_zAJalLKNZIQ5X4gx8IG4GG2_CcRqlFEHD1LxuJSL3MV0UHCOte-3IAjxjyTEN7NJB-SxsQ5CVcQcECo5DBUw23SfPT23iMpH9ERiIEkHDOjRQP6F/s400/image2.png" width="400" /></a> <p>These solutions give you multiple options to better reach and inform potential customers about your products as they shop across Google. </p> <p>If you have any questions, be sure to post in our <a href="https://support.google.com/webmasters/go/community">forum</a>.</p> <span class="byline-author">Posted by Bernhard Schindlholzer, Product Manager for Google Merchant Tools</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:Help customers discover your products on Google&url=https://webmasters.googleblog.com/2019/02/help-customers-discover-your-products.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2019/02/help-customers-discover-your-products.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2019/02/help-customers-discover-your-products.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/rich%20results?hl=en_US' rel='tag'> rich results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=en_US' rel='tag'> structured data </a> </span> </div> </div> </div> <div class='post' data-id='2450210226203938986' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/02/consolidating-your-website-traffic-on.html?hl=en_US' itemprop='url' title='Consolidating your website traffic on canonical URLs'> Consolidating your website traffic on canonical URLs </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, February 06, 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>In Search Console, the <a href="https://support.google.com/webmasters/answer/7576553">Performance report</a> currently credits all page metrics to the exact URL that the user is referred to by Google Search. Although this provides very specific data, it makes property management more difficult; for example: if your site has mobile and desktop versions on different properties, you must open multiple properties to see all your Search data for the same piece of content.</p> <p>To help unify your data, Search Console will soon begin assigning search metrics to the (Google-selected) <a href="https://support.google.com/webmasters/answer/139066">canonical URL</a>, rather than the URL referred to by Google Search. This change has several benefits:</p> <ul><li>It unifies all search metrics for a single piece of content into a single URL: the canonical URL. This shows you the full picture about a specific piece of content in one property.</li> <li>For users with separate mobile or AMP pages, it unifies all (or most, since some mobile URLs may end up as canonical) of your data to a single property (the "canonical" property).</li> <li>It improves the usability of the AMP and Mobile-Friendly reports. These reports currently show issues in the canonical page property, but show the impression in the property that owns the actual URL referred to by Google Search. After this change, the impressions and issues will be shown in the same property.</li></ul> <h3>When will this happen?</h3> <p>We plan to transition all performance data on April 10, 2019. In order to provide continuity to your data, we will pre-populate your unified data beginning from January 2018. We will also enable you to view both old and new versions for a few weeks during the transition to see the impact and understand the differences.</p> <p>API and Data Studio users: The <a href="https://developers.google.com/webmaster-tools/search-console-api-original/">Search Console API</a> will change to canonical data on April 10, 2019.</p> <h3>How will this affect my data?</h3> <ul><li>At an individual URL level, you will see traffic shift from any non-canonical (duplicate) URLs to the canonical URL.</li> <li>At the property level, you will see data from your alternate property (for example, your mobile site) shifted to your "canonical property". Your alternate property traffic probably won't drop to zero in Search Console because canonicalization is at the page, not the property level, and your mobile property might have some canonical pages. However, for most users, most property-level data will shift to one property. AMP property traffic will drop to zero in most cases (except for <a href="https://www.ampproject.org/docs/fundamentals/discovery#what-if-i-only-have-one-page?">self-canonical pages</a>).</li> <li>You will still be able to filter data by device, search appearance (such as AMP), country, and other dimensions without losing important information about your traffic.</li></ul> <p>You can see some examples of these traffic changes below.</p> <h3>Preparing for the change</h3> <ul><li>Consider whether you need to change user access to your various properties; for example: do you need to add new users to your canonical property, or do existing users continue to need access to the non-canonical properties.</li> <li>Modify any custom traffic reports you might have created in order to adapt for this traffic shift.</li> <li>If you need to learn the canonical URL for a given URL, you can use the <a href="https://support.google.com/webmasters/answer/9012289">URL Inspection tool</a>.</li> <li>If you want to save your traffic data calculated using the current system, you should download your data using either the Performance report's Export Data button, or using the <a href="https://developers.google.com/webmaster-tools/search-console-api-original/v3/how-tos/all-your-data">Search Console API</a>.</li></ul> <h3>Examples</h3> <p>Here are a few examples showing how data might change on your site. In these examples, you can see how your traffic numbers would change between a canonical site (called example.com) and alternate site (called m.example.com).</p> <p>Important: In these examples, the desktop site contains all the canonical pages and the mobile contains all the alternate pages. In the real world, your desktop site might contain some alternate pages and your mobile site might contain some canonical pages. You can <a href="https://support.google.com/webmasters/answer/9012289#google-selected-canonical">determine the canonical for a given URL using the URL Inspection tool</a>.</p> <p><b>Total traffic</b></p> <p>In the current version, some of your traffic is attributed to the canonical property and some to the alternate property. The new version should attribute all of your traffic to the canonical property.</p> <img border="0" data-original-height="40" data-original-width="428" height="37" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEicspXK0g8t6Sy07QGgtp16NjS4mcjHmr8beYjyXdDtUIpP2xLKlUQ0dbtZFroRFnhW_9TMETjyamBMkdsE4y4G3DuSNZJjzu2mFADbBtMfnMRKrqZqBjXCOLnq1hvlYEZgJyKV/s400/pasted+image+0.png" width="400" /> <table><colgroup><col><col><col></colgroup><tbody><tr><td><br></td><td>Canonical property<br>(http://example.com) </td><td>Alternate property<br>(http://m.example.com) </td></tr> <tr><td>Current </td><td><p><img height="97" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhqL3e4LuAnxgrAaolSXpqmn5tFIsWtx-JzBEvct7Ot9H5ODm_Q-g9PnEVpCBUr6mTgZ06Y-J5MKziF1grCv2ip5qyq-JnZDB67zzl3TyzyELRb9vuV5PZjDnlG8agfqrLxu8vj/s1600/pasted+image+0+%25281%2529.png" width="252"></p> </td><td><p><img height="93" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj86KE5xZE1TJIKvq4dlNzOeC9iqVY3PxYT-Ro0fv0TXw0xJxZlxE20lvayxzizdswL0nuz28ihax2dCa1bBojl35G1MmsUzcrqEgD0inXl2DzMslf_noUgInSQnURTWwT2LdKn/s1600/pasted+image+0+%25282%2529.png" width="247"></p> </td></tr> <tr><td>New, based on canonical URLs </td><td><p><img height="97" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhuwrZrtiAM0gXZUHcxeJznFxYTiVFht-Cx8X6s7BDvsGwR3JVMbgairRW4Uiu5ip4vHMmXOEstfc_-JI_K1yQZfk_So80UnsbuL9pjZt5zXV2B5A_Uzz1huS4Cokq_xIBc2NIM/s1600/pasted+image+0+%25283%2529.png" width="252"></p> </td><td><p><img height="95" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEipgITiQmaZ-eL5ANuvD8EHSp2LzoPoRCPcQC4xRtQgldh4IwUH1pCfSJCuBOzc1DLqkOwobuDJrcNUurj0LI3v4frb-95_UOyeKwN8nGpAXqIHrukzibSlSSlOnMAQAzlUfd4S/s1600/pasted+image+0+%25284%2529.png" width="247"></p> </td></tr> <tr><td>Change </td><td>+0.7K     |        +3K </td><td>-0.7K        |          -3K </td></tr></tbody></table> <p><b>Individual page traffic</b></p> <p>You can see traffic changes between the duplicate and canonical URLs for individual pages in the Pages view. The next example shows how traffic that used to be split between the canonical and alternate pages are now all attributed to the canonical URL:</p> <table><colgroup><col><col><col></colgroup><tbody><tr><td><br></td><td>Canonical property<br>(http://example.com) </td><td>Alternate property<br>(http://m.example.com) </td></tr> <tr><td><p style="white-space: nowrap">Old</p> </td><td><p><img height="43" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhT5Mpg1e8puEl4mJV3EDMPNbD3vUeQ2Mv3dp7-8jaD855kLHjA4of6LRQ25AmM1jRaTGN2CZhKi2Clk1x9ebUeSIHD_tJRMxbjJjHCWA4cTEWT4O1FWEc8r2fIghSwBuQExsfG/s1600/pasted+image+0+%25285%2529.png" width="260"></p> </td><td><p><img height="45" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh31nRHahx3e07bCM7TN2slrRQ7gC_9N44KshWnikiyCyzQpj9n4tGAAxprj9Xk9XHbZTZDESoUs7r__W8Ok2GzU-Ebivj4RO3wh0tDU-sm9IKMANK7DsDS4cQOOChTGQGE_hlI/s1600/pasted+image+0+%25286%2529.png" width="247"></p> </td></tr> <tr><td><p style="white-space: nowrap">New</p> </td><td><p><img height="43" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhU00nurJwEaxLhddEOUBSQ9bJP06qg0m21PVYUCweCG_vqjYOmSSbFX4538Y91vwIVfaE1XI4cbxpYrDWRBEA8CdijnELgT7QfPYpB9Tn4Zi2ur3HOC1umOfX91SzpY0pJyYFj/s1600/pasted+image+0+%25287%2529.png" width="260"></p> </td><td><p><img height="43" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjC4vQiwJvf916FfeRAP7SiQpo5Pec1XgFBrQr3FQgwGPc09eFcmTvsRGA58STCTLYV9O5j2gf_kdWXewtGUWwdlcIy1Fj8AoBrIN6Tw6kdAQL4CVBNHXpcgGMSF03m1sUD_IED/s1600/pasted+image+0+%25288%2529.png" width="247"></p> </td></tr> <tr><td><p style="white-space: nowrap">Change</p> </td><td><p>+150     |        +800</p> </td><td><p>-150     |        -800</p> </td></tr></tbody></table> <p><b>Mobile traffic</b></p> <p>In the current version, all of your mobile traffic was attributed to your m. property. The new version attributes all traffic to your canonical property when you apply the "Device: Mobile" filter as shown here:</p> <table><colgroup><col ><col><col ></colgroup><tbody><tr><td><br></td><td>Canonical property<br>(http://example.com) </td><td>Alternate property<br>(http://m.example.com) </td></tr> <tr><td><p style="white-space: nowrap">Old</p> </td><td><p><img height="97" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgmbT5Z-tORvxWXexpDdRX8jPjqktakdEUvBBXseVBmUNWTc7XZ3ReLC7-fmliy1kL35eg2nGkhy-UmAGGkno3e5uO_wrl0hYimpYww8jIFEYTn6CTo5RMTh1W-uit-1udfUUvw/s1600/pasted+image+0+%25289%2529.png" width="252"></p> </td><td><p><img height="93" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjAvFf9-9tBpQoadrTBoK5B8IPrz32zqhOixJAmFoz7D76LrwdkhqsXZGZn3VcQntlxjLiS3Dnn-YRSQwxNPJZSC11-lA13y2xa1GWtoM4H5Crq0f-h7egDWXzGv363JVDVaMQi/s1600/pasted+image+0+%252810%2529.png" width="247"></p> </td></tr> <tr><td><p style="white-space: nowrap">New</p> </td><td><p><img height="93" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhq6RHelLwEvH0KeNcdA8DRpDXuXzaJ5akoqpgtQUO8jSQ5xonPzslKx5HozHVsw015t-gjCjtlExl1ojrHff9fizvxJRVYvxw1yBaOSsdecj0clWHHXKzWje1RaJRVCQl4XEU1/s1600/pasted+image+0+%252811%2529.png" width="247"></p> </td><td><p><img height="95" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg8ZfMoLzsegA4LOZFTK58SZ072SkhTHcH8ShtH1s8tpBE10JLvHv9ePAuUHxfA4idi__xuorb2weaYXaPDHNiBoO5RY0CpjXVDybNJYSdBhdIKnfnamlmULnoGexgBTYCBYfdX/s1600/pasted+image+0+%252812%2529.png" width="247"></p> </td></tr> <tr><td><p style="white-space: nowrap">Change</p> </td><td><p>+0.7K      | +3K</p> </td><td><p>-0.7K      | -3K</p> </td></tr></tbody></table> <h3>In conclusion</h3> <p>We know that this change might seem a little confusing at first, but we're confident that it will simplify your job of tracking traffic data for your site. If you have any questions or concerns, please reach out on the <a href="https://g.co/webmasterhelpforum">Webmaster Help Forum</a>.</p> <br> <span class="byline-author">Posted by <a href="https://plus.google.com/+johnmueller">John Mueller</a>, Developer Advocate, Zurich</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>In Search Console, the <a href="https://support.google.com/webmasters/answer/7576553">Performance report</a> currently credits all page metrics to the exact URL that the user is referred to by Google Search. Although this provides very specific data, it makes property management more difficult; for example: if your site has mobile and desktop versions on different properties, you must open multiple properties to see all your Search data for the same piece of content.</p> <p>To help unify your data, Search Console will soon begin assigning search metrics to the (Google-selected) <a href="https://support.google.com/webmasters/answer/139066">canonical URL</a>, rather than the URL referred to by Google Search. This change has several benefits:</p> <ul><li>It unifies all search metrics for a single piece of content into a single URL: the canonical URL. This shows you the full picture about a specific piece of content in one property.</li> <li>For users with separate mobile or AMP pages, it unifies all (or most, since some mobile URLs may end up as canonical) of your data to a single property (the "canonical" property).</li> <li>It improves the usability of the AMP and Mobile-Friendly reports. These reports currently show issues in the canonical page property, but show the impression in the property that owns the actual URL referred to by Google Search. After this change, the impressions and issues will be shown in the same property.</li></ul> <h3>When will this happen?</h3> <p>We plan to transition all performance data on April 10, 2019. In order to provide continuity to your data, we will pre-populate your unified data beginning from January 2018. We will also enable you to view both old and new versions for a few weeks during the transition to see the impact and understand the differences.</p> <p>API and Data Studio users: The <a href="https://developers.google.com/webmaster-tools/search-console-api-original/">Search Console API</a> will change to canonical data on April 10, 2019.</p> <h3>How will this affect my data?</h3> <ul><li>At an individual URL level, you will see traffic shift from any non-canonical (duplicate) URLs to the canonical URL.</li> <li>At the property level, you will see data from your alternate property (for example, your mobile site) shifted to your "canonical property". Your alternate property traffic probably won't drop to zero in Search Console because canonicalization is at the page, not the property level, and your mobile property might have some canonical pages. However, for most users, most property-level data will shift to one property. AMP property traffic will drop to zero in most cases (except for <a href="https://www.ampproject.org/docs/fundamentals/discovery#what-if-i-only-have-one-page?">self-canonical pages</a>).</li> <li>You will still be able to filter data by device, search appearance (such as AMP), country, and other dimensions without losing important information about your traffic.</li></ul> <p>You can see some examples of these traffic changes below.</p> <h3>Preparing for the change</h3> <ul><li>Consider whether you need to change user access to your various properties; for example: do you need to add new users to your canonical property, or do existing users continue to need access to the non-canonical properties.</li> <li>Modify any custom traffic reports you might have created in order to adapt for this traffic shift.</li> <li>If you need to learn the canonical URL for a given URL, you can use the <a href="https://support.google.com/webmasters/answer/9012289">URL Inspection tool</a>.</li> <li>If you want to save your traffic data calculated using the current system, you should download your data using either the Performance report's Export Data button, or using the <a href="https://developers.google.com/webmaster-tools/search-console-api-original/v3/how-tos/all-your-data">Search Console API</a>.</li></ul> <h3>Examples</h3> <p>Here are a few examples showing how data might change on your site. In these examples, you can see how your traffic numbers would change between a canonical site (called example.com) and alternate site (called m.example.com).</p> <p>Important: In these examples, the desktop site contains all the canonical pages and the mobile contains all the alternate pages. In the real world, your desktop site might contain some alternate pages and your mobile site might contain some canonical pages. You can <a href="https://support.google.com/webmasters/answer/9012289#google-selected-canonical">determine the canonical for a given URL using the URL Inspection tool</a>.</p> <p><b>Total traffic</b></p> <p>In the current version, some of your traffic is attributed to the canonical property and some to the alternate property. The new version should attribute all of your traffic to the canonical property.</p> <img border="0" data-original-height="40" data-original-width="428" height="37" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEicspXK0g8t6Sy07QGgtp16NjS4mcjHmr8beYjyXdDtUIpP2xLKlUQ0dbtZFroRFnhW_9TMETjyamBMkdsE4y4G3DuSNZJjzu2mFADbBtMfnMRKrqZqBjXCOLnq1hvlYEZgJyKV/s400/pasted+image+0.png" width="400" /> <table><colgroup><col><col><col></colgroup><tbody><tr><td><br></td><td>Canonical property<br>(http://example.com) </td><td>Alternate property<br>(http://m.example.com) </td></tr> <tr><td>Current </td><td><p><img height="97" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhqL3e4LuAnxgrAaolSXpqmn5tFIsWtx-JzBEvct7Ot9H5ODm_Q-g9PnEVpCBUr6mTgZ06Y-J5MKziF1grCv2ip5qyq-JnZDB67zzl3TyzyELRb9vuV5PZjDnlG8agfqrLxu8vj/s1600/pasted+image+0+%25281%2529.png" width="252"></p> </td><td><p><img height="93" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj86KE5xZE1TJIKvq4dlNzOeC9iqVY3PxYT-Ro0fv0TXw0xJxZlxE20lvayxzizdswL0nuz28ihax2dCa1bBojl35G1MmsUzcrqEgD0inXl2DzMslf_noUgInSQnURTWwT2LdKn/s1600/pasted+image+0+%25282%2529.png" width="247"></p> </td></tr> <tr><td>New, based on canonical URLs </td><td><p><img height="97" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhuwrZrtiAM0gXZUHcxeJznFxYTiVFht-Cx8X6s7BDvsGwR3JVMbgairRW4Uiu5ip4vHMmXOEstfc_-JI_K1yQZfk_So80UnsbuL9pjZt5zXV2B5A_Uzz1huS4Cokq_xIBc2NIM/s1600/pasted+image+0+%25283%2529.png" width="252"></p> </td><td><p><img height="95" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEipgITiQmaZ-eL5ANuvD8EHSp2LzoPoRCPcQC4xRtQgldh4IwUH1pCfSJCuBOzc1DLqkOwobuDJrcNUurj0LI3v4frb-95_UOyeKwN8nGpAXqIHrukzibSlSSlOnMAQAzlUfd4S/s1600/pasted+image+0+%25284%2529.png" width="247"></p> </td></tr> <tr><td>Change </td><td>+0.7K     |        +3K </td><td>-0.7K        |          -3K </td></tr></tbody></table> <p><b>Individual page traffic</b></p> <p>You can see traffic changes between the duplicate and canonical URLs for individual pages in the Pages view. The next example shows how traffic that used to be split between the canonical and alternate pages are now all attributed to the canonical URL:</p> <table><colgroup><col><col><col></colgroup><tbody><tr><td><br></td><td>Canonical property<br>(http://example.com) </td><td>Alternate property<br>(http://m.example.com) </td></tr> <tr><td><p style="white-space: nowrap">Old</p> </td><td><p><img height="43" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhT5Mpg1e8puEl4mJV3EDMPNbD3vUeQ2Mv3dp7-8jaD855kLHjA4of6LRQ25AmM1jRaTGN2CZhKi2Clk1x9ebUeSIHD_tJRMxbjJjHCWA4cTEWT4O1FWEc8r2fIghSwBuQExsfG/s1600/pasted+image+0+%25285%2529.png" width="260"></p> </td><td><p><img height="45" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh31nRHahx3e07bCM7TN2slrRQ7gC_9N44KshWnikiyCyzQpj9n4tGAAxprj9Xk9XHbZTZDESoUs7r__W8Ok2GzU-Ebivj4RO3wh0tDU-sm9IKMANK7DsDS4cQOOChTGQGE_hlI/s1600/pasted+image+0+%25286%2529.png" width="247"></p> </td></tr> <tr><td><p style="white-space: nowrap">New</p> </td><td><p><img height="43" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhU00nurJwEaxLhddEOUBSQ9bJP06qg0m21PVYUCweCG_vqjYOmSSbFX4538Y91vwIVfaE1XI4cbxpYrDWRBEA8CdijnELgT7QfPYpB9Tn4Zi2ur3HOC1umOfX91SzpY0pJyYFj/s1600/pasted+image+0+%25287%2529.png" width="260"></p> </td><td><p><img height="43" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjC4vQiwJvf916FfeRAP7SiQpo5Pec1XgFBrQr3FQgwGPc09eFcmTvsRGA58STCTLYV9O5j2gf_kdWXewtGUWwdlcIy1Fj8AoBrIN6Tw6kdAQL4CVBNHXpcgGMSF03m1sUD_IED/s1600/pasted+image+0+%25288%2529.png" width="247"></p> </td></tr> <tr><td><p style="white-space: nowrap">Change</p> </td><td><p>+150     |        +800</p> </td><td><p>-150     |        -800</p> </td></tr></tbody></table> <p><b>Mobile traffic</b></p> <p>In the current version, all of your mobile traffic was attributed to your m. property. The new version attributes all traffic to your canonical property when you apply the "Device: Mobile" filter as shown here:</p> <table><colgroup><col ><col><col ></colgroup><tbody><tr><td><br></td><td>Canonical property<br>(http://example.com) </td><td>Alternate property<br>(http://m.example.com) </td></tr> <tr><td><p style="white-space: nowrap">Old</p> </td><td><p><img height="97" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgmbT5Z-tORvxWXexpDdRX8jPjqktakdEUvBBXseVBmUNWTc7XZ3ReLC7-fmliy1kL35eg2nGkhy-UmAGGkno3e5uO_wrl0hYimpYww8jIFEYTn6CTo5RMTh1W-uit-1udfUUvw/s1600/pasted+image+0+%25289%2529.png" width="252"></p> </td><td><p><img height="93" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjAvFf9-9tBpQoadrTBoK5B8IPrz32zqhOixJAmFoz7D76LrwdkhqsXZGZn3VcQntlxjLiS3Dnn-YRSQwxNPJZSC11-lA13y2xa1GWtoM4H5Crq0f-h7egDWXzGv363JVDVaMQi/s1600/pasted+image+0+%252810%2529.png" width="247"></p> </td></tr> <tr><td><p style="white-space: nowrap">New</p> </td><td><p><img height="93" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhq6RHelLwEvH0KeNcdA8DRpDXuXzaJ5akoqpgtQUO8jSQ5xonPzslKx5HozHVsw015t-gjCjtlExl1ojrHff9fizvxJRVYvxw1yBaOSsdecj0clWHHXKzWje1RaJRVCQl4XEU1/s1600/pasted+image+0+%252811%2529.png" width="247"></p> </td><td><p><img height="95" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg8ZfMoLzsegA4LOZFTK58SZ072SkhTHcH8ShtH1s8tpBE10JLvHv9ePAuUHxfA4idi__xuorb2weaYXaPDHNiBoO5RY0CpjXVDybNJYSdBhdIKnfnamlmULnoGexgBTYCBYfdX/s1600/pasted+image+0+%252812%2529.png" width="247"></p> </td></tr> <tr><td><p style="white-space: nowrap">Change</p> </td><td><p>+0.7K      | +3K</p> </td><td><p>-0.7K      | -3K</p> </td></tr></tbody></table> <h3>In conclusion</h3> <p>We know that this change might seem a little confusing at first, but we're confident that it will simplify your job of tracking traffic data for your site. If you have any questions or concerns, please reach out on the <a href="https://g.co/webmasterhelpforum">Webmaster Help Forum</a>.</p> <br> <span class="byline-author">Posted by <a href="https://plus.google.com/+johnmueller">John Mueller</a>, Developer Advocate, Zurich</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:Consolidating your website traffic on canonical URLs&url=https://webmasters.googleblog.com/2019/02/consolidating-your-website-traffic-on.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2019/02/consolidating-your-website-traffic-on.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2019/02/consolidating-your-website-traffic-on.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/mobile?hl=en_US' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20queries?hl=en_US' rel='tag'> search queries </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='2350991959496997521' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/01/focusing-on-new-search-console.html?hl=en_US' itemprop='url' title='Focusing on the new Search Console'> Focusing on the new Search Console </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Friday, January 25, 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>Over the last year, the <a href="https://support.google.com/webmasters/answer/7451491">new Search Console</a> has been <a href="https://webmasters.googleblog.com/2018/01/introducing-new-search-console.html">growing</a> and <a href="https://webmasters.googleblog.com/2018/09/the-new-search-console-is-graduating.html">growing</a>, with the goal of making it easier for site owners to focus on the important tasks. For us, focus means being able to put in all our work into the new Search Console, being committed to the users, and with that, being able to turn off some of the older, perhaps already-improved, aspects of the old Search Console. This gives us space to further build out the new Search Console, adding and improving features over time.</p> <p>Here are some of the upcoming <a href="https://support.google.com/webmasters/answer/9073702?hl=en">changes in Search Console</a> that we're planning on making towards end of March, 2019:</p> <h3>Crawl errors in the new Index Coverage report</h3> <p>One of the more common pieces of feedback we received was that the list of crawl errors in Search Console was not actionable when it came to setting priorities (it's normal that Google crawls URLs which don't exist, it's not something that needs to be fixed on the website). By changing the focus on issues and patterns used for site indexing, we believe that site owners will be able to find and fix issues much faster (and when issues are fixed, you can request reprocessing quickly too). With this, we're going to remove the old Crawl Errors report - for desktop, smartphone, and site-wide errors. We'll continue to improve the way issues are recognized and flagged, so if there's something that would help you, please submit feedback in the tools.</p> <p>Along with the Crawl Errors report, we're also deprecating the crawl errors API that's based on the same internal systems. At the moment, we don't have a replacement for this API. We'll inform API users of this change directly. </p> <h3>Sitemaps data in Index Coverage</h3> <p>As we move forward with the new Search Console, we're turning the old sitemaps report off. The new sitemaps report has most of the functionality of the old report, and we're aiming to bring the rest of the information - specifically for images & video - to the new reports over time. Moreover, to track URLs submitted in sitemap files, within the Index Coverage report you can select and filter using your sitemap files. This makes it easier to focus on URLs that you care about.</p> <h3>Using the URL inspection tool to fetch as Google</h3> <p>The new <a href="https://support.google.com/webmasters/answer/9012289?hl=en">URL inspection tool</a> offers many ways to check and review URLs on your website. It provides both a look into the current indexing, as well as a live check of URLs that you've recently changed. In the meantime, this tool shows even more information on URLs, such as the HTTP headers, page resource, the JavaScript console log, and a screenshot of the page. From there, you can also submit pages for re-processing, to have them added or updated in our search results as quickly as possible.</p> <h3>User-management is now in settings</h3> <p>We've improved the user management interface and decreased clutter from the tool by merging it with the Settings section of the new Search Console. This replaces the <a href="https://support.google.com/webmasters/answer/2453966?hl=en">user-management features</a> in the old Search Console. </p> <h3>Structured data dashboard to dedicated reports per vertical</h3> <p>To help you implement Rich Results for you site, we added several reports to the new Search Console last year. These include Jobs, Recipes, Events and Q&A. We are committed to keep adding reports like these to the new Search Console. When Google encounters a syntax error parsing Structured Data on a page, it will also be reported in aggregate to make sure you don’t miss anything critical.</p> <p>Other Structured Data types that are not supported with Rich Results features, will not be reported in Search Console anymore. We hope this reduces distraction from non-critical issues, and help you to focus on fixing problems which could be visible in Search. </p> <h3>Letting go of some old features</h3> <p>With the focus on features that we believe are critical to site owners, we've had to make a hard decision to drop some features in Search Console. In particular:</p> <p>HTML suggestions - finding short and duplicated titles can be useful for site owners, but Google's algorithms have gotten <a href="https://support.google.com/webmasters/answer/35624?hl=en">better at showing and improving titles</a> over the years. We still believe this is something useful for sites to look into, and there are some really good tools that help you to <a href="https://www.google.com/search?q=crawl+website+for+titles+and+descriptions">crawl your website to extract titles & descriptions</a> too. </p> <p>Property Sets - while they're loved by some site owners, the small number of users makes it hard to justify maintaining this feature. However, we did learn that users need a more comprehensive view of their website and so we will soon add the option of managing a search console account over an entire domain (regardless of schema type and sub-domains). Stay tuned!</p> <p>Android Apps - most of the relevant functionality has been moved to the <a href="https://console.firebase.google.com/">Firebase console</a> over the years. </p> <p>Blocked resources - we added this functionality to help sites with unblocking of CSS and JavaScript files for mobile-friendliness several years back. In the meantime, these issues have gotten much fewer, the usage of this tool has dropped significantly, and you're able to find blocked resources directly in the <a href="https://support.google.com/webmasters/answer/9012289?hl=en">URL inspection tool</a>.</p> <h3>Please send us feedback!</h3> <p>We realize some of these changes will affect your work-flows, so we want to let you know about them as early as possible. Please send us your feedback directly in the new Search Console, if there are aspects which are unclear, or which would ideally be different for your use-case. For more detailed feedback, please use our <a href="https://support.google.com/webmasters/go/community">help forums</a>, feel free to include screenshots & ideas. In the long run, we believe the new Search Console will make things much easier, help you focus on the issues affecting your site, and the opportunities available to your site, with regards to search. </p> <p>We're looking forward to an exciting year!</p> <br> <span class="byline-author">Posted by Hillel Maoz, Search Console 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>Over the last year, the <a href="https://support.google.com/webmasters/answer/7451491">new Search Console</a> has been <a href="https://webmasters.googleblog.com/2018/01/introducing-new-search-console.html">growing</a> and <a href="https://webmasters.googleblog.com/2018/09/the-new-search-console-is-graduating.html">growing</a>, with the goal of making it easier for site owners to focus on the important tasks. For us, focus means being able to put in all our work into the new Search Console, being committed to the users, and with that, being able to turn off some of the older, perhaps already-improved, aspects of the old Search Console. This gives us space to further build out the new Search Console, adding and improving features over time.</p> <p>Here are some of the upcoming <a href="https://support.google.com/webmasters/answer/9073702?hl=en">changes in Search Console</a> that we're planning on making towards end of March, 2019:</p> <h3>Crawl errors in the new Index Coverage report</h3> <p>One of the more common pieces of feedback we received was that the list of crawl errors in Search Console was not actionable when it came to setting priorities (it's normal that Google crawls URLs which don't exist, it's not something that needs to be fixed on the website). By changing the focus on issues and patterns used for site indexing, we believe that site owners will be able to find and fix issues much faster (and when issues are fixed, you can request reprocessing quickly too). With this, we're going to remove the old Crawl Errors report - for desktop, smartphone, and site-wide errors. We'll continue to improve the way issues are recognized and flagged, so if there's something that would help you, please submit feedback in the tools.</p> <p>Along with the Crawl Errors report, we're also deprecating the crawl errors API that's based on the same internal systems. At the moment, we don't have a replacement for this API. We'll inform API users of this change directly. </p> <h3>Sitemaps data in Index Coverage</h3> <p>As we move forward with the new Search Console, we're turning the old sitemaps report off. The new sitemaps report has most of the functionality of the old report, and we're aiming to bring the rest of the information - specifically for images & video - to the new reports over time. Moreover, to track URLs submitted in sitemap files, within the Index Coverage report you can select and filter using your sitemap files. This makes it easier to focus on URLs that you care about.</p> <h3>Using the URL inspection tool to fetch as Google</h3> <p>The new <a href="https://support.google.com/webmasters/answer/9012289?hl=en">URL inspection tool</a> offers many ways to check and review URLs on your website. It provides both a look into the current indexing, as well as a live check of URLs that you've recently changed. In the meantime, this tool shows even more information on URLs, such as the HTTP headers, page resource, the JavaScript console log, and a screenshot of the page. From there, you can also submit pages for re-processing, to have them added or updated in our search results as quickly as possible.</p> <h3>User-management is now in settings</h3> <p>We've improved the user management interface and decreased clutter from the tool by merging it with the Settings section of the new Search Console. This replaces the <a href="https://support.google.com/webmasters/answer/2453966?hl=en">user-management features</a> in the old Search Console. </p> <h3>Structured data dashboard to dedicated reports per vertical</h3> <p>To help you implement Rich Results for you site, we added several reports to the new Search Console last year. These include Jobs, Recipes, Events and Q&A. We are committed to keep adding reports like these to the new Search Console. When Google encounters a syntax error parsing Structured Data on a page, it will also be reported in aggregate to make sure you don’t miss anything critical.</p> <p>Other Structured Data types that are not supported with Rich Results features, will not be reported in Search Console anymore. We hope this reduces distraction from non-critical issues, and help you to focus on fixing problems which could be visible in Search. </p> <h3>Letting go of some old features</h3> <p>With the focus on features that we believe are critical to site owners, we've had to make a hard decision to drop some features in Search Console. In particular:</p> <p>HTML suggestions - finding short and duplicated titles can be useful for site owners, but Google's algorithms have gotten <a href="https://support.google.com/webmasters/answer/35624?hl=en">better at showing and improving titles</a> over the years. We still believe this is something useful for sites to look into, and there are some really good tools that help you to <a href="https://www.google.com/search?q=crawl+website+for+titles+and+descriptions">crawl your website to extract titles & descriptions</a> too. </p> <p>Property Sets - while they're loved by some site owners, the small number of users makes it hard to justify maintaining this feature. However, we did learn that users need a more comprehensive view of their website and so we will soon add the option of managing a search console account over an entire domain (regardless of schema type and sub-domains). Stay tuned!</p> <p>Android Apps - most of the relevant functionality has been moved to the <a href="https://console.firebase.google.com/">Firebase console</a> over the years. </p> <p>Blocked resources - we added this functionality to help sites with unblocking of CSS and JavaScript files for mobile-friendliness several years back. In the meantime, these issues have gotten much fewer, the usage of this tool has dropped significantly, and you're able to find blocked resources directly in the <a href="https://support.google.com/webmasters/answer/9012289?hl=en">URL inspection tool</a>.</p> <h3>Please send us feedback!</h3> <p>We realize some of these changes will affect your work-flows, so we want to let you know about them as early as possible. Please send us your feedback directly in the new Search Console, if there are aspects which are unclear, or which would ideally be different for your use-case. For more detailed feedback, please use our <a href="https://support.google.com/webmasters/go/community">help forums</a>, feel free to include screenshots & ideas. In the long run, we believe the new Search Console will make things much easier, help you focus on the issues affecting your site, and the opportunities available to your site, with regards to search. </p> <p>We're looking forward to an exciting year!</p> <br> <span class="byline-author">Posted by Hillel Maoz, Search Console 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:Focusing on the new Search Console&url=https://webmasters.googleblog.com/2019/01/focusing-on-new-search-console.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2019/01/focusing-on-new-search-console.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2019/01/focusing-on-new-search-console.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='1425010422692719398' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2018/09/the-new-search-console-is-graduating.html?hl=en_US' itemprop='url' title='The new Search Console is graduating out of Beta 🎓'> The new Search Console is graduating out of Beta 🎓 </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, September 04, 2018 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>Today we mark an important milestone in Search Console’s history: we are graduating the new Search Console out of beta! With this graduation we are also launching the Manual Actions report and a “Test Live” capability to the recently launched URL inspection tool, which are joining a stream of reports and features we launched in the new Search Console over the past few months.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh8HE9sCLX_Y0XiE2Er9zjdf4nuWDXbOvSPShbGDIi4bhxekCFEvt4gaaVEnbYxsWWnNli2rVeG4N3ISqoc4qMJ81y_E0nolSnMekes1T1mmK6abEvHR7YSj2BqhfevrpBH-A5q/s1600/post01.png" imageanchor="1" ><img border="0" data-original-height="800" data-original-width="700" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh8HE9sCLX_Y0XiE2Er9zjdf4nuWDXbOvSPShbGDIi4bhxekCFEvt4gaaVEnbYxsWWnNli2rVeG4N3ISqoc4qMJ81y_E0nolSnMekes1T1mmK6abEvHR7YSj2BqhfevrpBH-A5q/s400/post01.png" width="350" /></a> <h2>Our journey to the new Search Console</h2> <p>We <a href="https://webmasters.googleblog.com/2018/01/introducing-new-search-console.html">launched</a> the <a href="https://search.google.com/search-console">new Search Console</a> at the beginning of the year. Since then we have been busy hearing and responding to your <a href="https://webmasters.googleblog.com/2018/02/how-listening-to-our-users-helped-us.html">feedback</a>, adding new features such as the <a href="https://webmasters.googleblog.com/2018/06/new-url-inspection-tool-more-in-search.html">URL Inspection Tool</a>, and migrating <a href="https://webmasters.googleblog.com/2018/08/links-mobile-usability-and-site.html">key reports and features</a>. Here's what the new Search Console gives you:</p> <p>More data:</p> <ul><li>Get an accurate view of your website content using the <a href="https://support.google.com/webmasters/answer/7440203">Index Coverage report</a>.</li> <li>Review your Search Analytics data going back 16 months in the <a href="https://support.google.com/webmasters/answer/7576553">Performance report</a>.</li> <li>See information on links pointing to your site and within your site using the <a href="https://support.google.com/webmasters/answer/9049606">Links report</a>.</li> <li>Retrieve crawling, indexing, and serving information for any URL directly from the Google index using the <a href="https://support.google.com/webmasters/answer/9012289">URL Inspection Tool</a>.</li></ul> <p>Better alerting and new "fixed it" flows:</p> <ul><li>Get automatic alerts and see a listing of pages affected by Crawling, Indexing, AMP, Mobile Usability, Recipes, or Job posting issues. </li> <li>Reports now show the HTML code where we think a fix necessary (if applicable).</li> <li>Share information quickly with the relevant people in your organization to drive the fix.</li> <li>Notify Google when you've fixed an issue. We will review your pages, validate whether the issue is fixed, and return a <a href="https://support.google.com/webmasters/answer/7440203#validation">detailed log of the validation findings</a>.</li></ul> <p>Simplified sitemaps and account settings management:</p> <ul><li>Let Google know how your site is structured by <a href="https://support.google.com/webmasters/answer/7451001">submitting sitemaps</a></li> <li>Submit individual URLs for indexing (see below).</li> <li>Add new sites to your account, <a href="https://support.google.com/webmasters/answer/7687615">invite and manage users</a>.</li></ul> <h2>Out of Beta</h2> <p>While the old Search Console still has some features that are not yet available in the new one, we believe that the most common use cases are supported, in an improved way, in the new Search Console. When an equivalent feature exists in both old and new Search Console, our messages will point users to the new version. We'll also add a reminder link in the old report. After a reasonable period, we will remove the old report. </p> <p>Read more about how to migrate from old to the new Search Console, including a list of improved reports and how to perform common tasks, <a href="https://support.google.com/webmasters/answer/9073702">in our help center</a>.</p> <h2>Manual Actions and Security Issues alerts</h2> <p>To ensure that you don't miss any critical alerts for your site, active manual actions and security issues will be shown directly on the Overview page in the new console. In addition, the <a href="https://support.google.com/webmasters/answer/9044175">Manual Actions report</a> has gotten a fresher look in the new Search Console. From there, you can review the details for any pending Manual Action and, if needed, <a href="https://support.google.com/webmasters/answer/35843">file a reconsideration request</a>.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhfsmkXFbDMSMiqHRLxmN5z9j3TLgm08fBrdYpZVeGovvr4e7f2GN5req3xF6pgmZtNtS7ZCs9AfBhDp6fqRP-zM406sVcVK8-yQwhE0fW_K6sixEB0OJ23CK-XUifZP0juTfgw/s1600/post02.png" imageanchor="1" ><img border="0" data-original-height="800" data-original-width="700" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhfsmkXFbDMSMiqHRLxmN5z9j3TLgm08fBrdYpZVeGovvr4e7f2GN5req3xF6pgmZtNtS7ZCs9AfBhDp6fqRP-zM406sVcVK8-yQwhE0fW_K6sixEB0OJ23CK-XUifZP0juTfgw/s400/post02.png" width="350" /></a> <h2>URL Inspection - Live mode and request indexing</h2> <p>The <a href="https://webmasters.googleblog.com/2018/06/new-url-inspection-tool-more-in-search.html">URL inspection tool</a> that we launched a few months ago now enables you to run the inspection on the live version of the page. This is useful for debugging and fixing issues in a page or confirming whether a reported issue still exists in a page. If the issue is fixed on the live version of the page, you can ask Google to recrawl and index the page. </p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjJeRzM6pkq9ZJDUjwYKFrIfzt5c87jCHMEEQgiFHgrm6dEyNrzZiflZLcZprjo0FTBbafvcUVF5VxVasUK0Q8NgprnQbq890S9Pcz-USv_SbxPzns7gdaPGCZc9E-sPky7gWYG/s1600/post03.png" imageanchor="1" ><img border="0" data-original-height="800" data-original-width="700" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjJeRzM6pkq9ZJDUjwYKFrIfzt5c87jCHMEEQgiFHgrm6dEyNrzZiflZLcZprjo0FTBbafvcUVF5VxVasUK0Q8NgprnQbq890S9Pcz-USv_SbxPzns7gdaPGCZc9E-sPky7gWYG/s400/post03.png" width="350" /></a> <h2>We're not finished yet!</h2> <p>Your feedback is important to us! As we evolve Search Console, your feedback helps us to tune our efforts. You can still switch between the old and new products easily, so any missing functionality you need is just a few clicks away. We will continue working on moving more reports and tools as well as adding exciting new capabilities to the new Search Console.</p> <br> <span class="byline-author">Posted by Hillel Maoz and Yinnon Haviv, Engineering Leads, Search Console 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>Today we mark an important milestone in Search Console’s history: we are graduating the new Search Console out of beta! With this graduation we are also launching the Manual Actions report and a “Test Live” capability to the recently launched URL inspection tool, which are joining a stream of reports and features we launched in the new Search Console over the past few months.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh8HE9sCLX_Y0XiE2Er9zjdf4nuWDXbOvSPShbGDIi4bhxekCFEvt4gaaVEnbYxsWWnNli2rVeG4N3ISqoc4qMJ81y_E0nolSnMekes1T1mmK6abEvHR7YSj2BqhfevrpBH-A5q/s1600/post01.png" imageanchor="1" ><img border="0" data-original-height="800" data-original-width="700" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh8HE9sCLX_Y0XiE2Er9zjdf4nuWDXbOvSPShbGDIi4bhxekCFEvt4gaaVEnbYxsWWnNli2rVeG4N3ISqoc4qMJ81y_E0nolSnMekes1T1mmK6abEvHR7YSj2BqhfevrpBH-A5q/s400/post01.png" width="350" /></a> <h2>Our journey to the new Search Console</h2> <p>We <a href="https://webmasters.googleblog.com/2018/01/introducing-new-search-console.html">launched</a> the <a href="https://search.google.com/search-console">new Search Console</a> at the beginning of the year. Since then we have been busy hearing and responding to your <a href="https://webmasters.googleblog.com/2018/02/how-listening-to-our-users-helped-us.html">feedback</a>, adding new features such as the <a href="https://webmasters.googleblog.com/2018/06/new-url-inspection-tool-more-in-search.html">URL Inspection Tool</a>, and migrating <a href="https://webmasters.googleblog.com/2018/08/links-mobile-usability-and-site.html">key reports and features</a>. Here's what the new Search Console gives you:</p> <p>More data:</p> <ul><li>Get an accurate view of your website content using the <a href="https://support.google.com/webmasters/answer/7440203">Index Coverage report</a>.</li> <li>Review your Search Analytics data going back 16 months in the <a href="https://support.google.com/webmasters/answer/7576553">Performance report</a>.</li> <li>See information on links pointing to your site and within your site using the <a href="https://support.google.com/webmasters/answer/9049606">Links report</a>.</li> <li>Retrieve crawling, indexing, and serving information for any URL directly from the Google index using the <a href="https://support.google.com/webmasters/answer/9012289">URL Inspection Tool</a>.</li></ul> <p>Better alerting and new "fixed it" flows:</p> <ul><li>Get automatic alerts and see a listing of pages affected by Crawling, Indexing, AMP, Mobile Usability, Recipes, or Job posting issues. </li> <li>Reports now show the HTML code where we think a fix necessary (if applicable).</li> <li>Share information quickly with the relevant people in your organization to drive the fix.</li> <li>Notify Google when you've fixed an issue. We will review your pages, validate whether the issue is fixed, and return a <a href="https://support.google.com/webmasters/answer/7440203#validation">detailed log of the validation findings</a>.</li></ul> <p>Simplified sitemaps and account settings management:</p> <ul><li>Let Google know how your site is structured by <a href="https://support.google.com/webmasters/answer/7451001">submitting sitemaps</a></li> <li>Submit individual URLs for indexing (see below).</li> <li>Add new sites to your account, <a href="https://support.google.com/webmasters/answer/7687615">invite and manage users</a>.</li></ul> <h2>Out of Beta</h2> <p>While the old Search Console still has some features that are not yet available in the new one, we believe that the most common use cases are supported, in an improved way, in the new Search Console. When an equivalent feature exists in both old and new Search Console, our messages will point users to the new version. We'll also add a reminder link in the old report. After a reasonable period, we will remove the old report. </p> <p>Read more about how to migrate from old to the new Search Console, including a list of improved reports and how to perform common tasks, <a href="https://support.google.com/webmasters/answer/9073702">in our help center</a>.</p> <h2>Manual Actions and Security Issues alerts</h2> <p>To ensure that you don't miss any critical alerts for your site, active manual actions and security issues will be shown directly on the Overview page in the new console. In addition, the <a href="https://support.google.com/webmasters/answer/9044175">Manual Actions report</a> has gotten a fresher look in the new Search Console. From there, you can review the details for any pending Manual Action and, if needed, <a href="https://support.google.com/webmasters/answer/35843">file a reconsideration request</a>.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhfsmkXFbDMSMiqHRLxmN5z9j3TLgm08fBrdYpZVeGovvr4e7f2GN5req3xF6pgmZtNtS7ZCs9AfBhDp6fqRP-zM406sVcVK8-yQwhE0fW_K6sixEB0OJ23CK-XUifZP0juTfgw/s1600/post02.png" imageanchor="1" ><img border="0" data-original-height="800" data-original-width="700" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhfsmkXFbDMSMiqHRLxmN5z9j3TLgm08fBrdYpZVeGovvr4e7f2GN5req3xF6pgmZtNtS7ZCs9AfBhDp6fqRP-zM406sVcVK8-yQwhE0fW_K6sixEB0OJ23CK-XUifZP0juTfgw/s400/post02.png" width="350" /></a> <h2>URL Inspection - Live mode and request indexing</h2> <p>The <a href="https://webmasters.googleblog.com/2018/06/new-url-inspection-tool-more-in-search.html">URL inspection tool</a> that we launched a few months ago now enables you to run the inspection on the live version of the page. This is useful for debugging and fixing issues in a page or confirming whether a reported issue still exists in a page. If the issue is fixed on the live version of the page, you can ask Google to recrawl and index the page. </p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjJeRzM6pkq9ZJDUjwYKFrIfzt5c87jCHMEEQgiFHgrm6dEyNrzZiflZLcZprjo0FTBbafvcUVF5VxVasUK0Q8NgprnQbq890S9Pcz-USv_SbxPzns7gdaPGCZc9E-sPky7gWYG/s1600/post03.png" imageanchor="1" ><img border="0" data-original-height="800" data-original-width="700" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjJeRzM6pkq9ZJDUjwYKFrIfzt5c87jCHMEEQgiFHgrm6dEyNrzZiflZLcZprjo0FTBbafvcUVF5VxVasUK0Q8NgprnQbq890S9Pcz-USv_SbxPzns7gdaPGCZc9E-sPky7gWYG/s400/post03.png" width="350" /></a> <h2>We're not finished yet!</h2> <p>Your feedback is important to us! As we evolve Search Console, your feedback helps us to tune our efforts. You can still switch between the old and new products easily, so any missing functionality you need is just a few clicks away. We will continue working on moving more reports and tools as well as adding exciting new capabilities to the new Search Console.</p> <br> <span class="byline-author">Posted by Hillel Maoz and Yinnon Haviv, Engineering Leads, Search Console 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:The new Search Console is graduating out of Beta 🎓&url=https://webmasters.googleblog.com/2018/09/the-new-search-console-is-graduating.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2018/09/the-new-search-console-is-graduating.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2018/09/the-new-search-console-is-graduating.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='8624407059680938156' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2018/08/collaboration-and-user-management-in.html?hl=en_US' itemprop='url' title='Collaboration and user management in the new Search Console'> Collaboration and user management in the new Search Console </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, August 29, 2018 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>As part of our reinvention of Search Console, we have been rethinking the models of facilitating cooperation and accountability for our users. We decided to redesign the product around cooperative team usage and transparency of action history. The new Search Console will gradually provide better history tracking to show who performed which significant property-affecting modifications, such as changing a setting, validating an issue or submitting a new sitemap. In that spirit we also plan to enable all users to see critical site messages. </p> <h3>New features</h3> <ul><li>User management is now an integral part of Search Console.</li> <li>The new Search Console enables you to share a read-only view of many reports, including Index coverage, AMP, and Mobile Usability. <a href="https://support.google.com/webmasters/answer/7440203#sharing_the_report">Learn more</a>.</li> <li>A new user management interface that enables all users to see and (if appropriate), manage user roles for all property users.</li></ul> <h3>New Role definition</h3> <ul><li>In order to provide a simpler permission model, we are planning to limit the "restricted" user role to read-only status. While being able to see all information, read-only users will no longer be able to perform any state-changing actions, including starting a fix validation or sharing an issue. </li></ul> <h3>Best practices</h3> <p>As a reminder, here are some best practices for managing user permissions in Search Console:</p> <ul><li>Grant users only the permission level that they need to do their work. <a href="https://support.google.com/webmasters/answer/7687615#permissions">See the permissions descriptions.</a></li> <li>If you need to share an issue details report, click the Share link on that page.</li> <li>Revoke permissions from users who no longer work on a property.</li> <li>When removing a previous verified owner, be sure to <a href="https://support.google.com/webmasters/answer/7687615#manage-users">remove all verification tokens for that user</a>.</li> <li>Regularly audit and update the user permissions using the <a href="https://search.google.com/search-console/users">Users & Permissions</a> page in new Search Console.</li></ul> <h3>User feedback</h3> <p>As part of our Beta exploration, we released visibility of the user management interface to all user roles. Some users reached out to request more time to prepare for the updated user management model, including the ability of restricted and full users to easily see a list of other collaborators on the site. We’ve taken that feedback and will hold off on that part of the launch. Stay tuned for more updates relating to collaboration tools and changes on our permission models.</p> <p>As always, we love to hear feedback from our users. Feel free to use the feedback form within Search Console, and we welcome your discussions in our <a href="https://support.google.com/webmasters/go/community">help forums</a> as well!</p> <br> <span class="byline-author">Posted by John Mueller, Google Switzerland</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>As part of our reinvention of Search Console, we have been rethinking the models of facilitating cooperation and accountability for our users. We decided to redesign the product around cooperative team usage and transparency of action history. The new Search Console will gradually provide better history tracking to show who performed which significant property-affecting modifications, such as changing a setting, validating an issue or submitting a new sitemap. In that spirit we also plan to enable all users to see critical site messages. </p> <h3>New features</h3> <ul><li>User management is now an integral part of Search Console.</li> <li>The new Search Console enables you to share a read-only view of many reports, including Index coverage, AMP, and Mobile Usability. <a href="https://support.google.com/webmasters/answer/7440203#sharing_the_report">Learn more</a>.</li> <li>A new user management interface that enables all users to see and (if appropriate), manage user roles for all property users.</li></ul> <h3>New Role definition</h3> <ul><li>In order to provide a simpler permission model, we are planning to limit the "restricted" user role to read-only status. While being able to see all information, read-only users will no longer be able to perform any state-changing actions, including starting a fix validation or sharing an issue. </li></ul> <h3>Best practices</h3> <p>As a reminder, here are some best practices for managing user permissions in Search Console:</p> <ul><li>Grant users only the permission level that they need to do their work. <a href="https://support.google.com/webmasters/answer/7687615#permissions">See the permissions descriptions.</a></li> <li>If you need to share an issue details report, click the Share link on that page.</li> <li>Revoke permissions from users who no longer work on a property.</li> <li>When removing a previous verified owner, be sure to <a href="https://support.google.com/webmasters/answer/7687615#manage-users">remove all verification tokens for that user</a>.</li> <li>Regularly audit and update the user permissions using the <a href="https://search.google.com/search-console/users">Users & Permissions</a> page in new Search Console.</li></ul> <h3>User feedback</h3> <p>As part of our Beta exploration, we released visibility of the user management interface to all user roles. Some users reached out to request more time to prepare for the updated user management model, including the ability of restricted and full users to easily see a list of other collaborators on the site. We’ve taken that feedback and will hold off on that part of the launch. Stay tuned for more updates relating to collaboration tools and changes on our permission models.</p> <p>As always, we love to hear feedback from our users. Feel free to use the feedback form within Search Console, and we welcome your discussions in our <a href="https://support.google.com/webmasters/go/community">help forums</a> as well!</p> <br> <span class="byline-author">Posted by John Mueller, Google Switzerland</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Collaboration and user management in the new Search Console&url=https://webmasters.googleblog.com/2018/08/collaboration-and-user-management-in.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2018/08/collaboration-and-user-management-in.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2018/08/collaboration-and-user-management-in.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/general%20tips?hl=en_US' rel='tag'> general tips </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='728567517365270219' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2018/08/links-mobile-usability-and-site.html?hl=en_US' itemprop='url' title='Links, Mobile Usability, and site management in the new Search Console'> Links, Mobile Usability, and site management in the new Search Console </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, August 21, 2018 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>More features are coming to the <a href="https://webmasters.googleblog.com/2018/01/introducing-new-search-console.html">new Search Console</a>. This time we've focused on importing existing popular features from the old Search Console to the new product.</p> <h3>Links Report</h3> <p>Search Console users value the ability to see links to and within their site, as Google Search sees them. Today, we are rolling out the new <a href="https://support.google.com/webmasters/answer/9049606">Links</a> report, which combines the functionality of the “Links to your site” and “Internal Links” reports on the old Search Console. We hope you find this useful!</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEidC0Z8YyXmOMc0EusA6gsvlf5kTu-VkZKS9IeT2lkNb18gMEPb-pZXAHFeA0rd18NSU5l7cdwRicKPID2FSr-zXXrKKwBUoQnVHxDTH7s6GthIqDUPSxxgxELjDkL43qT7KQRh/s1600/image01.png" imageanchor="1" ><img border="0" data-original-height="1266" data-original-width="1084" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEidC0Z8YyXmOMc0EusA6gsvlf5kTu-VkZKS9IeT2lkNb18gMEPb-pZXAHFeA0rd18NSU5l7cdwRicKPID2FSr-zXXrKKwBUoQnVHxDTH7s6GthIqDUPSxxgxELjDkL43qT7KQRh/s400/image01.png" width="342" /></a> </p> <h3>Mobile Usability report</h3> <p><a href="https://developers.google.com/search/mobile-sites/">Mobile Usability</a> is an important priority for all site owners. In order to help site owners with fixing mobile usability issues, we launched the Mobile Usability report on the new Search Console. Issue names are the same as in the old report but we now allow users to submit a validation and reindexing request when an issue is fixed, similar to other reports in the new Search Console. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjjTDY73T3OUo7Af1Mn9o0207VwXtzRgn09hdgpRs24B0myv3_jsX2hw1WTtK8mUn7aAoMTpSSK8fsmMm6Y8iXCTxkEWXU3XjQQY2rsvJWFjD4e4CNTp0KOYEkE_UbXnS8ljPNr/s1600/image02.png" imageanchor="1" ><img border="0" data-original-height="1262" data-original-width="1086" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjjTDY73T3OUo7Af1Mn9o0207VwXtzRgn09hdgpRs24B0myv3_jsX2hw1WTtK8mUn7aAoMTpSSK8fsmMm6Y8iXCTxkEWXU3XjQQY2rsvJWFjD4e4CNTp0KOYEkE_UbXnS8ljPNr/s400/image02.png" width="344" /></a> </p> <h3>Site and user management</h3> <p>To make the new Search Console feel more like home, we’ve added the ability to add and verify new sites, and manage your property's users and permissions, directly in new Search Console using our newly added <a href="https://support.google.com/webmasters/answer/7687465">settings</a> page. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjzcG-07EbfT8litkW2iV5syOSrPBkbN7hKytuycE-PnWzo9c9I4UF4S1TJEyatDYvS2-HMKvr2Lmx2U2q4DZIS_MLdzfiu2t4z14s4xawR4M9DhCHKRXeLrmfyr5mN7LMUbPX0/s1600/image03.png" imageanchor="1" ><img border="0" data-original-height="1274" data-original-width="1090" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjzcG-07EbfT8litkW2iV5syOSrPBkbN7hKytuycE-PnWzo9c9I4UF4S1TJEyatDYvS2-HMKvr2Lmx2U2q4DZIS_MLdzfiu2t4z14s4xawR4M9DhCHKRXeLrmfyr5mN7LMUbPX0/s400/image03.png" width="342" /></a> </p> <h3>Keep sending feedback</h3> <p>As always, we would love to get your feedback through the tools directly and our <a href="https://support.google.com/webmasters/go/community">help forums</a> so please share and let us know how we're doing.</p> <br> <span class="byline-author">Posted by Ariel Kroszynski and Roman Kecher - Search Console engineers</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>More features are coming to the <a href="https://webmasters.googleblog.com/2018/01/introducing-new-search-console.html">new Search Console</a>. This time we've focused on importing existing popular features from the old Search Console to the new product.</p> <h3>Links Report</h3> <p>Search Console users value the ability to see links to and within their site, as Google Search sees them. Today, we are rolling out the new <a href="https://support.google.com/webmasters/answer/9049606">Links</a> report, which combines the functionality of the “Links to your site” and “Internal Links” reports on the old Search Console. We hope you find this useful!</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEidC0Z8YyXmOMc0EusA6gsvlf5kTu-VkZKS9IeT2lkNb18gMEPb-pZXAHFeA0rd18NSU5l7cdwRicKPID2FSr-zXXrKKwBUoQnVHxDTH7s6GthIqDUPSxxgxELjDkL43qT7KQRh/s1600/image01.png" imageanchor="1" ><img border="0" data-original-height="1266" data-original-width="1084" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEidC0Z8YyXmOMc0EusA6gsvlf5kTu-VkZKS9IeT2lkNb18gMEPb-pZXAHFeA0rd18NSU5l7cdwRicKPID2FSr-zXXrKKwBUoQnVHxDTH7s6GthIqDUPSxxgxELjDkL43qT7KQRh/s400/image01.png" width="342" /></a> </p> <h3>Mobile Usability report</h3> <p><a href="https://developers.google.com/search/mobile-sites/">Mobile Usability</a> is an important priority for all site owners. In order to help site owners with fixing mobile usability issues, we launched the Mobile Usability report on the new Search Console. Issue names are the same as in the old report but we now allow users to submit a validation and reindexing request when an issue is fixed, similar to other reports in the new Search Console. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjjTDY73T3OUo7Af1Mn9o0207VwXtzRgn09hdgpRs24B0myv3_jsX2hw1WTtK8mUn7aAoMTpSSK8fsmMm6Y8iXCTxkEWXU3XjQQY2rsvJWFjD4e4CNTp0KOYEkE_UbXnS8ljPNr/s1600/image02.png" imageanchor="1" ><img border="0" data-original-height="1262" data-original-width="1086" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjjTDY73T3OUo7Af1Mn9o0207VwXtzRgn09hdgpRs24B0myv3_jsX2hw1WTtK8mUn7aAoMTpSSK8fsmMm6Y8iXCTxkEWXU3XjQQY2rsvJWFjD4e4CNTp0KOYEkE_UbXnS8ljPNr/s400/image02.png" width="344" /></a> </p> <h3>Site and user management</h3> <p>To make the new Search Console feel more like home, we’ve added the ability to add and verify new sites, and manage your property's users and permissions, directly in new Search Console using our newly added <a href="https://support.google.com/webmasters/answer/7687465">settings</a> page. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjzcG-07EbfT8litkW2iV5syOSrPBkbN7hKytuycE-PnWzo9c9I4UF4S1TJEyatDYvS2-HMKvr2Lmx2U2q4DZIS_MLdzfiu2t4z14s4xawR4M9DhCHKRXeLrmfyr5mN7LMUbPX0/s1600/image03.png" imageanchor="1" ><img border="0" data-original-height="1274" data-original-width="1090" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjzcG-07EbfT8litkW2iV5syOSrPBkbN7hKytuycE-PnWzo9c9I4UF4S1TJEyatDYvS2-HMKvr2Lmx2U2q4DZIS_MLdzfiu2t4z14s4xawR4M9DhCHKRXeLrmfyr5mN7LMUbPX0/s400/image03.png" width="342" /></a> </p> <h3>Keep sending feedback</h3> <p>As always, we would love to get your feedback through the tools directly and our <a href="https://support.google.com/webmasters/go/community">help forums</a> so please share and let us know how we're doing.</p> <br> <span class="byline-author">Posted by Ariel Kroszynski and Roman Kecher - Search Console engineers</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Links, Mobile Usability, and site management in the new Search Console&url=https://webmasters.googleblog.com/2018/08/links-mobile-usability-and-site.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2018/08/links-mobile-usability-and-site.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2018/08/links-mobile-usability-and-site.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/mobile?hl=en_US' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US' rel='tag'> mobile-friendly </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='8385281410643633931' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2018/06/new-url-inspection-tool-more-in-search.html?hl=en_US' itemprop='url' title='New URL inspection tool & more in Search Console'> New URL inspection tool & more in Search Console </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Monday, June 25, 2018 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>A few months ago, we introduced the <a href="https://webmasters.googleblog.com/2018/01/introducing-new-search-console.html">new Search Console</a>. Here are some updates on how it's progressing. </p> <h3>Welcome "URL inspection" tool </h3> <p>One of our most common user requests in Search Console is for more details on how Google Search sees a specific URL. We listened, and today we've started launching a new tool, “<a href="https://support.google.com/webmasters/answer/9012289">URL inspection</a>,” to provide these details so Search becomes more transparent. The URL Inspection tool provides detailed <a href="https://support.google.com/webmasters/answer/70897">crawl, index, and serving information</a> about your pages, directly from the Google index.</p> <p>Enter a URL that you own to learn the last crawl date and status, any crawling or indexing errors, and the canonical URL for that page. If the page was successfully indexed, you can see information and status about any enhancements we found on the page, such as linked AMP version or rich results like Recipes and Jobs. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgMtyY5DJWL8aGYTkzARo5ZVGCg_F_wpNtnWK5QpjtN_GBkfNd4i8EwFG3l6E3chyOAKhfix6xk6h-Hz-AFF2iqvWILN3y9xJCUcgnymq4GEwzhOr5cB0Hhnxn1p-NrG74_c83X/s1600/01_submitted_and_indexed%25402x.png" imageanchor="1" ><img border="0" data-original-height="1600" data-original-width="1205" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgMtyY5DJWL8aGYTkzARo5ZVGCg_F_wpNtnWK5QpjtN_GBkfNd4i8EwFG3l6E3chyOAKhfix6xk6h-Hz-AFF2iqvWILN3y9xJCUcgnymq4GEwzhOr5cB0Hhnxn1p-NrG74_c83X/s400/01_submitted_and_indexed%25402x.png" width="301" /></a> <br> <i>URL is indexed with valid AMP enhancement</i> </p> <p>If a page isn't indexed, you can learn why. The new report includes information about <a href="https://support.google.com/webmasters/answer/93710">noindex robots meta tags</a> and Google's canonical URL for the page.</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjDaOLmviJM5xVeY6jgUzhbDL5aF-TB2PwYHQ9VlWlkcO3XcfmHCXl_pp58abuOO1IjUVmSG8NoU74dyJ2PFprhKTuLeUfIkPqYBi4SNKI08J5_vnZeCLT3iXmaA0EEC809dTPm/s1600/02_submitted_URL_marked_noindex%25402x.png" imageanchor="1" ><img border="0" data-original-height="1600" data-original-width="864" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjDaOLmviJM5xVeY6jgUzhbDL5aF-TB2PwYHQ9VlWlkcO3XcfmHCXl_pp58abuOO1IjUVmSG8NoU74dyJ2PFprhKTuLeUfIkPqYBi4SNKI08J5_vnZeCLT3iXmaA0EEC809dTPm/s400/02_submitted_URL_marked_noindex%25402x.png" width="216" /></a> <br> <i>URL is not indexed due to ‘noindex’ meta tag in the HTML</i> </p> <p>A single click can take you to the issue report showing all other pages affected by the same issue to help you track down and fix common bugs.</p> <p>We hope that the URL Inspection tool will help you debug issues with new or existing pages in the Google Index. We began rolling it out today; it will become available to all users in the coming weeks. </p> <h3>More exciting updates</h3> <p>In addition to the launch of URL inspection, we have a few more features and reports we recently launched to the new Search Console:</p> <ul><li><b>Sixteen months of traffic data</b>: The <a href="https://developers.google.com/webmaster-tools/search-console-api-original/v3/searchanalytics">Search Analytics API</a> now returns 16 months of data, just like the <a href="https://support.google.com/webmasters/answer/7576553">Performance report</a>. </li> <li><b>Recipe report</b>: The <a href="https://support.google.com/webmasters/answer/7552505">Recipe report</a> help you fix structured data issues affecting recipes rich results. Use our <a href="https://webmasters.googleblog.com/2018/01/introducing-new-search-console.html">task-oriented interface</a> to test and validate your fixes; we will keep you informed on your progress using messages.</li> <li><b>New Search Appearance filters in Search Analytics</b>: The <a href="https://support.google.com/webmasters/answer/7576553">performance</a> report now gives you more visibility on new search appearance results, including <a href="https://support.google.com/webmasters/answer/6211428">Web Light</a> and <a href="https://developer.android.com/topic/google-play-instant/">Google Play Instant</a> results.</li></ul> <h3>Thank you for your feedback</h3> <p>We are constantly reading your feedback, conducting surveys, and monitoring usage statistics of the new Search Console. We are happy to see so many of you using the new <a href="https://webmasters.googleblog.com/2018/01/introducing-new-search-console.html#enhance">issue validation flow</a> in Index Coverage and the AMP report. We notice that issues tend to get fixed quicker when you use these tools. We also see that you appreciate the updates on the validation process that we provide by email or on the validation details page.</p> <p>We want to thank everyone who provided feedback: it has helped us improve our flows and fix bugs on our side. </p> <h3>More to come</h3> <p>The new Search Console is still beta, but it's adding features and reports every month. Please keep sharing your feedback through the various channels and let us know how we're doing.</p> <br> <span class="byline-author">Posted by Roman Kecher and Sion Schori - Search Console engineers</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>A few months ago, we introduced the <a href="https://webmasters.googleblog.com/2018/01/introducing-new-search-console.html">new Search Console</a>. Here are some updates on how it's progressing. </p> <h3>Welcome "URL inspection" tool </h3> <p>One of our most common user requests in Search Console is for more details on how Google Search sees a specific URL. We listened, and today we've started launching a new tool, “<a href="https://support.google.com/webmasters/answer/9012289">URL inspection</a>,” to provide these details so Search becomes more transparent. The URL Inspection tool provides detailed <a href="https://support.google.com/webmasters/answer/70897">crawl, index, and serving information</a> about your pages, directly from the Google index.</p> <p>Enter a URL that you own to learn the last crawl date and status, any crawling or indexing errors, and the canonical URL for that page. If the page was successfully indexed, you can see information and status about any enhancements we found on the page, such as linked AMP version or rich results like Recipes and Jobs. </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgMtyY5DJWL8aGYTkzARo5ZVGCg_F_wpNtnWK5QpjtN_GBkfNd4i8EwFG3l6E3chyOAKhfix6xk6h-Hz-AFF2iqvWILN3y9xJCUcgnymq4GEwzhOr5cB0Hhnxn1p-NrG74_c83X/s1600/01_submitted_and_indexed%25402x.png" imageanchor="1" ><img border="0" data-original-height="1600" data-original-width="1205" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgMtyY5DJWL8aGYTkzARo5ZVGCg_F_wpNtnWK5QpjtN_GBkfNd4i8EwFG3l6E3chyOAKhfix6xk6h-Hz-AFF2iqvWILN3y9xJCUcgnymq4GEwzhOr5cB0Hhnxn1p-NrG74_c83X/s400/01_submitted_and_indexed%25402x.png" width="301" /></a> <br> <i>URL is indexed with valid AMP enhancement</i> </p> <p>If a page isn't indexed, you can learn why. The new report includes information about <a href="https://support.google.com/webmasters/answer/93710">noindex robots meta tags</a> and Google's canonical URL for the page.</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjDaOLmviJM5xVeY6jgUzhbDL5aF-TB2PwYHQ9VlWlkcO3XcfmHCXl_pp58abuOO1IjUVmSG8NoU74dyJ2PFprhKTuLeUfIkPqYBi4SNKI08J5_vnZeCLT3iXmaA0EEC809dTPm/s1600/02_submitted_URL_marked_noindex%25402x.png" imageanchor="1" ><img border="0" data-original-height="1600" data-original-width="864" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjDaOLmviJM5xVeY6jgUzhbDL5aF-TB2PwYHQ9VlWlkcO3XcfmHCXl_pp58abuOO1IjUVmSG8NoU74dyJ2PFprhKTuLeUfIkPqYBi4SNKI08J5_vnZeCLT3iXmaA0EEC809dTPm/s400/02_submitted_URL_marked_noindex%25402x.png" width="216" /></a> <br> <i>URL is not indexed due to ‘noindex’ meta tag in the HTML</i> </p> <p>A single click can take you to the issue report showing all other pages affected by the same issue to help you track down and fix common bugs.</p> <p>We hope that the URL Inspection tool will help you debug issues with new or existing pages in the Google Index. We began rolling it out today; it will become available to all users in the coming weeks. </p> <h3>More exciting updates</h3> <p>In addition to the launch of URL inspection, we have a few more features and reports we recently launched to the new Search Console:</p> <ul><li><b>Sixteen months of traffic data</b>: The <a href="https://developers.google.com/webmaster-tools/search-console-api-original/v3/searchanalytics">Search Analytics API</a> now returns 16 months of data, just like the <a href="https://support.google.com/webmasters/answer/7576553">Performance report</a>. </li> <li><b>Recipe report</b>: The <a href="https://support.google.com/webmasters/answer/7552505">Recipe report</a> help you fix structured data issues affecting recipes rich results. Use our <a href="https://webmasters.googleblog.com/2018/01/introducing-new-search-console.html">task-oriented interface</a> to test and validate your fixes; we will keep you informed on your progress using messages.</li> <li><b>New Search Appearance filters in Search Analytics</b>: The <a href="https://support.google.com/webmasters/answer/7576553">performance</a> report now gives you more visibility on new search appearance results, including <a href="https://support.google.com/webmasters/answer/6211428">Web Light</a> and <a href="https://developer.android.com/topic/google-play-instant/">Google Play Instant</a> results.</li></ul> <h3>Thank you for your feedback</h3> <p>We are constantly reading your feedback, conducting surveys, and monitoring usage statistics of the new Search Console. We are happy to see so many of you using the new <a href="https://webmasters.googleblog.com/2018/01/introducing-new-search-console.html#enhance">issue validation flow</a> in Index Coverage and the AMP report. We notice that issues tend to get fixed quicker when you use these tools. We also see that you appreciate the updates on the validation process that we provide by email or on the validation details page.</p> <p>We want to thank everyone who provided feedback: it has helped us improve our flows and fix bugs on our side. </p> <h3>More to come</h3> <p>The new Search Console is still beta, but it's adding features and reports every month. Please keep sharing your feedback through the various channels and let us know how we're doing.</p> <br> <span class="byline-author">Posted by Roman Kecher and Sion Schori - Search Console engineers</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:New URL inspection tool & more in Search Console&url=https://webmasters.googleblog.com/2018/06/new-url-inspection-tool-more-in-search.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2018/06/new-url-inspection-tool-more-in-search.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2018/06/new-url-inspection-tool-more-in-search.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en_US' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/rich%20results?hl=en_US' rel='tag'> rich results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='2804943324287873011' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2018/05/helping-webmasters-and-content.html?hl=en_US' itemprop='url' title='Our goal: helping webmasters and content creators'> Our goal: helping webmasters and content creators </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, May 10, 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"> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;">Great websites are the result of the hard work of website owners who make their content and services accessible to the world. Even though it’s simpler now to run a website than it was years ago, it can still feel like a complex undertaking. This is why we invest a lot of time and effort in improving Google Search so that website owners can spend more time focusing on building the most useful content for their users, while we take care of helping users find that content. </span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;">Most website owners find they don’t have to worry much about what Google is doing—they post their content, and then Googlebot discovers, crawls, indexes and understands that content, to point users to relevant pages on those sites. However, sometimes the technical details still matter, and sometimes a great deal.</span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="font-family: "arial" , "helvetica" , sans-serif;"><span style="white-space: pre-wrap;">For those times when site owners would like a bit of help from someone at Google, or an explanation for why something works a particular way, or why things appear in a particular way, or how to fix what looks like a technical glitch, we have a global team dedicated to making sure there are </span><span id="docs-internal-guid-2f9b6a4e-4c34-3c59-1342-7eb9dbf3a9b5"><a href="https://www.google.com/webmasters/support/" style="text-decoration-line: none;"><span style="color: #1155cc; vertical-align: baseline; white-space: pre-wrap;">many places for a website owner to get help</span></a></span><span style="white-space: pre-wrap;"> from Google and knowledgeable members of the community.</span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="font-family: "arial" , "helvetica" , sans-serif;"><span style="white-space: pre-wrap;">The first place to start for help is </span><span id="docs-internal-guid-b3141267-4c34-90ab-e9bb-8ce2099bc0e4"><a href="https://www.google.com/webmasters" style="text-decoration-line: none;"><span style="color: #1155cc; vertical-align: baseline; white-space: pre-wrap;">Google Webmasters</span></a></span><span style="white-space: pre-wrap;">, a place where all of our support resources (many of which are available in 40 languages) are within easy reach:</span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> </div> <ul style="text-align: left;"> <li><span style="font-family: "arial" , "helvetica" , sans-serif;"><span id="docs-internal-guid-e4cc8742-4c35-9296-fc93-cac05d590ca7"><a href="https://developers.google.com/web/" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Google Web Fundamentals</span></a></span>: Provides technical guidance on building a modern website that takes advantage of open web standards.</span></li> <li><span style="font-family: "arial" , "helvetica" , sans-serif;"><span id="docs-internal-guid-5f0744fe-4c35-bad5-cd7d-81bfa51802cf"><a href="http://developers.google.com/search" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Google Search developer documentation</span></a></span>: Describes how Google crawls and indexes a website. Includes authoritative guidance on building a site that is optimized for Google Search. </span></li> <li><span style="font-family: "arial" , "helvetica" , sans-serif;"><span id="docs-internal-guid-a217c0d6-4c35-e2e7-7ce6-b6db1ec4e537"><a href="https://support.google.com/webmasters#topic=3309469" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Search Console Help Center</span></a></span>: Provides detailed information on how to use and take advantage of <span id="docs-internal-guid-671b0506-4c36-0822-66b8-dacf64ade168"><a href="https://www.google.com/webmasters/tools/home" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Search Console</span></a></span>, the best way for a website owner to understand how Google sees their site. </span></li> <li><span style="font-family: "arial" , "helvetica" , sans-serif;">The <span id="docs-internal-guid-b78fe94d-4c36-34f4-9f17-80d85e90033b"><a href="https://support.google.com/webmasters/answer/7451184?hl=en" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Search Engine Optimization (SEO) Starter Guide</span></a></span>: Provides a complete overview of the basics of SEO according to our recommended best practices.</span></li> <li><span style="font-family: "arial" , "helvetica" , sans-serif;"><span id="docs-internal-guid-9e7fd398-4c36-5e7a-9bbe-29b61e2fe825"><a href="https://support.google.com/webmasters/answer/35769" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Google webmaster guidelines</span></a></span>: Describes policies and practices that may lead to a site being removed entirely from the Google index or otherwise affected by an algorithmic or manual spam action that can negatively affect their Search appearance. </span></li> <li><span id="docs-internal-guid-eca34a5b-4c36-8787-13c3-a953ad02eff3"><a href="https://www.youtube.com/channel/UCWf2ZlNsCGDS89VBF_awNvA" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Google Webmasters YouTube Channel</span></a></span></li> </ul> <br /> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;">Our second path to getting help is through our </span></span><span id="docs-internal-guid-84446268-4c36-b470-95bc-79c265c97803"><a href="https://productforums.google.com/forum/#!forum/webmasters" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Google Webmaster Central Help Forums</span></a></span><span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;">. We have forums in 16 languages—in </span></span><span id="docs-internal-guid-d0946682-4c36-e927-8ff1-d3fe0a060cfa"><a href="https://productforums.google.com/forum/#!forum/webmasters" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">English</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-es" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Spanish</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-hi" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Hindi</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-fr" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">French</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-it" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Italian</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-pt" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Portuguese</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-ja" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Japanese</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-de" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">German</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-ru" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Russian</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-tr" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Turkish</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-pl" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Polish</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-id" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Bahasa Indonesia</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-th" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Thai</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/?hl=vi#!topicsearchin/hotro-vi/category$3A%28webmaster-vi%29" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Vietnamese</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-zh-cn" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Chinese</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;"> and </span><a href="https://productforums.google.com/forum/#!forum/webmaster-ko" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Korean</span></a></span><span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;">. The forums are staffed with dedicated Googlers who are there to make sure your questions get answered. Aside from the Googlers who monitor the forums, there is an amazing group of <a href="https://topcontributor.withgoogle.com/profiles">Top Contributors</a> who generously offer their time to help other members of the community—many times providing greater detail and analysis for a particular website’s content than we could. The forums allow for both a public discussion and, if the case requires it, for private follow-up replies in the forum.</span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;">A third path for support to website owners is our series of </span></span><span id="docs-internal-guid-9bd4b4cf-4c3d-9e3f-eff1-ec2a09659099"><a href="https://www.google.com/webmasters/connect/" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Online Webmaster Office Hours</span></a></span><span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"> — in English, German, Japanese, Turkish, Hindi and French. Anyone who joins these is welcome to ask us questions about website appearance in Google Search, which we will answer to the best of our abilities. All of our team members think that one of the best parts of speaking at conferences and events is the opportunity to answer questions from the audience,  and the online office hours format creates that opportunity for many more people who might not be able to travel to a specialized event. You can always check out the </span></span><span id="docs-internal-guid-e226dfaf-4c3d-d8c5-2c6a-2f2bb7ff84ee"><a href="https://www.google.com/webmasters/connect/" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Google Webmaster calendar</span></a></span><span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"> for upcoming webmaster officer hours and live events.</span></span><br /> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></span> <span style="font-family: "arial" , "helvetica" , sans-serif;"><span style="white-space: pre-wrap;">Beyond all these resources, we also work hard to ensure that everyone who wants to understand Google Search can find relevant info on our frequently updated site <a href="https://www.google.com/search/howsearchworks/">How Search Works</a>.</span></span><br /> <span style="font-family: "arial" , "helvetica" , sans-serif; white-space: pre-wrap;"><br /></span> <span style="font-family: "arial" , "helvetica" , sans-serif; white-space: pre-wrap;">While how a website behaves on the web is openly visible to all who can see it, we know that some website owners prefer not to make it known their website has a problem in a public forum. There’s no shame in asking for support, but if you have an issue for your website that seems sensitive—for which you don’t think you can share all the details publicly—you can call out that you would prefer to share necessary details only with someone experienced and who is willing to help, using the forum’s “Private Reply” feature.</span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;">Are there other things you think we should be doing that would help your website get the most out of search? Please let us know -- in our forums, our office hours, or via Twitter <a href="https://twitter.com/search?q=%40googlewmc&src=typd&lang=en" target="_blank">@googlewmc</a>.</span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;">Posted by Juan Felipe Rincón from Google’s Webmaster Outreach & Support team</span></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 dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;">Great websites are the result of the hard work of website owners who make their content and services accessible to the world. Even though it’s simpler now to run a website than it was years ago, it can still feel like a complex undertaking. This is why we invest a lot of time and effort in improving Google Search so that website owners can spend more time focusing on building the most useful content for their users, while we take care of helping users find that content. </span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;">Most website owners find they don’t have to worry much about what Google is doing—they post their content, and then Googlebot discovers, crawls, indexes and understands that content, to point users to relevant pages on those sites. However, sometimes the technical details still matter, and sometimes a great deal.</span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="font-family: "arial" , "helvetica" , sans-serif;"><span style="white-space: pre-wrap;">For those times when site owners would like a bit of help from someone at Google, or an explanation for why something works a particular way, or why things appear in a particular way, or how to fix what looks like a technical glitch, we have a global team dedicated to making sure there are </span><span id="docs-internal-guid-2f9b6a4e-4c34-3c59-1342-7eb9dbf3a9b5"><a href="https://www.google.com/webmasters/support/" style="text-decoration-line: none;"><span style="color: #1155cc; vertical-align: baseline; white-space: pre-wrap;">many places for a website owner to get help</span></a></span><span style="white-space: pre-wrap;"> from Google and knowledgeable members of the community.</span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="font-family: "arial" , "helvetica" , sans-serif;"><span style="white-space: pre-wrap;">The first place to start for help is </span><span id="docs-internal-guid-b3141267-4c34-90ab-e9bb-8ce2099bc0e4"><a href="https://www.google.com/webmasters" style="text-decoration-line: none;"><span style="color: #1155cc; vertical-align: baseline; white-space: pre-wrap;">Google Webmasters</span></a></span><span style="white-space: pre-wrap;">, a place where all of our support resources (many of which are available in 40 languages) are within easy reach:</span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> </div> <ul style="text-align: left;"> <li><span style="font-family: "arial" , "helvetica" , sans-serif;"><span id="docs-internal-guid-e4cc8742-4c35-9296-fc93-cac05d590ca7"><a href="https://developers.google.com/web/" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Google Web Fundamentals</span></a></span>: Provides technical guidance on building a modern website that takes advantage of open web standards.</span></li> <li><span style="font-family: "arial" , "helvetica" , sans-serif;"><span id="docs-internal-guid-5f0744fe-4c35-bad5-cd7d-81bfa51802cf"><a href="http://developers.google.com/search" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Google Search developer documentation</span></a></span>: Describes how Google crawls and indexes a website. Includes authoritative guidance on building a site that is optimized for Google Search. </span></li> <li><span style="font-family: "arial" , "helvetica" , sans-serif;"><span id="docs-internal-guid-a217c0d6-4c35-e2e7-7ce6-b6db1ec4e537"><a href="https://support.google.com/webmasters#topic=3309469" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Search Console Help Center</span></a></span>: Provides detailed information on how to use and take advantage of <span id="docs-internal-guid-671b0506-4c36-0822-66b8-dacf64ade168"><a href="https://www.google.com/webmasters/tools/home" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Search Console</span></a></span>, the best way for a website owner to understand how Google sees their site. </span></li> <li><span style="font-family: "arial" , "helvetica" , sans-serif;">The <span id="docs-internal-guid-b78fe94d-4c36-34f4-9f17-80d85e90033b"><a href="https://support.google.com/webmasters/answer/7451184?hl=en" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Search Engine Optimization (SEO) Starter Guide</span></a></span>: Provides a complete overview of the basics of SEO according to our recommended best practices.</span></li> <li><span style="font-family: "arial" , "helvetica" , sans-serif;"><span id="docs-internal-guid-9e7fd398-4c36-5e7a-9bbe-29b61e2fe825"><a href="https://support.google.com/webmasters/answer/35769" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Google webmaster guidelines</span></a></span>: Describes policies and practices that may lead to a site being removed entirely from the Google index or otherwise affected by an algorithmic or manual spam action that can negatively affect their Search appearance. </span></li> <li><span id="docs-internal-guid-eca34a5b-4c36-8787-13c3-a953ad02eff3"><a href="https://www.youtube.com/channel/UCWf2ZlNsCGDS89VBF_awNvA" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Google Webmasters YouTube Channel</span></a></span></li> </ul> <br /> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;">Our second path to getting help is through our </span></span><span id="docs-internal-guid-84446268-4c36-b470-95bc-79c265c97803"><a href="https://productforums.google.com/forum/#!forum/webmasters" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Google Webmaster Central Help Forums</span></a></span><span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;">. We have forums in 16 languages—in </span></span><span id="docs-internal-guid-d0946682-4c36-e927-8ff1-d3fe0a060cfa"><a href="https://productforums.google.com/forum/#!forum/webmasters" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">English</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-es" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Spanish</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-hi" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Hindi</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-fr" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">French</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-it" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Italian</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-pt" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Portuguese</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-ja" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Japanese</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-de" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">German</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-ru" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Russian</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-tr" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Turkish</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-pl" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Polish</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-id" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Bahasa Indonesia</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-th" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Thai</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/?hl=vi#!topicsearchin/hotro-vi/category$3A%28webmaster-vi%29" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Vietnamese</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">, </span><a href="https://productforums.google.com/forum/#!forum/webmaster-zh-cn" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Chinese</span></a><span style="font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;"> and </span><a href="https://productforums.google.com/forum/#!forum/webmaster-ko" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Korean</span></a></span><span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;">. The forums are staffed with dedicated Googlers who are there to make sure your questions get answered. Aside from the Googlers who monitor the forums, there is an amazing group of <a href="https://topcontributor.withgoogle.com/profiles">Top Contributors</a> who generously offer their time to help other members of the community—many times providing greater detail and analysis for a particular website’s content than we could. The forums allow for both a public discussion and, if the case requires it, for private follow-up replies in the forum.</span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;">A third path for support to website owners is our series of </span></span><span id="docs-internal-guid-9bd4b4cf-4c3d-9e3f-eff1-ec2a09659099"><a href="https://www.google.com/webmasters/connect/" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Online Webmaster Office Hours</span></a></span><span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"> — in English, German, Japanese, Turkish, Hindi and French. Anyone who joins these is welcome to ask us questions about website appearance in Google Search, which we will answer to the best of our abilities. All of our team members think that one of the best parts of speaking at conferences and events is the opportunity to answer questions from the audience,  and the online office hours format creates that opportunity for many more people who might not be able to travel to a specialized event. You can always check out the </span></span><span id="docs-internal-guid-e226dfaf-4c3d-d8c5-2c6a-2f2bb7ff84ee"><a href="https://www.google.com/webmasters/connect/" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "arial"; vertical-align: baseline; white-space: pre-wrap;">Google Webmaster calendar</span></a></span><span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"> for upcoming webmaster officer hours and live events.</span></span><br /> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></span> <span style="font-family: "arial" , "helvetica" , sans-serif;"><span style="white-space: pre-wrap;">Beyond all these resources, we also work hard to ensure that everyone who wants to understand Google Search can find relevant info on our frequently updated site <a href="https://www.google.com/search/howsearchworks/">How Search Works</a>.</span></span><br /> <span style="font-family: "arial" , "helvetica" , sans-serif; white-space: pre-wrap;"><br /></span> <span style="font-family: "arial" , "helvetica" , sans-serif; white-space: pre-wrap;">While how a website behaves on the web is openly visible to all who can see it, we know that some website owners prefer not to make it known their website has a problem in a public forum. There’s no shame in asking for support, but if you have an issue for your website that seems sensitive—for which you don’t think you can share all the details publicly—you can call out that you would prefer to share necessary details only with someone experienced and who is willing to help, using the forum’s “Private Reply” feature.</span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;">Are there other things you think we should be doing that would help your website get the most out of search? Please let us know -- in our forums, our office hours, or via Twitter <a href="https://twitter.com/search?q=%40googlewmc&src=typd&lang=en" target="_blank">@googlewmc</a>.</span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></span></div> <div dir="ltr" style="line-height: 1.3800000000000001; margin-bottom: 0pt; margin-top: 0pt;"> <span style="white-space: pre-wrap;"><span style="font-family: "arial" , "helvetica" , sans-serif;">Posted by Juan Felipe Rincón from Google’s Webmaster Outreach & Support team</span></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:Our goal: helping webmasters and content creators&url=https://webmasters.googleblog.com/2018/05/helping-webmasters-and-content.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2018/05/helping-webmasters-and-content.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2018/05/helping-webmasters-and-content.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_US' rel='tag'> events </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/forums?hl=en_US' rel='tag'> forums </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/general%20tips?hl=en_US' rel='tag'> general tips </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/products%20and%20services?hl=en_US' rel='tag'> products and services </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/questions?hl=en_US' rel='tag'> questions </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/rich%20results?hl=en_US' rel='tag'> rich results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en_US' rel='tag'> webmaster community </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines?hl=en_US' rel='tag'> webmaster guidelines </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='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_US' 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_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2018/02/how-listening-to-our-users-helped-us.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2018/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_US' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/UX?hl=en_US' rel='tag'> UX </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en_US' rel='tag'> webmaster community </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='30395514059631024' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2018/01/introducing-new-search-console.html?hl=en_US' itemprop='url' title='Introducing the new Search Console'> Introducing the new Search Console </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Monday, January 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"> A few months ago 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 experience to a limited number of users. We are now starting to release this beta version to all users of Search Console, so that everyone can explore this simplified process of optimizing a website's presence on Google Search. The functionality will include <a href="https://support.google.com/webmasters/answer/7576553">Search performance</a>, <a href="https://support.google.com/webmasters/answer/7440203">Index Coverage</a>, <a href="https://support.google.com/webmasters/answer/7450883">AMP status</a>, and <a href="https://support.google.com/webmasters/answer/7552505">Job posting</a> reports. We will send a message once your site is ready in the new Search Console.<br /> We started by adding some of the most popular functionality in the new Search Console (which can now be used in your day-to-day flow of addressing these topics). We are not done yet, so over the course of the year the new Search Console (beta) will continue to add functionality from the classic Search Console. Until the new Search Console is complete, <strong>both versions will live side-by-side</strong> and will be easily interconnected via links in the navigation bar, so you can use both.<br /> The new Search Console was rebuilt from the ground up by surfacing the most actionable insights and creating an interaction model which guides you through the process of fixing any pending issues. We’ve also added ability to share reports within your own organization in order to simplify internal collaboration.<br /> <a name="performance"></a><h2 id="perf"> Search Performance: with 16 months of data!</h2> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgv3ujhM_2fUrjBihDCG90z7-jPT4qu-8BGl3XAPyYDBASBvR72f7kEil6QlKkEve3EpQmw8jhAit28IMmLlR-eQvq_8qrfoT2tWQNFRAEdxU13dujjDK-Bpe2uvbI-ffLNskRL/s1600/sc01.png" imageanchor="1"><img border="0" data-original-height="730" data-original-width="1024" height="285" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgv3ujhM_2fUrjBihDCG90z7-jPT4qu-8BGl3XAPyYDBASBvR72f7kEil6QlKkEve3EpQmw8jhAit28IMmLlR-eQvq_8qrfoT2tWQNFRAEdxU13dujjDK-Bpe2uvbI-ffLNskRL/s600/sc01.png" width="400" /></a> <br /> <br /> If you've been a fan of Search Analytics, you'll love the new <a href="https://support.google.com/webmasters/answer/7576553">Search Performance report</a>. Over the years, users have been consistent in asking us for more data in Search Analytics. With the new report, you'll have 16 months of data, to make analyzing longer-term trends easier and enable year-over-year comparisons. In the near future, this data will also be available via the <a href="https://developers.google.com/webmaster-tools/search-console-api-original/">Search Console API</a>.<br /> <h2 id="index"> Index Coverage: a comprehensive view on Google's indexing</h2> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEizzeLL6YqCLserAFsxQKoUw_mLXbFIoqKd5d-uE_DtFppji5JQYBL8O8U-pB9kQo_pd2sI_TYlBEJ7EPLSfu2A7DZz-K_WKX1iQTX0dc2MSYFaCE2D1eBDfOrwaoJUbq2QgouO/s1600/sc02.png" imageanchor="1"><img border="0" data-original-height="730" data-original-width="1024" height="285" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEizzeLL6YqCLserAFsxQKoUw_mLXbFIoqKd5d-uE_DtFppji5JQYBL8O8U-pB9kQo_pd2sI_TYlBEJ7EPLSfu2A7DZz-K_WKX1iQTX0dc2MSYFaCE2D1eBDfOrwaoJUbq2QgouO/s600/sc02.png" width="400" /></a> <br /> <br /> The updated <a href="https://support.google.com/webmasters/answer/7440203">Index Coverage report</a> gives you insight into the indexing of URLs from your website. It shows correctly indexed URLs, warnings about potential issues, and reasons why Google isn't indexing some URLs. The report is built on our new Issue tracking functionality that alerts you when new issues are detected and helps you monitor their fix. <br /> So how does that work?<br /> <ol> <li>When you drill down into a specific issue you will see a sample of URLs from your site. Clicking on error URLs brings up the <strong>page details</strong> with links to diagnostic-tools that help you understand what is the source of the problem. </li> <li>Fixing Search issues often involves multiple teams within a company. Giving the right people access to information about the current status, or about issues that have come up there, is critical to improving an implementation quickly. Now, within most reports in the new Search Console, you can do that with the <strong>share button</strong> on top of the report which will create a shareable link to the report. Once things are resolved, you can disable sharing just as easily.</li> <li>The new Search Console can also help you confirm that you've resolved an issue, and help us to update our index accordingly. To do this, select a flagged issue, and click <strong>validate fix</strong>. Google will then crawl and reprocess the affected URLs with a higher priority, helping your site to get back on track faster than ever. </li> <li>The Index Coverage report works best for sites that submit <a href="https://support.google.com/webmasters/answer/183668">sitemap files</a>. Sitemap files are a great way to let search engines know about new and updated URLs. Once you've submitted a sitemap file, you can now use the <strong>sitemap filter</strong> over the Index Coverage data, so that you're able to focus on an exact list of URLs. </li> </ol> <a name="enhancements"></a><h2 id="enhance"> Search Enhancements: improve your AMP and Job Postings pages</h2> The new Search Console is also aimed at helping you implement Search Enhancements such as <a href="https://support.google.com/webmasters/answer/7450883">AMP</a> and <a href="https://support.google.com/webmasters/answer/7552505">Job Postings</a> (more to come). These reports provide details into the specific errors and warnings that Google identified for these topics. In addition to the functionally described in the index coverage report, we augmented the reports with two extra features:<br /> <ul> <li>The first feature is aimed at providing faster feedback in the process of fixing an issue. This is achieved by running several instantaneous tests once you click the <strong>validate fix</strong> button. If your pages don’t pass this test we provide you with an immediate notification, otherwise we go ahead and reprocess the rest of the affected pages. </li> <li>The second new feature is aimed at providing positive feedback during the fix process by expanding the <strong>validation log</strong> with a list of URLs that were identified as fixed (in addition to URLs that failed the validation or might still be pending).</li> </ul> Similar to the AMP report, the new Search Console provides a <a href="https://support.google.com/webmasters/answer/7552505">Job postings report</a>. If you have jobs listings on your website, you may be eligible to have those shown directly through <a href="https://webmasters.googleblog.com/2017/06/connect-to-job-seekers-with-google.html">Google for Jobs</a> (currently only available in certain locations). <br /> <h2> Feedback welcome</h2> We couldn’t have gotten so far without the ongoing feedback from our diligent trusted testers (we plan to share more on how their feedback helped us dramatically improve Search Console). However, <strong>your continued feedback is critical for us</strong>: if there's something you find confusing or wrong, or if there's something you really like, <strong>please let us know through the feedback feature</strong> in the sidebar. Also note that the mobile experience in the new Search Console is still a work in progress.<br /> We want to end this blog sharing an encouraging response we got from a user who has been testing the new Search Console recently:<br /> <br /> <blockquote> "The UX of new Search Console is clean and well laid out, everything is where we expect it to be. I can even kick-off validation of my fixes and get email notifications with the result. It’s been a massive help in fixing up some pesky AMP errors and warnings that were affecting pages on our site. On top of all this, the Search Analytics report now extends to 16 months of data which is a total game changer for us" - Noah Szubski, Chief Product Officer, DailyMail.com</blockquote> <br /> Are there any other tools that would make your life as a webmaster easier? Let us know in the comments here, and feel free to jump into our <a href="https://support.google.com/webmasters/go/community">webmaster help forums</a> to discuss your ideas with others!<br /> <br /> <span class="byline-author">Posted by John Mueller, Ofir Roval and Hillel Maoz</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> A few months ago 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 experience to a limited number of users. We are now starting to release this beta version to all users of Search Console, so that everyone can explore this simplified process of optimizing a website's presence on Google Search. The functionality will include <a href="https://support.google.com/webmasters/answer/7576553">Search performance</a>, <a href="https://support.google.com/webmasters/answer/7440203">Index Coverage</a>, <a href="https://support.google.com/webmasters/answer/7450883">AMP status</a>, and <a href="https://support.google.com/webmasters/answer/7552505">Job posting</a> reports. We will send a message once your site is ready in the new Search Console.<br /> We started by adding some of the most popular functionality in the new Search Console (which can now be used in your day-to-day flow of addressing these topics). We are not done yet, so over the course of the year the new Search Console (beta) will continue to add functionality from the classic Search Console. Until the new Search Console is complete, <strong>both versions will live side-by-side</strong> and will be easily interconnected via links in the navigation bar, so you can use both.<br /> The new Search Console was rebuilt from the ground up by surfacing the most actionable insights and creating an interaction model which guides you through the process of fixing any pending issues. We’ve also added ability to share reports within your own organization in order to simplify internal collaboration.<br /> <a name="performance"></a><h2 id="perf"> Search Performance: with 16 months of data!</h2> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgv3ujhM_2fUrjBihDCG90z7-jPT4qu-8BGl3XAPyYDBASBvR72f7kEil6QlKkEve3EpQmw8jhAit28IMmLlR-eQvq_8qrfoT2tWQNFRAEdxU13dujjDK-Bpe2uvbI-ffLNskRL/s1600/sc01.png" imageanchor="1"><img border="0" data-original-height="730" data-original-width="1024" height="285" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgv3ujhM_2fUrjBihDCG90z7-jPT4qu-8BGl3XAPyYDBASBvR72f7kEil6QlKkEve3EpQmw8jhAit28IMmLlR-eQvq_8qrfoT2tWQNFRAEdxU13dujjDK-Bpe2uvbI-ffLNskRL/s600/sc01.png" width="400" /></a> <br /> <br /> If you've been a fan of Search Analytics, you'll love the new <a href="https://support.google.com/webmasters/answer/7576553">Search Performance report</a>. Over the years, users have been consistent in asking us for more data in Search Analytics. With the new report, you'll have 16 months of data, to make analyzing longer-term trends easier and enable year-over-year comparisons. In the near future, this data will also be available via the <a href="https://developers.google.com/webmaster-tools/search-console-api-original/">Search Console API</a>.<br /> <h2 id="index"> Index Coverage: a comprehensive view on Google's indexing</h2> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEizzeLL6YqCLserAFsxQKoUw_mLXbFIoqKd5d-uE_DtFppji5JQYBL8O8U-pB9kQo_pd2sI_TYlBEJ7EPLSfu2A7DZz-K_WKX1iQTX0dc2MSYFaCE2D1eBDfOrwaoJUbq2QgouO/s1600/sc02.png" imageanchor="1"><img border="0" data-original-height="730" data-original-width="1024" height="285" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEizzeLL6YqCLserAFsxQKoUw_mLXbFIoqKd5d-uE_DtFppji5JQYBL8O8U-pB9kQo_pd2sI_TYlBEJ7EPLSfu2A7DZz-K_WKX1iQTX0dc2MSYFaCE2D1eBDfOrwaoJUbq2QgouO/s600/sc02.png" width="400" /></a> <br /> <br /> The updated <a href="https://support.google.com/webmasters/answer/7440203">Index Coverage report</a> gives you insight into the indexing of URLs from your website. It shows correctly indexed URLs, warnings about potential issues, and reasons why Google isn't indexing some URLs. The report is built on our new Issue tracking functionality that alerts you when new issues are detected and helps you monitor their fix. <br /> So how does that work?<br /> <ol> <li>When you drill down into a specific issue you will see a sample of URLs from your site. Clicking on error URLs brings up the <strong>page details</strong> with links to diagnostic-tools that help you understand what is the source of the problem. </li> <li>Fixing Search issues often involves multiple teams within a company. Giving the right people access to information about the current status, or about issues that have come up there, is critical to improving an implementation quickly. Now, within most reports in the new Search Console, you can do that with the <strong>share button</strong> on top of the report which will create a shareable link to the report. Once things are resolved, you can disable sharing just as easily.</li> <li>The new Search Console can also help you confirm that you've resolved an issue, and help us to update our index accordingly. To do this, select a flagged issue, and click <strong>validate fix</strong>. Google will then crawl and reprocess the affected URLs with a higher priority, helping your site to get back on track faster than ever. </li> <li>The Index Coverage report works best for sites that submit <a href="https://support.google.com/webmasters/answer/183668">sitemap files</a>. Sitemap files are a great way to let search engines know about new and updated URLs. Once you've submitted a sitemap file, you can now use the <strong>sitemap filter</strong> over the Index Coverage data, so that you're able to focus on an exact list of URLs. </li> </ol> <a name="enhancements"></a><h2 id="enhance"> Search Enhancements: improve your AMP and Job Postings pages</h2> The new Search Console is also aimed at helping you implement Search Enhancements such as <a href="https://support.google.com/webmasters/answer/7450883">AMP</a> and <a href="https://support.google.com/webmasters/answer/7552505">Job Postings</a> (more to come). These reports provide details into the specific errors and warnings that Google identified for these topics. In addition to the functionally described in the index coverage report, we augmented the reports with two extra features:<br /> <ul> <li>The first feature is aimed at providing faster feedback in the process of fixing an issue. This is achieved by running several instantaneous tests once you click the <strong>validate fix</strong> button. If your pages don’t pass this test we provide you with an immediate notification, otherwise we go ahead and reprocess the rest of the affected pages. </li> <li>The second new feature is aimed at providing positive feedback during the fix process by expanding the <strong>validation log</strong> with a list of URLs that were identified as fixed (in addition to URLs that failed the validation or might still be pending).</li> </ul> Similar to the AMP report, the new Search Console provides a <a href="https://support.google.com/webmasters/answer/7552505">Job postings report</a>. If you have jobs listings on your website, you may be eligible to have those shown directly through <a href="https://webmasters.googleblog.com/2017/06/connect-to-job-seekers-with-google.html">Google for Jobs</a> (currently only available in certain locations). <br /> <h2> Feedback welcome</h2> We couldn’t have gotten so far without the ongoing feedback from our diligent trusted testers (we plan to share more on how their feedback helped us dramatically improve Search Console). However, <strong>your continued feedback is critical for us</strong>: if there's something you find confusing or wrong, or if there's something you really like, <strong>please let us know through the feedback feature</strong> in the sidebar. Also note that the mobile experience in the new Search Console is still a work in progress.<br /> We want to end this blog sharing an encouraging response we got from a user who has been testing the new Search Console recently:<br /> <br /> <blockquote> "The UX of new Search Console is clean and well laid out, everything is where we expect it to be. I can even kick-off validation of my fixes and get email notifications with the result. It’s been a massive help in fixing up some pesky AMP errors and warnings that were affecting pages on our site. On top of all this, the Search Analytics report now extends to 16 months of data which is a total game changer for us" - Noah Szubski, Chief Product Officer, DailyMail.com</blockquote> <br /> Are there any other tools that would make your life as a webmaster easier? Let us know in the comments here, and feel free to jump into our <a href="https://support.google.com/webmasters/go/community">webmaster help forums</a> to discuss your ideas with others!<br /> <br /> <span class="byline-author">Posted by John Mueller, Ofir Roval and Hillel Maoz</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 Search Console&url=https://webmasters.googleblog.com/2018/01/introducing-new-search-console.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2018/01/introducing-new-search-console.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2018/01/introducing-new-search-console.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_US' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/products%20and%20services?hl=en_US' rel='tag'> products and services </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20queries?hl=en_US' rel='tag'> search queries </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/sitemaps?hl=en_US' rel='tag'> sitemaps </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='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_US' 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_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/08/a-sneak-peek-at-two-experimental.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/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_US' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/products%20and%20services?hl=en_US' rel='tag'> products and services </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US' rel='tag'> search console </a> </span> </div> </div> </div> <div class='blog-pager' id='blog-pager'> <a class='home-link' href='https://webmasters.googleblog.com/?hl=en_US'> <i class='material-icons'>  </i> </a> <i class='material-icons disabled'>  </i> <span id='blog-pager-older-link'> <a class='blog-pager-older-link' href='https://webmasters.googleblog.com/search/label/search%20console?updated-max=2017-08-01T06:39:00-07:00&max-results=20&start=18&by-date=false&hl=en_US' id='Blog1_blog-pager-older-link' title='Older Posts'> <i class='material-icons'>  </i> </a> </span> </div> <div class='clear'></div> </div></div> </div> </div> <div class='col-right'> <div class='section' id='sidebar-top'><div class='widget HTML' data-version='1' id='HTML9'> <div class='widget-content'> <a href="https://www.google.com/webmasters/tools/mobile-friendly/?utm_source=wmc-blog&utm_medium=referral&utm_campaign=blog-nav"><img src="https://lh3.googleusercontent.com/-osGJupx0-HY/VQta1nmaAPI/AAAAAAAACfs/UdMPzubsXFk/w80-h1368-no/blog%2Bpromo.png" align="left" width="80" /></a> Hey! <a href="https://search.google.com/test/mobile-friendly">Check here if your site is mobile-friendly.</a> </div> <div class='clear'></div> </div><div class='widget HTML' data-version='1' id='HTML10'> <div class='widget-content'> <div class='searchBox'> <input type='text' title='Search This Blog' placeholder='Search blog ...' /> </div> </div> <div class='clear'></div> </div></div> <div id='aside'> <div class='section' id='sidebar'><div class='widget Label' data-version='1' id='Label1'> <div class='tab'> <img class='sidebar-icon' src='data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAYpJREFUeNrs2aFuwzAQBmAvKRkMKRjZA4QMDJaWFgyMjuzFRg37DIUlA3uFkoGQSaWzJU+tpri5O9+l/zSfdFJlpe59yTmyVedq1PjfcZMZ70NuQnaF8w8htyE/rABtpviXkLcK88c5HhLkMBfgVan43zfFBNGMjHVGT/s55KP2pAvidbGHd+nzKt1RKSLG3rKF1iPFv6UWiPke8i7kEqGdGsI1O+LYVdqJAjgirwkKYD0ytkJBUNbAMvX8V3q9PhUsYvU1sWD8SO/sQvx2ahxOiNoJCSBCoAHYCEQAC4EKICOQASQEOmAS8RcAFxFN5hiIiugpgC3wk9hQAHH/70EBHXUN7IER5EWMiBgo2+nzOKQv9SCAeEM/OQAkhE/ncccFICB87qzQMia5FsJfOui0zMnmRvipU1ormHQuxGTxUsAcCFLxJQBLBLn4UoAFglW8BkATwS5eC6CBEBWvCShBiIvXBkgQRcVbADiI4uKtABSESvGWgB9EzHt3+tNwyO0qa9SoIYtvAQYAqDJhaWWeMecAAAAASUVORK5CYII='/> <h2> Labels </h2> <i class='material-icons arrow'>  </i> </div> <div class='widget-content list-label-widget-content'> <ul> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/accessibility?hl=en_US'> accessibility </a> <span dir='ltr'> 10 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/advanced?hl=en_US'> advanced </a> <span dir='ltr'> 195 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/AMP?hl=en_US'> AMP </a> <span dir='ltr'> 13 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Android?hl=en_US'> Android </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/API?hl=en_US'> API </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/apps?hl=en_US'> apps </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/autocomplete?hl=en_US'> autocomplete </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/beginner?hl=en_US'> beginner </a> <span dir='ltr'> 173 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/CAPTCHA?hl=en_US'> CAPTCHA </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Chrome?hl=en_US'> Chrome </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/cms?hl=en_US'> cms </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en_US'> crawling and indexing </a> <span dir='ltr'> 158 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/encryption?hl=en_US'> encryption </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/events?hl=en_US'> events </a> <span dir='ltr'> 51 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=en_US'> feedback and communication </a> <span dir='ltr'> 83 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/forums?hl=en_US'> forums </a> <span dir='ltr'> 5 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/general%20tips?hl=en_US'> general tips </a> <span dir='ltr'> 90 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/geotargeting?hl=en_US'> geotargeting </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20Assistant?hl=en_US'> Google Assistant </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20I%2FO?hl=en_US'> Google I/O </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20Images?hl=en_US'> Google Images </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20News?hl=en_US'> Google News </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hacked%20sites?hl=en_US'> hacked sites </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hangout?hl=en_US'> hangout </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hreflang?hl=en_US'> hreflang </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/https?hl=en_US'> https </a> <span dir='ltr'> 5 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/images?hl=en_US'> images </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/intermediate?hl=en_US'> intermediate </a> <span dir='ltr'> 205 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/interstitials?hl=en_US'> interstitials </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/javascript?hl=en_US'> javascript </a> <span dir='ltr'> 8 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/job%20search?hl=en_US'> job search </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/localization?hl=en_US'> localization </a> <span dir='ltr'> 21 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/malware?hl=en_US'> malware </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/mobile?hl=en_US'> mobile </a> <span dir='ltr'> 63 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US'> mobile-friendly </a> <span dir='ltr'> 14 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/nohacked?hl=en_US'> nohacked </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/performance?hl=en_US'> performance </a> <span dir='ltr'> 17 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/product%20expert?hl=en_US'> product expert </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/product%20experts?hl=en_US'> product experts </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/products%20and%20services?hl=en_US'> products and services </a> <span dir='ltr'> 63 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/questions?hl=en_US'> questions </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/ranking?hl=en_US'> ranking </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/recipes?hl=en_US'> recipes </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rendering?hl=en_US'> rendering </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Responsive%20Web%20Design?hl=en_US'> Responsive Web Design </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rich%20cards?hl=en_US'> rich cards </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rich%20results?hl=en_US'> rich results </a> <span dir='ltr'> 10 </span> </li> <li> <span dir='ltr'> search console </span> <span dir='ltr'> 35 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20for%20beginners?hl=en_US'> search for beginners </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20queries?hl=en_US'> search queries </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en_US'> search results </a> <span dir='ltr'> 140 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/security?hl=en_US'> security </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/seo?hl=en_US'> seo </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/sitemaps?hl=en_US'> sitemaps </a> <span dir='ltr'> 46 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/speed?hl=en_US'> speed </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=en_US'> structured data </a> <span dir='ltr'> 33 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/summit?hl=en_US'> summit </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/TLDs?hl=en_US'> TLDs </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/url%20removals?hl=en_US'> url removals </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/UX?hl=en_US'> UX </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/verification?hl=en_US'> verification </a> <span dir='ltr'> 8 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/video?hl=en_US'> video </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en_US'> webmaster community </a> <span dir='ltr'> 24 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20forum?hl=en_US'> webmaster forum </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines?hl=en_US'> webmaster guidelines </a> <span dir='ltr'> 57 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US'> webmaster tools </a> <span dir='ltr'> 177 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmasters?hl=en_US'> webmasters </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/youtube%20channel?hl=en_US'> youtube channel </a> <span dir='ltr'> 6 </span> </li> </ul> <div class='clear'></div> </div> </div><div class='widget BlogArchive' data-version='1' id='BlogArchive1'> <div class='tab'> <i class='material-icons icon'>  </i> <h2> Archive </h2> <i class='material-icons arrow'>  </i> </div> <div class='widget-content'> <div id='ArchiveList'> <div id='BlogArchive1_ArchiveList'> <ul class='hierarchy'> <li class='archivedate expanded'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy toggle-open'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/?hl=en_US'> 2020 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate expanded'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/?hl=en_US'> 2019 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/?hl=en_US'> 2018 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/?hl=en_US'> 2017 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/?hl=en_US'> 2016 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/?hl=en_US'> 2015 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/?hl=en_US'> 2014 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/?hl=en_US'> 2013 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/?hl=en_US'> 2012 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/?hl=en_US'> 2011 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/?hl=en_US'> 2010 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/?hl=en_US'> 2009 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/?hl=en_US'> 2008 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/?hl=en_US'> 2007 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/?hl=en_US'> 2006 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> </div> </div> <div class='clear'></div> </div> </div><div class='widget HTML' data-version='1' id='HTML6'> <div class='widget-content'> <a href="https://googlewebmastercentral.blogspot.com/atom.xml"> <img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAihJREFUeNrsWa9Pw0AU7viRMDFRBAkzJDMIBIhJJhCzk7NILIqMv4AEhdz+BCY3OYssAlGBoAJREpZwAlHEBO8lr8nSvNeVbu1dyX3JlzTrXfa+u/e9d7c5joWFhYVO1Fa8PwH2gK6m+BRwAvSlAdsrgr8E1jUuMH73GTAEzrkBWymTewZlihhLmgDXIAFuHgGVQOUF7OSYM1p6PgTuA1vAZlUEvAnPdapcMY0VICECekQ0XRfYrqoHsAGNgXfAoMomRiFDEhOZkkL3S88hMaB2LwXp0bj+ps2edpToZpjfoIDQtBeU+xjoDzP2G/gCPKZ5f8WsCAFJoJgOCcFdWSTeL9YQMSvTA1h9BkI5jaiXhLpSCL/8mVZY0UpyJ9ZdOkniu1dmJ96BpzQu9w6s28gcOq9j6pwLdR8/36NK5CQKwJSMrb2MhhSglBpt4UjsrdsnNu0B3J0HCozbCc4TjyY2srEgos/4RQljCzNxl4ireQD8FOq+T+W0mTB2g7njhlR+Sy2jsXFvU658U8YTbeaGpdIu7mWkEAq5ZtIjIhFZdtfX7QHckSvB2B6zC3VdAkZk0kAQwaXTk/CzTXK3wjIExCs6ZJpTnE4uY1KV+KzFzA3KTiFPENHJkOPcsfpLhwe4btoSuvUqAR+6TOxlCE6ZfKUsJLgsqGW8OpqAGx2X+sLxrwUog+JUeQRMDBIwyXOcnlPtPnL0/UsT/8LnOxYWFhZG4leAAQAAQHEaYuzHbAAAAABJRU5ErkJggg==" class="sidebar-icon" /> <h2>Feed</h2> </a> </div> <div class='clear'></div> </div></div> <div class='section' id='sidebar-bottom'><div class='widget HTML' data-version='1' id='HTML5'> <div class='widget-content'> <div class='followgooglewrapper'> <script src="https://apis.google.com/js/plusone.js"></script></div> <div class="g-ytsubscribe class='followgooglewrapper'" data-channel="GoogleWebmasterHelp" data-layout="full"></div> <div class="share followgooglewrapper"> <button data-href="https://twitter.com/intent/follow?original_referer=https://googlewebmastercentral.blogspot.com/&screen_name=googlewmc" onclick='sharingPopup(this);' id='twitter-share'><span class="twitter-follow">Follow @googlewmc</span></button> <script> function sharingPopup (button) { var url = button.getAttribute("data-href"); window.open( url,'popUpWindow','height=500,width=500,left=10,top=10,resizable=yes,scrollbars=yes,toolbar=yes,menubar=no,location=no,directories=no,status=yes'); } </script> </div> </div> <div class='clear'></div> </div><div class='widget HTML' data-version='1' id='HTML1'> <div class='widget-content'> Give us feedback in our <a href="https://support.google.com/webmasters/go/community">Product Forums</a>. </div> <div class='clear'></div> </div><div class='widget HTML' data-version='1' id='HTML8'> <h2 class='title'> Subscribe via email </h2> <div class='widget-content'> <form #nsubmit="window.open('https://www.feedburner.com/fb/a/emailverifySubmit?feedId=1092589', 'popupwindow', 'scrollbars=yes,width=550,height=520');return true" action="https://www.feedburner.com/fb/a/emailverify" style="border:1px solid #ccc;padding:3px;text-align:center;" target="popupwindow" method="post"><p>Enter your email address:</p><p><input style="width:140px" name="email" type="text"/></p><input value="https://feeds.feedburner.com/~e?ffid=1092589" name="url" type="hidden"/><input value="Official Google Webmaster Central Blog" name="title" type="hidden"/><input value="en_US" name="loc" type="hidden"/><input value="Subscribe" type="submit"/><p>Delivered by <a href="https://www.feedburner.com" target="_blank">FeedBurner</a></p></form> </div> <div class='clear'></div> </div></div> </div> </div> <div style='clear:both;'></div> </div>  <div class='google-footer-outer loading'> <div id='google-footer'> <a href='//www.google.com/'> <img class='google-logo-dark' height='36' src='data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAALgAAABICAYAAABFoT/eAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAACLVJREFUeNrsXd+L20YQ3vOprdLqiMXFXE2qB7dcwEcTSB7ykIc+9A/PQx/yEMq1TWhNuYIpJriNr7XpmZ5IxFEvmW2EKs3Ornb1w50PxIFP0kiz387OzM6uhGAwGAxGP3Ho+f7x7ri1O7LdccPqZjSNA4dEHsLfaHcEFedJom93x9Xu2OyOFTcBo6sED3fHZHeMEELrkAHJF0B8Rr+gDFsZ5n0luLTQ95AXs4W06D/tjpR50xtM4CjD0y48YGB4rnyZxNOzyA7zBHr+nLnDaJLg0mo/ALekCasg3Z4XbM0ZdTEgnDPeHY8bIne+Qz2GvwyGNwsuyT218KWvIIBMcwGpLiipcolecjMxfBDchNyS1EvxLiOSIecp31q6IJ/C3yrIrMqMm4jhg+AxkdwbIO3aUO4KjqqMjCT3uaazMBhWBJfuxH3CtRfiXf66DhSRZWbmlMnNaILgZxrXJQO/eO3wORZwvwm4JUxuhheCjzVBYAbW1ces45YDSoZrFNOEE835M8FT6oyeEnws8Fz3QnBxFKPHBMem4GU+m6fPGb0leCTwWcM5B36MPgeZI01gudyDdw3hPeXfo8L/rmCUWnuMMdqUL2WqWeRbhf+twfVsO7YagZGNC79fw7OthEVtkiJ4jJzTd3KPwf3CRqhhiTu23AP5sl0/0xiwISQXpNwLIJK87mHF+U8ddzzdmgKlGzlPYjyxGJQouIhNT4k9AqWEFkqfguIvagTWbcq3KW1WE3xS3m8NtA9WS451xofwjKT5kkDoK/b6mDk5FfXr1lWDL4BofZEv2/SRsK/EHGlGdBdu8QNRb8HMCFwt7Yy3DDI/QP7fx5z3VLhdlJEIs4rKNuXXJXdxZPdB7kfCzWqwCO4V1LHgLjInX3tQ1KzCR52Cz+vDj1dydeRuS74rcvs2Pi6fT5H8OaaUQPQPYcWwRSGXyhhscn5dpAnEFMkuEZetbfkTAnlSuH4DxisE+aMGeJAQ3lFl7C4LJE6QWCaCd583ORQ1jYAwjFctal7nOs2ZZvicwvlZx+RHGrcoAwKUVX8uwcc/9TT65INeDOr5shL9LDRB6QTeIy3zwfdh3WOi6axLCEhSjXU7F3h6LqggUtvyJxpynwu8tDkD98fXApOxRj8zoZ9MnGveYVIVZKaGrkBXCY65BCYNN9NkjpKOyQ81Q79JgdxS+Jn3SDTEXRI7SWzaiSTB32oI3nU3BvMfM0urhOVYgwKhuiAfc4tM07wXwm1ZRoQYSl2NUwiu01fEAHVcpixd745FvVz4dzUUc0o8rwoLy8ZSwU6CyFx1RP5II9+1bFPEFs9HWbNLiimDXE+vCm7u1CS47cofzD3aEhVY57mxRo5zlqdt+RFC1JUH2S7bcVXg4liTMakaBZZVxiTICRoivcn1sEUBlk24JmaC6kxUbYmWoqvyfck2xZGGnDFYa9MMzkYQ1ijkCX6qidybrgePiQ0QIQqoi6qRLeqQfIoRsEHaQJLBdHOnLGetSdm/IPcymJuS1PAnbQPH0MOw/39C1vL11DiLOqIsbDI8QcHvGiLnySi2qUXBicaqUSxN5LEB0g7Jt3ENXJLPJ5S1tnaZBoWbpRqrmjRE7qHmpSmNHdQcYrEUadoh+TbBnc9ri7iycI1kzPeNcLDIvbiqXpez9Tmdq6zGREPuzECBoxrPMiI2WtvyNwhJba2wy3JZ6ky5dD1lSvmZS3e4SPA1wcf1VTFHKX+cGwZzdUYcqpvUtvwrD/InDttVlyZeAKlNN5MKbAiurHhKIPlUuJvlTCCiDjSKSCsUmCFWbGLZwCESfK07JB8LvMYWVtw0D00JEHV8Mq2HkqPbE0oHLvvK2g0o8ETg+4cfwTlZDT9JDoWygu4uQQE/ivIvtcnfPkaCqhiupz7jWOAzqL/vjtcdkv9G4MVMt+EaylfuImiPAXEUjRF3pjjaHiPPZ6If9TGGAO4ZY0am6jOCb+DQ+ZCqLkIpOIPrdNfIjnFPY6nyFut7TS/fanrziOBOKMupKw94WaLMtuVnSFt9CPrWWdJE6PeltCX432DEBoh+5Dv8RRhdis8YAv9uyq4/JAwtlEApgBe9Cw9xDD3tdk4Jn0MDfiHwPHcRPxBePCMER3GuIx7kGlv9fkZ4V9lolx2Uv4X7hEj7qJ3LDoAMGbTRMRibu4L2xQ8bgt8AyU+Q+x7nYrvDnH4iuO5LxKsYwPVbkPMvKF9Zky9wXzRfVWizi62r9X5VHf55h+WHhDjGBZ4WRhyTr6z5SlCoLMxLSpBZFsQ9F80uQFbF/6aFWi+Ev51vzzsuX+msyzuQXXjUz8zEBy+zpq9yweXAoxJW4JbYrDS6gYDqGHxPl+TKeiBfxj9/EBIElPYeOA4y8/qRQfknjvSzgRgtq0Pw/M1eQeMdOSb2Bnrhr6Led+1vcp2x7oTFHMnedFW+Ivlty062BUt74oHgSj+vHepnhunn0JJAMtBZgDI/qmGtMujRv8DDpo47zBJ8UtPOuAR/7rKn8t9AJ0tBdmBAmJ/Fu71yxp4I3qh+DhyRqbi5Y1ShVPlSb8X7bRNcfgZFl+WRGYo7uecrWq1r8X5bhmzP5OdlDwsGRm1suSxkg5rYm7ConyGQ3Zl+DgSD8V/kPwrWBMG9YcBtyShBnTLdTiHgttw7qAW7cqh/ZnmPKr/6ignOaKsdyxbsToT5UkPsW00bJjijDXficcX/JsLs6w2BwGtherdckH3w/kNXRPVI0OqJQoHX42/66IMfMj/2huRjxIidgKV/W0JS+bsstDoTeAHcrI8E5zTh/sDkqxL5rZup55/3USlswfcHf4IrQplVDgW9XFlOqnwr6pVPMMEZTuC60EttvdzbLbaZ4PsFVa3nohhO+vW+yn/ZB2fUhpysmQrzBcTSai9EszuZMcEZ1lCFVrp9zGXhm69iLyY4oxFIa178lPe12I/P2DAYDAaDwWAwGAwGg8FgMBgMBoPBYDD2Cf8IMADDRGoQTe+E9AAAAABJRU5ErkJggg==' style='margin-top: -16px;' width='92'/> </a> <ul> <li> <a href='//www.google.com/'> Google </a> </li> <li> <a href='//www.google.com/policies/privacy/'> Privacy </a> </li> <li> <a href='//www.google.com/policies/terms/'> Terms </a> </li> </ul> </div> </div> <script type='text/javascript'> //<![CDATA[ // Social sharing popups. var postEl = document.getElementsByClassName('social-wrapper'); var postCount = postEl.length; for(i=0; i<postCount;i++){ postEl[i].addEventListener("click", function(event){ var postUrl = this.getAttribute("data-href"); window.open( postUrl,'popUpWindow','height=500,width=500,left=10,top=10,resizable=yes,scrollbars=yes,toolbar=yes,menubar=no,location=no,directories=no,status=yes'); });} //]]> </script> <script type='text/javascript'> //<![CDATA[ var BreakpointHandler = function() { this.initted = false; this.isHomePage = false; this.isMobile = false; }; BreakpointHandler.prototype.finalizeSummary = function(summaryHtml, lastNode) { // Use $.trim for IE8 compatibility summaryHtml = $.trim(summaryHtml).replace(/(<br>|\s)+$/,''); if (lastNode.nodeType == 3) { var lastChar = summaryHtml.slice(-1); if (!lastChar.match(/[.”"?]/)) { if (!lastChar.match(/[A-Za-z]/)) { summaryHtml = summaryHtml.slice(0, -1); } summaryHtml += ' ...'; } } else if (lastNode.nodeType == 1 && (lastNode.nodeName == 'I' || lastNode.nodeName == 'A')) { summaryHtml += ' ...'; } return summaryHtml; }; BreakpointHandler.prototype.generateSummaryFromContent = function(content, numWords) { var seenWords = 0; var summaryHtml = ''; for (var i=0; i < content.childNodes.length; i++) { var node = content.childNodes[i]; var nodeText; if (node.nodeType == 1) { if (node.hasAttribute('data-about-pullquote')) { continue; } nodeText = node.textContent; if (nodeText === undefined) { // innerText for IE8 nodeText = node.innerText; } if (node.nodeName == 'DIV' || node.nodeName == 'B') { // Don't end early if we haven't seen enough words. if (seenWords < 10) { continue; } if (i > 0) { summaryHtml = this.finalizeSummary(summaryHtml, content.childNodes[i-1]); } break; } summaryHtml += node.outerHTML; } else if (node.nodeType == 3) { nodeText = node.nodeValue; summaryHtml += nodeText + ' '; } var words = nodeText.match(/\S+\s*/g); if (!words) { continue; } var remain = numWords - seenWords; if (words.length >= remain) { summaryHtml = this.finalizeSummary(summaryHtml, node); break; } seenWords += words.length; } return summaryHtml; }; BreakpointHandler.prototype.detect = function() { var match, pl = /\+/g, search = /([^&=]+)=?([^&]*)/g, decode = function (s) { return decodeURIComponent(s.replace(pl, " ")); }, query = window.location.search.substring(1); var urlParams = {}; while (match = search.exec(query)) urlParams[decode(match[1])] = decode(match[2]); this.isListPage = $('html').hasClass('list-page'); this.isMobile = urlParams['m'] === '1'; this.isHomePage = window.location.pathname == '/'; }; BreakpointHandler.prototype.initContent = function() { var self = this; $('.post').each(function(index) { var body = $(this).children('.post-body')[0]; var content = $(body).children('.post-content')[0]; $(content).addClass('post-original'); var data = $(content).children('script').html(); data = self.rewriteForSSL(data); // If exists, extract specified editor's preview. var match = data.match(/([\s\S]+?)<div data-is-preview.+?>([\s\S]+)<\/div>/m); if (match) { data = match[1]; } // Prevent big images from loading when they aren't needed. // This must be done as a pre-injection step, since image loading can't be // canceled once embedded into the DOM. if (self.isListPage && self.isMobile) { data = data.replace(/<(img|iframe) .+?>/g, ''); } // Insert template to be rendered as nodes. content.innerHTML = data; if (self.isListPage) { var summary = document.createElement('div'); $(summary).addClass('post-content'); $(summary).addClass('post-summary'); body.insertBefore(summary, content); if (match) { // Use provided summary. summary.innerHTML = match[2]; } else { // Generate a summary. // Summary generation relies on DOM, so it must occur after content is // inserted into the page. summary.innerHTML = self.generateSummaryFromContent(content, 30); } // Add read more link to summary. var titleAnchor = $(this).find('.title a')[0]; var link = titleAnchor.cloneNode(true); link.innerHTML = 'Read More'; $(link).addClass('read-more'); summary.appendChild(link); } }); // Firefox does not allow for proper styling of BR. if (navigator.userAgent.indexOf('Firefox') > -1) { $('.post-content br').replaceWith('<span class="space"></span>'); } $('.loading').removeClass('loading'); }; BreakpointHandler.prototype.process = function() { if (!this.initted) { var makeInsecureImageRegex = function(hosts) { var whitelist = hosts.join('|').replace(/\./g,'\\.'); // Normal image tags, plus input images (yes, this is possible!) return new RegExp('(<(img|input)[^>]+?src=("|\'))http:\/\/(' + whitelist +')', 'g'); }; this.sslImageRegex = makeInsecureImageRegex(BreakpointHandler.KNOWN_HTTPS_HOSTS); this.sslImageCurrentDomainRegex = makeInsecureImageRegex([window.location.hostname]); this.detect(); this.initContent(); this.initted = true; } }; BreakpointHandler.KNOWN_HTTPS_HOSTS = [ "www.google.org", "www.google.com", "services.google.com", "blogger.com", "draft.blogger.com", "www.blogger.com", "photos1.blogger.com", "photos2.blogger.com", "photos3.blogger.com", "blogblog.com", "img1.blogblog.com", "img2.blogblog.com", "www.blogblog.com", "www1.blogblog.com", "www2.blogblog.com", "0.bp.blogspot.com", "1.bp.blogspot.com", "2.bp.blogspot.com", "3.bp.blogspot.com", "4.bp.blogspot.com", "lh3.googleusercontent.com", "lh4.googleusercontent.com", "lh5.googleusercontent.com", "lh6.googleusercontent.com", "themes.googleusercontent.com", ]; BreakpointHandler.prototype.rewriteForSSL = function(html) { // Handle HTTP -> HTTPS source replacement of images, movies, and other embedded content. return html.replace(this.sslImageRegex, '$1https://$4') .replace(this.sslImageCurrentDomainRegex, '$1//$4') .replace(/(<(embed|iframe)[^>]+?src=("|'))http:\/\/([^"']*?(youtube|picasaweb\.google)\.com)/g, '$1https://$4') // Slideshow SWF takes a image host, so we need to rewrite that parameter. .replace(/(<embed[^>]+?feed=http(?=[^s]))/g, '$1s'); }; $(document).ready(function() { var handler = new BreakpointHandler(); handler.process(); // Top-level navigation. $(".BlogArchive .tab").click(function(ev) { ev.preventDefault(); $(this).parent().toggleClass('active'); $(this).siblings().slideToggle(300); }); $(".Label .tab").click(function(ev) { ev.preventDefault(); $(this).parent().toggleClass('active'); $(this).siblings().slideToggle(300); }); // Blog archive year expansion. $('.BlogArchive .intervalToggle').click(function(ev) { ev.preventDefault(); if ($(this).parent().hasClass('collapsed')) { $(this).parent().removeClass('collapsed'); $(this).parent().addClass('expanded'); } else { $(this).parent().removeClass('expanded'); $(this).parent().addClass('collapsed'); } }); // Reverse order of months. $('.BlogArchive .intervalToggle + div').each(function(_, items) { var year = $(this); year.children().each(function(_, month) { year.prepend(month); }); }); // Set anchors to open in new tab. $('.post-content img').parent().each(function(_, node) { if (node.nodeName == 'A') { $(this).attr('target', '_blank'); } }); // Process search requests. $('.searchBox input').on("keypress", function(ev) { if (ev.which == 13) { window.location.href = 'https://www.google.com/search?q=site%3A' + window.location.hostname + '%20' + encodeURIComponent ($(this).val()); } }); }); //]]> </script> <script type="text/javascript" src="https://www.blogger.com/static/v1/widgets/984859869-widgets.js"></script> <script type='text/javascript'> window['__wavt'] = 'AOuZoY4SBGnE-JTvaKII18HLQrEBKEeYxg:1732423066021';_WidgetManager._Init('//www.blogger.com/rearrange?blogID\x3d32069983','//webmasters.googleblog.com/search/label/search%20console?hl\x3den_US','32069983'); _WidgetManager._SetDataContext([{'name': 'blog', 'data': {'blogId': '32069983', 'title': 'Official Google Webmaster Central Blog', 'url': 'https://webmasters.googleblog.com/search/label/search%20console?hl\x3den_US', 'canonicalUrl': 'https://webmasters.googleblog.com/search/label/search%20console', 'homepageUrl': 'https://webmasters.googleblog.com/?hl\x3den_US', 'searchUrl': 'https://webmasters.googleblog.com/search', 'canonicalHomepageUrl': 'https://webmasters.googleblog.com/', 'blogspotFaviconUrl': 'https://webmasters.googleblog.com/favicon.ico', 'bloggerUrl': 'https://www.blogger.com', 'hasCustomDomain': true, 'httpsEnabled': true, 'enabledCommentProfileImages': false, 'gPlusViewType': 'FILTERED_POSTMOD', 'adultContent': false, 'analyticsAccountNumber': 'UA-18009-4', 'encoding': 'UTF-8', 'locale': 'en-US', 'localeUnderscoreDelimited': 'en', 'languageDirection': 'ltr', 'isPrivate': false, 'isMobile': false, 'isMobileRequest': false, 'mobileClass': '', 'isPrivateBlog': false, 'isDynamicViewsAvailable': true, 'feedLinks': '\x3clink rel\x3d\x22alternate\x22 type\x3d\x22application/atom+xml\x22 title\x3d\x22Official Google Webmaster Central Blog - Atom\x22 href\x3d\x22https://webmasters.googleblog.com/feeds/posts/default\x22 /\x3e\n\x3clink rel\x3d\x22alternate\x22 type\x3d\x22application/rss+xml\x22 title\x3d\x22Official Google Webmaster Central Blog - RSS\x22 href\x3d\x22https://webmasters.googleblog.com/feeds/posts/default?alt\x3drss\x22 /\x3e\n\x3clink rel\x3d\x22service.post\x22 type\x3d\x22application/atom+xml\x22 title\x3d\x22Official Google Webmaster Central Blog - Atom\x22 href\x3d\x22https://www.blogger.com/feeds/32069983/posts/default\x22 /\x3e\n', 'meTag': '', 'adsenseHostId': 'ca-host-pub-1556223355139109', 'adsenseHasAds': false, 'adsenseAutoAds': false, 'boqCommentIframeForm': true, 'loginRedirectParam': '', 'view': '', 'dynamicViewsCommentsSrc': '//www.blogblog.com/dynamicviews/4224c15c4e7c9321/js/comments.js', 'dynamicViewsScriptSrc': '//www.blogblog.com/dynamicviews/d78375fb222d99b3', 'plusOneApiSrc': 'https://apis.google.com/js/platform.js', 'disableGComments': true, 'interstitialAccepted': false, 'sharing': {'platforms': [{'name': 'Get link', 'key': 'link', 'shareMessage': 'Get link', 'target': ''}, {'name': 'Facebook', 'key': 'facebook', 'shareMessage': 'Share to Facebook', 'target': 'facebook'}, {'name': 'BlogThis!', 'key': 'blogThis', 'shareMessage': 'BlogThis!', 'target': 'blog'}, {'name': 'X', 'key': 'twitter', 'shareMessage': 'Share to X', 'target': 'twitter'}, {'name': 'Pinterest', 'key': 'pinterest', 'shareMessage': 'Share to Pinterest', 'target': 'pinterest'}, {'name': 'Email', 'key': 'email', 'shareMessage': 'Email', 'target': 'email'}], 'disableGooglePlus': true, 'googlePlusShareButtonWidth': 0, 'googlePlusBootstrap': '\x3cscript type\x3d\x22text/javascript\x22\x3ewindow.___gcfg \x3d {\x27lang\x27: \x27en\x27};\x3c/script\x3e'}, 'hasCustomJumpLinkMessage': false, 'jumpLinkMessage': 'Read more', 'pageType': 'index', 'searchLabel': 'search console', 'pageName': 'search console', 'pageTitle': 'Official Google Webmaster Central Blog: search console', '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/search%20console?hl\x3den_US', 'type': 'feed', 'isSingleItem': false, 'isMultipleItems': true, 'isError': false, 'isPage': false, 'isPost': false, 'isHomepage': false, 'isArchive': false, 'isSearch': true, 'isLabelSearch': true, 'search': {'label': 'search console', 'resultsMessage': 'Showing posts with the label search console', 'resultsMessageHtml': 'Showing posts with the label \x3cspan class\x3d\x27search-label\x27\x3esearch console\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\x3esearch console\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>