May 19, 2006<\/p>\n
\n We’d like to give you all a quick update on some of the issues you have been seeing when you do a \n We’ve got fixes for all of these rolling out in the next few days. They didn’t come out sooner \n This bug doesn’t involve any pages being dropped from the index. It’s the \n In the meantime, site: queries without the trailing slash may provide a better result (such as Thanks for your patience as we resolve this issue.<\/p>\n
\n site:<\/code> search to see how many pages of your site are in the index. We’ve been
\n refreshing our supplemental results (you can read more about that in
\n Matt Cutts’
\n blog post<\/a>) and this refresh has involved some serious changes under the hood. Unfortunately,
\n with change of this scale, there sometimes are bugs. In this case, we found a few bugs that
\n affected the site: operator. Some particular ones you may have noticed are that the following
\n types of queries don’t return the correct number of results:\n<\/p>\n\n
site:<\/code> queries where you type in a trailing slash
\n (such as site:www.example.com\/<\/code>)\n <\/li>\nsite:<\/code> queries for a domain with punctuation (such as
\n site: www.example-site.com<\/code>)\n <\/li>\n<\/ul>\n
\n because we’ve been testing them thoroughly, making sure you don’t get any unexpected surprises.\n<\/p>\nsite:<\/code>
\n operator that isn’t working properly. We’re freezing all refreshes of the supplemental results
\n until these issues are fixed, and things should be back to normal in a few days. We’ll keep you
\n posted when all fixes have been made.\n<\/p>\n
\n site:www.example.com<\/code>). If you are checking your site using the Index Stats page of
\n Google Sitemaps, note that it uses the trailing slash in the query, so you may see incorrect
\n results until this bug is fixed.\n<\/p>\n