4

I have read in many places that one should use Google Webmaster preferably to the site: search operator. However, I would like to know where the site: operator gets its information from?

Here is my situation. I have imported a new blog on Blogger and tried to have the pages added to the index. The problem is that Google Webmaster's index status is updated once per week —too slow for me. Right now, it says no pages have been added to the index yet.

But, when I search site:trovare-parole.blogspot.com, it returns plenty of links.

So does it mean Google has indexed some of my pages yet (and the index status is late) or not? How should I interpret the result of a site search?

2 Answers 2

3

I have read in many places that one should use Google Webmaster preferably to the site: command. [] I would like to know where the google site command takes its information from?

The information comes from the same place: their search index.

The problem is that Google Webmaster's index status is updated once per week -> Too slow for me. Right now, it says no pages have been added to the index yet. But, when I use the site:trovare-parole.blogspot.com command, it returns plenty of links.

If the Webmasters information is only updated once a week and these two events happened within a week of each other, then they don't necessarily say anything about each other.

The fact your site: search does return information tells you (at least some) pages have been indexed. But if you want to know exactly how many that is, you'll have to wait until your Webmaster Tools information gets updated. Using site: through the regular search interface explicitly does not return all indexed documents.

2

The site: command will return all pages Google knows about for the domain provided (example.com) plus subdomains, or for match to the subdomain provided (www.example.com).

Google returns all the pages it has scanned, including duplicate content.

Once scanned, Google has to process all the information and actually index it. So Google's index status is not too slow for you, you just haven't waited long enough for the data processing to occur.

It's a good sign stuff shows for site:, you just have to be patient while Google to does its job to determine whether your pages are relevant, where they are relevant and their ranking in consideration with incoming authoritative links.

5
  • 1
    site: does not return all pages.
    – Su'
    Commented Dec 25, 2012 at 10:42
  • The above information came from their blog. What pages aren't included? Commented Dec 25, 2012 at 22:16
  • Can you provide a link to whatever it is you're citing? I recall seeing a video(which I'm having trouble hunting down, of course) with Matt Cutts explicitly stating the site operator doesn't return all pages, one reason being that competing sites could use it to figure out how to undermine each other. (Also, for what it's worth, I just compared results for two of my own sites, and the numbers are drastically different.) At any rate, the supported/proper way to find out how many pages a domain you own has indexed is to go through Webmaster Tools, delay or not.
    – Su'
    Commented Dec 26, 2012 at 10:29
  • It's not the one I mentioned above, but as a start in this video(which started as a question about site:) Cutts basically says not to entirely trust the public search count numbers as representing precise values. And here's an older one saying the same more directly.
    – Su'
    Commented Dec 26, 2012 at 10:39
  • "It's a good sign stuff shows for site:, you just have to be patient while Google to does its job to determine whether your pages are relevant" -> No, the site: command takes information from the index itself, so we are past that point of evalutation! Commented Feb 14, 2013 at 15:24

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.