Forum Moderators: Robert Charlton & goodroi
But I've never never seen results be so on the bounce for so long.
ALL my sites(80+) are bouncing between google results from 3 weeks ago, and those I see right now. In 30 minutes, they will bounce back again, and then back again, between the two sets of results.
Is anyone else experiencing this? Surely this is not a dance, its gone on far too long.
Anyone else seeing this?
Neither do I and I feel like a very small business
owner when Walmart comes to town. Down the tube.
however the cache shows up different for results with [example.com...] and [example.com...]
for the former one, it shows cache of the site dating back on April 2004
any ideas what's wrong?
I would bet that most folks that enter in a single word like that are looking for a local business.
OK, so what happens when the user in Los Angeles types in "Venice"? How does Google know that user isn't planning a vacation in Venice, Italy rather than a trip to the beach in Venice, California?
And what if that user types in "Venice hotels"? It's unlikely that a resident of L.A. will want a hotel in Venice, California, so localizing the results wouldn't make any sense at all.
I like the idea of localizing results for, say, wireless PDAs (since most people who are walking around with a PDA probably aren't researching restaurant dinners, shopping, or parking garages on the other side of the world). But it wouldn't work very well for mainstream search unless the SE's localization was triggered by a hand-edited list of keywords or keyphrases such as "car dealer," "dry cleaner," or "dentist."
Probably the best way to handle localization is to make it an option on the search page. (While they're at it, they might want to provide a choice between information-weighted and commercially-weighted results, too!)
solution: [webmasterworld.com...]
Version 1:
RewriteEngine On
RewriteCond %{HTTP_HOST}!^www\.widget\.com
RewriteRule .* [widget.com...] [R=301,L]
Leave the "/.*$" off the end of the pattern in the first line - it's not needed and can cause problems if someone appends a host port number, which is a legal thing to do. You must tell mod_rewrite that you want to match periods by preceding them with "\". Otherwise they take on a special meaning of "any single character". An example is the pattern in the rewrite rule above, where "." means "any single character," and "*" means "any number of the preceding".
Version 2:
RewriteEngine On
RewriteCond %{HTTP_HOST}!^www\.widget\.com
RewriteRule (.*) [widget.com...] [R=301,L]
In this case, parenthesized pattern on the left side of the rewriterule is back-referenced by the "$1" on the right. Since it will contain the requested URI, this rewrite works identically to the first version above. Use whichever you like, but I suspect the second version is slightly faster, since it only has to look up the value of REQUEST_URI environment variable once. But that's just speculation on my part, I've never researched it or tested it.
Probably the best way to handle localization is to make it an option on the search page. (While they're at it, they might want to provide a choice between information-weighted and commercially-weighted results, too!)
EFV, users can be pretty dumb. The simplicity behind the original Google design helped make it the popular SE it is today (OK, OK quality of SERPs played a small :) part). Start giving users choices like BOOLEAN operators, tick boxes, refine search options (aka Teoma) and it all becomes too complicated/too much trouble for many of them.
EFV, users can be pretty dumb. The simplicity behind the original Google design helped make it the popular SE it is today (OK, OK quality of SERPs played a small :) part). Start giving users choices like BOOLEAN operators, tick boxes, refine search options (aka Teoma) and it all becomes too complicated/too much trouble for many of them.
I agree that the average user doesn't have a clue how to use a computer or a browser, but I don't think that adding a check box that is un-checked by default is going to cause any great confusion.
If they want to keep the design clean, they could get rid of that stupid 'I'm feeling lucky' button.
Options +FollowSymLinks
RewriteEngine on
RewriteCond %{HTTP_HOST} ^domain.com [NC]
RewriteRule ^(.*)$ [domain.com...] [L,R=301]
I just pulled it from a live server.
