美國 Google 接續 方法 = Link 바로가기 URL(Uniform Resource Locator)
https://www.google.com/webhp?hl=en&gws_rd=ssl?gl=us
美國 Google을 韓國에서 接續 時 www.google.com으로 接續해도 www.google.co.kr로 되돌아와 버립니다. 그래서 相當히 많은 분들이 google.com에 對한 檢索結果를 보기 爲해 美國 Google을 接續하는 方法을 물어오는데요, 美國 Google에 接續하는 方法은 相當히 많습니다.
Link URL 1 : https://www.google.com/ncr
Link URL 2 : https://www.google.com/webhp?hl=en
Link URL 3 : https://www.google.com/webhp?hl=en&gws_rd=ssl?gl=us
여기서 Google이 使用하는 Parameter에 對하여 잠깐 說明합니다.(Parameter는 URL 뒤에 나와 있는 “?”로 連結된 部分입니다.)
https://www.google.com/webhp?hl=en&gws_rd=ssl?gl=us
hl=en : 言語가 英語
gws_rd=ssl : https 卽 檢索 時 Key Word에 對해 保安이 됨
gl=us : 地域이 美國
海外 Google의 迂廻接續方法은 다른 記事에서 다루게 됩니다. 現在 美國 Google 뿐 아니라, 모든 Google이 SSL을 導入하게 되어 http → https로 保安이 되는 URL로 變更되었습니다.
美國 Google 住所 Link : https://www.google.com/ncr
美國 Google 住所 Link : https://www.google.com/webhp?hl=en?gl=us
英國 Google 住所 Link : https://www.google.co.uk/webhp?hl=en?gl=uk
濠洲 Google 住所 Link : https://www.google.com.au/webhp?hl=en?gl=au
Russia Google 住所 Link : https://www.google.ru/ncr(檢索窓 下端에 러시아語 링크 클릭)
France Google 住所 Link : https://www.google.fr/ncr(檢索窓 下端에 프랑스語 링크 클릭)
美國 Google 接續 時 한 가지 確認할 點 :
美國 Google 接續 時 Browser의 言語를 確認해야 합니다. 반드시 英語로 나온 境遇처럼 모든 內容이 英語로 나와야 제대로 接續되었다고 볼 수 있습니다.
萬若 言語가 아직도 韓國語라면, 檢索窓 右側 上端에 톱니바퀴 Button을 Click하여 言語를 選擇합니다. LANGUAGES, 그리고 ENGLISH를 選擇하고 貯藏하면 英語環境에서의 檢索結果가 나타납니다.
On Chrome Browser, Google Pane Right Upper⋮(Controll) → Settings → Advanced Settings → Languages →
여기까지 Check하여야 비로소 美國 Google에 제대로 接續했는지 아닌 지를 確實이 알 수 있겠지요! 그리고 Google과 宮合이 제일 좋은 브라우저는 ‘Google Chrome’이라는 點 잊지 마시고, 時間되시면 Google Chrome을 設置하여 Web-Surfing을 한다면 自動飜譯 等 Google의 便利한 機能을 잘 利用할 수 있게 됩니다. Google과 함께 즐거운 Web-Surfing을 하세요.
原文보기
How To Access Google USA From Other Countries?
Copyright © Walker 04 Oct 2010 23:36
Do you know how to access Google.com from outside of USA? Yes, there is a “switch” to stop Google.com redirects to the country domain where you access the Google Web Search service.
Suppose you’re at UK so when you type Google.com on web browser, it is automatically redirected to Google.co.uk. To disable this country redirection, you should change the Google.com to this URL: Google.com/ncr where the ‘/ncr’ is probably acronym of “No Country Redirect”. Whatever it is, this handy trick allows you to access the “original” Google.com instead of being redirected to other Google.com version of the respective countries.
Of course, you may also configure the web browser to access a US-based proxy server, establish a VPN connection to US, etc. The “/ncr” is just too simple to use!
UPDATE: See also the trick used to set Google Chrome default search engine to Google NCR.
I personally prefer to use the “real” Google.com if I want to locate the search subject in USA. Otherwise, the Google of other countries is flavored.
A Capsule of Walker’s Experience in Life
How To Set Google Chrome Default Search Engine To Google NCR?
It’s not always appropriate to use localized Google Search to look for info from the Net, unless you’re searching for localized topics. My preference is to use Google NCR (no country redirect), i.e. Google US edition.
However, this can be a little challenging when using Google Chrome (my preference of web browser too). So, let’s see how to configure Google Chrome default search engine to Google NCR or Google of your home country.
1. Right-click on Address bar (a.k.a. omnibox) and choose “Edit search engine”
2. Uses “Other search engines” section to add your preference. For example, type “Google NCR” in first two boxes and fill the 3rd box with this string:
http://www.google.com/search?&q=%s
To use Google UK, replace that string to be like this:
http://www.google.co.uk/search?&q=%s
Thus, to use Google of your preference country, just update the string with localized Google Search URL.
3. Once finish editing 3rd box, press ENTER key to add this new record.
4. Hovering your mouse pointer on that new record and click “Make default” button.
Thereafter, the Google Chrome will use Google Search edition of your choice and not the localized edition to do googling:
After knowing the trick, you may say it’s just piece of cake.
Official Blog
Insights from Googlers into our products, technology, and the Google culture
Making URLs shorter for Google Toolbar and FeedBurner December 14, 2009
This morning, we launched updated versions of the Google Toolbar and FeedBurner that offer a new URL shortening service from Google called the Google URL Shortener. We mentioned our URL shortener as a feature in both announcements, so we wanted to say a little more about how this product works and why we're offering it.
People share a lot of links online. This is particularly true as microblogging services such as Twitter have grown in popularity. If you're not familiar with them, URL shorteners basically squeeze a long URL into fewer characters to make it easier to share with others. With character limits in tweets, status updates and other modes of short form publishing, a shorter URL leaves more room to say what's on your mind — and that's why people use them.
First, we think people who use the Google Toolbar and FeedBurner will benefit from a shortener that is easily accessible — making it faster and easier to share, post and email links. Second, we've built this on Google's global infrastructure to offer the following benefits:
Stability: Google's scalable, multi-datacenter infrastructure provides great uptime and a reliable service to our users.
Security: As we do with web search, shortened URLs are automatically checked to detect sites that may be malicious and warn users when the short URL resolves to such sites.
Speed: At Google we like fast products and we've worked hard to ensure this service is quick. We'll continue to iterate and improve the speed of Google Url Shortener.
Google URL shortener is not a stand-alone service; you can't use it to shorten links directly. Currently, Google URL Shortener is only available from the Google Toolbar and FeedBurner. If the service proves useful, we may eventually make it available for a wider audience in the future.
We're excited about enabling this functionality — try it for Toolbar and FeedBurner!
Posted by Muthu Muthusrinivasan, Ben D'Angelo and Devin Mullins, Software Engineers