Forum Moderators: mack
http://search.live.com/result.aspx?q=KEYWORD&mrt=en-us&FORM=LVSP
When I load the referred page then I am told that there are no results. Also there is no relationsfip between the keyword and the page requested. The Kkeywords are single words and seem to be mainly concerned with the normal spam areas.
I have scoured Live to try and find form 'LSVP', searched everywhere that I acn think of.
Can anyone enlighten me as to what the heck form LSVP is? Have the spammers foound another flaw? I am based in the UK.
Thanks in advance.
[edited by: engine at 10:30 am (utc) on Aug. 18, 2007]
[edit reason] delinked [/edit]
They are hitting my sites mostly with keywords that appear on the site.
(With the exception of the porn keywords that are bad enough that I won't list them here.)
Sending porn referrers to Web sites on a massive scale cannot seriously be considered a "quality check", unless we are talking about the low quality of the concept.
My thought is that Microsoft wants webmasters to click through on the referrer links which will boost live.com's traffic. Microsoft might be thinking, "if we send them keywords that they are interested in, maybe they will start using Live.com Search".
I may be cynical by nature, but the exact same theory has passed my mind too.
I'm struggling to find any other reason.
The good news though is that despite banning the nuisance IP range, we've seen an upturn (up from 1% to 3% of total) in the number of genuine searches coming from Live Search and the real bot is happily spidering away and updating cached pages.
I may be cynical by nature, but the exact same theory has passed my mind too.
* Microsoft is sending keywords that match the subject matter of the Web sites
* They also insert some porn-related keywords
* This exactly matches referrer-spam behavior
* "MSNdude" ambiguously calls this a "quality check" and will not directly reply to concerns about this problem
* What kind of "quality check" would require sending of referrer strings to the webmasters' logs? Why does a webmaster need to see these referrers? Is MSN going to interview us about it when they are done?
Come on... there are a lot of experienced webmasters here. Can anyone think of any possible reasons why a "quality check" would require sending referrer strings that match the content of the site, or referrers that include porn words?
This is referrer spam.
Come on... there are a lot of experienced webmasters here. Can anyone think of any possible reasons why a "quality check" would require sending referrer strings that match the content of the site, or referrers that include porn words?
I can think of 2 non-legit reasons, and while they might both be a bit out there and tin foil hattish, I cannot think of any legit ones that would make more sense.
1) They are trying to boost their market shares by tricking millions of webmasters into checking their rankings on live.com
2) They are inflating the impressions of people AdSense reports, lowering their eCPM, in anticipation of releasing their own contextual advertising program for publishers, since if people start making less on G they would be more likely to switch.
Any other theories?
-Michael
Am I negatively biased from history? Well, probably. But this is too much, M$, way too much.
Kind regards,
R.
It pumps up their traffic numbers when Webmasters click through on their referrers to MSN Live.com.
I've already contacted a couple of media organization about it. Hopefully the story will be investigated and publicized.
It's corrupting my stats.
Maybe there should be a "ban LVSP" movement. Someone should write a WordPress plugin to block LVSP referrers...
As far as blocking this spider, not taking the Bandwidth into consideration, wouldn’t the entry still appear in the log file, but just with different status code returned? So would this be kind of useless as far as not having the entries in the log file?
wouldn’t the entry still appear in the log file, but just with different status code returned?
If you block with .htaccess rules, yes, you are right, the logs get polluted with that referrer spam, regardless if it comes with 200 or 403 status codes.
A better medicine would be grounding their IP addresses in the firewall, so the web server woulndn't see them at all.
That, however, prevents from seeing what is going on.
So, I let my webservers send them a 403, watch their tail through the logs, and later cut them out with a grep -v before processing the statistics.
This thread isn't dead yet ...
Kind regards,
R.
At least the IP address of the referrer-spam-bot now resolves to a valid "...search.live.com" name instead of the former invalid ".....phx.gbl". Did not check if they just changed IP addresses or finally fixed their DNS records.
livebot-65-55-210-70.search.live.com - - [22/Nov/2007:xx:xx:17 +0000] "GET /special/page.htm HTTP/1.0" 200 9820 "-" "msnbot/1.0 (+http://search.msn.com/msnbot.htm)" 65.55.210.70
livebot-65-55-165-98.search.live.com - - [22/Nov/2007:xx:xx:49 +0000] "GET /special/page.htm HTTP/1.0" 403 213 "http://search.live.com/results.aspx?q=special&mrt=en-us&FORM=LIVSOP" "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; .NET CLR 1.1.4322)" 65.55.165.98
Apparently, they don't get the message ...
I ask only out of curiousity, as threatening to ban a peeved-off webmaster is no threat at all... Never forget! They need us more than we need them! :)
... have you noticed any adverse effects?
Hard to tell, as I got very few traffic from MSN/serach.live before, and when looking at the raw logs now, I still see some real users occasionally coming from MSN, after all.
So doesn't look like a hard ban. Another piece of FUD from MSN?
Since the logs are screwed up by their ongoing* log spam and are therefore worthless, I can't tell for sure, if it is the same amount of traffic as before, or more, or less.
*ongoing: yes, this unfamous operation is still ongoing. Not high volume, but annoying.
Kind regards,
R.
-Michael
One of the biggest challenges with relevancy is how to distinguish legitimate information from various forms of search spam. This is one area that we've made especially good progress in over the last 8 months through a suite of tools that helps us detect, evaluate and manage spam. One of these tools is an extension to MSNBot, giving us an additional way to detect cloaking.
-Michael
You know what.... At least they are honest about what they are doing...
Google and Yahoo don't say a word about this...
Supposedly, search engines still won't spider the page with these spiders if their bot is blocked. But who knows...
Microsoft is still learning and Webmasters are much more advanced these days compared to the older days when Google was developing technology like this...
I don't know about you, but I am not satisfied at all with what they wrote.
They had to make a public response so they are trying to save face -- I'm not buying it either.
Unanswered questions:
* Why send referrers? The fact that they use an easily identifiable referrer (LIVSOP) means that it should be very easy to cloak against.
* Does anyone seriously spend a lot of effort cloaking to MSN? MSN/Live often sends little more traffic than Ask.com.
* Why download external JavaScript? (e.g., AdSense)
* Why did it take so long for Microsoft to come up with an explanation to the problem? And why doesn't MSNdude respond here?
It seems more likely to me that it was at least partially designed as a referrer spam campaign.
65.55.165.63
Http Code: 200 Date: Dec 19 05:39:12 Http Version: HTTP/1.0 Size in Bytes: 11209
Referer: <snip>
Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; .NET CLR 1.1.4322)
Considering the large amount of traffic on these secondary pages, a redirect script was added to send all external visitors (that are not referred from a local page) to the main page.
Also the customer complained about huge amounts of traffic beeing eaten up by bots. :¦
[edited by: engine at 12:03 pm (utc) on Dec. 19, 2007]
[edit reason] See TOS [webmasterworld.com] [/edit]
Two of my sites are just now getting hammered by the so-called MSLIVSOP bot log-spamming with fake, site-specific keyword referers of the form previously reported --
http://search.live.com/results.aspx?q=KEYWORD&mrt=en-us&FORM=LIVSOP
-- all hailing from MS corporate hosts/IPs --
livebot-65-55-165-aa.search.live.com
livebot-65-55-165-bbb.search.live.com
livebot-65-55-209-cc.search.live.com
-- all supposedly running --
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; .NET CLR 1.1.4322)
-- and some, but not all, hitting js in addition to html.
I decided the quickest solution was to allow only msnbot and/or msnbot-media from .search.live.com. Live human visitors don't show as coming from that host anyway.
And I thought I had enough problems with occasional MS employee abusers via tideXX.microsoft.com. Alleged MS corporate abuse using MSLIVSOP is significantly more resource-wasting.
[1][[b]edited by[/b]: Pfui at 12:24 am (utc) on Jan. 14, 2008][/1]
msnbot grabs robots.txt
msnbot grabs a page
Referral comes in the form of LVSP.
For a company their size, their approach to search engine technology is a joke. Their support is a series of "canned" responses. Their index is full of spam. Thankfully all their problems are completely obvious to end users.
If Live weren't the default on many browsers, they'd have close to zero share of search.