We usually aim for friendly (vanity) urls to help visitors identify where they are in the website, e.g. www.website.com/products/acme-product. But, are there standards here for search results?

At the moment our search results are something like this:


The search query string seems intuitive to me, but I am looking for some standards here - or, if it's been identified that we don't need to worry about intuitive URLs for search results.

  • 1
    The by=<category>=<selected_category> is non standard. A standard form would be category=<selected_category>. Or in general base-url?param1=value1&param2=value2&param3=value3. Commented Jul 10, 2012 at 22:59
  • Making them pretty enough is nice, but I wouldn't risk making the back end (significantly) code more complicated to try and make search urls more readable; unlike static pages it's unlikely they'll ever be typed in or bookmarked (and if they are bookmarked, they still work, so what?)
    – Zelda
    Commented Jul 11, 2012 at 13:06

3 Answers 3


I recently did some research on that, and I came to the conclusion that the search urls needn't be accessible. It is surely nice to have them accessible like http://yourdomain.com/search?q=hello, but if you cannot manage that, it's no big issue.

How I came to these results:

There may be, however, other things which speak for considering an easy search url

  • If you want to make your search url an access point of your API, for example, developers are surely happy to have easy accessible urls

  • If you want to implement Open Search on your site so the user can use your site as a search engine in his/her browser, easily accessible urls reduce implementation time.


It is important to stick to the search standards so that:

  1. Other utilities can search your sites. E.g. so that users can define (or add existing) search engine definitions to their browsers. (This is more of a SW API issue than a UX issue.)

  2. Advanced users can quickly edit the query.

  • That's a good point. I use the Chrome address bar to search directly in many sites. When I have to add a new search engine, I appreciate the fact that the search URL is easy to read and edit.
    – Pep López
    Commented Jul 11, 2012 at 19:46

Why not continue the 'vanity' standard you established with your users else-ware in the site?


Use a url mapper to set the /<param>/ to be executed by convention. This should not a big technical challenge and services both the points brought up by: Danny Varod

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.