CINXE.COM

<!DOCTYPE html> <html class='v2 list-page' dir='ltr' itemscope='' itemtype='http://schema.org/Blog' lang='zh-CN' 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 results </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%20results' 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%20results' 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%20results' 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=167c9891-4867-4c0b-870a-bc23641c9ee6' media='none' onload='if(media!='all')media='all'' rel='stylesheet'/><noscript><link href='https://www.blogger.com/dyn-css/authorization.css?targetBlogID=32069983&zx=167c9891-4867-4c0b-870a-bc23641c9ee6' 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=zh_CN'> <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='8630305347792431991' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2020/06/how-we-fought-search-spam-on-google.html?hl=zh_CN' itemprop='url' title='How we fought Search spam on Google - Webspam Report 2019'> How we fought Search spam on Google - Webspam Report 2019 </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> 星期二, 六月 09, 2020 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div class="separator" style="clear: both; text-align: justify;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhp3U8tN-OIlftfGWJrKEJ9UHjLK6-mYmELiMSfb2cSYtieJT7CH4qM6hlDMpEM3OkhINQAVpUmmDQ16iGms6W2I2Wza8nOvRIsecUm7rFQ4REoNOVgM8vuePp2XcNVVNnSNDgf/s1600/WebspamReport2019_1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="501" data-original-width="1400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhp3U8tN-OIlftfGWJrKEJ9UHjLK6-mYmELiMSfb2cSYtieJT7CH4qM6hlDMpEM3OkhINQAVpUmmDQ16iGms6W2I2Wza8nOvRIsecUm7rFQ4REoNOVgM8vuePp2XcNVVNnSNDgf/s1600/WebspamReport2019_1.png" /></a></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> Every search matters. That is why whenever you come to Google Search to find relevant and useful information, it is our ongoing commitment to make sure users receive the highest quality results possible. <br /> <br /></div> <div style="text-align: justify;"> Unfortunately, on the web there are some disruptive behaviors and content that we call "webspam" that can degrade the experience for people coming to find helpful information. We have a number of teams who work to prevent webspam from appearing in your search results, and it’s a constant challenge to stay ahead of the spammers. At the same time, we continue to engage with webmasters to ensure they’re following best practices and can find success on Search, making great content available on the open web. <br /> <br /></div> <div style="text-align: justify;"> Looking back at last year, here’s a snapshot of how we fought spam on Search in 2019, and how we supported the webmaster community. </div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <strong>Fighting Spam at Scale</strong> <br /> <strong><br /></strong></div> <div style="text-align: justify;"> With hundreds of billions of webpages in our index serving billions of queries every day, perhaps it’s not too surprising that there continue to be bad actors who try to manipulate search ranking. In fact, we observed that <strong>more than 25 Billion pages we discover each day are spammy</strong>. That’s a lot of spam and it goes to show the scale, persistence, and the lengths that spammers are willing to go. We’re very serious about making sure that your chance of encountering spammy pages in Search is as small as possible. Our efforts have helped ensure that more than 99% of visits from our results lead to spam-free experiences. </div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <strong>Updates from last year</strong> <br /> <strong><br /></strong></div> <div style="text-align: justify;"> In 2018, we reported that we had reduced <a href="https://support.google.com/webmasters/answer/2721437?hl=en">user-generated spam</a> by 80%, and we’re happy to confirm that this type of abuse did not grow in 2019. Link spam continued to be a popular form of spam, but our team was successful in containing its impact in 2019. More than 90% of link spam was caught by our systems, and techniques such as paid links or link exchange have been made less effective. </div> <div style="text-align: justify;"> <br /> Hacked spam, while still a commonly observed challenge, has been more stable compared to previous years. We continued to work on solutions to better detect and notify affected webmasters and platforms and <a href="https://developers.google.com/web/fundamentals/security/hacked/">help them recover from hacked websites</a>. </div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <strong>Spam Trends</strong> <br /> <strong><br /></strong></div> <div style="text-align: justify;"> One of our top priorities in 2019 was improving our spam fighting capabilities through machine learning systems. Our machine learning solutions, combined with our proven and time-tested manual enforcement capability, have been instrumental in identifying and preventing spammy results from being served to users. </div> <div style="text-align: justify;"> <br /> In the last few years, we’ve observed an increase in spammy sites with <a href="https://support.google.com/webmasters/answer/2721306?hl=en">auto-generated</a> and <a href="https://support.google.com/webmasters/answer/2721312?hl=en&ref_topic=6001971">scraped content</a> with behaviors that annoy or harm searchers, such as fake buttons, overwhelming ads, suspicious redirects and malware. These websites are often deceptive and offer no real value to people. In 2019, we were able to reduce the impact on Search users from this type of spam by more than 60% compared to 2018. </div> <div style="text-align: justify;"> <br /> As we improve our capability and efficiency in catching spam, we’re continuously investing in reducing broader types of harm, like scams and fraud. These sites trick people into thinking they’re visiting an official or authoritative site and in many cases, people can end up disclosing sensitive personal information, losing money, or infecting their devices with malware. We have been paying close attention to queries that are prone to scam and fraud and we’ve worked to stay ahead of spam tactics in those spaces to protect users. </div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <strong>Working with webmasters and developers for a better web</strong> </div> <div style="text-align: justify;"> <br /> Much of the work we do to fight against spam is using automated systems to detect spammy behavior, but those systems aren’t perfect and can’t catch everything. As someone who uses Search, you can also help us fight spam and other issues by <a href="https://support.google.com/webmasters/answer/93713">reporting spam on search</a>, <a href="https://safebrowsing.google.com/safebrowsing/report_phish/">phishing</a> or <a href="https://www.google.com/safebrowsing/report_badware/">malware</a>. We received nearly 230,000 reports of search spam in 2019, and we were able to take action on 82% of those reports we processed. We appreciate all the reports you sent to us and your help in keeping search results clean! </div> <div style="text-align: justify;"> <br /> So what do we do when we get those reports or identify that something isn’t quite right? An important part of what we do is notifying webmasters when we detect something wrong with their website. In 2019, we generated more than 90 million messages to website owners to let them know about issues, problems that may affect their site’s appearance on Search results and potential improvements that can be implemented. Of all messages, about 4.3 million were related to <a href="https://support.google.com/webmasters/answer/9044175">manual actions</a>, resulting from violations of our Webmaster Guidelines. </div> <div style="text-align: justify;"> <br /> And we’re always looking for ways to better help site owners. There were many initiatives in 2019 aimed at improving communications, such as <a href="https://webmasters.googleblog.com/2019/12/search-console-messages.html">the new Search Console messages</a>, <a href="https://webmasters.googleblog.com/2019/10/site-kit-is-now-available-for-all.html">Site Kit for WordPress sites</a> or <a href="https://webmasters.googleblog.com/2019/09/auto-dns-verification.html">the Auto-DNS verification in the new Search Console</a>. We hope that these initiatives have equipped webmasters with more convenient ways to get their sites verified and will continue to be helpful. We also hope this provides quicker access to news and that webmasters will be able to fix webspam issues or hack issues more effectively and efficiently. </div> <div style="text-align: justify;"> <br /> While we deeply focused on cleaning up spam, we also didn’t forget to keep up with the evolution of the web and <a href="https://webmasters.googleblog.com/2019/09/evolving-nofollow-new-ways-to-identify.html">rethought how we wanted to treat “nofollow” links</a>. Originally introduced as a means to help fight comment spam and annotate sponsored links, the “nofollow” attribute has come a long way. But we’re not stopping there. We believe it’s time for it to evolve even more, just as how our spam fighting capability has evolved. We introduced two new link attributes, rel="sponsored" and rel="ugc", that provide webmasters with additional ways to identify to Google Search the nature of particular links. Along with rel="nofollow", we began treating these as hints for us to incorporate for ranking purposes. We are very excited to see that these new rel attributes were well received and adopted by webmasters around the world! </div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <strong>Engaging with the community</strong> </div> <div style="text-align: justify;"> <br /> As always, we’re grateful for all the opportunities we had last year to connect with webmasters around the world, helping them improve their presence in Search and hearing feedback. We delivered more than 150 online office hours, online events and offline events in many cities across the globe to a wide range of audience including SEOs, developers, online marketers and business owners. Among those events, we have been delighted by <a href="https://webmasters.googleblog.com/2019/09/join-us-at-webmaster-conference-in.html">the momentum behind our Webmaster Conferences</a> in 35 locations across 15 countries and 12 languages around the world, including the first Product Summit version in Mountain View. While we’re not currently able to host in-person events, we look forward to more of these <a href="https://events.withgoogle.com/wmc/upcoming-events/#content">events</a> and virtual touchpoints in the future. </div> <div style="text-align: justify;"> <br /> Webmasters continued to find solutions and tips on our <a href="https://g.co/webmasterforum">Webmasters Help Community</a> with more than 30,000 threads in 2019 in more than a dozen languages. On YouTube, we <a href="https://webmasters.googleblog.com/2019/08/you-askgooglewebmasters-we-answer.html">launched #AskGoogleWebmasters</a> as well as series such as <a href="https://webmasters.googleblog.com/2019/06/a-new-series-on-seo-for-web-developers.html">SEO mythbusting</a> to ensure that your questions get answered and your uncertainties get clarified. </div> <div style="text-align: justify;"> <br /> We know that our journey to better web with you is ongoing and we would love to continue this with you in the year to come! Therefore, do keep in touch on <a href="https://twitter.com/googlewmc">Twitter</a>, <a href="https://www.youtube.com/channel/UCWf2ZlNsCGDS89VBF_awNvA">YouTube</a>, <a href="https://webmasters.googleblog.com/">blog</a>, <a href="https://support.google.com/webmasters/community?hl=en">Help Community</a> or see you in person at one of <a href="https://events.withgoogle.com/wmc/upcoming-events/">our conferences</a> near you! </div> <br /> <div id="gdcalert2"> </div> <br /> <div style="text-align: justify;"> <br /></div> <div class="separator" style="clear: both; text-align: justify;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgNvfAv2O6jZ6ZRWnieZE9X_-4vOjhVQzVUlnyvouAhsFtT0DD0dgMRGqH7NjMqzKaNJKiT1dsH7BQ6huCPPWm8J-8HqE6IJa-ockS8Wca424KIlANQ17TJXs6NBHiHIx85hXIw/s1600/WebspamReport2019_2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="501" data-original-width="1400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgNvfAv2O6jZ6ZRWnieZE9X_-4vOjhVQzVUlnyvouAhsFtT0DD0dgMRGqH7NjMqzKaNJKiT1dsH7BQ6huCPPWm8J-8HqE6IJa-ockS8Wca424KIlANQ17TJXs6NBHiHIx85hXIw/s1600/WebspamReport2019_2.png" /></a></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <span class="byline-author"> Posted by Cherry Prommawin, Search Relations, and Duy Nguyen, Search Quality Analyst</span> </div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div class="separator" style="clear: both; text-align: justify;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhp3U8tN-OIlftfGWJrKEJ9UHjLK6-mYmELiMSfb2cSYtieJT7CH4qM6hlDMpEM3OkhINQAVpUmmDQ16iGms6W2I2Wza8nOvRIsecUm7rFQ4REoNOVgM8vuePp2XcNVVNnSNDgf/s1600/WebspamReport2019_1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="501" data-original-width="1400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhp3U8tN-OIlftfGWJrKEJ9UHjLK6-mYmELiMSfb2cSYtieJT7CH4qM6hlDMpEM3OkhINQAVpUmmDQ16iGms6W2I2Wza8nOvRIsecUm7rFQ4REoNOVgM8vuePp2XcNVVNnSNDgf/s1600/WebspamReport2019_1.png" /></a></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> Every search matters. That is why whenever you come to Google Search to find relevant and useful information, it is our ongoing commitment to make sure users receive the highest quality results possible. <br /> <br /></div> <div style="text-align: justify;"> Unfortunately, on the web there are some disruptive behaviors and content that we call "webspam" that can degrade the experience for people coming to find helpful information. We have a number of teams who work to prevent webspam from appearing in your search results, and it’s a constant challenge to stay ahead of the spammers. At the same time, we continue to engage with webmasters to ensure they’re following best practices and can find success on Search, making great content available on the open web. <br /> <br /></div> <div style="text-align: justify;"> Looking back at last year, here’s a snapshot of how we fought spam on Search in 2019, and how we supported the webmaster community. </div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <strong>Fighting Spam at Scale</strong> <br /> <strong><br /></strong></div> <div style="text-align: justify;"> With hundreds of billions of webpages in our index serving billions of queries every day, perhaps it’s not too surprising that there continue to be bad actors who try to manipulate search ranking. In fact, we observed that <strong>more than 25 Billion pages we discover each day are spammy</strong>. That’s a lot of spam and it goes to show the scale, persistence, and the lengths that spammers are willing to go. We’re very serious about making sure that your chance of encountering spammy pages in Search is as small as possible. Our efforts have helped ensure that more than 99% of visits from our results lead to spam-free experiences. </div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <strong>Updates from last year</strong> <br /> <strong><br /></strong></div> <div style="text-align: justify;"> In 2018, we reported that we had reduced <a href="https://support.google.com/webmasters/answer/2721437?hl=en">user-generated spam</a> by 80%, and we’re happy to confirm that this type of abuse did not grow in 2019. Link spam continued to be a popular form of spam, but our team was successful in containing its impact in 2019. More than 90% of link spam was caught by our systems, and techniques such as paid links or link exchange have been made less effective. </div> <div style="text-align: justify;"> <br /> Hacked spam, while still a commonly observed challenge, has been more stable compared to previous years. We continued to work on solutions to better detect and notify affected webmasters and platforms and <a href="https://developers.google.com/web/fundamentals/security/hacked/">help them recover from hacked websites</a>. </div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <strong>Spam Trends</strong> <br /> <strong><br /></strong></div> <div style="text-align: justify;"> One of our top priorities in 2019 was improving our spam fighting capabilities through machine learning systems. Our machine learning solutions, combined with our proven and time-tested manual enforcement capability, have been instrumental in identifying and preventing spammy results from being served to users. </div> <div style="text-align: justify;"> <br /> In the last few years, we’ve observed an increase in spammy sites with <a href="https://support.google.com/webmasters/answer/2721306?hl=en">auto-generated</a> and <a href="https://support.google.com/webmasters/answer/2721312?hl=en&ref_topic=6001971">scraped content</a> with behaviors that annoy or harm searchers, such as fake buttons, overwhelming ads, suspicious redirects and malware. These websites are often deceptive and offer no real value to people. In 2019, we were able to reduce the impact on Search users from this type of spam by more than 60% compared to 2018. </div> <div style="text-align: justify;"> <br /> As we improve our capability and efficiency in catching spam, we’re continuously investing in reducing broader types of harm, like scams and fraud. These sites trick people into thinking they’re visiting an official or authoritative site and in many cases, people can end up disclosing sensitive personal information, losing money, or infecting their devices with malware. We have been paying close attention to queries that are prone to scam and fraud and we’ve worked to stay ahead of spam tactics in those spaces to protect users. </div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <strong>Working with webmasters and developers for a better web</strong> </div> <div style="text-align: justify;"> <br /> Much of the work we do to fight against spam is using automated systems to detect spammy behavior, but those systems aren’t perfect and can’t catch everything. As someone who uses Search, you can also help us fight spam and other issues by <a href="https://support.google.com/webmasters/answer/93713">reporting spam on search</a>, <a href="https://safebrowsing.google.com/safebrowsing/report_phish/">phishing</a> or <a href="https://www.google.com/safebrowsing/report_badware/">malware</a>. We received nearly 230,000 reports of search spam in 2019, and we were able to take action on 82% of those reports we processed. We appreciate all the reports you sent to us and your help in keeping search results clean! </div> <div style="text-align: justify;"> <br /> So what do we do when we get those reports or identify that something isn’t quite right? An important part of what we do is notifying webmasters when we detect something wrong with their website. In 2019, we generated more than 90 million messages to website owners to let them know about issues, problems that may affect their site’s appearance on Search results and potential improvements that can be implemented. Of all messages, about 4.3 million were related to <a href="https://support.google.com/webmasters/answer/9044175">manual actions</a>, resulting from violations of our Webmaster Guidelines. </div> <div style="text-align: justify;"> <br /> And we’re always looking for ways to better help site owners. There were many initiatives in 2019 aimed at improving communications, such as <a href="https://webmasters.googleblog.com/2019/12/search-console-messages.html">the new Search Console messages</a>, <a href="https://webmasters.googleblog.com/2019/10/site-kit-is-now-available-for-all.html">Site Kit for WordPress sites</a> or <a href="https://webmasters.googleblog.com/2019/09/auto-dns-verification.html">the Auto-DNS verification in the new Search Console</a>. We hope that these initiatives have equipped webmasters with more convenient ways to get their sites verified and will continue to be helpful. We also hope this provides quicker access to news and that webmasters will be able to fix webspam issues or hack issues more effectively and efficiently. </div> <div style="text-align: justify;"> <br /> While we deeply focused on cleaning up spam, we also didn’t forget to keep up with the evolution of the web and <a href="https://webmasters.googleblog.com/2019/09/evolving-nofollow-new-ways-to-identify.html">rethought how we wanted to treat “nofollow” links</a>. Originally introduced as a means to help fight comment spam and annotate sponsored links, the “nofollow” attribute has come a long way. But we’re not stopping there. We believe it’s time for it to evolve even more, just as how our spam fighting capability has evolved. We introduced two new link attributes, rel="sponsored" and rel="ugc", that provide webmasters with additional ways to identify to Google Search the nature of particular links. Along with rel="nofollow", we began treating these as hints for us to incorporate for ranking purposes. We are very excited to see that these new rel attributes were well received and adopted by webmasters around the world! </div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <strong>Engaging with the community</strong> </div> <div style="text-align: justify;"> <br /> As always, we’re grateful for all the opportunities we had last year to connect with webmasters around the world, helping them improve their presence in Search and hearing feedback. We delivered more than 150 online office hours, online events and offline events in many cities across the globe to a wide range of audience including SEOs, developers, online marketers and business owners. Among those events, we have been delighted by <a href="https://webmasters.googleblog.com/2019/09/join-us-at-webmaster-conference-in.html">the momentum behind our Webmaster Conferences</a> in 35 locations across 15 countries and 12 languages around the world, including the first Product Summit version in Mountain View. While we’re not currently able to host in-person events, we look forward to more of these <a href="https://events.withgoogle.com/wmc/upcoming-events/#content">events</a> and virtual touchpoints in the future. </div> <div style="text-align: justify;"> <br /> Webmasters continued to find solutions and tips on our <a href="https://g.co/webmasterforum">Webmasters Help Community</a> with more than 30,000 threads in 2019 in more than a dozen languages. On YouTube, we <a href="https://webmasters.googleblog.com/2019/08/you-askgooglewebmasters-we-answer.html">launched #AskGoogleWebmasters</a> as well as series such as <a href="https://webmasters.googleblog.com/2019/06/a-new-series-on-seo-for-web-developers.html">SEO mythbusting</a> to ensure that your questions get answered and your uncertainties get clarified. </div> <div style="text-align: justify;"> <br /> We know that our journey to better web with you is ongoing and we would love to continue this with you in the year to come! Therefore, do keep in touch on <a href="https://twitter.com/googlewmc">Twitter</a>, <a href="https://www.youtube.com/channel/UCWf2ZlNsCGDS89VBF_awNvA">YouTube</a>, <a href="https://webmasters.googleblog.com/">blog</a>, <a href="https://support.google.com/webmasters/community?hl=en">Help Community</a> or see you in person at one of <a href="https://events.withgoogle.com/wmc/upcoming-events/">our conferences</a> near you! </div> <br /> <div id="gdcalert2"> </div> <br /> <div style="text-align: justify;"> <br /></div> <div class="separator" style="clear: both; text-align: justify;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgNvfAv2O6jZ6ZRWnieZE9X_-4vOjhVQzVUlnyvouAhsFtT0DD0dgMRGqH7NjMqzKaNJKiT1dsH7BQ6huCPPWm8J-8HqE6IJa-ockS8Wca424KIlANQ17TJXs6NBHiHIx85hXIw/s1600/WebspamReport2019_2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="501" data-original-width="1400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgNvfAv2O6jZ6ZRWnieZE9X_-4vOjhVQzVUlnyvouAhsFtT0DD0dgMRGqH7NjMqzKaNJKiT1dsH7BQ6huCPPWm8J-8HqE6IJa-ockS8Wca424KIlANQ17TJXs6NBHiHIx85hXIw/s1600/WebspamReport2019_2.png" /></a></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <br /></div> <div style="text-align: justify;"> <span class="byline-author"> Posted by Cherry Prommawin, Search Relations, and Duy Nguyen, Search Quality Analyst</span> </div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:How we fought Search spam on Google - Webspam Report 2019&url=https://webmasters.googleblog.com/2020/06/how-we-fought-search-spam-on-google.html?hl=zh_CN&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/2020/06/how-we-fought-search-spam-on-google.html?hl=zh_CN'> <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/2020/06/how-we-fought-search-spam-on-google.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines?hl=zh_CN' rel='tag'> webmaster guidelines </a> </span> </div> </div> </div> <div class='post' data-id='4212925670054035524' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/10/video-series-for-new-webmasters-search.html?hl=zh_CN' itemprop='url' title='Video Series for New Webmasters: Search for Beginners!'> Video Series for New Webmasters: Search for Beginners! </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> 星期二, 十月 29, 2019 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p> We are excited to introduce our newest video series: “<a href="https://www.youtube.com/playlist?list=PLKoqnv2vTMUOHPb5IJIn-7egNRmsvbPIE">Search For Beginners</a>”! The series was created primarily to help new webmasters. It is also for anyone with an interest in Search or anyone who is still learning about the Web and how to manage their online presence. </p> <p> We love to see the webmaster community grow! Every day, there are countless new webmasters who are taking the first steps in learning how Search works, and how to make their websites perform well and discoverable on Search. We understand that it sometimes can be challenging or even overwhelming to start with our existing content without some prior knowledge or basic understandings of the Web. We find our basic videos in our <a href="https://www.youtube.com/channel/UCWf2ZlNsCGDS89VBF_awNvA">YouTube channels</a> to be the ones with the most views. At the same time, advanced webmasters also see the need for content that can be sent to clients or stakeholders to help explain important concepts in managing an online presence. </p> <p> We want to help all webmasters succeed, regardless of whether you have been managing websites for many years or you’ve just started out yesterday. We want to do more to help the new webmasters and this video series will hopefully help us achieve that.<br /> </p> <p>Introduction to the series:<br /><iframe allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" frameborder="0" height="315" src="https://www.youtube.com/embed/-0X1AVLIzt0" width="560" style="margin:0"></iframe> </p> <p> Episode 1:<br /> <iframe width="560" height="315" src="https://www.youtube.com/embed/AdATZ2G1k84" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen style="margin:0"></iframe> </p> <p> The “Search For Beginners” video series covers basic online presence topics ranging from ‘Do you need a website?’, ‘What are the goals for your website?’ to more organic search-related topics such as ‘How does Google Search work?’, ‘How to change description line’, or ‘How to change wrong address information on Google’. Actually, we get asked these questions frequently in <a href="https://support.google.com/webmasters/community">forums</a>, <a href="https://twitter.com/googlewmc">social channels</a> and at <a href="https://webmasters.googleblog.com/2019/09/join-us-at-webmaster-conference-in.html">events around the world</a>! The videos are fully animated. The videos are in English with subtitles available in Spanish, Portuguese, Korean, Chinese, Indonesian, Italian, Japanese, and English. We are working on more, so please stay tuned!<br /> </p> <p> And if you consider yourself a more experienced user, please feel free to use these videos to support your pitches or explaining things to your clients. If you want to share any ideas or learnings, please leave them in the comment section in each video so that others can benefit from your knowledge and experience.<br /> </p> <p> Follow us on <a href="https://twitter.com/googlewmc">Twitter</a> and subscribe on <a href="https://www.youtube.com/channel/UCWf2ZlNsCGDS89VBF_awNvA">YouTube</a> for the upcoming videos! We will be adding new videos in this series to <a href="https://www.youtube.com/playlist?list=PLKoqnv2vTMUOHPb5IJIn-7egNRmsvbPIE">this playlist </a>about every two weeks!<br /> </p> <span class="byline-author">Posted by Cherry Prommawin, Search Quality Analyst</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p> We are excited to introduce our newest video series: “<a href="https://www.youtube.com/playlist?list=PLKoqnv2vTMUOHPb5IJIn-7egNRmsvbPIE">Search For Beginners</a>”! The series was created primarily to help new webmasters. It is also for anyone with an interest in Search or anyone who is still learning about the Web and how to manage their online presence. </p> <p> We love to see the webmaster community grow! Every day, there are countless new webmasters who are taking the first steps in learning how Search works, and how to make their websites perform well and discoverable on Search. We understand that it sometimes can be challenging or even overwhelming to start with our existing content without some prior knowledge or basic understandings of the Web. We find our basic videos in our <a href="https://www.youtube.com/channel/UCWf2ZlNsCGDS89VBF_awNvA">YouTube channels</a> to be the ones with the most views. At the same time, advanced webmasters also see the need for content that can be sent to clients or stakeholders to help explain important concepts in managing an online presence. </p> <p> We want to help all webmasters succeed, regardless of whether you have been managing websites for many years or you’ve just started out yesterday. We want to do more to help the new webmasters and this video series will hopefully help us achieve that.<br /> </p> <p>Introduction to the series:<br /><iframe allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" frameborder="0" height="315" src="https://www.youtube.com/embed/-0X1AVLIzt0" width="560" style="margin:0"></iframe> </p> <p> Episode 1:<br /> <iframe width="560" height="315" src="https://www.youtube.com/embed/AdATZ2G1k84" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen style="margin:0"></iframe> </p> <p> The “Search For Beginners” video series covers basic online presence topics ranging from ‘Do you need a website?’, ‘What are the goals for your website?’ to more organic search-related topics such as ‘How does Google Search work?’, ‘How to change description line’, or ‘How to change wrong address information on Google’. Actually, we get asked these questions frequently in <a href="https://support.google.com/webmasters/community">forums</a>, <a href="https://twitter.com/googlewmc">social channels</a> and at <a href="https://webmasters.googleblog.com/2019/09/join-us-at-webmaster-conference-in.html">events around the world</a>! The videos are fully animated. The videos are in English with subtitles available in Spanish, Portuguese, Korean, Chinese, Indonesian, Italian, Japanese, and English. We are working on more, so please stay tuned!<br /> </p> <p> And if you consider yourself a more experienced user, please feel free to use these videos to support your pitches or explaining things to your clients. If you want to share any ideas or learnings, please leave them in the comment section in each video so that others can benefit from your knowledge and experience.<br /> </p> <p> Follow us on <a href="https://twitter.com/googlewmc">Twitter</a> and subscribe on <a href="https://www.youtube.com/channel/UCWf2ZlNsCGDS89VBF_awNvA">YouTube</a> for the upcoming videos! We will be adding new videos in this series to <a href="https://www.youtube.com/playlist?list=PLKoqnv2vTMUOHPb5IJIn-7egNRmsvbPIE">this playlist </a>about every two weeks!<br /> </p> <span class="byline-author">Posted by Cherry Prommawin, Search Quality Analyst</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:Video Series for New Webmasters: Search for Beginners!&url=https://webmasters.googleblog.com/2019/10/video-series-for-new-webmasters-search.html?hl=zh_CN&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/10/video-series-for-new-webmasters-search.html?hl=zh_CN'> <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/10/video-series-for-new-webmasters-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'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/search%20for%20beginners?hl=zh_CN' rel='tag'> search for beginners </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/seo?hl=zh_CN' rel='tag'> seo </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/video?hl=zh_CN' rel='tag'> video </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=zh_CN' rel='tag'> webmaster community </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines?hl=zh_CN' rel='tag'> webmaster guidelines </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmasters?hl=zh_CN' rel='tag'> webmasters </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/youtube%20channel?hl=zh_CN' rel='tag'> youtube channel </a> </span> </div> </div> </div> <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=zh_CN' 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'> 星期五, 九月 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=zh_CN&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=zh_CN'> <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'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=zh_CN' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=zh_CN' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=zh_CN' rel='tag'> structured data </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=zh_CN' rel='tag'> webmaster community </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=zh_CN' rel='tag'> webmaster tools </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/youtube%20channel?hl=zh_CN' rel='tag'> youtube channel </a> </span> </div> </div> </div> <div class='post' data-id='3790701813410625524' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/09/more-controls-on-search.html?hl=zh_CN' itemprop='url' title='More options to help websites preview their content on Google Search'> More options to help websites preview their content on Google Search </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> 星期二, 九月 24, 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>Google uses content previews, including <a href="https://support.google.com/webmasters/answer/35624">text snippets</a> and other media, to help people decide whether a result is relevant to their query. The type of preview shown depends on many factors, including the type of content a person is looking for and the kind of device they're viewing it on.</p> <p>For instance, if you look for recipe results on Google, you may see thumbnail images and user ratings--things that may be more helpful than text snippets when it comes to deciding what you want to eat. Alternately, or perhaps you're looking for a concert nearby, and are able to check out the events directly in the search results. These are made possible by publishers marking up their pages with <a href="https://developers.google.com/search/docs/guides/search-gallery">structured data</a>.</p> <p>Google automatically generates previews in a way intended to help a user understand why the results shown are relevant to their search and why the user would want to visit the linked pages. However, we recognize that site owners may wish to independently adjust the extent of their preview content in search results. To make it easier for individual websites to define how much or which text should be available for snippeting and the extent to which other media should be included in their previews, we're now introducing several new settings for webmasters. </p> <h3>Letting Google know about your snippet and content preview preferences</h3> <p>Previously, it was only possible to allow a textual snippet or to not allow one. We're now introducing a set of methods that allow more fine-grained configuration of the preview content shown for your pages. This is done through two types of new settings: a set of robots meta tags and an HTML attribute. </p> <h3>Using robots meta tags</h3> <p>The robots meta tag is added to an HTML page's <head>, or specified via the x-robots-tag HTTP header. The robots meta tags addressing the preview content for a page are:</p> <ul><li>"<code>nosnippet</code>"<br>This is an existing option to specify that you don't want any textual snippet shown for this page. </li> <li>"<code>max-snippet:[number]</code>"<br>New! Specify a maximum text-length, in characters, of a snippet for your page.</li> <li>"<code>max-video-preview:[number]</code>"<br>New! Specify a maximum duration in seconds of an animated video preview.</li> <li>"<code>max-image-preview:[setting]</code>"<br>New! Specify a maximum size of image preview to be shown for images on this page, using either "none", "standard", or "large".</li></ul> <p>They can be combined, for example:</p> <p><code><meta name="robots" content="max-snippet:50, max-image-preview:large"></code></p> <p>Preview settings from these meta tags will become effective in mid-to-late October 2019 and may take about a week for the global rollout to complete.</p> <h3>Using the new data-nosnippet HTML attribute</h3> <p>A new way to help limit which part of a page is eligible to be shown as a snippet is the "<code>data-nosnippet</code>" HTML attribute on <code>span</code>, <code>div</code>, and <code>section</code> elements. With this, you can prevent that part of an HTML page from being shown within the textual snippet on the page.</p> <p>For example:</p> <p><code><p><span data-nosnippet>Harry Houdini</span> is undoubtedly the most famous magician ever to live.</p></code></p> <p>The data-nosnippet HTML attribute will be start affecting presentation on Google products later this year. Learn more in our <a href="https://developers.google.com/search/reference/robots_meta_tag">developer documentation for the robots meta tag, x-robots-tag, and data-nosnippet</a>.</p> <h3>A note about rich results and featured snippets</h3> <p>Content in <a href="https://developers.google.com/search/docs/guides/intro-structured-data">structured data</a> is eligible for display as <a href="https://developers.google.com/search/docs/guides/search-gallery">rich results in search</a>. These kinds of results do not conform to limits declared in the above meta robots settings, but rather, can be addressed with much greater specificity by limiting or modifying the content provided in the structured data itself. For example, if a <a href="https://developers.google.com/search/docs/data-types/recipe">recipe</a> is included in structured data, the contents of that structured data may be presented in a recipe carousel in the search results. Similarly, if an event is marked up with structured data, it may be presented as such in the search results. To limit that presentation, a publisher can limit the amount and type of content in the structured data. </p> <p>Some special features on Search depend on the availability of preview content, so limiting your previews may prevent your content from appearing in these areas. <a href="https://support.google.com/websearch/answer/9351707">Featured snippets</a>, for example, requires a certain minimum number of characters to be displayed. This can vary by language, which is why there is no exact max-snippets length we can provide to ensure appearing in this feature. Those who do not wish to have content appear as featured snippets can experiment with lower max-snippet lengths. Those who want a guaranteed way to <a href="https://support.google.com/webmasters/answer/6229325">opt-out of featured snippets</a> should use nosnippet.</p> <h3>The AMP Format</h3> <p>The <a href="https://amp.dev/">AMP format</a> comes with certain benefits, including eligibility for more prominent presentation of thumbnail images in <a href="https://developers.google.com/search/docs/guides/about-amp">search results</a> and in the <a href="https://support.google.com/webmasters/answer/9046777">Google Discover feed</a>. These characteristics have been shown to drive more traffic to publishers’ articles. However, publishers who do not want Google to use larger thumbnail images when their AMP pages are presented in search and Discover can use the above meta robots settings to specify max-image-preview of “standard” or “none.”</p> <p>These new options are available to content owners worldwide and will operate the same for results we display globally. We hope they make it easier for you to optimize the value you get from Search and achieve your business goals. For more information, check out our <a href="https://developers.google.com/search/reference/robots_meta_tag">developer documentation on meta tags</a>. Should you have any questions, feel free to <a href="https://www.google.com/webmasters/connect">reach out to us</a>, or drop by our <a href="https://support.google.com/webmasters/go/community">webmaster help forums</a>.</p> <br> <span class="byline-author">Posted by <a href="https://twitter.com/johnmu?rel=rel">John Mueller</a>, Webmaster Trends Analyst, Google Switzerland</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>Google uses content previews, including <a href="https://support.google.com/webmasters/answer/35624">text snippets</a> and other media, to help people decide whether a result is relevant to their query. The type of preview shown depends on many factors, including the type of content a person is looking for and the kind of device they're viewing it on.</p> <p>For instance, if you look for recipe results on Google, you may see thumbnail images and user ratings--things that may be more helpful than text snippets when it comes to deciding what you want to eat. Alternately, or perhaps you're looking for a concert nearby, and are able to check out the events directly in the search results. These are made possible by publishers marking up their pages with <a href="https://developers.google.com/search/docs/guides/search-gallery">structured data</a>.</p> <p>Google automatically generates previews in a way intended to help a user understand why the results shown are relevant to their search and why the user would want to visit the linked pages. However, we recognize that site owners may wish to independently adjust the extent of their preview content in search results. To make it easier for individual websites to define how much or which text should be available for snippeting and the extent to which other media should be included in their previews, we're now introducing several new settings for webmasters. </p> <h3>Letting Google know about your snippet and content preview preferences</h3> <p>Previously, it was only possible to allow a textual snippet or to not allow one. We're now introducing a set of methods that allow more fine-grained configuration of the preview content shown for your pages. This is done through two types of new settings: a set of robots meta tags and an HTML attribute. </p> <h3>Using robots meta tags</h3> <p>The robots meta tag is added to an HTML page's <head>, or specified via the x-robots-tag HTTP header. The robots meta tags addressing the preview content for a page are:</p> <ul><li>"<code>nosnippet</code>"<br>This is an existing option to specify that you don't want any textual snippet shown for this page. </li> <li>"<code>max-snippet:[number]</code>"<br>New! Specify a maximum text-length, in characters, of a snippet for your page.</li> <li>"<code>max-video-preview:[number]</code>"<br>New! Specify a maximum duration in seconds of an animated video preview.</li> <li>"<code>max-image-preview:[setting]</code>"<br>New! Specify a maximum size of image preview to be shown for images on this page, using either "none", "standard", or "large".</li></ul> <p>They can be combined, for example:</p> <p><code><meta name="robots" content="max-snippet:50, max-image-preview:large"></code></p> <p>Preview settings from these meta tags will become effective in mid-to-late October 2019 and may take about a week for the global rollout to complete.</p> <h3>Using the new data-nosnippet HTML attribute</h3> <p>A new way to help limit which part of a page is eligible to be shown as a snippet is the "<code>data-nosnippet</code>" HTML attribute on <code>span</code>, <code>div</code>, and <code>section</code> elements. With this, you can prevent that part of an HTML page from being shown within the textual snippet on the page.</p> <p>For example:</p> <p><code><p><span data-nosnippet>Harry Houdini</span> is undoubtedly the most famous magician ever to live.</p></code></p> <p>The data-nosnippet HTML attribute will be start affecting presentation on Google products later this year. Learn more in our <a href="https://developers.google.com/search/reference/robots_meta_tag">developer documentation for the robots meta tag, x-robots-tag, and data-nosnippet</a>.</p> <h3>A note about rich results and featured snippets</h3> <p>Content in <a href="https://developers.google.com/search/docs/guides/intro-structured-data">structured data</a> is eligible for display as <a href="https://developers.google.com/search/docs/guides/search-gallery">rich results in search</a>. These kinds of results do not conform to limits declared in the above meta robots settings, but rather, can be addressed with much greater specificity by limiting or modifying the content provided in the structured data itself. For example, if a <a href="https://developers.google.com/search/docs/data-types/recipe">recipe</a> is included in structured data, the contents of that structured data may be presented in a recipe carousel in the search results. Similarly, if an event is marked up with structured data, it may be presented as such in the search results. To limit that presentation, a publisher can limit the amount and type of content in the structured data. </p> <p>Some special features on Search depend on the availability of preview content, so limiting your previews may prevent your content from appearing in these areas. <a href="https://support.google.com/websearch/answer/9351707">Featured snippets</a>, for example, requires a certain minimum number of characters to be displayed. This can vary by language, which is why there is no exact max-snippets length we can provide to ensure appearing in this feature. Those who do not wish to have content appear as featured snippets can experiment with lower max-snippet lengths. Those who want a guaranteed way to <a href="https://support.google.com/webmasters/answer/6229325">opt-out of featured snippets</a> should use nosnippet.</p> <h3>The AMP Format</h3> <p>The <a href="https://amp.dev/">AMP format</a> comes with certain benefits, including eligibility for more prominent presentation of thumbnail images in <a href="https://developers.google.com/search/docs/guides/about-amp">search results</a> and in the <a href="https://support.google.com/webmasters/answer/9046777">Google Discover feed</a>. These characteristics have been shown to drive more traffic to publishers’ articles. However, publishers who do not want Google to use larger thumbnail images when their AMP pages are presented in search and Discover can use the above meta robots settings to specify max-image-preview of “standard” or “none.”</p> <p>These new options are available to content owners worldwide and will operate the same for results we display globally. We hope they make it easier for you to optimize the value you get from Search and achieve your business goals. For more information, check out our <a href="https://developers.google.com/search/reference/robots_meta_tag">developer documentation on meta tags</a>. Should you have any questions, feel free to <a href="https://www.google.com/webmasters/connect">reach out to us</a>, or drop by our <a href="https://support.google.com/webmasters/go/community">webmaster help forums</a>.</p> <br> <span class="byline-author">Posted by <a href="https://twitter.com/johnmu?rel=rel">John Mueller</a>, Webmaster Trends Analyst, Google Switzerland</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:More options to help websites preview their content on Google Search&url=https://webmasters.googleblog.com/2019/09/more-controls-on-search.html?hl=zh_CN&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/more-controls-on-search.html?hl=zh_CN'> <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/more-controls-on-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'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=zh_CN' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/images?hl=zh_CN' rel='tag'> images </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> </span> </div> </div> </div> <div class='post' data-id='1124512533213197226' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/08/when-indexing-goes-wrong-how-google.html?hl=zh_CN' itemprop='url' title='When indexing goes wrong: how Google Search recovered from indexing issues & lessons learned since.'> When indexing goes wrong: how Google Search recovered from indexing issues & lessons learned since. </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> 星期一, 八月 12, 2019 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>Most of the time, our search engine runs properly. Our teams work hard to prevent technical issues that could affect our users who are searching the web, or webmasters whose sites we index and serve to users. Similarly, the underlying systems that we use to power the search engine also run as intended most of the time. When small disruptions happen, they are largely not visible to anyone except our teams who ensure that our products are up and running. However, like all complex systems, sometimes larger outages can occur, which may lead to disruptions for both users and website creators.</p> <p>In the last few months, such a situation occurred with our indexing systems, which had a ripple effect on some other parts of our infrastructure. While we worked as quickly as possible to remedy the situation, we apologize for the disruption, as our goal is to continuously provide high-quality products to our users and to the web ecosystem.</p> <p>Since then, we took a closer, careful look into the situation. In the process, we learned a few lessons that we'd like to share with you today. In this blog post, we will go into more details about what happened, clarify how we plan to communicate better if such things happen in the future, and remind website owners of the channels they can use to communicate with us.</p> <h2>So, what happened a few months ago?</h2> <p>In April, we had several issues related to our index. The Search index is the database that holds the hundreds of billions of web pages that we crawled on the web and that we think could answer some of our users’ queries. When a user enters a query in the Google search engine, our ranking algorithms sort through those pages in our Search index to find the most relevant, useful results in a fraction of a second. Here is more information on what happened.</p> <h3>1. The indexing issue</h3> <p>To start it off, we temporarily lost part of the Search index.<br>Wait... What? What do you mean “lost part of the index?” Is that even possible?</p> <p>Basically, when serving search results to users, to accelerate the speed of the service, the query of the user only “travels” as far as the closest of our data centers supporting the Google Search product, from which the Search Engine Results Page (SERP) is generated. So when there are modifications to the composition of the index (some pages added and removed, documents are merged, or other types of data modification), those modifications need to be reflected in all of those data centers. The consequence is that users all over the world are consistently served pages from the most recent version of the index.</p> <p><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlKmwOg0tP0MH7BMFbVu6haYtqJQE-IBkBpmMfZ3Lj_1p4C9s5fbpd-nYzWBHmSmyg-6pr4GQMLrnxI3R3puqEK40LByTpivFWCOSlnP41xuXE1bPRzwcbFJFpdMekHNTuGnwh/s1600/pasted+image+0.png" imageanchor="1" ><img border="0" data-original-height="333" data-original-width="500" height="266" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlKmwOg0tP0MH7BMFbVu6haYtqJQE-IBkBpmMfZ3Lj_1p4C9s5fbpd-nYzWBHmSmyg-6pr4GQMLrnxI3R3puqEK40LByTpivFWCOSlnP41xuXE1bPRzwcbFJFpdMekHNTuGnwh/s400/pasted+image+0.png" width="400" /></a> <small><br>Google owns and operates data centers (like the one pictured above) around the world, to keep our products running 24 hours a day, 7 days a week - <a href="https://www.google.com/about/datacenters/">source</a></small></p> <p>Keeping the index unified across all those data centers is a non trivial task. For large user-facing services, we may deploy updates by starting in one data center and expand until all relevant data centers are updated. For sensitive pieces of infrastructure, we may extend a rollout over several days, interleaving them across instances in different geographic regions. <a href="https://landing.google.com/sre/sre-book/chapters/release-engineering/">source</a></p> <p>So, as we pushed some planned changes to the Search index, on April 5th parts of the deployment system broke, on a Friday no-less! More specifically: as we were updating the index over some of our data centers, a small number of documents ended up being dropped from the index accidentally. Hence: “we lost part of the index.”</p> <p>Luckily, our <a href="https://landing.google.com/sre/sre-book/chapters/being-on-call/">on-call engineers</a> caught the issue pretty quickly, at the same time as we started picking up chatter on social media (thanks to everyone who notified us over that weekend!). As a result, we were able to start reverting the Search index to its previous stable state in all data centers only a few hours after the issue was uncovered (we keep back-ups of our indexes just in case such events happen).</p> <p>We communicated on Sunday, <a href="https://mobile.twitter.com/searchliaison/status/1114961119699804160">April 7th</a> that we were aware of the issue, and that things were starting to get back to normal. As data centers were progressively reverting back to a stable index, we continued updating on Twitter (on <a href="https://mobile.twitter.com/searchliaison/status/1115342598279913472">April 8th</a>, on <a href="https://mobile.twitter.com/searchliaison/status/1115700559317585920">April 9th</a>), until we were confident that all data centers were fully back to a complete version of the index on <a href="https://mobile.twitter.com/searchliaison/status/1116152155713392640">April 11th</a>.</p> <h3>2. The Search Console issue</h3> <p><a href="https://search.google.com/search-console/about">Search Console</a> is the set of tools and reports any webmaster can use to access data about their website’s performance in Search. For example, it shows how many impressions and clicks a website gets in the organic search results every day, or information on what pages of a website are included and excluded from the Search index.</p> <p>As a consequence of the Search index having the issues we described above, Search Console started to also show inconsistencies. This is because some of the data that surfaces in Search Console originates from the Search index itself:</p> <ul><li>the <a href="https://support.google.com/webmasters/answer/7440203">Index Coverage report</a> depends on the Search index being consistent across data centers.</li> <li>when we store a page in the Search index, we can annotate the entry with key signals about the page, like the fact that the page contains rich results markup for example. Therefore, an issue with the Search index can have an impact on the <a href="https://support.google.com/webmasters/answer/7552505">Rich Results reports</a> in Search Console.</li></ul> <p>Basically, many Search Console individual reports read data from a dedicated database. That database is partially built by using information that comes from the Search index. As we had to revert back to a previous version of the Search index, we also had to pause the updating of the Search Console database. This resulted in plateau-ing data for some reports (and flakiness in others, like the URL inspection tool).</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjkmVWgQhTSSF_Yiv8xxdKD6wbYB2Y8EFyz_iVHRBMULzLJ5HFw7U8wpTxwu11rKikQ3V9WeG__ZwrTgX7GJo9P3LxdLuCBI_QvzV5il3YBa4biPK5aCLcst9P7ssfyjWKjdYkY/s1600/pasted+image+0+%25281%2529.png" imageanchor="1" ><img border="0" data-original-height="266" data-original-width="911" height="117" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjkmVWgQhTSSF_Yiv8xxdKD6wbYB2Y8EFyz_iVHRBMULzLJ5HFw7U8wpTxwu11rKikQ3V9WeG__ZwrTgX7GJo9P3LxdLuCBI_QvzV5il3YBa4biPK5aCLcst9P7ssfyjWKjdYkY/s400/pasted+image+0+%25281%2529.png" width="400" /></a> <small><br>Index coverage report for indexed pages, which shows an example of the data freshness issues in Search Console in April 2019, with a longer time between 2 updates than what is usually observed.</small></p> <p>Because the whole Search index issue took several days to roll back (see explanation above), we were delayed focusing on fixing the Search Console database until a few days later, only after the indexing issues were fixed. We communicated on April 15th - <a href="https://mobile.twitter.com/googlewmc/status/1117739223405211650">tweet</a> - that the Search Console was having troubles and that we were working on fixing it, and we completed our fixes on April 28th (day on which the reports started gathering fresh data again, see graph above). We communicated on Twitter on April 30th that the issue was resolved- <a href="https://mobile.twitter.com/googlewmc/status/1123192022179962880">tweet</a>.</p> <h3>3. Other issues unrelated to the main indexing bug</h3> <p>Google Search relies on a number of systems that work together. While some of those systems can be tightly linked to one another, in some cases different parts of the system experience unrelated problems around the same time.</p> <p>In the present case for example, around the same time as the main indexing bug explained above, we also had brief problems gathering fresh Google News content. Additionally, while rendering pages, certain URLs started to redirect Googlebot to other unrelated pages. These issues were entirely unrelated to the indexing bug, and were quickly resolved (<a href="https://mobile.twitter.com/searchliaison/status/1118237091014385664">tweet 1</a> & <a href="https://mobile.twitter.com/googlewmc/status/1121538876126969859">tweet 2</a>).</p> <h2>Our communication and how we intend on doing better</h2> <p>In addition to communicating on social media (as highlighted above) during those few weeks, we also gave webmasters more details in 2 other channels: Search Console, as well as the Search Console Help Center.</p> <h3>In the Search Console Help Center</h3> <p>We updated our “<a href="https://support.google.com/webmasters/answer/6211453#general">Data anomalies in Search Console</a>” help page after the issue was fully identified. This page is used to communicate information about data disruptions to our Search Console service when the impact affects a large number of website owners.</p> <h3>In Search Console</h3> <p>Because we know that not all our users read social media or the external Help Center page, we also added annotations on Search Console reports, to notify users that the data might not be accurate (see image below). We added this information after the resolution of the bugs. Clicking on “see here for more details” sends users to the “Data Anomalies” page in the Help Center.</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhOEAFlQBbTXgfaS74PG_M5QizdlzXAbcrqjZJtvGbIYTEM9WLdMcRuXQokgb60Pg_OkGtNIMYRRrASePmhGBb-peu_O-12MaMp635lWl2XU5-HXqcfXetm9Ox0ZwLy1vlry00x/s1600/pasted+image+0+%25282%2529.png" imageanchor="1" ><img border="0" data-original-height="266" data-original-width="912" height="117" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhOEAFlQBbTXgfaS74PG_M5QizdlzXAbcrqjZJtvGbIYTEM9WLdMcRuXQokgb60Pg_OkGtNIMYRRrASePmhGBb-peu_O-12MaMp635lWl2XU5-HXqcfXetm9Ox0ZwLy1vlry00x/s400/pasted+image+0+%25282%2529.png" width="400" /></a> <br>Index coverage report for indexed pages, which shows an example of the data annotations that we can include to notify users of specific issues.</p> <h3>Communications going forward</h3> <p>When things break at Google, we have a strong “postmortem” culture: creating a document to debrief on the breakage, and try to avoid it happening next time. The whole process is described in more detail at the <a href="https://landing.google.com/sre/sre-book/chapters/postmortem-culture/">Google Site Reliability Engineering website</a>.</p> <p>In the wake of the April indexing issues, we included in the postmortem how to better communicate with webmasters in case of large system failures. Our key decisions were:</p> <ol><li>Explore ways to more quickly share information within Search Console itself about widespread bugs, and have that information serve as the main point of reference for webmasters to check, in case they are suspecting outages.</li> <li>More promptly post to the Search Console data anomalies page, when relevant (if the disturbance is going to be seen over the long term in Search Console data).</li> <li>Continue tweeting as quickly as we can about such issues to quickly reassure webmasters we’re aware and that the issue is on our end.</li> </ol> <p>Those commitments should make potential future similar situations more transparent for webmasters as a whole.</p> <h3>Putting our resolutions into action: the “new URLs not indexed” case study</h3> <p>On May 22nd, we tested our new communications strategy, as we experienced another issue. Here’s what happened: while processing certain URLs, our duplicate management system ran out of memory after a planned infrastructure upgrade, which caused all incoming URLs to stop processing.</p> <p>Here is a timeline of how we thought about communications, following the 3 points highlighted just above:</p> <ol><li>We noticed the issue (around 5.30am California time, May 22nd)<br>We <a href="https://mobile.twitter.com/googlewmc/status/1131193175652032516">tweeted</a> about the ongoing issue (around 6.40am California time, May 22nd)<br>We <a href="https://mobile.twitter.com/googlewmc/status/1131425970521542656">tweeted</a> about the resolution (around 10pm California time, May 22nd)</li> <li>We evaluated updating the “Data Anomalies” page in the Help Center, but decided against it since we did not expect any long-term impact for the majority of webmasters' Search Console data in the long run.</li> <li>The confusion that this issue created for many confirmed our earlier conclusions that we need a way to signal more clearly in the Search Console itself that there might be a disruption to one of our systems which could impact webmasters. Such a solution might take longer to implement. We will communicate on this topic in the future, as we have more news.</li> </ol> <p>Last week, we also had another indexing issue. As with May 22, we <a href="https://mobile.twitter.com/googlewmc/status/1159380861151797250">tweeted</a> to let people know there was an issue, that we were working to fix it and when the issue was resolved.</p> <h2>How to debug and communicate with us</h2> <p>We hope that this post will bring more clarity to how our systems are complex and can sometimes break, and will also help you understand how we communicate about these matters. But while this post focuses on a widespread breakage of our systems, it’s important to keep in mind that most website indexing issues are caused by an individual website’s configuration, which can create difficulties for Google Search to index that website properly. For those cases, all webmasters can debug issues using <a href="https://search.google.com/search-console">Search Console</a> and our <a href="https://support.google.com/webmasters">Help center</a>. After doing so, if you still think that an issue is not coming from your site or don’t know how to resolve it, come talk to us and our community, we always want to take feedback from our users. Here is how to signal an issue to us:<br><br></p> <ul><li>Check our <a href="https://support.google.com/webmasters/community">Webmaster Community</a>, sometimes other webmasters have highlighted an issue that also impacts your site.</li> <li>In person! We love contact, come and talk to us at events. <a href="https://www.google.com/webmasters/connect/">Calendar</a>.</li> <li>Within our products! The Search Console feedback tool is very useful to our teams.</li> <li><a href="https://mobile.twitter.com/googlewmc">Twitter</a> and <a href="https://www.youtube.com/user/GoogleWebmasterHelp">YouTube</a>!</li></ul> <br> <span class="byline-author">Posted by Vincent Courson, Google Search Outreach</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>Most of the time, our search engine runs properly. Our teams work hard to prevent technical issues that could affect our users who are searching the web, or webmasters whose sites we index and serve to users. Similarly, the underlying systems that we use to power the search engine also run as intended most of the time. When small disruptions happen, they are largely not visible to anyone except our teams who ensure that our products are up and running. However, like all complex systems, sometimes larger outages can occur, which may lead to disruptions for both users and website creators.</p> <p>In the last few months, such a situation occurred with our indexing systems, which had a ripple effect on some other parts of our infrastructure. While we worked as quickly as possible to remedy the situation, we apologize for the disruption, as our goal is to continuously provide high-quality products to our users and to the web ecosystem.</p> <p>Since then, we took a closer, careful look into the situation. In the process, we learned a few lessons that we'd like to share with you today. In this blog post, we will go into more details about what happened, clarify how we plan to communicate better if such things happen in the future, and remind website owners of the channels they can use to communicate with us.</p> <h2>So, what happened a few months ago?</h2> <p>In April, we had several issues related to our index. The Search index is the database that holds the hundreds of billions of web pages that we crawled on the web and that we think could answer some of our users’ queries. When a user enters a query in the Google search engine, our ranking algorithms sort through those pages in our Search index to find the most relevant, useful results in a fraction of a second. Here is more information on what happened.</p> <h3>1. The indexing issue</h3> <p>To start it off, we temporarily lost part of the Search index.<br>Wait... What? What do you mean “lost part of the index?” Is that even possible?</p> <p>Basically, when serving search results to users, to accelerate the speed of the service, the query of the user only “travels” as far as the closest of our data centers supporting the Google Search product, from which the Search Engine Results Page (SERP) is generated. So when there are modifications to the composition of the index (some pages added and removed, documents are merged, or other types of data modification), those modifications need to be reflected in all of those data centers. The consequence is that users all over the world are consistently served pages from the most recent version of the index.</p> <p><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlKmwOg0tP0MH7BMFbVu6haYtqJQE-IBkBpmMfZ3Lj_1p4C9s5fbpd-nYzWBHmSmyg-6pr4GQMLrnxI3R3puqEK40LByTpivFWCOSlnP41xuXE1bPRzwcbFJFpdMekHNTuGnwh/s1600/pasted+image+0.png" imageanchor="1" ><img border="0" data-original-height="333" data-original-width="500" height="266" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlKmwOg0tP0MH7BMFbVu6haYtqJQE-IBkBpmMfZ3Lj_1p4C9s5fbpd-nYzWBHmSmyg-6pr4GQMLrnxI3R3puqEK40LByTpivFWCOSlnP41xuXE1bPRzwcbFJFpdMekHNTuGnwh/s400/pasted+image+0.png" width="400" /></a> <small><br>Google owns and operates data centers (like the one pictured above) around the world, to keep our products running 24 hours a day, 7 days a week - <a href="https://www.google.com/about/datacenters/">source</a></small></p> <p>Keeping the index unified across all those data centers is a non trivial task. For large user-facing services, we may deploy updates by starting in one data center and expand until all relevant data centers are updated. For sensitive pieces of infrastructure, we may extend a rollout over several days, interleaving them across instances in different geographic regions. <a href="https://landing.google.com/sre/sre-book/chapters/release-engineering/">source</a></p> <p>So, as we pushed some planned changes to the Search index, on April 5th parts of the deployment system broke, on a Friday no-less! More specifically: as we were updating the index over some of our data centers, a small number of documents ended up being dropped from the index accidentally. Hence: “we lost part of the index.”</p> <p>Luckily, our <a href="https://landing.google.com/sre/sre-book/chapters/being-on-call/">on-call engineers</a> caught the issue pretty quickly, at the same time as we started picking up chatter on social media (thanks to everyone who notified us over that weekend!). As a result, we were able to start reverting the Search index to its previous stable state in all data centers only a few hours after the issue was uncovered (we keep back-ups of our indexes just in case such events happen).</p> <p>We communicated on Sunday, <a href="https://mobile.twitter.com/searchliaison/status/1114961119699804160">April 7th</a> that we were aware of the issue, and that things were starting to get back to normal. As data centers were progressively reverting back to a stable index, we continued updating on Twitter (on <a href="https://mobile.twitter.com/searchliaison/status/1115342598279913472">April 8th</a>, on <a href="https://mobile.twitter.com/searchliaison/status/1115700559317585920">April 9th</a>), until we were confident that all data centers were fully back to a complete version of the index on <a href="https://mobile.twitter.com/searchliaison/status/1116152155713392640">April 11th</a>.</p> <h3>2. The Search Console issue</h3> <p><a href="https://search.google.com/search-console/about">Search Console</a> is the set of tools and reports any webmaster can use to access data about their website’s performance in Search. For example, it shows how many impressions and clicks a website gets in the organic search results every day, or information on what pages of a website are included and excluded from the Search index.</p> <p>As a consequence of the Search index having the issues we described above, Search Console started to also show inconsistencies. This is because some of the data that surfaces in Search Console originates from the Search index itself:</p> <ul><li>the <a href="https://support.google.com/webmasters/answer/7440203">Index Coverage report</a> depends on the Search index being consistent across data centers.</li> <li>when we store a page in the Search index, we can annotate the entry with key signals about the page, like the fact that the page contains rich results markup for example. Therefore, an issue with the Search index can have an impact on the <a href="https://support.google.com/webmasters/answer/7552505">Rich Results reports</a> in Search Console.</li></ul> <p>Basically, many Search Console individual reports read data from a dedicated database. That database is partially built by using information that comes from the Search index. As we had to revert back to a previous version of the Search index, we also had to pause the updating of the Search Console database. This resulted in plateau-ing data for some reports (and flakiness in others, like the URL inspection tool).</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjkmVWgQhTSSF_Yiv8xxdKD6wbYB2Y8EFyz_iVHRBMULzLJ5HFw7U8wpTxwu11rKikQ3V9WeG__ZwrTgX7GJo9P3LxdLuCBI_QvzV5il3YBa4biPK5aCLcst9P7ssfyjWKjdYkY/s1600/pasted+image+0+%25281%2529.png" imageanchor="1" ><img border="0" data-original-height="266" data-original-width="911" height="117" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjkmVWgQhTSSF_Yiv8xxdKD6wbYB2Y8EFyz_iVHRBMULzLJ5HFw7U8wpTxwu11rKikQ3V9WeG__ZwrTgX7GJo9P3LxdLuCBI_QvzV5il3YBa4biPK5aCLcst9P7ssfyjWKjdYkY/s400/pasted+image+0+%25281%2529.png" width="400" /></a> <small><br>Index coverage report for indexed pages, which shows an example of the data freshness issues in Search Console in April 2019, with a longer time between 2 updates than what is usually observed.</small></p> <p>Because the whole Search index issue took several days to roll back (see explanation above), we were delayed focusing on fixing the Search Console database until a few days later, only after the indexing issues were fixed. We communicated on April 15th - <a href="https://mobile.twitter.com/googlewmc/status/1117739223405211650">tweet</a> - that the Search Console was having troubles and that we were working on fixing it, and we completed our fixes on April 28th (day on which the reports started gathering fresh data again, see graph above). We communicated on Twitter on April 30th that the issue was resolved- <a href="https://mobile.twitter.com/googlewmc/status/1123192022179962880">tweet</a>.</p> <h3>3. Other issues unrelated to the main indexing bug</h3> <p>Google Search relies on a number of systems that work together. While some of those systems can be tightly linked to one another, in some cases different parts of the system experience unrelated problems around the same time.</p> <p>In the present case for example, around the same time as the main indexing bug explained above, we also had brief problems gathering fresh Google News content. Additionally, while rendering pages, certain URLs started to redirect Googlebot to other unrelated pages. These issues were entirely unrelated to the indexing bug, and were quickly resolved (<a href="https://mobile.twitter.com/searchliaison/status/1118237091014385664">tweet 1</a> & <a href="https://mobile.twitter.com/googlewmc/status/1121538876126969859">tweet 2</a>).</p> <h2>Our communication and how we intend on doing better</h2> <p>In addition to communicating on social media (as highlighted above) during those few weeks, we also gave webmasters more details in 2 other channels: Search Console, as well as the Search Console Help Center.</p> <h3>In the Search Console Help Center</h3> <p>We updated our “<a href="https://support.google.com/webmasters/answer/6211453#general">Data anomalies in Search Console</a>” help page after the issue was fully identified. This page is used to communicate information about data disruptions to our Search Console service when the impact affects a large number of website owners.</p> <h3>In Search Console</h3> <p>Because we know that not all our users read social media or the external Help Center page, we also added annotations on Search Console reports, to notify users that the data might not be accurate (see image below). We added this information after the resolution of the bugs. Clicking on “see here for more details” sends users to the “Data Anomalies” page in the Help Center.</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhOEAFlQBbTXgfaS74PG_M5QizdlzXAbcrqjZJtvGbIYTEM9WLdMcRuXQokgb60Pg_OkGtNIMYRRrASePmhGBb-peu_O-12MaMp635lWl2XU5-HXqcfXetm9Ox0ZwLy1vlry00x/s1600/pasted+image+0+%25282%2529.png" imageanchor="1" ><img border="0" data-original-height="266" data-original-width="912" height="117" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhOEAFlQBbTXgfaS74PG_M5QizdlzXAbcrqjZJtvGbIYTEM9WLdMcRuXQokgb60Pg_OkGtNIMYRRrASePmhGBb-peu_O-12MaMp635lWl2XU5-HXqcfXetm9Ox0ZwLy1vlry00x/s400/pasted+image+0+%25282%2529.png" width="400" /></a> <br>Index coverage report for indexed pages, which shows an example of the data annotations that we can include to notify users of specific issues.</p> <h3>Communications going forward</h3> <p>When things break at Google, we have a strong “postmortem” culture: creating a document to debrief on the breakage, and try to avoid it happening next time. The whole process is described in more detail at the <a href="https://landing.google.com/sre/sre-book/chapters/postmortem-culture/">Google Site Reliability Engineering website</a>.</p> <p>In the wake of the April indexing issues, we included in the postmortem how to better communicate with webmasters in case of large system failures. Our key decisions were:</p> <ol><li>Explore ways to more quickly share information within Search Console itself about widespread bugs, and have that information serve as the main point of reference for webmasters to check, in case they are suspecting outages.</li> <li>More promptly post to the Search Console data anomalies page, when relevant (if the disturbance is going to be seen over the long term in Search Console data).</li> <li>Continue tweeting as quickly as we can about such issues to quickly reassure webmasters we’re aware and that the issue is on our end.</li> </ol> <p>Those commitments should make potential future similar situations more transparent for webmasters as a whole.</p> <h3>Putting our resolutions into action: the “new URLs not indexed” case study</h3> <p>On May 22nd, we tested our new communications strategy, as we experienced another issue. Here’s what happened: while processing certain URLs, our duplicate management system ran out of memory after a planned infrastructure upgrade, which caused all incoming URLs to stop processing.</p> <p>Here is a timeline of how we thought about communications, following the 3 points highlighted just above:</p> <ol><li>We noticed the issue (around 5.30am California time, May 22nd)<br>We <a href="https://mobile.twitter.com/googlewmc/status/1131193175652032516">tweeted</a> about the ongoing issue (around 6.40am California time, May 22nd)<br>We <a href="https://mobile.twitter.com/googlewmc/status/1131425970521542656">tweeted</a> about the resolution (around 10pm California time, May 22nd)</li> <li>We evaluated updating the “Data Anomalies” page in the Help Center, but decided against it since we did not expect any long-term impact for the majority of webmasters' Search Console data in the long run.</li> <li>The confusion that this issue created for many confirmed our earlier conclusions that we need a way to signal more clearly in the Search Console itself that there might be a disruption to one of our systems which could impact webmasters. Such a solution might take longer to implement. We will communicate on this topic in the future, as we have more news.</li> </ol> <p>Last week, we also had another indexing issue. As with May 22, we <a href="https://mobile.twitter.com/googlewmc/status/1159380861151797250">tweeted</a> to let people know there was an issue, that we were working to fix it and when the issue was resolved.</p> <h2>How to debug and communicate with us</h2> <p>We hope that this post will bring more clarity to how our systems are complex and can sometimes break, and will also help you understand how we communicate about these matters. But while this post focuses on a widespread breakage of our systems, it’s important to keep in mind that most website indexing issues are caused by an individual website’s configuration, which can create difficulties for Google Search to index that website properly. For those cases, all webmasters can debug issues using <a href="https://search.google.com/search-console">Search Console</a> and our <a href="https://support.google.com/webmasters">Help center</a>. After doing so, if you still think that an issue is not coming from your site or don’t know how to resolve it, come talk to us and our community, we always want to take feedback from our users. Here is how to signal an issue to us:<br><br></p> <ul><li>Check our <a href="https://support.google.com/webmasters/community">Webmaster Community</a>, sometimes other webmasters have highlighted an issue that also impacts your site.</li> <li>In person! We love contact, come and talk to us at events. <a href="https://www.google.com/webmasters/connect/">Calendar</a>.</li> <li>Within our products! The Search Console feedback tool is very useful to our teams.</li> <li><a href="https://mobile.twitter.com/googlewmc">Twitter</a> and <a href="https://www.youtube.com/user/GoogleWebmasterHelp">YouTube</a>!</li></ul> <br> <span class="byline-author">Posted by Vincent Courson, Google Search Outreach</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:When indexing goes wrong: how Google Search recovered from indexing issues & lessons learned since.&url=https://webmasters.googleblog.com/2019/08/when-indexing-goes-wrong-how-google.html?hl=zh_CN&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2019/08/when-indexing-goes-wrong-how-google.html?hl=zh_CN'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2019/08/when-indexing-goes-wrong-how-google.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=zh_CN' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=zh_CN' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=zh_CN' rel='tag'> webmaster community </a> </span> </div> </div> </div> <div class='post' data-id='1685947314817706235' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/07/helping-publishers-and-users-get-more.html?hl=zh_CN' itemprop='url' title='Helping publishers and users get more out of visual searches on Google Images with AMP'> Helping publishers and users get more out of visual searches on Google Images with AMP </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> 星期四, 七月 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>Google Images has made a series of changes to help people explore, learn and do more through visual search. An important element of visual search is the ability for users to scan many ideas before coming to a decision, whether it’s purchasing a product, learning more about a stylish room, or finding instructions for a DIY project. Often this involves loading many web pages, which can slow down a search considerably and prevent users from completing a task. </p> <p>As previewed at Google I/O, we’re launching a new AMP-powered feature in Google Images on the mobile web, Swipe to Visit, which makes it faster and easier for users to browse and visit web pages. After a Google Images user selects an image to view on a mobile device, they will get a preview of the website header, which can be easily swiped up to load the web page instantly. </p> <a href="https://3.bp.blogspot.com/-mjxaMYEDftw/XT9ZL987hHI/AAAAAAABEpo/XTD91NpGq4IWX6AmWY08y6yzqvn9-kcWgCLcBGAs/s1600/amp-phone%2B%25281%2529.gif" imageanchor="1" ><img border="0" data-original-height="1067" data-original-width="616" height="600" src="https://3.bp.blogspot.com/-mjxaMYEDftw/XT9ZL987hHI/AAAAAAABEpo/XTD91NpGq4IWX6AmWY08y6yzqvn9-kcWgCLcBGAs/s400/amp-phone%2B%25281%2529.gif" width="348" /></a> <p>Swipe to Visit uses AMP's prerender capability to show a preview of the page displayed at the bottom of the screen. When a user swipes up on the preview, the web page is displayed instantly and the publisher receives a pageview. The speed and ease of this experience makes it more likely for users to visit a publisher's site, while still allowing users to continue their browsing session.</p> <p>Publishers who support AMP don’t need to take any additional action for their sites to appear in Swipe to Visit on Google Images. Publishers who don’t support AMP can <a href="https://developers.google.com/search/docs/guides/enhance-amp">learn more about getting started with AMP here</a>. In the coming weeks, publishers can also view their traffic data from AMP in Google Images in a Search Console’s <a href="https://support.google.com/webmasters/answer/7576553">performance report</a> for Google Images in a new search area named “AMP on Image result”.</p> <p>We look forward to continuing to support the Google Images ecosystem with features that help users and publishers alike.</p> <br> <span class="byline-author">Posted by Assaf Broitman, Google Images PM</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>Google Images has made a series of changes to help people explore, learn and do more through visual search. An important element of visual search is the ability for users to scan many ideas before coming to a decision, whether it’s purchasing a product, learning more about a stylish room, or finding instructions for a DIY project. Often this involves loading many web pages, which can slow down a search considerably and prevent users from completing a task. </p> <p>As previewed at Google I/O, we’re launching a new AMP-powered feature in Google Images on the mobile web, Swipe to Visit, which makes it faster and easier for users to browse and visit web pages. After a Google Images user selects an image to view on a mobile device, they will get a preview of the website header, which can be easily swiped up to load the web page instantly. </p> <a href="https://3.bp.blogspot.com/-mjxaMYEDftw/XT9ZL987hHI/AAAAAAABEpo/XTD91NpGq4IWX6AmWY08y6yzqvn9-kcWgCLcBGAs/s1600/amp-phone%2B%25281%2529.gif" imageanchor="1" ><img border="0" data-original-height="1067" data-original-width="616" height="600" src="https://3.bp.blogspot.com/-mjxaMYEDftw/XT9ZL987hHI/AAAAAAABEpo/XTD91NpGq4IWX6AmWY08y6yzqvn9-kcWgCLcBGAs/s400/amp-phone%2B%25281%2529.gif" width="348" /></a> <p>Swipe to Visit uses AMP's prerender capability to show a preview of the page displayed at the bottom of the screen. When a user swipes up on the preview, the web page is displayed instantly and the publisher receives a pageview. The speed and ease of this experience makes it more likely for users to visit a publisher's site, while still allowing users to continue their browsing session.</p> <p>Publishers who support AMP don’t need to take any additional action for their sites to appear in Swipe to Visit on Google Images. Publishers who don’t support AMP can <a href="https://developers.google.com/search/docs/guides/enhance-amp">learn more about getting started with AMP here</a>. In the coming weeks, publishers can also view their traffic data from AMP in Google Images in a Search Console’s <a href="https://support.google.com/webmasters/answer/7576553">performance report</a> for Google Images in a new search area named “AMP on Image result”.</p> <p>We look forward to continuing to support the Google Images ecosystem with features that help users and publishers alike.</p> <br> <span class="byline-author">Posted by Assaf Broitman, Google Images PM</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Helping publishers and users get more out of visual searches on Google Images with AMP&url=https://webmasters.googleblog.com/2019/07/helping-publishers-and-users-get-more.html?hl=zh_CN&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/07/helping-publishers-and-users-get-more.html?hl=zh_CN'> <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/07/helping-publishers-and-users-get-more.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/AMP?hl=zh_CN' rel='tag'> AMP </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/images?hl=zh_CN' rel='tag'> images </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/speed?hl=zh_CN' rel='tag'> speed </a> </span> </div> </div> </div> <div class='post' data-id='5618870169875080581' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/04/instant-loading-amp-pages-from-your-own.html?hl=zh_CN' itemprop='url' title='Instant-loading AMP pages from your own domain'> Instant-loading AMP pages from your own domain </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> 星期二, 四月 16, 2019 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p>Today we are rolling out support in Google Search’s <a href="https://blog.google/products/search/search-results-are-officially-ampd/">AMP web results</a> (also known as “blue links”) to link to <a href="https://developers.google.com/web/updates/2018/11/signed-exchanges">signed exchanges</a>, an emerging new feature of the web enabled by the <a href="https://tools.ietf.org/id/draft-yasskin-dispatch-web-packaging-00.html">IETF web packaging specification</a>. Signed exchanges enable displaying the publisher’s domain when content is instantly loaded via Google Search. This is available in browsers that support the necessary web platform feature—as of the time of writing, Google Chrome—and availability will expand to include other browsers as they gain support (e.g. the upcoming version of Microsoft Edge).</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiyX3fKP0Y9fYwcf5hnwEx7GVl7oro36ggdhP_ggKe4iLfi4vEmnzNj5Cc8N07864z1FF3npv6oRfzMT4BYZ0uT-_kNqJcnezw-oS-xyNvOyHCntcSOLlqPESEzLkAQkiTYWIXB/s1600/ampdev-sxg.gif" imageanchor="1" ><img border="0" data-original-height="864" data-original-width="429" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiyX3fKP0Y9fYwcf5hnwEx7GVl7oro36ggdhP_ggKe4iLfi4vEmnzNj5Cc8N07864z1FF3npv6oRfzMT4BYZ0uT-_kNqJcnezw-oS-xyNvOyHCntcSOLlqPESEzLkAQkiTYWIXB/s400/ampdev-sxg.gif" width="199" /></a> <h3>Background on AMP’s instant loading</h3> <p>One of AMP's biggest user benefits has been the unique ability to instantly load AMP web pages that users click on in Google Search. Near-instant loading works by requesting content ahead of time, balancing the likelihood of a user clicking on a result with device and network constraints–and <a href="https://blog.amp.dev/2018/07/23/privacy-and-user-choice-in-amps-software-architecture/">doing it in a privacy-sensitive way</a>.</p> <p>We believe that privacy-preserving instant loading web content is a transformative user experience, but in order to accomplish this, we had to make trade-offs; namely, the <a href="https://developers.googleblog.com/2017/02/whats-in-amp-url.html">URLs</a> displayed in browser address bars begin with google.com/amp, as a consequence of being shown in the Google AMP Viewer, rather than display the domain of the publisher. We heard both user and publisher feedback over this, and last year we <a href="https://blog.amp.dev/2018/01/09/improving-urls-for-amp-pages/">identified</a> a web platform innovation that provides a solution that shows the content’s original URL while still retaining AMP's instant loading.</p> <h3>Introducing signed exchanges</h3> <p>A signed exchange is a file format, defined in the <a href="https://github.com/WICG/webpackage">web packaging specification</a>, that allows the browser to trust a document as if it belongs to your <a href="https://en.wikipedia.org/wiki/Same-origin_policy">origin</a>. This allows you to use first-party cookies and storage to customize content and simplify analytics integration. Your page appears under your URL instead of the google.com/amp URL.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgEsuMHfHYZP_H8qXnOuv5AXgxJay_IsvwRPtwMqRmjyX3b9U2BGhmeciIpgf-_FQDxRGJY_nXmJHRJ9YuFLNgbNsw1fC7OxfR_lZsvQRNksjPeDPHURJFGCncdFW7z9SwXqf8G/s1600/url_bar2.gif" imageanchor="1" ><img border="0" data-original-height="182" data-original-width="1600" height="46" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgEsuMHfHYZP_H8qXnOuv5AXgxJay_IsvwRPtwMqRmjyX3b9U2BGhmeciIpgf-_FQDxRGJY_nXmJHRJ9YuFLNgbNsw1fC7OxfR_lZsvQRNksjPeDPHURJFGCncdFW7z9SwXqf8G/s400/url_bar2.gif" width="400" /></a> <p>Google Search links to signed exchanges when the publisher, browser, and the Search experience context all support it. As a publisher, you will need to publish both the signed exchange version of the content in addition to the non-signed exchange version. Learn more about how <a href="https://developers.google.com/search/docs/guides/about-amp">Google Search supports signed exchange</a>.</p> <h3>Getting started with signed exchanges</h3> <p>Many publishers have already begun to publish signed exchanges since the <a href="https://blog.amp.dev/2018/11/13/developer-preview-of-better-amp-urls-in-google-search/">developer preview</a> opened up last fall. To implement signed exchanges in your own serving infrastructure, follow the guide “<a href="https://amp.dev/documentation/guides-and-tutorials/optimize-and-measure/signed-exchange">Serve AMP using Signed Exchanges</a>” available at amp.dev.</p> <p>If you use a CDN provider, ask them if they can provide AMP signed exchanges. <a href="https://www.cloudflare.com/">Cloudflare</a> has recently <a href="http://blog.cloudflare.com/announcing-amp-real-url/">announced</a> that it is offering signed exchanges to all of its customers free of charge.</p> <p>Check out our resources like the <a href="https://support.google.com/webmasters/community">webmaster community</a> or <a href="https://amp.dev/support/">get in touch with members of the AMP Project</a> with any questions. You can also <a href="https://github.com/WICG/webpackage/issues">provide feedback on the signed exchange specification</a>.</p> <br> <span class="byline-author">Posted by Devin Mullins and Greg Rogers</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p>Today we are rolling out support in Google Search’s <a href="https://blog.google/products/search/search-results-are-officially-ampd/">AMP web results</a> (also known as “blue links”) to link to <a href="https://developers.google.com/web/updates/2018/11/signed-exchanges">signed exchanges</a>, an emerging new feature of the web enabled by the <a href="https://tools.ietf.org/id/draft-yasskin-dispatch-web-packaging-00.html">IETF web packaging specification</a>. Signed exchanges enable displaying the publisher’s domain when content is instantly loaded via Google Search. This is available in browsers that support the necessary web platform feature—as of the time of writing, Google Chrome—and availability will expand to include other browsers as they gain support (e.g. the upcoming version of Microsoft Edge).</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiyX3fKP0Y9fYwcf5hnwEx7GVl7oro36ggdhP_ggKe4iLfi4vEmnzNj5Cc8N07864z1FF3npv6oRfzMT4BYZ0uT-_kNqJcnezw-oS-xyNvOyHCntcSOLlqPESEzLkAQkiTYWIXB/s1600/ampdev-sxg.gif" imageanchor="1" ><img border="0" data-original-height="864" data-original-width="429" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiyX3fKP0Y9fYwcf5hnwEx7GVl7oro36ggdhP_ggKe4iLfi4vEmnzNj5Cc8N07864z1FF3npv6oRfzMT4BYZ0uT-_kNqJcnezw-oS-xyNvOyHCntcSOLlqPESEzLkAQkiTYWIXB/s400/ampdev-sxg.gif" width="199" /></a> <h3>Background on AMP’s instant loading</h3> <p>One of AMP's biggest user benefits has been the unique ability to instantly load AMP web pages that users click on in Google Search. Near-instant loading works by requesting content ahead of time, balancing the likelihood of a user clicking on a result with device and network constraints–and <a href="https://blog.amp.dev/2018/07/23/privacy-and-user-choice-in-amps-software-architecture/">doing it in a privacy-sensitive way</a>.</p> <p>We believe that privacy-preserving instant loading web content is a transformative user experience, but in order to accomplish this, we had to make trade-offs; namely, the <a href="https://developers.googleblog.com/2017/02/whats-in-amp-url.html">URLs</a> displayed in browser address bars begin with google.com/amp, as a consequence of being shown in the Google AMP Viewer, rather than display the domain of the publisher. We heard both user and publisher feedback over this, and last year we <a href="https://blog.amp.dev/2018/01/09/improving-urls-for-amp-pages/">identified</a> a web platform innovation that provides a solution that shows the content’s original URL while still retaining AMP's instant loading.</p> <h3>Introducing signed exchanges</h3> <p>A signed exchange is a file format, defined in the <a href="https://github.com/WICG/webpackage">web packaging specification</a>, that allows the browser to trust a document as if it belongs to your <a href="https://en.wikipedia.org/wiki/Same-origin_policy">origin</a>. This allows you to use first-party cookies and storage to customize content and simplify analytics integration. Your page appears under your URL instead of the google.com/amp URL.</p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgEsuMHfHYZP_H8qXnOuv5AXgxJay_IsvwRPtwMqRmjyX3b9U2BGhmeciIpgf-_FQDxRGJY_nXmJHRJ9YuFLNgbNsw1fC7OxfR_lZsvQRNksjPeDPHURJFGCncdFW7z9SwXqf8G/s1600/url_bar2.gif" imageanchor="1" ><img border="0" data-original-height="182" data-original-width="1600" height="46" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgEsuMHfHYZP_H8qXnOuv5AXgxJay_IsvwRPtwMqRmjyX3b9U2BGhmeciIpgf-_FQDxRGJY_nXmJHRJ9YuFLNgbNsw1fC7OxfR_lZsvQRNksjPeDPHURJFGCncdFW7z9SwXqf8G/s400/url_bar2.gif" width="400" /></a> <p>Google Search links to signed exchanges when the publisher, browser, and the Search experience context all support it. As a publisher, you will need to publish both the signed exchange version of the content in addition to the non-signed exchange version. Learn more about how <a href="https://developers.google.com/search/docs/guides/about-amp">Google Search supports signed exchange</a>.</p> <h3>Getting started with signed exchanges</h3> <p>Many publishers have already begun to publish signed exchanges since the <a href="https://blog.amp.dev/2018/11/13/developer-preview-of-better-amp-urls-in-google-search/">developer preview</a> opened up last fall. To implement signed exchanges in your own serving infrastructure, follow the guide “<a href="https://amp.dev/documentation/guides-and-tutorials/optimize-and-measure/signed-exchange">Serve AMP using Signed Exchanges</a>” available at amp.dev.</p> <p>If you use a CDN provider, ask them if they can provide AMP signed exchanges. <a href="https://www.cloudflare.com/">Cloudflare</a> has recently <a href="http://blog.cloudflare.com/announcing-amp-real-url/">announced</a> that it is offering signed exchanges to all of its customers free of charge.</p> <p>Check out our resources like the <a href="https://support.google.com/webmasters/community">webmaster community</a> or <a href="https://amp.dev/support/">get in touch with members of the AMP Project</a> with any questions. You can also <a href="https://github.com/WICG/webpackage/issues">provide feedback on the signed exchange specification</a>.</p> <br> <span class="byline-author">Posted by Devin Mullins and Greg Rogers</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:Instant-loading AMP pages from your own domain&url=https://webmasters.googleblog.com/2019/04/instant-loading-amp-pages-from-your-own.html?hl=zh_CN&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/instant-loading-amp-pages-from-your-own.html?hl=zh_CN'> <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/instant-loading-amp-pages-from-your-own.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'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/AMP?hl=zh_CN' rel='tag'> AMP </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile?hl=zh_CN' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </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=zh_CN' 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'> 星期三, 四月 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=zh_CN&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=zh_CN'> <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'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=zh_CN' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=zh_CN' 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=zh_CN' 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'> 星期二, 三月 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=zh_CN&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=zh_CN'> <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'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=zh_CN' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=zh_CN' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20queries?hl=zh_CN' rel='tag'> search queries </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> </span> </div> </div> </div> <div class='post' data-id='3051682362674471538' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2019/01/ways-to-succeed-in-google-news.html?hl=zh_CN' itemprop='url' title='Ways to succeed in Google News'> Ways to succeed in Google News </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> 星期四, 一月 17, 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"> With the New Year now underway, we'd like to offer some best practices and advice we hope will lead publishers to more success within Google News in 2019. <br /> <h2> General advice</h2> There is a lot of helpful information to consider within the <a href="https://support.google.com/news/publisher-center/#topic=9010378">Google News Publisher Help Center</a>. Be sure to have read the material in this area, in particular the <a href="https://support.google.com/news/publisher-center/answer/6204050">content</a> and <a href="https://support.google.com/news/publisher-center/topic/9010253">technical</a> guidelines. <br /> <h2> Headlines and dates</h2> <br /> <ul style="text-align: left;"> <li><strong>Present clear headlines:</strong> Google News looks at a variety of signals to determine the headline of an article, including within your HTML title tag and for the most prominent text on the page. <a href="https://support.google.com/news/publisher-center/answer/93981">Review our headline tips</a>.</li> <li><strong>Provide accurate times and dates:</strong> Google News tries to determine the time and date to display for an article in a variety of ways. You can help ensure we get it right by using the following methods:</li> <ul> <li><strong>Show one clear date and time:</strong> As per our <a href="https://support.google.com/news/publisher-center/answer/70871">date guidelines</a>, show a clear, visible date and time between the headline and the article text. Prevent other dates from appearing on the page whenever possible, such as for related stories.</li> <li><strong>Use structured data: </strong>Use the <code>datePublished</code> and <code>dateModified</code> schema and use the correct time zone designator for <a href="https://developers.google.com/search/docs/data-types/article#amp">AMP</a> or <a href="https://developers.google.com/search/docs/data-types/article#non-amp">non-AMP pages</a>. </li> </ul> </ul> <ul style="text-align: left;"> <li><strong>Avoid artificially freshening stories:</strong> If an article has been substantially changed, it can make sense to give it a fresh date and time. However, don't artificially freshen a story without adding significant information or some other compelling reason for the freshening. Also, do not create a very slightly updated story from one previously published, then delete the old story and redirect to the new one. That's against our <a href="https://support.google.com/news/publisher-center/answer/68323">article URLs</a> guidelines.</li> </ul> <h2> Duplicate content</h2> Google News seeks to reward independent, original journalistic content by giving credit to the originating publisher, as both users and publishers would prefer. This means we try not to allow duplicate content—which includes scraped, rewritten, or republished material—to perform better than the original content. In line with this, these are guidelines publishers should follow: <br /> <br /> <ul style="text-align: left;"> <li><strong>Block scraped content: </strong><a href="https://support.google.com/webmasters/answer/2721312">Scraping</a><strong> </strong>commonly refers to taking material from another site, often on an automated basis. Sites that scrape content must <a href="https://support.google.com/news/publisher-center/answer/93977">block</a> scraped content from Google News.</li> <li><strong>Block rewritten content: </strong>Rewriting refers to taking material from another site, then rewriting that material so that it is not identical. Sites that rewrite content in a way that provides no substantial or clear added value must <a href="https://support.google.com/news/publisher-center/answer/93977">block</a> that rewritten content from Google News. This includes, but is not limited to, rewrites that make only very slight changes or those that make many word replacements but still keep the original article's overall meaning.</li> <li><strong>Block or consider canonical for republished content:</strong> Republishing<strong> </strong>refers to when a publisher has permission from another publisher or author to republish an original work, such as material from wire services or in partnership with other publications.<br />Publishers that allow others to republish content can help ensure that their original versions perform better in Google News by asking those republishing to <a href="https://support.google.com/news/publisher-center/answer/93977">block</a> or make use of <a href="https://support.google.com/news/publisher-center/answer/2589949">canonical</a>.<br />Google News also encourages those that republish material to consider proactively <a href="https://support.google.com/news/publisher-center/answer/93977">blocking</a> such content or making use of the <a href="https://support.google.com/news/publisher-center/answer/2589949">canonical</a>, so that we can better identify the original content and credit it appropriately.</li> <li><strong>Avoid duplicate content: </strong>If you operate a network of news sites that share content, the advice above about republishing is applicable to your network. Select what you consider to be the original article and consider <a href="https://support.google.com/news/publisher-center/answer/2589949">blocking duplicates</a> or making use of the <a href="https://support.google.com/news/publisher-center/answer/2589949">canonical</a> to point to the original.</li> </ul> <br /> <h2> Transparency</h2> <br /> <ul style="text-align: left;"> <li><strong>Be transparent:</strong> Visitors to your site want to trust and understand who publishes it and information about those who have written articles. That's why our <a href="https://support.google.com/news/publisher-center/answer/6204050">content guidelines</a> stress that content should have posts with clear bylines, information about authors, and contact information for the publication.</li> <li><strong>Don't be deceptive: </strong>Our <a href="https://support.google.com/news/producer/answer/6204050">content policies</a> do not allow sites or accounts that impersonate any person or organization, or that misrepresent or conceal their ownership or primary purpose. We do not allow sites or accounts that engage in coordinated activity to mislead users. This includes, but isn't limited to, sites or accounts that misrepresent or conceal their country of origin or that direct content at users in another country under false premises.</li> </ul> <br /> <h2> More tips</h2> <br /> <ul style="text-align: left;"> <li><strong>Avoid taking part in link schemes: </strong>Don't participate in link schemes, which can include <a href="https://webmasters.googleblog.com/2017/05/a-reminder-about-links-in-large-scale.html">large-scale article marketing programs</a> or selling links that pass PageRank. Review our page on <a href="https://support.google.com/webmasters/answer/66356">link schemes</a> for more information.</li> <li><strong>Use structured data for rich presentation:</strong> Both those using <a href="https://www.ampproject.org/">AMP</a> and non-AMP pages can make use of <a href="https://developers.google.com/search/docs/data-types/article#non-amp-sd">structured data</a> to optimize your content for rich results or carousel-like presentations.</li> <li><strong>Protect your users and their data</strong>: Consider securing every page of your website with HTTPS to protect the integrity and confidentiality of the data users exchange on your site. You can find more useful tips in our <a href="https://support.google.com/webmasters/answer/6073543?hl=en">best practices</a> on how to implement HTTPS.</li> </ul> <br /> <h2> Here's to a great 2019!</h2> We hope these tips help publishers succeed in Google News over the coming year. For those who have more questions about Google News, we are unable to do one-to-one support. However, we do monitor our <a href="https://support.google.com/news/publisher-center/threads?hl=en&max_results=20">Google News Publisher Forum</a>—which has been newly-revamped—and try to provide guidance on questions that might help a number of publishers all at once. The forum is also a great resource where publishers share tips and advice with each other. <br /> <span class="byline-author">Posted by Danny Sullivan, Public Liaison for Search</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"> With the New Year now underway, we'd like to offer some best practices and advice we hope will lead publishers to more success within Google News in 2019. <br /> <h2> General advice</h2> There is a lot of helpful information to consider within the <a href="https://support.google.com/news/publisher-center/#topic=9010378">Google News Publisher Help Center</a>. Be sure to have read the material in this area, in particular the <a href="https://support.google.com/news/publisher-center/answer/6204050">content</a> and <a href="https://support.google.com/news/publisher-center/topic/9010253">technical</a> guidelines. <br /> <h2> Headlines and dates</h2> <br /> <ul style="text-align: left;"> <li><strong>Present clear headlines:</strong> Google News looks at a variety of signals to determine the headline of an article, including within your HTML title tag and for the most prominent text on the page. <a href="https://support.google.com/news/publisher-center/answer/93981">Review our headline tips</a>.</li> <li><strong>Provide accurate times and dates:</strong> Google News tries to determine the time and date to display for an article in a variety of ways. You can help ensure we get it right by using the following methods:</li> <ul> <li><strong>Show one clear date and time:</strong> As per our <a href="https://support.google.com/news/publisher-center/answer/70871">date guidelines</a>, show a clear, visible date and time between the headline and the article text. Prevent other dates from appearing on the page whenever possible, such as for related stories.</li> <li><strong>Use structured data: </strong>Use the <code>datePublished</code> and <code>dateModified</code> schema and use the correct time zone designator for <a href="https://developers.google.com/search/docs/data-types/article#amp">AMP</a> or <a href="https://developers.google.com/search/docs/data-types/article#non-amp">non-AMP pages</a>. </li> </ul> </ul> <ul style="text-align: left;"> <li><strong>Avoid artificially freshening stories:</strong> If an article has been substantially changed, it can make sense to give it a fresh date and time. However, don't artificially freshen a story without adding significant information or some other compelling reason for the freshening. Also, do not create a very slightly updated story from one previously published, then delete the old story and redirect to the new one. That's against our <a href="https://support.google.com/news/publisher-center/answer/68323">article URLs</a> guidelines.</li> </ul> <h2> Duplicate content</h2> Google News seeks to reward independent, original journalistic content by giving credit to the originating publisher, as both users and publishers would prefer. This means we try not to allow duplicate content—which includes scraped, rewritten, or republished material—to perform better than the original content. In line with this, these are guidelines publishers should follow: <br /> <br /> <ul style="text-align: left;"> <li><strong>Block scraped content: </strong><a href="https://support.google.com/webmasters/answer/2721312">Scraping</a><strong> </strong>commonly refers to taking material from another site, often on an automated basis. Sites that scrape content must <a href="https://support.google.com/news/publisher-center/answer/93977">block</a> scraped content from Google News.</li> <li><strong>Block rewritten content: </strong>Rewriting refers to taking material from another site, then rewriting that material so that it is not identical. Sites that rewrite content in a way that provides no substantial or clear added value must <a href="https://support.google.com/news/publisher-center/answer/93977">block</a> that rewritten content from Google News. This includes, but is not limited to, rewrites that make only very slight changes or those that make many word replacements but still keep the original article's overall meaning.</li> <li><strong>Block or consider canonical for republished content:</strong> Republishing<strong> </strong>refers to when a publisher has permission from another publisher or author to republish an original work, such as material from wire services or in partnership with other publications.<br />Publishers that allow others to republish content can help ensure that their original versions perform better in Google News by asking those republishing to <a href="https://support.google.com/news/publisher-center/answer/93977">block</a> or make use of <a href="https://support.google.com/news/publisher-center/answer/2589949">canonical</a>.<br />Google News also encourages those that republish material to consider proactively <a href="https://support.google.com/news/publisher-center/answer/93977">blocking</a> such content or making use of the <a href="https://support.google.com/news/publisher-center/answer/2589949">canonical</a>, so that we can better identify the original content and credit it appropriately.</li> <li><strong>Avoid duplicate content: </strong>If you operate a network of news sites that share content, the advice above about republishing is applicable to your network. Select what you consider to be the original article and consider <a href="https://support.google.com/news/publisher-center/answer/2589949">blocking duplicates</a> or making use of the <a href="https://support.google.com/news/publisher-center/answer/2589949">canonical</a> to point to the original.</li> </ul> <br /> <h2> Transparency</h2> <br /> <ul style="text-align: left;"> <li><strong>Be transparent:</strong> Visitors to your site want to trust and understand who publishes it and information about those who have written articles. That's why our <a href="https://support.google.com/news/publisher-center/answer/6204050">content guidelines</a> stress that content should have posts with clear bylines, information about authors, and contact information for the publication.</li> <li><strong>Don't be deceptive: </strong>Our <a href="https://support.google.com/news/producer/answer/6204050">content policies</a> do not allow sites or accounts that impersonate any person or organization, or that misrepresent or conceal their ownership or primary purpose. We do not allow sites or accounts that engage in coordinated activity to mislead users. This includes, but isn't limited to, sites or accounts that misrepresent or conceal their country of origin or that direct content at users in another country under false premises.</li> </ul> <br /> <h2> More tips</h2> <br /> <ul style="text-align: left;"> <li><strong>Avoid taking part in link schemes: </strong>Don't participate in link schemes, which can include <a href="https://webmasters.googleblog.com/2017/05/a-reminder-about-links-in-large-scale.html">large-scale article marketing programs</a> or selling links that pass PageRank. Review our page on <a href="https://support.google.com/webmasters/answer/66356">link schemes</a> for more information.</li> <li><strong>Use structured data for rich presentation:</strong> Both those using <a href="https://www.ampproject.org/">AMP</a> and non-AMP pages can make use of <a href="https://developers.google.com/search/docs/data-types/article#non-amp-sd">structured data</a> to optimize your content for rich results or carousel-like presentations.</li> <li><strong>Protect your users and their data</strong>: Consider securing every page of your website with HTTPS to protect the integrity and confidentiality of the data users exchange on your site. You can find more useful tips in our <a href="https://support.google.com/webmasters/answer/6073543?hl=en">best practices</a> on how to implement HTTPS.</li> </ul> <br /> <h2> Here's to a great 2019!</h2> We hope these tips help publishers succeed in Google News over the coming year. For those who have more questions about Google News, we are unable to do one-to-one support. However, we do monitor our <a href="https://support.google.com/news/publisher-center/threads?hl=en&max_results=20">Google News Publisher Forum</a>—which has been newly-revamped—and try to provide guidance on questions that might help a number of publishers all at once. The forum is also a great resource where publishers share tips and advice with each other. <br /> <span class="byline-author">Posted by Danny Sullivan, Public Liaison for Search</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:Ways to succeed in Google News&url=https://webmasters.googleblog.com/2019/01/ways-to-succeed-in-google-news.html?hl=zh_CN&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/ways-to-succeed-in-google-news.html?hl=zh_CN'> <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/ways-to-succeed-in-google-news.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'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/Google%20News?hl=zh_CN' rel='tag'> Google News </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=zh_CN' rel='tag'> structured data </a> </span> </div> </div> </div> <div class='post' data-id='8573574762890954236' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2018/12/introducing-indexing-api-and-structured.html?hl=zh_CN' itemprop='url' title='Introducing the Indexing API and structured data for livestreams'> Introducing the Indexing API and structured data for livestreams </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> 星期三, 十二月 05, 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"> Over the past few years, it's become easier than ever to stream live videos online, from celebrity updates to special events. But it's not always easy for people to determine which videos are live and know when to tune in. <br /> Today, we're introducing new tools to help more people discover your livestreams in Search and Assistant. With livestream structured data and the Indexing API, you can let Google know when your video is live, so it will be eligible to appear with a red "live" badge: <br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhCFUaaFdYa6ChwDLURMG_tEFKiVI_qSSprYnN8CjVYU1BtW9qyXcGQ2CRbVUXCaodhgbQtKcDPAiAAfvVW81bahH8ON5bBhaC9-Og-E1UY1jJUnt4j1eNBzAlTV91enwPKq3ld/s1600/live-search-space.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="609" data-original-width="721" height="337" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhCFUaaFdYa6ChwDLURMG_tEFKiVI_qSSprYnN8CjVYU1BtW9qyXcGQ2CRbVUXCaodhgbQtKcDPAiAAfvVW81bahH8ON5bBhaC9-Og-E1UY1jJUnt4j1eNBzAlTV91enwPKq3ld/s400/live-search-space.png" width="400" /></a></div> <h2> Add livestream structured data to your page</h2> If your website streams live videos, <a href="https://developers.google.com/search/docs/data-types/livestream">use the livestream developer documentation</a> to flag your video as a live broadcast and mark the start and end times. In addition, VideoObject structured data is required to tell Google that there's a video on your page. <br /> <h2> Update Google quickly with the Indexing API</h2> The Indexing API now supports pages with livestream structured data. We encourage you to <a href="https://developers.google.com/search/docs/data-types/livestream#indexing-api">call the Indexing API</a> to request that your site is crawled in time for the livestream. We recommend calling the Indexing API when your livestream begins and ends, and if the structured data changes. <br /> For more information, visit our <a href="https://developers.google.com/search/docs/data-types/livestream">developer documentation</a>. If you have any questions, ask us in the <a href="https://g.co/webmasterhelpforum">Webmaster Help Forum</a>. We look forward to seeing your live videos on Google! <br /> <span class="byline-author">Posted by Danielle Marshak, Product Manager</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> Over the past few years, it's become easier than ever to stream live videos online, from celebrity updates to special events. But it's not always easy for people to determine which videos are live and know when to tune in. <br /> Today, we're introducing new tools to help more people discover your livestreams in Search and Assistant. With livestream structured data and the Indexing API, you can let Google know when your video is live, so it will be eligible to appear with a red "live" badge: <br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhCFUaaFdYa6ChwDLURMG_tEFKiVI_qSSprYnN8CjVYU1BtW9qyXcGQ2CRbVUXCaodhgbQtKcDPAiAAfvVW81bahH8ON5bBhaC9-Og-E1UY1jJUnt4j1eNBzAlTV91enwPKq3ld/s1600/live-search-space.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="609" data-original-width="721" height="337" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhCFUaaFdYa6ChwDLURMG_tEFKiVI_qSSprYnN8CjVYU1BtW9qyXcGQ2CRbVUXCaodhgbQtKcDPAiAAfvVW81bahH8ON5bBhaC9-Og-E1UY1jJUnt4j1eNBzAlTV91enwPKq3ld/s400/live-search-space.png" width="400" /></a></div> <h2> Add livestream structured data to your page</h2> If your website streams live videos, <a href="https://developers.google.com/search/docs/data-types/livestream">use the livestream developer documentation</a> to flag your video as a live broadcast and mark the start and end times. In addition, VideoObject structured data is required to tell Google that there's a video on your page. <br /> <h2> Update Google quickly with the Indexing API</h2> The Indexing API now supports pages with livestream structured data. We encourage you to <a href="https://developers.google.com/search/docs/data-types/livestream#indexing-api">call the Indexing API</a> to request that your site is crawled in time for the livestream. We recommend calling the Indexing API when your livestream begins and ends, and if the structured data changes. <br /> For more information, visit our <a href="https://developers.google.com/search/docs/data-types/livestream">developer documentation</a>. If you have any questions, ask us in the <a href="https://g.co/webmasterhelpforum">Webmaster Help Forum</a>. We look forward to seeing your live videos on Google! <br /> <span class="byline-author">Posted by Danielle Marshak, Product Manager</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Introducing the Indexing API and structured data for livestreams&url=https://webmasters.googleblog.com/2018/12/introducing-indexing-api-and-structured.html?hl=zh_CN&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/12/introducing-indexing-api-and-structured.html?hl=zh_CN'> <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/12/introducing-indexing-api-and-structured.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'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/API?hl=zh_CN' rel='tag'> API </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=zh_CN' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/rich%20results?hl=zh_CN' rel='tag'> rich results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=zh_CN' rel='tag'> structured data </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/video?hl=zh_CN' rel='tag'> video </a> </span> </div> </div> </div> <div class='post' data-id='7409980242580309208' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2018/12/rich-results-expands-for-question.html?hl=zh_CN' itemprop='url' title='Rich Results expands for Question & Answer pages'> Rich Results expands for Question & Answer pages </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> 星期一, 十二月 03, 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"> People come to Google seeking information about all kinds of questions.<br /> Frequently, the information they're looking for is on sites where users ask and answer each other's questions. Popular social news sites, expert forums, and help and support message boards are all examples of this pattern.<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/AVvXsEgC_VGazoyJSQ4OhfbCVp27gYUfsyvd0sqoZKqQmoK4sD-PBw-1PaboG1yWOWmqQujfokH82SXcWDnaZloEMaPBDYOFhhMxVmNBanoh-Pa76gMzCok7Ri0M_SwrY_6sEEI79ZsH/s1600/Screen+Shot+2018-10-23+at+3.31.54+PM.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" data-original-height="694" data-original-width="772" height="572" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgC_VGazoyJSQ4OhfbCVp27gYUfsyvd0sqoZKqQmoK4sD-PBw-1PaboG1yWOWmqQujfokH82SXcWDnaZloEMaPBDYOFhhMxVmNBanoh-Pa76gMzCok7Ri0M_SwrY_6sEEI79ZsH/s640/Screen+Shot+2018-10-23+at+3.31.54+PM.png" width="640" /></a></td></tr> <tr><td class="tr-caption" style="text-align: center;"><span id="docs-internal-guid-a4c057f9-7fff-def7-f41d-b541bb22e438"></span><br /> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span id="docs-internal-guid-2dcc5f42-7fff-d9e0-ef2b-9151c87e6fe4"><span style="background-color: white; color: #333333; font-family: Roboto; font-size: 10pt; font-variant-east-asian: normal; font-variant-numeric: normal; vertical-align: baseline; white-space: pre-wrap;">A screenshot of an example search result for a page titled “How do I remove a cable that is stuck in a USB port” with a list of the top answers from the page.</span></span></div> <span id="docs-internal-guid-a4c057f9-7fff-def7-f41d-b541bb22e438"> </span></td></tr> </tbody></table> In order to help users better identify which search results may give the best information about their question, we have developed a new rich result type for question and answer sites. Search results for eligible Q&A pages display a preview of the top answers. This new presentation helps site owners reach the right users for their content and helps users get the relevant information about their questions faster.<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/AVvXsEjogv6oR00NIhi7YJrjf5OXBjk7TCIS7briYBl-iyZl-rnrayQqiumYaR2hY-BRnpi71yzm-AMUvvMkKKz4Y9TcoN4c1LT7uPG5ojyBlj5ic9TVYfGAkoOcgDIiVp4vkbKAHQd5/s1600/Screen+Shot+2018-11-09+at+11.15.43+AM.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" data-original-height="700" data-original-width="866" height="515" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjogv6oR00NIhi7YJrjf5OXBjk7TCIS7briYBl-iyZl-rnrayQqiumYaR2hY-BRnpi71yzm-AMUvvMkKKz4Y9TcoN4c1LT7uPG5ojyBlj5ic9TVYfGAkoOcgDIiVp4vkbKAHQd5/s640/Screen+Shot+2018-11-09+at+11.15.43+AM.png" width="640" /></a></td></tr> <tr><td class="tr-caption" style="text-align: center;"><span id="docs-internal-guid-ecb3f9d5-7fff-a0b3-c1fa-b64cca5371d1"><span style="background-color: white; color: #333333; font-family: "roboto"; font-size: 10pt; vertical-align: baseline; white-space: pre-wrap;">A screenshot of an example search result for a page titled “Why do touchscreens sometimes register a touch when ...” with a preview of the top answers from the page.</span></span></td></tr> </tbody></table> <br /> To be eligible for this feature, <a href="https://developers.google.com/search/docs/data-types/qapage">add Q&A structured data</a> to your pages with Q&A content. Be sure to use the <a href="https://search.google.com/structured-data/testing-tool/">Structured Data Testing Tool</a> to see if your page is eligible and to preview the appearance in search results. You can also check out Search Console to see <a href="https://support.google.com/webmasters/answer/7552505">aggregate stats and markup error examples</a>. The <a href="https://support.google.com/webmasters/answer/7576553">Performance report</a> also tells you which queries show your Q&A Rich Result in Search results, and how these change over time.<br /> If you have any questions, ask us in the <a href="https://g.co/webmasterhelpforum">Webmaster Help Forum</a> or reach out on <a href="https://twitter.com/googlewmc/">Twitter</a>!<br /> <span class="byline-author">Posted by Kayla Hanson, Software Engineer</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> People come to Google seeking information about all kinds of questions.<br /> Frequently, the information they're looking for is on sites where users ask and answer each other's questions. Popular social news sites, expert forums, and help and support message boards are all examples of this pattern.<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/AVvXsEgC_VGazoyJSQ4OhfbCVp27gYUfsyvd0sqoZKqQmoK4sD-PBw-1PaboG1yWOWmqQujfokH82SXcWDnaZloEMaPBDYOFhhMxVmNBanoh-Pa76gMzCok7Ri0M_SwrY_6sEEI79ZsH/s1600/Screen+Shot+2018-10-23+at+3.31.54+PM.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" data-original-height="694" data-original-width="772" height="572" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgC_VGazoyJSQ4OhfbCVp27gYUfsyvd0sqoZKqQmoK4sD-PBw-1PaboG1yWOWmqQujfokH82SXcWDnaZloEMaPBDYOFhhMxVmNBanoh-Pa76gMzCok7Ri0M_SwrY_6sEEI79ZsH/s640/Screen+Shot+2018-10-23+at+3.31.54+PM.png" width="640" /></a></td></tr> <tr><td class="tr-caption" style="text-align: center;"><span id="docs-internal-guid-a4c057f9-7fff-def7-f41d-b541bb22e438"></span><br /> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span id="docs-internal-guid-2dcc5f42-7fff-d9e0-ef2b-9151c87e6fe4"><span style="background-color: white; color: #333333; font-family: Roboto; font-size: 10pt; font-variant-east-asian: normal; font-variant-numeric: normal; vertical-align: baseline; white-space: pre-wrap;">A screenshot of an example search result for a page titled “How do I remove a cable that is stuck in a USB port” with a list of the top answers from the page.</span></span></div> <span id="docs-internal-guid-a4c057f9-7fff-def7-f41d-b541bb22e438"> </span></td></tr> </tbody></table> In order to help users better identify which search results may give the best information about their question, we have developed a new rich result type for question and answer sites. Search results for eligible Q&A pages display a preview of the top answers. This new presentation helps site owners reach the right users for their content and helps users get the relevant information about their questions faster.<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/AVvXsEjogv6oR00NIhi7YJrjf5OXBjk7TCIS7briYBl-iyZl-rnrayQqiumYaR2hY-BRnpi71yzm-AMUvvMkKKz4Y9TcoN4c1LT7uPG5ojyBlj5ic9TVYfGAkoOcgDIiVp4vkbKAHQd5/s1600/Screen+Shot+2018-11-09+at+11.15.43+AM.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" data-original-height="700" data-original-width="866" height="515" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjogv6oR00NIhi7YJrjf5OXBjk7TCIS7briYBl-iyZl-rnrayQqiumYaR2hY-BRnpi71yzm-AMUvvMkKKz4Y9TcoN4c1LT7uPG5ojyBlj5ic9TVYfGAkoOcgDIiVp4vkbKAHQd5/s640/Screen+Shot+2018-11-09+at+11.15.43+AM.png" width="640" /></a></td></tr> <tr><td class="tr-caption" style="text-align: center;"><span id="docs-internal-guid-ecb3f9d5-7fff-a0b3-c1fa-b64cca5371d1"><span style="background-color: white; color: #333333; font-family: "roboto"; font-size: 10pt; vertical-align: baseline; white-space: pre-wrap;">A screenshot of an example search result for a page titled “Why do touchscreens sometimes register a touch when ...” with a preview of the top answers from the page.</span></span></td></tr> </tbody></table> <br /> To be eligible for this feature, <a href="https://developers.google.com/search/docs/data-types/qapage">add Q&A structured data</a> to your pages with Q&A content. Be sure to use the <a href="https://search.google.com/structured-data/testing-tool/">Structured Data Testing Tool</a> to see if your page is eligible and to preview the appearance in search results. You can also check out Search Console to see <a href="https://support.google.com/webmasters/answer/7552505">aggregate stats and markup error examples</a>. The <a href="https://support.google.com/webmasters/answer/7576553">Performance report</a> also tells you which queries show your Q&A Rich Result in Search results, and how these change over time.<br /> If you have any questions, ask us in the <a href="https://g.co/webmasterhelpforum">Webmaster Help Forum</a> or reach out on <a href="https://twitter.com/googlewmc/">Twitter</a>!<br /> <span class="byline-author">Posted by Kayla Hanson, Software Engineer</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Rich Results expands for Question & Answer pages&url=https://webmasters.googleblog.com/2018/12/rich-results-expands-for-question.html?hl=zh_CN&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/12/rich-results-expands-for-question.html?hl=zh_CN'> <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/12/rich-results-expands-for-question.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'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/rich%20cards?hl=zh_CN' rel='tag'> rich cards </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/rich%20results?hl=zh_CN' rel='tag'> rich results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=zh_CN' rel='tag'> structured data </a> </span> </div> </div> </div> <div class='post' data-id='5683059925024378064' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2018/06/introducing-indexing-api-for-job.html?hl=zh_CN' itemprop='url' title='Introducing the Indexing API for job posting URLs'> Introducing the Indexing API for job posting URLs </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> 星期二, 六月 26, 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> Last June we <a href="https://www.blog.google/products/search/connecting-more-americans-jobs/">launched a job search experience</a> that has since connected tens of millions of job seekers around the world with relevant job opportunities from third party providers across the web. Timely indexing of new job content is critical because many jobs are filled relatively quickly. Removal of expired postings is important because nothing's worse than finding a great job only to discover it's no longer accepting applications. </p> <p> Today we're releasing the <a href="https://developers.google.com/search/apis/indexing-api/">Indexing API</a> to address this problem. This API allows any site owner to directly notify Google when job posting pages are added or removed. This allows Google to schedule job postings for a fresh crawl, which can lead to higher quality user traffic and job applicant satisfaction. Currently, the Indexing API can only be used for job posting pages that include <a href="https://developers.google.com/search/docs/data-types/job-posting">job posting structured data</a>. </p> <p> For websites with many short-lived pages like job postings, the Indexing API keeps job postings fresh in Search results because it allows updates to be pushed individually. This API can be integrated into your job posting flow, allowing high quality job postings to be searchable quickly after publication. In addition, you can check the last time Google received each kind of notification for a given URL. </p> <p> Follow the <a href="https://developers.google.com/search/apis/indexing-api/v3/quickstart">Quickstart</a> guide to see how the Indexing API works. If you have any questions, ask us in the <a href="https://g.co/webmasterhelpforum">Webmaster Help Forum</a>. We look forward to hearing from you! </p> <span class="byline-author">Posted by Zach Clifford, Software Engineer</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <p> Last June we <a href="https://www.blog.google/products/search/connecting-more-americans-jobs/">launched a job search experience</a> that has since connected tens of millions of job seekers around the world with relevant job opportunities from third party providers across the web. Timely indexing of new job content is critical because many jobs are filled relatively quickly. Removal of expired postings is important because nothing's worse than finding a great job only to discover it's no longer accepting applications. </p> <p> Today we're releasing the <a href="https://developers.google.com/search/apis/indexing-api/">Indexing API</a> to address this problem. This API allows any site owner to directly notify Google when job posting pages are added or removed. This allows Google to schedule job postings for a fresh crawl, which can lead to higher quality user traffic and job applicant satisfaction. Currently, the Indexing API can only be used for job posting pages that include <a href="https://developers.google.com/search/docs/data-types/job-posting">job posting structured data</a>. </p> <p> For websites with many short-lived pages like job postings, the Indexing API keeps job postings fresh in Search results because it allows updates to be pushed individually. This API can be integrated into your job posting flow, allowing high quality job postings to be searchable quickly after publication. In addition, you can check the last time Google received each kind of notification for a given URL. </p> <p> Follow the <a href="https://developers.google.com/search/apis/indexing-api/v3/quickstart">Quickstart</a> guide to see how the Indexing API works. If you have any questions, ask us in the <a href="https://g.co/webmasterhelpforum">Webmaster Help Forum</a>. We look forward to hearing from you! </p> <span class="byline-author">Posted by Zach Clifford, Software Engineer</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Introducing the Indexing API for job posting URLs&url=https://webmasters.googleblog.com/2018/06/introducing-indexing-api-for-job.html?hl=zh_CN&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/introducing-indexing-api-for-job.html?hl=zh_CN'> <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/introducing-indexing-api-for-job.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'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/API?hl=zh_CN' rel='tag'> API </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/job%20search?hl=zh_CN' rel='tag'> job search </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=zh_CN' rel='tag'> structured data </a> </span> </div> </div> </div> <div class='post' data-id='3216449440194311736' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2018/04/we-updated-our-job-posting-guidelines.html?hl=zh_CN' itemprop='url' title='We updated our job posting guidelines'> We updated our job posting guidelines </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> 星期五, 四月 27, 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> Last year, we launched <a href="https://jobs.google.com/about/">job search on Google</a> to connect more people with jobs. When you provide <a href="https://developers.google.com/search/docs/data-types/job-posting#JobPosting-definition">Job Posting structured data</a>, it helps drive more relevant traffic to your page by connecting job seekers with your content. To ensure that job seekers are getting the best possible experience, it's important to follow our <a href="https://developers.google.com/search/docs/data-types/job-posting#guidelines">Job Posting guidelines</a>. <p> We've recently made some changes to our <a href="https://developers.google.com/search/docs/data-types/job-posting">Job Posting guidelines</a> to help improve the job seeker experience. </p><ul> <li>Remove expired jobs <li>Place structured data on the job's detail page <li>Make sure all job details are present in the job description</li></ul> <h2>Remove expired jobs</h2> <p> When job seekers put in effort to find a job and apply, it can be very discouraging to discover that the job that they wanted is no longer available. Sometimes, job seekers only discover that the job posting is expired after deciding to apply for the job. Removing expired jobs from your site may drive more traffic because job seekers are more confident when jobs that they visit on your site are still open for application. For more information on how to remove a job posting, see <a href="https://developers.google.com/search/docs/data-types/job-posting#remove-job-postings">Remove a job posting</a>. </p> <p> <br> </p> <h2>Place structured data on the job's detail page </h2> <p> Job seekers find it confusing when they land on a list of jobs instead of the specific job's detail page. To fix this, put structured data on the most detailed leaf page possible. Don't add structured data to pages intended to present a list of jobs (for example, search result pages) and only add it to the most specific page describing a single job with its relevant details. </p> <h2>Make sure all job details are present in the job description</h2> <p> We've also noticed that some sites include information in the <code>JobPosting</code> structured data that is not present anywhere in the job posting. Job seekers are confused when the job details they see in Google Search don't match the job description page. Make sure that the information in the <code>JobPosting</code> structured data always matches what's on the job posting page. Here are some examples: </p><ul> <li>If you add salary information to the structured data, then also add it to the job posting. Both salary figures should match. <li>The location in the structured data should match the location in the job posting. <br> </li></ul> <p> Providing structured data content that is consistent with the content of the job posting pages not only helps job seekers find the exact job that they were looking for, but may also drive more relevant traffic to your job postings and therefore increase the chances of finding the right candidates for your jobs.<br> </p> <p> If your site violates the <a href="https://developers.google.com/search/docs/data-types/job-posting#guidelines">Job Posting guidelines</a> (including the guidelines in this blog post), we may take <a href="https://support.google.com/webmasters/answer/2604824">manual action</a> against your site and it may not be eligible for display in the jobs experience on Google Search. You can submit a <a href="https://support.google.com/webmasters/answer/35843?hl=en">reconsideration request</a> to let us know that you have fixed the problem(s) identified in the manual action notification. If your request is approved, the manual action will be removed from your site or page. </p> <p> For more information, visit our <a href="https://developers.google.com/search/docs/data-types/job-posting">Job Posting developer documentation</a> and our <a href="https://productforums.google.com/forum/#!topic/webmasters/3cgW2pvS93o">JobPosting FAQ</a>. </p> <span class="byline-author">Posted by Anouar Bendahou, Trust & Safety Search 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> Last year, we launched <a href="https://jobs.google.com/about/">job search on Google</a> to connect more people with jobs. When you provide <a href="https://developers.google.com/search/docs/data-types/job-posting#JobPosting-definition">Job Posting structured data</a>, it helps drive more relevant traffic to your page by connecting job seekers with your content. To ensure that job seekers are getting the best possible experience, it's important to follow our <a href="https://developers.google.com/search/docs/data-types/job-posting#guidelines">Job Posting guidelines</a>. <p> We've recently made some changes to our <a href="https://developers.google.com/search/docs/data-types/job-posting">Job Posting guidelines</a> to help improve the job seeker experience. </p><ul> <li>Remove expired jobs <li>Place structured data on the job's detail page <li>Make sure all job details are present in the job description</li></ul> <h2>Remove expired jobs</h2> <p> When job seekers put in effort to find a job and apply, it can be very discouraging to discover that the job that they wanted is no longer available. Sometimes, job seekers only discover that the job posting is expired after deciding to apply for the job. Removing expired jobs from your site may drive more traffic because job seekers are more confident when jobs that they visit on your site are still open for application. For more information on how to remove a job posting, see <a href="https://developers.google.com/search/docs/data-types/job-posting#remove-job-postings">Remove a job posting</a>. </p> <p> <br> </p> <h2>Place structured data on the job's detail page </h2> <p> Job seekers find it confusing when they land on a list of jobs instead of the specific job's detail page. To fix this, put structured data on the most detailed leaf page possible. Don't add structured data to pages intended to present a list of jobs (for example, search result pages) and only add it to the most specific page describing a single job with its relevant details. </p> <h2>Make sure all job details are present in the job description</h2> <p> We've also noticed that some sites include information in the <code>JobPosting</code> structured data that is not present anywhere in the job posting. Job seekers are confused when the job details they see in Google Search don't match the job description page. Make sure that the information in the <code>JobPosting</code> structured data always matches what's on the job posting page. Here are some examples: </p><ul> <li>If you add salary information to the structured data, then also add it to the job posting. Both salary figures should match. <li>The location in the structured data should match the location in the job posting. <br> </li></ul> <p> Providing structured data content that is consistent with the content of the job posting pages not only helps job seekers find the exact job that they were looking for, but may also drive more relevant traffic to your job postings and therefore increase the chances of finding the right candidates for your jobs.<br> </p> <p> If your site violates the <a href="https://developers.google.com/search/docs/data-types/job-posting#guidelines">Job Posting guidelines</a> (including the guidelines in this blog post), we may take <a href="https://support.google.com/webmasters/answer/2604824">manual action</a> against your site and it may not be eligible for display in the jobs experience on Google Search. You can submit a <a href="https://support.google.com/webmasters/answer/35843?hl=en">reconsideration request</a> to let us know that you have fixed the problem(s) identified in the manual action notification. If your request is approved, the manual action will be removed from your site or page. </p> <p> For more information, visit our <a href="https://developers.google.com/search/docs/data-types/job-posting">Job Posting developer documentation</a> and our <a href="https://productforums.google.com/forum/#!topic/webmasters/3cgW2pvS93o">JobPosting FAQ</a>. </p> <span class="byline-author">Posted by Anouar Bendahou, Trust & Safety Search 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:We updated our job posting guidelines&url=https://webmasters.googleblog.com/2018/04/we-updated-our-job-posting-guidelines.html?hl=zh_CN&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/04/we-updated-our-job-posting-guidelines.html?hl=zh_CN'> <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/04/we-updated-our-job-posting-guidelines.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'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/job%20search?hl=zh_CN' rel='tag'> job search </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/rich%20cards?hl=zh_CN' rel='tag'> rich cards </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/rich%20results?hl=zh_CN' rel='tag'> rich results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/sitemaps?hl=zh_CN' rel='tag'> sitemaps </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=zh_CN' rel='tag'> structured data </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines?hl=zh_CN' rel='tag'> webmaster guidelines </a> </span> </div> </div> </div> <div class='post' data-id='1797041529782499189' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2018/01/using-page-speed-in-mobile-search.html?hl=zh_CN' itemprop='url' title='Using page speed in mobile search ranking'> Using page speed in mobile search ranking </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> 星期三, 一月 17, 2018 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p><i>Update July 9, 2018: The Speed Update is now rolling out for all users.</i></p> <p>People want to be able to find answers to their questions as fast as possible — <a href="https://www.thinkwithgoogle.com/marketing-resources/data-measurement/mobile-page-speed-industry-benchmarks/">studies</a> show that people really care about the speed of a page. Although speed has been used in ranking for some time, that <a href="https://webmasters.googleblog.com/2010/04/using-site-speed-in-web-search-ranking.html">signal</a> was focused on desktop searches. Today we’re announcing that starting in July 2018, page speed will be a ranking factor for mobile searches.</p> <p>The “Speed Update,” as we’re calling it, will only affect pages that deliver the slowest experience to users and will only affect a small percentage of queries. It applies the same standard to all pages, regardless of the technology used to build the page. The intent of the search query is still a very strong signal, so a slow page may still rank highly if it has great, relevant content.</p> <p>We encourage developers to think broadly about how <a href="https://developers.google.com/web/fundamentals/performance/rail">performance</a> affects a user’s experience of their page and to consider a variety of <a href="https://developers.google.com/web/updates/2017/06/user-centric-performance-metrics">user experience metrics</a>. Although there is no tool that directly indicates whether a page is affected by this new ranking factor, here are some resources that can be used to evaluate a page’s performance. </p> <ul><li><a href="https://developers.google.com/web/tools/chrome-user-experience-report/">Chrome User Experience Report</a>, a public dataset of key user experience metrics for popular destinations on the web, as experienced by Chrome users under real-world conditions</li> <li><a href="https://developers.google.com/web/tools/lighthouse/">Lighthouse</a>, an automated tool and a part of Chrome Developer Tools for auditing the quality (performance, accessibility, and more) of web pages</li> <li><a href="https://developers.google.com/speed/pagespeed/insights/">PageSpeed Insights</a>, a tool that indicates how well a page performs on the Chrome UX Report and suggests performance optimizations</li></ul> <p>As always, if you have any questions or feedback, please visit our <a href="https://productforums.google.com/forum/#!forum/webmasters">webmaster forums</a>. </p> <span class="byline-author">Posted by Zhiheng Wang and Doantam Phan</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p><i>Update July 9, 2018: The Speed Update is now rolling out for all users.</i></p> <p>People want to be able to find answers to their questions as fast as possible — <a href="https://www.thinkwithgoogle.com/marketing-resources/data-measurement/mobile-page-speed-industry-benchmarks/">studies</a> show that people really care about the speed of a page. Although speed has been used in ranking for some time, that <a href="https://webmasters.googleblog.com/2010/04/using-site-speed-in-web-search-ranking.html">signal</a> was focused on desktop searches. Today we’re announcing that starting in July 2018, page speed will be a ranking factor for mobile searches.</p> <p>The “Speed Update,” as we’re calling it, will only affect pages that deliver the slowest experience to users and will only affect a small percentage of queries. It applies the same standard to all pages, regardless of the technology used to build the page. The intent of the search query is still a very strong signal, so a slow page may still rank highly if it has great, relevant content.</p> <p>We encourage developers to think broadly about how <a href="https://developers.google.com/web/fundamentals/performance/rail">performance</a> affects a user’s experience of their page and to consider a variety of <a href="https://developers.google.com/web/updates/2017/06/user-centric-performance-metrics">user experience metrics</a>. Although there is no tool that directly indicates whether a page is affected by this new ranking factor, here are some resources that can be used to evaluate a page’s performance. </p> <ul><li><a href="https://developers.google.com/web/tools/chrome-user-experience-report/">Chrome User Experience Report</a>, a public dataset of key user experience metrics for popular destinations on the web, as experienced by Chrome users under real-world conditions</li> <li><a href="https://developers.google.com/web/tools/lighthouse/">Lighthouse</a>, an automated tool and a part of Chrome Developer Tools for auditing the quality (performance, accessibility, and more) of web pages</li> <li><a href="https://developers.google.com/speed/pagespeed/insights/">PageSpeed Insights</a>, a tool that indicates how well a page performs on the Chrome UX Report and suggests performance optimizations</li></ul> <p>As always, if you have any questions or feedback, please visit our <a href="https://productforums.google.com/forum/#!forum/webmasters">webmaster forums</a>. </p> <span class="byline-author">Posted by Zhiheng Wang and Doantam Phan</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Using page speed in mobile search ranking&url=https://webmasters.googleblog.com/2018/01/using-page-speed-in-mobile-search.html?hl=zh_CN&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/using-page-speed-in-mobile-search.html?hl=zh_CN'> <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/using-page-speed-in-mobile-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'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/mobile?hl=zh_CN' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/performance?hl=zh_CN' rel='tag'> performance </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/speed?hl=zh_CN' rel='tag'> speed </a> </span> </div> </div> </div> <div class='post' data-id='2770587079739738421' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/12/rendering-ajax-crawling-pages.html?hl=zh_CN' itemprop='url' title='Rendering AJAX-crawling pages'> Rendering AJAX-crawling pages </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> 星期一, 十二月 04, 2017 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>The <a href="https://web.archive.org/web/20151201031357/https://developers.google.com/webmasters/ajax-crawling/docs/learn-more">AJAX crawling scheme</a> was introduced as a way of making JavaScript-based webpages accessible to Googlebot, and we've previously announced our <a href="https://webmasters.googleblog.com/2015/10/deprecating-our-ajax-crawling-scheme.html">plans to turn it down</a>. Over time, Google engineers have significantly improved rendering of JavaScript for Googlebot. Given these advances, in the second quarter of 2018, we'll be switching to rendering these pages on Google's side, rather than on requiring that sites do this themselves. In short, we'll no longer be using the AJAX crawling scheme.</p> <p>As a reminder, the AJAX crawling scheme accepts pages with either a "#!" in the URL or a "<a href="https://web.archive.org/web/20151101113107/https://developers.google.com/webmasters/ajax-crawling/docs/getting-started#3-handle-pages-without-hash-fragments">fragment meta tag</a>" on them, and then crawls them with an "?_escaped_fragment_=" in the URL. That escaped version needs to be a fully-rendered and/or equivalent version of the page, created by the website itself. </p> <p>With this change, Googlebot will render the #! URL directly, making it unnecessary for the website owner to provide a rendered version of the page. We'll continue to support these URLs in our search results.</p> <p>We expect that most AJAX-crawling websites won't see significant changes with this update. Webmasters can double-check their pages as detailed below, and we'll be sending notifications to any sites with potential issues. </p> <p>If your site is currently using either #! URLs or the fragment meta tag, we recommend:</p> <ul><li>Verify ownership of the website in <a href="https://www.google.com/webmasters/tools/home">Google Search Console</a> to gain access to the tools there, and to allow Google to notify you of any issues that might be found.</li> <li>Test with Search Console's <a href="https://support.google.com/webmasters/answer/6066468">Fetch & Render</a>. Compare the results of the #! URL and the escaped URL to see any differences. Do this for any significantly different part of the website. Check our <a href="https://developers.google.com/search/docs/guides/rendering">developer documentation</a> for more information on supported APIs, and see our <a href="https://developers.google.com/search/docs/guides/debug-rendering">debugging guide</a> when needed.</li> <li>Use Chrome's <a href="https://developers.google.com/web/tools/chrome-devtools/inspect-styles/">Inspect Element</a> to confirm that links use <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a">"a" HTML elements</a> and include a <a href="https://support.google.com/webmasters/answer/96569">rel=nofollow</a> where appropriate (for example, in user-generated content)</li> <li>Use Chrome's <a href="https://developers.google.com/web/tools/chrome-devtools/inspect-styles/">Inspect Element</a> to check the <a href="https://support.google.com/webmasters/answer/35624">page's title and description meta tag</a>, any robots meta tag, and other meta data. Also check that any <a href="https://developers.google.com/search/docs/guides/intro-structured-data">structured data</a> is available on the rendered page. </li> <li>Content in Flash, Silverlight, or other plugin-based technologies needs to be converted to either JavaScript or "normal" HTML, if their content should be indexed in search. </li></ul> <p>We hope that this change makes it a bit easier for your website, and reduces the need to render pages on your end. Should you have any questions or comments, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">webmaster help forums</a>, or to join our <a href="https://groups.google.com/forum/#!forum/js-sites-wg">JavaScript sites working group</a>. </p> <br> <span class="byline-author">Posted by <a href="https://plus.google.com/+johnmueller?rel=john">John Mueller</a>, 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>The <a href="https://web.archive.org/web/20151201031357/https://developers.google.com/webmasters/ajax-crawling/docs/learn-more">AJAX crawling scheme</a> was introduced as a way of making JavaScript-based webpages accessible to Googlebot, and we've previously announced our <a href="https://webmasters.googleblog.com/2015/10/deprecating-our-ajax-crawling-scheme.html">plans to turn it down</a>. Over time, Google engineers have significantly improved rendering of JavaScript for Googlebot. Given these advances, in the second quarter of 2018, we'll be switching to rendering these pages on Google's side, rather than on requiring that sites do this themselves. In short, we'll no longer be using the AJAX crawling scheme.</p> <p>As a reminder, the AJAX crawling scheme accepts pages with either a "#!" in the URL or a "<a href="https://web.archive.org/web/20151101113107/https://developers.google.com/webmasters/ajax-crawling/docs/getting-started#3-handle-pages-without-hash-fragments">fragment meta tag</a>" on them, and then crawls them with an "?_escaped_fragment_=" in the URL. That escaped version needs to be a fully-rendered and/or equivalent version of the page, created by the website itself. </p> <p>With this change, Googlebot will render the #! URL directly, making it unnecessary for the website owner to provide a rendered version of the page. We'll continue to support these URLs in our search results.</p> <p>We expect that most AJAX-crawling websites won't see significant changes with this update. Webmasters can double-check their pages as detailed below, and we'll be sending notifications to any sites with potential issues. </p> <p>If your site is currently using either #! URLs or the fragment meta tag, we recommend:</p> <ul><li>Verify ownership of the website in <a href="https://www.google.com/webmasters/tools/home">Google Search Console</a> to gain access to the tools there, and to allow Google to notify you of any issues that might be found.</li> <li>Test with Search Console's <a href="https://support.google.com/webmasters/answer/6066468">Fetch & Render</a>. Compare the results of the #! URL and the escaped URL to see any differences. Do this for any significantly different part of the website. Check our <a href="https://developers.google.com/search/docs/guides/rendering">developer documentation</a> for more information on supported APIs, and see our <a href="https://developers.google.com/search/docs/guides/debug-rendering">debugging guide</a> when needed.</li> <li>Use Chrome's <a href="https://developers.google.com/web/tools/chrome-devtools/inspect-styles/">Inspect Element</a> to confirm that links use <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a">"a" HTML elements</a> and include a <a href="https://support.google.com/webmasters/answer/96569">rel=nofollow</a> where appropriate (for example, in user-generated content)</li> <li>Use Chrome's <a href="https://developers.google.com/web/tools/chrome-devtools/inspect-styles/">Inspect Element</a> to check the <a href="https://support.google.com/webmasters/answer/35624">page's title and description meta tag</a>, any robots meta tag, and other meta data. Also check that any <a href="https://developers.google.com/search/docs/guides/intro-structured-data">structured data</a> is available on the rendered page. </li> <li>Content in Flash, Silverlight, or other plugin-based technologies needs to be converted to either JavaScript or "normal" HTML, if their content should be indexed in search. </li></ul> <p>We hope that this change makes it a bit easier for your website, and reduces the need to render pages on your end. Should you have any questions or comments, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">webmaster help forums</a>, or to join our <a href="https://groups.google.com/forum/#!forum/js-sites-wg">JavaScript sites working group</a>. </p> <br> <span class="byline-author">Posted by <a href="https://plus.google.com/+johnmueller?rel=john">John Mueller</a>, 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:Rendering AJAX-crawling pages&url=https://webmasters.googleblog.com/2017/12/rendering-ajax-crawling-pages.html?hl=zh_CN&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/12/rendering-ajax-crawling-pages.html?hl=zh_CN'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/12/rendering-ajax-crawling-pages.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=zh_CN' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/rendering?hl=zh_CN' rel='tag'> rendering </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> </span> </div> </div> </div> <div class='post' data-id='6564854437761627791' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/11/a-reminder-about-event-markup.html?hl=zh_CN' itemprop='url' title='A reminder about “event” markup'> A reminder about “event” markup </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> 星期一, 十一月 27, 2017 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>Lately we’ve been receiving feedback from users seeing non-events like coupons or vouchers showing up in search results where “events” snippets appear. This is really confusing for users and also against our guidelines, where we have added <a href="https://developers.google.com/search/docs/data-types/events">additional clarification</a>.</p> <p>So, what’s the problem?</p> <p>We’ve seen a number of  publishers in the coupons/vouchers space use the “event” markup to describe their offers. And as much as using a discount voucher can be a very special thing, that doesn’t make coupons or vouchers events or “saleEvents”. Using <a href="https://developers.google.com/search/docs/data-types/events">Event markup</a> to describe something that is not an event creates a bad user experience, by triggering a rich result for something that will happen at a particular time, despite no actual event being present.</p> <p>Here are some examples to illustrate the issue:</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjbNCdLMI5pUkShA-dyx50jtJ8aMcA63_7oeTTdD8MXiu8H77Pv1_saGCpYxHc3vzOp9li_sXUdGbyYFMrs7dL9bACUWXtm_oCCD0gvJSLQ4_xjoYLVCNh36RYbi2kCpLFCy-_J/s1600/nope-nope-nope.png" imageanchor="1" ><img border="0" data-original-height="107" data-original-width="623" height="69" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjbNCdLMI5pUkShA-dyx50jtJ8aMcA63_7oeTTdD8MXiu8H77Pv1_saGCpYxHc3vzOp9li_sXUdGbyYFMrs7dL9bACUWXtm_oCCD0gvJSLQ4_xjoYLVCNh36RYbi2kCpLFCy-_J/s400/nope-nope-nope.png" width="400" /></a> </p> <p>Since this creates a misleading user experience, we may take manual action on such cases. In case your website is affected by such a manual action, you will find a notification in your Search Console account. If a manual action is taken, it can result in structured data markup for the whole site not being used for search results.  </p> <p>While we’re specifically highlighting coupons and vouchers in this blogpost, this applies to all other non-event items being annotated with “event” markup as well -- or, really, for applying a type of markup to something other than the type of thing it is meant to describe.</p> <p>For more information, please visit our <a href="https://developers.google.com/search/docs/data-types/events">developer documentation</a> or stop by our <a href="https://support.google.com/webmasters/go/community">Webmaster Forum</a> in case you have additional questions!</p> <br> <span class="byline-author">Posted by Sven Naumann, Trust & Safety Search 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>Lately we’ve been receiving feedback from users seeing non-events like coupons or vouchers showing up in search results where “events” snippets appear. This is really confusing for users and also against our guidelines, where we have added <a href="https://developers.google.com/search/docs/data-types/events">additional clarification</a>.</p> <p>So, what’s the problem?</p> <p>We’ve seen a number of  publishers in the coupons/vouchers space use the “event” markup to describe their offers. And as much as using a discount voucher can be a very special thing, that doesn’t make coupons or vouchers events or “saleEvents”. Using <a href="https://developers.google.com/search/docs/data-types/events">Event markup</a> to describe something that is not an event creates a bad user experience, by triggering a rich result for something that will happen at a particular time, despite no actual event being present.</p> <p>Here are some examples to illustrate the issue:</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjbNCdLMI5pUkShA-dyx50jtJ8aMcA63_7oeTTdD8MXiu8H77Pv1_saGCpYxHc3vzOp9li_sXUdGbyYFMrs7dL9bACUWXtm_oCCD0gvJSLQ4_xjoYLVCNh36RYbi2kCpLFCy-_J/s1600/nope-nope-nope.png" imageanchor="1" ><img border="0" data-original-height="107" data-original-width="623" height="69" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjbNCdLMI5pUkShA-dyx50jtJ8aMcA63_7oeTTdD8MXiu8H77Pv1_saGCpYxHc3vzOp9li_sXUdGbyYFMrs7dL9bACUWXtm_oCCD0gvJSLQ4_xjoYLVCNh36RYbi2kCpLFCy-_J/s400/nope-nope-nope.png" width="400" /></a> </p> <p>Since this creates a misleading user experience, we may take manual action on such cases. In case your website is affected by such a manual action, you will find a notification in your Search Console account. If a manual action is taken, it can result in structured data markup for the whole site not being used for search results.  </p> <p>While we’re specifically highlighting coupons and vouchers in this blogpost, this applies to all other non-event items being annotated with “event” markup as well -- or, really, for applying a type of markup to something other than the type of thing it is meant to describe.</p> <p>For more information, please visit our <a href="https://developers.google.com/search/docs/data-types/events">developer documentation</a> or stop by our <a href="https://support.google.com/webmasters/go/community">Webmaster Forum</a> in case you have additional questions!</p> <br> <span class="byline-author">Posted by Sven Naumann, Trust & Safety Search 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:A reminder about “event” markup&url=https://webmasters.googleblog.com/2017/11/a-reminder-about-event-markup.html?hl=zh_CN&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/11/a-reminder-about-event-markup.html?hl=zh_CN'> <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/11/a-reminder-about-event-markup.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'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/rich%20cards?hl=zh_CN' rel='tag'> rich cards </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/rich%20results?hl=zh_CN' rel='tag'> rich results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=zh_CN' rel='tag'> structured data </a> </span> </div> </div> </div> <div class='post' data-id='6013420081723539335' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/11/engaging-users-through-high-quality-amp.html?hl=zh_CN' itemprop='url' title='Engaging users through high quality AMP pages'> Engaging users through high quality AMP pages </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> 星期四, 十一月 16, 2017 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p>To improve our users' experience with AMP results, we are making changes to how we enforce our policy on content parity with AMP. Starting Feb 1, 2018, the policy requires that the AMP page content be comparable to the (original) canonical page content. AMP is not a ranking signal and there is no change in terms of the ranking policy with respect to AMP.</p> <p>The open source accelerated mobile pages project (AMP) <a href="https://googleblog.blogspot.com/2015/10/introducing-accelerated-mobile-pages.html">launched in 2015</a> and has seen tremendous growth with over <a href="https://www.ampproject.org/latest/blog/amp-two-years-of-user-first-webpages/">25M domains</a> having implemented the AMP format. This rapid progress comes with a sense of responsibility of ensuring that our users continue to have a great content consumption experience that ultimately leads to more engagement with publisher content.</p> <p>In some cases, webmasters publish two versions of their content: a canonical page that is not based on AMP and an AMP page. In the ideal scenario, both these pages have equivalent content leading the user to get the same content but with a faster and smoother experience via AMP.  However, in some cases the content on the AMP page does not match the content on its original (canonical) page.</p> <p>In a small number of cases, AMP pages are used as teaser pages which create a particularly bad user experience since they only contain minimal content. In these instances, users have to click twice to get to the real content. Below is an example of how this may look like: a brief text of the main article and then asking the user to click to visit another page to complete reading the article.</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjUBDI2Pdnt09VOcXjpGRHZarvbdEJuRaWSe1OJXeyTNQmbtPrvML0TGnl0nUczDianxeMOVB4Wa_32ouhE6BgMFuPWfH72hHqjk7uJFfAgPWhyphenhyphenpLyaJJKhcOVhQWajNXSxODnt/s1600/amp01.png" imageanchor="1" ><img border="0" data-original-height="1016" data-original-width="735" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjUBDI2Pdnt09VOcXjpGRHZarvbdEJuRaWSe1OJXeyTNQmbtPrvML0TGnl0nUczDianxeMOVB4Wa_32ouhE6BgMFuPWfH72hHqjk7uJFfAgPWhyphenhyphenpLyaJJKhcOVhQWajNXSxODnt/s400/amp01.png" width="289" /></a> </p> <p>AMP was introduced to dramatically improve the performance of the web and deliver a fast, consistent content consumption experience. In keeping with this goal, we'll be enforcing <a href="https://support.google.com/webmasters/answer/6340290">the requirement</a> of close parity between AMP and canonical page, for pages that wish to be shown in Google Search as AMPs.</p> <p>Where we find that an AMP page doesn't contain the same critical content as its non-AMP equivalent, we will direct our users to the non-AMP page. This does not affect Search ranking. However, these pages will not be considered for Search features that require AMP, such as the Top Stories carousel with AMP. Additionally, we will notify the webmaster via <a href="https://www.google.com/webmasters/tools/">Search console</a> as a manual action message and give the publisher the opportunity to fix the issue before its AMP page can be served again. The <a href="https://www.ampproject.org/">AMP open source website</a> has several helpful guides to help produce fast, beautiful and high-performing AMP pages.</p> <p>We hope this change encourages webmasters to maintain content parity between the canonical and AMP equivalent. This will lead to better experience on your site and ultimately happier users.</p> <br> <span class="byline-author">Posted by Ashish Mehta, 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>To improve our users' experience with AMP results, we are making changes to how we enforce our policy on content parity with AMP. Starting Feb 1, 2018, the policy requires that the AMP page content be comparable to the (original) canonical page content. AMP is not a ranking signal and there is no change in terms of the ranking policy with respect to AMP.</p> <p>The open source accelerated mobile pages project (AMP) <a href="https://googleblog.blogspot.com/2015/10/introducing-accelerated-mobile-pages.html">launched in 2015</a> and has seen tremendous growth with over <a href="https://www.ampproject.org/latest/blog/amp-two-years-of-user-first-webpages/">25M domains</a> having implemented the AMP format. This rapid progress comes with a sense of responsibility of ensuring that our users continue to have a great content consumption experience that ultimately leads to more engagement with publisher content.</p> <p>In some cases, webmasters publish two versions of their content: a canonical page that is not based on AMP and an AMP page. In the ideal scenario, both these pages have equivalent content leading the user to get the same content but with a faster and smoother experience via AMP.  However, in some cases the content on the AMP page does not match the content on its original (canonical) page.</p> <p>In a small number of cases, AMP pages are used as teaser pages which create a particularly bad user experience since they only contain minimal content. In these instances, users have to click twice to get to the real content. Below is an example of how this may look like: a brief text of the main article and then asking the user to click to visit another page to complete reading the article.</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjUBDI2Pdnt09VOcXjpGRHZarvbdEJuRaWSe1OJXeyTNQmbtPrvML0TGnl0nUczDianxeMOVB4Wa_32ouhE6BgMFuPWfH72hHqjk7uJFfAgPWhyphenhyphenpLyaJJKhcOVhQWajNXSxODnt/s1600/amp01.png" imageanchor="1" ><img border="0" data-original-height="1016" data-original-width="735" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjUBDI2Pdnt09VOcXjpGRHZarvbdEJuRaWSe1OJXeyTNQmbtPrvML0TGnl0nUczDianxeMOVB4Wa_32ouhE6BgMFuPWfH72hHqjk7uJFfAgPWhyphenhyphenpLyaJJKhcOVhQWajNXSxODnt/s400/amp01.png" width="289" /></a> </p> <p>AMP was introduced to dramatically improve the performance of the web and deliver a fast, consistent content consumption experience. In keeping with this goal, we'll be enforcing <a href="https://support.google.com/webmasters/answer/6340290">the requirement</a> of close parity between AMP and canonical page, for pages that wish to be shown in Google Search as AMPs.</p> <p>Where we find that an AMP page doesn't contain the same critical content as its non-AMP equivalent, we will direct our users to the non-AMP page. This does not affect Search ranking. However, these pages will not be considered for Search features that require AMP, such as the Top Stories carousel with AMP. Additionally, we will notify the webmaster via <a href="https://www.google.com/webmasters/tools/">Search console</a> as a manual action message and give the publisher the opportunity to fix the issue before its AMP page can be served again. The <a href="https://www.ampproject.org/">AMP open source website</a> has several helpful guides to help produce fast, beautiful and high-performing AMP pages.</p> <p>We hope this change encourages webmasters to maintain content parity between the canonical and AMP equivalent. This will lead to better experience on your site and ultimately happier users.</p> <br> <span class="byline-author">Posted by Ashish Mehta, 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:Engaging users through high quality AMP pages&url=https://webmasters.googleblog.com/2017/11/engaging-users-through-high-quality-amp.html?hl=zh_CN&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/11/engaging-users-through-high-quality-amp.html?hl=zh_CN'> <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/11/engaging-users-through-high-quality-amp.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/AMP?hl=zh_CN' rel='tag'> AMP </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/general%20tips?hl=zh_CN' rel='tag'> general tips </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> </span> </div> </div> </div> <div class='post' data-id='27077260461562735' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/11/make-your-sites-complete-jobs.html?hl=zh_CN' itemprop='url' title='Make your site's complete jobs information accessible to job seekers'> Make your site's complete jobs information accessible to job seekers </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> 星期三, 十一月 15, 2017 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>In June, we <a href="https://www.blog.google/products/search/connecting-more-americans-jobs/">announced a new experience</a> that put the convenience of Search into the hands of job seekers. Today, we are taking the next step in improving the job search experience on Google by adding a feature that shows estimated salary information from the web alongside job postings, as well as adding new UI features for users.</p> <p>Salary information has been one of the most requested additions from job seekers. This helps people evaluate whether a job is a good fit, and is an opportunity for sites with estimated salary information to:</p> <ul><li><b>Increase brand awareness</b>: Estimated salary information shows a representative logo from the estimated salary provider. </li></ul> <ul><li><b>Get more referral traffic</b>: Users can click through directly to salary estimate pages when salary information surfaces in job search results.</li></ul> <p>If your site provides salary estimates, you can take advantage of these changes in the following ways:</p> <p><b>Specify actual salary information</b></p> <p>Actual salary refers to the base salary information that is provided by the employer. If your site publishes job listings, you can add <a href="https://developers.google.com/search/docs/data-types/job-postings">JobPosting structured data</a> and populate the baseSalary property to be eligible for inclusion in job search results.</p> <p>This salary information will be made available in both the list and the detail views.</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjMcLRNAWJWsWEkYM8vu4Eqvr82icujR1Yeq6jgNJcYGFDtBsPlLY4tF6_jWRSRGMErB3Y7j_FGWLvIZk34XJxq7FmzcuuamucHND5d8sGW_cZTe6gL7DBAvKW2QRgbql5ELaSY/s1600/img01.png" imageanchor="1" ><img border="0" data-original-height="1451" data-original-width="1600" height="363" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjMcLRNAWJWsWEkYM8vu4Eqvr82icujR1Yeq6jgNJcYGFDtBsPlLY4tF6_jWRSRGMErB3Y7j_FGWLvIZk34XJxq7FmzcuuamucHND5d8sGW_cZTe6gL7DBAvKW2QRgbql5ELaSY/s400/img01.png" width="400" /></a> </p> <p><b>Provide estimated salary information</b></p> <p>In cases where employers don’t provide actual salary, job seekers may see estimated salaries sourced from multiple partners for the same or similar occupation. If your site provides salary estimate information, you can add <a href="https://developers.google.com/search/docs/data-types/occupation">Occupation structured data</a> to be eligible for inclusion in job search results.  </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgPmWsluacpRDyftrvETJrl2HhbaTSuQBf1IKHXGlT2PmiW2npeLK1vUbeBaW1IoMA1hAESW3Zbos2K3c6XpIUmD_LRiM1RZuKg7T5IsesF45lEdUHb7HhozY6eZrZ5FG9gMQOB/s1600/img02.png" imageanchor="1" ><img border="0" data-original-height="1600" data-original-width="912" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgPmWsluacpRDyftrvETJrl2HhbaTSuQBf1IKHXGlT2PmiW2npeLK1vUbeBaW1IoMA1hAESW3Zbos2K3c6XpIUmD_LRiM1RZuKg7T5IsesF45lEdUHb7HhozY6eZrZ5FG9gMQOB/s400/img02.png" width="228" /></a> </p> <p><b>Include exact location information</b></p> <p>We've heard from users that having accurate, street-level location information helps them to focus on opportunities that work best for them. Sites that publish job listings can do this can do this by using the jobLocation property in <a href="https://developers.google.com/search/docs/data-types/job-postings#JobPosting-definition">JobPosting structured data</a>.</p> <p><b>Validate your structured data</b></p> <p>To double-check the structured data on your pages, we'll be updating the <a href="https://search.google.com/structured-data/testing-tool">Structured Data Testing Tool</a> and the <a href="https://support.google.com/webmasters/answer/6381755">Search Console reports</a> in the near future. In the meantime, you can <a href="https://support.google.com/webmasters/answer/7042828">monitor the performance of your job postings in Search Analytics</a>. Stay tuned! </p> <p>Since launching this summer, we’ve seen over 60% growth in number of companies with jobs showing on Google and connected tens of millions of people to new job opportunities. We are excited to help users find jobs with salaries that meet their needs, and to route them to your site for more information. We invite sites that provide salary estimates to mark up their salary pages using the <a href="https://developers.google.com/search/docs/data-types/occupation">Occupation structured data</a>. Should you have any questions regarding the use of structured data on your site, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">webmaster help forums</a>.</p> <br> <span class="byline-author">Posted by Nick Zakrasek, Product Manager</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>In June, we <a href="https://www.blog.google/products/search/connecting-more-americans-jobs/">announced a new experience</a> that put the convenience of Search into the hands of job seekers. Today, we are taking the next step in improving the job search experience on Google by adding a feature that shows estimated salary information from the web alongside job postings, as well as adding new UI features for users.</p> <p>Salary information has been one of the most requested additions from job seekers. This helps people evaluate whether a job is a good fit, and is an opportunity for sites with estimated salary information to:</p> <ul><li><b>Increase brand awareness</b>: Estimated salary information shows a representative logo from the estimated salary provider. </li></ul> <ul><li><b>Get more referral traffic</b>: Users can click through directly to salary estimate pages when salary information surfaces in job search results.</li></ul> <p>If your site provides salary estimates, you can take advantage of these changes in the following ways:</p> <p><b>Specify actual salary information</b></p> <p>Actual salary refers to the base salary information that is provided by the employer. If your site publishes job listings, you can add <a href="https://developers.google.com/search/docs/data-types/job-postings">JobPosting structured data</a> and populate the baseSalary property to be eligible for inclusion in job search results.</p> <p>This salary information will be made available in both the list and the detail views.</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjMcLRNAWJWsWEkYM8vu4Eqvr82icujR1Yeq6jgNJcYGFDtBsPlLY4tF6_jWRSRGMErB3Y7j_FGWLvIZk34XJxq7FmzcuuamucHND5d8sGW_cZTe6gL7DBAvKW2QRgbql5ELaSY/s1600/img01.png" imageanchor="1" ><img border="0" data-original-height="1451" data-original-width="1600" height="363" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjMcLRNAWJWsWEkYM8vu4Eqvr82icujR1Yeq6jgNJcYGFDtBsPlLY4tF6_jWRSRGMErB3Y7j_FGWLvIZk34XJxq7FmzcuuamucHND5d8sGW_cZTe6gL7DBAvKW2QRgbql5ELaSY/s400/img01.png" width="400" /></a> </p> <p><b>Provide estimated salary information</b></p> <p>In cases where employers don’t provide actual salary, job seekers may see estimated salaries sourced from multiple partners for the same or similar occupation. If your site provides salary estimate information, you can add <a href="https://developers.google.com/search/docs/data-types/occupation">Occupation structured data</a> to be eligible for inclusion in job search results.  </p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgPmWsluacpRDyftrvETJrl2HhbaTSuQBf1IKHXGlT2PmiW2npeLK1vUbeBaW1IoMA1hAESW3Zbos2K3c6XpIUmD_LRiM1RZuKg7T5IsesF45lEdUHb7HhozY6eZrZ5FG9gMQOB/s1600/img02.png" imageanchor="1" ><img border="0" data-original-height="1600" data-original-width="912" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgPmWsluacpRDyftrvETJrl2HhbaTSuQBf1IKHXGlT2PmiW2npeLK1vUbeBaW1IoMA1hAESW3Zbos2K3c6XpIUmD_LRiM1RZuKg7T5IsesF45lEdUHb7HhozY6eZrZ5FG9gMQOB/s400/img02.png" width="228" /></a> </p> <p><b>Include exact location information</b></p> <p>We've heard from users that having accurate, street-level location information helps them to focus on opportunities that work best for them. Sites that publish job listings can do this can do this by using the jobLocation property in <a href="https://developers.google.com/search/docs/data-types/job-postings#JobPosting-definition">JobPosting structured data</a>.</p> <p><b>Validate your structured data</b></p> <p>To double-check the structured data on your pages, we'll be updating the <a href="https://search.google.com/structured-data/testing-tool">Structured Data Testing Tool</a> and the <a href="https://support.google.com/webmasters/answer/6381755">Search Console reports</a> in the near future. In the meantime, you can <a href="https://support.google.com/webmasters/answer/7042828">monitor the performance of your job postings in Search Analytics</a>. Stay tuned! </p> <p>Since launching this summer, we’ve seen over 60% growth in number of companies with jobs showing on Google and connected tens of millions of people to new job opportunities. We are excited to help users find jobs with salaries that meet their needs, and to route them to your site for more information. We invite sites that provide salary estimates to mark up their salary pages using the <a href="https://developers.google.com/search/docs/data-types/occupation">Occupation structured data</a>. Should you have any questions regarding the use of structured data on your site, feel free to drop by our <a href="https://support.google.com/webmasters/go/community">webmaster help forums</a>.</p> <br> <span class="byline-author">Posted by Nick Zakrasek, Product Manager</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Make your site's complete jobs information accessible to job seekers&url=https://webmasters.googleblog.com/2017/11/make-your-sites-complete-jobs.html?hl=zh_CN&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/11/make-your-sites-complete-jobs.html?hl=zh_CN'> <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/11/make-your-sites-complete-jobs.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'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/products%20and%20services?hl=zh_CN' rel='tag'> products and services </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=zh_CN' rel='tag'> structured data </a> </span> </div> </div> </div> <div class='post' data-id='6164746050338448159' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/10/enabling-more-high-quality-content.html?hl=zh_CN' itemprop='url' title='Enabling more high quality content for users'> Enabling more high quality content for users </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> 星期日, 十月 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"> <p>In Google’s <a href="https://www.google.com/search/howsearchworks/mission/">mission</a> to organize the world's information, we want to guide Google users to the highest quality content, the principle exemplified in our <a href="http://static.googleusercontent.com/media/www.google.com/en//insidesearch/howsearchworks/assets/searchqualityevaluatorguidelines.pdf">quality rater guidelines</a>. Professional publishers provide the lion’s share of quality content that benefits users and we want to encourage their success.</p> <p>The ecosystem is sustained via two main sources of revenue: ads and subscriptions, with the latter requiring a delicate balance to be effective in Search. Typically subscription content is hidden behind paywalls, so that users who don’t have a subscription don’t have access. Our evaluations have shown that users who are not familiar with the high quality content behind a paywall often turn to other sites offering free content. It is difficult to justify a subscription if one doesn't already know how valuable the content is, and in fact, our experiments have shown that a portion of users shy away from subscription sites. Therefore, it is essential that sites provide some amount of free sampling of their content so that users can learn how valuable their content is. </p> <p>The First Click Free (FCF) policy for both Google <a href="https://webmasters.googleblog.com/2008/10/first-click-free-for-web-search.html">web search</a> and <a href="https://news.googleblog.com/2007/09/first-click-free.html">News</a> was designed to address this issue. It offers promotion and discovery opportunities for publishers with subscription content, while giving Google users an opportunity to discover that content. Over the past year, we have worked with publishers to investigate the effects of FCF on user satisfaction and on the sustainability of the publishing ecosystem. We found that while FCF is a reasonable sampling model, publishers are in a better position to determine what specific sampling strategy works best for them. Therefore, we are removing FCF as a requirement for Search, and we encourage publishers to experiment with different free sampling schemes, as long as they stay within the updated <a href="https://support.google.com/webmasters/answer/35769">webmaster guidelines</a>. We call this <b>Flexible Sampling</b>.</p> <p>One of the original motivations for FCF is to address the issues surrounding <a href="https://support.google.com/webmasters/answer/66355?hl=en">cloaking</a>, where the content served to Googlebot is different from the content served to users. Spammers often seek to game search engines by showing interesting content to the search engine, say healthy food recipes, but then showing users an offer for diet pills. This “bait and switch” scheme creates a bad user experience since users do not get the content they expected. Sites with paywalls are strongly encouraged to apply the new <a href="https://developers.google.com/search/docs/data-types/paywalled-content">structured data</a> to their pages, because without it, the paywall may be interpreted as a form of cloaking, and the pages would then be removed from search results. </p> <p>Based on our investigations, we have created detailed <a href="https://support.google.com/webmasters/answer/7532484">best practices</a> for implementing flexible sampling. There are two types of sampling we advise: <b>metering</b>, which provides users with a quota of free articles to consume, after which paywalls will start appearing; and <b>lead-in</b>, which offers a portion of an article’s content without it being shown in full. </p> <p>For metering, we think that monthly (rather than daily) metering provides more flexibility and a safer environment for testing. The user impact of changing from one integer value to the next is less significant at, say, 10 monthly samples than at 3 daily samples. All publishers and their audiences are different, so there is no single value for optimal free sampling across publishers. However, we recommend that publishers start by providing 10 free clicks per month to Google search users in order to preserve a good user experience for new potential subscribers. Publishers should then experiment to optimize the tradeoff between discovery and conversion that works best for their businesses.</p> <p>Lead-in is generally implemented as truncated content, such as the first few sentences or 50-100 words of the article. Lead-in allows users a taste of how valuable the content may be. Compared to a page with completely blocked content, lead-in clearly provides more utility and added value to users. </p> <p>We are excited by this change as it allows the growth of the premium content ecosystem, which ultimately benefits users. We look forward to the prospect of serving users more high quality content!</p> <br> <span class="byline-author">Posted by Cody Kwok, Principal Engineer</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>In Google’s <a href="https://www.google.com/search/howsearchworks/mission/">mission</a> to organize the world's information, we want to guide Google users to the highest quality content, the principle exemplified in our <a href="http://static.googleusercontent.com/media/www.google.com/en//insidesearch/howsearchworks/assets/searchqualityevaluatorguidelines.pdf">quality rater guidelines</a>. Professional publishers provide the lion’s share of quality content that benefits users and we want to encourage their success.</p> <p>The ecosystem is sustained via two main sources of revenue: ads and subscriptions, with the latter requiring a delicate balance to be effective in Search. Typically subscription content is hidden behind paywalls, so that users who don’t have a subscription don’t have access. Our evaluations have shown that users who are not familiar with the high quality content behind a paywall often turn to other sites offering free content. It is difficult to justify a subscription if one doesn't already know how valuable the content is, and in fact, our experiments have shown that a portion of users shy away from subscription sites. Therefore, it is essential that sites provide some amount of free sampling of their content so that users can learn how valuable their content is. </p> <p>The First Click Free (FCF) policy for both Google <a href="https://webmasters.googleblog.com/2008/10/first-click-free-for-web-search.html">web search</a> and <a href="https://news.googleblog.com/2007/09/first-click-free.html">News</a> was designed to address this issue. It offers promotion and discovery opportunities for publishers with subscription content, while giving Google users an opportunity to discover that content. Over the past year, we have worked with publishers to investigate the effects of FCF on user satisfaction and on the sustainability of the publishing ecosystem. We found that while FCF is a reasonable sampling model, publishers are in a better position to determine what specific sampling strategy works best for them. Therefore, we are removing FCF as a requirement for Search, and we encourage publishers to experiment with different free sampling schemes, as long as they stay within the updated <a href="https://support.google.com/webmasters/answer/35769">webmaster guidelines</a>. We call this <b>Flexible Sampling</b>.</p> <p>One of the original motivations for FCF is to address the issues surrounding <a href="https://support.google.com/webmasters/answer/66355?hl=en">cloaking</a>, where the content served to Googlebot is different from the content served to users. Spammers often seek to game search engines by showing interesting content to the search engine, say healthy food recipes, but then showing users an offer for diet pills. This “bait and switch” scheme creates a bad user experience since users do not get the content they expected. Sites with paywalls are strongly encouraged to apply the new <a href="https://developers.google.com/search/docs/data-types/paywalled-content">structured data</a> to their pages, because without it, the paywall may be interpreted as a form of cloaking, and the pages would then be removed from search results. </p> <p>Based on our investigations, we have created detailed <a href="https://support.google.com/webmasters/answer/7532484">best practices</a> for implementing flexible sampling. There are two types of sampling we advise: <b>metering</b>, which provides users with a quota of free articles to consume, after which paywalls will start appearing; and <b>lead-in</b>, which offers a portion of an article’s content without it being shown in full. </p> <p>For metering, we think that monthly (rather than daily) metering provides more flexibility and a safer environment for testing. The user impact of changing from one integer value to the next is less significant at, say, 10 monthly samples than at 3 daily samples. All publishers and their audiences are different, so there is no single value for optimal free sampling across publishers. However, we recommend that publishers start by providing 10 free clicks per month to Google search users in order to preserve a good user experience for new potential subscribers. Publishers should then experiment to optimize the tradeoff between discovery and conversion that works best for their businesses.</p> <p>Lead-in is generally implemented as truncated content, such as the first few sentences or 50-100 words of the article. Lead-in allows users a taste of how valuable the content may be. Compared to a page with completely blocked content, lead-in clearly provides more utility and added value to users. </p> <p>We are excited by this change as it allows the growth of the premium content ecosystem, which ultimately benefits users. We look forward to the prospect of serving users more high quality content!</p> <br> <span class="byline-author">Posted by Cody Kwok, Principal Engineer</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Enabling more high quality content for users&url=https://webmasters.googleblog.com/2017/10/enabling-more-high-quality-content.html?hl=zh_CN&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/10/enabling-more-high-quality-content.html?hl=zh_CN'> <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/10/enabling-more-high-quality-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'> 标签： </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=zh_CN' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=zh_CN' rel='tag'> structured data </a> </span> </div> </div> </div> <div class='blog-pager' id='blog-pager'> <a class='home-link' href='https://webmasters.googleblog.com/?hl=zh_CN'> <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%20results?updated-max=2017-10-01T21:04:00-07:00&max-results=20&start=20&by-date=false&hl=zh_CN' id='Blog1_blog-pager-older-link' title='较旧的博文'> <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> 标签 </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=zh_CN'> accessibility </a> <span dir='ltr'> 10 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/advanced?hl=zh_CN'> advanced </a> <span dir='ltr'> 195 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/AMP?hl=zh_CN'> AMP </a> <span dir='ltr'> 13 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Android?hl=zh_CN'> Android </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/API?hl=zh_CN'> API </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/apps?hl=zh_CN'> apps </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/autocomplete?hl=zh_CN'> autocomplete </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/beginner?hl=zh_CN'> beginner </a> <span dir='ltr'> 173 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/CAPTCHA?hl=zh_CN'> CAPTCHA </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Chrome?hl=zh_CN'> Chrome </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/cms?hl=zh_CN'> cms </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=zh_CN'> crawling and indexing </a> <span dir='ltr'> 158 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/encryption?hl=zh_CN'> encryption </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/events?hl=zh_CN'> events </a> <span dir='ltr'> 51 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=zh_CN'> feedback and communication </a> <span dir='ltr'> 83 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/forums?hl=zh_CN'> forums </a> <span dir='ltr'> 5 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/general%20tips?hl=zh_CN'> general tips </a> <span dir='ltr'> 90 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/geotargeting?hl=zh_CN'> geotargeting </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20Assistant?hl=zh_CN'> Google Assistant </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20I%2FO?hl=zh_CN'> Google I/O </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20Images?hl=zh_CN'> Google Images </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20News?hl=zh_CN'> Google News </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hacked%20sites?hl=zh_CN'> hacked sites </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hangout?hl=zh_CN'> hangout </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hreflang?hl=zh_CN'> hreflang </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/https?hl=zh_CN'> https </a> <span dir='ltr'> 5 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/images?hl=zh_CN'> images </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/intermediate?hl=zh_CN'> intermediate </a> <span dir='ltr'> 205 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/interstitials?hl=zh_CN'> interstitials </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/javascript?hl=zh_CN'> javascript </a> <span dir='ltr'> 8 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/job%20search?hl=zh_CN'> job search </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/localization?hl=zh_CN'> localization </a> <span dir='ltr'> 21 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/malware?hl=zh_CN'> malware </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/mobile?hl=zh_CN'> mobile </a> <span dir='ltr'> 63 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=zh_CN'> mobile-friendly </a> <span dir='ltr'> 14 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/nohacked?hl=zh_CN'> nohacked </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/performance?hl=zh_CN'> performance </a> <span dir='ltr'> 17 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/product%20expert?hl=zh_CN'> product expert </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/product%20experts?hl=zh_CN'> product experts </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/products%20and%20services?hl=zh_CN'> products and services </a> <span dir='ltr'> 63 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/questions?hl=zh_CN'> questions </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/ranking?hl=zh_CN'> ranking </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/recipes?hl=zh_CN'> recipes </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rendering?hl=zh_CN'> rendering </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Responsive%20Web%20Design?hl=zh_CN'> Responsive Web Design </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rich%20cards?hl=zh_CN'> rich cards </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rich%20results?hl=zh_CN'> rich results </a> <span dir='ltr'> 10 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20console?hl=zh_CN'> search console </a> <span dir='ltr'> 35 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20for%20beginners?hl=zh_CN'> search for beginners </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20queries?hl=zh_CN'> search queries </a> <span dir='ltr'> 7 </span> </li> <li> <span dir='ltr'> search results </span> <span dir='ltr'> 140 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/security?hl=zh_CN'> security </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/seo?hl=zh_CN'> seo </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/sitemaps?hl=zh_CN'> sitemaps </a> <span dir='ltr'> 46 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/speed?hl=zh_CN'> speed </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=zh_CN'> structured data </a> <span dir='ltr'> 33 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/summit?hl=zh_CN'> summit </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/TLDs?hl=zh_CN'> TLDs </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/url%20removals?hl=zh_CN'> url removals </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/UX?hl=zh_CN'> UX </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/verification?hl=zh_CN'> verification </a> <span dir='ltr'> 8 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/video?hl=zh_CN'> video </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=zh_CN'> webmaster community </a> <span dir='ltr'> 24 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20forum?hl=zh_CN'> webmaster forum </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines?hl=zh_CN'> webmaster guidelines </a> <span dir='ltr'> 57 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=zh_CN'> webmaster tools </a> <span dir='ltr'> 177 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmasters?hl=zh_CN'> webmasters </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/youtube%20channel?hl=zh_CN'> 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=zh_CN'> 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=zh_CN'> 11月 </a> </div> <div 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=zh_CN'> 10月 </a> </div> <div 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=zh_CN'> 9月 </a> </div> <div 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=zh_CN'> 8月 </a> </div> <div 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=zh_CN'> 7月 </a> </div> <div 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=zh_CN'> 6月 </a> </div> <div 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=zh_CN'> 5月 </a> </div> <div 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=zh_CN'> 4月 </a> </div> <div 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=zh_CN'> 3月 </a> </div> <div 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=zh_CN'> 2月 </a> </div> <div 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=zh_CN'> 1月 </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=zh_CN'> 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=zh_CN'> 12月 </a> </div> <div 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=zh_CN'> 11月 </a> </div> <div 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=zh_CN'> 10月 </a> </div> <div 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=zh_CN'> 9月 </a> </div> <div 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=zh_CN'> 8月 </a> </div> <div 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=zh_CN'> 7月 </a> </div> <div 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=zh_CN'> 6月 </a> </div> <div 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=zh_CN'> 5月 </a> </div> <div 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=zh_CN'> 4月 </a> </div> <div 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=zh_CN'> 3月 </a> </div> <div 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=zh_CN'> 2月 </a> </div> <div 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=zh_CN'> 1月 </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=zh_CN'> 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=zh_CN'> 12月 </a> </div> <div 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=zh_CN'> 11月 </a> </div> <div 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=zh_CN'> 10月 </a> </div> <div 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=zh_CN'> 9月 </a> </div> <div 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=zh_CN'> 8月 </a> </div> <div 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=zh_CN'> 7月 </a> </div> <div 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=zh_CN'> 6月 </a> </div> <div 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=zh_CN'> 5月 </a> </div> <div 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=zh_CN'> 4月 </a> </div> <div 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=zh_CN'> 3月 </a> </div> <div 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=zh_CN'> 2月 </a> </div> <div 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=zh_CN'> 1月 </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=zh_CN'> 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=zh_CN'> 12月 </a> </div> <div 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=zh_CN'> 11月 </a> </div> <div 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=zh_CN'> 10月 </a> </div> <div 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=zh_CN'> 9月 </a> </div> <div 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=zh_CN'> 8月 </a> </div> <div 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=zh_CN'> 6月 </a> </div> <div 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=zh_CN'> 5月 </a> </div> <div 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=zh_CN'> 4月 </a> </div> <div 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=zh_CN'> 3月 </a> </div> <div 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=zh_CN'> 2月 </a> </div> <div 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=zh_CN'> 1月 </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=zh_CN'> 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=zh_CN'> 12月 </a> </div> <div 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=zh_CN'> 11月 </a> </div> <div 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=zh_CN'> 10月 </a> </div> <div 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=zh_CN'> 9月 </a> </div> <div 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=zh_CN'> 8月 </a> </div> <div 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=zh_CN'> 6月 </a> </div> <div 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=zh_CN'> 5月 </a> </div> <div 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=zh_CN'> 4月 </a> </div> <div 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=zh_CN'> 3月 </a> </div> <div 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=zh_CN'> 1月 </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=zh_CN'> 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=zh_CN'> 12月 </a> </div> <div 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=zh_CN'> 11月 </a> </div> <div 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=zh_CN'> 10月 </a> </div> <div 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=zh_CN'> 9月 </a> </div> <div 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=zh_CN'> 8月 </a> </div> <div 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=zh_CN'> 7月 </a> </div> <div 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=zh_CN'> 5月 </a> </div> <div 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=zh_CN'> 4月 </a> </div> <div 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=zh_CN'> 3月 </a> </div> <div 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=zh_CN'> 2月 </a> </div> <div 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=zh_CN'> 1月 </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=zh_CN'> 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=zh_CN'> 12月 </a> </div> <div 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=zh_CN'> 11月 </a> </div> <div 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=zh_CN'> 10月 </a> </div> <div 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=zh_CN'> 9月 </a> </div> <div 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=zh_CN'> 8月 </a> </div> <div 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=zh_CN'> 7月 </a> </div> <div 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=zh_CN'> 6月 </a> </div> <div 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=zh_CN'> 5月 </a> </div> <div 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=zh_CN'> 4月 </a> </div> <div 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=zh_CN'> 3月 </a> </div> <div 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=zh_CN'> 2月 </a> </div> <div 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=zh_CN'> 1月 </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=zh_CN'> 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=zh_CN'> 12月 </a> </div> <div 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=zh_CN'> 11月 </a> </div> <div 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=zh_CN'> 10月 </a> </div> <div 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=zh_CN'> 9月 </a> </div> <div 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=zh_CN'> 8月 </a> </div> <div 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=zh_CN'> 7月 </a> </div> <div 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=zh_CN'> 6月 </a> </div> <div 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=zh_CN'> 5月 </a> </div> <div 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=zh_CN'> 4月 </a> </div> <div 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=zh_CN'> 3月 </a> </div> <div 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=zh_CN'> 2月 </a> </div> <div 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=zh_CN'> 1月 </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=zh_CN'> 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=zh_CN'> 12月 </a> </div> <div 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=zh_CN'> 11月 </a> </div> <div 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=zh_CN'> 10月 </a> </div> <div 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=zh_CN'> 9月 </a> </div> <div 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=zh_CN'> 8月 </a> </div> <div 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=zh_CN'> 7月 </a> </div> <div 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=zh_CN'> 6月 </a> </div> <div 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=zh_CN'> 5月 </a> </div> <div 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=zh_CN'> 4月 </a> </div> <div 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=zh_CN'> 3月 </a> </div> <div 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=zh_CN'> 2月 </a> </div> <div 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=zh_CN'> 1月 </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=zh_CN'> 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=zh_CN'> 12月 </a> </div> <div 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=zh_CN'> 11月 </a> </div> <div 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=zh_CN'> 10月 </a> </div> <div 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=zh_CN'> 9月 </a> </div> <div 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=zh_CN'> 8月 </a> </div> <div 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=zh_CN'> 7月 </a> </div> <div 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=zh_CN'> 6月 </a> </div> <div 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=zh_CN'> 5月 </a> </div> <div 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=zh_CN'> 4月 </a> </div> <div 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=zh_CN'> 3月 </a> </div> <div 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=zh_CN'> 2月 </a> </div> <div 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=zh_CN'> 1月 </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=zh_CN'> 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=zh_CN'> 12月 </a> </div> <div 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=zh_CN'> 11月 </a> </div> <div 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=zh_CN'> 10月 </a> </div> <div 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=zh_CN'> 9月 </a> </div> <div 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=zh_CN'> 8月 </a> </div> <div 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=zh_CN'> 7月 </a> </div> <div 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=zh_CN'> 6月 </a> </div> <div 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=zh_CN'> 5月 </a> </div> <div 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=zh_CN'> 4月 </a> </div> <div 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=zh_CN'> 3月 </a> </div> <div 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=zh_CN'> 2月 </a> </div> <div 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=zh_CN'> 1月 </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=zh_CN'> 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=zh_CN'> 12月 </a> </div> <div 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=zh_CN'> 11月 </a> </div> <div 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=zh_CN'> 10月 </a> </div> <div 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=zh_CN'> 9月 </a> </div> <div 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=zh_CN'> 8月 </a> </div> <div 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=zh_CN'> 7月 </a> </div> <div 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=zh_CN'> 6月 </a> </div> <div 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=zh_CN'> 5月 </a> </div> <div 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=zh_CN'> 4月 </a> </div> <div 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=zh_CN'> 3月 </a> </div> <div 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=zh_CN'> 2月 </a> </div> <div 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=zh_CN'> 1月 </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=zh_CN'> 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=zh_CN'> 12月 </a> </div> <div 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=zh_CN'> 11月 </a> </div> <div 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=zh_CN'> 10月 </a> </div> <div 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=zh_CN'> 9月 </a> </div> <div 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=zh_CN'> 8月 </a> </div> <div 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=zh_CN'> 7月 </a> </div> <div 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=zh_CN'> 6月 </a> </div> <div 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=zh_CN'> 5月 </a> </div> <div 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=zh_CN'> 4月 </a> </div> <div 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=zh_CN'> 3月 </a> </div> <div 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=zh_CN'> 2月 </a> </div> <div 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=zh_CN'> 1月 </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=zh_CN'> 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=zh_CN'> 12月 </a> </div> <div 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=zh_CN'> 11月 </a> </div> <div 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=zh_CN'> 10月 </a> </div> <div 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=zh_CN'> 9月 </a> </div> <div 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=zh_CN'> 8月 </a> </div> <div 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=zh_CN'> 7月 </a> </div> <div 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=zh_CN'> 6月 </a> </div> <div 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=zh_CN'> 5月 </a> </div> <div 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=zh_CN'> 4月 </a> </div> <div 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=zh_CN'> 3月 </a> </div> <div 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=zh_CN'> 2月 </a> </div> <div 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=zh_CN'> 1月 </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=zh_CN'> 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=zh_CN'> 12月 </a> </div> <div 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=zh_CN'> 11月 </a> </div> <div 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=zh_CN'> 10月 </a> </div> <div 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=zh_CN'> 9月 </a> </div> <div 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=zh_CN'> 8月 </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/2263754362-widgets.js"></script> <script type='text/javascript'> window['__wavt'] = 'AOuZoY7rYy-qcIVL_lj8AzIR2gfGyo0Mxg:1733198628651';_WidgetManager._Init('//www.blogger.com/rearrange?blogID\x3d32069983','//webmasters.googleblog.com/search/label/search%20results?hl\x3dzh_CN','32069983'); _WidgetManager._SetDataContext([{'name': 'blog', 'data': {'blogId': '32069983', 'title': 'Official Google Webmaster Central Blog', 'url': 'https://webmasters.googleblog.com/search/label/search%20results?hl\x3dzh_CN', 'canonicalUrl': 'https://webmasters.googleblog.com/search/label/search%20results', 'homepageUrl': 'https://webmasters.googleblog.com/?hl\x3dzh_CN', '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': 'zh-CN', 'localeUnderscoreDelimited': 'zh_cn', '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/0399bd29ab1434ad', 'plusOneApiSrc': 'https://apis.google.com/js/platform.js', 'disableGComments': true, 'interstitialAccepted': false, 'sharing': {'platforms': [{'name': '\u83b7\u53d6\u94fe\u63a5', 'key': 'link', 'shareMessage': '\u83b7\u53d6\u94fe\u63a5', 'target': ''}, {'name': 'Facebook', 'key': 'facebook', 'shareMessage': '\u5206\u4eab\u5230 Facebook', 'target': 'facebook'}, {'name': 'BlogThis!', 'key': 'blogThis', 'shareMessage': 'BlogThis!', 'target': 'blog'}, {'name': 'X', 'key': 'twitter', 'shareMessage': '\u5206\u4eab\u5230 X', 'target': 'twitter'}, {'name': 'Pinterest', 'key': 'pinterest', 'shareMessage': '\u5206\u4eab\u5230 Pinterest', 'target': 'pinterest'}, {'name': '\u7535\u5b50\u90ae\u4ef6', 'key': 'email', 'shareMessage': '\u7535\u5b50\u90ae\u4ef6', 'target': 'email'}], 'disableGooglePlus': true, 'googlePlusShareButtonWidth': 0, 'googlePlusBootstrap': '\x3cscript type\x3d\x22text/javascript\x22\x3ewindow.___gcfg \x3d {\x27lang\x27: \x27zh_CN\x27};\x3c/script\x3e'}, 'hasCustomJumpLinkMessage': false, 'jumpLinkMessage': '\u9605\u8bfb\u5168\u6587', 'pageType': 'index', 'searchLabel': 'search results', 'pageName': 'search results', 'pageTitle': 'Official Google Webmaster Central Blog: search results', 'metaDescription': 'Official news on crawling and indexing sites for the Google index'}}, {'name': 'features', 'data': {}}, {'name': 'messages', 'data': {'edit': '\u4fee\u6539', 'linkCopiedToClipboard': '\u94fe\u63a5\u5df2\u590d\u5236\u5230\u526a\u8d34\u677f\uff01', 'ok': '\u786e\u5b9a', 'postLink': '\u535a\u6587\u94fe\u63a5'}}, {'name': 'template', 'data': {'name': 'custom', 'localizedName': '\u81ea\u5b9a\u4e49', '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%20results?hl\x3dzh_CN', 'type': 'feed', 'isSingleItem': false, 'isMultipleItems': true, 'isError': false, 'isPage': false, 'isPost': false, 'isHomepage': false, 'isArchive': false, 'isSearch': true, 'isLabelSearch': true, 'search': {'label': 'search results', 'resultsMessage': '\u76ee\u524d\u663e\u793a\u7684\u662f\u6807\u7b7e\u4e3a\u201csearch results\u201d\u7684\u535a\u6587', 'resultsMessageHtml': '\u76ee\u524d\u663e\u793a\u7684\u662f\u6807\u7b7e\u4e3a\u201c\x3cspan class\x3d\x27search-label\x27\x3esearch results\x3c/span\x3e\u201d\u7684\u535a\u6587'}}}]); _WidgetManager._RegisterWidget('_HeaderView', new _WidgetInfo('Header1', 'header', document.getElementById('Header1'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_BlogView', new _WidgetInfo('Blog1', 'main', document.getElementById('Blog1'), {'cmtInteractionsEnabled': false, 'navMessage': '\u663e\u793a\u6807\u7b7e\u4e3a\u201c\x3cb\x3esearch results\x3c/b\x3e\u201d\u7684\u535a\u6587\u3002\x3ca href\x3d\x22https://webmasters.googleblog.com/\x22\x3e\u663e\u793a\u6240\u6709\u535a\u6587\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': '\u6b63\u5728\u52a0\u8f7d\u2026'}, '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>