diff options
Diffstat (limited to 'old/published/Webmonkey/Monkey_Bites/2007/05.14.07/Thu/GoogleExperimental1.txt')
| -rw-r--r-- | old/published/Webmonkey/Monkey_Bites/2007/05.14.07/Thu/GoogleExperimental1.txt | 26 |
1 files changed, 0 insertions, 26 deletions
diff --git a/old/published/Webmonkey/Monkey_Bites/2007/05.14.07/Thu/GoogleExperimental1.txt b/old/published/Webmonkey/Monkey_Bites/2007/05.14.07/Thu/GoogleExperimental1.txt deleted file mode 100644 index 98831a2..0000000 --- a/old/published/Webmonkey/Monkey_Bites/2007/05.14.07/Thu/GoogleExperimental1.txt +++ /dev/null @@ -1,26 +0,0 @@ -As part of Google's recent and significant [search overhaul][1], there's a new Google Labs project that allows curious users to try out experimental Google Search features before they're rolled out on the main search page. [Google Experimental][2], as the new section is called, currently features four handy new ways to use the search engine. - -The first feature we'll explore is the new Timeline and Maps views. Timeline allows you see results on a timeline. Google extracts key dates for your search and displays them chronologically (screenshots after the jump). - -Maps view does the same thing but plots significant places on Google maps. - -Obviously both timeline and map views work best for searches related to things with either historical or location contexts such as people, companies, events and places. - -If you find yourself using either of these features on a regular basis there's some new search operators that allow you go directly to either view, just append <code>view:timeline</code> or <code>view:map</code> to the end of your search parameters. - -Of the two I think the maps visualization will end up being the most interesting, especially as geodata continues to infiltrate the metadata structure of the web. For instance, this search maps results for the phrase [Wired Magazine][3]. - -At the moment the results range from San Francisco (our home office) to 2005's Wired NextFest in Chicago, neither of which are particularly astounding. - -But imagine if Wired were to add some metadata in our posts that allowed Google to index the location each article was filed from -- the results would be a global map index of Wired stories, which would be an interesting visual way to explore the site (or any other site with similar data). - -Taking this idea a bit further you can combine the <code>view:map</code> operator with the <code>site:</code> operator to get a visual representation of all Wired stories that [mention a specific location][4]. In that link I've searched for all stories that mention a location and contain the search term "Firefox." - -Note that this also highlights some flaws in Google's technology since a mention of the the fact that Firefox was once called Phoenix causes Google to associate that result with the city in Arizona. Clearly the Maps view has some kinks to work out. - -Google hasn't announced any formal plans for the new experimental search visualizations, but some kind of standardized geo format information in the sitemaps protocol strikes me a logical way to tell Google about location data relevant to each page of a site. - -[1]: http://blog.wired.com/monkeybites/2007/05/google_to_add_e.html "Google To Add Embedded Videos to Default Search Results" -[2]: http://www.google.com/experimental/ "Google Experimental" -[3]: http://www.google.com/views?q=wired+magazine+view%3Amap&btnGm=Search "Google Maps Search: Wired Magazine" -[4]: http://www.google.com/views?q=Firefox+site%3Ahttp%3A%2F%2Fwired.com+view%3Amap&btnGm=Search
\ No newline at end of file |