6 ms·

I'm pretty sure Chrome send URLs to Google at least for indexing purposes. I've put up random pages on my websites, not linked to them anywhere at all but visit

I'm pretty sure Chrome send URLs to Google at least for indexing purposes. I've put up random pages on my websites, not linked to them anywhere at all but visited them in Chrome and then BAM - indexed soon after in search.

beaumartinez 15y ago
IIRC, it has components of Google Toolbar built in. If you accessed those pages with a browser with the Google Toolbar you'd have experienced the same.
- philfreo 15y ago
  I'm hoping you're offering that as an FYI, rather than as a justification... because it's not a very good justification
- aboodman 15y ago
  You recall incorrectly. Chrome does not send the URLs of pages you visit to Google for indexing, or for any other reason. Please see the privacy policy. It answers these questions quite clearly: http://www.google.com/intl/en/privacy/ http://www.google.com/intl/en/privacy/
  - WalterGR 15y ago
    http://www.google.com/chrome/intl/en/privacy.html http://www.google.com/chrome/intl/en/privacy.html ... > When you type URLs or queries in the address bar, the letters you type are sent to your default search engine so the Suggest feature can automatically recommend terms or URLs you may be looking for. If you choose Google as your search engine, Google Chrome will contact Google when it starts so as to determine the best local address to send search queries. If you choose to share usage statistics with Google and you accept a suggested query or URL, Google Chrome will send that information to Google as well. You can disable this feature as explained here. ... > If you navigate to a URL that does not exist, Google Chrome may send the URL to Google so we can help you find the URL you were looking for. You can disable this feature as explained here. ... > If you enable the optional AutoFill feature, which automatically completes web forms for you, Google Chrome will send Google limited information about the structure of pages that have web forms and information such as the arrangement of the form so that we can improve our AutoFill service for that page. (end excerpts) Could you give us more information about the AutoFill feature? Does it send the URL along with the listed information? Does it do this for every URL that contains a web form?
danmaz74 15y ago
What did you visit after hitting those pages? There is also "referer"...
- philfreo 15y ago
  nope... no outbound links
mikewest 15y ago
Chrome does not arbitrarily send URLs to Google. We go out of our way to avoid doing that, actually. Look at the implementation of SafeBrowsing, for instance, which does some clever work with hashes to ensure that Google never knows exactly what URL you visited that triggered the warning. It would have been _much_ simpler to just send the URLs, I assure you.
- rpearl 15y ago
  Chrome, or Chromium? One is open source, one really isn't. The set of things that Chrome does is certainly based on Chromium, but Google certainly has the freedom to add some very useful tracking behavior... if they want to. On one, we have source. On the other, we just have the quote "We go out of our way to avoid doing that, actually." What other evidence?
  - mikewest 15y ago
    Given that I'm responding to "I'm pretty sure Chrome send URLs to Google at least for indexing purposes." let's first agree that there's been no evidence provided that I can respond to. :) I mean both Chrome and Chromium. The source is there, we develop in the open, and I'm not sure what additional evidence I can provide to you to prove a negative. Wireshark?
    - philfreo 15y ago
      Well the source for Chrome is not open (edit: correction acknowledged - I thought only Chromium was open), though if you are a Chrome developer confidently saying this is impossible then I would give merit to that. My experiences were non-scientific but still gave me enough suspicious to right this. I may try a more rigorous/careful/documented experiment sometime in the future.
      - justinschuh 15y ago
        The source to Chrome is definitely open and you can compile an effectively identical version yourself (minus the branding). There are some closed source plugins (eg. PDF and Flash) that are shipped as dynamic libraries. However, you could disable them (via about:plugins) or simply delete the corresponding binaries from a Chrome distribution and everything remaining would be open source.
scott_s 15y ago
Try putting up new pages, only visit them in non-Chrome browsers, and see if they still get indexed. If they do, then it's not Chrome.
- zobzu 15y ago
  and dont forget to disable safe-browsing (which is pinging google) eg in Firefox "block known blah and bleh sites"
  - tonfa 15y ago
    Last time I checked, safe-browsing wasn't leaking url, hashes were sent around. Has this changed?
blauwbilgorgel 15y ago
When I had this happen, or when I heard this happen, there was always a reason that was far less sinister than initially thought. * Public referrer logs created a backlink * Somebody (else) published the URL * Somebody (else) shared the URL * You pinged the URL to search engines or other services. * The URL appeared in your RSS feed * The URL appeared in your sitemap * Your pages URL ranges are easily guessable (/item.php?id=1007, /item.php?id=1008) and traversed by a search engine. And more recently, something less innocuous: You simply added a Google +1 button to your pages. When you add the +1 button to a page, Google assumes that you want that page to be publicly available and visible in Google Search results. As a result, we may fetch and show that page even if it is disallowed in robots.txt. http://www.google.com/support/webmasters/bin/answer.py?answer=1140194&hl=en http://www.google.com/support/webmasters/bin/answer.py?answe...

beaumartinez 15y ago

IIRC, it has components of Google Toolbar built in. If you accessed those pages with a browser with the Google Toolbar you'd have experienced the same.

philfreo 15y ago
I'm hoping you're offering that as an FYI, rather than as a justification... because it's not a very good justification
aboodman 15y ago
You recall incorrectly. Chrome does not send the URLs of pages you visit to Google for indexing, or for any other reason. Please see the privacy policy. It answers these questions quite clearly: http://www.google.com/intl/en/privacy/ http://www.google.com/intl/en/privacy/
- WalterGR 15y ago
  http://www.google.com/chrome/intl/en/privacy.html http://www.google.com/chrome/intl/en/privacy.html ... > When you type URLs or queries in the address bar, the letters you type are sent to your default search engine so the Suggest feature can automatically recommend terms or URLs you may be looking for. If you choose Google as your search engine, Google Chrome will contact Google when it starts so as to determine the best local address to send search queries. If you choose to share usage statistics with Google and you accept a suggested query or URL, Google Chrome will send that information to Google as well. You can disable this feature as explained here. ... > If you navigate to a URL that does not exist, Google Chrome may send the URL to Google so we can help you find the URL you were looking for. You can disable this feature as explained here. ... > If you enable the optional AutoFill feature, which automatically completes web forms for you, Google Chrome will send Google limited information about the structure of pages that have web forms and information such as the arrangement of the form so that we can improve our AutoFill service for that page. (end excerpts) Could you give us more information about the AutoFill feature? Does it send the URL along with the listed information? Does it do this for every URL that contains a web form?

danmaz74 15y ago

What did you visit after hitting those pages? There is also "referer"...

philfreo 15y ago
nope... no outbound links

mikewest 15y ago

Chrome does not arbitrarily send URLs to Google. We go out of our way to avoid doing that, actually. Look at the implementation of SafeBrowsing, for instance, which does some clever work with hashes to ensure that Google never knows exactly what URL you visited that triggered the warning. It would have been _much_ simpler to just send the URLs, I assure you.

rpearl 15y ago
Chrome, or Chromium? One is open source, one really isn't. The set of things that Chrome does is certainly based on Chromium, but Google certainly has the freedom to add some very useful tracking behavior... if they want to. On one, we have source. On the other, we just have the quote "We go out of our way to avoid doing that, actually." What other evidence?
- mikewest 15y ago
  Given that I'm responding to "I'm pretty sure Chrome send URLs to Google at least for indexing purposes." let's first agree that there's been no evidence provided that I can respond to. :) I mean both Chrome and Chromium. The source is there, we develop in the open, and I'm not sure what additional evidence I can provide to you to prove a negative. Wireshark?
  - philfreo 15y ago
    Well the source for Chrome is not open (edit: correction acknowledged - I thought only Chromium was open), though if you are a Chrome developer confidently saying this is impossible then I would give merit to that. My experiences were non-scientific but still gave me enough suspicious to right this. I may try a more rigorous/careful/documented experiment sometime in the future.
    - justinschuh 15y ago
      The source to Chrome is definitely open and you can compile an effectively identical version yourself (minus the branding). There are some closed source plugins (eg. PDF and Flash) that are shipped as dynamic libraries. However, you could disable them (via about:plugins) or simply delete the corresponding binaries from a Chrome distribution and everything remaining would be open source.

scott_s 15y ago

Try putting up new pages, only visit them in non-Chrome browsers, and see if they still get indexed. If they do, then it's not Chrome.

zobzu 15y ago
and dont forget to disable safe-browsing (which is pinging google) eg in Firefox "block known blah and bleh sites"
- tonfa 15y ago
  Last time I checked, safe-browsing wasn't leaking url, hashes were sent around. Has this changed?

blauwbilgorgel 15y ago

When I had this happen, or when I heard this happen, there was always a reason that was far less sinister than initially thought. * Public referrer logs created a backlink * Somebody (else) published the URL * Somebody (else) shared the URL * You pinged the URL to search engines or other services. * The URL appeared in your RSS feed * The URL appeared in your sitemap * Your pages URL ranges are easily guessable (/item.php?id=1007, /item.php?id=1008) and traversed by a search engine. And more recently, something less innocuous: You simply added a Google +1 button to your pages. When you add the +1 button to a page, Google assumes that you want that page to be publicly available and visible in Google Search results. As a result, we may fetch and show that page even if it is disallowed in robots.txt. http://www.google.com/support/webmasters/bin/answer.py?answer=1140194&hl=en http://www.google.com/support/webmasters/bin/answer.py?answe...