谷歌使用＃代替搜索？在URL。为什么？ [英] Google using # instead of search? in URL. Why?
问题描述
我不知道多久，他们已经做了，但我只是用谷歌发现的＃在其搜索网址，而不是搜索
新办法
http://www.google.com/#q=stackoverflow
老办法
<一href="http://www.google.com/search?q=stackoverflow">http://www.google.com/search?q=stackoverflow
的磅/散列符号通常用作锚页面的一个部分。
除了一个较短的URL这可能是谷歌的好处？这似乎违背了搜索引擎的惯例，但话又说回来谷歌设置约定。是否有任何问题，你可以看到这种方法？
更新
为了测试自己使用的 www.google.com 一般的搜索框。你会得到的网址，但在Q前部的一些其他垃圾=就是我引用了这个问题。
更新2
看起来这可能是他们正在测试的随机用户如一些人被重新路由到的搜索？的试图进入的＃的结果时结果。<实验性功能/ P>
更新3
从谈话中这里看来这已经被推广到所有的Firefox使用主google.com网站搜索用户
摘要的
09年4月27日 该＃查询参数是一个 单独的实验中，该搜索 团队在做（基于AJAX的搜索 结果页）的开始一段时间 背部。它很热切讨论 在雅虎网站分析讨论 组几个月前。随机组 的人/分配是一个 实验的一部分，那 会导致所有的关键字数据为 用户从每个分析dissapear 工具。它看起来像实验 仍在进行中。
09年4月28日的＃查询参数 似乎已被推广到所有 在www.google.com Firefox用户 SERP`s，因此必须已通过 测试阶段。我猜测， Firefox是能够更好地处理AJAX 该IE的，因此，它没有被轧制 出到IE浏览器的用户。
09年5月1日当我挖成SERP的 它看起来像谷歌最初的网页 把网站真实的网址，在 链接，但一旦链接被点击的 的URL被替换为谷歌重定向 形式的网址 www.google.com/url?q=flowers&blahblahblah。 重定向URL是显示在 在HTTP引用领域，哪些得到 报告的web浏览器（和 因此，分析工具）。
我的谷歌仍然使用搜索？ preFIX，使用散列但受益（ ＃）是它不需要重新加载该页面。添加查询字符串（？）强制页面重新加载在所有浏览器。
通过使用散列它们可通过允许它坚持在浏览器元件保持在记忆的项目。添加哈希也创造了该页面的历史记录对象。这保持前进和后退的功能，同时让他们来处理使用AJAX搜索。基本上，这意味着他们可以处理你的搜索更快只为获取加载整个页面所需的HTTP标头的一个子集，而不会失去一个满负荷的功能。
I'm not sure how long they've been doing it but I just noticed google using # in their search url instead of search?.
New way
http://www.google.com/#q=stackoverflow
Old way
http://www.google.com/search?q=stackoverflow
The pound/hash sign is generally used as an anchor to a section of a page.
Besides a shorter url what could be the benefits to Google? It seems to go against search engine convention, but then again Google sets convention. Are there any problems you can see to this approach?
UPDATE
To test for yourself use the general search box on www.google.com. You'll get some other junk in the url but the portion before the q= is what I'm referencing for this question.
UPDATE 2
Looks like this may be an experimental feature they're testing with random users as some people are being rerouted to the search? results when trying to go to the # results.
UPDATE 3
From the conversation here it appears this has been rolled out to all firefox users using the main google.com site for searching.
excerpts
4/27/09 The # in query parameters is a separate experiment that the search team was doing (AJAX based search results pages) that started some time back. It was discussed quite fervently in the Yahoo Web Analytics discussion group a few months ago. Random groups of people were/are assigned to be a part of the experiment, and that caused all the keyword data for that user to dissapear from every Analytics tool. It looks like the experiment is still going on.
4/28/09 The # in query parameters appears to have been rolled out to all Firefox users on www.google.com SERP`s, so this must have passed the testing stage. I am speculating that FireFox is able to handle AJAX better that IE, thus it has not been rolled out to IE users.
5/1/09 When I dug into the SERP's pages it looks like Google initially puts the websites "true" URL in the link, but once the link is clicked the URL is replaced with a Google redirect URL of the form www.google.com/url?q=flowers&blahblahblah. That redirect URL is what shows up in the HTTP referrer field and what gets reported by the web browser (and therefore the Analytics tools).
My google still uses the search? prefix, however the benefit of using the hash (#) is that it does not require reloading the page. Adding a query string (?) forces the page to reload in all browsers.
By using the hash they can keep an item in 'memory' by allowing it to persist in the browser element. Adding the hash also creates a history object for the page. This maintains forward and back functionality, while allowing them to process your search using AJAX. Basically this means they can process your search quicker by only having to fetch a subset of the HTTP headers required to load an entire page without losing functionality of a full load.
这篇关于谷歌使用＃代替搜索？在URL。为什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
