I need to check with the guys to see how reliable the URL creation is, but then there's the issue of changing data which search engines don't like. Even if we used the path/to/something method, the search results would vary day to day, so we'd probably want to block search results via robots.txt anyway right?
I don't care as much about how it looks, I just want to ensure that we're not missing out on anything that you can only get with the traditional method.
Prior, we were keeping search params in the session but nixed that in favor of sharable URLs. So the key here is sharability and reliability.
--- On Tue, 9/1/09, Michael Tougeron <[address removed]> wrote:
> From: Michael Tougeron <[address removed]>
> Subject: RE: [php-139] Search arch question
> To: [address removed]
> Date: Tuesday, September 1, 2009, 9:08 AM
>
>
>
>
>
>
>
>
> There used to be a debate about
> this around SEO impact. e.g.,
> if the text is in the query string it doesn't count to
> keyword matching but if
> it was in the dir structure it would. But I'm
> pretty sure that it doesn't
> matter anymore.
>
>
>
> Personally, and this is just my
> opinion, I'd rather use the
> query string method for search. I think there would
> be less of a chance
> of mistake with the creation of the URL. For
> product URLs or
> listing pages I prefer something more like
> /music/bands/country
/top10.html.
>
>
>
> -Mike
>
>
>
>
>
>
>
> From: [address removed]
> [mailto:[address removed]] On Behalf Of Robert
> Gonzalez
>
> Sent: Tuesday, September 01, 2009 8:46 AM
>
> To: [address removed]
>
> Subject: Re: [php-139] Search arch
> question
>
>
>
>
>
>
>
> Is it
> really just a matter of
> how it looks?
>
>
>
> On Tue, Sep 1, 2009 at 2:16 AM, Scott
> Hildebrand <[address removed]>
> wrote:
>
> So this
> project I'm involved
> with is doing queries this way:
>
> /search/q/music/l3/u
kiah/lid/2449750/l2/
California/l1/United
> States/r/300/jt/+/i/
+/c/+
>
>
>
> It basically amounts to search being the controller, and
> then the rest are
> key/value pairs. When there's no value it ends up just
> being "+"
>
>
>
> I think that's fugly and I'd rather see a
> traditional URL:
>
> /search?q=music&
l3=ukiah&lid=244
9750&l2=Californ
ia&l1=United
> States&r=300&
jt=&i=&c=
>
>
>
> Is there any reason why a traditional URL would be better,
> or am I just
> outnumbered by the other engineers and out of luck?
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
> Please Note: If you hit "REPLY", your message
> will be sent to
> everyone on this mailing list ([address removed])
>
> http://www.sfphp....
>
> This message was sent by Scott Hildebrand ([address removed])
> from The San Francisco PHP Meetup Group.
>
> To learn more about Scott Hildebrand, visit his/her member
> profile: http://www.sfphp....
>
> To unsubscribe or to update your mailing list settings,
> click here: http://www.meetup...
>
> Meetup Support: [address removed]
>
> 632 Broadway, New York, NY 10012 USA
>
>
>
>
>
>
>
>
>
> --
>
>
>
> Robert Gonzalez
>
> http://www.robert...
>
>
>
>
>
>
>
>
>
> --
>
> Please Note: If you hit "REPLY",
> your message will
> be sent to everyone on this mailing list
> ([address removed])
>
> This message was sent by Robert Gonzalez
> ([address removed]) from The San
> Francisco PHP Meetup Group.
>
> To learn more about Robert Gonzalez, visit his/her member
> profile
>
> To unsubscribe or to update your mailing list settings, click here
>
>
>
> Meetup Support:
> [address removed]
>
> 632 Broadway, New York, NY 10012 USA
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
> Please Note: If you hit "REPLY",
> your message will be sent to everyone on
> this mailing list ([address removed])
>
> This message was sent by Michael Tougeron
> ([address removed]) from The San
> Francisco PHP Meetup Group.
>
> To learn more about Michael Tougeron, visit his/her member
> profile
>
> To unsubscribe or to update your mailing list settings, click here
>
>
>
> Meetup Support: [address removed]
>
> 632 Broadway, New York, NY 10012 USA
>
>
>