CINXE.COM

<!DOCTYPE html> <html class='v2 list-page' dir='ltr' itemscope='' itemtype='http://schema.org/Blog' lang='en' xmlns='http://www.w3.org/1999/xhtml' xmlns:b='http://www.google.com/2005/gml/b' xmlns:data='http://www.google.com/2005/gml/data' xmlns:expr='http://www.google.com/2005/gml/expr'> <head> <link href='https://www.blogger.com/static/v1/widgets/3566091532-css_bundle_v2.css' rel='stylesheet' type='text/css'/> <title> Official Google Webmaster Central Blog: 2017 </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/2017/' 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/2017/' 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://draft.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/2017/' 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://draft.blogger.com/dyn-css/authorization.css?targetBlogID=32069983&zx=8855dad6-3029-4476-9a6a-423344a04200' media='none' onload='if(media!='all')media='all'' rel='stylesheet'/><noscript><link href='https://draft.blogger.com/dyn-css/authorization.css?targetBlogID=32069983&zx=8855dad6-3029-4476-9a6a-423344a04200' rel='stylesheet'/></noscript> <meta name='google-adsense-platform-account' content='ca-host-pub-1556223355139109'/> <meta name='google-adsense-platform-domain' content='blogspot.com'/> </head> <body> <script type='text/javascript'> //<![CDATA[ var axel = Math.random() + ""; var a = axel * 10000000000000; document.write('<iframe src="https://2542116.fls.doubleclick.net/activityi;src=2542116;type=gblog;cat=googl0;ord=ord=' + a + '?" width="1" height="1" frameborder="0" style="display:none"></iframe>'); //]]> </script> <noscript> <img alt='' height='1' src='https://ad.doubleclick.net/ddm/activity/src=2542116;type=gblog;cat=googl0;ord=1?' width='1'/> </noscript>  <div class='header-outer'> <div class='header-inner'> <div class='section' id='header'><div class='widget Header' data-version='1' id='Header1'> <div class='header-left'> <div class='header-title'> <a class='google-logo' href='https://webmasters.googleblog.com/?hl=en'> <img height='50' src='https://www.gstatic.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png'/> </a> <a href='/'> <h2> Webmaster Central Blog </h2> </a> </div> <div class='header-desc'> Official news on crawling and indexing sites for the Google index </div> </div> </div></div> </div> </div>  <div class='cols-wrapper loading'> <div class='col-main-wrapper'> <div class='col-main'> <div class='section' id='main'><div class='widget Blog' data-version='1' id='Blog1'> <div class='post' data-id='4516182304328193300' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/12/the-seo-snippets-video-series.html?hl=en' itemprop='url' title='Introducing the new Webmaster Video Series'> Introducing the new Webmaster Video Series </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, December 21, 2017 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>Google has a broad range of resources to help you better understand your website and improve its performance. This Webmaster Central Blog, the Help Center, the Webmaster forum, and the recently released <a href="https://support.google.com/webmasters/answer/7451184">Search Engine Optimization (SEO) Starter Guide</a> are just a few. </p> <p>We also have a YouTube channel, for answers to your questions in video format. To help with short & to the point answers to specific questions, we've just launched a new series, which we call <a href="https://www.youtube.com/watch?v=p74HC4x5AUE&list=PLKoqnv2vTMUPhLQ054sMg3vgzy9md9tWg">SEO Snippets.</a></p> <iframe width="560" height="315" src="https://www.youtube.com/embed/p74HC4x5AUE?list=PLKoqnv2vTMUPhLQ054sMg3vgzy9md9tWg" frameborder="0" gesture="media" allow="encrypted-media" allowfullscreen></iframe> <p>In this series of short videos, the Google team will be answering some of the webmaster and SEO questions that we regularly see on the <a href="https://support.google.com/webmasters/go/community">Webmaster Central Help Forum</a>. From 404 errors, how and when crawling works, a site's URL structure, to duplicate content, we'll have something here for you.</p> <p>Check out the links shared in the videos to get more helpful webmaster information, drop by our <a href="https://support.google.com/webmasters/go/community">help forum</a> and subscribe to our <a href="https://www.youtube.com/googlewebmasters">YouTube channel</a> for more tips and insights!</p> <br> <span class="byline-author">Posted by Aurora Morales, Google Search Outreach</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <p>Google has a broad range of resources to help you better understand your website and improve its performance. This Webmaster Central Blog, the Help Center, the Webmaster forum, and the recently released <a href="https://support.google.com/webmasters/answer/7451184">Search Engine Optimization (SEO) Starter Guide</a> are just a few. </p> <p>We also have a YouTube channel, for answers to your questions in video format. To help with short & to the point answers to specific questions, we've just launched a new series, which we call <a href="https://www.youtube.com/watch?v=p74HC4x5AUE&list=PLKoqnv2vTMUPhLQ054sMg3vgzy9md9tWg">SEO Snippets.</a></p> <iframe width="560" height="315" src="https://www.youtube.com/embed/p74HC4x5AUE?list=PLKoqnv2vTMUPhLQ054sMg3vgzy9md9tWg" frameborder="0" gesture="media" allow="encrypted-media" allowfullscreen></iframe> <p>In this series of short videos, the Google team will be answering some of the webmaster and SEO questions that we regularly see on the <a href="https://support.google.com/webmasters/go/community">Webmaster Central Help Forum</a>. From 404 errors, how and when crawling works, a site's URL structure, to duplicate content, we'll have something here for you.</p> <p>Check out the links shared in the videos to get more helpful webmaster information, drop by our <a href="https://support.google.com/webmasters/go/community">help forum</a> and subscribe to our <a href="https://www.youtube.com/googlewebmasters">YouTube channel</a> for more tips and insights!</p> <br> <span class="byline-author">Posted by Aurora Morales, Google Search Outreach</span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Introducing the new Webmaster Video Series&url=https://webmasters.googleblog.com/2017/12/the-seo-snippets-video-series.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/12/the-seo-snippets-video-series.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/12/the-seo-snippets-video-series.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/beginner?hl=en' rel='tag'> beginner </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/video?hl=en' rel='tag'> video </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en' rel='tag'> webmaster community </a> </span> </div> </div> </div> <div class='post' data-id='4104461644038344640' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/12/rich-results-tester.html?hl=en' itemprop='url' title='Introducing Rich Results & the Rich Results Testing Tool'> Introducing Rich Results & the Rich Results Testing Tool </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, December 19, 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><a href="https://webmasters.googleblog.com/2009/05/introducing-rich-snippets.html">Over the years</a>, the different ways you can choose to highlight your website's content in search has grown dramatically. In the past, we've called these rich snippets, rich cards, or enriched results. Going forward - to simplify the terminology -  our documentation will use the name "rich results" for all of them. Additionally, we're introducing a <a href="https://search.google.com/test/rich-results">new rich results testing tool</a> to make diagnosing your pages' structured data easier.</p> <p>The new testing tool focuses on the structured data types that are eligible to be shown as rich results. It allows you to test all data sources on your pages, such as JSON-LD (which we recommend), Microdata, or RDFa. The new tool provides a more accurate reflection of the page’s appearance on Search and includes improved handling for Structured Data found on dynamically loaded content. The tests for Recipes, Jobs, Movies, and Courses are currently supported -- but this is just a first step, we plan on expanding over time.</p> <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgv55zwhRjRPwwyflIduGrTGWoXpaVlFtsd5NgJfLuxv2WnhjBpXV74M5Ri2bQQtZHz-7IElsVm4JNygSbPpal7KDxaKceJ4HChGLglul6DqjOd0X9lz4ivRDbcCCQGY7uK7IFx/s1600/kahhhhhhhhhhnn.png" imageanchor="1" style="clear: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="1330" data-original-width="825" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgv55zwhRjRPwwyflIduGrTGWoXpaVlFtsd5NgJfLuxv2WnhjBpXV74M5Ri2bQQtZHz-7IElsVm4JNygSbPpal7KDxaKceJ4HChGLglul6DqjOd0X9lz4ivRDbcCCQGY7uK7IFx/s400/kahhhhhhhhhhnn.png" width="248" /></a></div> <p>Testing a page is easy: just open the <a href="https://search.google.com/test/rich-results">testing tool</a>, enter a URL, and review the output. If there are issues, the tool will highlight the invalid code in the page source. If you're working with others on this page, the share-icon on the bottom-right lets you do that quickly. You can also use preview button to view all the different rich results the page is eligible for. And … once you're happy with the result, use Submit To Google to fetch & index this page for search. </p> <p>Want to get started with <strike>rich snippets</strike> rich results? Check out our <a href="https://developers.google.com/search/docs/guides/search-gallery">guides for marking up your content</a>. Feel free to drop by our <a href="https://support.google.com/webmasters/go/community">Webmaster Help forums</a> should you have any questions or get stuck; the awesome experts there can often help resolve issues and give you tips in no time!</p> <br> <span class="byline-author">Posted by Shachar Pooyae, 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><a href="https://webmasters.googleblog.com/2009/05/introducing-rich-snippets.html">Over the years</a>, the different ways you can choose to highlight your website's content in search has grown dramatically. In the past, we've called these rich snippets, rich cards, or enriched results. Going forward - to simplify the terminology -  our documentation will use the name "rich results" for all of them. Additionally, we're introducing a <a href="https://search.google.com/test/rich-results">new rich results testing tool</a> to make diagnosing your pages' structured data easier.</p> <p>The new testing tool focuses on the structured data types that are eligible to be shown as rich results. It allows you to test all data sources on your pages, such as JSON-LD (which we recommend), Microdata, or RDFa. The new tool provides a more accurate reflection of the page’s appearance on Search and includes improved handling for Structured Data found on dynamically loaded content. The tests for Recipes, Jobs, Movies, and Courses are currently supported -- but this is just a first step, we plan on expanding over time.</p> <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgv55zwhRjRPwwyflIduGrTGWoXpaVlFtsd5NgJfLuxv2WnhjBpXV74M5Ri2bQQtZHz-7IElsVm4JNygSbPpal7KDxaKceJ4HChGLglul6DqjOd0X9lz4ivRDbcCCQGY7uK7IFx/s1600/kahhhhhhhhhhnn.png" imageanchor="1" style="clear: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="1330" data-original-width="825" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgv55zwhRjRPwwyflIduGrTGWoXpaVlFtsd5NgJfLuxv2WnhjBpXV74M5Ri2bQQtZHz-7IElsVm4JNygSbPpal7KDxaKceJ4HChGLglul6DqjOd0X9lz4ivRDbcCCQGY7uK7IFx/s400/kahhhhhhhhhhnn.png" width="248" /></a></div> <p>Testing a page is easy: just open the <a href="https://search.google.com/test/rich-results">testing tool</a>, enter a URL, and review the output. If there are issues, the tool will highlight the invalid code in the page source. If you're working with others on this page, the share-icon on the bottom-right lets you do that quickly. You can also use preview button to view all the different rich results the page is eligible for. And … once you're happy with the result, use Submit To Google to fetch & index this page for search. </p> <p>Want to get started with <strike>rich snippets</strike> rich results? Check out our <a href="https://developers.google.com/search/docs/guides/search-gallery">guides for marking up your content</a>. Feel free to drop by our <a href="https://support.google.com/webmasters/go/community">Webmaster Help forums</a> should you have any questions or get stuck; the awesome experts there can often help resolve issues and give you tips in no time!</p> <br> <span class="byline-author">Posted by Shachar Pooyae, 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 Rich Results & the Rich Results Testing Tool&url=https://webmasters.googleblog.com/2017/12/rich-results-tester.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/12/rich-results-tester.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/12/rich-results-tester.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/rich%20cards?hl=en' rel='tag'> rich cards </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/rich%20results?hl=en' rel='tag'> rich results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=en' rel='tag'> structured data </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='5978040791584347089' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/12/nohacked-30-fixing-common-hack-cases.html?hl=en' itemprop='url' title='#NoHacked 3.0: Fixing common hack cases'> #NoHacked 3.0: Fixing common hack cases </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Monday, December 18, 2017 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> So far on <a href="https://twitter.com/googlewmc ">#NoHacked</a>, we have shared some tips on detection and prevention. Now that you are able to detect hack attack, we would like to introduce some common hacking techniques and guides on how to fix them! </p><ul> <li><a href="https://developers.google.com/webmasters/hacked/docs/fixing_the_cloaked_keywords_hack ">Fixing the Cloaked Keywords and Links Hack</a> <div class="blgimg1"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlBtPKBYN8jr3EFt_k646T8UXnycDIdloEEA56rmlQfPA7tQomd4fAVxJNZ_7XRRf0YQzQu9NxQ_6SVNixIJFD8BUxGf0VdbLNvOIkq2WAEc9-IENBSihJtVenRwck59bb9BcS/s1600/image4.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlBtPKBYN8jr3EFt_k646T8UXnycDIdloEEA56rmlQfPA7tQomd4fAVxJNZ_7XRRf0YQzQu9NxQ_6SVNixIJFD8BUxGf0VdbLNvOIkq2WAEc9-IENBSihJtVenRwck59bb9BcS/s1600/image4.png" /></a></div> The cloaked keywords and link hack automatically creates many pages with nonsensical sentences, links, and images. These pages sometimes contain basic template elements from the original site, so at first glance, the pages might look like normal parts of the target site until you read the content. In this type of attack, hackers usually use cloaking techniques to hide the malicious content and make the injected page appear as part of the original site or a 404 error page. <li><a href="https://developers.google.com/webmasters/hacked/docs/fixing_the_gibberish_hack">Fixing the Gibberish Hack</a> <div class="blgimg2"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgN89F5rRLUfrg3sFQ6r-j-wHs8gfx6Pdoun4HcO26PXWgdadJ36ndvXpxhHLDGJq6H_9THzCkZccpY172CEJTvpAZCrtki5b0dX3wUXorPvuGJRVD74BQOKsaPAkQ1xSuPTXAo/s1600/image1.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgN89F5rRLUfrg3sFQ6r-j-wHs8gfx6Pdoun4HcO26PXWgdadJ36ndvXpxhHLDGJq6H_9THzCkZccpY172CEJTvpAZCrtki5b0dX3wUXorPvuGJRVD74BQOKsaPAkQ1xSuPTXAo/s1600/image1.png" /></a></div> The gibberish hack automatically creates many pages with nonsensical sentences filled with keywords on the target site. Hackers do this so the hacked pages show up in Google Search. Then, when people try to visit these pages, they'll be redirected to an unrelated page, like a porn site for example. <li><a href="https://developers.google.com/webmasters/hacked/docs/fixing_the_japanese_keyword_hack">Fixing the Japanese Keywords Hack </a> <div class="blgimg3"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjbPhKa423QXxP8sKp_c8eF8HWB2tH0hqYDwXFJLsZMc746qY7CyFo6IRNQiaw8-OtD4Z3pLjXpoyJZ6UvzdwyauG6-mnNl7MDz_3QnBXsoefoGYy9H9eJ7kv6Jox30tdTkyEuC/s1600/image3.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjbPhKa423QXxP8sKp_c8eF8HWB2tH0hqYDwXFJLsZMc746qY7CyFo6IRNQiaw8-OtD4Z3pLjXpoyJZ6UvzdwyauG6-mnNl7MDz_3QnBXsoefoGYy9H9eJ7kv6Jox30tdTkyEuC/s1600/image3.png" /></a></div> The Japanese keywords hack typically creates new pages with Japanese text on the target site in randomly generated directory names. These pages are monetized using affiliate links to stores selling fake brand merchandise and then shown in Google search. Sometimes the accounts of the hackers get added in Search Console as site owners. </li></ul> <p> Lastly, after you clean your site and fix the problem, make sure to <a href="https://support.google.com/webmasters/answer/35843">file for a reconsideration request</a> to have our teams review your site. </p> <div class="blgimg4"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiDTG1FSIUeBevJ8nXhMNYyvjUKoZog1QFRlpzGcnS1yc8vP5ezRlSMyCb2_AWuTpmKSBqJmU3SKTZdsfNUdmXP7mpM7llodWtv7lXu1GeOENbZeThkzf_Y55ygviuEliYbnlCk/s1600/image2.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiDTG1FSIUeBevJ8nXhMNYyvjUKoZog1QFRlpzGcnS1yc8vP5ezRlSMyCb2_AWuTpmKSBqJmU3SKTZdsfNUdmXP7mpM7llodWtv7lXu1GeOENbZeThkzf_Y55ygviuEliYbnlCk/s1600/image2.png" /></a></div> <p> If you have any questions, post your questions on <a href="https://productforums.google.com/forum/#!forum/webmasters">our Webmaster Help Forums</a>! </p> <style> .blgimg1 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; } .blgimg2 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; } .blgimg3 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; } .blgimg4 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; } </style> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> So far on <a href="https://twitter.com/googlewmc ">#NoHacked</a>, we have shared some tips on detection and prevention. Now that you are able to detect hack attack, we would like to introduce some common hacking techniques and guides on how to fix them! </p><ul> <li><a href="https://developers.google.com/webmasters/hacked/docs/fixing_the_cloaked_keywords_hack ">Fixing the Cloaked Keywords and Links Hack</a> <div class="blgimg1"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlBtPKBYN8jr3EFt_k646T8UXnycDIdloEEA56rmlQfPA7tQomd4fAVxJNZ_7XRRf0YQzQu9NxQ_6SVNixIJFD8BUxGf0VdbLNvOIkq2WAEc9-IENBSihJtVenRwck59bb9BcS/s1600/image4.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlBtPKBYN8jr3EFt_k646T8UXnycDIdloEEA56rmlQfPA7tQomd4fAVxJNZ_7XRRf0YQzQu9NxQ_6SVNixIJFD8BUxGf0VdbLNvOIkq2WAEc9-IENBSihJtVenRwck59bb9BcS/s1600/image4.png" /></a></div> The cloaked keywords and link hack automatically creates many pages with nonsensical sentences, links, and images. These pages sometimes contain basic template elements from the original site, so at first glance, the pages might look like normal parts of the target site until you read the content. In this type of attack, hackers usually use cloaking techniques to hide the malicious content and make the injected page appear as part of the original site or a 404 error page. <li><a href="https://developers.google.com/webmasters/hacked/docs/fixing_the_gibberish_hack">Fixing the Gibberish Hack</a> <div class="blgimg2"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgN89F5rRLUfrg3sFQ6r-j-wHs8gfx6Pdoun4HcO26PXWgdadJ36ndvXpxhHLDGJq6H_9THzCkZccpY172CEJTvpAZCrtki5b0dX3wUXorPvuGJRVD74BQOKsaPAkQ1xSuPTXAo/s1600/image1.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgN89F5rRLUfrg3sFQ6r-j-wHs8gfx6Pdoun4HcO26PXWgdadJ36ndvXpxhHLDGJq6H_9THzCkZccpY172CEJTvpAZCrtki5b0dX3wUXorPvuGJRVD74BQOKsaPAkQ1xSuPTXAo/s1600/image1.png" /></a></div> The gibberish hack automatically creates many pages with nonsensical sentences filled with keywords on the target site. Hackers do this so the hacked pages show up in Google Search. Then, when people try to visit these pages, they'll be redirected to an unrelated page, like a porn site for example. <li><a href="https://developers.google.com/webmasters/hacked/docs/fixing_the_japanese_keyword_hack">Fixing the Japanese Keywords Hack </a> <div class="blgimg3"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjbPhKa423QXxP8sKp_c8eF8HWB2tH0hqYDwXFJLsZMc746qY7CyFo6IRNQiaw8-OtD4Z3pLjXpoyJZ6UvzdwyauG6-mnNl7MDz_3QnBXsoefoGYy9H9eJ7kv6Jox30tdTkyEuC/s1600/image3.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjbPhKa423QXxP8sKp_c8eF8HWB2tH0hqYDwXFJLsZMc746qY7CyFo6IRNQiaw8-OtD4Z3pLjXpoyJZ6UvzdwyauG6-mnNl7MDz_3QnBXsoefoGYy9H9eJ7kv6Jox30tdTkyEuC/s1600/image3.png" /></a></div> The Japanese keywords hack typically creates new pages with Japanese text on the target site in randomly generated directory names. These pages are monetized using affiliate links to stores selling fake brand merchandise and then shown in Google search. Sometimes the accounts of the hackers get added in Search Console as site owners. </li></ul> <p> Lastly, after you clean your site and fix the problem, make sure to <a href="https://support.google.com/webmasters/answer/35843">file for a reconsideration request</a> to have our teams review your site. </p> <div class="blgimg4"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiDTG1FSIUeBevJ8nXhMNYyvjUKoZog1QFRlpzGcnS1yc8vP5ezRlSMyCb2_AWuTpmKSBqJmU3SKTZdsfNUdmXP7mpM7llodWtv7lXu1GeOENbZeThkzf_Y55ygviuEliYbnlCk/s1600/image2.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiDTG1FSIUeBevJ8nXhMNYyvjUKoZog1QFRlpzGcnS1yc8vP5ezRlSMyCb2_AWuTpmKSBqJmU3SKTZdsfNUdmXP7mpM7llodWtv7lXu1GeOENbZeThkzf_Y55ygviuEliYbnlCk/s1600/image2.png" /></a></div> <p> If you have any questions, post your questions on <a href="https://productforums.google.com/forum/#!forum/webmasters">our Webmaster Help Forums</a>! </p> <style> .blgimg1 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; } .blgimg2 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; } .blgimg3 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; } .blgimg4 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; } </style> <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:#NoHacked 3.0: Fixing common hack cases&url=https://webmasters.googleblog.com/2017/12/nohacked-30-fixing-common-hack-cases.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/12/nohacked-30-fixing-common-hack-cases.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/12/nohacked-30-fixing-common-hack-cases.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> </div> </div> </div> <div class='post' data-id='2832288981765021097' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/12/getting-your-site-ready-for-mobile.html?hl=en' itemprop='url' title='Getting your site ready for mobile-first indexing'> Getting your site ready for mobile-first indexing </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Monday, December 18, 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"> When we <a href="https://webmasters.googleblog.com/2016/11/mobile-first-indexing.html">announced</a> almost a year ago that we're experimenting with mobile-first indexing, we said we'd update publishers about our progress, something that we've done the past few months through public talks in <a href="https://www.youtube.com/user/GoogleWebmasterHelp/playlists?sort=dd&view=50&shelf_id=7">office hours on Hangouts on Air</a> and at conferences like <a href="https://www.google.com/search?q=mobile+first+indexing+pubcon">Pubcon</a>.<br /> <br /> To recap, currently our crawling, indexing, and ranking systems typically look at the desktop version of a page's content, which may cause issues for mobile searchers when that version is vastly different from the mobile version. Mobile-first indexing means that we'll use the mobile version of the content for indexing and ranking, to better help our – primarily mobile – users find what they're looking for. Webmasters will see significantly increased crawling by <a href="https://support.google.com/webmasters/answer/1061943">Smartphone Googlebot</a>, and the snippets in the results, as well as the content on the <a href="https://support.google.com/websearch/answer/1687222">Google cache pages</a>, will be from the mobile version of the pages.<br /> <br /> <a href="https://webmasters.googleblog.com/2016/11/mobile-first-indexing.html">As we said</a>, sites that make use of <a href="https://developers.google.com/search/mobile-sites/mobile-seo/responsive-design">responsive web design</a> and correctly implement <a href="https://developers.google.com/search/mobile-sites/mobile-seo/dynamic-serving">dynamic serving</a> (that include all of the desktop content and markup) generally don't have to do anything. Here are some extra tips that help ensure a site is ready for mobile-first indexing:<br /> <ul> <li>Make sure the mobile version of the site also has the important, high-quality content. This includes text, images (with alt-attributes), and videos - in the usual crawlable and indexable formats.</li> <li>Structured data is important for indexing and search features that users love: it should be both on the mobile and desktop version of the site. Ensure URLs within the structured data are updated to the mobile version on the mobile pages.</li> <li>Metadata should be present on both versions of the site. It provides hints about the content on a page for indexing and serving. For example, make sure that titles and meta descriptions are equivalent across both versions of all pages on the site.</li> <li>No changes are necessary for interlinking with separate mobile URLs (m.-dot sites). For <a href="https://developers.google.com/search/mobile-sites/mobile-seo/separate-urls">sites using separate mobile URLs</a>, keep the existing link rel=canonical and link rel=alternate elements between these versions.</li> <li>Check hreflang links on separate mobile URLs. When using <a href="https://support.google.com/webmasters/answer/189077">link rel=hreflang</a> elements for <a href="https://support.google.com/webmasters/answer/182192">internationalization</a>, link between mobile and desktop URLs separately. Your mobile URLs' hreflang should point to the other language/region versions on other mobile URLs, and similarly link desktop with other desktop URLs using hreflang link elements there.</li> <li>Ensure the servers hosting the site have enough capacity to handle potentially increased <a href="https://webmasters.googleblog.com/2017/01/what-crawl-budget-means-for-googlebot.html">crawl rate</a>. This doesn't affect sites that use responsive web design and dynamic serving, only sites where the mobile version is on a separate host, such as m.example.com.</li> </ul> We will be evaluating sites independently on their readiness for mobile-first indexing based on the above criteria and transitioning them when ready. This process has already started for a handful of sites and is closely being monitored by the search team.<br /> <br /> We continue to be cautious with rolling out mobile-first indexing. We believe taking this slowly will help webmasters get their sites ready for mobile users, and because of that, we currently don't have a timeline for when it's going to be completed. If you have any questions, drop by our <a href="https://support.google.com/webmasters/go/community">Webmaster forums</a> or our <a href="https://www.google.com/webmasters/connect/">public events</a>.<br /> <br /> Posted by <a href="https://twitter.com/methode">Gary</a><br /> <div> <br /></div> </div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> When we <a href="https://webmasters.googleblog.com/2016/11/mobile-first-indexing.html">announced</a> almost a year ago that we're experimenting with mobile-first indexing, we said we'd update publishers about our progress, something that we've done the past few months through public talks in <a href="https://www.youtube.com/user/GoogleWebmasterHelp/playlists?sort=dd&view=50&shelf_id=7">office hours on Hangouts on Air</a> and at conferences like <a href="https://www.google.com/search?q=mobile+first+indexing+pubcon">Pubcon</a>.<br /> <br /> To recap, currently our crawling, indexing, and ranking systems typically look at the desktop version of a page's content, which may cause issues for mobile searchers when that version is vastly different from the mobile version. Mobile-first indexing means that we'll use the mobile version of the content for indexing and ranking, to better help our – primarily mobile – users find what they're looking for. Webmasters will see significantly increased crawling by <a href="https://support.google.com/webmasters/answer/1061943">Smartphone Googlebot</a>, and the snippets in the results, as well as the content on the <a href="https://support.google.com/websearch/answer/1687222">Google cache pages</a>, will be from the mobile version of the pages.<br /> <br /> <a href="https://webmasters.googleblog.com/2016/11/mobile-first-indexing.html">As we said</a>, sites that make use of <a href="https://developers.google.com/search/mobile-sites/mobile-seo/responsive-design">responsive web design</a> and correctly implement <a href="https://developers.google.com/search/mobile-sites/mobile-seo/dynamic-serving">dynamic serving</a> (that include all of the desktop content and markup) generally don't have to do anything. Here are some extra tips that help ensure a site is ready for mobile-first indexing:<br /> <ul> <li>Make sure the mobile version of the site also has the important, high-quality content. This includes text, images (with alt-attributes), and videos - in the usual crawlable and indexable formats.</li> <li>Structured data is important for indexing and search features that users love: it should be both on the mobile and desktop version of the site. Ensure URLs within the structured data are updated to the mobile version on the mobile pages.</li> <li>Metadata should be present on both versions of the site. It provides hints about the content on a page for indexing and serving. For example, make sure that titles and meta descriptions are equivalent across both versions of all pages on the site.</li> <li>No changes are necessary for interlinking with separate mobile URLs (m.-dot sites). For <a href="https://developers.google.com/search/mobile-sites/mobile-seo/separate-urls">sites using separate mobile URLs</a>, keep the existing link rel=canonical and link rel=alternate elements between these versions.</li> <li>Check hreflang links on separate mobile URLs. When using <a href="https://support.google.com/webmasters/answer/189077">link rel=hreflang</a> elements for <a href="https://support.google.com/webmasters/answer/182192">internationalization</a>, link between mobile and desktop URLs separately. Your mobile URLs' hreflang should point to the other language/region versions on other mobile URLs, and similarly link desktop with other desktop URLs using hreflang link elements there.</li> <li>Ensure the servers hosting the site have enough capacity to handle potentially increased <a href="https://webmasters.googleblog.com/2017/01/what-crawl-budget-means-for-googlebot.html">crawl rate</a>. This doesn't affect sites that use responsive web design and dynamic serving, only sites where the mobile version is on a separate host, such as m.example.com.</li> </ul> We will be evaluating sites independently on their readiness for mobile-first indexing based on the above criteria and transitioning them when ready. This process has already started for a handful of sites and is closely being monitored by the search team.<br /> <br /> We continue to be cautious with rolling out mobile-first indexing. We believe taking this slowly will help webmasters get their sites ready for mobile users, and because of that, we currently don't have a timeline for when it's going to be completed. If you have any questions, drop by our <a href="https://support.google.com/webmasters/go/community">Webmaster forums</a> or our <a href="https://www.google.com/webmasters/connect/">public events</a>.<br /> <br /> Posted by <a href="https://twitter.com/methode">Gary</a><br /> <div> <br /></div> </div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Getting your site ready for mobile-first indexing&url=https://webmasters.googleblog.com/2017/12/getting-your-site-ready-for-mobile.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/12/getting-your-site-ready-for-mobile.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/12/getting-your-site-ready-for-mobile.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> </div> </div> </div> <div class='post' data-id='1390719792653442279' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/12/nohacked-30-tips-on-prevention.html?hl=en' itemprop='url' title='#NoHacked 3.0: Tips on prevention'> #NoHacked 3.0: Tips on prevention </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, December 14, 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"> Last week on <a href="https://twitter.com/googlewmc">#NoHacked</a>, we have shared on hack detection and the reasons why you might get hacked. This week we focus on prevention and here are some tips for you! <br /> <ul> <li><strong>Top ways websites get hacked by spammers: </strong> <div class="blgimg1"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEih1CFZkea9q2dMVly4gyNJ0gDkrMQdOnk_0ob2UgtNMQxwlbdQFn7S7WNN-2nSMAYcln8F2jB9k80f8HL1aHPQjfZm8LPFwTVmYKs8NWib5DtApRVBPhAHyeyeS1fyxoEUtvr4/s1600/image3.png" imageanchor="1"><img border="0" data-original-height="512" data-original-width="1024" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEih1CFZkea9q2dMVly4gyNJ0gDkrMQdOnk_0ob2UgtNMQxwlbdQFn7S7WNN-2nSMAYcln8F2jB9k80f8HL1aHPQjfZm8LPFwTVmYKs8NWib5DtApRVBPhAHyeyeS1fyxoEUtvr4/s1600/image3.png" /></a></div> <br /> Understanding how your site was compromised is an important part of protecting your site from attacks, here some<a href="https://developers.google.com/webmasters/hacked/docs/top_ways_websites_get_hacked_by_spammers"> top ways that sites get compromised by spammers</a>.</li> </ul> <ul style="text-align: left;"> <li><strong>Be mindful of your sources! Be very careful of a free premium theme/plugin! </strong> <div class="blgimg2"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjnRITFf133GuprzFK3S5iUECQwHNCoycsXbnEYj62UHETy09D4RodttggS77Hu7bV7bi9pPLAd0k18rBcv63r9kepP2CEq76W8EYUTxFXCO7fZ2USO-Xju8B0qdvh3G_MxzP3I/s1600/image1.png" imageanchor="1"><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjnRITFf133GuprzFK3S5iUECQwHNCoycsXbnEYj62UHETy09D4RodttggS77Hu7bV7bi9pPLAd0k18rBcv63r9kepP2CEq76W8EYUTxFXCO7fZ2USO-Xju8B0qdvh3G_MxzP3I/s1600/image1.png" /></a><br /> You probably have heard about free premium plugins! If you've ever stumbled upon a site offering you plugins you normally have to purchase for free, be very careful. Many hackers lure you in by copying a popular plugin and then add backdoors or malware that will allow them to access your site. Read more about a similar case on <a href="https://blog.sucuri.net/2015/05/fake-jquery-scripts-in-nulled-wordpress-pugins.html">the Sucuri blog</a>. Additionally, even legit good quality plugins and themes can become dangerous if :</div></li> <div><br /></div> <ul> <li>you do not update them as soon as a new version becomes available</li> <li>the developer of said theme or plugin does not update them, and they become old over time</li> </ul> </ul> <br /> <div> In any case, keeping all your site's software modern and updated is essential in keeping hackers out of your website. </div> <br /> <ul> <li><strong>Botnet in wordpress </strong> <div class="blgimg3"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh-rFI56Rw3TGHoATNbCjbzhMurQCvK5G_IUga1JKW_lgfmtbe8y2FTb4YGRSJV6aPqt3LrDaxH5wbQfqrf88PZf5-2s6Y1XVWd5nQef8_6dV1D-zRDAt8aKag2jy0yFbUKWRzf/s1600/image2.png" imageanchor="1"><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh-rFI56Rw3TGHoATNbCjbzhMurQCvK5G_IUga1JKW_lgfmtbe8y2FTb4YGRSJV6aPqt3LrDaxH5wbQfqrf88PZf5-2s6Y1XVWd5nQef8_6dV1D-zRDAt8aKag2jy0yFbUKWRzf/s1600/image2.png" /></a></div> <strong> </strong>A <a href="https://www.wordfence.com/blog/2016/08/hacking-wordpress-botnet/">botnet</a> is a cluster of machines, devices, or websites under the control of a third party often used to commit malicious acts, such as operating spam campaigns, clickbots, or DDoS. It's difficult to detect if your site has been infected by a botnet because there are often no specific changes to your site. However, your site's reputation, resources, and data are at risk if your site is in a botnet. Learn more about botnets, how to detect them, and how they can affect your site at <a href="https://www.bleepingcomputer.com/news/security/wordpress-and-joomla-sites-fuel-resurrected-spamtorte-botnet/">Botnet in wordpress and joomla article.</a></li> </ul> As usual if you have any questions post on <a href="https://productforums.google.com/forum/#!forum/webmasters">our Webmaster Help Forums</a> for help from the friendly community and see you next week! <br /> <style> .blgimg1 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; float: left; } .blgimg2 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; float: left; } .blgimg3 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; } .blgimg4 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; } </style></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"> Last week on <a href="https://twitter.com/googlewmc">#NoHacked</a>, we have shared on hack detection and the reasons why you might get hacked. This week we focus on prevention and here are some tips for you! <br /> <ul> <li><strong>Top ways websites get hacked by spammers: </strong> <div class="blgimg1"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEih1CFZkea9q2dMVly4gyNJ0gDkrMQdOnk_0ob2UgtNMQxwlbdQFn7S7WNN-2nSMAYcln8F2jB9k80f8HL1aHPQjfZm8LPFwTVmYKs8NWib5DtApRVBPhAHyeyeS1fyxoEUtvr4/s1600/image3.png" imageanchor="1"><img border="0" data-original-height="512" data-original-width="1024" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEih1CFZkea9q2dMVly4gyNJ0gDkrMQdOnk_0ob2UgtNMQxwlbdQFn7S7WNN-2nSMAYcln8F2jB9k80f8HL1aHPQjfZm8LPFwTVmYKs8NWib5DtApRVBPhAHyeyeS1fyxoEUtvr4/s1600/image3.png" /></a></div> <br /> Understanding how your site was compromised is an important part of protecting your site from attacks, here some<a href="https://developers.google.com/webmasters/hacked/docs/top_ways_websites_get_hacked_by_spammers"> top ways that sites get compromised by spammers</a>.</li> </ul> <ul style="text-align: left;"> <li><strong>Be mindful of your sources! Be very careful of a free premium theme/plugin! </strong> <div class="blgimg2"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjnRITFf133GuprzFK3S5iUECQwHNCoycsXbnEYj62UHETy09D4RodttggS77Hu7bV7bi9pPLAd0k18rBcv63r9kepP2CEq76W8EYUTxFXCO7fZ2USO-Xju8B0qdvh3G_MxzP3I/s1600/image1.png" imageanchor="1"><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjnRITFf133GuprzFK3S5iUECQwHNCoycsXbnEYj62UHETy09D4RodttggS77Hu7bV7bi9pPLAd0k18rBcv63r9kepP2CEq76W8EYUTxFXCO7fZ2USO-Xju8B0qdvh3G_MxzP3I/s1600/image1.png" /></a><br /> You probably have heard about free premium plugins! If you've ever stumbled upon a site offering you plugins you normally have to purchase for free, be very careful. Many hackers lure you in by copying a popular plugin and then add backdoors or malware that will allow them to access your site. Read more about a similar case on <a href="https://blog.sucuri.net/2015/05/fake-jquery-scripts-in-nulled-wordpress-pugins.html">the Sucuri blog</a>. Additionally, even legit good quality plugins and themes can become dangerous if :</div></li> <div><br /></div> <ul> <li>you do not update them as soon as a new version becomes available</li> <li>the developer of said theme or plugin does not update them, and they become old over time</li> </ul> </ul> <br /> <div> In any case, keeping all your site's software modern and updated is essential in keeping hackers out of your website. </div> <br /> <ul> <li><strong>Botnet in wordpress </strong> <div class="blgimg3"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh-rFI56Rw3TGHoATNbCjbzhMurQCvK5G_IUga1JKW_lgfmtbe8y2FTb4YGRSJV6aPqt3LrDaxH5wbQfqrf88PZf5-2s6Y1XVWd5nQef8_6dV1D-zRDAt8aKag2jy0yFbUKWRzf/s1600/image2.png" imageanchor="1"><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh-rFI56Rw3TGHoATNbCjbzhMurQCvK5G_IUga1JKW_lgfmtbe8y2FTb4YGRSJV6aPqt3LrDaxH5wbQfqrf88PZf5-2s6Y1XVWd5nQef8_6dV1D-zRDAt8aKag2jy0yFbUKWRzf/s1600/image2.png" /></a></div> <strong> </strong>A <a href="https://www.wordfence.com/blog/2016/08/hacking-wordpress-botnet/">botnet</a> is a cluster of machines, devices, or websites under the control of a third party often used to commit malicious acts, such as operating spam campaigns, clickbots, or DDoS. It's difficult to detect if your site has been infected by a botnet because there are often no specific changes to your site. However, your site's reputation, resources, and data are at risk if your site is in a botnet. Learn more about botnets, how to detect them, and how they can affect your site at <a href="https://www.bleepingcomputer.com/news/security/wordpress-and-joomla-sites-fuel-resurrected-spamtorte-botnet/">Botnet in wordpress and joomla article.</a></li> </ul> As usual if you have any questions post on <a href="https://productforums.google.com/forum/#!forum/webmasters">our Webmaster Help Forums</a> for help from the friendly community and see you next week! <br /> <style> .blgimg1 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; float: left; } .blgimg2 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; float: left; } .blgimg3 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; } .blgimg4 { width: 100%; padding: 0 0 -10px 0; margin: 0; border: 0; } </style></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:#NoHacked 3.0: Tips on prevention&url=https://webmasters.googleblog.com/2017/12/nohacked-30-tips-on-prevention.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/12/nohacked-30-tips-on-prevention.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/12/nohacked-30-tips-on-prevention.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> </div> </div> </div> <div class='post' data-id='3531415526232940036' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/12/a-revamped-seo-starter-guide_12.html?hl=en' itemprop='url' title='A revamped SEO Starter Guide'> A revamped SEO Starter Guide </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, December 12, 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"> There are lots of resources out there to create great websites. Website owners often ask Google what our recommended practices are to make sure great websites are search-engine-friendly. Traditionally, our resources for beginners were the SEO Starter Guide and the Webmaster Academy. To help webmasters create modern, search-engine-friendly websites, we’re announcing today the launch of a <a href="https://support.google.com/webmasters/answer/7451184" target="_blank">new, updated SEO Starter Guide</a>.<br /> <br /> The traditional SEO Starter Guide lists best practices that make it easier for search engines to crawl, index and understand content on websites. The Webmaster Academy has the information and tools to teach webmasters how to create a site and have it found in Google Search. Since these two resources have some overlapping purpose and content, and could be more exhaustive on some aspects of creating a user friendly and safe website, we’re deprecating the Webmaster Academy and removing the old SEO Starter Guide PDF. <br /> <br /> <span id="docs-internal-guid-effccfcd-4afa-d144-89cf-0ef404127765"><span style="font-family: Arial; font-size: 11pt; vertical-align: baseline; white-space: pre-wrap;"><img height="268" src="https://lh4.googleusercontent.com/WVEK8d4R05u6teqD0SSX_pF7KHf2B8vIO3XphQ_apzJbu8wgae9D8g9ObTU2Po0t4cqlAF5-hUeJ2owzgswUVq4zZuzlKTLep-FjUIKU-5cdZEakpmV5Nq9LflQM1IeTsWXYugOC" style="border: none; transform: rotate(0rad);" width="640" /></span></span><br /> <br /> The updated SEO Starter Guide will replace both the old Starter Guide and the Webmaster Academy. The updated version builds on top of the previously available document, and has additional sections on the need for search engine optimization, adding structured data markup and building mobile-friendly websites.<br /> This new Guide is available in nine languages (English, German, Spanish, French, Italian, Japanese, Portuguese, Russian and Turkish) starting today, and we’ll be adding sixteen more languages very soon.<br /> <br /> Go check out the new SEO Starter Guide, and let us know what you think about it.<br /> <br /> For any questions, feel free to drop by our <a href="https://support.google.com/webmasters/go/community" target="_blank">Webmaster Help Forums</a>!<br /> <br /> <span style="color: #666666;">Posted by Abhas Tripathi, Search Quality Strategist</span><br /> <div> <br /></div> </div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> There are lots of resources out there to create great websites. Website owners often ask Google what our recommended practices are to make sure great websites are search-engine-friendly. Traditionally, our resources for beginners were the SEO Starter Guide and the Webmaster Academy. To help webmasters create modern, search-engine-friendly websites, we’re announcing today the launch of a <a href="https://support.google.com/webmasters/answer/7451184" target="_blank">new, updated SEO Starter Guide</a>.<br /> <br /> The traditional SEO Starter Guide lists best practices that make it easier for search engines to crawl, index and understand content on websites. The Webmaster Academy has the information and tools to teach webmasters how to create a site and have it found in Google Search. Since these two resources have some overlapping purpose and content, and could be more exhaustive on some aspects of creating a user friendly and safe website, we’re deprecating the Webmaster Academy and removing the old SEO Starter Guide PDF. <br /> <br /> <span id="docs-internal-guid-effccfcd-4afa-d144-89cf-0ef404127765"><span style="font-family: Arial; font-size: 11pt; vertical-align: baseline; white-space: pre-wrap;"><img height="268" src="https://lh4.googleusercontent.com/WVEK8d4R05u6teqD0SSX_pF7KHf2B8vIO3XphQ_apzJbu8wgae9D8g9ObTU2Po0t4cqlAF5-hUeJ2owzgswUVq4zZuzlKTLep-FjUIKU-5cdZEakpmV5Nq9LflQM1IeTsWXYugOC" style="border: none; transform: rotate(0rad);" width="640" /></span></span><br /> <br /> The updated SEO Starter Guide will replace both the old Starter Guide and the Webmaster Academy. The updated version builds on top of the previously available document, and has additional sections on the need for search engine optimization, adding structured data markup and building mobile-friendly websites.<br /> This new Guide is available in nine languages (English, German, Spanish, French, Italian, Japanese, Portuguese, Russian and Turkish) starting today, and we’ll be adding sixteen more languages very soon.<br /> <br /> Go check out the new SEO Starter Guide, and let us know what you think about it.<br /> <br /> For any questions, feel free to drop by our <a href="https://support.google.com/webmasters/go/community" target="_blank">Webmaster Help Forums</a>!<br /> <br /> <span style="color: #666666;">Posted by Abhas Tripathi, Search Quality Strategist</span><br /> <div> <br /></div> </div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:A revamped SEO Starter Guide&url=https://webmasters.googleblog.com/2017/12/a-revamped-seo-starter-guide_12.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/12/a-revamped-seo-starter-guide_12.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/12/a-revamped-seo-starter-guide_12.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> </div> </div> </div> <div class='post' data-id='1787779924474569642' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/12/nohacked-30-how-do-i-know-if-my-site-is.html?hl=en' itemprop='url' title='#NoHacked 3.0: How do I know if my site is hacked?'> #NoHacked 3.0: How do I know if my site is hacked? </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Friday, December 08, 2017 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> Last week #NoHacked is back on our <a href="https://plus.google.com/+GoogleWebmasters">G+</a> and <a href="https://twitter.com/googlewmc">Twitter</a> channels! #NoHacked is our social campaign which aims to bring awareness about hacking attacks and offer tips on how to keep your sites safe from hackers. This time we would like to start sharing content from #NoHacked campaign on this blog in your local language! <div class="blgimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiBe5dfJM8kYXK5xfZZATTRlGHeW00I9XPdTMZ2095jlZvL8YNguI7x2UofqLuoBvtpI42nm9cUmO0dHL0iS6jP4uYtRfLhL3v6YKg-C9eQMN4sWjT2HCqMOnyS-v_mk4kq1WOr/s1600/image7.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiBe5dfJM8kYXK5xfZZATTRlGHeW00I9XPdTMZ2095jlZvL8YNguI7x2UofqLuoBvtpI42nm9cUmO0dHL0iS6jP4uYtRfLhL3v6YKg-C9eQMN4sWjT2HCqMOnyS-v_mk4kq1WOr/s1600/image7.png" /></a> </div> <p> Why do sites get hacked? Hackers have<a href="https://developers.google.com/webmasters/hacked/docs/FAQs_for_hacked_sites"> different motives for compromising a website</a>, and hack attacks can be very different, so they are not always easily detected. Here are some tips which will help you in detecting hacked sites! </p> <ul> <li> <strong>Getting started:</strong> <div class="blgimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjTkQJJgFocxmnNrlb5RjnxUsW8mhl6qmWTcn2nRbGvMDIIT2QDuZwaNquObyeCvZTSBY-A5o6fF9laVTcjnbQBQRfG4f8wc8t1f3xgIB8WegQM4tsFcm8keBJ_G3DnMHm2O8Cm/s1600/image6.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjTkQJJgFocxmnNrlb5RjnxUsW8mhl6qmWTcn2nRbGvMDIIT2QDuZwaNquObyeCvZTSBY-A5o6fF9laVTcjnbQBQRfG4f8wc8t1f3xgIB8WegQM4tsFcm8keBJ_G3DnMHm2O8Cm/s1600/image6.png" /></a> </div> <p> Start with our guide "How do I know if my site is hacked?" if you've received a security alert from Google or another party. <a href="https://developers.google.com/webmasters/hacked/docs/how_do_I_know_if_site_hacked">This guide</a> will walk you through basic steps to check for any signs of compromises on your site. </p> </li> <li> <strong>Understand the alert on Google Search: </strong> <div class="blgimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgDynKAdxyUySSQWPq7oFw7Lzwfz9xSv5F3QStSZ0ANT-AaCBpVGS28c7XK62reBX3PpnB04WuwKt57OZTwT9RdnfM_ETyaH2V2DcVXLcuTtbHq-Zb0GcL0l3zqmGDLGq495xVQ/s1600/image5.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgDynKAdxyUySSQWPq7oFw7Lzwfz9xSv5F3QStSZ0ANT-AaCBpVGS28c7XK62reBX3PpnB04WuwKt57OZTwT9RdnfM_ETyaH2V2DcVXLcuTtbHq-Zb0GcL0l3zqmGDLGq495xVQ/s1600/image5.png" /></a> </div> <p> At Google, we have different processes to deal with hacking scenarios. Scanning tools will often detect malware, but they can miss some spamming hacks. A clean verdict from Safe Browsing does not mean that you haven't been hacked to distribute spam. </p> <ul> <li>If you ever see <a href="https://support.google.com/websearch/answer/190597">"This site may be hacked",</a> your site may have been hacked to display spam. Essentially, your site has been hijacked to serve some free advertising.</li> <li>If you see<a href="https://support.google.com/websearch/answer/45449"> "This site may harm your computer"</a> beneath the site URL then we think the site you're about to visit might allow programs to install malicious software on your computer.</li> <li>If you see a big red screen before your site, that can mean a <a href="https://support.google.com/chrome/answer/99020">variety of things</a>: <ul> <li>If you see "The site ahead contains malware", Google has detected that your site distributes <a href="https://support.google.com/webmasters/answer/3258249?hl=en">malware</a>.</li> <li>If you see "The site ahead contains harmful programs", then the site has been flagged for distributing <a href="https://www.google.com/about/unwanted-software-policy.html">unwanted software</a>.</li> <li>"Deceptive site ahead" warnings indicate that your site may be serving <a href="https://support.google.com/webmasters/answer/6350487?hl=en">phishing or social engineering</a>. Your site could have been hacked to do any of these things.</li> </ul> </ul> </li> </li> <li> <strong>Malvertising vs Hack:</strong> <div class="blgimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiIjAFcAWg5iOIORXN6hn-KKIMXFY4Ut1DrHV4_IYRES6rYmuwgWWPO6fJaSwFNQ-F3veqg3XOkKquN6VBNtrgTbv-bS2Ks2dXwlKBHJh2BJYz5WADuhD1Phbq9LhQTjPmG5FN0/s1600/image3.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiIjAFcAWg5iOIORXN6hn-KKIMXFY4Ut1DrHV4_IYRES6rYmuwgWWPO6fJaSwFNQ-F3veqg3XOkKquN6VBNtrgTbv-bS2Ks2dXwlKBHJh2BJYz5WADuhD1Phbq9LhQTjPmG5FN0/s1600/image3.png" /></a> </div> <p> Malvertising happens when your site loads a bad ad. It may make it seem as though your site has been hacked, perhaps by redirecting your visitors, but in fact is just an ad behaving badly. </p> </li> <li> <strong>Open redirects: check if your site is enabling open redirects</strong> <div class="blgimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLBMp47kjEO_KXpVwjckjPbC4VrYaBwP6GFTtnmHljxXUOINe7BeUkN7cyCDNdkIxILA-SKWmiRQ7S7uui9zUvzG5QcIbQBAxLCyLEsiSW2Uulqr51HjjkKd5WO-QsSU4uR-lN/s1600/image1.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLBMp47kjEO_KXpVwjckjPbC4VrYaBwP6GFTtnmHljxXUOINe7BeUkN7cyCDNdkIxILA-SKWmiRQ7S7uui9zUvzG5QcIbQBAxLCyLEsiSW2Uulqr51HjjkKd5WO-QsSU4uR-lN/s1600/image1.png" /></a> </div> <p> Hackers might want to take advantage of a good site to mask their URLs. One way they do this is by using open redirects, which allow them to use your site to redirect users to any URL of their choice. You can <a href="https://www.owasp.org/index.php/Unvalidated_Redirects_and_Forwards_Cheat_Sheet">read more here</a>! </p> </li> <li> <strong>Mobile check: make sure to view your site from a mobile browser in incognito mode. Check for bad mobile ad networks.</strong> <div class="blgimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhTYtwnwB1kMv8VHUeLs58ZIthzzBkHejPbM5MD5hXS_MF1h71sBOoU8asJ_fnoHzaZ7cQEqHxvCY43BroEPNaU5xft4JBpbcAPsUDE73gQybUqNqmaSCAAlYjCPzAJJP-7mq-X/s1600/image2.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhTYtwnwB1kMv8VHUeLs58ZIthzzBkHejPbM5MD5hXS_MF1h71sBOoU8asJ_fnoHzaZ7cQEqHxvCY43BroEPNaU5xft4JBpbcAPsUDE73gQybUqNqmaSCAAlYjCPzAJJP-7mq-X/s1600/image2.png" /></a> </div> <p> Sometimes bad content like ads or other third-party elements <a href="https://support.google.com/webmasters/answer/6388720?hl=en">unknowingly redirect mobile users</a>. This behavior can easily escape detection because it's only visible from certain browsers. Be sure to check that the mobile and desktop versions of your site show the same content. </p> </li> <li> <strong>Use Search Console and get message:</strong> <div class="blgimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhZTuOzHlS95ks73E_XAHKJfrv0Aqz6ATqHhXYpWX791IRik5oUaQZqE09QWvTKL_NGcp7Q1nwXB1HOkJ_EEPQqiLL0yld3gfipzLrXVkakEHkze1_neuRsZ3_urFEUi6z6OIQi/s1600/image4.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhZTuOzHlS95ks73E_XAHKJfrv0Aqz6ATqHhXYpWX791IRik5oUaQZqE09QWvTKL_NGcp7Q1nwXB1HOkJ_EEPQqiLL0yld3gfipzLrXVkakEHkze1_neuRsZ3_urFEUi6z6OIQi/s1600/image4.png" /></a> </div> <p> Search Console is a tool that Google uses to communicate with you about your website. It also includes many other tools that can help you improve and manage your website. Make sure you have your site <a href="https://support.google.com/webmasters/answer/35179?hl=en">verified in Search Console</a> even if you aren't a primary developer on your site. The alerts and messages in Search Console will let you know if Google has detected any critical errors on your site. </p> </li> </ul> <p> If you're still unable to find any signs of a hack, ask a security expert or post on <a href="https://productforums.google.com/forum/#!forum/webmasters">our Webmaster Help Forums</a> for a second look. </p> <p> The #NoHacked campaign will run for the next 3 weeks. Follow us on our <a href="https://plus.google.com/+GoogleWebmasters">G+</a> and <a href="https://twitter.com/googlewmc">Twitter</a> channels or look out for the content in this blog as we will be posting summary for each week right here at the beginning of each week! Stay safe meanwhile! </p> <style> .blgimg img { width: 100%; border: 0; margin: 0; padding: 10px 0 0 0; } </style> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> Last week #NoHacked is back on our <a href="https://plus.google.com/+GoogleWebmasters">G+</a> and <a href="https://twitter.com/googlewmc">Twitter</a> channels! #NoHacked is our social campaign which aims to bring awareness about hacking attacks and offer tips on how to keep your sites safe from hackers. This time we would like to start sharing content from #NoHacked campaign on this blog in your local language! <div class="blgimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiBe5dfJM8kYXK5xfZZATTRlGHeW00I9XPdTMZ2095jlZvL8YNguI7x2UofqLuoBvtpI42nm9cUmO0dHL0iS6jP4uYtRfLhL3v6YKg-C9eQMN4sWjT2HCqMOnyS-v_mk4kq1WOr/s1600/image7.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiBe5dfJM8kYXK5xfZZATTRlGHeW00I9XPdTMZ2095jlZvL8YNguI7x2UofqLuoBvtpI42nm9cUmO0dHL0iS6jP4uYtRfLhL3v6YKg-C9eQMN4sWjT2HCqMOnyS-v_mk4kq1WOr/s1600/image7.png" /></a> </div> <p> Why do sites get hacked? Hackers have<a href="https://developers.google.com/webmasters/hacked/docs/FAQs_for_hacked_sites"> different motives for compromising a website</a>, and hack attacks can be very different, so they are not always easily detected. Here are some tips which will help you in detecting hacked sites! </p> <ul> <li> <strong>Getting started:</strong> <div class="blgimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjTkQJJgFocxmnNrlb5RjnxUsW8mhl6qmWTcn2nRbGvMDIIT2QDuZwaNquObyeCvZTSBY-A5o6fF9laVTcjnbQBQRfG4f8wc8t1f3xgIB8WegQM4tsFcm8keBJ_G3DnMHm2O8Cm/s1600/image6.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjTkQJJgFocxmnNrlb5RjnxUsW8mhl6qmWTcn2nRbGvMDIIT2QDuZwaNquObyeCvZTSBY-A5o6fF9laVTcjnbQBQRfG4f8wc8t1f3xgIB8WegQM4tsFcm8keBJ_G3DnMHm2O8Cm/s1600/image6.png" /></a> </div> <p> Start with our guide "How do I know if my site is hacked?" if you've received a security alert from Google or another party. <a href="https://developers.google.com/webmasters/hacked/docs/how_do_I_know_if_site_hacked">This guide</a> will walk you through basic steps to check for any signs of compromises on your site. </p> </li> <li> <strong>Understand the alert on Google Search: </strong> <div class="blgimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgDynKAdxyUySSQWPq7oFw7Lzwfz9xSv5F3QStSZ0ANT-AaCBpVGS28c7XK62reBX3PpnB04WuwKt57OZTwT9RdnfM_ETyaH2V2DcVXLcuTtbHq-Zb0GcL0l3zqmGDLGq495xVQ/s1600/image5.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgDynKAdxyUySSQWPq7oFw7Lzwfz9xSv5F3QStSZ0ANT-AaCBpVGS28c7XK62reBX3PpnB04WuwKt57OZTwT9RdnfM_ETyaH2V2DcVXLcuTtbHq-Zb0GcL0l3zqmGDLGq495xVQ/s1600/image5.png" /></a> </div> <p> At Google, we have different processes to deal with hacking scenarios. Scanning tools will often detect malware, but they can miss some spamming hacks. A clean verdict from Safe Browsing does not mean that you haven't been hacked to distribute spam. </p> <ul> <li>If you ever see <a href="https://support.google.com/websearch/answer/190597">"This site may be hacked",</a> your site may have been hacked to display spam. Essentially, your site has been hijacked to serve some free advertising.</li> <li>If you see<a href="https://support.google.com/websearch/answer/45449"> "This site may harm your computer"</a> beneath the site URL then we think the site you're about to visit might allow programs to install malicious software on your computer.</li> <li>If you see a big red screen before your site, that can mean a <a href="https://support.google.com/chrome/answer/99020">variety of things</a>: <ul> <li>If you see "The site ahead contains malware", Google has detected that your site distributes <a href="https://support.google.com/webmasters/answer/3258249?hl=en">malware</a>.</li> <li>If you see "The site ahead contains harmful programs", then the site has been flagged for distributing <a href="https://www.google.com/about/unwanted-software-policy.html">unwanted software</a>.</li> <li>"Deceptive site ahead" warnings indicate that your site may be serving <a href="https://support.google.com/webmasters/answer/6350487?hl=en">phishing or social engineering</a>. Your site could have been hacked to do any of these things.</li> </ul> </ul> </li> </li> <li> <strong>Malvertising vs Hack:</strong> <div class="blgimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiIjAFcAWg5iOIORXN6hn-KKIMXFY4Ut1DrHV4_IYRES6rYmuwgWWPO6fJaSwFNQ-F3veqg3XOkKquN6VBNtrgTbv-bS2Ks2dXwlKBHJh2BJYz5WADuhD1Phbq9LhQTjPmG5FN0/s1600/image3.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiIjAFcAWg5iOIORXN6hn-KKIMXFY4Ut1DrHV4_IYRES6rYmuwgWWPO6fJaSwFNQ-F3veqg3XOkKquN6VBNtrgTbv-bS2Ks2dXwlKBHJh2BJYz5WADuhD1Phbq9LhQTjPmG5FN0/s1600/image3.png" /></a> </div> <p> Malvertising happens when your site loads a bad ad. It may make it seem as though your site has been hacked, perhaps by redirecting your visitors, but in fact is just an ad behaving badly. </p> </li> <li> <strong>Open redirects: check if your site is enabling open redirects</strong> <div class="blgimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLBMp47kjEO_KXpVwjckjPbC4VrYaBwP6GFTtnmHljxXUOINe7BeUkN7cyCDNdkIxILA-SKWmiRQ7S7uui9zUvzG5QcIbQBAxLCyLEsiSW2Uulqr51HjjkKd5WO-QsSU4uR-lN/s1600/image1.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLBMp47kjEO_KXpVwjckjPbC4VrYaBwP6GFTtnmHljxXUOINe7BeUkN7cyCDNdkIxILA-SKWmiRQ7S7uui9zUvzG5QcIbQBAxLCyLEsiSW2Uulqr51HjjkKd5WO-QsSU4uR-lN/s1600/image1.png" /></a> </div> <p> Hackers might want to take advantage of a good site to mask their URLs. One way they do this is by using open redirects, which allow them to use your site to redirect users to any URL of their choice. You can <a href="https://www.owasp.org/index.php/Unvalidated_Redirects_and_Forwards_Cheat_Sheet">read more here</a>! </p> </li> <li> <strong>Mobile check: make sure to view your site from a mobile browser in incognito mode. Check for bad mobile ad networks.</strong> <div class="blgimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhTYtwnwB1kMv8VHUeLs58ZIthzzBkHejPbM5MD5hXS_MF1h71sBOoU8asJ_fnoHzaZ7cQEqHxvCY43BroEPNaU5xft4JBpbcAPsUDE73gQybUqNqmaSCAAlYjCPzAJJP-7mq-X/s1600/image2.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhTYtwnwB1kMv8VHUeLs58ZIthzzBkHejPbM5MD5hXS_MF1h71sBOoU8asJ_fnoHzaZ7cQEqHxvCY43BroEPNaU5xft4JBpbcAPsUDE73gQybUqNqmaSCAAlYjCPzAJJP-7mq-X/s1600/image2.png" /></a> </div> <p> Sometimes bad content like ads or other third-party elements <a href="https://support.google.com/webmasters/answer/6388720?hl=en">unknowingly redirect mobile users</a>. This behavior can easily escape detection because it's only visible from certain browsers. Be sure to check that the mobile and desktop versions of your site show the same content. </p> </li> <li> <strong>Use Search Console and get message:</strong> <div class="blgimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhZTuOzHlS95ks73E_XAHKJfrv0Aqz6ATqHhXYpWX791IRik5oUaQZqE09QWvTKL_NGcp7Q1nwXB1HOkJ_EEPQqiLL0yld3gfipzLrXVkakEHkze1_neuRsZ3_urFEUi6z6OIQi/s1600/image4.png" imageanchor="1" ><img border="0" data-original-height="513" data-original-width="1025" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhZTuOzHlS95ks73E_XAHKJfrv0Aqz6ATqHhXYpWX791IRik5oUaQZqE09QWvTKL_NGcp7Q1nwXB1HOkJ_EEPQqiLL0yld3gfipzLrXVkakEHkze1_neuRsZ3_urFEUi6z6OIQi/s1600/image4.png" /></a> </div> <p> Search Console is a tool that Google uses to communicate with you about your website. It also includes many other tools that can help you improve and manage your website. Make sure you have your site <a href="https://support.google.com/webmasters/answer/35179?hl=en">verified in Search Console</a> even if you aren't a primary developer on your site. The alerts and messages in Search Console will let you know if Google has detected any critical errors on your site. </p> </li> </ul> <p> If you're still unable to find any signs of a hack, ask a security expert or post on <a href="https://productforums.google.com/forum/#!forum/webmasters">our Webmaster Help Forums</a> for a second look. </p> <p> The #NoHacked campaign will run for the next 3 weeks. Follow us on our <a href="https://plus.google.com/+GoogleWebmasters">G+</a> and <a href="https://twitter.com/googlewmc">Twitter</a> channels or look out for the content in this blog as we will be posting summary for each week right here at the beginning of each week! Stay safe meanwhile! </p> <style> .blgimg img { width: 100%; border: 0; margin: 0; padding: 10px 0 0 0; } </style> <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:#NoHacked 3.0: How do I know if my site is hacked?&url=https://webmasters.googleblog.com/2017/12/nohacked-30-how-do-i-know-if-my-site-is.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/12/nohacked-30-how-do-i-know-if-my-site-is.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/12/nohacked-30-how-do-i-know-if-my-site-is.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/hacked%20sites?hl=en' rel='tag'> hacked sites </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/nohacked?hl=en' rel='tag'> nohacked </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=en' 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'> Monday, December 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=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/12/rendering-ajax-crawling-pages.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/12/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'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/rendering?hl=en' rel='tag'> rendering </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en' 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=en' 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'> Monday, November 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=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/11/a-reminder-about-event-markup.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/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'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/rich%20cards?hl=en' rel='tag'> rich cards </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/rich%20results?hl=en' rel='tag'> rich results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=en' rel='tag'> structured data </a> </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=en' 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'> Thursday, November 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=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/11/engaging-users-through-high-quality-amp.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/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'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/AMP?hl=en' rel='tag'> AMP </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/general%20tips?hl=en' rel='tag'> general tips </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en' 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=en' 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'> Wednesday, November 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=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/11/make-your-sites-complete-jobs.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/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'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/products%20and%20services?hl=en' rel='tag'> products and services </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=en' rel='tag'> structured data </a> </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=en' 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'> Sunday, October 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=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/10/enabling-more-high-quality-content.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/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'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=en' rel='tag'> structured data </a> </span> </div> </div> </div> <div class='post' data-id='4330928010124212244' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/09/how-to-move-from-m-dot-urls-to.html?hl=en' itemprop='url' title='How to move from m-dot URLs to responsive site'> How to move from m-dot URLs to responsive site </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, September 14, 2017 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p> With more sites moving towards responsive web design, many webmasters have questions about migrating from <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/separate-urls">separate mobile URLs</a>, also frequently known as "m-dot URLs", to using <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/responsive-design?mp-r-id=hc3bEy4=">responsive web design</a>. Here are some recommendations on how to move from separate urls to one responsive URL in a way that gives your sites the best chance of performing well on Google's search results. </p> <h3>Moving to responsive sites in a Googlebot-friendly way</h3> <p> Once you have your responsive site ready, moving is something you can definitely do with just a bit of forethought. Considering your URLs stay the same for desktop version, all you have to do is to configure 301 redirects from the mobile URLs to the responsive web URLs. </p> <p> Here are the detailed steps: </p> <ol> <li>Get your responsive site ready <div class="blogimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiJLuz0xgXDvhzg6iqBeg8FbhCwOl9UWh2brZdSdpK-hdIxGHzNVbSWui0-I3nF741bB_sRoVSEbhfxZqCBaOeJw_0kQiufgfLvI85mWPVuwQL6Bvqmvm3hQIQ0-TLtn56ygDZN/s1600/image2.png" imageanchor="1" ><img border="0" data-original-height="1019" data-original-width="1600" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiJLuz0xgXDvhzg6iqBeg8FbhCwOl9UWh2brZdSdpK-hdIxGHzNVbSWui0-I3nF741bB_sRoVSEbhfxZqCBaOeJw_0kQiufgfLvI85mWPVuwQL6Bvqmvm3hQIQ0-TLtn56ygDZN/s1600/image2.png" /> </a> </div> </li> <li>Configure 301 redirects on the old mobile URLs to point to the responsive versions (the new pages). These redirects need to be done on a per-URL basis, individually from each mobile URLs to the responsive URLs.</li> <div class="blogimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjCfLMAXsp7uEvqa4hV_j2lBpqJ7m_Pdf-eqrYhU1D-xtvbnPtCndb_v3lI_IE1g3hvFrfz2O-VTrU86DUYa3Xj-yE5oKTFzffY9bWRwJqsTHyV2N1KPy1sh04cltpvLtu8KgqV/s1600/image1.png" imageanchor="1" ><img border="0" data-original-height="385" data-original-width="604" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjCfLMAXsp7uEvqa4hV_j2lBpqJ7m_Pdf-eqrYhU1D-xtvbnPtCndb_v3lI_IE1g3hvFrfz2O-VTrU86DUYa3Xj-yE5oKTFzffY9bWRwJqsTHyV2N1KPy1sh04cltpvLtu8KgqV/s1600/image1.png" /></a> </div> <li>Remove any mobile-URL specific configuration your site might have, such as conditional redirects or a vary HTTP header. <li>As a good practice, <a href="https://support.google.com/webmasters/answer/139066?hl=en">setup rel=canonical </a>on the responsive URLs pointing to themselves (self-referential canonicals).</li> </ol> <p> If you're currently using dynamic serving and want to move to responsive design, you don't need to add or change any redirects. </p> <h3>Some benefits for moving to responsive web design</h3> <p> Moving to a responsive site should make maintenance and reporting much easier for you down the road. Aside from no longer needing to manage separate URLs for all pages, it will also make it much easier to adopt practices and technologies such as hreflang for internationalization, AMP for speed, structured data for advanced search features and more. </p> <p> As always, if you need more help you can ask a question in our <a href="http://productforums.google.com/d/forum/webmasters">webmaster forum</a>. </p> <span class="byline-author">Posted by Cherry Prommawin, Webmaster Relations</span> <style> .blogimg img { width: 100%; border: 0; margin: 0; padding: 10px 0 10px 0; } </style> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p> With more sites moving towards responsive web design, many webmasters have questions about migrating from <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/separate-urls">separate mobile URLs</a>, also frequently known as "m-dot URLs", to using <a href="https://developers.google.com/webmasters/mobile-sites/mobile-seo/responsive-design?mp-r-id=hc3bEy4=">responsive web design</a>. Here are some recommendations on how to move from separate urls to one responsive URL in a way that gives your sites the best chance of performing well on Google's search results. </p> <h3>Moving to responsive sites in a Googlebot-friendly way</h3> <p> Once you have your responsive site ready, moving is something you can definitely do with just a bit of forethought. Considering your URLs stay the same for desktop version, all you have to do is to configure 301 redirects from the mobile URLs to the responsive web URLs. </p> <p> Here are the detailed steps: </p> <ol> <li>Get your responsive site ready <div class="blogimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiJLuz0xgXDvhzg6iqBeg8FbhCwOl9UWh2brZdSdpK-hdIxGHzNVbSWui0-I3nF741bB_sRoVSEbhfxZqCBaOeJw_0kQiufgfLvI85mWPVuwQL6Bvqmvm3hQIQ0-TLtn56ygDZN/s1600/image2.png" imageanchor="1" ><img border="0" data-original-height="1019" data-original-width="1600" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiJLuz0xgXDvhzg6iqBeg8FbhCwOl9UWh2brZdSdpK-hdIxGHzNVbSWui0-I3nF741bB_sRoVSEbhfxZqCBaOeJw_0kQiufgfLvI85mWPVuwQL6Bvqmvm3hQIQ0-TLtn56ygDZN/s1600/image2.png" /> </a> </div> </li> <li>Configure 301 redirects on the old mobile URLs to point to the responsive versions (the new pages). These redirects need to be done on a per-URL basis, individually from each mobile URLs to the responsive URLs.</li> <div class="blogimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjCfLMAXsp7uEvqa4hV_j2lBpqJ7m_Pdf-eqrYhU1D-xtvbnPtCndb_v3lI_IE1g3hvFrfz2O-VTrU86DUYa3Xj-yE5oKTFzffY9bWRwJqsTHyV2N1KPy1sh04cltpvLtu8KgqV/s1600/image1.png" imageanchor="1" ><img border="0" data-original-height="385" data-original-width="604" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjCfLMAXsp7uEvqa4hV_j2lBpqJ7m_Pdf-eqrYhU1D-xtvbnPtCndb_v3lI_IE1g3hvFrfz2O-VTrU86DUYa3Xj-yE5oKTFzffY9bWRwJqsTHyV2N1KPy1sh04cltpvLtu8KgqV/s1600/image1.png" /></a> </div> <li>Remove any mobile-URL specific configuration your site might have, such as conditional redirects or a vary HTTP header. <li>As a good practice, <a href="https://support.google.com/webmasters/answer/139066?hl=en">setup rel=canonical </a>on the responsive URLs pointing to themselves (self-referential canonicals).</li> </ol> <p> If you're currently using dynamic serving and want to move to responsive design, you don't need to add or change any redirects. </p> <h3>Some benefits for moving to responsive web design</h3> <p> Moving to a responsive site should make maintenance and reporting much easier for you down the road. Aside from no longer needing to manage separate URLs for all pages, it will also make it much easier to adopt practices and technologies such as hreflang for internationalization, AMP for speed, structured data for advanced search features and more. </p> <p> As always, if you need more help you can ask a question in our <a href="http://productforums.google.com/d/forum/webmasters">webmaster forum</a>. </p> <span class="byline-author">Posted by Cherry Prommawin, Webmaster Relations</span> <style> .blogimg img { width: 100%; border: 0; margin: 0; padding: 10px 0 10px 0; } </style> <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 move from m-dot URLs to responsive site&url=https://webmasters.googleblog.com/2017/09/how-to-move-from-m-dot-urls-to.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/09/how-to-move-from-m-dot-urls-to.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/09/how-to-move-from-m-dot-urls-to.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/mobile?hl=en' rel='tag'> mobile </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/Responsive%20Web%20Design?hl=en' rel='tag'> Responsive Web Design </a> </span> </div> </div> </div> <div class='post' data-id='792099309282141236' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/08/introducing-our-new-international.html?hl=en' itemprop='url' title='Introducing Our New International Webmaster Blogs!'> Introducing Our New International Webmaster Blogs! </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, August 23, 2017 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div class="blogimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhcQpSFlLsD9cMe9-Y2gxIYrO0qnTuDlb1JIgMSeUPhiQFqS7u1pe1bSaXuZ_40SIxaAX7CObZqXW6fmbtuOAa-JKfq38vUVgv6Y0HaNsUtkYTDoILlSC3JetVDHLtsalJ_Yr1E/s1600/image1.png" imageanchor="1" ><img border="0" data-original-height="501" data-original-width="1400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhcQpSFlLsD9cMe9-Y2gxIYrO0qnTuDlb1JIgMSeUPhiQFqS7u1pe1bSaXuZ_40SIxaAX7CObZqXW6fmbtuOAa-JKfq38vUVgv6Y0HaNsUtkYTDoILlSC3JetVDHLtsalJ_Yr1E/s1600/image1.png" /></a> </div> <p> Join us in <strong>welcoming</strong> the latest additions to the Webmasters community: </p> <p> <strong>नमस्ते</strong> <a href="https://webmaster-hi.googleblog.com/2017/08/blog-post.html">Webmasters in Hindi</a>! </p> <p> <strong>Добро Пожаловать</strong> <a href="https://webmaster-ru.googleblog.com/2017/08/blog-post.html">Webmasters in Russian</a>! </p> <p> <strong>Hoşgeldiniz</strong> <a href="https://webmaster-tr.googleblog.com/2017/08/turkce-webmaster-bloguna-hosgeldiniz.html">Webmasters in Turkish</a>! </p> <p> <strong>สวัสดีค่ะ</strong> <a href="https://webmaster-th.googleblog.com/">Webmasters in Thai</a>! </p> <p> <strong>xin chào</strong> <a href="https://webmaster-vi.googleblog.com/">Webmasters in Vietnamese</a>! </p> <p> We will be sharing webmaster-related updates in our current and new blogs to make sure you have a place to follow the latest launches, updates and changes in Search in your languages! We will share links to relevant Help resources, educational content and events as they become available. </p> <p> Just a reminder, here are some of the resources that we have available in multiple languages: </p><ul> <li><a href="https://www.google.com/webmasters/">Google.com/webmasters</a> - documentation, support channels, tools (including a link to <a href="https://www.google.com/webmasters/tools/home?hl=en">Search Console</a>) and learning materials. <li><a href="https://support.google.com/webmasters/?hl=en#topic=3309469">Help Center</a> - tips and tutorials on using Search Console, answers to frequently asked questions and step-by-step guides. <li><a href="https://productforums.google.com/forum/#!forum/webmasters">Help forum</a> - ask your questions and get advice from the Webmaster community <li><a href="https://www.youtube.com/user/GoogleWebmasterHelp">YouTube Channel</a> - recordings of Hangouts on Air in different languages are on our <li><a href="https://plus.google.com/+GoogleWebmasters">G+ community</a> - another place we announce and share our Hangouts On Air </li></ul> <p> Testing tools: </p><ul> <li><a href="https://developers.google.com/speed/pagespeed/insights/">PageSpeed insights</a> - actionable insights on how to increase your site's performance <li><a href="https://search.google.com/test/mobile-friendly">Mobile-Friendly test</a> - identify areas where you can improve your site's performance on Mobile devices <li><a href="https://search.google.com/structured-data/testing-tool">Structure Data testing tool</a> - preview and test your Structured Data markup</li></ul> <p> Some other valuable resources (English-only): </p><ul> <li><a href="https://developers.google.com/search/">Developer documentation on Search</a> - a great resource where you can find feature guides, code labs, videos and links to more useful tools for webmasters. </li></ul> <p> If you have webmaster-specific questions, check our <a href="https://www.google.com/webmasters/connect/">event calendar</a> for the next hangout session or live event! Alternatively, you can post your questions to one of the local help forum, where our talented Product Experts from the <a href="https://topcontributor.withgoogle.com/">TC program</a> will try to answer your questions. Our Experts are product enthusiasts who have earned the distinction of "Top Contributor," or "Rising Star," by sharing their knowledge on the Google Help Forums. </p> <p> If you have suggestions, please let us know in the comments below. We look forward to working with you in your language! </p> <style> .blogimg img { width: 100%; border: 0; margin: 0; padding: 0 0 10px 0; } </style> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div class="blogimg"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhcQpSFlLsD9cMe9-Y2gxIYrO0qnTuDlb1JIgMSeUPhiQFqS7u1pe1bSaXuZ_40SIxaAX7CObZqXW6fmbtuOAa-JKfq38vUVgv6Y0HaNsUtkYTDoILlSC3JetVDHLtsalJ_Yr1E/s1600/image1.png" imageanchor="1" ><img border="0" data-original-height="501" data-original-width="1400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhcQpSFlLsD9cMe9-Y2gxIYrO0qnTuDlb1JIgMSeUPhiQFqS7u1pe1bSaXuZ_40SIxaAX7CObZqXW6fmbtuOAa-JKfq38vUVgv6Y0HaNsUtkYTDoILlSC3JetVDHLtsalJ_Yr1E/s1600/image1.png" /></a> </div> <p> Join us in <strong>welcoming</strong> the latest additions to the Webmasters community: </p> <p> <strong>नमस्ते</strong> <a href="https://webmaster-hi.googleblog.com/2017/08/blog-post.html">Webmasters in Hindi</a>! </p> <p> <strong>Добро Пожаловать</strong> <a href="https://webmaster-ru.googleblog.com/2017/08/blog-post.html">Webmasters in Russian</a>! </p> <p> <strong>Hoşgeldiniz</strong> <a href="https://webmaster-tr.googleblog.com/2017/08/turkce-webmaster-bloguna-hosgeldiniz.html">Webmasters in Turkish</a>! </p> <p> <strong>สวัสดีค่ะ</strong> <a href="https://webmaster-th.googleblog.com/">Webmasters in Thai</a>! </p> <p> <strong>xin chào</strong> <a href="https://webmaster-vi.googleblog.com/">Webmasters in Vietnamese</a>! </p> <p> We will be sharing webmaster-related updates in our current and new blogs to make sure you have a place to follow the latest launches, updates and changes in Search in your languages! We will share links to relevant Help resources, educational content and events as they become available. </p> <p> Just a reminder, here are some of the resources that we have available in multiple languages: </p><ul> <li><a href="https://www.google.com/webmasters/">Google.com/webmasters</a> - documentation, support channels, tools (including a link to <a href="https://www.google.com/webmasters/tools/home?hl=en">Search Console</a>) and learning materials. <li><a href="https://support.google.com/webmasters/?hl=en#topic=3309469">Help Center</a> - tips and tutorials on using Search Console, answers to frequently asked questions and step-by-step guides. <li><a href="https://productforums.google.com/forum/#!forum/webmasters">Help forum</a> - ask your questions and get advice from the Webmaster community <li><a href="https://www.youtube.com/user/GoogleWebmasterHelp">YouTube Channel</a> - recordings of Hangouts on Air in different languages are on our <li><a href="https://plus.google.com/+GoogleWebmasters">G+ community</a> - another place we announce and share our Hangouts On Air </li></ul> <p> Testing tools: </p><ul> <li><a href="https://developers.google.com/speed/pagespeed/insights/">PageSpeed insights</a> - actionable insights on how to increase your site's performance <li><a href="https://search.google.com/test/mobile-friendly">Mobile-Friendly test</a> - identify areas where you can improve your site's performance on Mobile devices <li><a href="https://search.google.com/structured-data/testing-tool">Structure Data testing tool</a> - preview and test your Structured Data markup</li></ul> <p> Some other valuable resources (English-only): </p><ul> <li><a href="https://developers.google.com/search/">Developer documentation on Search</a> - a great resource where you can find feature guides, code labs, videos and links to more useful tools for webmasters. </li></ul> <p> If you have webmaster-specific questions, check our <a href="https://www.google.com/webmasters/connect/">event calendar</a> for the next hangout session or live event! Alternatively, you can post your questions to one of the local help forum, where our talented Product Experts from the <a href="https://topcontributor.withgoogle.com/">TC program</a> will try to answer your questions. Our Experts are product enthusiasts who have earned the distinction of "Top Contributor," or "Rising Star," by sharing their knowledge on the Google Help Forums. </p> <p> If you have suggestions, please let us know in the comments below. We look forward to working with you in your language! </p> <style> .blogimg img { width: 100%; border: 0; margin: 0; padding: 0 0 10px 0; } </style> <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 Our New International Webmaster Blogs!&url=https://webmasters.googleblog.com/2017/08/introducing-our-new-international.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/08/introducing-our-new-international.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/08/introducing-our-new-international.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en' rel='tag'> webmaster community </a> </span> </div> </div> </div> <div class='post' data-id='3949086383067022203' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/08/a-sneak-peek-at-two-experimental.html?hl=en' itemprop='url' title='The new Search Console: a sneak peek at two experimental features'> The new Search Console: a sneak peek at two experimental features </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, August 01, 2017 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> Search Console was <a href="http://sitemaps.blogspot.ch/2005/11/more-stats.html">initially launched</a> with just four reports more than a decade ago. Today, the product includes more than two dozen reports and tools covering AMP, structured data, and live testing tools, all designed to help improve your site's performance on Google Search.<br /> Now we have decided to embark on an extensive redesign to better serve you, our users. Our hope is that this redesign will provide you with:<br /> <ul> <li><strong>More actionable insights</strong> - We will now group the identified issues by what we suspect is the common “root-cause” to help you find where you should fix your code. We organize these issues into tasks that have a state (similar to bug tracking systems) so you can easily see whether the issue is still open, whether Google has detected your fix, and track the progress of re-processing the affected pages. </li> <li><strong>Better support of your organizational workflow</strong> - As we talked to many organizations, we’ve learned that multiple people are typically involved in implementing, diagnosing, and fixing issues. This is why we are introducing sharing functionality that allows you to pick-up an action item and share it with other people in your group, like developers who will get references to the code in question.</li> <li><strong>Faster feedback loops between you and Google</strong> - We’ve built a mechanism to allow you to iterate quickly on your fixes, and not waste time waiting for Google to recrawl your site, only to tell you later that it’s not fixed yet. Rather, we’ll provide on-the-spot testing of fixes and are automatically speeding up crawling once we see things are ok. Similarly, the testing tools will include code snippets and a search preview - so you can quickly see where your issues are, confirm you've fixed them, and see how the pages will look on Search.</li> </ul> </div> In the next few weeks, we're releasing two exciting BETA features from the new Search Console to a small set of users — Index Coverage report and AMP fixing flow.<br /> <h3></h3> The new Index Coverage report shows the count of indexed pages, information about why some pages could not be indexed, along with example pages and tips on how to fix indexing issues. It also enables a simple sitemap submission flow, and the capability to filter all Index Coverage data to any of the submitted sitemaps.<br /> Here’s a peek of our new Index Coverage report:<br /> <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2fRZ-57fe2pPfNWl58UGOQ2rRI0RKvRtIyuy-8PaJAilWgY5YaMKb3iryM6Uv_tLcIT0keukO9Byvq4e9LEoGtT4tbN5hgcOIoi2AT2DufG3A3bDzBIRfsE4WwPpfh0VM4BLF/s1600/New+Search+Console+index+status+report+screenshot.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="913" data-original-width="1007" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2fRZ-57fe2pPfNWl58UGOQ2rRI0RKvRtIyuy-8PaJAilWgY5YaMKb3iryM6Uv_tLcIT0keukO9Byvq4e9LEoGtT4tbN5hgcOIoi2AT2DufG3A3bDzBIRfsE4WwPpfh0VM4BLF/s1600/New+Search+Console+index+status+report+screenshot.png" width="640" /></a></div> <h3>The new AMP fixing flow</h3> The new AMP fixing experience starts with the AMP Issues report. This report shows the current AMP issues affecting your site, grouped by the underlying error. Drill down into an issue to get more details, including sample affected pages. After you fix the underlying issue, click a button to verify your fix, and have Google recrawl the pages affected by that issue. Google will notify you of the progress of the recrawl, and will update the report as your fixes are validated.<br /> <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhfj-6wb8_gLZpAPMk2lF5-3PmYdqlSU2VYpaTQI4z_jjyUsOLbbvQKloPFDm_Dx67ejYcLWnEOUpWiWps8V9NHOLN2afUjWODUDdk6yshyphenhyphenMvbBs50YpsWcQTj5g63HuPBjRTkL/s1600/New+Search+Console+AMP+error+report+screenshot.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="913" data-original-width="1007" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhfj-6wb8_gLZpAPMk2lF5-3PmYdqlSU2VYpaTQI4z_jjyUsOLbbvQKloPFDm_Dx67ejYcLWnEOUpWiWps8V9NHOLN2afUjWODUDdk6yshyphenhyphenMvbBs50YpsWcQTj5g63HuPBjRTkL/s1600/New+Search+Console+AMP+error+report+screenshot.png" width="640" /></a></div> As we start to experiment with these new features, some users will be introduced to the new redesign through the coming weeks.<br /> <span class="byline-author">Posted by John Mueller and the Search Console Team</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> Search Console was <a href="http://sitemaps.blogspot.ch/2005/11/more-stats.html">initially launched</a> with just four reports more than a decade ago. Today, the product includes more than two dozen reports and tools covering AMP, structured data, and live testing tools, all designed to help improve your site's performance on Google Search.<br /> Now we have decided to embark on an extensive redesign to better serve you, our users. Our hope is that this redesign will provide you with:<br /> <ul> <li><strong>More actionable insights</strong> - We will now group the identified issues by what we suspect is the common “root-cause” to help you find where you should fix your code. We organize these issues into tasks that have a state (similar to bug tracking systems) so you can easily see whether the issue is still open, whether Google has detected your fix, and track the progress of re-processing the affected pages. </li> <li><strong>Better support of your organizational workflow</strong> - As we talked to many organizations, we’ve learned that multiple people are typically involved in implementing, diagnosing, and fixing issues. This is why we are introducing sharing functionality that allows you to pick-up an action item and share it with other people in your group, like developers who will get references to the code in question.</li> <li><strong>Faster feedback loops between you and Google</strong> - We’ve built a mechanism to allow you to iterate quickly on your fixes, and not waste time waiting for Google to recrawl your site, only to tell you later that it’s not fixed yet. Rather, we’ll provide on-the-spot testing of fixes and are automatically speeding up crawling once we see things are ok. Similarly, the testing tools will include code snippets and a search preview - so you can quickly see where your issues are, confirm you've fixed them, and see how the pages will look on Search.</li> </ul> </div> In the next few weeks, we're releasing two exciting BETA features from the new Search Console to a small set of users — Index Coverage report and AMP fixing flow.<br /> <h3></h3> The new Index Coverage report shows the count of indexed pages, information about why some pages could not be indexed, along with example pages and tips on how to fix indexing issues. It also enables a simple sitemap submission flow, and the capability to filter all Index Coverage data to any of the submitted sitemaps.<br /> Here’s a peek of our new Index Coverage report:<br /> <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2fRZ-57fe2pPfNWl58UGOQ2rRI0RKvRtIyuy-8PaJAilWgY5YaMKb3iryM6Uv_tLcIT0keukO9Byvq4e9LEoGtT4tbN5hgcOIoi2AT2DufG3A3bDzBIRfsE4WwPpfh0VM4BLF/s1600/New+Search+Console+index+status+report+screenshot.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="913" data-original-width="1007" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2fRZ-57fe2pPfNWl58UGOQ2rRI0RKvRtIyuy-8PaJAilWgY5YaMKb3iryM6Uv_tLcIT0keukO9Byvq4e9LEoGtT4tbN5hgcOIoi2AT2DufG3A3bDzBIRfsE4WwPpfh0VM4BLF/s1600/New+Search+Console+index+status+report+screenshot.png" width="640" /></a></div> <h3>The new AMP fixing flow</h3> The new AMP fixing experience starts with the AMP Issues report. This report shows the current AMP issues affecting your site, grouped by the underlying error. Drill down into an issue to get more details, including sample affected pages. After you fix the underlying issue, click a button to verify your fix, and have Google recrawl the pages affected by that issue. Google will notify you of the progress of the recrawl, and will update the report as your fixes are validated.<br /> <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhfj-6wb8_gLZpAPMk2lF5-3PmYdqlSU2VYpaTQI4z_jjyUsOLbbvQKloPFDm_Dx67ejYcLWnEOUpWiWps8V9NHOLN2afUjWODUDdk6yshyphenhyphenMvbBs50YpsWcQTj5g63HuPBjRTkL/s1600/New+Search+Console+AMP+error+report+screenshot.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="913" data-original-width="1007" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhfj-6wb8_gLZpAPMk2lF5-3PmYdqlSU2VYpaTQI4z_jjyUsOLbbvQKloPFDm_Dx67ejYcLWnEOUpWiWps8V9NHOLN2afUjWODUDdk6yshyphenhyphenMvbBs50YpsWcQTj5g63HuPBjRTkL/s1600/New+Search+Console+AMP+error+report+screenshot.png" width="640" /></a></div> As we start to experiment with these new features, some users will be introduced to the new redesign through the coming weeks.<br /> <span class="byline-author">Posted by John Mueller and the Search Console Team</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:The new Search Console: a sneak peek at two experimental features&url=https://webmasters.googleblog.com/2017/08/a-sneak-peek-at-two-experimental.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/08/a-sneak-peek-at-two-experimental.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/08/a-sneak-peek-at-two-experimental.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=en' rel='tag'> feedback and communication </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/products%20and%20services?hl=en' rel='tag'> products and services </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en' rel='tag'> search console </a> </span> </div> </div> </div> <div class='post' data-id='5920601435777924500' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/08/badges-on-image-search-help-users-find.html?hl=en' itemprop='url' title='Badges on Image Search help users find what they really want'> Badges on Image Search help users find what they really want </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, August 01, 2017 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <div dir="ltr" style="text-align: left;" trbidi="on"> <span style="font-family: inherit;">When you want to bake cupcakes, but you don't know what kind, Image Search can help you make a decision. Finding an image with a recipe can be challenging: you might end up on a page that has only pictures of these delicious things, or a cupcake fan site that doesn't have recipes, but everything else about them.</span><br /> <span style="font-family: inherit;">To help users find exactly what they want, Image Search on mobile devices now includes <a href="https://www.blog.google/products/search/new-badges-help-you-discover-and-take-action-image-search/">relevant badges on the thumbnails</a>. Currently we have badges for recipes, videos, products, and animated images (GIFs).</span><br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj1OTr4VqGD5pkY333LtiF8nHMPaulKxrlwQmDRP1WvwWAQ1Hw5q_qK6wUjLr048O3zahKfpLlZNZavHYeBEDyLFuHr3HMzhWFMrvyQOkCb_I12WtKnRE8-IxkRvT_-wF5lrKMy/s1600/cupcakes-pr3-device.gif" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1012" data-original-width="500" height="640" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj1OTr4VqGD5pkY333LtiF8nHMPaulKxrlwQmDRP1WvwWAQ1Hw5q_qK6wUjLr048O3zahKfpLlZNZavHYeBEDyLFuHr3HMzhWFMrvyQOkCb_I12WtKnRE8-IxkRvT_-wF5lrKMy/s640/cupcakes-pr3-device.gif" width="316" /></a></div> <br /> <span style="font-family: inherit;">If you have images on your site, you can help users identify the type of content associated with the image by using appropriate structured data on your pages. This helps users find relevant content quickly, and sends better targeted traffic to your site. </span><br /> <span style="font-family: inherit;">If you're publishing recipes, add <a href="https://developers.google.com/search/docs/data-types/recipes">Recipe markup</a> on your page, for products, add <a href="https://developers.google.com/search/docs/data-types/products">Product markup</a>, and for videos, add <a href="https://developers.google.com/search/docs/data-types/videos">Video markup</a>. Our algorithms will automatically badge GIFs, without the need of any markup. While we can't guarantee that badges will always be shown, adding the recommended structured data fields in addition to the required fields may increase the chance of adding a badge to your image search results.</span><br /> <span style="font-family: inherit;">You can use the <a href="https://search.google.com/structured-data/testing-tool">Structured Data Testing Tool</a> to verify that your pages are free of errors, and therefore eligible for the new Image Search badges. In addition, the <a href="https://support.google.com/webmasters/answer/6381755">Rich Cards report</a> in Search Console can provide aggregate stats on your markup. </span><br /> <span style="font-family: inherit;">If you have questions about the feature, please ask us in the <a href="https://g.co/webmasterhelpforum">Webmaster Help Forum</a>.</span><br /> <span class="byline-author" style="font-family: inherit;">Posted by Assaf Broitman, Image 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"> <span style="font-family: inherit;">When you want to bake cupcakes, but you don't know what kind, Image Search can help you make a decision. Finding an image with a recipe can be challenging: you might end up on a page that has only pictures of these delicious things, or a cupcake fan site that doesn't have recipes, but everything else about them.</span><br /> <span style="font-family: inherit;">To help users find exactly what they want, Image Search on mobile devices now includes <a href="https://www.blog.google/products/search/new-badges-help-you-discover-and-take-action-image-search/">relevant badges on the thumbnails</a>. Currently we have badges for recipes, videos, products, and animated images (GIFs).</span><br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj1OTr4VqGD5pkY333LtiF8nHMPaulKxrlwQmDRP1WvwWAQ1Hw5q_qK6wUjLr048O3zahKfpLlZNZavHYeBEDyLFuHr3HMzhWFMrvyQOkCb_I12WtKnRE8-IxkRvT_-wF5lrKMy/s1600/cupcakes-pr3-device.gif" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1012" data-original-width="500" height="640" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj1OTr4VqGD5pkY333LtiF8nHMPaulKxrlwQmDRP1WvwWAQ1Hw5q_qK6wUjLr048O3zahKfpLlZNZavHYeBEDyLFuHr3HMzhWFMrvyQOkCb_I12WtKnRE8-IxkRvT_-wF5lrKMy/s640/cupcakes-pr3-device.gif" width="316" /></a></div> <br /> <span style="font-family: inherit;">If you have images on your site, you can help users identify the type of content associated with the image by using appropriate structured data on your pages. This helps users find relevant content quickly, and sends better targeted traffic to your site. </span><br /> <span style="font-family: inherit;">If you're publishing recipes, add <a href="https://developers.google.com/search/docs/data-types/recipes">Recipe markup</a> on your page, for products, add <a href="https://developers.google.com/search/docs/data-types/products">Product markup</a>, and for videos, add <a href="https://developers.google.com/search/docs/data-types/videos">Video markup</a>. Our algorithms will automatically badge GIFs, without the need of any markup. While we can't guarantee that badges will always be shown, adding the recommended structured data fields in addition to the required fields may increase the chance of adding a badge to your image search results.</span><br /> <span style="font-family: inherit;">You can use the <a href="https://search.google.com/structured-data/testing-tool">Structured Data Testing Tool</a> to verify that your pages are free of errors, and therefore eligible for the new Image Search badges. In addition, the <a href="https://support.google.com/webmasters/answer/6381755">Rich Cards report</a> in Search Console can provide aggregate stats on your markup. </span><br /> <span style="font-family: inherit;">If you have questions about the feature, please ask us in the <a href="https://g.co/webmasterhelpforum">Webmaster Help Forum</a>.</span><br /> <span class="byline-author" style="font-family: inherit;">Posted by Assaf Broitman, Image 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:Badges on Image Search help users find what they really want&url=https://webmasters.googleblog.com/2017/08/badges-on-image-search-help-users-find.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/08/badges-on-image-search-help-users-find.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/08/badges-on-image-search-help-users-find.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/images?hl=en' rel='tag'> images </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=en' rel='tag'> structured data </a> </span> </div> </div> </div> <div class='post' data-id='7626097425779130115' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/06/connect-to-job-seekers-with-google.html?hl=en' itemprop='url' title='Connect to job seekers with Google Search'> Connect to job seekers with Google Search </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, June 20, 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><i><b>July 20, 2017 update</b>: Starting today, impressions and clicks stats for job listing pages and job details pages are available in the Search Analytics report in Search Console. Read more about how Jobs impressions and clicks are counted <a href="https://support.google.com/webmasters/answer/7042828">in the help centre</a>. If you have questions, head to the <a href="https://g.co/webmasterhelpforum">webmaster forums</a>. </i></p> <hr> At Google I/O this year, we <a href="https://youtu.be/Y2VF8tmLFHw?t=6704">announced Google for Jobs</a>, a new company-wide initiative focused on helping both job seekers and employers, through collaboration with the job matching industry. One major part of this effort is launching an improved experience for job seekers on Google Search. We’re happy to announce this new experience is now open for all developers and site owners.<br /> For queries with clear intent like [<a href="https://www.google.com/webhp?hl=en&gws_rd=cr&fg=1#q=head+of+catering+jobs+nyc">head of catering jobs in nyc</a>] or [<a href="https://www.google.com/webhp?hl=en&gws_rd=cr&fg=1#q=entry+level+jobs+in+dc">entry level jobs in DC</a>], we’ll show a job listings preview, and each job can expand to display comprehensive details about the listing: <br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgBf4h6AzfkZovBz1sDf4OXh7v819tjinJ55zGyh-knka5BGlyZ7DkWxNfxl6y0r7sTkL7G2FVPQ1p-15-gSbOMz6a_QVzm_HvvVgV23khy5ggBoIfXI7voMM740bL4lcWefwH_/s1600/SD+Jobs+head+of+catering+.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="934" data-original-width="1166" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgBf4h6AzfkZovBz1sDf4OXh7v819tjinJ55zGyh-knka5BGlyZ7DkWxNfxl6y0r7sTkL7G2FVPQ1p-15-gSbOMz6a_QVzm_HvvVgV23khy5ggBoIfXI7voMM740bL4lcWefwH_/s640/SD+Jobs+head+of+catering+.png" width="640" /></a></div> For employers or site owners with job content, this feature brings many benefits: <br /> <ul> <li><strong>Prominent place in Search results</strong>: your postings are eligible to be displayed in the in the new job search feature on Google, featuring your logo, reviews, ratings, and job details.</li> <li><strong>More, motivated applicants</strong>: job seekers can filter by various criteria like location or job title, meaning you’re more likely to get applicants who are looking exactly for that job.</li> <li><strong>Increased chances of discovery and conversion</strong>: job seekers will have a new avenue to interact with your postings and click through to your site.</li> </ul> <br /> <h3> Get your job listings on Google</h3> Implementation involves two steps: <br /> <ol> <li>Mark up your job listings with <a href="https://developers.google.com/search/docs/data-types/job-postings">Job Posting structured data</a>.</li> <li>Submit a sitemap (or an RSS or Atom feed) with a <lastmod> date for each listing.</li> </ol> <br /> If you have more than 100,000 job postings or more than 10,000 changes per day, you can <a href="https://docs.google.com/a/google.com/forms/d/e/1FAIpQLSdlj1CC6jX1wNV-jwfJ_0QNR5Cq6gpkIfjBo5e_Rx_VmYcGsg/viewform">express interest</a> to use the High Change Rate feature.<br /> If you already publish your job openings on another site like LinkedIn, Monster, DirectEmployers, CareerBuilder, Glassdoor, and Facebook, they are eligible to appear in the feature as well.<br /> Job search is an enriched search experience. We’ve created a <a href="https://support.google.com/webmasters/answer/7407437">dedicated guide</a> to help you understand how Google ranking works for enriched search and practices for improving your presence<br /> <h3> Keep track of how you’re doing and fix issues</h3> There’s a suite of tools to help you with the implementation: <br /> <ul> <li>Validate your markup with the <a href="https://search.google.com/structured-data/testing-tool">Structured Data Testing Tool</a></li> <li><a href="https://developers.google.com/search/docs/guides/prototype#preview-markup">Preview your listing</a> in the Structured Data Testing Tool</li> <li><a href="https://support.google.com/webmasters/answer/183669">Keep track of your sitemap</a> status in Search Console</li> <li><a href="https://support.google.com/webmasters/answer/6381755">See aggregate stats and markup error examples</a> in Search Console</li> </ul> <br /> In the coming weeks, we’ll add new job listings filters in the <a href="https://support.google.com/webmasters/answer/6155685">Search Analytics report</a> in Search Console, so you can track clicks and impressions for your listings.<br /> As always, if you have questions, ask in the <a href="https://g.co/webmasterhelpforum">forums</a> or find us on <a href="https://twitter.com/googlewmc/">Twitter</a>!<br /> <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><i><b>July 20, 2017 update</b>: Starting today, impressions and clicks stats for job listing pages and job details pages are available in the Search Analytics report in Search Console. Read more about how Jobs impressions and clicks are counted <a href="https://support.google.com/webmasters/answer/7042828">in the help centre</a>. If you have questions, head to the <a href="https://g.co/webmasterhelpforum">webmaster forums</a>. </i></p> <hr> At Google I/O this year, we <a href="https://youtu.be/Y2VF8tmLFHw?t=6704">announced Google for Jobs</a>, a new company-wide initiative focused on helping both job seekers and employers, through collaboration with the job matching industry. One major part of this effort is launching an improved experience for job seekers on Google Search. We’re happy to announce this new experience is now open for all developers and site owners.<br /> For queries with clear intent like [<a href="https://www.google.com/webhp?hl=en&gws_rd=cr&fg=1#q=head+of+catering+jobs+nyc">head of catering jobs in nyc</a>] or [<a href="https://www.google.com/webhp?hl=en&gws_rd=cr&fg=1#q=entry+level+jobs+in+dc">entry level jobs in DC</a>], we’ll show a job listings preview, and each job can expand to display comprehensive details about the listing: <br /> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgBf4h6AzfkZovBz1sDf4OXh7v819tjinJ55zGyh-knka5BGlyZ7DkWxNfxl6y0r7sTkL7G2FVPQ1p-15-gSbOMz6a_QVzm_HvvVgV23khy5ggBoIfXI7voMM740bL4lcWefwH_/s1600/SD+Jobs+head+of+catering+.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="934" data-original-width="1166" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgBf4h6AzfkZovBz1sDf4OXh7v819tjinJ55zGyh-knka5BGlyZ7DkWxNfxl6y0r7sTkL7G2FVPQ1p-15-gSbOMz6a_QVzm_HvvVgV23khy5ggBoIfXI7voMM740bL4lcWefwH_/s640/SD+Jobs+head+of+catering+.png" width="640" /></a></div> For employers or site owners with job content, this feature brings many benefits: <br /> <ul> <li><strong>Prominent place in Search results</strong>: your postings are eligible to be displayed in the in the new job search feature on Google, featuring your logo, reviews, ratings, and job details.</li> <li><strong>More, motivated applicants</strong>: job seekers can filter by various criteria like location or job title, meaning you’re more likely to get applicants who are looking exactly for that job.</li> <li><strong>Increased chances of discovery and conversion</strong>: job seekers will have a new avenue to interact with your postings and click through to your site.</li> </ul> <br /> <h3> Get your job listings on Google</h3> Implementation involves two steps: <br /> <ol> <li>Mark up your job listings with <a href="https://developers.google.com/search/docs/data-types/job-postings">Job Posting structured data</a>.</li> <li>Submit a sitemap (or an RSS or Atom feed) with a <lastmod> date for each listing.</li> </ol> <br /> If you have more than 100,000 job postings or more than 10,000 changes per day, you can <a href="https://docs.google.com/a/google.com/forms/d/e/1FAIpQLSdlj1CC6jX1wNV-jwfJ_0QNR5Cq6gpkIfjBo5e_Rx_VmYcGsg/viewform">express interest</a> to use the High Change Rate feature.<br /> If you already publish your job openings on another site like LinkedIn, Monster, DirectEmployers, CareerBuilder, Glassdoor, and Facebook, they are eligible to appear in the feature as well.<br /> Job search is an enriched search experience. We’ve created a <a href="https://support.google.com/webmasters/answer/7407437">dedicated guide</a> to help you understand how Google ranking works for enriched search and practices for improving your presence<br /> <h3> Keep track of how you’re doing and fix issues</h3> There’s a suite of tools to help you with the implementation: <br /> <ul> <li>Validate your markup with the <a href="https://search.google.com/structured-data/testing-tool">Structured Data Testing Tool</a></li> <li><a href="https://developers.google.com/search/docs/guides/prototype#preview-markup">Preview your listing</a> in the Structured Data Testing Tool</li> <li><a href="https://support.google.com/webmasters/answer/183669">Keep track of your sitemap</a> status in Search Console</li> <li><a href="https://support.google.com/webmasters/answer/6381755">See aggregate stats and markup error examples</a> in Search Console</li> </ul> <br /> In the coming weeks, we’ll add new job listings filters in the <a href="https://support.google.com/webmasters/answer/6155685">Search Analytics report</a> in Search Console, so you can track clicks and impressions for your listings.<br /> As always, if you have questions, ask in the <a href="https://g.co/webmasterhelpforum">forums</a> or find us on <a href="https://twitter.com/googlewmc/">Twitter</a>!<br /> <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:Connect to job seekers with Google Search&url=https://webmasters.googleblog.com/2017/06/connect-to-job-seekers-with-google.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/06/connect-to-job-seekers-with-google.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/06/connect-to-job-seekers-with-google.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en' rel='tag'> search console </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en' rel='tag'> search results </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=en' rel='tag'> structured data </a> </span> </div> </div> </div> <div class='post' data-id='6325363575053591471' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/06/making-internet-safer-and-faster.html?hl=en' itemprop='url' title='Making the Internet safer and faster: Introducing reCAPTCHA Android API'> Making the Internet safer and faster: Introducing reCAPTCHA Android API </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, June 08, 2017 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p>When we launched reCAPTCHA ten years ago, we had a simple goal: enable users to visit the sites they love without worrying about spam and abuse. Over the years, reCAPTCHA has changed quite a bit. It evolved from the distorted text to <a href="https://security.googleblog.com/2014/04/street-view-and-recaptcha-technology.html">street numbers</a> and names, then <a href="https://security.googleblog.com/2014/12/are-you-robot-introducing-no-captcha.html">No CAPTCHA reCAPTCHA</a> in 2014 and Invisible reCAPTCHA in March this year.</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjs7Ke1KBl3mNnOpKhMBHxFiuzPlNYW8vrDiW0Jdy-oS0TUkywdCe9oz7AW372tVKv3dBgSDSQ_JRhXaJEJGYtPGH4sge2i3KcF_u_s_PfSgsjiq6lfTpZ27vFDxXMeHGW8x8Td/s1600/recaptcha1.gif" imageanchor="1" ><img border="0" data-original-height="150" data-original-width="450" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjs7Ke1KBl3mNnOpKhMBHxFiuzPlNYW8vrDiW0Jdy-oS0TUkywdCe9oz7AW372tVKv3dBgSDSQ_JRhXaJEJGYtPGH4sge2i3KcF_u_s_PfSgsjiq6lfTpZ27vFDxXMeHGW8x8Td/s1600/recaptcha1.gif" /></a> </p> <p>By now, more than a billion users have benefited from reCAPTCHA and we continue to work to refine our protections.</p> <p>reCAPTCHA protects users wherever they may be online. As the use of mobile devices has grown rapidly, it’s important to keep the mobile applications and data safe. Today, on reCAPTCHA’s tenth birthday, we’re glad to announce the first reCAPTCHA <a href="https://developer.android.com/training/safetynet/recaptcha.html">Android API</a> as part of Google Play Services.</p> <p>With this API, reCAPTCHA can better tell human and bots apart to provide a streamlined user experience on mobile. It will use our newest Invisible reCAPTCHA technology, which runs risk analysis behind the scene and has enabled millions of human users to pass through with zero click everyday. Now mobile users can enjoy their apps without being interrupted, while still staying away from spam and abuse.</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh9MO8ePap4JPKD3ju12rQBK5Ycs2WC0SCoZ1WLBYPCt59j0ZegiS-KVdkZakOfx6bnp6WzOf-oCwENN9oMaeenhh8jyPC-o8uIC7Rn9CQjY0i6pDCIyAbnRiioscUV77VqDd8Q/s1600/recaptcha2.gif" imageanchor="1" ><img border="0" data-original-height="1136" data-original-width="640" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh9MO8ePap4JPKD3ju12rQBK5Ycs2WC0SCoZ1WLBYPCt59j0ZegiS-KVdkZakOfx6bnp6WzOf-oCwENN9oMaeenhh8jyPC-o8uIC7Rn9CQjY0i6pDCIyAbnRiioscUV77VqDd8Q/s400/recaptcha2.gif" width="225" /></a> </p> <p>reCAPTCHA Android API is included with Google <a href="https://developer.android.com/training/safetynet/index.html">SafetyNet</a>, which provides services like device attestation and safe browsing to protect mobile apps. Mobile developers can do both the device and user attestations in the same API to mitigate security risks of their apps more efficiently. This adds to the <a href="https://security.googleblog.com/2017/03/diverse-protections-for-diverse.html">diversity of security protections</a> on Android: <a href="https://blog.google/products/android/google-play-protect/">Google Play Protect</a> to monitor for potentially harmful applications, device encryption, and regular security updates. Please <a href="https://developers.google.com/recaptcha/docs/versions">visit our site</a> to learn more about how to integrate with the reCAPTCHA Android API, and keep an eye out for our iOS library.</p> <p>The journey of reCAPTCHA continues: we’ll make the Internet safer and easier to use for everyone (except bots).</p> <br> <span class="byline-author">Posted by Wei Liu, Product Manager, reCAPTCHA</span> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p>When we launched reCAPTCHA ten years ago, we had a simple goal: enable users to visit the sites they love without worrying about spam and abuse. Over the years, reCAPTCHA has changed quite a bit. It evolved from the distorted text to <a href="https://security.googleblog.com/2014/04/street-view-and-recaptcha-technology.html">street numbers</a> and names, then <a href="https://security.googleblog.com/2014/12/are-you-robot-introducing-no-captcha.html">No CAPTCHA reCAPTCHA</a> in 2014 and Invisible reCAPTCHA in March this year.</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjs7Ke1KBl3mNnOpKhMBHxFiuzPlNYW8vrDiW0Jdy-oS0TUkywdCe9oz7AW372tVKv3dBgSDSQ_JRhXaJEJGYtPGH4sge2i3KcF_u_s_PfSgsjiq6lfTpZ27vFDxXMeHGW8x8Td/s1600/recaptcha1.gif" imageanchor="1" ><img border="0" data-original-height="150" data-original-width="450" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjs7Ke1KBl3mNnOpKhMBHxFiuzPlNYW8vrDiW0Jdy-oS0TUkywdCe9oz7AW372tVKv3dBgSDSQ_JRhXaJEJGYtPGH4sge2i3KcF_u_s_PfSgsjiq6lfTpZ27vFDxXMeHGW8x8Td/s1600/recaptcha1.gif" /></a> </p> <p>By now, more than a billion users have benefited from reCAPTCHA and we continue to work to refine our protections.</p> <p>reCAPTCHA protects users wherever they may be online. As the use of mobile devices has grown rapidly, it’s important to keep the mobile applications and data safe. Today, on reCAPTCHA’s tenth birthday, we’re glad to announce the first reCAPTCHA <a href="https://developer.android.com/training/safetynet/recaptcha.html">Android API</a> as part of Google Play Services.</p> <p>With this API, reCAPTCHA can better tell human and bots apart to provide a streamlined user experience on mobile. It will use our newest Invisible reCAPTCHA technology, which runs risk analysis behind the scene and has enabled millions of human users to pass through with zero click everyday. Now mobile users can enjoy their apps without being interrupted, while still staying away from spam and abuse.</p> <p> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh9MO8ePap4JPKD3ju12rQBK5Ycs2WC0SCoZ1WLBYPCt59j0ZegiS-KVdkZakOfx6bnp6WzOf-oCwENN9oMaeenhh8jyPC-o8uIC7Rn9CQjY0i6pDCIyAbnRiioscUV77VqDd8Q/s1600/recaptcha2.gif" imageanchor="1" ><img border="0" data-original-height="1136" data-original-width="640" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh9MO8ePap4JPKD3ju12rQBK5Ycs2WC0SCoZ1WLBYPCt59j0ZegiS-KVdkZakOfx6bnp6WzOf-oCwENN9oMaeenhh8jyPC-o8uIC7Rn9CQjY0i6pDCIyAbnRiioscUV77VqDd8Q/s400/recaptcha2.gif" width="225" /></a> </p> <p>reCAPTCHA Android API is included with Google <a href="https://developer.android.com/training/safetynet/index.html">SafetyNet</a>, which provides services like device attestation and safe browsing to protect mobile apps. Mobile developers can do both the device and user attestations in the same API to mitigate security risks of their apps more efficiently. This adds to the <a href="https://security.googleblog.com/2017/03/diverse-protections-for-diverse.html">diversity of security protections</a> on Android: <a href="https://blog.google/products/android/google-play-protect/">Google Play Protect</a> to monitor for potentially harmful applications, device encryption, and regular security updates. Please <a href="https://developers.google.com/recaptcha/docs/versions">visit our site</a> to learn more about how to integrate with the reCAPTCHA Android API, and keep an eye out for our iOS library.</p> <p>The journey of reCAPTCHA continues: we’ll make the Internet safer and easier to use for everyone (except bots).</p> <br> <span class="byline-author">Posted by Wei Liu, Product Manager, reCAPTCHA</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:Making the Internet safer and faster: Introducing reCAPTCHA Android API&url=https://webmasters.googleblog.com/2017/06/making-internet-safer-and-faster.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/06/making-internet-safer-and-faster.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/06/making-internet-safer-and-faster.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/Android?hl=en' rel='tag'> Android </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/API?hl=en' rel='tag'> API </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/apps?hl=en' rel='tag'> apps </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/mobile?hl=en' rel='tag'> mobile </a> </span> </div> </div> </div> <div class='post' data-id='9008215185536899116' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/06/better-snippets-for-your-users.html?hl=en' itemprop='url' title='Better Snippets for your Users'> Better Snippets for your Users </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Friday, June 02, 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"> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Before buying a book, people like to get a snapshot of how they’re about to spend a few hours reading. They'll take a look at the synopsis, the preface, or even the prologue just to get a sense about whether they'll like the book. </span></div> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Search result snippets are much the same; they help people decide whether or not it makes sense to invest the time reading the page the snippet belongs to.  </span></div> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"><img height="272" src="https://lh5.googleusercontent.com/ztOsmTHJywDInZy7olQGaYwxAkwrEpU-tYgO7exNQucA26DYPF4vg5iVc5S9uYcOlWRP8fLNbN5rCQVi6jJFEENsPxmC904Oh5WUL4GjbEIZHljHO1Wl23vp5ojBrWxFb-o6XE1C" style="border: none; transform: rotate(0rad);" width="624" /></span></div> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">The more descriptive and relevant a search result snippet is, the more likely that people will click through and be satisfied with the page they land on. Historically, snippets came from 3 places:</span></div> <ol style="margin-bottom: 0pt; margin-top: 0pt;"> <li dir="ltr" style="background-color: transparent; color: #424242; font-family: Roboto; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.2; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">The content of the page</span></div> </li> <li dir="ltr" style="background-color: transparent; color: #424242; font-family: Roboto; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.2; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">The meta description</span></div> </li> <li dir="ltr" style="background-color: transparent; color: #424242; font-family: Roboto; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">DMOZ listings</span></div> </li> </ol> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">The content of the page is an obvious choice for result snippets, and  the content that can be extracted is often the most relevant to people’s queries. However, there are times when the content itself isn't the best source for a snippet. For instance, when someone searches for a publishing company for their book, the relevant homepages in the result set may contain only a few images describing the businesses and a logo, and maybe some links, none of which are particularly useful for a snippet. </span></div> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">The logical fallback in cases when the content of a page doesn't have much textual content for a search result snippet is the meta description. This should be short blurbs that describe accurately and precisely the content in a few words. </span></div> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Finally, when a page doesn't have much textual content for snippet generation </span><span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: italic; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">and</span><span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"> the meta description is missing, unrelated to the page, or low quality, our fallback was </span><a href="https://en.wikipedia.org/wiki/DMOZ" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">DMOZ, also known as The Open Directory Project</span></a><span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">. For over 10 years, we relied on DMOZ for snippets because the quality of the DMOZ snippets were often much higher quality than those  provided by webmasters in their meta description, or were more descriptive than what the page provided. </span></div> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">With DMOZ </span><a href="http://www.dmoz.org/" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">now closed</span></a><span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">, we've stopped using its listings for snippeting, so it's a lot more important that webmasters provide good meta descriptions, if adding more content to the page is not an option. </span></div> <h5 dir="ltr" style="line-height: 1.2; margin-bottom: 4pt; margin-top: 12pt;"> <span style="background-color: transparent; color: #64b5f6; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">What makes a good meta description?</span></h5> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Good meta descriptions are short blurbs that describe accurately the content of the page. They are like a pitch that convince the user that the page is exactly what they're looking for. For more tips, we have a handy </span><a href="https://support.google.com/webmasters/answer/35624" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">help center article</span></a><span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"> on the topic. Remember to make sure that both your desktop and your mobile pages include both a title and a meta description. </span></div> <h5 dir="ltr" style="line-height: 1.2; margin-bottom: 4pt; margin-top: 12pt;"> <span style="background-color: transparent; color: #64b5f6; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">What are the most common problems with meta descriptions?</span></h5> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Because meta descriptions are usually visible only to search engines and other software, webmasters sometimes forget about them, leaving them completely empty. It's also common, for the same reason, that the same meta description is used across multiple (and sometimes many) pages. On the flip side, it's also relatively common that the description is completely off-topic, low quality, or outright spammy. These issues tarnish our users' search experience, so we prefer to ignore such meta descriptions. </span></div> <h5 dir="ltr" style="line-height: 1.2; margin-bottom: 4pt; margin-top: 12pt;"> <span style="background-color: transparent; color: #64b5f6; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Is there a character limit for meta descriptions?</span></h5> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">There's no limit on how long a meta description can be, but the search result snippets are truncated as needed, typically to fit the device width.</span></div> <h5 dir="ltr" style="line-height: 1.2; margin-bottom: 4pt; margin-top: 12pt;"> <span style="background-color: transparent; color: #64b5f6; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">What will happen with the </span><a href="https://developers.google.com/webmasters/control-crawl-index/docs/robots_meta_tag#valid-indexing--serving-directives" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">"NOODP" robots directive</span></a><span style="background-color: transparent; color: #64b5f6; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">?</span></h5> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">With DMOZ (ODP) closed, we stopped relying on its data and thus the NOODP directive is already no-op. </span></div> <h5 dir="ltr" style="line-height: 1.2; margin-bottom: 4pt; margin-top: 12pt;"> <span style="background-color: transparent; color: #64b5f6; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Can I prevent Google from using the page contents as snippet? </span></h5> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">You can prevent Google from generating snippets altogether by specifying the </span><a href="https://developers.google.com/webmasters/control-crawl-index/docs/robots_meta_tag#valid-indexing--serving-directives" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">"nosnippet" robots directive</span></a><span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">. There's no way to prevent using page contents as snippet while allowing other sources.</span></div> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <br /></div> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">As always, if you have questions, ask in the </span><a href="//g.co/webmasterhelpforum" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">forums</span></a><span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"> or find us on </span><a href="https://twitter.com/googlewmc/" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">Twitter</span></a><span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">!</span></div> <span id="docs-internal-guid-77a8b6f5-53f8-6a62-fd5e-5308b1c6bf53"><span style="color: #424242; font-family: "roboto"; font-size: 11pt; vertical-align: baseline; white-space: pre-wrap;">Posted by </span><a href="https://twitter.com/methode" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "roboto"; font-size: 11pt; vertical-align: baseline; white-space: pre-wrap;">Gary</span></a><span style="color: #424242; font-family: "roboto"; font-size: 11pt; vertical-align: baseline; white-space: pre-wrap;">, Search Team</span></span></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Before buying a book, people like to get a snapshot of how they’re about to spend a few hours reading. They'll take a look at the synopsis, the preface, or even the prologue just to get a sense about whether they'll like the book. </span></div> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Search result snippets are much the same; they help people decide whether or not it makes sense to invest the time reading the page the snippet belongs to.  </span></div> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"><img height="272" src="https://lh5.googleusercontent.com/ztOsmTHJywDInZy7olQGaYwxAkwrEpU-tYgO7exNQucA26DYPF4vg5iVc5S9uYcOlWRP8fLNbN5rCQVi6jJFEENsPxmC904Oh5WUL4GjbEIZHljHO1Wl23vp5ojBrWxFb-o6XE1C" style="border: none; transform: rotate(0rad);" width="624" /></span></div> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">The more descriptive and relevant a search result snippet is, the more likely that people will click through and be satisfied with the page they land on. Historically, snippets came from 3 places:</span></div> <ol style="margin-bottom: 0pt; margin-top: 0pt;"> <li dir="ltr" style="background-color: transparent; color: #424242; font-family: Roboto; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.2; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">The content of the page</span></div> </li> <li dir="ltr" style="background-color: transparent; color: #424242; font-family: Roboto; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.2; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">The meta description</span></div> </li> <li dir="ltr" style="background-color: transparent; color: #424242; font-family: Roboto; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">DMOZ listings</span></div> </li> </ol> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">The content of the page is an obvious choice for result snippets, and  the content that can be extracted is often the most relevant to people’s queries. However, there are times when the content itself isn't the best source for a snippet. For instance, when someone searches for a publishing company for their book, the relevant homepages in the result set may contain only a few images describing the businesses and a logo, and maybe some links, none of which are particularly useful for a snippet. </span></div> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">The logical fallback in cases when the content of a page doesn't have much textual content for a search result snippet is the meta description. This should be short blurbs that describe accurately and precisely the content in a few words. </span></div> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Finally, when a page doesn't have much textual content for snippet generation </span><span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: italic; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">and</span><span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"> the meta description is missing, unrelated to the page, or low quality, our fallback was </span><a href="https://en.wikipedia.org/wiki/DMOZ" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">DMOZ, also known as The Open Directory Project</span></a><span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">. For over 10 years, we relied on DMOZ for snippets because the quality of the DMOZ snippets were often much higher quality than those  provided by webmasters in their meta description, or were more descriptive than what the page provided. </span></div> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">With DMOZ </span><a href="http://www.dmoz.org/" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">now closed</span></a><span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">, we've stopped using its listings for snippeting, so it's a lot more important that webmasters provide good meta descriptions, if adding more content to the page is not an option. </span></div> <h5 dir="ltr" style="line-height: 1.2; margin-bottom: 4pt; margin-top: 12pt;"> <span style="background-color: transparent; color: #64b5f6; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">What makes a good meta description?</span></h5> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Good meta descriptions are short blurbs that describe accurately the content of the page. They are like a pitch that convince the user that the page is exactly what they're looking for. For more tips, we have a handy </span><a href="https://support.google.com/webmasters/answer/35624" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">help center article</span></a><span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"> on the topic. Remember to make sure that both your desktop and your mobile pages include both a title and a meta description. </span></div> <h5 dir="ltr" style="line-height: 1.2; margin-bottom: 4pt; margin-top: 12pt;"> <span style="background-color: transparent; color: #64b5f6; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">What are the most common problems with meta descriptions?</span></h5> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Because meta descriptions are usually visible only to search engines and other software, webmasters sometimes forget about them, leaving them completely empty. It's also common, for the same reason, that the same meta description is used across multiple (and sometimes many) pages. On the flip side, it's also relatively common that the description is completely off-topic, low quality, or outright spammy. These issues tarnish our users' search experience, so we prefer to ignore such meta descriptions. </span></div> <h5 dir="ltr" style="line-height: 1.2; margin-bottom: 4pt; margin-top: 12pt;"> <span style="background-color: transparent; color: #64b5f6; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Is there a character limit for meta descriptions?</span></h5> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">There's no limit on how long a meta description can be, but the search result snippets are truncated as needed, typically to fit the device width.</span></div> <h5 dir="ltr" style="line-height: 1.2; margin-bottom: 4pt; margin-top: 12pt;"> <span style="background-color: transparent; color: #64b5f6; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">What will happen with the </span><a href="https://developers.google.com/webmasters/control-crawl-index/docs/robots_meta_tag#valid-indexing--serving-directives" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">"NOODP" robots directive</span></a><span style="background-color: transparent; color: #64b5f6; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">?</span></h5> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">With DMOZ (ODP) closed, we stopped relying on its data and thus the NOODP directive is already no-op. </span></div> <h5 dir="ltr" style="line-height: 1.2; margin-bottom: 4pt; margin-top: 12pt;"> <span style="background-color: transparent; color: #64b5f6; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Can I prevent Google from using the page contents as snippet? </span></h5> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">You can prevent Google from generating snippets altogether by specifying the </span><a href="https://developers.google.com/webmasters/control-crawl-index/docs/robots_meta_tag#valid-indexing--serving-directives" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">"nosnippet" robots directive</span></a><span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">. There's no way to prevent using page contents as snippet while allowing other sources.</span></div> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <br /></div> <div dir="ltr" style="line-height: 1.2; margin-bottom: 10pt; margin-top: 0pt;"> <span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">As always, if you have questions, ask in the </span><a href="//g.co/webmasterhelpforum" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">forums</span></a><span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"> or find us on </span><a href="https://twitter.com/googlewmc/" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">Twitter</span></a><span style="background-color: transparent; color: #424242; font-family: "roboto"; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">!</span></div> <span id="docs-internal-guid-77a8b6f5-53f8-6a62-fd5e-5308b1c6bf53"><span style="color: #424242; font-family: "roboto"; font-size: 11pt; vertical-align: baseline; white-space: pre-wrap;">Posted by </span><a href="https://twitter.com/methode" style="text-decoration-line: none;"><span style="color: #1155cc; font-family: "roboto"; font-size: 11pt; vertical-align: baseline; white-space: pre-wrap;">Gary</span></a><span style="color: #424242; font-family: "roboto"; font-size: 11pt; vertical-align: baseline; white-space: pre-wrap;">, Search Team</span></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:Better Snippets for your Users&url=https://webmasters.googleblog.com/2017/06/better-snippets-for-your-users.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/06/better-snippets-for-your-users.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/06/better-snippets-for-your-users.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en' rel='tag'> search results </a> </span> </div> </div> </div> <div class='post' data-id='8359434776291127931' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2017/05/a-reminder-about-links-in-large-scale.html?hl=en' itemprop='url' title='A reminder about links in large-scale article campaigns'> A reminder about links in large-scale article campaigns </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, May 25, 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"> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="font-family: Arial; font-size: 11pt; white-space: pre-wrap;">Lately we've seen an increase in spammy links contained in articles referred to as contributor posts, guest posts, partner posts, or syndicated posts. These articles are generally written by or in the name of one website, and published on a different one.</span></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <br /></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Google does not discourage these types of articles in the cases when they inform users, educate another site’s audience or bring awareness to your cause or company. However, what does violate </span><a href="https://support.google.com/webmasters/answer/66356?hl=en" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">Google's guidelines on link schemes</span></a><span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"> is when the main intent is to build links in a large-scale way back to the author’s site. Below are factors that, when taken to an extreme, can indicate when an article is in violation of these guidelines:</span></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <br /></div> <ul style="margin-bottom: 0pt; margin-top: 0pt;"> <li dir="ltr" style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; list-style-type: disc; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Stuffing keyword-rich links to your site in your articles</span></div> </li> <li dir="ltr" style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; list-style-type: disc; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Having the articles published across many different sites; alternatively, having a large number of articles on a few large, different sites</span></div> </li> <li dir="ltr" style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; list-style-type: disc; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Using or hiring article writers that aren’t knowledgeable about the topics they’re writing on</span></div> </li> <li dir="ltr" style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; list-style-type: disc; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Using the same or similar content across these articles; alternatively, duplicating the full content of articles found on your own site (in which case use of </span><a href="https://support.google.com/webmasters/answer/139066?hl=en" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">rel=”canonical”</span></a><span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">, in addition to </span><a href="https://support.google.com/webmasters/answer/96569?hl=en" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">rel=”nofollow”</span></a><span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">, is advised)</span></div> </li> </ul> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <br /></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">When Google detects that a website is publishing articles that contain spammy links, this may change Google's perception of the quality of the site and could affect its ranking. Sites accepting and publishing such articles should carefully vet them, asking questions like: Do I know this person? Does this person’s message fit with my site’s audience? Does the article contain useful content? If there are links of questionable intent in the article, has the author used </span><a href="https://support.google.com/webmasters/answer/96569?hl=en" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">rel=”nofollow”</span></a><span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"> on them?</span></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <br /></div> <span id="docs-internal-guid-f9feb677-40a1-a7c6-eebd-9af28d6a1455"></span><br /> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">For websites creating articles made for links, Google takes action on this behavior because it’s bad for the Web as a whole. When link building comes first, the quality of the articles can suffer and create a bad experience for users. Also, webmasters generally prefer not to receive aggressive or repeated "Post my article!" requests, and we encourage such cases to be reported to our </span><a href="https://www.google.com/webmasters/tools/spamreport?pli=1" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">spam report form</span></a><span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">. And lastly, if a link is a form of endorsement, and you’re the one creating most of the endorsements for your own site, is this putting forth the best impression of your site? Our best advice in relation to link building is to focus on improving your site’s content and everything--including links--will follow (no pun intended).</span></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"><br /></span></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"><span style="font-size: 14.6667px;">Posted by the Google Webspam Team</span></span></div> </div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <div dir="ltr" style="text-align: left;" trbidi="on"> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="font-family: Arial; font-size: 11pt; white-space: pre-wrap;">Lately we've seen an increase in spammy links contained in articles referred to as contributor posts, guest posts, partner posts, or syndicated posts. These articles are generally written by or in the name of one website, and published on a different one.</span></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <br /></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Google does not discourage these types of articles in the cases when they inform users, educate another site’s audience or bring awareness to your cause or company. However, what does violate </span><a href="https://support.google.com/webmasters/answer/66356?hl=en" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">Google's guidelines on link schemes</span></a><span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"> is when the main intent is to build links in a large-scale way back to the author’s site. Below are factors that, when taken to an extreme, can indicate when an article is in violation of these guidelines:</span></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <br /></div> <ul style="margin-bottom: 0pt; margin-top: 0pt;"> <li dir="ltr" style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; list-style-type: disc; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Stuffing keyword-rich links to your site in your articles</span></div> </li> <li dir="ltr" style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; list-style-type: disc; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Having the articles published across many different sites; alternatively, having a large number of articles on a few large, different sites</span></div> </li> <li dir="ltr" style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; list-style-type: disc; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Using or hiring article writers that aren’t knowledgeable about the topics they’re writing on</span></div> </li> <li dir="ltr" style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; list-style-type: disc; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Using the same or similar content across these articles; alternatively, duplicating the full content of articles found on your own site (in which case use of </span><a href="https://support.google.com/webmasters/answer/139066?hl=en" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">rel=”canonical”</span></a><span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">, in addition to </span><a href="https://support.google.com/webmasters/answer/96569?hl=en" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">rel=”nofollow”</span></a><span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">, is advised)</span></div> </li> </ul> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <br /></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">When Google detects that a website is publishing articles that contain spammy links, this may change Google's perception of the quality of the site and could affect its ranking. Sites accepting and publishing such articles should carefully vet them, asking questions like: Do I know this person? Does this person’s message fit with my site’s audience? Does the article contain useful content? If there are links of questionable intent in the article, has the author used </span><a href="https://support.google.com/webmasters/answer/96569?hl=en" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">rel=”nofollow”</span></a><span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"> on them?</span></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <br /></div> <span id="docs-internal-guid-f9feb677-40a1-a7c6-eebd-9af28d6a1455"></span><br /> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">For websites creating articles made for links, Google takes action on this behavior because it’s bad for the Web as a whole. When link building comes first, the quality of the articles can suffer and create a bad experience for users. Also, webmasters generally prefer not to receive aggressive or repeated "Post my article!" requests, and we encourage such cases to be reported to our </span><a href="https://www.google.com/webmasters/tools/spamreport?pli=1" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">spam report form</span></a><span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">. And lastly, if a link is a form of endorsement, and you’re the one creating most of the endorsements for your own site, is this putting forth the best impression of your site? Our best advice in relation to link building is to focus on improving your site’s content and everything--including links--will follow (no pun intended).</span></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"><br /></span></div> <div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"> <span style="background-color: transparent; color: black; font-family: Arial; font-size: 11pt; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"><span style="font-size: 14.6667px;">Posted by the Google Webspam Team</span></span></div> </div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:A reminder about links in large-scale article campaigns&url=https://webmasters.googleblog.com/2017/05/a-reminder-about-links-in-large-scale.html?hl=en&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2017/05/a-reminder-about-links-in-large-scale.html?hl=en'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2017/05/a-reminder-about-links-in-large-scale.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines?hl=en' rel='tag'> webmaster guidelines </a> </span> </div> </div> </div> <div class='blog-pager' id='blog-pager'> <a class='home-link' href='https://webmasters.googleblog.com/?hl=en'> <i class='material-icons'>  </i> </a> <span id='blog-pager-newer-link'> <a class='blog-pager-newer-link' href='https://webmasters.googleblog.com/search?updated-max=2018-04-04T04:59:00-07:00&max-results=7&reverse-paginate=true&hl=en' id='Blog1_blog-pager-newer-link' title='Newer Posts'> <i class='material-icons'>  </i> </a> </span> <span id='blog-pager-older-link'> <a class='blog-pager-older-link' href='https://webmasters.googleblog.com/search?updated-max=2017-05-25T10:23:00-07:00&max-results=7&hl=en' id='Blog1_blog-pager-older-link' title='Older Posts'> <i class='material-icons'>  </i> </a> </span> </div> <div class='clear'></div> </div></div> </div> </div> <div class='col-right'> <div class='section' id='sidebar-top'><div class='widget HTML' data-version='1' id='HTML9'> <div class='widget-content'> <a href="https://www.google.com/webmasters/tools/mobile-friendly/?utm_source=wmc-blog&utm_medium=referral&utm_campaign=blog-nav"><img src="https://lh3.googleusercontent.com/-osGJupx0-HY/VQta1nmaAPI/AAAAAAAACfs/UdMPzubsXFk/w80-h1368-no/blog%2Bpromo.png" align="left" width="80" /></a> Hey! <a href="https://search.google.com/test/mobile-friendly">Check here if your site is mobile-friendly.</a> </div> <div class='clear'></div> </div><div class='widget HTML' data-version='1' id='HTML10'> <div class='widget-content'> <div class='searchBox'> <input type='text' title='Search This Blog' placeholder='Search blog ...' /> </div> </div> <div class='clear'></div> </div></div> <div id='aside'> <div class='section' id='sidebar'><div class='widget Label' data-version='1' id='Label1'> <div class='tab'> <img class='sidebar-icon' src='data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAYpJREFUeNrs2aFuwzAQBmAvKRkMKRjZA4QMDJaWFgyMjuzFRg37DIUlA3uFkoGQSaWzJU+tpri5O9+l/zSfdFJlpe59yTmyVedq1PjfcZMZ70NuQnaF8w8htyE/rABtpviXkLcK88c5HhLkMBfgVan43zfFBNGMjHVGT/s55KP2pAvidbGHd+nzKt1RKSLG3rKF1iPFv6UWiPke8i7kEqGdGsI1O+LYVdqJAjgirwkKYD0ytkJBUNbAMvX8V3q9PhUsYvU1sWD8SO/sQvx2ahxOiNoJCSBCoAHYCEQAC4EKICOQASQEOmAS8RcAFxFN5hiIiugpgC3wk9hQAHH/70EBHXUN7IER5EWMiBgo2+nzOKQv9SCAeEM/OQAkhE/ncccFICB87qzQMia5FsJfOui0zMnmRvipU1ormHQuxGTxUsAcCFLxJQBLBLn4UoAFglW8BkATwS5eC6CBEBWvCShBiIvXBkgQRcVbADiI4uKtABSESvGWgB9EzHt3+tNwyO0qa9SoIYtvAQYAqDJhaWWeMecAAAAASUVORK5CYII='/> <h2> Labels </h2> <i class='material-icons arrow'>  </i> </div> <div class='widget-content list-label-widget-content'> <ul> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/accessibility?hl=en'> accessibility </a> <span dir='ltr'> 10 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/advanced?hl=en'> advanced </a> <span dir='ltr'> 195 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/AMP?hl=en'> AMP </a> <span dir='ltr'> 13 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Android?hl=en'> Android </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/API?hl=en'> API </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/apps?hl=en'> apps </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/autocomplete?hl=en'> autocomplete </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/beginner?hl=en'> beginner </a> <span dir='ltr'> 173 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/CAPTCHA?hl=en'> CAPTCHA </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Chrome?hl=en'> Chrome </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/cms?hl=en'> cms </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en'> crawling and indexing </a> <span dir='ltr'> 158 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/encryption?hl=en'> encryption </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/events?hl=en'> events </a> <span dir='ltr'> 51 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=en'> feedback and communication </a> <span dir='ltr'> 83 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/forums?hl=en'> forums </a> <span dir='ltr'> 5 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/general%20tips?hl=en'> general tips </a> <span dir='ltr'> 90 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/geotargeting?hl=en'> geotargeting </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20Assistant?hl=en'> Google Assistant </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20I%2FO?hl=en'> Google I/O </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20Images?hl=en'> Google Images </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20News?hl=en'> Google News </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hacked%20sites?hl=en'> hacked sites </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hangout?hl=en'> hangout </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hreflang?hl=en'> hreflang </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/https?hl=en'> https </a> <span dir='ltr'> 5 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/images?hl=en'> images </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/intermediate?hl=en'> intermediate </a> <span dir='ltr'> 205 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/interstitials?hl=en'> interstitials </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/javascript?hl=en'> javascript </a> <span dir='ltr'> 8 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/job%20search?hl=en'> job search </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/localization?hl=en'> localization </a> <span dir='ltr'> 21 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/malware?hl=en'> malware </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/mobile?hl=en'> mobile </a> <span dir='ltr'> 63 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en'> mobile-friendly </a> <span dir='ltr'> 14 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/nohacked?hl=en'> nohacked </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/performance?hl=en'> performance </a> <span dir='ltr'> 17 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/product%20expert?hl=en'> product expert </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/product%20experts?hl=en'> product experts </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/products%20and%20services?hl=en'> products and services </a> <span dir='ltr'> 63 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/questions?hl=en'> questions </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/ranking?hl=en'> ranking </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/recipes?hl=en'> recipes </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rendering?hl=en'> rendering </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Responsive%20Web%20Design?hl=en'> Responsive Web Design </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rich%20cards?hl=en'> rich cards </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rich%20results?hl=en'> rich results </a> <span dir='ltr'> 10 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en'> search console </a> <span dir='ltr'> 35 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20for%20beginners?hl=en'> search for beginners </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20queries?hl=en'> search queries </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en'> search results </a> <span dir='ltr'> 140 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/security?hl=en'> security </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/seo?hl=en'> seo </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/sitemaps?hl=en'> sitemaps </a> <span dir='ltr'> 46 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/speed?hl=en'> speed </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=en'> structured data </a> <span dir='ltr'> 33 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/summit?hl=en'> summit </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/TLDs?hl=en'> TLDs </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/url%20removals?hl=en'> url removals </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/UX?hl=en'> UX </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/verification?hl=en'> verification </a> <span dir='ltr'> 8 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/video?hl=en'> video </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en'> webmaster community </a> <span dir='ltr'> 24 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20forum?hl=en'> webmaster forum </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines?hl=en'> webmaster guidelines </a> <span dir='ltr'> 57 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en'> webmaster tools </a> <span dir='ltr'> 177 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmasters?hl=en'> webmasters </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/youtube%20channel?hl=en'> youtube channel </a> <span dir='ltr'> 6 </span> </li> </ul> <div class='clear'></div> </div> </div><div class='widget BlogArchive' data-version='1' id='BlogArchive1'> <div class='tab'> <i class='material-icons icon'>  </i> <h2> Archive </h2> <i class='material-icons arrow'>  </i> </div> <div class='widget-content'> <div id='ArchiveList'> <div id='BlogArchive1_ArchiveList'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/?hl=en'> 2020 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/?hl=en'> 2019 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/?hl=en'> 2018 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate 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/2017/?hl=en'> 2017 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate expanded'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/?hl=en'> 2016 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/?hl=en'> 2015 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/?hl=en'> 2014 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/?hl=en'> 2013 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/?hl=en'> 2012 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/?hl=en'> 2011 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/?hl=en'> 2010 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/?hl=en'> 2009 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/?hl=en'> 2008 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/?hl=en'> 2007 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/07/?hl=en'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/06/?hl=en'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/05/?hl=en'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/04/?hl=en'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/03/?hl=en'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/02/?hl=en'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/01/?hl=en'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/?hl=en'> 2006 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/12/?hl=en'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/11/?hl=en'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/10/?hl=en'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/09/?hl=en'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/08/?hl=en'> Aug </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> </div> </div> <div class='clear'></div> </div> </div><div class='widget HTML' data-version='1' id='HTML6'> <div class='widget-content'> <a href="https://googlewebmastercentral.blogspot.com/atom.xml"> <img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAihJREFUeNrsWa9Pw0AU7viRMDFRBAkzJDMIBIhJJhCzk7NILIqMv4AEhdz+BCY3OYssAlGBoAJREpZwAlHEBO8lr8nSvNeVbu1dyX3JlzTrXfa+u/e9d7c5joWFhYVO1Fa8PwH2gK6m+BRwAvSlAdsrgr8E1jUuMH73GTAEzrkBWymTewZlihhLmgDXIAFuHgGVQOUF7OSYM1p6PgTuA1vAZlUEvAnPdapcMY0VICECekQ0XRfYrqoHsAGNgXfAoMomRiFDEhOZkkL3S88hMaB2LwXp0bj+ps2edpToZpjfoIDQtBeU+xjoDzP2G/gCPKZ5f8WsCAFJoJgOCcFdWSTeL9YQMSvTA1h9BkI5jaiXhLpSCL/8mVZY0UpyJ9ZdOkniu1dmJ96BpzQu9w6s28gcOq9j6pwLdR8/36NK5CQKwJSMrb2MhhSglBpt4UjsrdsnNu0B3J0HCozbCc4TjyY2srEgos/4RQljCzNxl4ireQD8FOq+T+W0mTB2g7njhlR+Sy2jsXFvU658U8YTbeaGpdIu7mWkEAq5ZtIjIhFZdtfX7QHckSvB2B6zC3VdAkZk0kAQwaXTk/CzTXK3wjIExCs6ZJpTnE4uY1KV+KzFzA3KTiFPENHJkOPcsfpLhwe4btoSuvUqAR+6TOxlCE6ZfKUsJLgsqGW8OpqAGx2X+sLxrwUog+JUeQRMDBIwyXOcnlPtPnL0/UsT/8LnOxYWFhZG4leAAQAAQHEaYuzHbAAAAABJRU5ErkJggg==" class="sidebar-icon" /> <h2>Feed</h2> </a> </div> <div class='clear'></div> </div></div> <div class='section' id='sidebar-bottom'><div class='widget HTML' data-version='1' id='HTML5'> <div class='widget-content'> <div class='followgooglewrapper'> <script src="https://apis.google.com/js/plusone.js"></script></div> <div class="g-ytsubscribe class='followgooglewrapper'" data-channel="GoogleWebmasterHelp" data-layout="full"></div> <div class="share followgooglewrapper"> <button data-href="https://twitter.com/intent/follow?original_referer=https://googlewebmastercentral.blogspot.com/&screen_name=googlewmc" onclick='sharingPopup(this);' id='twitter-share'><span class="twitter-follow">Follow @googlewmc</span></button> <script> function sharingPopup (button) { var url = button.getAttribute("data-href"); window.open( url,'popUpWindow','height=500,width=500,left=10,top=10,resizable=yes,scrollbars=yes,toolbar=yes,menubar=no,location=no,directories=no,status=yes'); } </script> </div> </div> <div class='clear'></div> </div><div class='widget HTML' data-version='1' id='HTML1'> <div class='widget-content'> Give us feedback in our <a href="https://support.google.com/webmasters/go/community">Product Forums</a>. </div> <div class='clear'></div> </div><div class='widget HTML' data-version='1' id='HTML8'> <h2 class='title'> Subscribe via email </h2> <div class='widget-content'> <form #nsubmit="window.open('https://www.feedburner.com/fb/a/emailverifySubmit?feedId=1092589', 'popupwindow', 'scrollbars=yes,width=550,height=520');return true" action="https://www.feedburner.com/fb/a/emailverify" style="border:1px solid #ccc;padding:3px;text-align:center;" target="popupwindow" method="post"><p>Enter your email address:</p><p><input style="width:140px" name="email" type="text"/></p><input value="https://feeds.feedburner.com/~e?ffid=1092589" name="url" type="hidden"/><input value="Official Google Webmaster Central Blog" name="title" type="hidden"/><input value="en_US" name="loc" type="hidden"/><input value="Subscribe" type="submit"/><p>Delivered by <a href="https://www.feedburner.com" target="_blank">FeedBurner</a></p></form> </div> <div class='clear'></div> </div></div> </div> </div> <div style='clear:both;'></div> </div>  <div class='google-footer-outer loading'> <div id='google-footer'> <a href='//www.google.com/'> <img class='google-logo-dark' height='36' src='data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAALgAAABICAYAAABFoT/eAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAACLVJREFUeNrsXd+L20YQ3vOprdLqiMXFXE2qB7dcwEcTSB7ykIc+9A/PQx/yEMq1TWhNuYIpJriNr7XpmZ5IxFEvmW2EKs3Ornb1w50PxIFP0kiz387OzM6uhGAwGAxGP3Ho+f7x7ri1O7LdccPqZjSNA4dEHsLfaHcEFedJom93x9Xu2OyOFTcBo6sED3fHZHeMEELrkAHJF0B8Rr+gDFsZ5n0luLTQ95AXs4W06D/tjpR50xtM4CjD0y48YGB4rnyZxNOzyA7zBHr+nLnDaJLg0mo/ALekCasg3Z4XbM0ZdTEgnDPeHY8bIne+Qz2GvwyGNwsuyT218KWvIIBMcwGpLiipcolecjMxfBDchNyS1EvxLiOSIecp31q6IJ/C3yrIrMqMm4jhg+AxkdwbIO3aUO4KjqqMjCT3uaazMBhWBJfuxH3CtRfiXf66DhSRZWbmlMnNaILgZxrXJQO/eO3wORZwvwm4JUxuhheCjzVBYAbW1ces45YDSoZrFNOEE835M8FT6oyeEnws8Fz3QnBxFKPHBMem4GU+m6fPGb0leCTwWcM5B36MPgeZI01gudyDdw3hPeXfo8L/rmCUWnuMMdqUL2WqWeRbhf+twfVsO7YagZGNC79fw7OthEVtkiJ4jJzTd3KPwf3CRqhhiTu23AP5sl0/0xiwISQXpNwLIJK87mHF+U8ddzzdmgKlGzlPYjyxGJQouIhNT4k9AqWEFkqfguIvagTWbcq3KW1WE3xS3m8NtA9WS451xofwjKT5kkDoK/b6mDk5FfXr1lWDL4BofZEv2/SRsK/EHGlGdBdu8QNRb8HMCFwt7Yy3DDI/QP7fx5z3VLhdlJEIs4rKNuXXJXdxZPdB7kfCzWqwCO4V1LHgLjInX3tQ1KzCR52Cz+vDj1dydeRuS74rcvs2Pi6fT5H8OaaUQPQPYcWwRSGXyhhscn5dpAnEFMkuEZetbfkTAnlSuH4DxisE+aMGeJAQ3lFl7C4LJE6QWCaCd583ORQ1jYAwjFctal7nOs2ZZvicwvlZx+RHGrcoAwKUVX8uwcc/9TT65INeDOr5shL9LDRB6QTeIy3zwfdh3WOi6axLCEhSjXU7F3h6LqggUtvyJxpynwu8tDkD98fXApOxRj8zoZ9MnGveYVIVZKaGrkBXCY65BCYNN9NkjpKOyQ81Q79JgdxS+Jn3SDTEXRI7SWzaiSTB32oI3nU3BvMfM0urhOVYgwKhuiAfc4tM07wXwm1ZRoQYSl2NUwiu01fEAHVcpixd745FvVz4dzUUc0o8rwoLy8ZSwU6CyFx1RP5II9+1bFPEFs9HWbNLiimDXE+vCm7u1CS47cofzD3aEhVY57mxRo5zlqdt+RFC1JUH2S7bcVXg4liTMakaBZZVxiTICRoivcn1sEUBlk24JmaC6kxUbYmWoqvyfck2xZGGnDFYa9MMzkYQ1ijkCX6qidybrgePiQ0QIQqoi6qRLeqQfIoRsEHaQJLBdHOnLGetSdm/IPcymJuS1PAnbQPH0MOw/39C1vL11DiLOqIsbDI8QcHvGiLnySi2qUXBicaqUSxN5LEB0g7Jt3ENXJLPJ5S1tnaZBoWbpRqrmjRE7qHmpSmNHdQcYrEUadoh+TbBnc9ri7iycI1kzPeNcLDIvbiqXpez9Tmdq6zGREPuzECBoxrPMiI2WtvyNwhJba2wy3JZ6ky5dD1lSvmZS3e4SPA1wcf1VTFHKX+cGwZzdUYcqpvUtvwrD/InDttVlyZeAKlNN5MKbAiurHhKIPlUuJvlTCCiDjSKSCsUmCFWbGLZwCESfK07JB8LvMYWVtw0D00JEHV8Mq2HkqPbE0oHLvvK2g0o8ETg+4cfwTlZDT9JDoWygu4uQQE/ivIvtcnfPkaCqhiupz7jWOAzqL/vjtcdkv9G4MVMt+EaylfuImiPAXEUjRF3pjjaHiPPZ6If9TGGAO4ZY0am6jOCb+DQ+ZCqLkIpOIPrdNfIjnFPY6nyFut7TS/fanrziOBOKMupKw94WaLMtuVnSFt9CPrWWdJE6PeltCX432DEBoh+5Dv8RRhdis8YAv9uyq4/JAwtlEApgBe9Cw9xDD3tdk4Jn0MDfiHwPHcRPxBePCMER3GuIx7kGlv9fkZ4V9lolx2Uv4X7hEj7qJ3LDoAMGbTRMRibu4L2xQ8bgt8AyU+Q+x7nYrvDnH4iuO5LxKsYwPVbkPMvKF9Zky9wXzRfVWizi62r9X5VHf55h+WHhDjGBZ4WRhyTr6z5SlCoLMxLSpBZFsQ9F80uQFbF/6aFWi+Ev51vzzsuX+msyzuQXXjUz8zEBy+zpq9yweXAoxJW4JbYrDS6gYDqGHxPl+TKeiBfxj9/EBIElPYeOA4y8/qRQfknjvSzgRgtq0Pw/M1eQeMdOSb2Bnrhr6Led+1vcp2x7oTFHMnedFW+Ivlty062BUt74oHgSj+vHepnhunn0JJAMtBZgDI/qmGtMujRv8DDpo47zBJ8UtPOuAR/7rKn8t9AJ0tBdmBAmJ/Fu71yxp4I3qh+DhyRqbi5Y1ShVPlSb8X7bRNcfgZFl+WRGYo7uecrWq1r8X5bhmzP5OdlDwsGRm1suSxkg5rYm7ConyGQ3Zl+DgSD8V/kPwrWBMG9YcBtyShBnTLdTiHgttw7qAW7cqh/ZnmPKr/6ignOaKsdyxbsToT5UkPsW00bJjijDXficcX/JsLs6w2BwGtherdckH3w/kNXRPVI0OqJQoHX42/66IMfMj/2huRjxIidgKV/W0JS+bsstDoTeAHcrI8E5zTh/sDkqxL5rZup55/3USlswfcHf4IrQplVDgW9XFlOqnwr6pVPMMEZTuC60EttvdzbLbaZ4PsFVa3nohhO+vW+yn/ZB2fUhpysmQrzBcTSai9EszuZMcEZ1lCFVrp9zGXhm69iLyY4oxFIa178lPe12I/P2DAYDAaDwWAwGAwGg8FgMBgMBoPBYDD2Cf8IMADDRGoQTe+E9AAAAABJRU5ErkJggg==' style='margin-top: -16px;' width='92'/> </a> <ul> <li> <a href='//www.google.com/'> Google </a> </li> <li> <a href='//www.google.com/policies/privacy/'> Privacy </a> </li> <li> <a href='//www.google.com/policies/terms/'> Terms </a> </li> </ul> </div> </div> <script type='text/javascript'> //<![CDATA[ // Social sharing popups. var postEl = document.getElementsByClassName('social-wrapper'); var postCount = postEl.length; for(i=0; i<postCount;i++){ postEl[i].addEventListener("click", function(event){ var postUrl = this.getAttribute("data-href"); window.open( postUrl,'popUpWindow','height=500,width=500,left=10,top=10,resizable=yes,scrollbars=yes,toolbar=yes,menubar=no,location=no,directories=no,status=yes'); });} //]]> </script> <script type='text/javascript'> //<![CDATA[ var BreakpointHandler = function() { this.initted = false; this.isHomePage = false; this.isMobile = false; }; BreakpointHandler.prototype.finalizeSummary = function(summaryHtml, lastNode) { // Use $.trim for IE8 compatibility summaryHtml = $.trim(summaryHtml).replace(/(<br>|\s)+$/,''); if (lastNode.nodeType == 3) { var lastChar = summaryHtml.slice(-1); if (!lastChar.match(/[.”"?]/)) { if (!lastChar.match(/[A-Za-z]/)) { summaryHtml = summaryHtml.slice(0, -1); } summaryHtml += ' ...'; } } else if (lastNode.nodeType == 1 && (lastNode.nodeName == 'I' || lastNode.nodeName == 'A')) { summaryHtml += ' ...'; } return summaryHtml; }; BreakpointHandler.prototype.generateSummaryFromContent = function(content, numWords) { var seenWords = 0; var summaryHtml = ''; for (var i=0; i < content.childNodes.length; i++) { var node = content.childNodes[i]; var nodeText; if (node.nodeType == 1) { if (node.hasAttribute('data-about-pullquote')) { continue; } nodeText = node.textContent; if (nodeText === undefined) { // innerText for IE8 nodeText = node.innerText; } if (node.nodeName == 'DIV' || node.nodeName == 'B') { // Don't end early if we haven't seen enough words. if (seenWords < 10) { continue; } if (i > 0) { summaryHtml = this.finalizeSummary(summaryHtml, content.childNodes[i-1]); } break; } summaryHtml += node.outerHTML; } else if (node.nodeType == 3) { nodeText = node.nodeValue; summaryHtml += nodeText + ' '; } var words = nodeText.match(/\S+\s*/g); if (!words) { continue; } var remain = numWords - seenWords; if (words.length >= remain) { summaryHtml = this.finalizeSummary(summaryHtml, node); break; } seenWords += words.length; } return summaryHtml; }; BreakpointHandler.prototype.detect = function() { var match, pl = /\+/g, search = /([^&=]+)=?([^&]*)/g, decode = function (s) { return decodeURIComponent(s.replace(pl, " ")); }, query = window.location.search.substring(1); var urlParams = {}; while (match = search.exec(query)) urlParams[decode(match[1])] = decode(match[2]); this.isListPage = $('html').hasClass('list-page'); this.isMobile = urlParams['m'] === '1'; this.isHomePage = window.location.pathname == '/'; }; BreakpointHandler.prototype.initContent = function() { var self = this; $('.post').each(function(index) { var body = $(this).children('.post-body')[0]; var content = $(body).children('.post-content')[0]; $(content).addClass('post-original'); var data = $(content).children('script').html(); data = self.rewriteForSSL(data); // If exists, extract specified editor's preview. var match = data.match(/([\s\S]+?)<div data-is-preview.+?>([\s\S]+)<\/div>/m); if (match) { data = match[1]; } // Prevent big images from loading when they aren't needed. // This must be done as a pre-injection step, since image loading can't be // canceled once embedded into the DOM. if (self.isListPage && self.isMobile) { data = data.replace(/<(img|iframe) .+?>/g, ''); } // Insert template to be rendered as nodes. content.innerHTML = data; if (self.isListPage) { var summary = document.createElement('div'); $(summary).addClass('post-content'); $(summary).addClass('post-summary'); body.insertBefore(summary, content); if (match) { // Use provided summary. summary.innerHTML = match[2]; } else { // Generate a summary. // Summary generation relies on DOM, so it must occur after content is // inserted into the page. summary.innerHTML = self.generateSummaryFromContent(content, 30); } // Add read more link to summary. var titleAnchor = $(this).find('.title a')[0]; var link = titleAnchor.cloneNode(true); link.innerHTML = 'Read More'; $(link).addClass('read-more'); summary.appendChild(link); } }); // Firefox does not allow for proper styling of BR. if (navigator.userAgent.indexOf('Firefox') > -1) { $('.post-content br').replaceWith('<span class="space"></span>'); } $('.loading').removeClass('loading'); }; BreakpointHandler.prototype.process = function() { if (!this.initted) { var makeInsecureImageRegex = function(hosts) { var whitelist = hosts.join('|').replace(/\./g,'\\.'); // Normal image tags, plus input images (yes, this is possible!) return new RegExp('(<(img|input)[^>]+?src=("|\'))http:\/\/(' + whitelist +')', 'g'); }; this.sslImageRegex = makeInsecureImageRegex(BreakpointHandler.KNOWN_HTTPS_HOSTS); this.sslImageCurrentDomainRegex = makeInsecureImageRegex([window.location.hostname]); this.detect(); this.initContent(); this.initted = true; } }; BreakpointHandler.KNOWN_HTTPS_HOSTS = [ "www.google.org", "www.google.com", "services.google.com", "blogger.com", "draft.blogger.com", "www.blogger.com", "photos1.blogger.com", "photos2.blogger.com", "photos3.blogger.com", "blogblog.com", "img1.blogblog.com", "img2.blogblog.com", "www.blogblog.com", "www1.blogblog.com", "www2.blogblog.com", "0.bp.blogspot.com", "1.bp.blogspot.com", "2.bp.blogspot.com", "3.bp.blogspot.com", "4.bp.blogspot.com", "lh3.googleusercontent.com", "lh4.googleusercontent.com", "lh5.googleusercontent.com", "lh6.googleusercontent.com", "themes.googleusercontent.com", ]; BreakpointHandler.prototype.rewriteForSSL = function(html) { // Handle HTTP -> HTTPS source replacement of images, movies, and other embedded content. return html.replace(this.sslImageRegex, '$1https://$4') .replace(this.sslImageCurrentDomainRegex, '$1//$4') .replace(/(<(embed|iframe)[^>]+?src=("|'))http:\/\/([^"']*?(youtube|picasaweb\.google)\.com)/g, '$1https://$4') // Slideshow SWF takes a image host, so we need to rewrite that parameter. .replace(/(<embed[^>]+?feed=http(?=[^s]))/g, '$1s'); }; $(document).ready(function() { var handler = new BreakpointHandler(); handler.process(); // Top-level navigation. $(".BlogArchive .tab").click(function(ev) { ev.preventDefault(); $(this).parent().toggleClass('active'); $(this).siblings().slideToggle(300); }); $(".Label .tab").click(function(ev) { ev.preventDefault(); $(this).parent().toggleClass('active'); $(this).siblings().slideToggle(300); }); // Blog archive year expansion. $('.BlogArchive .intervalToggle').click(function(ev) { ev.preventDefault(); if ($(this).parent().hasClass('collapsed')) { $(this).parent().removeClass('collapsed'); $(this).parent().addClass('expanded'); } else { $(this).parent().removeClass('expanded'); $(this).parent().addClass('collapsed'); } }); // Reverse order of months. $('.BlogArchive .intervalToggle + div').each(function(_, items) { var year = $(this); year.children().each(function(_, month) { year.prepend(month); }); }); // Set anchors to open in new tab. $('.post-content img').parent().each(function(_, node) { if (node.nodeName == 'A') { $(this).attr('target', '_blank'); } }); // Process search requests. $('.searchBox input').on("keypress", function(ev) { if (ev.which == 13) { window.location.href = 'https://www.google.com/search?q=site%3A' + window.location.hostname + '%20' + encodeURIComponent ($(this).val()); } }); }); //]]> </script> <script type="text/javascript" src="https://www.blogger.com/static/v1/widgets/984859869-widgets.js"></script> <script type='text/javascript'> window['__wavt'] = 'AOuZoY4cWeuDs5bcauHie-cV_0tdV-46OA:1732409235986';_WidgetManager._Init('//draft.blogger.com/rearrange?blogID\x3d32069983','//webmasters.googleblog.com/2017/?hl\x3den','32069983'); _WidgetManager._SetDataContext([{'name': 'blog', 'data': {'blogId': '32069983', 'title': 'Official Google Webmaster Central Blog', 'url': 'https://webmasters.googleblog.com/2017/?hl\x3den', 'canonicalUrl': 'https://webmasters.googleblog.com/2017/', 'homepageUrl': 'https://webmasters.googleblog.com/?hl\x3den', 'searchUrl': 'https://webmasters.googleblog.com/search', 'canonicalHomepageUrl': 'https://webmasters.googleblog.com/', 'blogspotFaviconUrl': 'https://webmasters.googleblog.com/favicon.ico', 'bloggerUrl': 'https://draft.blogger.com', 'hasCustomDomain': true, 'httpsEnabled': true, 'enabledCommentProfileImages': false, 'gPlusViewType': 'FILTERED_POSTMOD', 'adultContent': false, 'analyticsAccountNumber': 'UA-18009-4', 'encoding': 'UTF-8', 'locale': 'en', 'localeUnderscoreDelimited': 'en', 'languageDirection': 'ltr', 'isPrivate': false, 'isMobile': false, 'isMobileRequest': false, 'mobileClass': '', 'isPrivateBlog': false, 'isDynamicViewsAvailable': true, 'feedLinks': '\x3clink rel\x3d\x22alternate\x22 type\x3d\x22application/atom+xml\x22 title\x3d\x22Official Google Webmaster Central Blog - Atom\x22 href\x3d\x22https://webmasters.googleblog.com/feeds/posts/default\x22 /\x3e\n\x3clink rel\x3d\x22alternate\x22 type\x3d\x22application/rss+xml\x22 title\x3d\x22Official Google Webmaster Central Blog - RSS\x22 href\x3d\x22https://webmasters.googleblog.com/feeds/posts/default?alt\x3drss\x22 /\x3e\n\x3clink rel\x3d\x22service.post\x22 type\x3d\x22application/atom+xml\x22 title\x3d\x22Official Google Webmaster Central Blog - Atom\x22 href\x3d\x22https://draft.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/da8f33dd880cc4f1', 'plusOneApiSrc': 'https://apis.google.com/js/platform.js', 'disableGComments': true, 'interstitialAccepted': false, 'sharing': {'platforms': [{'name': 'Get link', 'key': 'link', 'shareMessage': 'Get link', 'target': ''}, {'name': 'Facebook', 'key': 'facebook', 'shareMessage': 'Share to Facebook', 'target': 'facebook'}, {'name': 'BlogThis!', 'key': 'blogThis', 'shareMessage': 'BlogThis!', 'target': 'blog'}, {'name': 'X', 'key': 'twitter', 'shareMessage': 'Share to X', 'target': 'twitter'}, {'name': 'Pinterest', 'key': 'pinterest', 'shareMessage': 'Share to Pinterest', 'target': 'pinterest'}, {'name': 'Email', 'key': 'email', 'shareMessage': 'Email', 'target': 'email'}], 'disableGooglePlus': true, 'googlePlusShareButtonWidth': 0, 'googlePlusBootstrap': '\x3cscript type\x3d\x22text/javascript\x22\x3ewindow.___gcfg \x3d {\x27lang\x27: \x27en\x27};\x3c/script\x3e'}, 'hasCustomJumpLinkMessage': false, 'jumpLinkMessage': 'Read more', 'pageType': 'archive', 'pageName': '2017', 'pageTitle': 'Official Google Webmaster Central Blog: 2017', 'metaDescription': 'Official news on crawling and indexing sites for the Google index'}}, {'name': 'features', 'data': {}}, {'name': 'messages', 'data': {'edit': 'Edit', 'linkCopiedToClipboard': 'Link copied to clipboard!', 'ok': 'Ok', 'postLink': 'Post Link'}}, {'name': 'template', 'data': {'name': 'custom', 'localizedName': 'Custom', 'isResponsive': false, 'isAlternateRendering': false, 'isCustom': true}}, {'name': 'view', 'data': {'classic': {'name': 'classic', 'url': '?view\x3dclassic'}, 'flipcard': {'name': 'flipcard', 'url': '?view\x3dflipcard'}, 'magazine': {'name': 'magazine', 'url': '?view\x3dmagazine'}, 'mosaic': {'name': 'mosaic', 'url': '?view\x3dmosaic'}, 'sidebar': {'name': 'sidebar', 'url': '?view\x3dsidebar'}, 'snapshot': {'name': 'snapshot', 'url': '?view\x3dsnapshot'}, 'timeslide': {'name': 'timeslide', 'url': '?view\x3dtimeslide'}, 'isMobile': false, 'title': 'Official Google Webmaster Central Blog', 'description': 'Official news on crawling and indexing sites for the Google index', 'url': 'https://webmasters.googleblog.com/2017/?hl\x3den', 'type': 'feed', 'isSingleItem': false, 'isMultipleItems': true, 'isError': false, 'isPage': false, 'isPost': false, 'isHomepage': false, 'isArchive': true, 'isLabelSearch': false, 'archive': {'year': 2017, 'rangeMessage': 'Showing posts from 2017'}}}]); _WidgetManager._RegisterWidget('_HeaderView', new _WidgetInfo('Header1', 'header', document.getElementById('Header1'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_BlogView', new _WidgetInfo('Blog1', 'main', document.getElementById('Blog1'), {'cmtInteractionsEnabled': false}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML9', 'sidebar-top', document.getElementById('HTML9'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML10', 'sidebar-top', document.getElementById('HTML10'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_LabelView', new _WidgetInfo('Label1', 'sidebar', document.getElementById('Label1'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_BlogArchiveView', new _WidgetInfo('BlogArchive1', 'sidebar', document.getElementById('BlogArchive1'), {'languageDirection': 'ltr', 'loadingMessage': 'Loading\x26hellip;'}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML6', 'sidebar', document.getElementById('HTML6'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML5', 'sidebar-bottom', document.getElementById('HTML5'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML1', 'sidebar-bottom', document.getElementById('HTML1'), {}, 'displayModeFull')); _WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML8', 'sidebar-bottom', document.getElementById('HTML8'), {}, 'displayModeFull')); </script> </body> </html>