CINXE.COM

<!DOCTYPE html> <html class='v2 list-page' dir='ltr' itemscope='' itemtype='http://schema.org/Blog' lang='en-US' xmlns='http://www.w3.org/1999/xhtml' xmlns:b='http://www.google.com/2005/gml/b' xmlns:data='http://www.google.com/2005/gml/data' xmlns:expr='http://www.google.com/2005/gml/expr'> <head> <link href='https://www.blogger.com/static/v1/widgets/3566091532-css_bundle_v2.css' rel='stylesheet' type='text/css'/> <title> Official Google Webmaster Central Blog: 2006 </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/2006/' 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/2006/' rel='canonical'/> <link rel="alternate" type="application/atom+xml" title="Official Google Webmaster Central Blog - Atom" href="https://webmasters.googleblog.com/feeds/posts/default" /> <link rel="alternate" type="application/rss+xml" title="Official Google Webmaster Central Blog - RSS" href="https://webmasters.googleblog.com/feeds/posts/default?alt=rss" /> <link rel="service.post" type="application/atom+xml" title="Official Google Webmaster Central Blog - Atom" href="https://www.blogger.com/feeds/32069983/posts/default" />  <meta content='Official news on crawling and indexing sites for the Google index' name='description'/> <meta content='https://webmasters.googleblog.com/2006/' property='og:url'/> <meta content='Official Google Webmaster Central Blog' property='og:title'/> <meta content='Official news on crawling and indexing sites for the Google index' property='og:description'/>  <base target='_self'/> <style> html { font-family: Roboto, sans-serif; -moz-osx-font-smoothing: grayscale; -webkit-font-smoothing: antialiased; } body { padding: 0; /* This ensures that the scroll bar is always present, which is needed */ /* because content render happens after page load; otherwise the header */ /* would "bounce" in-between states. */ min-height: 150%; } h2 { font-size: 16px; } h1, h2, h3, h4, h5 { line-height: 2em; } html, h4, h5, h6 { font-size: 14px; } a, a:visited { color: #4184F3; text-decoration: none; } a:focus, a:hover, a:active { text-decoration: none; } .Header { margin-top: 15px; } .Header h1 { font-size: 32px; font-weight: 300; line-height: 32px; height: 42px; } .header-inner .Header .titlewrapper { padding: 0; margin-top: 30px; } .header-inner .Header .descriptionwrapper { padding: 0; margin: 0; } .cols-wrapper { margin-top: 56px; } .header-outer, .cols-wrapper, .footer-outer, .google-footer-outer { padding: 0 60px; } .header-inner { height: 256px; position: relative; } html, .header-inner a { color: #212121; color: rgba(0,0,0,.87); } .header-inner .google-logo { display: inline-block; background-size: contain; z-index: 1; height: 46px; overflow: hidden; margin-top: 4px; margin-right: 8px; } .header-left { position: absolute; top: 50%; -webkit-transform: translateY(-50%); transform: translateY(-50%); margin-top: 12px; width: 100%; } .google-logo { margin-left: -4px; } #google-footer { position: relative; font-size: 13px; list-style: none; text-align: right; } #google-footer a { color: #444; } #google-footer ul { margin: 0; padding: 0; height: 144px; line-height: 144px; } #google-footer ul li { display: inline; } #google-footer ul li:before { color: #999; content: "\00b7"; font-weight: bold; margin: 5px; } #google-footer ul li:first-child:before { content: ''; } #google-footer .google-logo-dark { left: 0; margin-top: -16px; position: absolute; top: 50%; } /** Sitemap links. **/ .footer-inner-2 { font-size: 14px; padding-top: 42px; padding-bottom: 74px; } .footer-inner-2 .HTML h2 { color: #212121; color: rgba(0,0,0,.87); font-size: 14px; font-weight: 500; padding-left: 0; margin: 10px 0; } .footer-inner-2 .HTML ul { font-weight: normal; list-style: none; padding-left: 0; } .footer-inner-2 .HTML li { line-height: 24px; padding: 0; } .footer-inner-2 li a { color: rgba(65,132,243,.87); } /** Archive widget. **/ .BlogArchive { font-size: 13px; font-weight: normal; } .BlogArchive .widget-content { display: none; } .BlogArchive h2, .Label h2 { color: #4184F3; text-decoration: none; } .BlogArchive .hierarchy li { display: inline-block; } /* Specificity needed here to override widget CSS defaults. */ .BlogArchive #ArchiveList ul li, .BlogArchive #ArchiveList ul ul li { margin: 0; padding-left: 0; text-indent: 0; } .BlogArchive .intervalToggle { cursor: pointer; } .BlogArchive .expanded .intervalToggle .new-toggle { -ms-transform: rotate(180deg); transform: rotate(180deg); } .BlogArchive .new-toggle { float: right; padding-top: 3px; opacity: 0.87; } #ArchiveList { text-transform: uppercase; } #ArchiveList .expanded > ul:last-child { margin-bottom: 16px; } #ArchiveList .archivedate { width: 100%; } /* Months */ .BlogArchive .items { max-width: 150px; margin-left: -4px; } .BlogArchive .expanded .items { margin-bottom: 10px; overflow: hidden; } .BlogArchive .items > ul { float: left; height: 32px; } .BlogArchive .items a { padding: 0 4px; } .Label { font-size: 13px; font-weight: normal; } .sidebar-icon { display: inline-block; width: 24px; height: 24px; vertical-align: middle; margin-right: 12px; margin-top: -1px } .Label a { margin-right: 4px; } .Label .widget-content { display: none; } .FollowByEmail { font-size: 13px; font-weight: normal; } .FollowByEmail h2 { background: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABEAAAALCAYAAACZIGYHAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAUBJREFUeNrMkSGLAlEUhb+ZB4JFi8mx2cz+ApvhRUGTcUCrNqNJDYIi+DO0GUwmQXDK2DSIoGgZcSaIjDrzwrK4ssvChj1w0733O+fdp+m6PozH4yQSCfb7Pa7r8pOi0SjJZBLP8zgej4gAIMvlMuPxmADIYrHger1+C6lUKmo+NJ/NZojb7SZDWiwWo1qtks1msW2bw+HwZdkwDHq9HvV6nel0SqvVYrvdIh6Ph3Qch+VyqRYLhQJSSjRNw7IsfN9XgGKxSLfbJZfL0e/3aTabrFYr7vc7IujLcOh8PqunrNdr0uk0pVKJVCpFJBJRgEajweVyod1uMxgM2O12BAGUgRbU8DV2JpOhVquRz+cRQii3+XxOp9NRN3jVR5LPOp1OjEYjlSL8hclkgmmabDabt4d+m+S30vkD/R/IU4ABAPTZgnZdmG/PAAAAAElFTkSuQmCC"); background-repeat: no-repeat; background-position: 0 50%; text-indent: 30px; } .FollowByEmail .widget-content { display: none; } .searchBox input { border: 1px solid #eee; color: #212121; color: rgba(0,0,0,.87); font-size: 14px; padding: 8px 8px 8px 40px; width: 164px; font-family: Roboto, sans-serif; background: url("https://www.gstatic.com/images/icons/material/system/1x/search_grey600_24dp.png") 8px center no-repeat; } .searchBox ::-webkit-input-placeholder { /* WebKit, Blink, Edge */ color: rgba(0,0,0,.54); } .searchBox :-moz-placeholder { /* Mozilla Firefox 4 to 18 */ color: #000; opacity: 0.54; } .searchBox ::-moz-placeholder { /* Mozilla Firefox 19+ */ color: #000; opacity: 0.54; } .searchBox :-ms-input-placeholder { /* Internet Explorer 10-11 */ color: #757575; } .widget-item-control { margin-top: 0px; } .section { margin: 0; padding: 0; } #sidebar-top { border: 1px solid #eee; } #sidebar-top > div { margin: 16px 0; } .widget ul { line-height: 1.6; } /*main post*/ .post { margin-bottom:30px; } #main .post .title { margin: 0; } #main .post .title a { color: #212121; color: rgba(0,0,0,.87); font-weight: normal; font-size: 24px; } #main .post .title a:hover { text-decoration:none; color:#4184F3; } .message, #main .post .post-header { margin: 0; padding: 0; } #main .post .post-header .caption, #main .post .post-header .labels-caption, #main .post .post-footer .caption, #main .post .post-footer .labels-caption { color: #444; font-weight: 500; } #main .tr-caption-container td { text-align: left; } #main .post .tr-caption { color: #757575; color: rgba(0,0,0,.54); display: block; max-width: 560px; padding-bottom: 20px; } #main .post .tr-caption-container { line-height: 24px; margin: -1px 0 0 0 !important; padding: 4px 0; text-align: left; } #main .post .post-header .published{ font-size:11px; font-weight:bold; } .post-header .publishdate { font-size: 17px; font-weight:normal; color: #757575; color: rgba(0,0,0,.54); } #main .post .post-footer{ font-size:12px; padding-bottom: 21px; } .label-footer { margin-bottom: 12px; margin-top: 12px; } .comment-img { margin-right: 16px; opacity: 0.54; vertical-align: middle; } #main .post .post-header .published { margin-bottom: 40px; margin-top: -2px; } .post .post-content { color: #212121; color: rgba(0,0,0,.87); font-size: 17px; margin: 25px 0 36px 0; line-height: 32px; } .post-body .post-content ul, .post-body .post-content ol { margin: 16px 0; padding: 0 48px; } .post-summary { display: none; } /* Another old-style caption. */ .post-content div i, .post-content div + i { font-size: 14px; font-style: normal; color: #757575; color: rgba(0,0,0,.54); display: block; line-height: 24px; margin-bottom: 16px; text-align: left; } /* Another old-style caption (with link) */ .post-content a > i { color: #4184F3 !important; } /* Old-style captions for images. */ .post-content .separator + div:not(.separator) { margin-top: -16px; } /* Capture section headers. */ .post-content br + br + b, .post-content .space + .space + b, .post-content .separator + b { display: inline-block; margin-bottom: 8px; margin-top: 24px; } .post-content li { line-height: 32px; } /* Override all post images/videos to left align. */ .post-content .separator, .post-content > div { text-align: left; } .post-content .separator > a, .post-content .separator > span { margin-left: 0 !important; } .post-content img { max-width: 100%; height: auto; width: auto; } .post-content .tr-caption-container img { margin-bottom: 12px; } .post-content iframe, .post-content embed { max-width: 100%; } .post-content .carousel-container { margin-bottom: 48px; } #main .post-content b { font-weight: 500; } /* These are the main paragraph spacing tweaks. */ #main .post-content br { content: ' '; display: block; padding: 4px; } .post-content .space { display: block; height: 8px; } .post-content iframe + .space, .post-content iframe + br { padding: 0 !important; } #main .post .jump-link { margin-bottom:10px; } .post-content img, .post-content iframe { margin: 30px 0 20px 0; } .post-content > img:first-child, .post-content > iframe:first-child { margin-top: 0; } .col-right .section { padding: 0 16px; } #aside { background:#fff; border:1px solid #eee; border-top: 0; } #aside .widget { margin:0; } #aside .widget h2, #ArchiveList .toggle + a.post-count-link { color: #212121; color: rgba(0,0,0,.87); font-weight: 400 !important; margin: 0; } #ArchiveList .toggle { float: right; } #ArchiveList .toggle .material-icons { padding-top: 4px; } #sidebar .tab { cursor: pointer; } #sidebar .tab .arrow { display: inline-block; float: right; } #sidebar .tab .icon { display: inline-block; vertical-align: top; height: 24px; width: 24px; margin-right: 13px; margin-left: -1px; margin-top: 1px; color: #757575; color: rgba(0,0,0,.54); } #sidebar .widget-content > :first-child { padding-top: 8px; } #sidebar .active .tab .arrow { -ms-transform: rotate(180deg); transform: rotate(180deg); } #sidebar .arrow { color: #757575; color: rgba(0,0,0,.54); } #sidebar .widget h2 { font-size: 14px; line-height: 24px; display: inline-block; } #sidebar .widget .BlogArchive { padding-bottom: 8px; } #sidebar .widget { border-bottom: 1px solid #eee; box-shadow: 0px 1px 0 white; margin-bottom: 0; padding: 14px 0; min-height: 20px; } #sidebar .widget:last-child { border-bottom: none; box-shadow: none; margin-bottom: 0; } #sidebar ul { margin: 0; padding: 0; } #sidebar ul li { list-style:none; padding:0; } #sidebar ul li a { line-height: 32px; } #sidebar .archive { background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAYCAYAAADzoH0MAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAE1JREFUeNpiNDY23s9AAWBioBCwYBM8c+YMVsUmJibEGYBNMS5DaeMFfDYSZQA2v9I3FrB5AZeriI4FmnrBccCT8mhmGs1MwyAzAQQYAKEWG9zm9QFEAAAAAElFTkSuQmCC"); height: 24px; line-height: 24px; padding-left: 30px; } #sidebar .labels { background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABEAAAARCAYAAAA7bUf6AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAUxJREFUeNpiNDY23s9AAMycOfM7UF05kHkZmzwTMkdSUhKrIcXFxZy3bt3qBjIN8RrS09PDsHnzZjCNDr58+cKQlpbGDjSoHcg1w2oIyAUODg5gARCNzUVIBrUCuVYYhjx//pzhwIEDYAEQDeJjA1CDWIAGNQK59jBxRuSABbkAlwHIgIeHh2HWrFn/1NTU2oDcvSgBS4wBSC5iArqoCsj1YGIgEyAZVMoEchqlBjEB/cZAiUHg2AEGznpKDAImxOeM////B4VLKtBvEUCngZ1ILKivr3/u6+ubBzJAGZQ9gC5aQoqLgAY8BhkAZL4BuQQkxgXE34A4BuiiZEIuAhrwEGhAEZD5DpzYoIaA2UAM4kQADUrHZRDUgAIg8wO2XAwzbQXQa5OweQ1owB10AyA6gS7BgX1u3ry5397eHow3bdo0EyjGi00tQIABANPgyAH1q1eaAAAAAElFTkSuQmCC"); height: 20px; line-height: 20px; padding-left: 30px; } #sidebar .rss a { background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABIAAAASCAYAAABWzo5XAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAX5JREFUeNqsVDGSgkAQHL2rIiIikohIc/EBRkbwAIwuwgfwAXiAD9AHSI7kEkECRCb6AIyINDLx7K0aa6kT7uq0q7YYtnZ7umdnt7darXbr9Zpegeu61DNNc0dvwCcH4/GYJpMJnc9nOhwOVJbl/4hAAokMECZJQtvt9k+kH7qufyEYDAakqqqYxFdRFBqNRmTbNg2HQ0rTlK7XayvR0xqBdDqdkuM4dE/0ULhYLOh4PHYrknG5XGi/31MYhuL/nkwonM1mlGUZ1XXdrsiyLGEDhY7juJEZ1u5tIixDGdYhmYw+B7CAzPP5nDabjdgIAgCksMX1832/3drtdqPT6SQWapomiGEFNkDEdpDMMAzK81ys/7XYy+XyoQgq2WoURSIJ2iIIgp/WZCCTvFm2wgeAU31aI3Q2GhIDMeB53qPYPIcm5VrxXIOIOxsDMStjVawAc1VViRgN22lNBiuQN3GR+SY07hpOoStmFQAKXRRFY93bnpG+fONfedi+BRgAbkS8Fxp7QQIAAAAASUVORK5CYII="); } #sidebar .subscription a { background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABEAAAALCAYAAACZIGYHAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAUBJREFUeNrMkSGLAlEUhb+ZB4JFi8mx2cz+ApvhRUGTcUCrNqNJDYIi+DO0GUwmQXDK2DSIoGgZcSaIjDrzwrK4ssvChj1w0733O+fdp+m6PozH4yQSCfb7Pa7r8pOi0SjJZBLP8zgej4gAIMvlMuPxmADIYrHger1+C6lUKmo+NJ/NZojb7SZDWiwWo1qtks1msW2bw+HwZdkwDHq9HvV6nel0SqvVYrvdIh6Ph3Qch+VyqRYLhQJSSjRNw7IsfN9XgGKxSLfbJZfL0e/3aTabrFYr7vc7IujLcOh8PqunrNdr0uk0pVKJVCpFJBJRgEajweVyod1uMxgM2O12BAGUgRbU8DV2JpOhVquRz+cRQii3+XxOp9NRN3jVR5LPOp1OjEYjlSL8hclkgmmabDabt4d+m+S30vkD/R/IU4ABAPTZgnZdmG/PAAAAAElFTkSuQmCC"); } #sidebar-bottom { background: #f5f5f5; border-top:1px solid #eee; } #sidebar-bottom .widget { border-bottom: 1px solid #e0e0e0; padding: 15px 0; text-align: center; } #sidebar-bottom > div:last-child { border-bottom: 0; } #sidebar-bottom .text { line-height: 20px; } /* Home, forward, and backward pagination. */ .blog-pager { border-top : 1px #e0e0e0 solid; padding-top: 10px; margin-top: 15px; text-align: right !important; } #blog-pager { margin-botom: 0; margin-top: -14px; padding: 16px 0 0 0; } #blog-pager a { display: inline-block; } .blog-pager i.disabled { opacity: 0.2 !important; } .blog-pager i { color: black; margin-left: 16px; opacity: 0.54; } .blog-pager i:hover, .blog-pager i:active { opacity: 0.87; } #blog-pager-older-link, #blog-pager-newer-link { float: none; } .gplus-profile { background-color: #fafafa; border: 1px solid #eee; overflow: hidden; width: 212px; } .gplus-profile-inner { margin-left: -1px; margin-top: -1px; } /* Sidebar follow buttons. */ .followgooglewrapper { padding: 12px 0 0 0; } .loading { visibility: hidden; } .detail-page .post-footer .cmt_iframe_holder { padding-top: 40px !important; } /** Desktop **/ @media (max-width: 900px) { .col-right { display: none; } .col-main { margin-right: 0; min-width: initial; } .footer-outer { display: none; } .cols-wrapper { min-width: initial; } .google-footer-outer { background-color: #f5f5f5; } } /** Tablet **/ @media (max-width: 712px) { .header-outer, .cols-wrapper, .footer-outer, .google-footer-outer { padding: 0 40px; } } /* An extra breakpoint accommodating for long blog titles. */ @media (max-width: 600px) { .header-left { height: 100%; top: inherit; margin-top: 0; -webkit-transform: initial; transform: initial; } .header-title { margin-top: 18px; } .header-inner .google-logo { height: 40px; margin-top: 3px; } .header-inner .google-logo img { height: 42px; } .header-title h2 { font-size: 32px; line-height: 40px; } .header-desc { bottom: 24px; position: absolute; } } /** Mobile/small desktop window; also landscape. **/ @media (max-width: 480px), (max-height: 480px) { .header-outer, .cols-wrapper, .footer-outer, .google-footer-outer { padding: 0 16px; } .cols-wrapper { margin-top: 0; } .post-header .publishdate, .post .post-content { font-size: 16px; } .post .post-content { line-height: 28px; margin-bottom: 30px; } .post { margin-top: 30px; } .byline-author { display: block; font-size: 12px; line-height: 24px; margin-top: 6px; } #main .post .title a { font-weight: 500; color: #4c4c4c; color: rgba(0,0,0,.70); } #main .post .post-header { padding-bottom: 12px; } #main .post .post-header .published { margin-bottom: -8px; margin-top: 3px; } .post .read-more { display: block; margin-top: 14px; } .post .tr-caption { font-size: 12px; } #main .post .title a { font-size: 20px; line-height: 30px; } .post-content iframe { /* iframe won't keep aspect ratio when scaled down. */ max-height: 240px; } .post-content .separator img, .post-content .tr-caption-container img, .post-content iframe { margin-left: -16px; max-width: inherit; width: calc(100% + 32px); } .post-content table, .post-content td { width: 100%; } #blog-pager { margin: 0; padding: 16px 0; } /** List page tweaks. **/ .list-page .post-original { display: none; } .list-page .post-summary { display: block; } .list-page .comment-container { display: none; } .list-page #blog-pager { padding-top: 0; border: 0; margin-top: -8px; } .list-page .label-footer { display: none; } .list-page #main .post .post-footer { border-bottom: 1px solid #eee; margin: -16px 0 0 0; padding: 0 0 20px 0; } .list-page .post .share { display: none; } /** Detail page tweaks. **/ .detail-page .post-footer .cmt_iframe_holder { padding-top: 32px !important; } .detail-page .label-footer { margin-bottom: 0; } .detail-page #main .post .post-footer { padding-bottom: 0; } .detail-page #comments { display: none; } } [data-about-pullquote], [data-is-preview], [data-about-syndication] { display: none; } </style> <noscript> <style> .loading { visibility: visible }</style> </noscript> <script type='text/javascript'> (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) })(window,document,'script','https://www.google-analytics.com/analytics.js','ga'); ga('create', 'UA-18009-4', 'auto', 'blogger'); ga('blogger.send', 'pageview'); </script> <link href='https://www.blogger.com/dyn-css/authorization.css?targetBlogID=32069983&zx=8855dad6-3029-4476-9a6a-423344a04200' media='none' onload='if(media!='all')media='all'' rel='stylesheet'/><noscript><link href='https://www.blogger.com/dyn-css/authorization.css?targetBlogID=32069983&zx=8855dad6-3029-4476-9a6a-423344a04200' rel='stylesheet'/></noscript> <meta name='google-adsense-platform-account' content='ca-host-pub-1556223355139109'/> <meta name='google-adsense-platform-domain' content='blogspot.com'/> </head> <body> <script type='text/javascript'> //<![CDATA[ var axel = Math.random() + ""; var a = axel * 10000000000000; document.write('<iframe src="https://2542116.fls.doubleclick.net/activityi;src=2542116;type=gblog;cat=googl0;ord=ord=' + a + '?" width="1" height="1" frameborder="0" style="display:none"></iframe>'); //]]> </script> <noscript> <img alt='' height='1' src='https://ad.doubleclick.net/ddm/activity/src=2542116;type=gblog;cat=googl0;ord=1?' width='1'/> </noscript>  <div class='header-outer'> <div class='header-inner'> <div class='section' id='header'><div class='widget Header' data-version='1' id='Header1'> <div class='header-left'> <div class='header-title'> <a class='google-logo' href='https://webmasters.googleblog.com/?hl=en_US'> <img height='50' src='https://www.gstatic.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png'/> </a> <a href='/'> <h2> Webmaster Central Blog </h2> </a> </div> <div class='header-desc'> Official news on crawling and indexing sites for the Google index </div> </div> </div></div> </div> </div>  <div class='cols-wrapper loading'> <div class='col-main-wrapper'> <div class='col-main'> <div class='section' id='main'><div class='widget Blog' data-version='1' id='Blog1'> <div class='post' data-id='116674159977298697' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/12/better-understanding-of-your-site.html?hl=en_US' itemprop='url' title='Better understanding of your site'> Better understanding of your site </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, December 21, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <a title="SES Chicago" href="http://googlewebmastercentral.blogspot.com/2006/12/come-and-see-us-at-search-engine.html">SES Chicago</a> was wonderful. Meeting so many of you made the trip absolutely perfect. It was as special as if (Chicago local) <a title="Oprah Winfrey" href="http://en.wikipedia.org/wiki/Oprah_Winfrey">Oprah </a>had joined us!<br /><br />While hanging out at the Google booth, I was often asked about how to take advantage of our <a title="webmaster tools" href="https://www.google.com/webmasters/tools/">webmaster tools</a>. For example, here's one tip on Common Words.<br /><br /><span style="font-weight: bold;">Common Words: Our prioritized listing of your site's content</span><br />The common words feature lists <span style="font-style: italic;">in order of priority</span> (from highest to lowest) the prevalent words we've found in your site, and in links to your site. (This information isn't available for subdirectories or subdomains.) Here are the steps to leveraging common words:<br /><br />1. Determine your website's key concepts. If it offers getaways to a cattle ranch in Wyoming, the key concepts may be "cattle ranch," "horseback riding," and "Wyoming."<br /><br />2. Verify that Google detected the same phrases you believe are of high importance. Login to webmaster tools, select your <a title="verified site" href="https://www.google.com/support/webmasters/bin/answer.py?answer=35153">verified site</a>, and choose <span style="font-weight: bold;">Page analysis</span> from the <span style="font-weight: bold;">Statistics </span>tab. Here, under "Common words in your site's content," we list the phrases detected from your site's content in order of prevalence. Do the common words lack any concepts you believe are important? Are they listing phrases that have little direct relevance to your site?<br /><br />2a. If you're missing important phrases, you should first review your content. Do you have solid, textual information that explains and relates to the key concepts of your site? If in the cattle-ranch example, "horseback riding" was absent from common words, you may then want to review the "activities" page of the site. Does it include mostly images, or only list a schedule of riding lessons, rather than conceptually relevant information?<br /><br />It may sound obvious, but if you want to rank for a certain set of keywords, but we don't even see those keyword phrases on your website, then ranking for those phrases will be difficult.<br /><span class="sg"></span><br />2b. When you see general, non-illustrative common words that don't relate helpfully to your site's content (e.g. a top listing of "driving directions" or "contact us"), then it may be beneficial to increase the ratio of relevant content on your site. (Although don't be too worried if you see a few of these common words, as long as you also see words that are relevant to your main topics.) In the cattle ranch example, you would give visitors "driving directions" and "contact us" information. However, if these general, non-illustrative terms surface as the highest-rated common words, or the entire list of common words is only these types of terms, then Google (and likely other search engines) could not find enough "meaty" content.<br /><br />2c. If you find that many of the common words still don't relate to your site, check out our blog post on <a title="unexpected common words" href="http://sitemaps.blogspot.com/2006/02/unexpected-common-words.html">unexpected common words</a>.<br /><br />3. Here are a few of our favorite posts on improving your site's content:<br /><a href="http://googlewebmastercentral.blogspot.com/2006/10/target-visitors-or-search-engines.html" title="Target visitors or search engines?">Target visitors or search engines?</a><br /><br /><a title="Improving your site's indexing and ranking" href="http://sitemaps.blogspot.com/2006/02/improving-your-sites-indexing-and.html">Improving your site's indexing and ranking</a><br /><br /><a title="NEW! SES Chicago - Using Images" href="http://googlewebmastercentral.blogspot.com/2006/12/ses-chicago-using-images.html">NEW! SES Chicago - Using Images</a><br /><br />4. Should you decide to update your content, please keep in mind that we will need to recrawl your site in order to recognize changes, and that this may take time. Of course, you can notify us of modifications by <a title="submitting Sitemap" href="https://www.google.com/support/webmasters/bin/topic.py?topic=8477">submitting a Sitemap</a>.<br /><br />Happy holidays from all of us on the Webmaster Central team!<br /><br /><table style="width: auto;"><tbody><tr><td><a href="//picasaweb.google.com/maileko/SESChicago/photo#5011109822457855298"><img src="//lh3.google.com/image/maileko/RYsJ1WISPUI/AAAAAAAAABI/HfQ_-Yme1rw/s288/DSC06525.jpg"></a></td></tr><tr><td>SES Chicago: Googlers Trevor Foucher, Adam Lasnik and Jonathan Simon</td></tr></tbody></table> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <a title="SES Chicago" href="http://googlewebmastercentral.blogspot.com/2006/12/come-and-see-us-at-search-engine.html">SES Chicago</a> was wonderful. Meeting so many of you made the trip absolutely perfect. It was as special as if (Chicago local) <a title="Oprah Winfrey" href="http://en.wikipedia.org/wiki/Oprah_Winfrey">Oprah </a>had joined us!<br /><br />While hanging out at the Google booth, I was often asked about how to take advantage of our <a title="webmaster tools" href="https://www.google.com/webmasters/tools/">webmaster tools</a>. For example, here's one tip on Common Words.<br /><br /><span style="font-weight: bold;">Common Words: Our prioritized listing of your site's content</span><br />The common words feature lists <span style="font-style: italic;">in order of priority</span> (from highest to lowest) the prevalent words we've found in your site, and in links to your site. (This information isn't available for subdirectories or subdomains.) Here are the steps to leveraging common words:<br /><br />1. Determine your website's key concepts. If it offers getaways to a cattle ranch in Wyoming, the key concepts may be "cattle ranch," "horseback riding," and "Wyoming."<br /><br />2. Verify that Google detected the same phrases you believe are of high importance. Login to webmaster tools, select your <a title="verified site" href="https://www.google.com/support/webmasters/bin/answer.py?answer=35153">verified site</a>, and choose <span style="font-weight: bold;">Page analysis</span> from the <span style="font-weight: bold;">Statistics </span>tab. Here, under "Common words in your site's content," we list the phrases detected from your site's content in order of prevalence. Do the common words lack any concepts you believe are important? Are they listing phrases that have little direct relevance to your site?<br /><br />2a. If you're missing important phrases, you should first review your content. Do you have solid, textual information that explains and relates to the key concepts of your site? If in the cattle-ranch example, "horseback riding" was absent from common words, you may then want to review the "activities" page of the site. Does it include mostly images, or only list a schedule of riding lessons, rather than conceptually relevant information?<br /><br />It may sound obvious, but if you want to rank for a certain set of keywords, but we don't even see those keyword phrases on your website, then ranking for those phrases will be difficult.<br /><span class="sg"></span><br />2b. When you see general, non-illustrative common words that don't relate helpfully to your site's content (e.g. a top listing of "driving directions" or "contact us"), then it may be beneficial to increase the ratio of relevant content on your site. (Although don't be too worried if you see a few of these common words, as long as you also see words that are relevant to your main topics.) In the cattle ranch example, you would give visitors "driving directions" and "contact us" information. However, if these general, non-illustrative terms surface as the highest-rated common words, or the entire list of common words is only these types of terms, then Google (and likely other search engines) could not find enough "meaty" content.<br /><br />2c. If you find that many of the common words still don't relate to your site, check out our blog post on <a title="unexpected common words" href="http://sitemaps.blogspot.com/2006/02/unexpected-common-words.html">unexpected common words</a>.<br /><br />3. Here are a few of our favorite posts on improving your site's content:<br /><a href="http://googlewebmastercentral.blogspot.com/2006/10/target-visitors-or-search-engines.html" title="Target visitors or search engines?">Target visitors or search engines?</a><br /><br /><a title="Improving your site's indexing and ranking" href="http://sitemaps.blogspot.com/2006/02/improving-your-sites-indexing-and.html">Improving your site's indexing and ranking</a><br /><br /><a title="NEW! SES Chicago - Using Images" href="http://googlewebmastercentral.blogspot.com/2006/12/ses-chicago-using-images.html">NEW! SES Chicago - Using Images</a><br /><br />4. Should you decide to update your content, please keep in mind that we will need to recrawl your site in order to recognize changes, and that this may take time. Of course, you can notify us of modifications by <a title="submitting Sitemap" href="https://www.google.com/support/webmasters/bin/topic.py?topic=8477">submitting a Sitemap</a>.<br /><br />Happy holidays from all of us on the Webmaster Central team!<br /><br /><table style="width: auto;"><tbody><tr><td><a href="//picasaweb.google.com/maileko/SESChicago/photo#5011109822457855298"><img src="//lh3.google.com/image/maileko/RYsJ1WISPUI/AAAAAAAAABI/HfQ_-Yme1rw/s288/DSC06525.jpg"></a></td></tr><tr><td>SES Chicago: Googlers Trevor Foucher, Adam Lasnik and Jonathan Simon</td></tr></tbody></table> <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 understanding of your site&url=https://webmasters.googleblog.com/2006/12/better-understanding-of-your-site.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/12/better-understanding-of-your-site.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/12/better-understanding-of-your-site.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en_US' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='116648094361121770' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/12/deftly-dealing-with-duplicate-content.html?hl=en_US' itemprop='url' title='Deftly dealing with duplicate content'> Deftly dealing with duplicate content </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Monday, December 18, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> At the recent Search Engine Strategies conference in freezing Chicago, many of us Googlers were asked questions about duplicate content. We recognize that there are many nuances and a bit of confusion on the topic, so we'd like to help set the record straight.<br /><br /><span style="font-size:130%;"><span style="font-weight: bold;"> What is duplicate content?</span></span><br />Duplicate content generally refers to substantive blocks of content within or across domains that either completely match other content or are appreciably similar. Most of the time when we see this, it's unintentional or at least not malicious in origin: forums that generate both regular and stripped-down mobile-targeted pages, store items shown (and -- worse yet -- linked) via multiple distinct URLs, and so on. In some cases, content is duplicated across domains in an attempt to manipulate search engine rankings or garner more traffic via popular or long-tail queries.<br /><br /><span style="font-size:130%;"><span style="font-weight: bold;">What </span><span style="font-style: italic; font-weight: bold;">isn't </span><span style="font-weight: bold;">duplicate content?</span></span><br />Though we do offer <a href="http://translate.google.com/" title="a handy translation utility">a handy translation utility</a>, our algorithms won't view the same article written in English and Spanish as duplicate content. Similarly, you shouldn't worry about occasional snippets (quotes and otherwise) being flagged as duplicate content.<br /><br /><span style="font-size:130%;"><span style="font-weight: bold;"> Why does Google care about duplicate content?</span></span><br />Our users typically want to see a diverse cross-section of unique content when they do searches. In contrast, they're understandably annoyed when they see substantially the same content within a set of search results. Also, webmasters become sad when we show a complex URL (example.com/contentredir?value=shorty-george〈=en) instead of the pretty URL they prefer (example.com/en/shorty-george.htm).<br /><br /><span style="font-weight: bold;"><span style="font-size:130%;">What does Google do about it?</span><br /></span>During our crawling and when serving search results, we try hard to index and show pages with distinct information. This filtering means, for instance, that if your site has articles in "regular" and "printer" versions and neither set is blocked in robots.txt or via a noindex meta tag, we'll choose one version to list. In the rare cases in which we perceive that duplicate content may be shown with intent to manipulate our rankings and deceive our users, we'll also make appropriate adjustments in the indexing and ranking of the sites involved. However, we prefer to focus on filtering rather than ranking adjustments ... so in the vast majority of cases, the worst thing that'll befall webmasters is to see the "less desired" version of a page shown in our index.<br /><br /><span style="font-size:130%;"><span style="font-weight: bold;">How can Webmasters proactively address duplicate content issues?</span></span><br /><ul><li><span style="font-weight: bold;">Block appropriately: </span>Rather than letting our algorithms determine the "best" version of a document, you may wish to help guide us to your preferred version. For instance, if you don't want us to index the printer versions of your site's articles, disallow those directories or make use of regular expressions in your robots.txt file. </li><li> <span style="font-weight: bold;">Use 301s: </span>If you have restructured your site, use 301 redirects ("RedirectPermanent") in your .htaccess file to smartly redirect users, the Googlebot, and other spiders.<br /></li><li> <span style="font-weight: bold;">Be consistent: </span>Endeavor to keep your internal linking consistent; don't link to /page/ and /page and /page/index.htm.</li><li> <span style="font-weight: bold;">Use TLDs: </span>To help us serve the most appropriate version of a document, use top level domains whenever possible to handle country-specific content. We're more likely to know that .de indicates Germany-focused content, for instance, than /de or de.example.com.</li><li><span style="font-weight: bold;">Syndicate carefully: </span>If you syndicate your content on other sites, make sure they include a link back to the original article on each syndicated article. Even with that, note that we'll always show the (unblocked) version we think is most appropriate for users in each given search, which may or may not be the version you'd prefer. </li><li><span style="font-weight: bold;">Use the preferred domain feature of webmaster tools: </span>If other sites link to yours using both the www and non-www version of your URLs, you can let us know which way you prefer your site to be indexed.<br /> <span style="font-weight: bold;"></span></li><li><span style="font-weight: bold;">Minimize boilerplate repetition: </span>For instance, instead of including lengthy copyright text on the bottom of every page, include a very brief summary and then link to a page with more details. </li><li> <span style="font-weight: bold;"> Avoid publishing stubs: </span>Users don't like seeing "empty" pages, so avoid placeholders where possible. This means not publishing (or at least blocking) pages with zero reviews, no real estate listings, etc., so users (and bots) aren't subjected to a zillion instances of "Below you'll find a superb list of all the great rental opportunities in [insert cityname]..." with no actual listings.</li><li> <span style="font-weight: bold;">Understand your CMS: </span>Make sure you're familiar with how content is displayed on your Web site, particularly if it includes a blog, a forum, or related system that often shows the same content in multiple formats.</li><li> <span style="font-weight: bold;">Don't worry be happy: </span>Don't fret too much about sites that scrape (misappropriate and republish) your content. Though annoying, it's highly unlikely that such sites can negatively impact <span style="font-style: italic;">your</span> site's presence in Google. If you do spot a case that's particularly frustrating, you are welcome to file a <a href="//www.google.com/dmca.html" title="DMCA request">DMCA request</a> to claim ownership of the content and have us deal with the rogue site. </li></ul><br />In short, a general awareness of duplicate content issues and a few minutes of thoughtful preventative maintenance should help you to help us provide users with unique and relevant content. <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> At the recent Search Engine Strategies conference in freezing Chicago, many of us Googlers were asked questions about duplicate content. We recognize that there are many nuances and a bit of confusion on the topic, so we'd like to help set the record straight.<br /><br /><span style="font-size:130%;"><span style="font-weight: bold;"> What is duplicate content?</span></span><br />Duplicate content generally refers to substantive blocks of content within or across domains that either completely match other content or are appreciably similar. Most of the time when we see this, it's unintentional or at least not malicious in origin: forums that generate both regular and stripped-down mobile-targeted pages, store items shown (and -- worse yet -- linked) via multiple distinct URLs, and so on. In some cases, content is duplicated across domains in an attempt to manipulate search engine rankings or garner more traffic via popular or long-tail queries.<br /><br /><span style="font-size:130%;"><span style="font-weight: bold;">What </span><span style="font-style: italic; font-weight: bold;">isn't </span><span style="font-weight: bold;">duplicate content?</span></span><br />Though we do offer <a href="http://translate.google.com/" title="a handy translation utility">a handy translation utility</a>, our algorithms won't view the same article written in English and Spanish as duplicate content. Similarly, you shouldn't worry about occasional snippets (quotes and otherwise) being flagged as duplicate content.<br /><br /><span style="font-size:130%;"><span style="font-weight: bold;"> Why does Google care about duplicate content?</span></span><br />Our users typically want to see a diverse cross-section of unique content when they do searches. In contrast, they're understandably annoyed when they see substantially the same content within a set of search results. Also, webmasters become sad when we show a complex URL (example.com/contentredir?value=shorty-george〈=en) instead of the pretty URL they prefer (example.com/en/shorty-george.htm).<br /><br /><span style="font-weight: bold;"><span style="font-size:130%;">What does Google do about it?</span><br /></span>During our crawling and when serving search results, we try hard to index and show pages with distinct information. This filtering means, for instance, that if your site has articles in "regular" and "printer" versions and neither set is blocked in robots.txt or via a noindex meta tag, we'll choose one version to list. In the rare cases in which we perceive that duplicate content may be shown with intent to manipulate our rankings and deceive our users, we'll also make appropriate adjustments in the indexing and ranking of the sites involved. However, we prefer to focus on filtering rather than ranking adjustments ... so in the vast majority of cases, the worst thing that'll befall webmasters is to see the "less desired" version of a page shown in our index.<br /><br /><span style="font-size:130%;"><span style="font-weight: bold;">How can Webmasters proactively address duplicate content issues?</span></span><br /><ul><li><span style="font-weight: bold;">Block appropriately: </span>Rather than letting our algorithms determine the "best" version of a document, you may wish to help guide us to your preferred version. For instance, if you don't want us to index the printer versions of your site's articles, disallow those directories or make use of regular expressions in your robots.txt file. </li><li> <span style="font-weight: bold;">Use 301s: </span>If you have restructured your site, use 301 redirects ("RedirectPermanent") in your .htaccess file to smartly redirect users, the Googlebot, and other spiders.<br /></li><li> <span style="font-weight: bold;">Be consistent: </span>Endeavor to keep your internal linking consistent; don't link to /page/ and /page and /page/index.htm.</li><li> <span style="font-weight: bold;">Use TLDs: </span>To help us serve the most appropriate version of a document, use top level domains whenever possible to handle country-specific content. We're more likely to know that .de indicates Germany-focused content, for instance, than /de or de.example.com.</li><li><span style="font-weight: bold;">Syndicate carefully: </span>If you syndicate your content on other sites, make sure they include a link back to the original article on each syndicated article. Even with that, note that we'll always show the (unblocked) version we think is most appropriate for users in each given search, which may or may not be the version you'd prefer. </li><li><span style="font-weight: bold;">Use the preferred domain feature of webmaster tools: </span>If other sites link to yours using both the www and non-www version of your URLs, you can let us know which way you prefer your site to be indexed.<br /> <span style="font-weight: bold;"></span></li><li><span style="font-weight: bold;">Minimize boilerplate repetition: </span>For instance, instead of including lengthy copyright text on the bottom of every page, include a very brief summary and then link to a page with more details. </li><li> <span style="font-weight: bold;"> Avoid publishing stubs: </span>Users don't like seeing "empty" pages, so avoid placeholders where possible. This means not publishing (or at least blocking) pages with zero reviews, no real estate listings, etc., so users (and bots) aren't subjected to a zillion instances of "Below you'll find a superb list of all the great rental opportunities in [insert cityname]..." with no actual listings.</li><li> <span style="font-weight: bold;">Understand your CMS: </span>Make sure you're familiar with how content is displayed on your Web site, particularly if it includes a blog, a forum, or related system that often shows the same content in multiple formats.</li><li> <span style="font-weight: bold;">Don't worry be happy: </span>Don't fret too much about sites that scrape (misappropriate and republish) your content. Though annoying, it's highly unlikely that such sites can negatively impact <span style="font-style: italic;">your</span> site's presence in Google. If you do spot a case that's particularly frustrating, you are welcome to file a <a href="//www.google.com/dmca.html" title="DMCA request">DMCA request</a> to claim ownership of the content and have us deal with the rogue site. </li></ul><br />In short, a general awareness of duplicate content issues and a few minutes of thoughtful preventative maintenance should help you to help us provide users with unique and relevant content. <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:Deftly dealing with duplicate content&url=https://webmasters.googleblog.com/2006/12/deftly-dealing-with-duplicate-content.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/12/deftly-dealing-with-duplicate-content.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/12/deftly-dealing-with-duplicate-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/crawling%20and%20indexing?hl=en_US' rel='tag'> crawling and indexing </a> </span> </div> </div> </div> <div class='post' data-id='116621569245134199' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/12/building-link-based-popularity.html?hl=en_US' itemprop='url' title='Building link-based popularity'> Building link-based popularity </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Friday, December 15, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> Late in November we were at <a href="http://www.searchenginestrategies.com/sew/paris06/index.html">SES in Paris</a>, where we had the opportunity to meet some of the most prominent figures in the French SEO and SEM market. One of the issues that came up in sessions and in conversations was a certain confusion about how to most effectively increase the link-based popularity of a website. As a result we thought it might be helpful to clarify how search engines treat link spamming to increase a site´s popularity.<br /><br />This confusion lies in the common belief that there are two ways for optimizing the link-based popularity of your website: Either the meritocratic and long-term option of developing natural links or the risky and short-term option of non-earned backlinks via link spamming tactics such as buying links. We've always taken a clear stance with respect to manipulating the PageRank algorithm in our <a href="//www.google.com/support/webmasters/bin/answer.py?answer=35769">Quality Guidelines</a>. Despite these policies, the strategy of participating in link schemes might have previously paid off. But more recently, Google has tremendously refined its link-weighting algorithms. We have more people working on Google's link-weighting for quality control and to correct issues we find. So nowadays, undermining the PageRank algorithm is likely to result in the loss of the ability of link-selling sites to pass on reputation via links to other sites.<br /><br />Discounting non-earned links by search engines opened a new and wide field of tactics to build link-based popularity: Classically this involves optimizing your content so that thematically-related or trusted websites link to you by choice. A more recent method is <a href="http://www.mattcutts.com/blog/seo-advice-linkbait-and-linkbaiting/">link baiting</a>, which typically takes advantage of Web 2.0 social content websites. One example of this new way of generating links is to submit a handcrafted article to a service such as <a href="http://digg.com/">http://digg.com</a>. Another example is to earn a reputation in a certain field by building an authority through services such as <a href="http://answers.yahoo.com/">http://answers.yahoo.com</a>. Our general advice is: Always focus on the users and not on search engines when developing your optimization strategy. Ask yourself what creates value for your users. Investing in the quality of your content and thereby earning natural backlinks benefits both the users and drives more qualified traffic to your site.<br /><br />To sum up, even though improved algorithms have promoted a transition away from paid or exchanged links towards earned organic links, there still seems to be some confusion within the market about what the most effective link strategy is. So when taking advice from your SEO consultant, keep in mind that nowadays search engines reward sweat-of-the-brow work on content that bait natural links given by choice.<br /><br />In French / en Francais<br /><br /><b>Liens et popularité.<br /></b>[Translated by] Eric et Adrien, l’équipe de qualité de recherche.<br /><br />Les 28 et 29 Novembre dernier, nous étions à Paris pour assister à <a href="http://www.searchenginestrategies.com/sew/paris06/fr/index.html">SES</a>. Nous avons eu la chance de rencontrer les acteurs du référencement et du Web marketing en France. L’un des principaux points qui a été abordé au cours de cette conférence, et sur lequel il règne toujours une certaine confusion, concerne l’utilisation des liens dans le but d’augmenter la popularité d’un site. Nous avons pensé qu’il serait utile de clarifier le traitement réservé aux liens spam par les moteurs de recherche.<br /><br />Cette confusion vient du fait qu’un grand nombre de personnes pensent qu’il existe deux manières d’utiliser les liens pour augmenter la popularité de leurs sites. D’une part, l’option à long terme, basée sur le mérite, qui consiste à développer des liens de manière naturelle. D’autre part, l’option à court terme, plus risquée, qui consiste à obtenir des liens spam, tel les liens achetés. Nous avons toujours eu une position claire concernant les techniques visant à manipuler l’algorithme PageRank dans nos <a href="//www.google.com/support/webmasters/bin/answer.py?answer=35769">conseils aux webmasters</a>.<br /><br />Il est vrai que certaines de ces techniques ont pu fonctionner par le passé. Cependant, Google a récemment affiné les algorithmes qui mesurent l’importance des liens. Un plus grand nombre de personnes évaluent aujourd’hui la pertinence de ces liens et corrigent les problèmes éventuels. Désormais, les sites qui tentent de manipuler le Page Rank en vendant des liens peuvent voir leur habilité à transmettre leur popularité diminuer.<br /><br />Du fait que les moteurs de recherche ne prennent désormais en compte que les liens pertinents, de nouvelles techniques se sont développées pour augmenter la popularité d’un site Web. Il y a d’une part la manière classique, et légitime, qui consiste à optimiser son contenu pour obtenir des liens naturels de la part de sites aux thématiques similaires ou faisant autorité. Une technique plus récente, la pêche aux liens, (en Anglais « <a href="http://www.mattcutts.com/blog/seo-advice-linkbait-and-linkbaiting/">link baiting</a> »), consiste à utiliser à son profit certains sites Web 2.0 dont les contenus sont générés par les utilisateurs. Un exemple classique étant de soumettre un article soigneusement prépare à un site comme <a href="http://digg.com/">http://digg.com</a>. Un autre exemple consiste à acquérir un statut d’expert concernant un sujet précis, sur un site comme <a href="http://answers.yahoo.com/">http://answers.yahoo.com</a>. Notre conseil est simple : lorsque vous développez votre stratégie d’optimisation, pensez en premier lieu à vos utilisateurs plutôt qu’aux moteurs de recherche. Demandez-vous quelle est la valeur ajoutée de votre contenu pour vos utilisateurs. De cette manière, tout le monde y gagne : investir dans la qualité de votre contenu bénéficie à vos utilisateurs, cela vous permet aussi d’augmenter le nombre et la qualité des liens naturels qui pointent vers votre site, et donc, de mieux cibler vos visiteurs.<br /><br />En conclusion, bien que les algorithmes récents aient mis un frein aux techniques d’échanges et d’achats de liens au profit des liens naturels, il semble toujours régner une certaine confusion sur la stratégie à adopter. Gardez donc à l’esprit, lorsque vous demandez conseil à votre expert en référencement, que les moteurs de recherche récompensent aujourd’hui le travail apporté au contenu qui attire des liens naturels. <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> Late in November we were at <a href="http://www.searchenginestrategies.com/sew/paris06/index.html">SES in Paris</a>, where we had the opportunity to meet some of the most prominent figures in the French SEO and SEM market. One of the issues that came up in sessions and in conversations was a certain confusion about how to most effectively increase the link-based popularity of a website. As a result we thought it might be helpful to clarify how search engines treat link spamming to increase a site´s popularity.<br /><br />This confusion lies in the common belief that there are two ways for optimizing the link-based popularity of your website: Either the meritocratic and long-term option of developing natural links or the risky and short-term option of non-earned backlinks via link spamming tactics such as buying links. We've always taken a clear stance with respect to manipulating the PageRank algorithm in our <a href="//www.google.com/support/webmasters/bin/answer.py?answer=35769">Quality Guidelines</a>. Despite these policies, the strategy of participating in link schemes might have previously paid off. But more recently, Google has tremendously refined its link-weighting algorithms. We have more people working on Google's link-weighting for quality control and to correct issues we find. So nowadays, undermining the PageRank algorithm is likely to result in the loss of the ability of link-selling sites to pass on reputation via links to other sites.<br /><br />Discounting non-earned links by search engines opened a new and wide field of tactics to build link-based popularity: Classically this involves optimizing your content so that thematically-related or trusted websites link to you by choice. A more recent method is <a href="http://www.mattcutts.com/blog/seo-advice-linkbait-and-linkbaiting/">link baiting</a>, which typically takes advantage of Web 2.0 social content websites. One example of this new way of generating links is to submit a handcrafted article to a service such as <a href="http://digg.com/">http://digg.com</a>. Another example is to earn a reputation in a certain field by building an authority through services such as <a href="http://answers.yahoo.com/">http://answers.yahoo.com</a>. Our general advice is: Always focus on the users and not on search engines when developing your optimization strategy. Ask yourself what creates value for your users. Investing in the quality of your content and thereby earning natural backlinks benefits both the users and drives more qualified traffic to your site.<br /><br />To sum up, even though improved algorithms have promoted a transition away from paid or exchanged links towards earned organic links, there still seems to be some confusion within the market about what the most effective link strategy is. So when taking advice from your SEO consultant, keep in mind that nowadays search engines reward sweat-of-the-brow work on content that bait natural links given by choice.<br /><br />In French / en Francais<br /><br /><b>Liens et popularité.<br /></b>[Translated by] Eric et Adrien, l’équipe de qualité de recherche.<br /><br />Les 28 et 29 Novembre dernier, nous étions à Paris pour assister à <a href="http://www.searchenginestrategies.com/sew/paris06/fr/index.html">SES</a>. Nous avons eu la chance de rencontrer les acteurs du référencement et du Web marketing en France. L’un des principaux points qui a été abordé au cours de cette conférence, et sur lequel il règne toujours une certaine confusion, concerne l’utilisation des liens dans le but d’augmenter la popularité d’un site. Nous avons pensé qu’il serait utile de clarifier le traitement réservé aux liens spam par les moteurs de recherche.<br /><br />Cette confusion vient du fait qu’un grand nombre de personnes pensent qu’il existe deux manières d’utiliser les liens pour augmenter la popularité de leurs sites. D’une part, l’option à long terme, basée sur le mérite, qui consiste à développer des liens de manière naturelle. D’autre part, l’option à court terme, plus risquée, qui consiste à obtenir des liens spam, tel les liens achetés. Nous avons toujours eu une position claire concernant les techniques visant à manipuler l’algorithme PageRank dans nos <a href="//www.google.com/support/webmasters/bin/answer.py?answer=35769">conseils aux webmasters</a>.<br /><br />Il est vrai que certaines de ces techniques ont pu fonctionner par le passé. Cependant, Google a récemment affiné les algorithmes qui mesurent l’importance des liens. Un plus grand nombre de personnes évaluent aujourd’hui la pertinence de ces liens et corrigent les problèmes éventuels. Désormais, les sites qui tentent de manipuler le Page Rank en vendant des liens peuvent voir leur habilité à transmettre leur popularité diminuer.<br /><br />Du fait que les moteurs de recherche ne prennent désormais en compte que les liens pertinents, de nouvelles techniques se sont développées pour augmenter la popularité d’un site Web. Il y a d’une part la manière classique, et légitime, qui consiste à optimiser son contenu pour obtenir des liens naturels de la part de sites aux thématiques similaires ou faisant autorité. Une technique plus récente, la pêche aux liens, (en Anglais « <a href="http://www.mattcutts.com/blog/seo-advice-linkbait-and-linkbaiting/">link baiting</a> »), consiste à utiliser à son profit certains sites Web 2.0 dont les contenus sont générés par les utilisateurs. Un exemple classique étant de soumettre un article soigneusement prépare à un site comme <a href="http://digg.com/">http://digg.com</a>. Un autre exemple consiste à acquérir un statut d’expert concernant un sujet précis, sur un site comme <a href="http://answers.yahoo.com/">http://answers.yahoo.com</a>. Notre conseil est simple : lorsque vous développez votre stratégie d’optimisation, pensez en premier lieu à vos utilisateurs plutôt qu’aux moteurs de recherche. Demandez-vous quelle est la valeur ajoutée de votre contenu pour vos utilisateurs. De cette manière, tout le monde y gagne : investir dans la qualité de votre contenu bénéficie à vos utilisateurs, cela vous permet aussi d’augmenter le nombre et la qualité des liens naturels qui pointent vers votre site, et donc, de mieux cibler vos visiteurs.<br /><br />En conclusion, bien que les algorithmes récents aient mis un frein aux techniques d’échanges et d’achats de liens au profit des liens naturels, il semble toujours régner une certaine confusion sur la stratégie à adopter. Gardez donc à l’esprit, lorsque vous demandez conseil à votre expert en référencement, que les moteurs de recherche récompensent aujourd’hui le travail apporté au contenu qui attire des liens naturels. <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Building link-based popularity&url=https://webmasters.googleblog.com/2006/12/building-link-based-popularity.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/12/building-link-based-popularity.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/12/building-link-based-popularity.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/events?hl=en_US' rel='tag'> events </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines?hl=en_US' rel='tag'> webmaster guidelines </a> </span> </div> </div> </div> <div class='post' data-id='116614401823768816' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/12/ses-chicago-using-images.html?hl=en_US' itemprop='url' title='SES Chicago - Using Images'> SES Chicago - Using Images </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, December 14, 2006 </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-weight: bold;"></span>We all had a great time at <a href="http://www.searchenginestrategies.com/sew/chicago06/glance.html" title="SES Chicago">SES Chicago</a> last week, answering questions and getting feedback.<br /> <br /> One of the sessions I participated in was <a href="http://www.searchenginestrategies.com/sew/chicago06/agenda3.html#images" title="Images and Search Engines">Images and Search Engines</a>, and the panelists had great information about using images on your site, as well as on optimizing for Google Image search.<br /> <br /> <span style="font-weight: bold;">Ensuring visitors and search engines know what your content is about</span><br /> Images on a site are great -- but search engines can't read them, and not all visitors can. Make sure your site is accessible and can be understood by visitors viewing your site with images turned off in their browsers, on mobile devices, and with screen readers. If you do that, search engines won't have any trouble. Some things that you can do to ensure this:<br /> <br /> <ul> <li>Don't put the bulk of your text in images. It may sound simple, but the best thing you can do is to put your text into well, text. Reserve images for graphical elements. If all of the text on your page is in an image, it becomes inaccessible.</li> <li>Take advantage of alt tags for all of your images. Make sure the alt text is descriptive and unique. For instance, alt text such as "picture1" or "logo" doesn't provide much information about the image. "Charting the path of stock x" and "Company Y" give more details.</li> <li>Don't overload your alt text. Be descriptive, but don't stuff it with extra keywords.</li> <li>It's important to use alt text for any image on your pages, but if your company name, navigation, or other major elements of your pages are in images, alt text becomes especially important. Consider moving vital details to text to ensure all visitors can view them.</li> <li>Look at the image-to-text ratio on your page. How much text do you have? One way of looking at this is to look at your site with images turned off in your browser. What content can you see? Is the intent of your site obvious? Do the pages convey your message effectively?</li> </ul> <br /> <span style="font-weight: bold;">Taking advantage of Image search</span><br /> The panelists pointed out that shoppers often use Image search to see the things they want to buy. If you have a retail site, make sure that you have images of your products (and that they can be easily identified with alt text, headings, and textual descriptions). Searchers can then find your images and get to your site.<br /> <br /> One thing that can help your images be returned for results in Google Image search is opting in to <a href="//www.google.com/support/webmasters/bin/answer.py?answer=48367" title="enhanced image search">enhanced image search</a> in webmaster tools. This enables us to use your images in the <a href="http://images.google.com/imagelabeler/" title="Google Image Labeler">Google Image Labeler</a>, which harnesses the power of the community for adding metadata to your images.<br /> <br /> Someone asked if we have a maximum number of images per site that we accept for the Image Labeler. We don't. You can opt in no matter how many, or how few, images your site has.<br /> <br /> <b>Update:</b> <a href="http://support.google.com/webmasters/bin/answer.py?hl=en&answer=114016">More information on using images</a> can be found in our Help Center. </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-weight: bold;"></span>We all had a great time at <a href="http://www.searchenginestrategies.com/sew/chicago06/glance.html" title="SES Chicago">SES Chicago</a> last week, answering questions and getting feedback.<br /> <br /> One of the sessions I participated in was <a href="http://www.searchenginestrategies.com/sew/chicago06/agenda3.html#images" title="Images and Search Engines">Images and Search Engines</a>, and the panelists had great information about using images on your site, as well as on optimizing for Google Image search.<br /> <br /> <span style="font-weight: bold;">Ensuring visitors and search engines know what your content is about</span><br /> Images on a site are great -- but search engines can't read them, and not all visitors can. Make sure your site is accessible and can be understood by visitors viewing your site with images turned off in their browsers, on mobile devices, and with screen readers. If you do that, search engines won't have any trouble. Some things that you can do to ensure this:<br /> <br /> <ul> <li>Don't put the bulk of your text in images. It may sound simple, but the best thing you can do is to put your text into well, text. Reserve images for graphical elements. If all of the text on your page is in an image, it becomes inaccessible.</li> <li>Take advantage of alt tags for all of your images. Make sure the alt text is descriptive and unique. For instance, alt text such as "picture1" or "logo" doesn't provide much information about the image. "Charting the path of stock x" and "Company Y" give more details.</li> <li>Don't overload your alt text. Be descriptive, but don't stuff it with extra keywords.</li> <li>It's important to use alt text for any image on your pages, but if your company name, navigation, or other major elements of your pages are in images, alt text becomes especially important. Consider moving vital details to text to ensure all visitors can view them.</li> <li>Look at the image-to-text ratio on your page. How much text do you have? One way of looking at this is to look at your site with images turned off in your browser. What content can you see? Is the intent of your site obvious? Do the pages convey your message effectively?</li> </ul> <br /> <span style="font-weight: bold;">Taking advantage of Image search</span><br /> The panelists pointed out that shoppers often use Image search to see the things they want to buy. If you have a retail site, make sure that you have images of your products (and that they can be easily identified with alt text, headings, and textual descriptions). Searchers can then find your images and get to your site.<br /> <br /> One thing that can help your images be returned for results in Google Image search is opting in to <a href="//www.google.com/support/webmasters/bin/answer.py?answer=48367" title="enhanced image search">enhanced image search</a> in webmaster tools. This enables us to use your images in the <a href="http://images.google.com/imagelabeler/" title="Google Image Labeler">Google Image Labeler</a>, which harnesses the power of the community for adding metadata to your images.<br /> <br /> Someone asked if we have a maximum number of images per site that we accept for the Image Labeler. We don't. You can opt in no matter how many, or how few, images your site has.<br /> <br /> <b>Update:</b> <a href="http://support.google.com/webmasters/bin/answer.py?hl=en&answer=114016">More information on using images</a> can be found in our Help Center. </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:SES Chicago - Using Images&url=https://webmasters.googleblog.com/2006/12/ses-chicago-using-images.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/12/ses-chicago-using-images.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/12/ses-chicago-using-images.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en_US' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/events?hl=en_US' rel='tag'> events </a> </span> </div> </div> </div> <div class='post' data-id='116510048562502770' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/12/come-and-see-us-at-search-engine.html?hl=en_US' itemprop='url' title='Come and see us at Search Engine Strategies Chicago'> Come and see us at Search Engine Strategies Chicago </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Saturday, December 02, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <span style="font-weight: bold;"></span>If you're planning to be at <a title="SES Chicago" href="http://www.searchenginestrategies.com/sew/chicago06/index.html">SES Chicago</a> this week, be sure to stop by and say hi to the many Googlers who are coming out to brave the <a title="cold and snow" href="//www.google.com/search?q=weather+chicago">cold and snow</a>. Many of us will be on hand at the booth, speaking at sessions, and wandering the halls. Check out <a title="Search Engine Land" href="http://searchengineland.com/061201-084842.html">Search Engine Land</a> for tips on how to spot some of us and be sure to catch our sessions:<br /><br /><span style="font-weight: bold;">Monday, December 4th</span><br /><br /><a title="Drive traffic to your site with Google" href="http://www.searchenginestrategies.com/sew/chicago06/agenda.html#drive">Drive traffic to your site with Google</a><br />Jessica Ewing, Product Manager, Google Gadgets<br />Vanessa Fox, Product Manager, Webmaster Central<br />Shashi Seth, Lead Product Manager, Custom Search Egnine<br /><br /><a title="Lunch with Google Webmaster Central" href="http://www.searchenginestrategies.com/sew/chicago06/agenda.html#google">Lunch with Google Webmaster Central</a><br />Vanessa Fox, Product Manager, Webmaster Central<br />Amanda Camp, Software Engineer, Webmaster Tools<br />Trevor Foucher, Software Engineer, Webmaster Tools<br />Adam Lasnik, Search Evangelist<br />Evan Roseman, Software Engineer<br />Maile Ohye, Developer Support Engineer<br /><br /><span style="font-weight: bold;">Tuesday, December 5th</span><br /><br /><a title="Bulk Submit 2.0" href="http://www.searchenginestrategies.com/sew/chicago06/agenda2.html#bulk">Bulk Submit 2.0</a><br />Amanda Camp, Software Engineer, Webmaster Tools<br /><br /><a title="Domaining and Address Bar-Driven Traffic" href="http://www.searchenginestrategies.com/sew/chicago06/agenda2.html#dom">Domaining and Address Bar-Driven Traffic</a><br />Hal Bailey, Strategic Partner Manager<br /><br /><a title="Duplicate Content and Multiple Site Issues" href="http://www.searchenginestrategies.com/sew/chicago06/agenda2.html#duplicate">Duplicate Content and Multiple Site Issues</a><br />Adam Lasnik, Search Evangelist<br /><br /><a title="Bot Obedience Course" href="http://www.searchenginestrategies.com/sew/chicago06/agenda2.html#bot">Bot Obedience Course</a><br />Vanessa Fox, Product Manager, Webmaster Central<br /><br /><a title="Met the Search Ad Networks" href="http://www.searchenginestrategies.com/sew/chicago06/agenda2.html#meet">Meet the Search Ad Networks</a><br />Gretchen Howard, Online Sales and Operations Manager<br /><br /><a title="Meet the Mobile Search Engines" href="http://www.searchenginestrategies.com/sew/chicago06/agenda2.html#meet2">Meet the Mobile Search Engines</a><br />Sumit Agarwal, Product Manager, Mobile<br /><br /><span style="font-weight: bold;">Wednesday, December 6th</span><br /><br /><a title="Social Search Overview" href="http://www.searchenginestrategies.com/sew/chicago06/agenda3.html#social">Social Search Overview</a><br />Shashi Seth, Product Manager, Custom Search Engine<br /><br /><a title="Images and Search Engines" href="http://www.searchenginestrategies.com/sew/chicago06/agenda3.html#images">Images and Search Engines</a><br />Vanessa Fox, Product Manager, Webmaster Central<br /><br /><a title="Vendor Chat on Measuring Success" href="http://www.searchenginestrategies.com/sew/chicago06/agenda3.html#vendor">Vendor Chat on Measuring Success</a><br />Paul Botto, Google Analytics<br /><br /><a title="Flash and Search Engines" href="http://www.searchenginestrategies.com/sew/chicago06/agenda3.html#flash">Flash and Search Engines</a><br />Dan Crow, Product Manager<br /><br /><a title="CSS, AJAX, Web 2.0, and Search Engines" href="http://www.searchenginestrategies.com/sew/chicago06/agenda3.html#css">CSS, AJAX, Web 2.0, and Search Engines</a><br />Dan Crow, Product Manager<br /><br /><a title="Auditing Paid Listings and Click Fraud Issues" href="http://www.searchenginestrategies.com/sew/chicago06/agenda3.html#audit">Auditing Paid Listings and Click Fraud Issues</a><br />Shuman Ghosemajumder, Business Product Manager, Trust and Safety<br /><br /><span style="font-weight: bold;">Thursday, December 7th</span><br /><br /><a title="Meet the Crawlers" href="http://www.searchenginestrategies.com/sew/chicago06/agenda4.html#meet">Meet the Crawlers</a><br />Evan Roseman, Software Engineer<br /><br /><a title="Search Engine Q&A on Links" href="http://www.searchenginestrategies.com/sew/chicago06/agenda4.html#search">Search Engine Q&A on Links</a><br />Adam Lasnik, Search Evangelist <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <span style="font-weight: bold;"></span>If you're planning to be at <a title="SES Chicago" href="http://www.searchenginestrategies.com/sew/chicago06/index.html">SES Chicago</a> this week, be sure to stop by and say hi to the many Googlers who are coming out to brave the <a title="cold and snow" href="//www.google.com/search?q=weather+chicago">cold and snow</a>. Many of us will be on hand at the booth, speaking at sessions, and wandering the halls. Check out <a title="Search Engine Land" href="http://searchengineland.com/061201-084842.html">Search Engine Land</a> for tips on how to spot some of us and be sure to catch our sessions:<br /><br /><span style="font-weight: bold;">Monday, December 4th</span><br /><br /><a title="Drive traffic to your site with Google" href="http://www.searchenginestrategies.com/sew/chicago06/agenda.html#drive">Drive traffic to your site with Google</a><br />Jessica Ewing, Product Manager, Google Gadgets<br />Vanessa Fox, Product Manager, Webmaster Central<br />Shashi Seth, Lead Product Manager, Custom Search Egnine<br /><br /><a title="Lunch with Google Webmaster Central" href="http://www.searchenginestrategies.com/sew/chicago06/agenda.html#google">Lunch with Google Webmaster Central</a><br />Vanessa Fox, Product Manager, Webmaster Central<br />Amanda Camp, Software Engineer, Webmaster Tools<br />Trevor Foucher, Software Engineer, Webmaster Tools<br />Adam Lasnik, Search Evangelist<br />Evan Roseman, Software Engineer<br />Maile Ohye, Developer Support Engineer<br /><br /><span style="font-weight: bold;">Tuesday, December 5th</span><br /><br /><a title="Bulk Submit 2.0" href="http://www.searchenginestrategies.com/sew/chicago06/agenda2.html#bulk">Bulk Submit 2.0</a><br />Amanda Camp, Software Engineer, Webmaster Tools<br /><br /><a title="Domaining and Address Bar-Driven Traffic" href="http://www.searchenginestrategies.com/sew/chicago06/agenda2.html#dom">Domaining and Address Bar-Driven Traffic</a><br />Hal Bailey, Strategic Partner Manager<br /><br /><a title="Duplicate Content and Multiple Site Issues" href="http://www.searchenginestrategies.com/sew/chicago06/agenda2.html#duplicate">Duplicate Content and Multiple Site Issues</a><br />Adam Lasnik, Search Evangelist<br /><br /><a title="Bot Obedience Course" href="http://www.searchenginestrategies.com/sew/chicago06/agenda2.html#bot">Bot Obedience Course</a><br />Vanessa Fox, Product Manager, Webmaster Central<br /><br /><a title="Met the Search Ad Networks" href="http://www.searchenginestrategies.com/sew/chicago06/agenda2.html#meet">Meet the Search Ad Networks</a><br />Gretchen Howard, Online Sales and Operations Manager<br /><br /><a title="Meet the Mobile Search Engines" href="http://www.searchenginestrategies.com/sew/chicago06/agenda2.html#meet2">Meet the Mobile Search Engines</a><br />Sumit Agarwal, Product Manager, Mobile<br /><br /><span style="font-weight: bold;">Wednesday, December 6th</span><br /><br /><a title="Social Search Overview" href="http://www.searchenginestrategies.com/sew/chicago06/agenda3.html#social">Social Search Overview</a><br />Shashi Seth, Product Manager, Custom Search Engine<br /><br /><a title="Images and Search Engines" href="http://www.searchenginestrategies.com/sew/chicago06/agenda3.html#images">Images and Search Engines</a><br />Vanessa Fox, Product Manager, Webmaster Central<br /><br /><a title="Vendor Chat on Measuring Success" href="http://www.searchenginestrategies.com/sew/chicago06/agenda3.html#vendor">Vendor Chat on Measuring Success</a><br />Paul Botto, Google Analytics<br /><br /><a title="Flash and Search Engines" href="http://www.searchenginestrategies.com/sew/chicago06/agenda3.html#flash">Flash and Search Engines</a><br />Dan Crow, Product Manager<br /><br /><a title="CSS, AJAX, Web 2.0, and Search Engines" href="http://www.searchenginestrategies.com/sew/chicago06/agenda3.html#css">CSS, AJAX, Web 2.0, and Search Engines</a><br />Dan Crow, Product Manager<br /><br /><a title="Auditing Paid Listings and Click Fraud Issues" href="http://www.searchenginestrategies.com/sew/chicago06/agenda3.html#audit">Auditing Paid Listings and Click Fraud Issues</a><br />Shuman Ghosemajumder, Business Product Manager, Trust and Safety<br /><br /><span style="font-weight: bold;">Thursday, December 7th</span><br /><br /><a title="Meet the Crawlers" href="http://www.searchenginestrategies.com/sew/chicago06/agenda4.html#meet">Meet the Crawlers</a><br />Evan Roseman, Software Engineer<br /><br /><a title="Search Engine Q&A on Links" href="http://www.searchenginestrategies.com/sew/chicago06/agenda4.html#search">Search Engine Q&A on Links</a><br />Adam Lasnik, Search Evangelist <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:Come and see us at Search Engine Strategies Chicago&url=https://webmasters.googleblog.com/2006/12/come-and-see-us-at-search-engine.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/12/come-and-see-us-at-search-engine.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/12/come-and-see-us-at-search-engine.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/events?hl=en_US' rel='tag'> events </a> </span> </div> </div> </div> <div class='post' data-id='116477420533960848' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/11/viva-webmasters-in-vegas.html?hl=en_US' itemprop='url' title='Viva, Webmasters in Vegas'> Viva, Webmasters in Vegas </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, November 28, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> Thanks for visiting us at WebmasterWorld PubCon in Las Vegas couple weeks ago. Whether it was at the panel sessions, the exhibitor hall, or the Safe Bets event, we had a blast meeting you and sharing with you the many Google products that are available to webmasters to enhance and drive traffic to your site. For those who weren't able to join us, here are answers to some of the top questions that we heard:<br /><br /><span style="font-weight: bold;">Q: How do I increase the visibility of my site in search results?</span><br />A: There are many factors that can impact visibility of your site in search results. We outlined just a few tips that can make a big difference to increasing your site's visibility in Google search results. First, you should ensure your site has quality content that is unique. Second, have quality sites link to your site. Third, submit a Sitemap to let us know about all the URLs on your site. Fourth, sign up for a <a title="webmaster tools" href="//www.google.com/webmasters/tools">webmaster tools</a> account to get information how about Google sees your site, such as crawl errors, indexing details, and top queries to your site. Lastly, you can visit <a title="Webmaster Central" href="//www.google.com/webmasters">Webmaster Central</a> and <a title="Webmaster Help Center" href="//www.google.com/support/webmasters/bin/answer.py?answer=35769">Webmaster Help Center</a> for more webmaster related questions and resources.<span style="font-weight: bold;"><br /><br />Q How much do I have to pay to create a Google Custom Search Engine?</span><br />A: Nothing -- it's free. In addition to being able to create your own <a title="custom search engine" href="//google.com/coop/cse/">custom search engine</a> on your site, you can make money on your site using <a title="AdSense" href="//www.google.com/adsenseapply">AdSense</a> for Search.<span style="color: rgb(153, 0, 0);"></span><br /><br /><span style="font-weight: bold;">Q: Why is it better to create gadgets rather than create feeds?</span><br />A: First, <a title="gadgets" href="//www.google.com/webmasters/gadgets">gadgets</a> are much more flexible. As a publisher, you control the format of your content. Second, gadgets are by nature more interactive. They can be built with flash, HTML or AJAX, and are generally much more interesting than feeds. Finally, your users can customize a gadget to their liking, making your content a lot more targeted.<br /><br /><span style="font-weight: bold;">Q: What is this new ad placement feature for AdSense and how come I don't see it in my account? </span><br />A: <a title="Ad placements" href="https://www.google.com/adsense/support/bin/answer.py?answer=50691">Ad placements</a> are publisher-defined groups of ad units that advertisers will see when searching for places where they can target their ads. If you don't yet see it in your AdSense account, it's because we've been slowly rolling out this feature to everyone. This exciting feature will be available to all publishers in the next few weeks, so be sure to keep an eye out.<br /><br /><span style="font-weight: bold;">Q: What's the easiest way to put a searchable Google Map on my web page?</span><br />A: Use the <a title="Map Search Wizard" href="//google.com/uds/solutions/wizards/mapsearch.html">Map Search Wizard</a> to design a Google Map for your page. The wizard will write all of the code for you; all you need to do is copy and paste the code into your web page, and your users will see your location on a map.<br /><br />For more information about Google products for webmasters, you can check them out here:<br /><ul><li><a title="Webmaster tools" href="//www.google.com/webmasters/tools">Webmaster tools</a></li><li><a title="Gadgets" href="//www.google.com/webmasters/gadgets">Gadgets</a></li><li><a title="Custom Search Engine" href="//google.com/coop/cse/">Custom Search Engine</a></li><li><a title="Code" href="http://code.google.com/">Code</a></li><li><a title="AdSense" href="//www.google.com/adsenseapply">AdSense</a></li><li><a title="AdWords" href="//www.google.com/adwords">AdWords</a></li><li><a title="Analytics" href="//www.google.com/analytics">Analytics</a></li></ul>We also wanted to share some <a title="photos" href="//picasaweb.google.com/webmastercentralblog/PubconLasVegas2006">photos</a> from PubCon. If you look closely enough, you may be able to see yourself.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/x/blogger/431/4248/1600/706024/PubCon_audience.jpg"><img alt="" border="0" src="//photos1.blogger.com/x/blogger/431/4248/400/452242/PubCon_audience.jpg" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><br />Thanks for stopping by, on behalf of the 25 Googlers in attendance! <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> Thanks for visiting us at WebmasterWorld PubCon in Las Vegas couple weeks ago. Whether it was at the panel sessions, the exhibitor hall, or the Safe Bets event, we had a blast meeting you and sharing with you the many Google products that are available to webmasters to enhance and drive traffic to your site. For those who weren't able to join us, here are answers to some of the top questions that we heard:<br /><br /><span style="font-weight: bold;">Q: How do I increase the visibility of my site in search results?</span><br />A: There are many factors that can impact visibility of your site in search results. We outlined just a few tips that can make a big difference to increasing your site's visibility in Google search results. First, you should ensure your site has quality content that is unique. Second, have quality sites link to your site. Third, submit a Sitemap to let us know about all the URLs on your site. Fourth, sign up for a <a title="webmaster tools" href="//www.google.com/webmasters/tools">webmaster tools</a> account to get information how about Google sees your site, such as crawl errors, indexing details, and top queries to your site. Lastly, you can visit <a title="Webmaster Central" href="//www.google.com/webmasters">Webmaster Central</a> and <a title="Webmaster Help Center" href="//www.google.com/support/webmasters/bin/answer.py?answer=35769">Webmaster Help Center</a> for more webmaster related questions and resources.<span style="font-weight: bold;"><br /><br />Q How much do I have to pay to create a Google Custom Search Engine?</span><br />A: Nothing -- it's free. In addition to being able to create your own <a title="custom search engine" href="//google.com/coop/cse/">custom search engine</a> on your site, you can make money on your site using <a title="AdSense" href="//www.google.com/adsenseapply">AdSense</a> for Search.<span style="color: rgb(153, 0, 0);"></span><br /><br /><span style="font-weight: bold;">Q: Why is it better to create gadgets rather than create feeds?</span><br />A: First, <a title="gadgets" href="//www.google.com/webmasters/gadgets">gadgets</a> are much more flexible. As a publisher, you control the format of your content. Second, gadgets are by nature more interactive. They can be built with flash, HTML or AJAX, and are generally much more interesting than feeds. Finally, your users can customize a gadget to their liking, making your content a lot more targeted.<br /><br /><span style="font-weight: bold;">Q: What is this new ad placement feature for AdSense and how come I don't see it in my account? </span><br />A: <a title="Ad placements" href="https://www.google.com/adsense/support/bin/answer.py?answer=50691">Ad placements</a> are publisher-defined groups of ad units that advertisers will see when searching for places where they can target their ads. If you don't yet see it in your AdSense account, it's because we've been slowly rolling out this feature to everyone. This exciting feature will be available to all publishers in the next few weeks, so be sure to keep an eye out.<br /><br /><span style="font-weight: bold;">Q: What's the easiest way to put a searchable Google Map on my web page?</span><br />A: Use the <a title="Map Search Wizard" href="//google.com/uds/solutions/wizards/mapsearch.html">Map Search Wizard</a> to design a Google Map for your page. The wizard will write all of the code for you; all you need to do is copy and paste the code into your web page, and your users will see your location on a map.<br /><br />For more information about Google products for webmasters, you can check them out here:<br /><ul><li><a title="Webmaster tools" href="//www.google.com/webmasters/tools">Webmaster tools</a></li><li><a title="Gadgets" href="//www.google.com/webmasters/gadgets">Gadgets</a></li><li><a title="Custom Search Engine" href="//google.com/coop/cse/">Custom Search Engine</a></li><li><a title="Code" href="http://code.google.com/">Code</a></li><li><a title="AdSense" href="//www.google.com/adsenseapply">AdSense</a></li><li><a title="AdWords" href="//www.google.com/adwords">AdWords</a></li><li><a title="Analytics" href="//www.google.com/analytics">Analytics</a></li></ul>We also wanted to share some <a title="photos" href="//picasaweb.google.com/webmastercentralblog/PubconLasVegas2006">photos</a> from PubCon. If you look closely enough, you may be able to see yourself.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/x/blogger/431/4248/1600/706024/PubCon_audience.jpg"><img alt="" border="0" src="//photos1.blogger.com/x/blogger/431/4248/400/452242/PubCon_audience.jpg" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><br />Thanks for stopping by, on behalf of the 25 Googlers in attendance! <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:Viva, Webmasters in Vegas&url=https://webmasters.googleblog.com/2006/11/viva-webmasters-in-vegas.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/11/viva-webmasters-in-vegas.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/11/viva-webmasters-in-vegas.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/events?hl=en_US' rel='tag'> events </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/products%20and%20services?hl=en_US' rel='tag'> products and services </a> </span> </div> </div> </div> <div class='post' data-id='116404353231977078' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/11/introducing-sitemaps-for-google-news.html?hl=en_US' itemprop='url' title='Introducing Sitemaps for Google News'> Introducing Sitemaps for Google News </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Monday, November 20, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> Good news for webmasters of English-language news sites: If your site is currently included in <a title="Google News" href="http://news.google.com/">Google News</a>, you can now create News Sitemaps that tell us exactly which articles to crawl for inclusion in Google News. In addition, you can access crawl errors, which tell you if there were any problems crawling the articles in your News Sitemaps, or, for that matter, any articles on your site that Google News reaches through its normal crawl.<br /><br />Freshness is important for news, so we recrawl all News Sitemaps frequently. The <a title="News sitemaps XML definition" href="//www.google.com/support/webmasters/bin/answer.py?answer=42738">News Sitemaps XML definition</a> lets you specify a publication date and time for each article to help us process fresh articles in timely fashion. You can also specify keywords for each article to inform the placement of the articles into sections on Google News.<br /><br />If your English-language news site is currently included in Google News, the news features are automatically enabled in webmaster tools; just add the site to your account. Here's how the new summary page will look:<br /><br /><div style="text-align: center;"><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/7660/4159/1600/sitemaps.0.jpg"><img alt="" border="0" src="//photos1.blogger.com/blogger/7660/4159/400/sitemaps.jpg" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a></div>The presence of the <span style="font-style: italic;">News crawl</span> link on the left indicates that the news features are enabled. A few things to note:<br /><ul><li><p>You will only have the news features enabled if your site is currently included in Google News. If it's not, you can <a title="request inclusion" href="//www.google.com/support/news_pub/bin/answer.py?answer=40787">request inclusion</a>.</p></li><li><p>In most cases, you should <a title="add the site" href="//www.google.com/support/webmasters/bin/answer.py?answer=34592&hl=en">add the site</a> for the <span style="font-style: italic;">hostname</span> under which you publish your articles. For example, if you publish your articles at URLs such as <span style="color: rgb(0, 102, 0);font-family:Courier New;">http://www.example.com/business/article123.html</span>, you should add the site <span style="color: rgb(0, 102, 0);font-family:Courier New;">http://www.example.com/</span>. Exception: If your site is within a hosting site, you should add the site for your <span style="font-style: italic;">homepage</span>, e.g., <span style="color: rgb(0, 102, 0);font-family:Courier New;">http://members.tripod.com/mynewssite/</span>. If you publish articles under multiple hostnames, you should add a site for each of them.</p></li><li><p>You must <a title="verify your site" href="//www.google.com/support/webmasters/bin/answer.py?answer=35181">verify your site</a> to enable the news features.</p></li></ul>We'll be working to make the news features available to publishers in more languages as soon as possible. <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> Good news for webmasters of English-language news sites: If your site is currently included in <a title="Google News" href="http://news.google.com/">Google News</a>, you can now create News Sitemaps that tell us exactly which articles to crawl for inclusion in Google News. In addition, you can access crawl errors, which tell you if there were any problems crawling the articles in your News Sitemaps, or, for that matter, any articles on your site that Google News reaches through its normal crawl.<br /><br />Freshness is important for news, so we recrawl all News Sitemaps frequently. The <a title="News sitemaps XML definition" href="//www.google.com/support/webmasters/bin/answer.py?answer=42738">News Sitemaps XML definition</a> lets you specify a publication date and time for each article to help us process fresh articles in timely fashion. You can also specify keywords for each article to inform the placement of the articles into sections on Google News.<br /><br />If your English-language news site is currently included in Google News, the news features are automatically enabled in webmaster tools; just add the site to your account. Here's how the new summary page will look:<br /><br /><div style="text-align: center;"><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/7660/4159/1600/sitemaps.0.jpg"><img alt="" border="0" src="//photos1.blogger.com/blogger/7660/4159/400/sitemaps.jpg" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a></div>The presence of the <span style="font-style: italic;">News crawl</span> link on the left indicates that the news features are enabled. A few things to note:<br /><ul><li><p>You will only have the news features enabled if your site is currently included in Google News. If it's not, you can <a title="request inclusion" href="//www.google.com/support/news_pub/bin/answer.py?answer=40787">request inclusion</a>.</p></li><li><p>In most cases, you should <a title="add the site" href="//www.google.com/support/webmasters/bin/answer.py?answer=34592&hl=en">add the site</a> for the <span style="font-style: italic;">hostname</span> under which you publish your articles. For example, if you publish your articles at URLs such as <span style="color: rgb(0, 102, 0);font-family:Courier New;">http://www.example.com/business/article123.html</span>, you should add the site <span style="color: rgb(0, 102, 0);font-family:Courier New;">http://www.example.com/</span>. Exception: If your site is within a hosting site, you should add the site for your <span style="font-style: italic;">homepage</span>, e.g., <span style="color: rgb(0, 102, 0);font-family:Courier New;">http://members.tripod.com/mynewssite/</span>. If you publish articles under multiple hostnames, you should add a site for each of them.</p></li><li><p>You must <a title="verify your site" href="//www.google.com/support/webmasters/bin/answer.py?answer=35181">verify your site</a> to enable the news features.</p></li></ul>We'll be working to make the news features available to publishers in more languages as soon as possible. <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 Sitemaps for Google News&url=https://webmasters.googleblog.com/2006/11/introducing-sitemaps-for-google-news.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/11/introducing-sitemaps-for-google-news.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/11/introducing-sitemaps-for-google-news.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/sitemaps?hl=en_US' rel='tag'> sitemaps </a> </span> </div> </div> </div> <div class='post' data-id='116364522035598657' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/11/joint-support-for-sitemap-protocol.html?hl=en_US' itemprop='url' title='Joint support for the Sitemap Protocol'> Joint support for the Sitemap Protocol </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, November 15, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> We're thrilled to tell you that Yahoo! and Microsoft are joining us in supporting the Sitemap protocol.<br /><br />As part of this development, we're moving the protocol to a new namespace, www.sitemaps.org, and raising the version number to 0.9. The sponsoring companies will continue to collaborate on the protocol and publish enhancements on the jointly-maintained site <a href="http://www.sitemaps.org/"><span style="font-weight: bold;">sitemaps.org</span></a>.<br /><br />If you've already submitted a Sitemap to Google using the previous namespace and version number, we'll continue to accept it. If you haven't submitted a Sitemap before, check out the documentation on <a href="http://www.sitemaps.org/">www.sitemaps.org</a> for information on creating one. You can submit your Sitemap file to Google using <a href="//www.google.com/webmasters/sitemaps">Google webmaster tools</a>. See the documentation that Yahoo! and Microsoft provide for information about submitting to them.<br /><br />If any website owners, tool writers, or webserver developers haven't gotten around to implementing Sitemaps yet, thinking this was just a <a href="http://googleblog.blogspot.com/2005/06/webmaster-friendly.html">crazy Google experiment</a>, we hope this joint announcement shows that the industry is heading in this direction. The more Sitemaps eventually cover the entire web, the more we can revolutionize the way web crawlers interact with websites. In our view, the experiment is still underway. <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> We're thrilled to tell you that Yahoo! and Microsoft are joining us in supporting the Sitemap protocol.<br /><br />As part of this development, we're moving the protocol to a new namespace, www.sitemaps.org, and raising the version number to 0.9. The sponsoring companies will continue to collaborate on the protocol and publish enhancements on the jointly-maintained site <a href="http://www.sitemaps.org/"><span style="font-weight: bold;">sitemaps.org</span></a>.<br /><br />If you've already submitted a Sitemap to Google using the previous namespace and version number, we'll continue to accept it. If you haven't submitted a Sitemap before, check out the documentation on <a href="http://www.sitemaps.org/">www.sitemaps.org</a> for information on creating one. You can submit your Sitemap file to Google using <a href="//www.google.com/webmasters/sitemaps">Google webmaster tools</a>. See the documentation that Yahoo! and Microsoft provide for information about submitting to them.<br /><br />If any website owners, tool writers, or webserver developers haven't gotten around to implementing Sitemaps yet, thinking this was just a <a href="http://googleblog.blogspot.com/2005/06/webmaster-friendly.html">crazy Google experiment</a>, we hope this joint announcement shows that the industry is heading in this direction. The more Sitemaps eventually cover the entire web, the more we can revolutionize the way web crawlers interact with websites. In our view, the experiment is still underway. <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:Joint support for the Sitemap Protocol&url=https://webmasters.googleblog.com/2006/11/joint-support-for-sitemap-protocol.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/11/joint-support-for-sitemap-protocol.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/11/joint-support-for-sitemap-protocol.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/sitemaps?hl=en_US' rel='tag'> sitemaps </a> </span> </div> </div> </div> <div class='post' data-id='116354742092952785' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/11/badware-alerts-for-your-sites.html?hl=en_US' itemprop='url' title='Badware alerts for your sites'> Badware alerts for your sites </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, November 14, 2006 </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"> As part of our efforts to protect users, we have been warning people using Google search before they visit sites that have been determined to distribute badware under the <a href="http://www.stopbadware.org/home/guidelines#website" title="guidelines">guidelines</a> published by StopBadware. Warning users is only part of the solution, though; the real win comes from helping webmasters protect their own users by alerting them when their sites have been flagged for badware -- and working with them to remove the threats.<br /> <br /> It's my pleasure to introduce badware alerts in Google webmaster tools. You can see on the Diagnostic Summary tab if your site has been determined to distribute badware and can access information to <a href="//www.google.com/support/webmasters/bin/answer.py?answer=45432" title="help you correct this">help you correct this</a>.<br /> <br /> <a href="//photos1.blogger.com/blogger/3402/1340/1600/badware.gif" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/badware.png" style="cursor: pointer; display: block; margin: 0px auto 10px; text-align: center;"></a>If your site has been flagged and you believe you've since removed the threats, go to <a href="http://stopbadware.org/home/review">http://stopbadware.org/home/review</a> to request a review. If that's successful, your site will no longer be flagged -- and your users will be safer as a result of your diligence.<br /> <br /> This version is only the beginning: we plan to continue to provide more data to help webmasters diagnose issues on their sites. We realize that in many cases, badware distribution is unintentional and the result of being hacked or running ads which lead directly to pages with browser exploits. Stay tuned for improvements to this feature and others on webmaster tools.<br /> <br /> <span style="font-weight: bold;">Update</span>: this post has been updated to provide a link to the new form for requesting a review.<br /> <br /><br /> <b>Update: </b>More information is available in our <a href="http://support.google.com/webmasters/bin/answer.py?hl=en&answer=163633">Help Center article on malware and hacked sites</a>.</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"> As part of our efforts to protect users, we have been warning people using Google search before they visit sites that have been determined to distribute badware under the <a href="http://www.stopbadware.org/home/guidelines#website" title="guidelines">guidelines</a> published by StopBadware. Warning users is only part of the solution, though; the real win comes from helping webmasters protect their own users by alerting them when their sites have been flagged for badware -- and working with them to remove the threats.<br /> <br /> It's my pleasure to introduce badware alerts in Google webmaster tools. You can see on the Diagnostic Summary tab if your site has been determined to distribute badware and can access information to <a href="//www.google.com/support/webmasters/bin/answer.py?answer=45432" title="help you correct this">help you correct this</a>.<br /> <br /> <a href="//photos1.blogger.com/blogger/3402/1340/1600/badware.gif" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/badware.png" style="cursor: pointer; display: block; margin: 0px auto 10px; text-align: center;"></a>If your site has been flagged and you believe you've since removed the threats, go to <a href="http://stopbadware.org/home/review">http://stopbadware.org/home/review</a> to request a review. If that's successful, your site will no longer be flagged -- and your users will be safer as a result of your diligence.<br /> <br /> This version is only the beginning: we plan to continue to provide more data to help webmasters diagnose issues on their sites. We realize that in many cases, badware distribution is unintentional and the result of being hacked or running ads which lead directly to pages with browser exploits. Stay tuned for improvements to this feature and others on webmaster tools.<br /> <br /> <span style="font-weight: bold;">Update</span>: this post has been updated to provide a link to the new form for requesting a review.<br /> <br /><br /> <b>Update: </b>More information is available in our <a href="http://support.google.com/webmasters/bin/answer.py?hl=en&answer=163633">Help Center article on malware and hacked sites</a>.</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:Badware alerts for your sites&url=https://webmasters.googleblog.com/2006/11/badware-alerts-for-your-sites.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/11/badware-alerts-for-your-sites.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/11/badware-alerts-for-your-sites.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/general%20tips?hl=en_US' rel='tag'> general tips </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='116345851438795964' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/11/las-vegas-pubcon-2006.html?hl=en_US' itemprop='url' title='Las Vegas Pubcon 2006'> Las Vegas Pubcon 2006 </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Monday, November 13, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> As if working at Google isn't already a party, today I'm traveling to Las Vegas for <a href="http://www.pubcon.com/" title="WebmasterWorld PubCon 2006">WebmasterWorld PubCon 2006</a>! But instead of talking bets and odds, I'll be talking about how Google can help webmasters improve their sites. I love chatting with webmasters about all the work that goes into creating a great website. Several other Googlers will be there too, so if you have a burning question or just wanna talk about random stuff feel free to stop us and say hi. Besides the sessions, we'll be at the Google booth on Wednesday and Thursday, so come by and introduce yourself.<br /><br />Here's the list of Google events at PubCon:<br /><br /><span style="font-weight: bold;">Tuesday 14</span><br /><br />10:15 - 11:30 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=50" title="SEO and Big Search">SEO and Big Search</a> Adam Lasnik, Search Evangelist<br /><br />1:30 - 2:45 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=35" title="PPC Search Advertising Programs">PPC Search Advertising Programs</a> Frederick Vallaeys, Senior Product Specialist, AdWords<br /><br />2:45 - 4:00 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=67" title="PPC Tracking and Reconciliation">PPC Tracking and Reconciliation</a> Brett Crosby, Senior Manager, Google Analytics<br /><br /><span style="font-weight: bold;">Wednesday 15</span><br /><br />10:15 - 11:30 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=39" title="Contextual Advertising Optimization">Contextual Advertising Optimization</a> Tom Pickett, Online Sales and Operations<br /><br />11:35 - 12:50 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=51" title="Site Structure for Crawlability">Site Structure for Crawlability</a> Vanessa Fox, Product Manager, Google Webmaster Central<br /><br />1:30 - 3:10 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=66" title="Duplicate Content Issues">Duplicate Content Issues</a> Vanessa Fox, Product Manager, Google Webmaster Central<br /><br />5:30 - 7:30 Safe Bets From Google Cocktail party!<br /><br /><span style="font-weight: bold;">Thursday 16</span><br /><br />11:35 - 12:50 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=72" title="Spider and DOS Defense">Spider and DOS Defense</a> Vanessa Fox, Product Manager, Google Webmaster Central<br /><br />1:30 - 3:10 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=62" title="Interactive Site Reviews">Interactive Site Reviews</a> Matt Cutts, Software Engineer<br /><br />3:30 - 5:00 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=77" title="Super Session">Super Session</a> Matt Cutts, Software Engineer<br /><br />You can view this schedule on Google Calendar here: <a href="//www.google.com/calendar/render?cid=mq4cd7dv596jm2e9hpiu7brp2k@group.calendar.google.com" target="_blank"><img border="0" src="//www.google.com/calendar/images/ext/gc_button1_en.gif"></a><br /><br />Come to "Safe Bets From Google" on Wednesday 5:30-7:30pm -- it's a cocktail party where you can mingle with other webmasters and Googlers, learn about other Google products for webmasters, and in typical Google style enjoy some great food and drinks. I'll be there with some other engineers from our Seattle office. Don't miss it! <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> As if working at Google isn't already a party, today I'm traveling to Las Vegas for <a href="http://www.pubcon.com/" title="WebmasterWorld PubCon 2006">WebmasterWorld PubCon 2006</a>! But instead of talking bets and odds, I'll be talking about how Google can help webmasters improve their sites. I love chatting with webmasters about all the work that goes into creating a great website. Several other Googlers will be there too, so if you have a burning question or just wanna talk about random stuff feel free to stop us and say hi. Besides the sessions, we'll be at the Google booth on Wednesday and Thursday, so come by and introduce yourself.<br /><br />Here's the list of Google events at PubCon:<br /><br /><span style="font-weight: bold;">Tuesday 14</span><br /><br />10:15 - 11:30 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=50" title="SEO and Big Search">SEO and Big Search</a> Adam Lasnik, Search Evangelist<br /><br />1:30 - 2:45 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=35" title="PPC Search Advertising Programs">PPC Search Advertising Programs</a> Frederick Vallaeys, Senior Product Specialist, AdWords<br /><br />2:45 - 4:00 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=67" title="PPC Tracking and Reconciliation">PPC Tracking and Reconciliation</a> Brett Crosby, Senior Manager, Google Analytics<br /><br /><span style="font-weight: bold;">Wednesday 15</span><br /><br />10:15 - 11:30 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=39" title="Contextual Advertising Optimization">Contextual Advertising Optimization</a> Tom Pickett, Online Sales and Operations<br /><br />11:35 - 12:50 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=51" title="Site Structure for Crawlability">Site Structure for Crawlability</a> Vanessa Fox, Product Manager, Google Webmaster Central<br /><br />1:30 - 3:10 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=66" title="Duplicate Content Issues">Duplicate Content Issues</a> Vanessa Fox, Product Manager, Google Webmaster Central<br /><br />5:30 - 7:30 Safe Bets From Google Cocktail party!<br /><br /><span style="font-weight: bold;">Thursday 16</span><br /><br />11:35 - 12:50 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=72" title="Spider and DOS Defense">Spider and DOS Defense</a> Vanessa Fox, Product Manager, Google Webmaster Central<br /><br />1:30 - 3:10 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=62" title="Interactive Site Reviews">Interactive Site Reviews</a> Matt Cutts, Software Engineer<br /><br />3:30 - 5:00 <a href="http://www.pubcon.com/sessions.cgi?action=view&record=77" title="Super Session">Super Session</a> Matt Cutts, Software Engineer<br /><br />You can view this schedule on Google Calendar here: <a href="//www.google.com/calendar/render?cid=mq4cd7dv596jm2e9hpiu7brp2k@group.calendar.google.com" target="_blank"><img border="0" src="//www.google.com/calendar/images/ext/gc_button1_en.gif"></a><br /><br />Come to "Safe Bets From Google" on Wednesday 5:30-7:30pm -- it's a cocktail party where you can mingle with other webmasters and Googlers, learn about other Google products for webmasters, and in typical Google style enjoy some great food and drinks. I'll be there with some other engineers from our Seattle office. Don't miss it! <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:Las Vegas Pubcon 2006&url=https://webmasters.googleblog.com/2006/11/las-vegas-pubcon-2006.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/11/las-vegas-pubcon-2006.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/11/las-vegas-pubcon-2006.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/events?hl=en_US' rel='tag'> events </a> </span> </div> </div> </div> <div class='post' data-id='116318215239833033' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/11/new-third-party-sitemaps-tools.html?hl=en_US' itemprop='url' title='New third-party Sitemaps tools'> New third-party Sitemaps tools </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Friday, November 10, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> Hello, webmasters, I'm Maile, and I recently joined the team here at <a title="Google webmaster central" href="//www.google.com/webmasters/">Google webmaster central</a>. And I already have good news to report: we've updated our <a title="third-party program and websites" href="http://code.google.com/sm_thirdparty.html">third-party program and websites</a> information. These third-party tools provide lots of options for easily generate a Sitemap -- from plugins for content management systems to online generators.<br /><br />Many thanks to this community for continuing to innovate and improve the Sitemap tools. <span style="font-style: italic; color: rgb(153, 0, 0);"></span>Since most of my work focuses on the Sitemaps protocol, I hope to meet you on our <a title="Sitemaps protocol discussion group" href="http://groups.google.com/group/Google_Webmaster_Help-Sitemap?tsc=1">Sitemaps protocol discussion group</a>. <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> Hello, webmasters, I'm Maile, and I recently joined the team here at <a title="Google webmaster central" href="//www.google.com/webmasters/">Google webmaster central</a>. And I already have good news to report: we've updated our <a title="third-party program and websites" href="http://code.google.com/sm_thirdparty.html">third-party program and websites</a> information. These third-party tools provide lots of options for easily generate a Sitemap -- from plugins for content management systems to online generators.<br /><br />Many thanks to this community for continuing to innovate and improve the Sitemap tools. <span style="font-style: italic; color: rgb(153, 0, 0);"></span>Since most of my work focuses on the Sitemaps protocol, I hope to meet you on our <a title="Sitemaps protocol discussion group" href="http://groups.google.com/group/Google_Webmaster_Help-Sitemap?tsc=1">Sitemaps protocol discussion group</a>. <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:New third-party Sitemaps tools&url=https://webmasters.googleblog.com/2006/11/new-third-party-sitemaps-tools.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/11/new-third-party-sitemaps-tools.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/11/new-third-party-sitemaps-tools.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/sitemaps?hl=en_US' rel='tag'> sitemaps </a> </span> </div> </div> </div> <div class='post' data-id='116311864041998355' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/11/number-of-pages-googlebot-crawls.html?hl=en_US' itemprop='url' title='The number of pages Googlebot crawls'> The number of pages Googlebot crawls </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, November 09, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> The <a title="Googlebot activity reports" href="http://googlewebmastercentral.blogspot.com/2006/10/googlebot-activity-reports.html">Googlebot activity reports</a> in webmaster tools show you the number of pages of your site Googlebot has crawled over the last 90 days. We've seen some of you asking why this number might be higher than the total number of pages on your sites.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/pages_final.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/pages_final.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><br />Googlebot crawls pages of your site based on a number of things including:<br /><ul><li>pages it already knows about<br /></li><li>links from other web pages (within your site and on other sites)</li><li>pages listed in your Sitemap file</li></ul>More specifically, Googlebot doesn't access pages, it accesses URLs. And the same page can often be accessed via several URLs. Consider the home page of a site that can be accessed from the following four URLs:<br /><ul><li>http://www.example.com/</li><li>http://www.example.com/index.html</li><li>http://example.com</li><li>http://example.com/index.html</li></ul>Although all URLs lead to the same page, all four URLs may be used in links to the page. When Googlebot follows these links, a count of four is added to the activity report.<br /><br />Many other scenarios can lead to multiple URLs for the same page. For instance, a page may have several named anchors, such as:<br /><ul><li>http://www.example.com/mypage.html#heading1</li><li>http://www.example.com/mypage.html#heading2</li><li>http://www.example.com/mypage.html#heading3</li></ul>And dynamically generated pages often can be reached by multiple URLs, such as:<br /><ul><li>http://www.example.com/furniture?type=chair&brand=123</li><li>http://www.example.com/hotbuys?type=chair&brand=123</li></ul>As you can see, when you consider that each page on your site might have multiple URLs that lead to it, the number of URLs that Googlebot crawls can be considerably higher than the number of total pages for your site.<br /><br />Of course, you (and we) only want one version of the URL to be returned in the search results. Not to worry -- this is exactly what happens. Our algorithms selects a version to include, and you can provide input on this selection process.<br /><br /><span style="font-weight: bold;">Redirect to the preferred version of the URL</span><br />You can do this using <a href="http://en.wikipedia.org/wiki/URL_redirection">301 (permanent) redirect</a>. In the first example that shows four URLs that point to a site's home page, you may want to redirect <span style="font-weight: bold;">index.html</span> to <span style="font-weight: bold;">www.example.com/</span>. And you may want to redirect <span style="font-weight: bold;">example.com</span> to <span style="font-weight: bold;">www.example.com</span> so that any URLs that begin with one version are redirected to the other version. Note that you can do this latter redirect with the <a title="Preferred Domain feature" href="http://googlewebmastercentral.blogspot.com/2006/09/setting-preferred-domain.html">Preferred Domain feature</a> in webmaster tools. (If you also use a 301 redirect, make sure that this redirect matches what you set for the preferred domain.)<br /><br /><span style="font-weight: bold;">Block the non-preferred versions of a URL with a robots.txt file</span><br />For dynamically generated pages, you may want to block the non-preferred version using <a title="pattern matching" href="//www.google.com/support/webmasters/bin/answer.py?answer=40367&topic=8846">pattern matching</a> in your robots.txt file. (Note that not all search engines support pattern matching, so check the guidelines for each search engine bot you're interested in.) For instance, in the third example that shows two URLs that point to a page about the chairs available from brand 123, the "hotbuys" section rotates periodically and the content is always available from a primary and permanent location. If that case, you may want to index the first version, and block the "hotbuys" version. To do this, add the following to your robots.txt file:<br /><br />User-agent: Googlebot<br />Disallow: /hotbuys?*<br /><br />To ensure that this directive will actually block and allow what you intend, use the robots.txt analysis tool in webmaster tools. Just add this directive to the robots.txt section on that page, list the URLs you want to check in the "Test URLs" section and click the <span style="font-weight: bold;">Check </span>button. For this example, you'd see a result like this:<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/robots_googlebot.0.png"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/robots_googlebot.0.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a>Don't worry about links to anchors, because while Googlebot will crawl each link, our algorithms will index the URL without the anchor.<br /><br />And if you don't provide input such as that described above, our algorithms do a really good job of picking a version to show in the search results. <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> The <a title="Googlebot activity reports" href="http://googlewebmastercentral.blogspot.com/2006/10/googlebot-activity-reports.html">Googlebot activity reports</a> in webmaster tools show you the number of pages of your site Googlebot has crawled over the last 90 days. We've seen some of you asking why this number might be higher than the total number of pages on your sites.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/pages_final.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/pages_final.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><br />Googlebot crawls pages of your site based on a number of things including:<br /><ul><li>pages it already knows about<br /></li><li>links from other web pages (within your site and on other sites)</li><li>pages listed in your Sitemap file</li></ul>More specifically, Googlebot doesn't access pages, it accesses URLs. And the same page can often be accessed via several URLs. Consider the home page of a site that can be accessed from the following four URLs:<br /><ul><li>http://www.example.com/</li><li>http://www.example.com/index.html</li><li>http://example.com</li><li>http://example.com/index.html</li></ul>Although all URLs lead to the same page, all four URLs may be used in links to the page. When Googlebot follows these links, a count of four is added to the activity report.<br /><br />Many other scenarios can lead to multiple URLs for the same page. For instance, a page may have several named anchors, such as:<br /><ul><li>http://www.example.com/mypage.html#heading1</li><li>http://www.example.com/mypage.html#heading2</li><li>http://www.example.com/mypage.html#heading3</li></ul>And dynamically generated pages often can be reached by multiple URLs, such as:<br /><ul><li>http://www.example.com/furniture?type=chair&brand=123</li><li>http://www.example.com/hotbuys?type=chair&brand=123</li></ul>As you can see, when you consider that each page on your site might have multiple URLs that lead to it, the number of URLs that Googlebot crawls can be considerably higher than the number of total pages for your site.<br /><br />Of course, you (and we) only want one version of the URL to be returned in the search results. Not to worry -- this is exactly what happens. Our algorithms selects a version to include, and you can provide input on this selection process.<br /><br /><span style="font-weight: bold;">Redirect to the preferred version of the URL</span><br />You can do this using <a href="http://en.wikipedia.org/wiki/URL_redirection">301 (permanent) redirect</a>. In the first example that shows four URLs that point to a site's home page, you may want to redirect <span style="font-weight: bold;">index.html</span> to <span style="font-weight: bold;">www.example.com/</span>. And you may want to redirect <span style="font-weight: bold;">example.com</span> to <span style="font-weight: bold;">www.example.com</span> so that any URLs that begin with one version are redirected to the other version. Note that you can do this latter redirect with the <a title="Preferred Domain feature" href="http://googlewebmastercentral.blogspot.com/2006/09/setting-preferred-domain.html">Preferred Domain feature</a> in webmaster tools. (If you also use a 301 redirect, make sure that this redirect matches what you set for the preferred domain.)<br /><br /><span style="font-weight: bold;">Block the non-preferred versions of a URL with a robots.txt file</span><br />For dynamically generated pages, you may want to block the non-preferred version using <a title="pattern matching" href="//www.google.com/support/webmasters/bin/answer.py?answer=40367&topic=8846">pattern matching</a> in your robots.txt file. (Note that not all search engines support pattern matching, so check the guidelines for each search engine bot you're interested in.) For instance, in the third example that shows two URLs that point to a page about the chairs available from brand 123, the "hotbuys" section rotates periodically and the content is always available from a primary and permanent location. If that case, you may want to index the first version, and block the "hotbuys" version. To do this, add the following to your robots.txt file:<br /><br />User-agent: Googlebot<br />Disallow: /hotbuys?*<br /><br />To ensure that this directive will actually block and allow what you intend, use the robots.txt analysis tool in webmaster tools. Just add this directive to the robots.txt section on that page, list the URLs you want to check in the "Test URLs" section and click the <span style="font-weight: bold;">Check </span>button. For this example, you'd see a result like this:<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/robots_googlebot.0.png"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/robots_googlebot.0.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a>Don't worry about links to anchors, because while Googlebot will crawl each link, our algorithms will index the URL without the anchor.<br /><br />And if you don't provide input such as that described above, our algorithms do a really good job of picking a version to show in the search results. <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 number of pages Googlebot crawls&url=https://webmasters.googleblog.com/2006/11/number-of-pages-googlebot-crawls.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/11/number-of-pages-googlebot-crawls.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/11/number-of-pages-googlebot-crawls.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en_US' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='116234092100134668' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/10/target-visitors-or-search-engines.html?hl=en_US' itemprop='url' title='Target visitors or search engines?'> Target visitors or search engines? </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, October 31, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> Last Friday afternoon, I was able to catch the end of the <a title="Blog Business Summit" href="http://www.blogbusinesssummit.com/">Blog Business Summit</a> in Seattle. At the session called "Blogging and SEO Strategies," <a title="John Battelle" href="http://battellemedia.com/">John Battelle</a> brought up a good point. He said that as a writer, he doesn't want to have to think about all of this search engine optimization stuff. <a title="Dave Taylor" href="http://www.intuitive.com/blog/">Dave Taylor</a> had just been talking about order of words in title tags and keyword density and <a title="using hyphens" href="http://mattcutts.com/blog/guest-post-vanessa-fox-on-organic-site-review-session/">using hyphens</a> rather than <a title="underscores" href="http://mattcutts.com/blog/dashes-vs-underscores/">underscores</a> in URLs.<br /><br />We agree, which is why you'll find that the main point in our <a title="webmaster guidelines" href="//www.google.com/support/webmasters/bin/answer.py?answer=35769">webmaster guidelines</a> is to make sites for visitors, not for search engines. Visitor-friendly design makes for search engine friendly design as well. The team at Google webmaster central talks a lot with site owners who care a lot about the details of how Google crawls and indexes sites (hyphens and underscores included), but many site owners out there are just concerned with building great sites. The good news is that the guidelines and tips about how Google crawls and indexes sites come down to wanting great content for our search results.<br /><br />In the spirit of John Battelle's point, here's a recap of some quick tips for ensuring your site is friendly for visitors.<br /><br /><span style="font-weight: bold;">Make good use of page titles</span><br />This is true of the main heading on the page itself, but is also true of the title that appears in the browser's title bar.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/titlebar.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/titlebar.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><br />Whenever possible, ensure each page has a unique title that describes the page well. For instance, if your site is for your store "Buffy's House of Sofas", a visitor may want to bookmark your home page and the order page for your red, fluffy sofa. If all of your pages have the same title: "Wecome to my site!", then a visitor will have trouble finding your site again in the bookmarks. However, if your home page has the title "Buffy's House of Sofas" and your red sofa page has the title "Buffy's red fluffy sofa", then visitors can glance at the title to see what it's about and can easily find it in the bookmarks later. And if your visitors are anything like me, they may have several browser tabs open and appreciate descriptive titles for easier navigation.<br /><br />This simple tip for visitors helps search engines too. Search engines index pages based on the words contained in them, and including descriptive titles helps search engines know what the pages are about. And search engines often use a page's title in the search results. "Welcome to my site" may not entice searchers to click on your site in the results quite so much as "Buffy's House of Sofas".<br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/title_searchresults.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/title_searchresults.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><span style="font-weight: bold;">Write with words<br /></span>Images, flash, and other multimedia make for pretty web pages, but make sure your core messages are in text or use ALT text to provide textual descriptions of your multimedia. This is great for search engines, which are based on text: searchers enter search queries as word, after all. But it's also great for visitors, who may have images or Flash turned off in their browsers or might be using screen readers or mobile devices. You can also provide HTML versions of your multimedia-based pages (if you do that, be sure to block the multimedia versions from being indexed using a <a title="robots.txt file" href="//www.google.com/support/webmasters/bin/answer.py?answer=40360&topic=8846">robots.txt file</a>).<br /><br /><span style="font-weight: bold;">Make sure the text you're talking about is in your content</span><br />Visitors may not read your web site linearly like they would a newspaper article or book. Visitors may follow links from elsewhere on the web to any of your pages. Make sure that they have context for any page they're on. On your order page, don't just write "order now!" Write something like "Order your fluffy red sofa now!" But write it for people who will be reading your site. Don't try to cram as many words in as possible, thinking search engines can index more words that way. Think of your visitors. What are they going to be searching for? Is your site full of industry jargon when they'll be searching for you with more informal words?<br /><br />As I wrote in that <a title="guest post" href="http://mattcutts.com/blog/guest-post-vanessa-fox-on-organic-site-review-session/">guest post</a> <span style="color: rgb(204, 0, 0);"> </span>on Matt Cutts' blog when I talked about hyphens and underscores:<br /><br /><span style="font-style: italic;"> You know what your site’s about, so it may seem completely obvious to you when you look at your home page. But ask someone else to take a look and don’t tell them anything about the site. What do they think your site is about?<br /></span> <p style="font-style: italic;">Consider this text:</p> <p style="font-style: italic;">“We have hundreds of workshops and classes available. You can choose the workshop that is right for you. Spend an hour or a week in our relaxing facility.”</p> <p style="font-style: italic;">Will this site show up for searches for [cooking classes] or [wine tasting workshops] or even [classes in Seattle]? It may not be as obvious to visitors (and search engine bots) what your page is about as you think.</p> <p style="font-style: italic;">Along those same lines, does your content use words that people are searching for? Does your site text say “check out our homes for sale” when people are searching for [real estate in Boston]?</p><span style="font-weight: bold;">Make sure your pages are accessible</span><br />I know -- this post was supposed to be about writing content, not technical details. But visitors can't read your site if they can't access it. If the network is down or your server returns errors when someone tries to access the pages of your site, it's not just search engines who will have trouble. Fortunately, <a title="webmaster tools" href="//www.google.com/webmasters/sitemaps/siteoverview">webmaster tools</a> makes it easy. We'll let you know if we've had any trouble accessing any of the pages. We tell you the specific page we couldn't access and the exact error we got. These problems aren't always easy to fix, but we try to make them easy to find. <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> Last Friday afternoon, I was able to catch the end of the <a title="Blog Business Summit" href="http://www.blogbusinesssummit.com/">Blog Business Summit</a> in Seattle. At the session called "Blogging and SEO Strategies," <a title="John Battelle" href="http://battellemedia.com/">John Battelle</a> brought up a good point. He said that as a writer, he doesn't want to have to think about all of this search engine optimization stuff. <a title="Dave Taylor" href="http://www.intuitive.com/blog/">Dave Taylor</a> had just been talking about order of words in title tags and keyword density and <a title="using hyphens" href="http://mattcutts.com/blog/guest-post-vanessa-fox-on-organic-site-review-session/">using hyphens</a> rather than <a title="underscores" href="http://mattcutts.com/blog/dashes-vs-underscores/">underscores</a> in URLs.<br /><br />We agree, which is why you'll find that the main point in our <a title="webmaster guidelines" href="//www.google.com/support/webmasters/bin/answer.py?answer=35769">webmaster guidelines</a> is to make sites for visitors, not for search engines. Visitor-friendly design makes for search engine friendly design as well. The team at Google webmaster central talks a lot with site owners who care a lot about the details of how Google crawls and indexes sites (hyphens and underscores included), but many site owners out there are just concerned with building great sites. The good news is that the guidelines and tips about how Google crawls and indexes sites come down to wanting great content for our search results.<br /><br />In the spirit of John Battelle's point, here's a recap of some quick tips for ensuring your site is friendly for visitors.<br /><br /><span style="font-weight: bold;">Make good use of page titles</span><br />This is true of the main heading on the page itself, but is also true of the title that appears in the browser's title bar.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/titlebar.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/titlebar.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><br />Whenever possible, ensure each page has a unique title that describes the page well. For instance, if your site is for your store "Buffy's House of Sofas", a visitor may want to bookmark your home page and the order page for your red, fluffy sofa. If all of your pages have the same title: "Wecome to my site!", then a visitor will have trouble finding your site again in the bookmarks. However, if your home page has the title "Buffy's House of Sofas" and your red sofa page has the title "Buffy's red fluffy sofa", then visitors can glance at the title to see what it's about and can easily find it in the bookmarks later. And if your visitors are anything like me, they may have several browser tabs open and appreciate descriptive titles for easier navigation.<br /><br />This simple tip for visitors helps search engines too. Search engines index pages based on the words contained in them, and including descriptive titles helps search engines know what the pages are about. And search engines often use a page's title in the search results. "Welcome to my site" may not entice searchers to click on your site in the results quite so much as "Buffy's House of Sofas".<br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/title_searchresults.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/title_searchresults.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><span style="font-weight: bold;">Write with words<br /></span>Images, flash, and other multimedia make for pretty web pages, but make sure your core messages are in text or use ALT text to provide textual descriptions of your multimedia. This is great for search engines, which are based on text: searchers enter search queries as word, after all. But it's also great for visitors, who may have images or Flash turned off in their browsers or might be using screen readers or mobile devices. You can also provide HTML versions of your multimedia-based pages (if you do that, be sure to block the multimedia versions from being indexed using a <a title="robots.txt file" href="//www.google.com/support/webmasters/bin/answer.py?answer=40360&topic=8846">robots.txt file</a>).<br /><br /><span style="font-weight: bold;">Make sure the text you're talking about is in your content</span><br />Visitors may not read your web site linearly like they would a newspaper article or book. Visitors may follow links from elsewhere on the web to any of your pages. Make sure that they have context for any page they're on. On your order page, don't just write "order now!" Write something like "Order your fluffy red sofa now!" But write it for people who will be reading your site. Don't try to cram as many words in as possible, thinking search engines can index more words that way. Think of your visitors. What are they going to be searching for? Is your site full of industry jargon when they'll be searching for you with more informal words?<br /><br />As I wrote in that <a title="guest post" href="http://mattcutts.com/blog/guest-post-vanessa-fox-on-organic-site-review-session/">guest post</a> <span style="color: rgb(204, 0, 0);"> </span>on Matt Cutts' blog when I talked about hyphens and underscores:<br /><br /><span style="font-style: italic;"> You know what your site’s about, so it may seem completely obvious to you when you look at your home page. But ask someone else to take a look and don’t tell them anything about the site. What do they think your site is about?<br /></span> <p style="font-style: italic;">Consider this text:</p> <p style="font-style: italic;">“We have hundreds of workshops and classes available. You can choose the workshop that is right for you. Spend an hour or a week in our relaxing facility.”</p> <p style="font-style: italic;">Will this site show up for searches for [cooking classes] or [wine tasting workshops] or even [classes in Seattle]? It may not be as obvious to visitors (and search engine bots) what your page is about as you think.</p> <p style="font-style: italic;">Along those same lines, does your content use words that people are searching for? Does your site text say “check out our homes for sale” when people are searching for [real estate in Boston]?</p><span style="font-weight: bold;">Make sure your pages are accessible</span><br />I know -- this post was supposed to be about writing content, not technical details. But visitors can't read your site if they can't access it. If the network is down or your server returns errors when someone tries to access the pages of your site, it's not just search engines who will have trouble. Fortunately, <a title="webmaster tools" href="//www.google.com/webmasters/sitemaps/siteoverview">webmaster tools</a> makes it easy. We'll let you know if we've had any trouble accessing any of the pages. We tell you the specific page we couldn't access and the exact error we got. These problems aren't always easy to fix, but we try to make them easy to find. <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:Target visitors or search engines?&url=https://webmasters.googleblog.com/2006/10/target-visitors-or-search-engines.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/10/target-visitors-or-search-engines.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/10/target-visitors-or-search-engines.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en_US' rel='tag'> crawling and indexing </a> </span> </div> </div> </div> <div class='post' data-id='116178747346714704' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/10/update-to-our-webmaster-guidelines.html?hl=en_US' itemprop='url' title='Update to our webmaster guidelines'> Update to our webmaster guidelines </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, October 25, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <span style="font-weight: bold;"></span>As the web continues to change and evolve, our algorithms change right along with it. Recently, as a result of one of those algorithmic changes, we've modified our <a title="webmaster guidelines" href="//www.google.com/support/webmasters/bin/answer.py?answer=35769">webmaster guidelines</a>. Previously, these stated:<br /><br /><br /><span style="font-style: italic;">Don't use "&id=" as a parameter in your URLs, as we don't include these pages in our index.</span><br /><br />However, we've recently removed that technical guideline, and now index URLs that contain that parameter. So if your site uses a dynamic structure that generates it, don't worry about rewriting it -- we'll accept it just fine as is. Keep in mind, however, that dynamic URLs with a large number of parameters may be problematic for search engine crawlers in general, so rewriting dynamic URLs into user-friendly versions is always a good practice when that option is available to you. If you can, keeping the number of URL parameters to one or two may make it more likely that search engines will crawl your dynamic urls. <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <span style="font-weight: bold;"></span>As the web continues to change and evolve, our algorithms change right along with it. Recently, as a result of one of those algorithmic changes, we've modified our <a title="webmaster guidelines" href="//www.google.com/support/webmasters/bin/answer.py?answer=35769">webmaster guidelines</a>. Previously, these stated:<br /><br /><br /><span style="font-style: italic;">Don't use "&id=" as a parameter in your URLs, as we don't include these pages in our index.</span><br /><br />However, we've recently removed that technical guideline, and now index URLs that contain that parameter. So if your site uses a dynamic structure that generates it, don't worry about rewriting it -- we'll accept it just fine as is. Keep in mind, however, that dynamic URLs with a large number of parameters may be problematic for search engine crawlers in general, so rewriting dynamic URLs into user-friendly versions is always a good practice when that option is available to you. If you can, keeping the number of URL parameters to one or two may make it more likely that search engines will crawl your dynamic urls. <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:Update to our webmaster guidelines&url=https://webmasters.googleblog.com/2006/10/update-to-our-webmaster-guidelines.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/10/update-to-our-webmaster-guidelines.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/10/update-to-our-webmaster-guidelines.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines?hl=en_US' rel='tag'> webmaster guidelines </a> </span> </div> </div> </div> <div class='post' data-id='116128720985255774' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/10/googlebot-activity-reports.html?hl=en_US' itemprop='url' title='Googlebot activity reports'> Googlebot activity reports </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, October 19, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> The <a href="https://www.google.com/webmasters/sitemaps">webmaster tools</a> team has a very exciting mission: we dig into our logs, find as much useful information as possible, and pass it on to you, the webmasters. Our reward is that you more easily understand what Google sees, and why some pages don't make it to the index.<br /><br />The latest batch of information that we've put together for you is the amount of traffic between Google and a given site. We show you the number of requests, number of kilobytes (yes, yes, I know that tech-savvy webmasters can usually dig this out, but our new charts make it really easy to see at a glance), and the average document download time. You can see this information in chart form, as well as in hard numbers (the maximum, minimum, and average).<br /><br />For instance, here's the number of pages Googlebot has crawled in the Webmaster Central blog over the last 90 days. The maximum number of pages Googlebot has crawled in one day is 24 and the minimum is 2. That makes sense, because the blog was launched less than 90 days ago, and the chart shows that the number of pages crawled per day has increased over time. The number of pages crawled is sometimes more than the total number of pages in the site -- especially if the same page can be accessed via several URLs. So <a title="http://googlewebmastercentral.blogspot.com/2006/10/learn-more-about-googlebots-crawl-of.html" href="http://googlewebmastercentral.blogspot.com/2006/10/learn-more-about-googlebots-crawl-of.html">http://googlewebmastercentral.blogspot.com/2006/10/learn-more-about-googlebots-crawl-of.html</a> and <a title="http://googlewebmastercentral.blogspot.com/2006/10/learn-more-about-googlebots-crawl-of.html#links" href="http://googlewebmastercentral.blogspot.com/2006/10/learn-more-about-googlebots-crawl-of.html#links">http://googlewebmastercentral.blogspot.com/2006/10/learn-more-about-googlebots-crawl-of.html#links</a> are different, but point to the same page (the second points to an anchor within the page).<br /><span style="font-style: italic; color: rgb(204, 0, 0);"></span><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/5446/4056/1600/pages_final.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/5446/4056/400/pages_final.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><br />And here's the average number of kilobytes downloaded from this blog each day. As you can see, as the site has grown over the last two and a half months, the number of average kilobytes downloaded has increased as well.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/5446/4056/1600/kb_final.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/5446/4056/400/kb_final.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><br />The first two reports can help you diagnose the impact that changes in your site may have on its coverage. If you overhaul your site and dramatically reduce the number of pages, you'll likely notice a drop in the number of pages that Googlebot accesses.<br /><br />The average document download time can help pinpoint subtle networking problems. If the average time spikes, you might have network slowdowns or bottlenecks that you should investigate. Here's the report for this blog that shows that we did have a short spike in early September (the maximum time was 1057 ms), but it quickly went back to a normal level, so things now look OK.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/5446/4056/1600/time_final.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/5446/4056/400/time_final.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a>In general, the load time of a page doesn't affect its ranking, but we wanted to give this info because it can help you spot problems. We hope you will find this data as useful as we do! <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> The <a href="https://www.google.com/webmasters/sitemaps">webmaster tools</a> team has a very exciting mission: we dig into our logs, find as much useful information as possible, and pass it on to you, the webmasters. Our reward is that you more easily understand what Google sees, and why some pages don't make it to the index.<br /><br />The latest batch of information that we've put together for you is the amount of traffic between Google and a given site. We show you the number of requests, number of kilobytes (yes, yes, I know that tech-savvy webmasters can usually dig this out, but our new charts make it really easy to see at a glance), and the average document download time. You can see this information in chart form, as well as in hard numbers (the maximum, minimum, and average).<br /><br />For instance, here's the number of pages Googlebot has crawled in the Webmaster Central blog over the last 90 days. The maximum number of pages Googlebot has crawled in one day is 24 and the minimum is 2. That makes sense, because the blog was launched less than 90 days ago, and the chart shows that the number of pages crawled per day has increased over time. The number of pages crawled is sometimes more than the total number of pages in the site -- especially if the same page can be accessed via several URLs. So <a title="http://googlewebmastercentral.blogspot.com/2006/10/learn-more-about-googlebots-crawl-of.html" href="http://googlewebmastercentral.blogspot.com/2006/10/learn-more-about-googlebots-crawl-of.html">http://googlewebmastercentral.blogspot.com/2006/10/learn-more-about-googlebots-crawl-of.html</a> and <a title="http://googlewebmastercentral.blogspot.com/2006/10/learn-more-about-googlebots-crawl-of.html#links" href="http://googlewebmastercentral.blogspot.com/2006/10/learn-more-about-googlebots-crawl-of.html#links">http://googlewebmastercentral.blogspot.com/2006/10/learn-more-about-googlebots-crawl-of.html#links</a> are different, but point to the same page (the second points to an anchor within the page).<br /><span style="font-style: italic; color: rgb(204, 0, 0);"></span><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/5446/4056/1600/pages_final.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/5446/4056/400/pages_final.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><br />And here's the average number of kilobytes downloaded from this blog each day. As you can see, as the site has grown over the last two and a half months, the number of average kilobytes downloaded has increased as well.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/5446/4056/1600/kb_final.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/5446/4056/400/kb_final.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><br />The first two reports can help you diagnose the impact that changes in your site may have on its coverage. If you overhaul your site and dramatically reduce the number of pages, you'll likely notice a drop in the number of pages that Googlebot accesses.<br /><br />The average document download time can help pinpoint subtle networking problems. If the average time spikes, you might have network slowdowns or bottlenecks that you should investigate. Here's the report for this blog that shows that we did have a short spike in early September (the maximum time was 1057 ms), but it quickly went back to a normal level, so things now look OK.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/5446/4056/1600/time_final.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/5446/4056/400/time_final.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a>In general, the load time of a page doesn't affect its ranking, but we wanted to give this info because it can help you spot problems. We hope you will find this data as useful as we do! <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:Googlebot activity reports&url=https://webmasters.googleblog.com/2006/10/googlebot-activity-reports.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/10/googlebot-activity-reports.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/10/googlebot-activity-reports.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en_US' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='116104915326213970' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/10/learn-more-about-googlebots-crawl-of.html?hl=en_US' itemprop='url' title='Learn more about Googlebot's crawl of your site and more!'> Learn more about Googlebot's crawl of your site and more! </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, October 17, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> We've added a few new features to <a href="//www.google.com/webmasters/sitemaps/">webmaster tools</a> and invite you to check them out.<p><span style="font-weight: bold;">Googlebot activity reports</span><br />Check out these cool charts! We show you the number of pages Googlebot's crawled from your site per day, the number of kilobytes of data Googlebot's downloaded per day, and the average time it took Googlebot to download pages. Webmaster tools show each of these for the last 90 days. Stay tuned for more information about this data and how you can use it to pinpoint issues with your site.</p><p><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/googlebot1017.0.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/googlebot1017.0.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a></p><p><span style="font-weight: bold;">Crawl rate control</span><br />Googlebot uses sophisticated algorithms that determine how much to crawl each site. Our goal is to crawl as many pages from your site as we can on each visit without overwhelming your server's bandwidth. </p> <p>We've been conducting a limited test of a new feature that enables you to provide us information about how we crawl your site. Today, we're making this tool available to everyone. You can access this tool from the Diagnostic tab. If you'd like Googlebot to slow down the crawl of your site, simply choose the <span style="font-weight: bold;">Slower </span>option. </p>If we feel your server could handle the additional bandwidth, and we can crawl your site more, we'll let you know and offer the option for a faster crawl.<br /><br />If you request a changed crawl rate, this change will last for 90 days. If you liked the changed rate, you can simply return to webmaster tools and make the change again.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/crawlrate1017.0.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/crawlrate1017.0.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><br /><span style="font-weight: bold;">Enhanced image search</span><br />You can now opt into enhanced image search for the images on your site, which enables our tools such as <a title="Google Image Labeler" href="http://images.google.com/imagelabeler/">Google Image Labeler</a> to associate the images included in your site with labels that will improve indexing and search quality of those images. After you've opted in, you can opt out at any time.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/image1017.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/image1017.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><span style="font-weight: bold;">Number of URLs submitted</span><br />Recently at <a title="SES San Jose" href="http://googlewebmastercentral.blogspot.com/2006/08/back-from-ses-san-jose.html">SES San Jose</a>, a webmaster asked me if we could show the number of URLs we find in a Sitemap. He said that he generates his Sitemaps automatically and he'd like confirmation that the number he thinks he generated is the same number we received. We thought this was a great idea. Simply access the Sitemaps tab to see the number of URLs we found in each Sitemap you've submitted.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/urlcount1017.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/urlcount1017.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a>As always, we hope you find these updates useful and look forward to <a href="http://groups.google.com/group/Google_Webmaster_Help">hearing what you think</a>. <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> We've added a few new features to <a href="//www.google.com/webmasters/sitemaps/">webmaster tools</a> and invite you to check them out.<p><span style="font-weight: bold;">Googlebot activity reports</span><br />Check out these cool charts! We show you the number of pages Googlebot's crawled from your site per day, the number of kilobytes of data Googlebot's downloaded per day, and the average time it took Googlebot to download pages. Webmaster tools show each of these for the last 90 days. Stay tuned for more information about this data and how you can use it to pinpoint issues with your site.</p><p><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/googlebot1017.0.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/googlebot1017.0.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a></p><p><span style="font-weight: bold;">Crawl rate control</span><br />Googlebot uses sophisticated algorithms that determine how much to crawl each site. Our goal is to crawl as many pages from your site as we can on each visit without overwhelming your server's bandwidth. </p> <p>We've been conducting a limited test of a new feature that enables you to provide us information about how we crawl your site. Today, we're making this tool available to everyone. You can access this tool from the Diagnostic tab. If you'd like Googlebot to slow down the crawl of your site, simply choose the <span style="font-weight: bold;">Slower </span>option. </p>If we feel your server could handle the additional bandwidth, and we can crawl your site more, we'll let you know and offer the option for a faster crawl.<br /><br />If you request a changed crawl rate, this change will last for 90 days. If you liked the changed rate, you can simply return to webmaster tools and make the change again.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/crawlrate1017.0.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/crawlrate1017.0.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><br /><span style="font-weight: bold;">Enhanced image search</span><br />You can now opt into enhanced image search for the images on your site, which enables our tools such as <a title="Google Image Labeler" href="http://images.google.com/imagelabeler/">Google Image Labeler</a> to associate the images included in your site with labels that will improve indexing and search quality of those images. After you've opted in, you can opt out at any time.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/image1017.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/image1017.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><span style="font-weight: bold;">Number of URLs submitted</span><br />Recently at <a title="SES San Jose" href="http://googlewebmastercentral.blogspot.com/2006/08/back-from-ses-san-jose.html">SES San Jose</a>, a webmaster asked me if we could show the number of URLs we find in a Sitemap. He said that he generates his Sitemaps automatically and he'd like confirmation that the number he thinks he generated is the same number we received. We thought this was a great idea. Simply access the Sitemaps tab to see the number of URLs we found in each Sitemap you've submitted.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/urlcount1017.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/urlcount1017.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a>As always, we hope you find these updates useful and look forward to <a href="http://groups.google.com/group/Google_Webmaster_Help">hearing what you think</a>. <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:Learn more about Googlebot's crawl of your site and more!&url=https://webmasters.googleblog.com/2006/10/learn-more-about-googlebots-crawl-of.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/10/learn-more-about-googlebots-crawl-of.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/10/learn-more-about-googlebots-crawl-of.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en_US' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/sitemaps?hl=en_US' rel='tag'> sitemaps </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='116058965303349943' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/10/got-website-get-gadgets.html?hl=en_US' itemprop='url' title='Got a website? Get gadgets.'> Got a website? Get gadgets. </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, October 11, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <a href="http://gmodules.com/ig/creator?synd=open&url=http://www.flightstats.com/go/FlightStatus/AddGoogleHomePageFlightStatus.module&source=wmbp"><img alt="" border="1" src="//photos1.blogger.com/blogger/1363/3999/320/FlightStatusGadget2.jpg" style="margin: 0px 0px 10px 10px; float: right;"></a> Google Gadgets are miniature-sized devices that offer cool and dynamic content -- they can be games, news clips, weather reports, maps, or most anything you can dream up. They've been around for a while, but their reach got a lot broader last week when we made it possible for anyone to add gadgets to their own webpages. Here's an example of a flight status tracker, for instance, that can be placed on any page on the web for free.<br /><br />Anyone can search for gadgets to add to their own webpage for free in our directory of <a href="//www.google.com/ig/directory?synd=open&source=wmbp">gadgets for your webpage</a>. To put a gadget on your page, just pick the gadget you like, set your preferences, and copy-and-paste the HTML that is generated for you onto your own page.<br /><br />Creating gadgets for others isn't hard, either, and it can be a great way to get your content in front of people while they're visiting Google or other sites. Here are a few suggestions for distributing your own content on the Google homepage or other pages across the web:<br /><br />* <a href="//www.google.com/apis/homepage/">Create a Google Gadget</a> for distribution across the web. Gadgets can be most anything, from simple HTML to complex applications. It’s easy to experiment with gadgets – anyone with even a little bit of web design experience can make a simple one (even me!), and more advanced programmers can create really snazzy, complex ones. But remember, it’s also quick and easy for people to delete gadgets or add new ones too their own pages. To help you make sure your gadget will be popular across the web, we provide a few <a href="//www.google.com/webmasters/gadgets/guidelines.html">guidelines</a> you can use to create gadgets. The more often folks find your content to be useful, the longer they'll keep your gadget on their pages, and the more often they’ll visit your site.<br /><br />* If your website has a feed, visitors can put snippets of your content on their own Google homepages quickly and easily, and you don't even need to develop a gadget. However, you will be able to customize their experience much more fully with a gadget than with a feed.<br /><br />* By putting the <a href="//www.google.com/webmasters/add.html">“Add to Google” button</a> in a prominent spot on your site, you can increase the reach of your content, because visitors who click to add your gadget or feed to Google can see your content each time they visit the Google homepage. Promoting your own gadget or feed can also increase its popularity, which contributes to a higher ranking in the directory of <a href="//www.google.com/ig/directory?source=wmbp">gadgets for the Google personalized homepage</a>. <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <a href="http://gmodules.com/ig/creator?synd=open&url=http://www.flightstats.com/go/FlightStatus/AddGoogleHomePageFlightStatus.module&source=wmbp"><img alt="" border="1" src="//photos1.blogger.com/blogger/1363/3999/320/FlightStatusGadget2.jpg" style="margin: 0px 0px 10px 10px; float: right;"></a> Google Gadgets are miniature-sized devices that offer cool and dynamic content -- they can be games, news clips, weather reports, maps, or most anything you can dream up. They've been around for a while, but their reach got a lot broader last week when we made it possible for anyone to add gadgets to their own webpages. Here's an example of a flight status tracker, for instance, that can be placed on any page on the web for free.<br /><br />Anyone can search for gadgets to add to their own webpage for free in our directory of <a href="//www.google.com/ig/directory?synd=open&source=wmbp">gadgets for your webpage</a>. To put a gadget on your page, just pick the gadget you like, set your preferences, and copy-and-paste the HTML that is generated for you onto your own page.<br /><br />Creating gadgets for others isn't hard, either, and it can be a great way to get your content in front of people while they're visiting Google or other sites. Here are a few suggestions for distributing your own content on the Google homepage or other pages across the web:<br /><br />* <a href="//www.google.com/apis/homepage/">Create a Google Gadget</a> for distribution across the web. Gadgets can be most anything, from simple HTML to complex applications. It’s easy to experiment with gadgets – anyone with even a little bit of web design experience can make a simple one (even me!), and more advanced programmers can create really snazzy, complex ones. But remember, it’s also quick and easy for people to delete gadgets or add new ones too their own pages. To help you make sure your gadget will be popular across the web, we provide a few <a href="//www.google.com/webmasters/gadgets/guidelines.html">guidelines</a> you can use to create gadgets. The more often folks find your content to be useful, the longer they'll keep your gadget on their pages, and the more often they’ll visit your site.<br /><br />* If your website has a feed, visitors can put snippets of your content on their own Google homepages quickly and easily, and you don't even need to develop a gadget. However, you will be able to customize their experience much more fully with a gadget than with a feed.<br /><br />* By putting the <a href="//www.google.com/webmasters/add.html">“Add to Google” button</a> in a prominent spot on your site, you can increase the reach of your content, because visitors who click to add your gadget or feed to Google can see your content each time they visit the Google homepage. Promoting your own gadget or feed can also increase its popularity, which contributes to a higher ranking in the directory of <a href="//www.google.com/ig/directory?source=wmbp">gadgets for the Google personalized homepage</a>. <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:Got a website? Get gadgets.&url=https://webmasters.googleblog.com/2006/10/got-website-get-gadgets.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/10/got-website-get-gadgets.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/10/got-website-get-gadgets.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/general%20tips?hl=en_US' rel='tag'> general tips </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/products%20and%20services?hl=en_US' rel='tag'> products and services </a> </span> </div> </div> </div> <div class='post' data-id='116043842260522884' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/10/multiple-sitemaps-in-same-directory.html?hl=en_US' itemprop='url' title='Multiple Sitemaps in the same directory'> Multiple Sitemaps in the same directory </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Monday, October 09, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <span style="font-weight: bold;"></span>We've gotten a few questions about whether you can put multiple <a href="//www.google.com/support/webmasters/bin/answer.py?answer=40318&topic=8514" title="Sitemaps">Sitemaps</a> in the same directory. Yes, you can!<br /><br />You might want to have multiple Sitemap files in a single directory for a number of reasons. For instance, if you have an auction site, you might want to have a daily Sitemap with new auction offers and a weekly Sitemap with less time-sensitive URLs. Or you could generate a new Sitemap every day with new offers, so that the list of Sitemaps grows over time. Either of these solutions works just fine.<br /><br />Or, here's another sample scenario: Suppose you're a provider that supports multiple web shops, and they share a similar URL structure differentiated by a parameter. For example:<br /><br />http://example.com/stores/home?id=1<br />http://example.com/stores/home?id=2<br />http://example.com/stores/home?id=3<br /><br />Since they're all in the same directory, it's fine by our rules to put the URLs for all of the stores into a single Sitemap, under http://example.com/ or http://example.com/stores/. However, some webmasters may prefer to have separate Sitemaps for each store, such as:<br /><br />http://example.com/stores/store1_sitemap.xml<br />http://example.com/stores/store2_sitemap.xml<br />http://example.com/stores/store3_sitemap.xml<br /><br />As long as all URLs listed in the Sitemap are at the same location as the Sitemap or in a sub directory (in the above example http://example.com/stores/ or perhaps http://example.com/stores/catalog) it's fine for multiple Sitemaps to live in the same directory (as many as you want!). The important thing is that Sitemaps not contain URLs from parent directories or completely different directories -- if that happens, we can't be sure that the submitter controls the URL's directory, so we can't trust the metadata.<br /><br />The above Sitemaps could also be collected into a single <a href="https://www.google.com/webmasters/sitemaps/docs/en/protocol.html#sitemapFileRequirements" title="Sitemap index file">Sitemap index file</a> and easily be submitted via Google webmaster tools. For example, you could create http://example.com/stores/sitemap_index.xml as follows:<br /><br /><pre><?xml version="1.0" encoding="UTF-8"?><br /><sitemapindex xmlns="http://www.google.com/schemas/sitemap/0.84"><br /> <sitemap><br /> <loc>http://example.com/stores/store1_sitemap.xml</loc><br /> <lastmod>2006-10-01T18:23:17+00:00</lastmod><br /> </sitemap><br /> <sitemap><br /> <loc>http://example.com/stores/store2_sitemap.xml</loc><br /> <lastmod>2006-10-01</lastmod><br /> </sitemap><br /><sitemap><br /> <loc>http://example.com/stores/store3_sitemap.xml</loc><br /> <lastmod>2006-10-05</lastmod><br /> </sitemap><br /></sitemapindex></pre><br />Then simply <a href="//www.google.com/support/webmasters/bin/answer.py?answer=34575&topic=8496" title="add">add</a> the index file to your account, and you'll be able to see any <a href="//www.google.com/support/webmasters/bin/answer.py?answer=35738&topic=8497" title="errors">errors</a> for each of the child Sitemaps.<br /><br />If each store includes more than 50,000 URLs (the maximum number for a single Sitemap), you would need to have multiple Sitemaps for each store. In that case, you may want to create a Sitemap index file for each store that lists the Sitemaps for that store. For instance:<br /><br />http://example.com/stores/store1_sitemapindex.xml<br />http://example.com/stores/store2_sitemapindex.xml<br />http://example.com/stores/store3_sitemapindex.xml<br /><br />Since Sitemap index files can't contain other index files, you would need to submit each Sitemap index file to your account separately.<br /><br />Whether you list all URLs in a single Sitemap or in multiple Sitemaps (in the same directory of different directories) is simply based on what's easiest for you to maintain. We treat the URLs equally for each of these methods of organization. <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <span style="font-weight: bold;"></span>We've gotten a few questions about whether you can put multiple <a href="//www.google.com/support/webmasters/bin/answer.py?answer=40318&topic=8514" title="Sitemaps">Sitemaps</a> in the same directory. Yes, you can!<br /><br />You might want to have multiple Sitemap files in a single directory for a number of reasons. For instance, if you have an auction site, you might want to have a daily Sitemap with new auction offers and a weekly Sitemap with less time-sensitive URLs. Or you could generate a new Sitemap every day with new offers, so that the list of Sitemaps grows over time. Either of these solutions works just fine.<br /><br />Or, here's another sample scenario: Suppose you're a provider that supports multiple web shops, and they share a similar URL structure differentiated by a parameter. For example:<br /><br />http://example.com/stores/home?id=1<br />http://example.com/stores/home?id=2<br />http://example.com/stores/home?id=3<br /><br />Since they're all in the same directory, it's fine by our rules to put the URLs for all of the stores into a single Sitemap, under http://example.com/ or http://example.com/stores/. However, some webmasters may prefer to have separate Sitemaps for each store, such as:<br /><br />http://example.com/stores/store1_sitemap.xml<br />http://example.com/stores/store2_sitemap.xml<br />http://example.com/stores/store3_sitemap.xml<br /><br />As long as all URLs listed in the Sitemap are at the same location as the Sitemap or in a sub directory (in the above example http://example.com/stores/ or perhaps http://example.com/stores/catalog) it's fine for multiple Sitemaps to live in the same directory (as many as you want!). The important thing is that Sitemaps not contain URLs from parent directories or completely different directories -- if that happens, we can't be sure that the submitter controls the URL's directory, so we can't trust the metadata.<br /><br />The above Sitemaps could also be collected into a single <a href="https://www.google.com/webmasters/sitemaps/docs/en/protocol.html#sitemapFileRequirements" title="Sitemap index file">Sitemap index file</a> and easily be submitted via Google webmaster tools. For example, you could create http://example.com/stores/sitemap_index.xml as follows:<br /><br /><pre><?xml version="1.0" encoding="UTF-8"?><br /><sitemapindex xmlns="http://www.google.com/schemas/sitemap/0.84"><br /> <sitemap><br /> <loc>http://example.com/stores/store1_sitemap.xml</loc><br /> <lastmod>2006-10-01T18:23:17+00:00</lastmod><br /> </sitemap><br /> <sitemap><br /> <loc>http://example.com/stores/store2_sitemap.xml</loc><br /> <lastmod>2006-10-01</lastmod><br /> </sitemap><br /><sitemap><br /> <loc>http://example.com/stores/store3_sitemap.xml</loc><br /> <lastmod>2006-10-05</lastmod><br /> </sitemap><br /></sitemapindex></pre><br />Then simply <a href="//www.google.com/support/webmasters/bin/answer.py?answer=34575&topic=8496" title="add">add</a> the index file to your account, and you'll be able to see any <a href="//www.google.com/support/webmasters/bin/answer.py?answer=35738&topic=8497" title="errors">errors</a> for each of the child Sitemaps.<br /><br />If each store includes more than 50,000 URLs (the maximum number for a single Sitemap), you would need to have multiple Sitemaps for each store. In that case, you may want to create a Sitemap index file for each store that lists the Sitemaps for that store. For instance:<br /><br />http://example.com/stores/store1_sitemapindex.xml<br />http://example.com/stores/store2_sitemapindex.xml<br />http://example.com/stores/store3_sitemapindex.xml<br /><br />Since Sitemap index files can't contain other index files, you would need to submit each Sitemap index file to your account separately.<br /><br />Whether you list all URLs in a single Sitemap or in multiple Sitemaps (in the same directory of different directories) is simply based on what's easiest for you to maintain. We treat the URLs equally for each of these methods of organization. <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:Multiple Sitemaps in the same directory&url=https://webmasters.googleblog.com/2006/10/multiple-sitemaps-in-same-directory.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/10/multiple-sitemaps-in-same-directory.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/10/multiple-sitemaps-in-same-directory.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/sitemaps?hl=en_US' rel='tag'> sitemaps </a> </span> </div> </div> </div> <div class='post' data-id='116009774210312195' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/10/useful-information-you-may-have-missed.html?hl=en_US' itemprop='url' title='Useful information you may have missed'> Useful information you may have missed </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, October 05, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <span style="font-weight: bold;"></span>When we launched this blog in early August, we said goodbye to the <span style="font-style: italic;">Inside Google Sitemaps</span> blog and started redirecting it here. The redirect makes the posts we did there a little difficult to get to. For those of you who started reading with this newer blog, here are links to some of the older posts that may be of interest. <br /><ul><li><a href="http://sitemaps.blogspot.com/2006/08/back-from-blogher.html">Tips from BlogHer</a> | <a href="http://sitemaps.blogspot.com/2006/08/blogher-tips.html"> More tips</a> </li><li><a href="http://sitemaps.blogspot.com/2006/07/more-control-over-page-snippets.html">Opting-out of Open Directory Project descriptions</a> and <a href="http://sitemaps.blogspot.com/2006/07/more-control-over-titles-too.html">titles</a> in our search results </li><li><a href="http://sitemaps.blogspot.com/2006/07/tips-for-non-us-sites.html">Tips for non-US sites</a> </li><li><a href="http://sitemaps.blogspot.com/2006/06/webmaster-help-center-updates.html">Information on robots.txt files</a> | <a href="http://sitemaps.blogspot.com/2006/02/using-robotstxt-file.html">More tips on using a robots.txt file</a> </li><li><a href="http://sitemaps.blogspot.com/2006/02/improving-your-sites-indexing-and.html">Improving your site's indexing and ranking 101</a> </li><li><a href="http://sitemaps.blogspot.com/2005/11/changing-domains.html">Changing domain names</a> | <a href="http://sitemaps.blogspot.com/2006/01/more-about-changing-domain-names.html">More about changing domain names</a> </li></ul> <b><br />Webmaster Tools Account questions</b> <br /><ul><li><a href="http://sitemaps.blogspot.com/2006/02/giving-others-access-to-sitemaps.html">Can multiple account holders view information for a site?</a> </li><li><a title="About meta tag verification" href="http://sitemaps.blogspot.com/2006/05/more-about-meta-tag-verification.html">About meta tag verification</a> </li><li><a href="http://sitemaps.blogspot.com/2006/02/unexpected-common-words.html">About the common words feature</a> </li><li><a href="http://sitemaps.blogspot.com/2005/10/when-your-site-changes.html">Changing your Sitemap when your site changes</a> </li><li><a href="http://sitemaps.blogspot.com/2005/10/including-site-pages-in-sitemap.html">Do you have to include every page from your site in your Sitemap?</a> </li><li><a href="http://sitemaps.blogspot.com/2005/09/verifying-your-site-trouble-with-404.html">If you try to verify and get the error: We've detected that your 404 (file not found) error page returns a status of 200 (OK) in the header</a> </li><li><a href="http://sitemaps.blogspot.com/2005/08/submitting-mobile-sitemaps.html">Submitting mobile Sitemaps</a> </li></ul> And you can always browse the <a title="blog's archives" href="http://sitemaps.blogspot.com/archives/2006_08_01_sitemaps_archive.html">blog's archives</a> . <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <span style="font-weight: bold;"></span>When we launched this blog in early August, we said goodbye to the <span style="font-style: italic;">Inside Google Sitemaps</span> blog and started redirecting it here. The redirect makes the posts we did there a little difficult to get to. For those of you who started reading with this newer blog, here are links to some of the older posts that may be of interest. <br /><ul><li><a href="http://sitemaps.blogspot.com/2006/08/back-from-blogher.html">Tips from BlogHer</a> | <a href="http://sitemaps.blogspot.com/2006/08/blogher-tips.html"> More tips</a> </li><li><a href="http://sitemaps.blogspot.com/2006/07/more-control-over-page-snippets.html">Opting-out of Open Directory Project descriptions</a> and <a href="http://sitemaps.blogspot.com/2006/07/more-control-over-titles-too.html">titles</a> in our search results </li><li><a href="http://sitemaps.blogspot.com/2006/07/tips-for-non-us-sites.html">Tips for non-US sites</a> </li><li><a href="http://sitemaps.blogspot.com/2006/06/webmaster-help-center-updates.html">Information on robots.txt files</a> | <a href="http://sitemaps.blogspot.com/2006/02/using-robotstxt-file.html">More tips on using a robots.txt file</a> </li><li><a href="http://sitemaps.blogspot.com/2006/02/improving-your-sites-indexing-and.html">Improving your site's indexing and ranking 101</a> </li><li><a href="http://sitemaps.blogspot.com/2005/11/changing-domains.html">Changing domain names</a> | <a href="http://sitemaps.blogspot.com/2006/01/more-about-changing-domain-names.html">More about changing domain names</a> </li></ul> <b><br />Webmaster Tools Account questions</b> <br /><ul><li><a href="http://sitemaps.blogspot.com/2006/02/giving-others-access-to-sitemaps.html">Can multiple account holders view information for a site?</a> </li><li><a title="About meta tag verification" href="http://sitemaps.blogspot.com/2006/05/more-about-meta-tag-verification.html">About meta tag verification</a> </li><li><a href="http://sitemaps.blogspot.com/2006/02/unexpected-common-words.html">About the common words feature</a> </li><li><a href="http://sitemaps.blogspot.com/2005/10/when-your-site-changes.html">Changing your Sitemap when your site changes</a> </li><li><a href="http://sitemaps.blogspot.com/2005/10/including-site-pages-in-sitemap.html">Do you have to include every page from your site in your Sitemap?</a> </li><li><a href="http://sitemaps.blogspot.com/2005/09/verifying-your-site-trouble-with-404.html">If you try to verify and get the error: We've detected that your 404 (file not found) error page returns a status of 200 (OK) in the header</a> </li><li><a href="http://sitemaps.blogspot.com/2005/08/submitting-mobile-sitemaps.html">Submitting mobile Sitemaps</a> </li></ul> And you can always browse the <a title="blog's archives" href="http://sitemaps.blogspot.com/archives/2006_08_01_sitemaps_archive.html">blog's archives</a> . <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:Useful information you may have missed&url=https://webmasters.googleblog.com/2006/10/useful-information-you-may-have-missed.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/10/useful-information-you-may-have-missed.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/10/useful-information-you-may-have-missed.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en_US' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='115946761504064571' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/09/fresher-query-stats.html?hl=en_US' itemprop='url' title='Fresher query stats'> Fresher query stats </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, September 28, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> Query stats in webmaster tools provide information about the search queries that most often return your site in the results. You can view this information by a variety of search types (such as web search, mobile search, or image search) and countries. We show you the top search types and locations for your site. You can access these stats by selecting a verified site in your account and then choosing <span style="font-weight: bold;">Query stats </span>from the Statistics tab.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/querypic.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/querypic.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><br />If you've checked your site's query stats lately, you may have noticed that they're changing more often than they used to. This is because we recently changed how frequently we calculate them. Previously, we showed data that was averaged over a period of three weeks. Now, we show data that is averaged over a period of one week. This results in fresher stats for you, as well as stats that more accurately reflect the current queries that return your site in the results. We update these stats every week, so if you'd like to keep a history of the top queries for your site week by week, you can simply download the data each week. We generally update this data each Monday.<br /><br /><span style="font-weight: bold;">How we calculate query stats</span><br /><a href="http://learn-to-market-online116.blogspot.com/2006/07/google-query-stats-questions-what-does.html">Some of you have asked</a> how we calculate query stats.<br /><br />These results are based on results that searchers see. For instance, say a search for [Britney Spears] brings up your site as position 21, which is on the third page of the results. And say 1000 people searched for [Britney Spears] during the course of a week (in reality, a few more people than that search for her name, but just go with me for this example). 600 of those people only looked at the first page of results and the other 400 browsed to at least the third page. That means that your site was seen by 400 searchers. Even though your site was at position 21 for all 1000 searchers, only 400 are counted for purposes of this calculation.<br /><br />Both <span style="font-weight: bold;">top search queries</span> and <span style="font-weight: bold;">top search query clicks</span> are based on the total number of searches for each query. The stats we show are based on the queries that most often return your site in the results. For instance, going back to that familiar [Britney Spears] query -- 400 searchers saw your site in the results. Now, maybe your site isn't really about Britney Spears -- it's more about Buffy the Vampire Slayer. And say Google received 50 queries for [Buffy the Vampire Slayer] in the same week, and your site was returned in the results at position 2. So, all 50 searchers saw your site in the results. In this example, Britney Spears would show as a top search query above Buffy the Vampire Slayer (because your site was seen by 400 searchers for Britney but 50 searchers for Buffy).<br /><br />The same is true of top search query clicks. If 100 of the Britney-seekers clicked on your site in the search results and all 50 of the Buffy-searchers click on your site in the search results, Britney would show as a top search query above Buffy.<br /><br />At times, this may cause some of the query stats we show you to seem unusual. If your site is returned for a very high-traffic query, then even if a low percentage of searchers click on your site for that query, the total <span style="font-style: italic;">number </span>of searchers who click on your site may still be higher for the query than for queries for which a much higher percentage of searchers click on your site in the results.<br /><br />The <span style="font-weight: bold;">average top position</span> for <span style="font-style: italic;">top search queries</span> is the position of the page on your site that ranks most highly for the query. The average top position for <span style="font-style: italic;">top search query clicks</span> is the position of the page on your site that searchers clicked on (even if a different page ranked more highly for the query). We show you the average position for this top page across all data centers over the course of the week.<br /><br />A variety of download options are available. You can:<br /><ul><li>download individual tables of data by clicking the <span style="font-weight: bold;">Download this table</span> link.</li><li>download stats for all subfolders on your site (for all search types and locations) by clicking the <span style="font-weight: bold;">Download all query stats for this site (including subfolders)</span> link.</li><li>download all stats (including query stats) for all verified sites in your account by choosing <span style="font-weight: bold;">Tools </span>from the My Sites page, then choosing <span style="font-weight: bold;">Download data for all sites</span> and then <span style="font-weight: bold;">Download statistics for all sites</span>.</li></ul> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> Query stats in webmaster tools provide information about the search queries that most often return your site in the results. You can view this information by a variety of search types (such as web search, mobile search, or image search) and countries. We show you the top search types and locations for your site. You can access these stats by selecting a verified site in your account and then choosing <span style="font-weight: bold;">Query stats </span>from the Statistics tab.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="//photos1.blogger.com/blogger/3402/1340/1600/querypic.gif"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/querypic.png" style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;"></a><br />If you've checked your site's query stats lately, you may have noticed that they're changing more often than they used to. This is because we recently changed how frequently we calculate them. Previously, we showed data that was averaged over a period of three weeks. Now, we show data that is averaged over a period of one week. This results in fresher stats for you, as well as stats that more accurately reflect the current queries that return your site in the results. We update these stats every week, so if you'd like to keep a history of the top queries for your site week by week, you can simply download the data each week. We generally update this data each Monday.<br /><br /><span style="font-weight: bold;">How we calculate query stats</span><br /><a href="http://learn-to-market-online116.blogspot.com/2006/07/google-query-stats-questions-what-does.html">Some of you have asked</a> how we calculate query stats.<br /><br />These results are based on results that searchers see. For instance, say a search for [Britney Spears] brings up your site as position 21, which is on the third page of the results. And say 1000 people searched for [Britney Spears] during the course of a week (in reality, a few more people than that search for her name, but just go with me for this example). 600 of those people only looked at the first page of results and the other 400 browsed to at least the third page. That means that your site was seen by 400 searchers. Even though your site was at position 21 for all 1000 searchers, only 400 are counted for purposes of this calculation.<br /><br />Both <span style="font-weight: bold;">top search queries</span> and <span style="font-weight: bold;">top search query clicks</span> are based on the total number of searches for each query. The stats we show are based on the queries that most often return your site in the results. For instance, going back to that familiar [Britney Spears] query -- 400 searchers saw your site in the results. Now, maybe your site isn't really about Britney Spears -- it's more about Buffy the Vampire Slayer. And say Google received 50 queries for [Buffy the Vampire Slayer] in the same week, and your site was returned in the results at position 2. So, all 50 searchers saw your site in the results. In this example, Britney Spears would show as a top search query above Buffy the Vampire Slayer (because your site was seen by 400 searchers for Britney but 50 searchers for Buffy).<br /><br />The same is true of top search query clicks. If 100 of the Britney-seekers clicked on your site in the search results and all 50 of the Buffy-searchers click on your site in the search results, Britney would show as a top search query above Buffy.<br /><br />At times, this may cause some of the query stats we show you to seem unusual. If your site is returned for a very high-traffic query, then even if a low percentage of searchers click on your site for that query, the total <span style="font-style: italic;">number </span>of searchers who click on your site may still be higher for the query than for queries for which a much higher percentage of searchers click on your site in the results.<br /><br />The <span style="font-weight: bold;">average top position</span> for <span style="font-style: italic;">top search queries</span> is the position of the page on your site that ranks most highly for the query. The average top position for <span style="font-style: italic;">top search query clicks</span> is the position of the page on your site that searchers clicked on (even if a different page ranked more highly for the query). We show you the average position for this top page across all data centers over the course of the week.<br /><br />A variety of download options are available. You can:<br /><ul><li>download individual tables of data by clicking the <span style="font-weight: bold;">Download this table</span> link.</li><li>download stats for all subfolders on your site (for all search types and locations) by clicking the <span style="font-weight: bold;">Download all query stats for this site (including subfolders)</span> link.</li><li>download all stats (including query stats) for all verified sites in your account by choosing <span style="font-weight: bold;">Tools </span>from the My Sites page, then choosing <span style="font-weight: bold;">Download data for all sites</span> and then <span style="font-weight: bold;">Download statistics for all sites</span>.</li></ul> <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:Fresher query stats&url=https://webmasters.googleblog.com/2006/09/fresher-query-stats.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/09/fresher-query-stats.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/09/fresher-query-stats.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%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='115938128130607995' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/09/introducing-google-checkout.html?hl=en_US' itemprop='url' title='Introducing Google Checkout'> Introducing Google Checkout </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, September 27, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> For you webmasters that manage sites that sell online, we'd like to introduce you to one of our newest products, <a title="Google Checkout" href="https://checkout.google.com/sell?promo=swmb">Google Checkout</a>. Google Checkout is a checkout process that you integrate with your site(s), enabling your customers to quickly buy from you by providing only a single username and password. From there, you can use Checkout to charge your customers' credit cards and process their orders.<br /><br />Users of Google's search advertising program, <a title="AdWords" href="http://adwords.google.com/">AdWords</a>, get the added benefit of the Google Checkout badge and free transaction processing. The Google Checkout badge is an icon that appears on your AdWords ads and improves the effectiveness of your advertising by letting searchers know that you accept Checkout. Also, for every $1 you spend on AdWords, you can process $10 of Checkout sales for free. Even if you don't use AdWords, you can still process sales for a low 2% and $0.20 per transaction. So if you're interested in implementing Google Checkout, we encourage you to <a title="learn more " href="https://checkout.google.com/sell?promo=swmb">learn more</a>.<br /><br />If you're managing the sites of other sellers, you might want to sign up for our <a title="merchant referral program" href="https://services.google.com/inquiry/checkout_merchant_referrals">merchant referral program</a> where you can earn cash for helping your sellers get up and running with Google Checkout. You can earn $25 for every merchant you refer that processes at least 3 unique customer transactions and $500 in Checkout sales. And you can earn $5 for every $1,000 of Checkout sales processed by the merchants you refer. If you're interested, <a title="apply here" href="https://services.google.com/inquiry/checkout_merchant_referrals">apply here</a>. <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> For you webmasters that manage sites that sell online, we'd like to introduce you to one of our newest products, <a title="Google Checkout" href="https://checkout.google.com/sell?promo=swmb">Google Checkout</a>. Google Checkout is a checkout process that you integrate with your site(s), enabling your customers to quickly buy from you by providing only a single username and password. From there, you can use Checkout to charge your customers' credit cards and process their orders.<br /><br />Users of Google's search advertising program, <a title="AdWords" href="http://adwords.google.com/">AdWords</a>, get the added benefit of the Google Checkout badge and free transaction processing. The Google Checkout badge is an icon that appears on your AdWords ads and improves the effectiveness of your advertising by letting searchers know that you accept Checkout. Also, for every $1 you spend on AdWords, you can process $10 of Checkout sales for free. Even if you don't use AdWords, you can still process sales for a low 2% and $0.20 per transaction. So if you're interested in implementing Google Checkout, we encourage you to <a title="learn more " href="https://checkout.google.com/sell?promo=swmb">learn more</a>.<br /><br />If you're managing the sites of other sellers, you might want to sign up for our <a title="merchant referral program" href="https://services.google.com/inquiry/checkout_merchant_referrals">merchant referral program</a> where you can earn cash for helping your sellers get up and running with Google Checkout. You can earn $25 for every merchant you refer that processes at least 3 unique customer transactions and $500 in Checkout sales. And you can earn $5 for every $1,000 of Checkout sales processed by the merchants you refer. If you're interested, <a title="apply here" href="https://services.google.com/inquiry/checkout_merchant_referrals">apply here</a>. <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 Google Checkout&url=https://webmasters.googleblog.com/2006/09/introducing-google-checkout.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/09/introducing-google-checkout.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/09/introducing-google-checkout.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_US' rel='tag'> products and services </a> </span> </div> </div> </div> <div class='post' data-id='115877813163290113' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/09/how-to-verify-googlebot.html?hl=en_US' itemprop='url' title='How to verify Googlebot'> How to verify Googlebot </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Wednesday, September 20, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> Lately I've heard a couple <a href="http://www.crawlwall.com/">smart</a> <a href="http://www.crazyguyonabike.com/">people</a> ask that search engines provide a way know that a bot is authentic. After all, any spammer could name their bot "Googlebot" and claim to be Google, so which bots do you trust and which do you block?<br /><br />The common request we hear is to post a list of Googlebot IP addresses in some public place. The problem with that is that if/when the IP ranges of our crawlers change, not everyone will know to check. In fact, the crawl team migrated Googlebot IPs a couple years ago and it was a real hassle alerting webmasters who had hard-coded an IP range. So the crawl folks have provided another way to authenticate Googlebot. Here's an answer from one of the crawl people (quoted with their permission):<br /><br /><blockquote><br />Telling webmasters to use DNS to verify on a case-by-case basis seems like the best way to go. I think the recommended technique would be to do a reverse DNS lookup, verify that the name is in the googlebot.com domain, and then do a corresponding forward DNS->IP lookup using that googlebot.com name; eg:<br /><br />> host 66.249.66.1<br />1.66.249.66.in-addr.arpa domain name pointer crawl-66-249-66-1.googlebot.com.<br /><br />> host crawl-66-249-66-1.googlebot.com<br />crawl-66-249-66-1.googlebot.com has address 66.249.66.1<br /><br />I don't think just doing a reverse DNS lookup is sufficient, because a spoofer could set up reverse DNS to point to crawl-a-b-c-d.googlebot.com.<br /></blockquote><br /><br />This answer has also been provided to our help-desk, so I'd consider it an official way to authenticate Googlebot. In order to fetch from the "official" Googlebot IP range, the bot has to respect robots.txt and our internal hostload conventions so that Google doesn't crawl you too hard.<br /><br />(Thanks to N. and J. for help on this answer from the crawl side of things.) <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> Lately I've heard a couple <a href="http://www.crawlwall.com/">smart</a> <a href="http://www.crazyguyonabike.com/">people</a> ask that search engines provide a way know that a bot is authentic. After all, any spammer could name their bot "Googlebot" and claim to be Google, so which bots do you trust and which do you block?<br /><br />The common request we hear is to post a list of Googlebot IP addresses in some public place. The problem with that is that if/when the IP ranges of our crawlers change, not everyone will know to check. In fact, the crawl team migrated Googlebot IPs a couple years ago and it was a real hassle alerting webmasters who had hard-coded an IP range. So the crawl folks have provided another way to authenticate Googlebot. Here's an answer from one of the crawl people (quoted with their permission):<br /><br /><blockquote><br />Telling webmasters to use DNS to verify on a case-by-case basis seems like the best way to go. I think the recommended technique would be to do a reverse DNS lookup, verify that the name is in the googlebot.com domain, and then do a corresponding forward DNS->IP lookup using that googlebot.com name; eg:<br /><br />> host 66.249.66.1<br />1.66.249.66.in-addr.arpa domain name pointer crawl-66-249-66-1.googlebot.com.<br /><br />> host crawl-66-249-66-1.googlebot.com<br />crawl-66-249-66-1.googlebot.com has address 66.249.66.1<br /><br />I don't think just doing a reverse DNS lookup is sufficient, because a spoofer could set up reverse DNS to point to crawl-a-b-c-d.googlebot.com.<br /></blockquote><br /><br />This answer has also been provided to our help-desk, so I'd consider it an official way to authenticate Googlebot. In order to fetch from the "official" Googlebot IP range, the bot has to respect robots.txt and our internal hostload conventions so that Google doesn't crawl you too hard.<br /><br />(Thanks to N. and J. for help on this answer from the crawl side of things.) <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 verify Googlebot&url=https://webmasters.googleblog.com/2006/09/how-to-verify-googlebot.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/09/how-to-verify-googlebot.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/09/how-to-verify-googlebot.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en_US' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/general%20tips?hl=en_US' rel='tag'> general tips </a> </span> </div> </div> </div> <div class='post' data-id='115870902261649332' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/09/debugging-blocked-urls_19.html?hl=en_US' itemprop='url' title='Debugging blocked URLs'> Debugging blocked URLs </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, September 19, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> Vanessa's been posting a lot lately, and I'm starting to feel left out. So here my tidbit of wisdom for you: I've noticed a couple of webmasters confused by "<a href="//www.google.com/support/webmasters/bin/answer.py?answer=35235" title="blocked by robots.txt">blocked by robots.txt</a>" errors, and I wanted to share the steps I take when debugging <a href="//www.google.com/support/webmasters/bin/answer.py?answer=40360" title="robots.txt">robots.txt</a> problems:<br /><br /><span style="font-weight: bold;">A handy checklist for debugging a blocked URL<br /><br /></span><div style="margin-left: 40px;"> Let's assume you are looking at crawl errors for your website and notice a URL restricted by robots.txt that you weren't intending to block:<br />http://www.example.com/amanda.html URL restricted by robots.txt Sep 3, 2006<br /><br /> <span style="font-weight: bold;">Check the robots.txt analysis tool</span><br />The first thing you should do is go to the <a href="//www.google.com/support/webmasters/bin/answer.py?answer=35237" title="robots.txt analysis tool">robots.txt analysis tool</a> for that site. Make sure you are looking at the correct site for that URL, paying attention that you are looking at the right protocol and subdomain. (Subdomains and protocols may have their own robots.txt file, so https://www.example.com/robots.txt may be different from http://example.com/robots.txt and may be different from http://amanda.example.com/robots.txt.) Paste the blocked URL into the "Test URLs against this robots.txt file" box. If the tool reports that it is blocked, you've found your problem. If the tool reports that it's allowed, we need to investigate further.<br /><br />At the top of the robots.txt analysis tool, take a look at the <a href="//www.google.com/support/webmasters/bin/answer.py?answer=83040">HTTP status code</a>. If we are reporting anything other than a 200 (Success) or a 404 (Not found) then we may not be able to reach your robots.txt file, which stops our crawling process. (Note that you can see the last time we downloaded your robots.txt file at the top of this tool. If you make changes to your file, check this date and time to see if your changes were made after our last download.)<br /><br /><span style="font-weight: bold;">Check for changes in your robots.txt file</span><br />If these look fine, you may want to check and see if your robots.txt file has changed since the error occurred by checking the date to see when your robots.txt file was last modified. If it was modified after the date given for the error in the crawl errors, it might be that someone has changed the file so that the new version no longer blocks this URL.<br /><br /><span style="font-weight: bold;">Check for redirects of the URL</span><br />If you can be certain that this URL isn't blocked, check to see if the URL redirects to another page. When Googlebot fetches a URL, it checks the robots.txt file to make sure it is allowed to access the URL. If the robots.txt file allows access to the URL, but the URL returns a redirect, Googlebot checks the robots.txt file again to see if the destination URL is accessible. If at any point Googlebot is redirected to a blocked URL, it reports that it could not get the content of the original URL because it was blocked by robots.txt.<br /><br />Sometimes this behavior is easy to spot because a particular URL always redirects to another one. But sometimes this can be tricky to figure out. For instance:<br /></div> <ul style="margin-left: 40px;"><li> Your site may not have a robots.txt file at all (and therefore, allows access to all pages), but a URL on the site may redirect to a different site, which does have a robots.txt file. In this case, you may see URLs blocked by robots.txt for your site (even though you don't have a robots.txt file).</li><li> Your site may prompt for registration after a certain number of page views. You may have the registration page blocked by a robots.txt file. In this case, the URL itself may not redirect, but if Googlebot triggers the registration prompt when accessing the URL, it will be redirected to the blocked registration page, and the original URL will be listed in the crawl errors page as blocked by robots.txt.<br /></li></ul> <div style="margin-left: 40px;"> <br /> <span style="font-weight: bold;">Ask for help</span><br />Finally, if you still can't pinpoint the problem, you might want to post on our <a href="http://groups-beta.google.com/group/Google_Webmaster_Help" title="forum">forum</a> for help. Be sure to include the URL that is blocked in your message. Sometimes its easier for other people to notice oversights you may have missed.<br /></div><br />Good luck debugging! And by the way -- unrelated to robots.txt -- make sure that you don't have "noindex" meta tags at the top of your web pages; those also result in Google not showing a web site in our index. <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> Vanessa's been posting a lot lately, and I'm starting to feel left out. So here my tidbit of wisdom for you: I've noticed a couple of webmasters confused by "<a href="//www.google.com/support/webmasters/bin/answer.py?answer=35235" title="blocked by robots.txt">blocked by robots.txt</a>" errors, and I wanted to share the steps I take when debugging <a href="//www.google.com/support/webmasters/bin/answer.py?answer=40360" title="robots.txt">robots.txt</a> problems:<br /><br /><span style="font-weight: bold;">A handy checklist for debugging a blocked URL<br /><br /></span><div style="margin-left: 40px;"> Let's assume you are looking at crawl errors for your website and notice a URL restricted by robots.txt that you weren't intending to block:<br />http://www.example.com/amanda.html URL restricted by robots.txt Sep 3, 2006<br /><br /> <span style="font-weight: bold;">Check the robots.txt analysis tool</span><br />The first thing you should do is go to the <a href="//www.google.com/support/webmasters/bin/answer.py?answer=35237" title="robots.txt analysis tool">robots.txt analysis tool</a> for that site. Make sure you are looking at the correct site for that URL, paying attention that you are looking at the right protocol and subdomain. (Subdomains and protocols may have their own robots.txt file, so https://www.example.com/robots.txt may be different from http://example.com/robots.txt and may be different from http://amanda.example.com/robots.txt.) Paste the blocked URL into the "Test URLs against this robots.txt file" box. If the tool reports that it is blocked, you've found your problem. If the tool reports that it's allowed, we need to investigate further.<br /><br />At the top of the robots.txt analysis tool, take a look at the <a href="//www.google.com/support/webmasters/bin/answer.py?answer=83040">HTTP status code</a>. If we are reporting anything other than a 200 (Success) or a 404 (Not found) then we may not be able to reach your robots.txt file, which stops our crawling process. (Note that you can see the last time we downloaded your robots.txt file at the top of this tool. If you make changes to your file, check this date and time to see if your changes were made after our last download.)<br /><br /><span style="font-weight: bold;">Check for changes in your robots.txt file</span><br />If these look fine, you may want to check and see if your robots.txt file has changed since the error occurred by checking the date to see when your robots.txt file was last modified. If it was modified after the date given for the error in the crawl errors, it might be that someone has changed the file so that the new version no longer blocks this URL.<br /><br /><span style="font-weight: bold;">Check for redirects of the URL</span><br />If you can be certain that this URL isn't blocked, check to see if the URL redirects to another page. When Googlebot fetches a URL, it checks the robots.txt file to make sure it is allowed to access the URL. If the robots.txt file allows access to the URL, but the URL returns a redirect, Googlebot checks the robots.txt file again to see if the destination URL is accessible. If at any point Googlebot is redirected to a blocked URL, it reports that it could not get the content of the original URL because it was blocked by robots.txt.<br /><br />Sometimes this behavior is easy to spot because a particular URL always redirects to another one. But sometimes this can be tricky to figure out. For instance:<br /></div> <ul style="margin-left: 40px;"><li> Your site may not have a robots.txt file at all (and therefore, allows access to all pages), but a URL on the site may redirect to a different site, which does have a robots.txt file. In this case, you may see URLs blocked by robots.txt for your site (even though you don't have a robots.txt file).</li><li> Your site may prompt for registration after a certain number of page views. You may have the registration page blocked by a robots.txt file. In this case, the URL itself may not redirect, but if Googlebot triggers the registration prompt when accessing the URL, it will be redirected to the blocked registration page, and the original URL will be listed in the crawl errors page as blocked by robots.txt.<br /></li></ul> <div style="margin-left: 40px;"> <br /> <span style="font-weight: bold;">Ask for help</span><br />Finally, if you still can't pinpoint the problem, you might want to post on our <a href="http://groups-beta.google.com/group/Google_Webmaster_Help" title="forum">forum</a> for help. Be sure to include the URL that is blocked in your message. Sometimes its easier for other people to notice oversights you may have missed.<br /></div><br />Good luck debugging! And by the way -- unrelated to robots.txt -- make sure that you don't have "noindex" meta tags at the top of your web pages; those also result in Google not showing a web site in our index. <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:Debugging blocked URLs&url=https://webmasters.googleblog.com/2006/09/debugging-blocked-urls_19.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/09/debugging-blocked-urls_19.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/09/debugging-blocked-urls_19.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en_US' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='115836477023839908' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/09/for-those-wondering-about-public.html?hl=en_US' itemprop='url' title='For Those Wondering About Public Service Search'> For Those Wondering About Public Service Search </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Friday, September 15, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <p style="padding:0.8em; border-left: 6px solid #A03; background-color:#FEE; color:#000; line-height:1.5em; font-weight:bold">Update: The described product or service is no longer available. <a href="http://googlewebmastercentral.blogspot.com/2007/02/update-on-public-service-search.html">More information</a>.<br /></p> <div dir="ltr" style="text-align: left;" trbidi="on"> We recently learned of a security issue with our Public Service Search service and disabled login functionality temporarily to protect our Public Service Search users while we were working to fix the problem. We are not aware of any malicious exploits of this problem and this service represents an extremely small portion of searches.<br /> <br /> We have a temporary fix in place currently that prevents exploitation of this problem and will have a permanent solution in place shortly. Unfortunately, the temporary fix may inconvenience a small number of Public Service Search users in the following ways:<br /> <br /> * Public Service Search is currently not open to new signups.<br /> * If you use Public Service Search on your site, you are currently unable to log in to make changes, but rest assured that Public Service Search continues to function properly on your site.<br /> * The template system is currently disabled, so search results will appear in a standard Google search results format, rather than customized to match the look and feel of your site. However, the search results themselves are not being modified.<br /> <br /> <br /> If you are a Public Service Search user and are having trouble logging in right now, please sit tight. As soon as the permanent solution is in place the service will be back on its feet again. In the meantime, you will still be able to provide site-specific searches on your site as usual.<br /> <br /> Google introduced this service several years ago to support universities and non-profit organizations by offering ad-free search capabilities for their sites. Our non-profit and university users are extremely important to us and we apologize for any inconvenience this may cause.<br /> <br /> Please post any questions or concerns in our <a href="http://groups.google.com/group/Google_Webmaster_Help" title="webmaster discussion forum">webmaster discussion forum</a> and we'll try our best to answer any questions you may have.</div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <p style="padding:0.8em; border-left: 6px solid #A03; background-color:#FEE; color:#000; line-height:1.5em; font-weight:bold">Update: The described product or service is no longer available. <a href="http://googlewebmastercentral.blogspot.com/2007/02/update-on-public-service-search.html">More information</a>.<br /></p> <div dir="ltr" style="text-align: left;" trbidi="on"> We recently learned of a security issue with our Public Service Search service and disabled login functionality temporarily to protect our Public Service Search users while we were working to fix the problem. We are not aware of any malicious exploits of this problem and this service represents an extremely small portion of searches.<br /> <br /> We have a temporary fix in place currently that prevents exploitation of this problem and will have a permanent solution in place shortly. Unfortunately, the temporary fix may inconvenience a small number of Public Service Search users in the following ways:<br /> <br /> * Public Service Search is currently not open to new signups.<br /> * If you use Public Service Search on your site, you are currently unable to log in to make changes, but rest assured that Public Service Search continues to function properly on your site.<br /> * The template system is currently disabled, so search results will appear in a standard Google search results format, rather than customized to match the look and feel of your site. However, the search results themselves are not being modified.<br /> <br /> <br /> If you are a Public Service Search user and are having trouble logging in right now, please sit tight. As soon as the permanent solution is in place the service will be back on its feet again. In the meantime, you will still be able to provide site-specific searches on your site as usual.<br /> <br /> Google introduced this service several years ago to support universities and non-profit organizations by offering ad-free search capabilities for their sites. Our non-profit and university users are extremely important to us and we apologize for any inconvenience this may cause.<br /> <br /> Please post any questions or concerns in our <a href="http://groups.google.com/group/Google_Webmaster_Help" title="webmaster discussion forum">webmaster discussion forum</a> and we'll try our best to answer any questions you may have.</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:For Those Wondering About Public Service Search&url=https://webmasters.googleblog.com/2006/09/for-those-wondering-about-public.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/09/for-those-wondering-about-public.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/09/for-those-wondering-about-public.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_US' rel='tag'> products and services </a> </span> </div> </div> </div> <div class='post' data-id='115806719889561827' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/09/setting-preferred-domain.html?hl=en_US' itemprop='url' title='Setting the preferred domain'> Setting the preferred domain </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, September 12, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> <span style="font-weight: bold;"></span>Based on your input, we've recently made a few changes to the preferred domain feature of webmaster tools. And since you've had some questions about this feature, we'd like to answer them.<br /><span style="font-weight: bold;"></span><br />The <a href="//www.google.com/support/webmasters/bin/answer.py?answer=44231&topic=9025" title="preferred domain feature">preferred domain feature</a> enables you to tell us if you'd like URLs from your site crawled and indexed using the www version of the domain (http://www.example.com) or the non-www version of the domain (http://example.com). When we initially launched this, we added the non-preferred version to your account when you specified a preference so that you could see any information associated with the non-preferred version. But many of you found that confusing, so we've made the following changes:<br /><ul><li> When you set the preferred domain, we no longer will add the non-preferred version to your account. </li><li> If you had previously added the non-preferred version to your account, you'll still see it listed there, but you won't be able to add a Sitemap for the non-preferred version. </li><li> If you have already set the preferred domain and we had added the non-preferred version to your account, we'll be removing that non-preferred version from your account over the next few days. </li></ul> Note that if you would like to see any information we have about the non-preferred version, you can always add it to your account.<br /><br />Here are some questions we've had about this preferred domain feature, and our replies.<br /><br /><span style="font-weight: bold;">Once I've set my preferred domain, how long will it take before I see changes?</span><br />The time frame depends on many factors (such as how often your site is crawled and how many pages are indexed with the non-preferred version). You should start to see changes in the few weeks after you set your preferred domain.<br /><br /><span style="font-weight: bold;">Is the preferred domain feature a filter or a redirect? Does it simply cause the search results to display on the URLs that are in the version I prefer?</span><br />The preferred domain feature is not a filter. When you set a preference, we:<br /><ul><li> Consider all links that point to the site (whether those links use the www version or the non-www version) to be pointing at the version you prefer. This helps us more accurately determine PageRank for your pages.</li><li>Once we know that both versions of a URL point to the same page, we try to select the preferred version for future crawls. </li><li> Index pages of your site using the version you prefer. If some pages of your site are indexed using the www version and other pages are indexed using the non-www version, then over time, you should see a shift to the preference you've set.<br /></li></ul> <span style="font-weight: bold;">If I use a 301 redirect on my site to point the www and non-www versions to the same version, do I still need to use this feature?</span><br />You don't have to use it, as we can follow the redirects. However, you still can benefit from using this feature in two ways: we can more easily consolidate links to your site and over time, we'll direct our crawl to the preferred version of your pages.<br /><br /><span style="font-weight: bold;">If I use this feature, should I still use a 301 redirect on my site?</span><br />You don't need to use it for Googlebot, but you should still use the 301 redirect, if it's available. This will help visitors and other search engines. Of course, make sure that you point to the same URL with the preferred domain feature and the 301 redirect.<br /><br />You can find more about this in our <a href="//www.google.com/support/webmasters" title="webmaster help center">webmaster help center.</a> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> <span style="font-weight: bold;"></span>Based on your input, we've recently made a few changes to the preferred domain feature of webmaster tools. And since you've had some questions about this feature, we'd like to answer them.<br /><span style="font-weight: bold;"></span><br />The <a href="//www.google.com/support/webmasters/bin/answer.py?answer=44231&topic=9025" title="preferred domain feature">preferred domain feature</a> enables you to tell us if you'd like URLs from your site crawled and indexed using the www version of the domain (http://www.example.com) or the non-www version of the domain (http://example.com). When we initially launched this, we added the non-preferred version to your account when you specified a preference so that you could see any information associated with the non-preferred version. But many of you found that confusing, so we've made the following changes:<br /><ul><li> When you set the preferred domain, we no longer will add the non-preferred version to your account. </li><li> If you had previously added the non-preferred version to your account, you'll still see it listed there, but you won't be able to add a Sitemap for the non-preferred version. </li><li> If you have already set the preferred domain and we had added the non-preferred version to your account, we'll be removing that non-preferred version from your account over the next few days. </li></ul> Note that if you would like to see any information we have about the non-preferred version, you can always add it to your account.<br /><br />Here are some questions we've had about this preferred domain feature, and our replies.<br /><br /><span style="font-weight: bold;">Once I've set my preferred domain, how long will it take before I see changes?</span><br />The time frame depends on many factors (such as how often your site is crawled and how many pages are indexed with the non-preferred version). You should start to see changes in the few weeks after you set your preferred domain.<br /><br /><span style="font-weight: bold;">Is the preferred domain feature a filter or a redirect? Does it simply cause the search results to display on the URLs that are in the version I prefer?</span><br />The preferred domain feature is not a filter. When you set a preference, we:<br /><ul><li> Consider all links that point to the site (whether those links use the www version or the non-www version) to be pointing at the version you prefer. This helps us more accurately determine PageRank for your pages.</li><li>Once we know that both versions of a URL point to the same page, we try to select the preferred version for future crawls. </li><li> Index pages of your site using the version you prefer. If some pages of your site are indexed using the www version and other pages are indexed using the non-www version, then over time, you should see a shift to the preference you've set.<br /></li></ul> <span style="font-weight: bold;">If I use a 301 redirect on my site to point the www and non-www versions to the same version, do I still need to use this feature?</span><br />You don't have to use it, as we can follow the redirects. However, you still can benefit from using this feature in two ways: we can more easily consolidate links to your site and over time, we'll direct our crawl to the preferred version of your pages.<br /><br /><span style="font-weight: bold;">If I use this feature, should I still use a 301 redirect on my site?</span><br />You don't need to use it for Googlebot, but you should still use the 301 redirect, if it's available. This will help visitors and other search engines. Of course, make sure that you point to the same URL with the preferred domain feature and the 301 redirect.<br /><br />You can find more about this in our <a href="//www.google.com/support/webmasters" title="webmaster help center">webmaster help center.</a> <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:Setting the preferred domain&url=https://webmasters.googleblog.com/2006/09/setting-preferred-domain.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/09/setting-preferred-domain.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/09/setting-preferred-domain.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en_US' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US' rel='tag'> webmaster tools </a> </span> </div> </div> </div> <div class='post' data-id='115765346882004536' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/09/information-about-sitelinks.html?hl=en_US' itemprop='url' title='Information about Sitelinks'> Information about Sitelinks </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, September 07, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> You may have noticed that some search results include a set of links below them to pages within the site. We've just updated our help center with <a href="//www.google.com/support/webmasters/bin/answer.py?answer=47334&topic=8523">information on how we generate these links</a>, called Sitelinks, and why we show them.<br /><br />Our process for generating Sitelinks is completely automated. We show them when we think they'll be most useful to searchers, saving them time from hunting through web pages to find the information they are looking for. Over time, we may look for ways to incorporate input from webmasters too. <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> You may have noticed that some search results include a set of links below them to pages within the site. We've just updated our help center with <a href="//www.google.com/support/webmasters/bin/answer.py?answer=47334&topic=8523">information on how we generate these links</a>, called Sitelinks, and why we show them.<br /><br />Our process for generating Sitelinks is completely automated. We show them when we think they'll be most useful to searchers, saving them time from hunting through web pages to find the information they are looking for. Over time, we may look for ways to incorporate input from webmasters too. <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:Information about Sitelinks&url=https://webmasters.googleblog.com/2006/09/information-about-sitelinks.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/09/information-about-sitelinks.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/09/information-about-sitelinks.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_US' rel='tag'> search results </a> </span> </div> </div> </div> <div class='post' data-id='115746739444207811' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/09/better-details-about-when-googlebot.html?hl=en_US' itemprop='url' title='Better details about when Googlebot last visited a page'> Better details about when Googlebot last visited a page </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Tuesday, September 05, 2006 </span> </div> </div> <div class='post-body'> <div class='post-content' itemprop='articleBody'> <script type='text/template'> Most people know that Googlebot downloads pages from web servers to crawl the web. Not as many people know that if Googlebot accesses a page and gets a <a href="//www.google.com/support/webmasters/bin/answer.py?answer=83040">304</a> (Not-Modified) response to a If-Modified-Since qualified request, Googlebot doesn't download the contents of that page. This reduces the bandwidth consumed on your web server.<br /><br />When you look at Google's cache of a page (for instance, by using the <a href="//www.google.com/intl/en/help/operators.html">cache: operator</a> or clicking the Cached link under a URL in the search results), you can see the date that Googlebot retrieved that page. Previously, the date we listed for the page's cache was the date that we last successfully fetched the content of the page. This meant that even if we visited a page very recently, the cache date might be quite a bit older if the page hadn't changed since the previous visit. This made it difficult for webmasters to use the cache date we display to determine Googlebot's most recent visit. Consider the following example:<br /><ol><li>Googlebot crawls a page on April 12, 2006.</li><li>Our cached version of that page notes that "This is G o o g l e's cache of http://www.example.com/ as retrieved on April 12, 2006 20:02:06 GMT."</li><li>Periodically, Googlebot checks to see if that page has changed, and each time, receives a Not-Modified response. For instance, on August 27, 2006, Googlebot checks the page, receives a Not-Modified response, and therefore, doesn't download the contents of the page.</li><li>On August 28, 2006, our cached version of the page still shows the April 12, 2006 date -- the date we last downloaded the page's contents, even though Googlebot last visited the day before.</li></ol>We've recently changed the date we show for the cached page to reflect when Googlebot last <span style="font-style: italic;">accessed </span>it (whether the page had changed or not). This should make it easier for you to determine the most recent date Googlebot visited the page. For instance, in the above example, the cached version of the page would now say "This is G o o g l e's cache of http://www.example.com/ as retrieved on August 27, 2006 13:13:37 GMT."<br /><br />Note that this change will be reflected for individual pages as we update those pages in our index. <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </script> <noscript> Most people know that Googlebot downloads pages from web servers to crawl the web. Not as many people know that if Googlebot accesses a page and gets a <a href="//www.google.com/support/webmasters/bin/answer.py?answer=83040">304</a> (Not-Modified) response to a If-Modified-Since qualified request, Googlebot doesn't download the contents of that page. This reduces the bandwidth consumed on your web server.<br /><br />When you look at Google's cache of a page (for instance, by using the <a href="//www.google.com/intl/en/help/operators.html">cache: operator</a> or clicking the Cached link under a URL in the search results), you can see the date that Googlebot retrieved that page. Previously, the date we listed for the page's cache was the date that we last successfully fetched the content of the page. This meant that even if we visited a page very recently, the cache date might be quite a bit older if the page hadn't changed since the previous visit. This made it difficult for webmasters to use the cache date we display to determine Googlebot's most recent visit. Consider the following example:<br /><ol><li>Googlebot crawls a page on April 12, 2006.</li><li>Our cached version of that page notes that "This is G o o g l e's cache of http://www.example.com/ as retrieved on April 12, 2006 20:02:06 GMT."</li><li>Periodically, Googlebot checks to see if that page has changed, and each time, receives a Not-Modified response. For instance, on August 27, 2006, Googlebot checks the page, receives a Not-Modified response, and therefore, doesn't download the contents of the page.</li><li>On August 28, 2006, our cached version of the page still shows the April 12, 2006 date -- the date we last downloaded the page's contents, even though Googlebot last visited the day before.</li></ol>We've recently changed the date we show for the cached page to reflect when Googlebot last <span style="font-style: italic;">accessed </span>it (whether the page had changed or not). This should make it easier for you to determine the most recent date Googlebot visited the page. For instance, in the above example, the cached version of the page would now say "This is G o o g l e's cache of http://www.example.com/ as retrieved on August 27, 2006 13:13:37 GMT."<br /><br />Note that this change will be reflected for individual pages as we update those pages in our index. <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 details about when Googlebot last visited a page&url=https://webmasters.googleblog.com/2006/09/better-details-about-when-googlebot.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/09/better-details-about-when-googlebot.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/09/better-details-about-when-googlebot.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en_US' rel='tag'> crawling and indexing </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en_US' rel='tag'> search results </a> </span> </div> </div> </div> <div class='post' data-id='115707016998615372' itemscope='' itemtype='http://schema.org/BlogPosting'> <h2 class='title' itemprop='name'> <a href='https://webmasters.googleblog.com/2006/08/how-search-results-may-differ-based-on.html?hl=en_US' itemprop='url' title='How search results may differ based on accented characters and interface languages'> How search results may differ based on accented characters and interface languages </a> </h2> <div class='post-header'> <div class='published'> <span class='publishdate' itemprop='datePublished'> Thursday, August 31, 2006 </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 a searcher enters a query that includes a word with accented characters, our algorithms consider web pages that contain versions of that word both with and without the accent. For instance, if a searcher enters [México], we'll return results for pages about both "Mexico" and "México."<br /> <br /> <a href="//photos1.blogger.com/blogger/3402/1340/1600/mexico_accent.gif" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/mexico_accent.png" style="cursor: pointer; display: block; margin: 0px auto 10px; text-align: center;"></a><br /> <br /> Conversely, if a searcher enters a query without using accented characters, but a word in that query could be spelled with them, our algorithms consider web pages with both the accented and non-accented versions of the word. So if a searcher enters [Mexico], we'll return results for pages about both "Mexico" and "México."<br /> <br /> <a href="//photos1.blogger.com/blogger/3402/1340/1600/mexico_noaccent.gif" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/mexico_noaccent.png" style="cursor: pointer; display: block; margin: 0px auto 10px; text-align: center;"></a><br /> <br /> <span style="font-weight: bold;">How the searcher's interface language comes into play</span><br /> The searcher's interface language is taken into account during this process. For instance, the set of accented characters that are treated as equivalent to non-accented characters varies based on the searcher's interface language, as language-level rules for accenting differ.<br /> <br /> Also, documents in the chosen interface language tend to be considered more relevant. If a searcher's interface language is English, our algorithms assume that the queries are in English and that the searcher prefers English language documents returned.<br /> <br /> This means that the search results for the same query can vary depending on the language interface of the searcher. They can also vary depending on the location of the searcher (which is based on IP address) and if the searcher chooses to see results only from the specified language. If the searcher has personalized search enabled, that will also influence the search results.<br /> <br /> The example below illustrates the results returned when a searcher queries [Mexico] with the interface language set to Spanish.<br /> <br /> <a href="//photos1.blogger.com/blogger/3402/1340/1600/spanish_noaccent.gif" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/spanish_noaccent.png" style="cursor: pointer; display: block; margin: 0px auto 10px; text-align: center;"></a><br /> <br /> Note that when the interface language is set to Spanish, more results with accented characters are returned, even though the query didn't include the accented character.<br /> <span style="font-weight: bold;"></span><span style="font-weight: bold;"></span><span style="font-weight: bold;"></span><br /> <span style="font-weight: bold;">How to restrict search results</span><br /> To obtain search results for only a specific version of the word (with or without accented characters), you can place a <span style="font-weight: bold;">+</span> <span style="background-color: #ffff33;"></span>before the word. For instance, the search [+Mexico] returns only pages about "Mexico" (and not "México"). The search [+México] returns only pages about "México" and not "Mexico." Note that you may see some search results that don't appear to use the version of word you specified in your query, but that version of the word may appear within the content of the page or in anchor text to the page, rather than in the title or description listed in the results. (You can see the top anchor text used to link to your site by choosing <span style="font-weight: bold;">Statistics </span>> <span style="font-weight: bold;">Page analysis</span> in <a href="//www.google.com/webmasters/sitemaps" title="webmaster tools">webmaster tools</a>.)<br /> <br /> The example below illustrates the results returned when a searcher queries [+Mexico].<br /> <br /> <a href="//photos1.blogger.com/blogger/3402/1340/1600/noaccentplus.gif" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/noaccentplus.png" style="cursor: pointer; display: block; margin: 0px auto 10px; text-align: center;"></a></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 a searcher enters a query that includes a word with accented characters, our algorithms consider web pages that contain versions of that word both with and without the accent. For instance, if a searcher enters [México], we'll return results for pages about both "Mexico" and "México."<br /> <br /> <a href="//photos1.blogger.com/blogger/3402/1340/1600/mexico_accent.gif" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/mexico_accent.png" style="cursor: pointer; display: block; margin: 0px auto 10px; text-align: center;"></a><br /> <br /> Conversely, if a searcher enters a query without using accented characters, but a word in that query could be spelled with them, our algorithms consider web pages with both the accented and non-accented versions of the word. So if a searcher enters [Mexico], we'll return results for pages about both "Mexico" and "México."<br /> <br /> <a href="//photos1.blogger.com/blogger/3402/1340/1600/mexico_noaccent.gif" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/mexico_noaccent.png" style="cursor: pointer; display: block; margin: 0px auto 10px; text-align: center;"></a><br /> <br /> <span style="font-weight: bold;">How the searcher's interface language comes into play</span><br /> The searcher's interface language is taken into account during this process. For instance, the set of accented characters that are treated as equivalent to non-accented characters varies based on the searcher's interface language, as language-level rules for accenting differ.<br /> <br /> Also, documents in the chosen interface language tend to be considered more relevant. If a searcher's interface language is English, our algorithms assume that the queries are in English and that the searcher prefers English language documents returned.<br /> <br /> This means that the search results for the same query can vary depending on the language interface of the searcher. They can also vary depending on the location of the searcher (which is based on IP address) and if the searcher chooses to see results only from the specified language. If the searcher has personalized search enabled, that will also influence the search results.<br /> <br /> The example below illustrates the results returned when a searcher queries [Mexico] with the interface language set to Spanish.<br /> <br /> <a href="//photos1.blogger.com/blogger/3402/1340/1600/spanish_noaccent.gif" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/spanish_noaccent.png" style="cursor: pointer; display: block; margin: 0px auto 10px; text-align: center;"></a><br /> <br /> Note that when the interface language is set to Spanish, more results with accented characters are returned, even though the query didn't include the accented character.<br /> <span style="font-weight: bold;"></span><span style="font-weight: bold;"></span><span style="font-weight: bold;"></span><br /> <span style="font-weight: bold;">How to restrict search results</span><br /> To obtain search results for only a specific version of the word (with or without accented characters), you can place a <span style="font-weight: bold;">+</span> <span style="background-color: #ffff33;"></span>before the word. For instance, the search [+Mexico] returns only pages about "Mexico" (and not "México"). The search [+México] returns only pages about "México" and not "Mexico." Note that you may see some search results that don't appear to use the version of word you specified in your query, but that version of the word may appear within the content of the page or in anchor text to the page, rather than in the title or description listed in the results. (You can see the top anchor text used to link to your site by choosing <span style="font-weight: bold;">Statistics </span>> <span style="font-weight: bold;">Page analysis</span> in <a href="//www.google.com/webmasters/sitemaps" title="webmaster tools">webmaster tools</a>.)<br /> <br /> The example below illustrates the results returned when a searcher queries [+Mexico].<br /> <br /> <a href="//photos1.blogger.com/blogger/3402/1340/1600/noaccentplus.gif" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" src="//photos1.blogger.com/blogger/3402/1340/400/noaccentplus.png" style="cursor: pointer; display: block; margin: 0px auto 10px; text-align: center;"></a></div> <span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://plus.google.com/116899029375914044550' itemprop='url'/> </span> </noscript> </div> </div> <div class='share'> <span class='twitter-custom social-wrapper' data-href='http://twitter.com/share?text=Official Google Webmaster Central Blog:How search results may differ based on accented characters and interface languages&url=https://webmasters.googleblog.com/2006/08/how-search-results-may-differ-based-on.html?hl=en_US&via=googlewmc'> <img alt='Share on Twitter' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png' width='24'/> </span> <span class='fb-custom social-wrapper' data-href='https://www.facebook.com/sharer.php?u=https://webmasters.googleblog.com/2006/08/how-search-results-may-differ-based-on.html?hl=en_US'> <img alt='Share on Facebook' height='24' src='https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png' width='24'/> </span> </div> <div class='post-footer'> <div class='cmt_iframe_holder' data-href='https://webmasters.googleblog.com/2006/08/how-search-results-may-differ-based-on.html' data-viewtype='FILTERED_POSTMOD'></div> <a href='https://plus.google.com/112374322230920073195' rel='author' style='display:none;'> Google </a> <div class='label-footer'> <span class='labels-caption'> Labels: </span> <span class='labels'> <a class='label' href='https://webmasters.googleblog.com/search/label/localization?hl=en_US' rel='tag'> localization </a> , <a class='label' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en_US' rel='tag'> search results </a> </span> </div> </div> </div> <div class='blog-pager' id='blog-pager'> <a class='home-link' href='https://webmasters.googleblog.com/?hl=en_US'> <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=2007-02-20T12:18:00-08:00&max-results=7&reverse-paginate=true&hl=en_US' 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=2006-08-31T17:22:00-07:00&max-results=7&hl=en_US' id='Blog1_blog-pager-older-link' title='Older Posts'> <i class='material-icons'>  </i> </a> </span> </div> <div class='clear'></div> </div></div> </div> </div> <div class='col-right'> <div class='section' id='sidebar-top'><div class='widget HTML' data-version='1' id='HTML9'> <div class='widget-content'> <a href="https://www.google.com/webmasters/tools/mobile-friendly/?utm_source=wmc-blog&utm_medium=referral&utm_campaign=blog-nav"><img src="https://lh3.googleusercontent.com/-osGJupx0-HY/VQta1nmaAPI/AAAAAAAACfs/UdMPzubsXFk/w80-h1368-no/blog%2Bpromo.png" align="left" width="80" /></a> Hey! <a href="https://search.google.com/test/mobile-friendly">Check here if your site is mobile-friendly.</a> </div> <div class='clear'></div> </div><div class='widget HTML' data-version='1' id='HTML10'> <div class='widget-content'> <div class='searchBox'> <input type='text' title='Search This Blog' placeholder='Search blog ...' /> </div> </div> <div class='clear'></div> </div></div> <div id='aside'> <div class='section' id='sidebar'><div class='widget Label' data-version='1' id='Label1'> <div class='tab'> <img class='sidebar-icon' src='data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAYpJREFUeNrs2aFuwzAQBmAvKRkMKRjZA4QMDJaWFgyMjuzFRg37DIUlA3uFkoGQSaWzJU+tpri5O9+l/zSfdFJlpe59yTmyVedq1PjfcZMZ70NuQnaF8w8htyE/rABtpviXkLcK88c5HhLkMBfgVan43zfFBNGMjHVGT/s55KP2pAvidbGHd+nzKt1RKSLG3rKF1iPFv6UWiPke8i7kEqGdGsI1O+LYVdqJAjgirwkKYD0ytkJBUNbAMvX8V3q9PhUsYvU1sWD8SO/sQvx2ahxOiNoJCSBCoAHYCEQAC4EKICOQASQEOmAS8RcAFxFN5hiIiugpgC3wk9hQAHH/70EBHXUN7IER5EWMiBgo2+nzOKQv9SCAeEM/OQAkhE/ncccFICB87qzQMia5FsJfOui0zMnmRvipU1ormHQuxGTxUsAcCFLxJQBLBLn4UoAFglW8BkATwS5eC6CBEBWvCShBiIvXBkgQRcVbADiI4uKtABSESvGWgB9EzHt3+tNwyO0qa9SoIYtvAQYAqDJhaWWeMecAAAAASUVORK5CYII='/> <h2> Labels </h2> <i class='material-icons arrow'>  </i> </div> <div class='widget-content list-label-widget-content'> <ul> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/accessibility?hl=en_US'> accessibility </a> <span dir='ltr'> 10 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/advanced?hl=en_US'> advanced </a> <span dir='ltr'> 195 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/AMP?hl=en_US'> AMP </a> <span dir='ltr'> 13 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Android?hl=en_US'> Android </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/API?hl=en_US'> API </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/apps?hl=en_US'> apps </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/autocomplete?hl=en_US'> autocomplete </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/beginner?hl=en_US'> beginner </a> <span dir='ltr'> 173 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/CAPTCHA?hl=en_US'> CAPTCHA </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Chrome?hl=en_US'> Chrome </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/cms?hl=en_US'> cms </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/crawling%20and%20indexing?hl=en_US'> crawling and indexing </a> <span dir='ltr'> 158 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/encryption?hl=en_US'> encryption </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/events?hl=en_US'> events </a> <span dir='ltr'> 51 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/feedback%20and%20communication?hl=en_US'> feedback and communication </a> <span dir='ltr'> 83 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/forums?hl=en_US'> forums </a> <span dir='ltr'> 5 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/general%20tips?hl=en_US'> general tips </a> <span dir='ltr'> 90 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/geotargeting?hl=en_US'> geotargeting </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20Assistant?hl=en_US'> Google Assistant </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20I%2FO?hl=en_US'> Google I/O </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20Images?hl=en_US'> Google Images </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Google%20News?hl=en_US'> Google News </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hacked%20sites?hl=en_US'> hacked sites </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hangout?hl=en_US'> hangout </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/hreflang?hl=en_US'> hreflang </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/https?hl=en_US'> https </a> <span dir='ltr'> 5 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/images?hl=en_US'> images </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/intermediate?hl=en_US'> intermediate </a> <span dir='ltr'> 205 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/interstitials?hl=en_US'> interstitials </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/javascript?hl=en_US'> javascript </a> <span dir='ltr'> 8 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/job%20search?hl=en_US'> job search </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/localization?hl=en_US'> localization </a> <span dir='ltr'> 21 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/malware?hl=en_US'> malware </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/mobile?hl=en_US'> mobile </a> <span dir='ltr'> 63 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/mobile-friendly?hl=en_US'> mobile-friendly </a> <span dir='ltr'> 14 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/nohacked?hl=en_US'> nohacked </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/performance?hl=en_US'> performance </a> <span dir='ltr'> 17 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/product%20expert?hl=en_US'> product expert </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/product%20experts?hl=en_US'> product experts </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/products%20and%20services?hl=en_US'> products and services </a> <span dir='ltr'> 63 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/questions?hl=en_US'> questions </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/ranking?hl=en_US'> ranking </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/recipes?hl=en_US'> recipes </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rendering?hl=en_US'> rendering </a> <span dir='ltr'> 2 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/Responsive%20Web%20Design?hl=en_US'> Responsive Web Design </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rich%20cards?hl=en_US'> rich cards </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/rich%20results?hl=en_US'> rich results </a> <span dir='ltr'> 10 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20console?hl=en_US'> 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_US'> search for beginners </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20queries?hl=en_US'> search queries </a> <span dir='ltr'> 7 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/search%20results?hl=en_US'> search results </a> <span dir='ltr'> 140 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/security?hl=en_US'> security </a> <span dir='ltr'> 12 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/seo?hl=en_US'> seo </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/sitemaps?hl=en_US'> sitemaps </a> <span dir='ltr'> 46 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/speed?hl=en_US'> speed </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/structured%20data?hl=en_US'> structured data </a> <span dir='ltr'> 33 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/summit?hl=en_US'> summit </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/TLDs?hl=en_US'> TLDs </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/url%20removals?hl=en_US'> url removals </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/UX?hl=en_US'> UX </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/verification?hl=en_US'> verification </a> <span dir='ltr'> 8 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/video?hl=en_US'> video </a> <span dir='ltr'> 6 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20community?hl=en_US'> webmaster community </a> <span dir='ltr'> 24 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20forum?hl=en_US'> webmaster forum </a> <span dir='ltr'> 1 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20guidelines?hl=en_US'> webmaster guidelines </a> <span dir='ltr'> 57 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmaster%20tools?hl=en_US'> webmaster tools </a> <span dir='ltr'> 177 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/webmasters?hl=en_US'> webmasters </a> <span dir='ltr'> 3 </span> </li> <li> <a dir='ltr' href='https://webmasters.googleblog.com/search/label/youtube%20channel?hl=en_US'> youtube channel </a> <span dir='ltr'> 6 </span> </li> </ul> <div class='clear'></div> </div> </div><div class='widget BlogArchive' data-version='1' id='BlogArchive1'> <div class='tab'> <i class='material-icons icon'>  </i> <h2> Archive </h2> <i class='material-icons arrow'>  </i> </div> <div class='widget-content'> <div id='ArchiveList'> <div id='BlogArchive1_ArchiveList'> <ul class='hierarchy'> <li class='archivedate 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_US'> 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_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2020/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/?hl=en_US'> 2019 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2019/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/?hl=en_US'> 2018 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2018/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/?hl=en_US'> 2017 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2017/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/?hl=en_US'> 2016 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2016/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/?hl=en_US'> 2015 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2015/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/?hl=en_US'> 2014 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2014/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/?hl=en_US'> 2013 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2013/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/?hl=en_US'> 2012 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2012/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/?hl=en_US'> 2011 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2011/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/?hl=en_US'> 2010 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2010/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/?hl=en_US'> 2009 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2009/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/?hl=en_US'> 2008 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2008/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class='intervalToggle'> <span class='new-toggle' href='javascript:void(0)'> <i class='material-icons arrow'>  </i> </span> <a class='toggle' href='javascript:void(0)' style='display: none'> <span class='zippy'> <i class='material-icons'>  </i>   </span> </a> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/?hl=en_US'> 2007 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/07/?hl=en_US'> Jul </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/06/?hl=en_US'> Jun </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/05/?hl=en_US'> May </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/04/?hl=en_US'> Apr </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/03/?hl=en_US'> Mar </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/02/?hl=en_US'> Feb </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2007/01/?hl=en_US'> Jan </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate 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/2006/?hl=en_US'> 2006 </a> </div> <div class='items'> <ul class='hierarchy'> <li class='archivedate expanded'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/12/?hl=en_US'> Dec </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/11/?hl=en_US'> Nov </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/10/?hl=en_US'> Oct </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/09/?hl=en_US'> Sep </a> </div> <div class='items'> </div> </li> </ul> <ul class='hierarchy'> <li class='archivedate collapsed'> <div class=''> <a class='post-count-link' href='https://webmasters.googleblog.com/2006/08/?hl=en_US'> Aug </a> </div> <div class='items'> </div> </li> </ul> </div> </li> </ul> </div> </div> <div class='clear'></div> </div> </div><div class='widget HTML' data-version='1' id='HTML6'> <div class='widget-content'> <a href="https://googlewebmastercentral.blogspot.com/atom.xml"> <img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAihJREFUeNrsWa9Pw0AU7viRMDFRBAkzJDMIBIhJJhCzk7NILIqMv4AEhdz+BCY3OYssAlGBoAJREpZwAlHEBO8lr8nSvNeVbu1dyX3JlzTrXfa+u/e9d7c5joWFhYVO1Fa8PwH2gK6m+BRwAvSlAdsrgr8E1jUuMH73GTAEzrkBWymTewZlihhLmgDXIAFuHgGVQOUF7OSYM1p6PgTuA1vAZlUEvAnPdapcMY0VICECekQ0XRfYrqoHsAGNgXfAoMomRiFDEhOZkkL3S88hMaB2LwXp0bj+ps2edpToZpjfoIDQtBeU+xjoDzP2G/gCPKZ5f8WsCAFJoJgOCcFdWSTeL9YQMSvTA1h9BkI5jaiXhLpSCL/8mVZY0UpyJ9ZdOkniu1dmJ96BpzQu9w6s28gcOq9j6pwLdR8/36NK5CQKwJSMrb2MhhSglBpt4UjsrdsnNu0B3J0HCozbCc4TjyY2srEgos/4RQljCzNxl4ireQD8FOq+T+W0mTB2g7njhlR+Sy2jsXFvU658U8YTbeaGpdIu7mWkEAq5ZtIjIhFZdtfX7QHckSvB2B6zC3VdAkZk0kAQwaXTk/CzTXK3wjIExCs6ZJpTnE4uY1KV+KzFzA3KTiFPENHJkOPcsfpLhwe4btoSuvUqAR+6TOxlCE6ZfKUsJLgsqGW8OpqAGx2X+sLxrwUog+JUeQRMDBIwyXOcnlPtPnL0/UsT/8LnOxYWFhZG4leAAQAAQHEaYuzHbAAAAABJRU5ErkJggg==" class="sidebar-icon" /> <h2>Feed</h2> </a> </div> <div class='clear'></div> </div></div> <div class='section' id='sidebar-bottom'><div class='widget HTML' data-version='1' id='HTML5'> <div class='widget-content'> <div class='followgooglewrapper'> <script src="https://apis.google.com/js/plusone.js"></script></div> <div class="g-ytsubscribe class='followgooglewrapper'" data-channel="GoogleWebmasterHelp" data-layout="full"></div> <div class="share followgooglewrapper"> <button data-href="https://twitter.com/intent/follow?original_referer=https://googlewebmastercentral.blogspot.com/&screen_name=googlewmc" onclick='sharingPopup(this);' id='twitter-share'><span class="twitter-follow">Follow @googlewmc</span></button> <script> function sharingPopup (button) { var url = button.getAttribute("data-href"); window.open( url,'popUpWindow','height=500,width=500,left=10,top=10,resizable=yes,scrollbars=yes,toolbar=yes,menubar=no,location=no,directories=no,status=yes'); } </script> </div> </div> <div class='clear'></div> </div><div class='widget HTML' data-version='1' id='HTML1'> <div class='widget-content'> Give us feedback in our <a href="https://support.google.com/webmasters/go/community">Product Forums</a>. </div> <div class='clear'></div> </div><div class='widget HTML' data-version='1' id='HTML8'> <h2 class='title'> Subscribe via email </h2> <div class='widget-content'> <form #nsubmit="window.open('https://www.feedburner.com/fb/a/emailverifySubmit?feedId=1092589', 'popupwindow', 'scrollbars=yes,width=550,height=520');return true" action="https://www.feedburner.com/fb/a/emailverify" style="border:1px solid #ccc;padding:3px;text-align:center;" target="popupwindow" method="post"><p>Enter your email address:</p><p><input style="width:140px" name="email" type="text"/></p><input value="https://feeds.feedburner.com/~e?ffid=1092589" name="url" type="hidden"/><input value="Official Google Webmaster Central Blog" name="title" type="hidden"/><input value="en_US" name="loc" type="hidden"/><input value="Subscribe" type="submit"/><p>Delivered by <a href="https://www.feedburner.com" target="_blank">FeedBurner</a></p></form> </div> <div class='clear'></div> </div></div> </div> </div> <div style='clear:both;'></div> </div>  <div class='google-footer-outer loading'> <div id='google-footer'> <a href='//www.google.com/'> <img class='google-logo-dark' height='36' src='data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAALgAAABICAYAAABFoT/eAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAACLVJREFUeNrsXd+L20YQ3vOprdLqiMXFXE2qB7dcwEcTSB7ykIc+9A/PQx/yEMq1TWhNuYIpJriNr7XpmZ5IxFEvmW2EKs3Ornb1w50PxIFP0kiz387OzM6uhGAwGAxGP3Ho+f7x7ri1O7LdccPqZjSNA4dEHsLfaHcEFedJom93x9Xu2OyOFTcBo6sED3fHZHeMEELrkAHJF0B8Rr+gDFsZ5n0luLTQ95AXs4W06D/tjpR50xtM4CjD0y48YGB4rnyZxNOzyA7zBHr+nLnDaJLg0mo/ALekCasg3Z4XbM0ZdTEgnDPeHY8bIne+Qz2GvwyGNwsuyT218KWvIIBMcwGpLiipcolecjMxfBDchNyS1EvxLiOSIecp31q6IJ/C3yrIrMqMm4jhg+AxkdwbIO3aUO4KjqqMjCT3uaazMBhWBJfuxH3CtRfiXf66DhSRZWbmlMnNaILgZxrXJQO/eO3wORZwvwm4JUxuhheCjzVBYAbW1ces45YDSoZrFNOEE835M8FT6oyeEnws8Fz3QnBxFKPHBMem4GU+m6fPGb0leCTwWcM5B36MPgeZI01gudyDdw3hPeXfo8L/rmCUWnuMMdqUL2WqWeRbhf+twfVsO7YagZGNC79fw7OthEVtkiJ4jJzTd3KPwf3CRqhhiTu23AP5sl0/0xiwISQXpNwLIJK87mHF+U8ddzzdmgKlGzlPYjyxGJQouIhNT4k9AqWEFkqfguIvagTWbcq3KW1WE3xS3m8NtA9WS451xofwjKT5kkDoK/b6mDk5FfXr1lWDL4BofZEv2/SRsK/EHGlGdBdu8QNRb8HMCFwt7Yy3DDI/QP7fx5z3VLhdlJEIs4rKNuXXJXdxZPdB7kfCzWqwCO4V1LHgLjInX3tQ1KzCR52Cz+vDj1dydeRuS74rcvs2Pi6fT5H8OaaUQPQPYcWwRSGXyhhscn5dpAnEFMkuEZetbfkTAnlSuH4DxisE+aMGeJAQ3lFl7C4LJE6QWCaCd583ORQ1jYAwjFctal7nOs2ZZvicwvlZx+RHGrcoAwKUVX8uwcc/9TT65INeDOr5shL9LDRB6QTeIy3zwfdh3WOi6axLCEhSjXU7F3h6LqggUtvyJxpynwu8tDkD98fXApOxRj8zoZ9MnGveYVIVZKaGrkBXCY65BCYNN9NkjpKOyQ81Q79JgdxS+Jn3SDTEXRI7SWzaiSTB32oI3nU3BvMfM0urhOVYgwKhuiAfc4tM07wXwm1ZRoQYSl2NUwiu01fEAHVcpixd745FvVz4dzUUc0o8rwoLy8ZSwU6CyFx1RP5II9+1bFPEFs9HWbNLiimDXE+vCm7u1CS47cofzD3aEhVY57mxRo5zlqdt+RFC1JUH2S7bcVXg4liTMakaBZZVxiTICRoivcn1sEUBlk24JmaC6kxUbYmWoqvyfck2xZGGnDFYa9MMzkYQ1ijkCX6qidybrgePiQ0QIQqoi6qRLeqQfIoRsEHaQJLBdHOnLGetSdm/IPcymJuS1PAnbQPH0MOw/39C1vL11DiLOqIsbDI8QcHvGiLnySi2qUXBicaqUSxN5LEB0g7Jt3ENXJLPJ5S1tnaZBoWbpRqrmjRE7qHmpSmNHdQcYrEUadoh+TbBnc9ri7iycI1kzPeNcLDIvbiqXpez9Tmdq6zGREPuzECBoxrPMiI2WtvyNwhJba2wy3JZ6ky5dD1lSvmZS3e4SPA1wcf1VTFHKX+cGwZzdUYcqpvUtvwrD/InDttVlyZeAKlNN5MKbAiurHhKIPlUuJvlTCCiDjSKSCsUmCFWbGLZwCESfK07JB8LvMYWVtw0D00JEHV8Mq2HkqPbE0oHLvvK2g0o8ETg+4cfwTlZDT9JDoWygu4uQQE/ivIvtcnfPkaCqhiupz7jWOAzqL/vjtcdkv9G4MVMt+EaylfuImiPAXEUjRF3pjjaHiPPZ6If9TGGAO4ZY0am6jOCb+DQ+ZCqLkIpOIPrdNfIjnFPY6nyFut7TS/fanrziOBOKMupKw94WaLMtuVnSFt9CPrWWdJE6PeltCX432DEBoh+5Dv8RRhdis8YAv9uyq4/JAwtlEApgBe9Cw9xDD3tdk4Jn0MDfiHwPHcRPxBePCMER3GuIx7kGlv9fkZ4V9lolx2Uv4X7hEj7qJ3LDoAMGbTRMRibu4L2xQ8bgt8AyU+Q+x7nYrvDnH4iuO5LxKsYwPVbkPMvKF9Zky9wXzRfVWizi62r9X5VHf55h+WHhDjGBZ4WRhyTr6z5SlCoLMxLSpBZFsQ9F80uQFbF/6aFWi+Ev51vzzsuX+msyzuQXXjUz8zEBy+zpq9yweXAoxJW4JbYrDS6gYDqGHxPl+TKeiBfxj9/EBIElPYeOA4y8/qRQfknjvSzgRgtq0Pw/M1eQeMdOSb2Bnrhr6Led+1vcp2x7oTFHMnedFW+Ivlty062BUt74oHgSj+vHepnhunn0JJAMtBZgDI/qmGtMujRv8DDpo47zBJ8UtPOuAR/7rKn8t9AJ0tBdmBAmJ/Fu71yxp4I3qh+DhyRqbi5Y1ShVPlSb8X7bRNcfgZFl+WRGYo7uecrWq1r8X5bhmzP5OdlDwsGRm1suSxkg5rYm7ConyGQ3Zl+DgSD8V/kPwrWBMG9YcBtyShBnTLdTiHgttw7qAW7cqh/ZnmPKr/6ignOaKsdyxbsToT5UkPsW00bJjijDXficcX/JsLs6w2BwGtherdckH3w/kNXRPVI0OqJQoHX42/66IMfMj/2huRjxIidgKV/W0JS+bsstDoTeAHcrI8E5zTh/sDkqxL5rZup55/3USlswfcHf4IrQplVDgW9XFlOqnwr6pVPMMEZTuC60EttvdzbLbaZ4PsFVa3nohhO+vW+yn/ZB2fUhpysmQrzBcTSai9EszuZMcEZ1lCFVrp9zGXhm69iLyY4oxFIa178lPe12I/P2DAYDAaDwWAwGAwGg8FgMBgMBoPBYDD2Cf8IMADDRGoQTe+E9AAAAABJRU5ErkJggg==' style='margin-top: -16px;' width='92'/> </a> <ul> <li> <a href='//www.google.com/'> Google </a> </li> <li> <a href='//www.google.com/policies/privacy/'> Privacy </a> </li> <li> <a href='//www.google.com/policies/terms/'> Terms </a> </li> </ul> </div> </div> <script type='text/javascript'> //<![CDATA[ // Social sharing popups. var postEl = document.getElementsByClassName('social-wrapper'); var postCount = postEl.length; for(i=0; i<postCount;i++){ postEl[i].addEventListener("click", function(event){ var postUrl = this.getAttribute("data-href"); window.open( postUrl,'popUpWindow','height=500,width=500,left=10,top=10,resizable=yes,scrollbars=yes,toolbar=yes,menubar=no,location=no,directories=no,status=yes'); });} //]]> </script> <script type='text/javascript'> //<![CDATA[ var BreakpointHandler = function() { this.initted = false; this.isHomePage = false; this.isMobile = false; }; BreakpointHandler.prototype.finalizeSummary = function(summaryHtml, lastNode) { // Use $.trim for IE8 compatibility summaryHtml = $.trim(summaryHtml).replace(/(<br>|\s)+$/,''); if (lastNode.nodeType == 3) { var lastChar = summaryHtml.slice(-1); if (!lastChar.match(/[.”"?]/)) { if (!lastChar.match(/[A-Za-z]/)) { summaryHtml = summaryHtml.slice(0, -1); } summaryHtml += ' ...'; } } else if (lastNode.nodeType == 1 && (lastNode.nodeName == 'I' || lastNode.nodeName == 'A')) { summaryHtml += ' ...'; } return summaryHtml; }; BreakpointHandler.prototype.generateSummaryFromContent = function(content, numWords) { var seenWords = 0; var summaryHtml = ''; for (var i=0; i < content.childNodes.length; i++) { var node = content.childNodes[i]; var nodeText; if (node.nodeType == 1) { if (node.hasAttribute('data-about-pullquote')) { continue; } nodeText = node.textContent; if (nodeText === undefined) { // innerText for IE8 nodeText = node.innerText; } if (node.nodeName == 'DIV' || node.nodeName == 'B') { // Don't end early if we haven't seen enough words. if (seenWords < 10) { continue; } if (i > 0) { summaryHtml = this.finalizeSummary(summaryHtml, content.childNodes[i-1]); } break; } summaryHtml += node.outerHTML; } else if (node.nodeType == 3) { nodeText = node.nodeValue; summaryHtml += nodeText + ' '; } var words = nodeText.match(/\S+\s*/g); if (!words) { continue; } var remain = numWords - seenWords; if (words.length >= remain) { summaryHtml = this.finalizeSummary(summaryHtml, node); break; } seenWords += words.length; } return summaryHtml; }; BreakpointHandler.prototype.detect = function() { var match, pl = /\+/g, search = /([^&=]+)=?([^&]*)/g, decode = function (s) { return decodeURIComponent(s.replace(pl, " ")); }, query = window.location.search.substring(1); var urlParams = {}; while (match = search.exec(query)) urlParams[decode(match[1])] = decode(match[2]); this.isListPage = $('html').hasClass('list-page'); this.isMobile = urlParams['m'] === '1'; this.isHomePage = window.location.pathname == '/'; }; BreakpointHandler.prototype.initContent = function() { var self = this; $('.post').each(function(index) { var body = $(this).children('.post-body')[0]; var content = $(body).children('.post-content')[0]; $(content).addClass('post-original'); var data = $(content).children('script').html(); data = self.rewriteForSSL(data); // If exists, extract specified editor's preview. var match = data.match(/([\s\S]+?)<div data-is-preview.+?>([\s\S]+)<\/div>/m); if (match) { data = match[1]; } // Prevent big images from loading when they aren't needed. // This must be done as a pre-injection step, since image loading can't be // canceled once embedded into the DOM. if (self.isListPage && self.isMobile) { data = data.replace(/<(img|iframe) .+?>/g, ''); } // Insert template to be rendered as nodes. content.innerHTML = data; if (self.isListPage) { var summary = document.createElement('div'); $(summary).addClass('post-content'); $(summary).addClass('post-summary'); body.insertBefore(summary, content); if (match) { // Use provided summary. summary.innerHTML = match[2]; } else { // Generate a summary. // Summary generation relies on DOM, so it must occur after content is // inserted into the page. summary.innerHTML = self.generateSummaryFromContent(content, 30); } // Add read more link to summary. var titleAnchor = $(this).find('.title a')[0]; var link = titleAnchor.cloneNode(true); link.innerHTML = 'Read More'; $(link).addClass('read-more'); summary.appendChild(link); } }); // Firefox does not allow for proper styling of BR. if (navigator.userAgent.indexOf('Firefox') > -1) { $('.post-content br').replaceWith('<span class="space"></span>'); } $('.loading').removeClass('loading'); }; BreakpointHandler.prototype.process = function() { if (!this.initted) { var makeInsecureImageRegex = function(hosts) { var whitelist = hosts.join('|').replace(/\./g,'\\.'); // Normal image tags, plus input images (yes, this is possible!) return new RegExp('(<(img|input)[^>]+?src=("|\'))http:\/\/(' + whitelist +')', 'g'); }; this.sslImageRegex = makeInsecureImageRegex(BreakpointHandler.KNOWN_HTTPS_HOSTS); this.sslImageCurrentDomainRegex = makeInsecureImageRegex([window.location.hostname]); this.detect(); this.initContent(); this.initted = true; } }; BreakpointHandler.KNOWN_HTTPS_HOSTS = [ "www.google.org", "www.google.com", "services.google.com", "blogger.com", "draft.blogger.com", "www.blogger.com", "photos1.blogger.com", "photos2.blogger.com", "photos3.blogger.com", "blogblog.com", "img1.blogblog.com", "img2.blogblog.com", "www.blogblog.com", "www1.blogblog.com", "www2.blogblog.com", "0.bp.blogspot.com", "1.bp.blogspot.com", "2.bp.blogspot.com", "3.bp.blogspot.com", "4.bp.blogspot.com", "lh3.googleusercontent.com", "lh4.googleusercontent.com", "lh5.googleusercontent.com", "lh6.googleusercontent.com", "themes.googleusercontent.com", ]; BreakpointHandler.prototype.rewriteForSSL = function(html) { // Handle HTTP -> HTTPS source replacement of images, movies, and other embedded content. return html.replace(this.sslImageRegex, '$1https://$4') .replace(this.sslImageCurrentDomainRegex, '$1//$4') .replace(/(<(embed|iframe)[^>]+?src=("|'))http:\/\/([^"']*?(youtube|picasaweb\.google)\.com)/g, '$1https://$4') // Slideshow SWF takes a image host, so we need to rewrite that parameter. .replace(/(<embed[^>]+?feed=http(?=[^s]))/g, '$1s'); }; $(document).ready(function() { var handler = new BreakpointHandler(); handler.process(); // Top-level navigation. $(".BlogArchive .tab").click(function(ev) { ev.preventDefault(); $(this).parent().toggleClass('active'); $(this).siblings().slideToggle(300); }); $(".Label .tab").click(function(ev) { ev.preventDefault(); $(this).parent().toggleClass('active'); $(this).siblings().slideToggle(300); }); // Blog archive year expansion. $('.BlogArchive .intervalToggle').click(function(ev) { ev.preventDefault(); if ($(this).parent().hasClass('collapsed')) { $(this).parent().removeClass('collapsed'); $(this).parent().addClass('expanded'); } else { $(this).parent().removeClass('expanded'); $(this).parent().addClass('collapsed'); } }); // Reverse order of months. $('.BlogArchive .intervalToggle + div').each(function(_, items) { var year = $(this); year.children().each(function(_, month) { year.prepend(month); }); }); // Set anchors to open in new tab. $('.post-content img').parent().each(function(_, node) { if (node.nodeName == 'A') { $(this).attr('target', '_blank'); } }); // Process search requests. $('.searchBox input').on("keypress", function(ev) { if (ev.which == 13) { window.location.href = 'https://www.google.com/search?q=site%3A' + window.location.hostname + '%20' + encodeURIComponent ($(this).val()); } }); }); //]]> </script> <script type="text/javascript" src="https://www.blogger.com/static/v1/widgets/984859869-widgets.js"></script> <script type='text/javascript'> window['__wavt'] = 'AOuZoY76-n62473YXLvXd8u46OkFltTPbA:1732419328832';_WidgetManager._Init('//www.blogger.com/rearrange?blogID\x3d32069983','//webmasters.googleblog.com/2006/?hl\x3den_US','32069983'); _WidgetManager._SetDataContext([{'name': 'blog', 'data': {'blogId': '32069983', 'title': 'Official Google Webmaster Central Blog', 'url': 'https://webmasters.googleblog.com/2006/?hl\x3den_US', 'canonicalUrl': 'https://webmasters.googleblog.com/2006/', 'homepageUrl': 'https://webmasters.googleblog.com/?hl\x3den_US', 'searchUrl': 'https://webmasters.googleblog.com/search', 'canonicalHomepageUrl': 'https://webmasters.googleblog.com/', 'blogspotFaviconUrl': 'https://webmasters.googleblog.com/favicon.ico', 'bloggerUrl': 'https://www.blogger.com', 'hasCustomDomain': true, 'httpsEnabled': true, 'enabledCommentProfileImages': false, 'gPlusViewType': 'FILTERED_POSTMOD', 'adultContent': false, 'analyticsAccountNumber': 'UA-18009-4', 'encoding': 'UTF-8', 'locale': 'en-US', 'localeUnderscoreDelimited': 'en', 'languageDirection': 'ltr', 'isPrivate': false, 'isMobile': false, 'isMobileRequest': false, 'mobileClass': '', 'isPrivateBlog': false, 'isDynamicViewsAvailable': true, 'feedLinks': '\x3clink rel\x3d\x22alternate\x22 type\x3d\x22application/atom+xml\x22 title\x3d\x22Official Google Webmaster Central Blog - Atom\x22 href\x3d\x22https://webmasters.googleblog.com/feeds/posts/default\x22 /\x3e\n\x3clink rel\x3d\x22alternate\x22 type\x3d\x22application/rss+xml\x22 title\x3d\x22Official Google Webmaster Central Blog - RSS\x22 href\x3d\x22https://webmasters.googleblog.com/feeds/posts/default?alt\x3drss\x22 /\x3e\n\x3clink rel\x3d\x22service.post\x22 type\x3d\x22application/atom+xml\x22 title\x3d\x22Official Google Webmaster Central Blog - Atom\x22 href\x3d\x22https://www.blogger.com/feeds/32069983/posts/default\x22 /\x3e\n', 'meTag': '', 'adsenseHostId': 'ca-host-pub-1556223355139109', 'adsenseHasAds': false, 'adsenseAutoAds': false, 'boqCommentIframeForm': true, 'loginRedirectParam': '', 'view': '', 'dynamicViewsCommentsSrc': '//www.blogblog.com/dynamicviews/4224c15c4e7c9321/js/comments.js', 'dynamicViewsScriptSrc': '//www.blogblog.com/dynamicviews/d78375fb222d99b3', 'plusOneApiSrc': 'https://apis.google.com/js/platform.js', 'disableGComments': true, 'interstitialAccepted': false, 'sharing': {'platforms': [{'name': 'Get link', 'key': 'link', 'shareMessage': 'Get link', 'target': ''}, {'name': 'Facebook', 'key': 'facebook', 'shareMessage': 'Share to Facebook', 'target': 'facebook'}, {'name': 'BlogThis!', 'key': 'blogThis', 'shareMessage': 'BlogThis!', 'target': 'blog'}, {'name': 'X', 'key': 'twitter', 'shareMessage': 'Share to X', 'target': 'twitter'}, {'name': 'Pinterest', 'key': 'pinterest', 'shareMessage': 'Share to Pinterest', 'target': 'pinterest'}, {'name': 'Email', 'key': 'email', 'shareMessage': 'Email', 'target': 'email'}], 'disableGooglePlus': true, 'googlePlusShareButtonWidth': 0, 'googlePlusBootstrap': '\x3cscript type\x3d\x22text/javascript\x22\x3ewindow.___gcfg \x3d {\x27lang\x27: \x27en\x27};\x3c/script\x3e'}, 'hasCustomJumpLinkMessage': false, 'jumpLinkMessage': 'Read more', 'pageType': 'archive', 'pageName': '2006', 'pageTitle': 'Official Google Webmaster Central Blog: 2006', '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/2006/?hl\x3den_US', 'type': 'feed', 'isSingleItem': false, 'isMultipleItems': true, 'isError': false, 'isPage': false, 'isPost': false, 'isHomepage': false, 'isArchive': true, 'isLabelSearch': false, 'archive': {'year': 2006, 'rangeMessage': 'Showing posts from 2006'}}}]); _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>