3 ms·
Two potential problems: 1) I don't recall who it is, but someone who is not google holds a patent (sigh) on using the URL path after the host as the search str
by iigs 17y ago
Two potential problems:
1) I don't recall who it is, but someone who is not google holds a patent (sigh) on using the URL path after the host as the search string.
2) If it was my property to control, I would not want google.com/{*} to accumulate links on the internet. That is to say, before there was google.com/maps, one would expect some people to link to that URL directing their users to search for maps. Now that google is so big, that could be a dicey prospect, because substituting their own property for what would have previously been a search could reasonably be seen as anti-competitive.
- roryokane 17y agoIn response to point 2, Google could still require that links to search pages still go to google.com/search?q=whatever. google.com/whatever would show a differently formatted page that shows a big error message at the top, with the search results as an extra, not the point of the page. This would mean that Google introducing new sections of the site would not conflict with links to search pages.