What does 450 Policy violation mean? I did a search for my domain name in Google and this came up in the results: X-Google-Crawl-Date: Sat, 01 Oct 2005 19:28:56 GMT 450 Policy ... X-Google-Crawl-Date: Sat, 01 Oct 2005 19:28:56 GMT 450 Policy violation. When I did a search on "450 Policy violation" a lot of sites came up.
So the error is in the header of my website? Is there somewhere else, other than search results, I can check after I've updated my site?
I'm not certain but I don't think it's your site. I suspect that's a server issue. I would start by contacting your host and letting them know about this. You can also check what headers are being returned for your site here: http://www.kenkai.com/seo-tools-page-header.php or http://www.searchengineworld.com/cgi-bin/servercheck.cgi
I think it may be way too quick to automatically assume that any 3-digit number is automatically an HTTP status code. Particularly when the code doesn't match the standard error text... If you do a search for "450 Policy violation", and start looking at the sites, they're almost all sites that you'd certainly hope Google would ban from its indexes(mostly parked domains). If you view the 'cache' on one of these, you'll see somply "450 Policy violation" as the text. My thoughts: 1. Google Spider downloads all webpages 2. Google Processor sees something bad about these specific pages, and passes this data, "450 policy violation", along with the date, to the Google Indexer. Or maybe it's just an HTTP status code with mis-matching code to standard error text... But I don't think so... -- Derek
If we had a URL we could determione if the headers are returning anything odd. If that's the case, though, dkalweit, why haven't we heard about it before? Is this something new in Google? It's not like sites haven't been banned in the past...
The domain in question is newlovelife.com Until last week it was parked at sedo. I ran it through the sites referenced by minstrel and they came back ok. Could it be referencing an old cache?
We have just been going through a major update called Jagger, as I know you know... Matt Cutts has been openly stating that it was addressing spam. If you do the search on google as I suggested, you'll see that all the datetime stamps are on or after 9/30/2005(from what I could see). This is well within Jagger's data-collection phase, at least(and many report seeing major updates since 9/22, including myself). Now, if these results were showing for the past month, who knows-- maybe they're just now starting to show up. Either way, it's possible that we just now have heard about them, as based on the time stamps they're all fairly recent(<5 weeks old). Yes, site have been banned in the past, but one of people's biggest beef with Google, is not being told out-right. Maybe this is Google telling people out-right. New things happen all the time... Keep your mind open. Just because something didn't happen yesterday, doesn't mean it won't happen tomorrow. -- Derek
The site was last cached on 10/1 according to Google. If this site was parked at SEDO at that time, I'd say that it matches up with all the 'policy violation' sites for content-- Google has no reason to index parked domains. Considering parking is so common, I'd think(hope?) that Google would continue to index the site for changes and start to index this new page. thatgirl, if your site comes back in Google(indexed for real content instead of '450 policy violation'), please tell us here-- it will help us know if people can come back from this sort of 'policy violation' if it's a new Google thing as I suppose. -- Derek
Finally my site was indexed for the current content. Here's the timeline: 10/30 -- put up new site (on existing domain parked at sedo) and started submitting to engines 11/6 -- submitted sitemap to Google 11/14 -- started Adwords campaign 11/20 -- finally re-indexed by Google Thanks!