I love W3schools btw. Got me into coding and I still use it for reference. Hate me all you want but I'm tired of people bashing them for no reason.
What redeeming feature do they have? If you aren't easy to use, accurate, comprehensive, or responsive...how good a reference site are you?
I've yet to see anyone bash W3schools for no reason, but I see plenty of people defending them for no reason.
i generally write code at my desk more so then on the go, so i always have those books handy
Their Perl tutorial set is pretty terrible. They call it "PERL" (it's Perl), they believe the latest stable version is 5.10 (it's 5.14) and the code samples are simply awful.
Unfortunately they seem to have moved it onto w3c's domain and now it looks completely awful: http://www.w3.org/community/webed/wiki/Main_Page
Those are not accidental. No one types "www.jigsaw". That's intentionally affiliating the URL with the word "jigsaw" that comes from the W3's validator. Look at the other subdomains. Those can't be accidents. It's not a wildcard thing at all.
That looks like wildcard DNS to me. The question is where the linkbacks are coming from. It is possible w3schools is creating those themselves, in which case that does seem like unethical SEO tricks. But if not, well, they can't be responsible for how people link to them.
My opinion is that they're trying to use technically-allowable but questionable methods to bypass the fact that people are 'blocking' them from search results.
Except they've been providing useful info for longer than Wikipedia has been around. Sounds kind of right to me. They may not be as current as they used to be, but for the 12 years that I've used them they have helped fill in my knowledge cracks and I've appreciated it.
I don't understand the hate. If you really want someone to hate, hate the W3C for making their info so cryptic or non-existent for years that places like W3Schools had a market.
Google states that it "may use everyone's blocking information to improve the ranking of search results overall" so this may be the best way to take action.
You can permanently block them from search results on Google by visiting: http://www.google.com/reviews/t
and entering http://w3schools.com
Edit: Also On DDG the same search would have been !js replace and you would have seen this page : https://developer.mozilla.org/en-US/search?q=replace
I guess it's kind of like a bang, and way better than having to write "site:developer.mozilla.org"
They're not exactly the easiest things to browse or find what you're looking for. For webdevs they've got a load of stuff that you just don't care about.
I did just check out their settings area and it offers a lot of customisation which I love. I might just give it another (duck duck) go!
Don't get me wrong though, I do agree that their different subdomains are a wrong thing to do, and I fully agree if Google decides to punish them by blocking/lowering results for *.w3schools.com for a couple months. I also agree that the Mozilla Developer Network may be a much better resource, both for newbies and professionals. But if you are that much against W3Schools, why don't you use the search function of MDN instead of Google's general search?
Now, it's not merely being wrong once in a blue moon or one or two articles being a bit behind the curve, but the sheer egregiousness of its mistakes plus the lack of action despite being shown to be incorrect (see: w3fools.com) which in the eyes of many qualifies it to be called a "cancer"; certainly in the realm of web development resources, that label seems rather valid.
It is highly unlikely that this was done intentionally, just wildcard subdomains set as many have already said.
Read the last few comments on the actual post for good laugh.
W3Schools is definitely doing something scuzzy here.
Of course, big brands do get penalized like JCPenny and Forbes, but this often happens when they're called out by the media. Google for the most part, since Panda have said they want to rely more on algorithms rather than on handjobs
1) why is w3school in that list?
2) if they got it because lots of (outdated) sites are linking to them, why do their alternate subdomains get a similar bonus?
3) this whole privileged "authority" bucket crap stinks. it used to be that a really good sub-page on somebody's geocities site could be the no.1 go-to first result for a certain search topic. why? because loads of people that knew it was good would link to it because it was just that good of a comprehensive resource. hearing more and more about this new ranking method makes me wonder whether it's even possible for a small guy to come up top in the results like that. And it's not so much that I feel for this small guy, but rather that I know I'm missing out on a lot of honest good web content that Google simply isn't showing me.
If you search for "Remote Unix" on Google (at least for me), a post on my humble blog is the second result. This isn't exactly the narrowest search term, and I'm certainly no juggernaut of a site, so I take that to mean that small random-ass pages can still rank well for a query.
This is exactly why w3schools is at the the top of search results, and exactly why the http://w3fools.com was started -- because there are a ton of developers out there that think that w3schools is authoritative, correct, and kept up to date and link to it and use it. At one time it seemed to fill a niche, but no longer, and the cycle needs to be broken. In the meantime, unless you do some kind of sentiment analysis (and arbitrary changes based on the leanings of google, which you seem to be classifying as a bad thing), pagerank at least would probably conclude that the internet still loves w3schools.
> whether it's even possible for a small guy to come up top in the results like that
w3schools is actually about as small guy as you can get. They may have ubiquity, but it's run by like two people.
> I know I'm missing out on a lot of honest good web content that Google simply isn't showing me.
Yes, but there is too much good web content out there for you to see in your lifetime anyway. Meanwhile, defining "good" based on a nebulous query is kind of the crux of the whole problem, isn't it? I'm not convinced there is an answer.
(Or, I suspect having a $100k+/month Adwords buy probably gives you a magical number to call.)
This very day, I have it on good authority that their ability to game Google's search algorithm is entirely coincidental.
If you enter http://bigresource.com on that page, it will block that site and all subdomains.
duplicate (sub)domains resulting in duplicate sites with duplicate pages mostly have a negative impact on the performance of a webproperty in the SERPs.
a link to www1.example.com does not automatically count as a vote for www.example.com, a link to www.example.com does not count as a vote for www1.example.com, that means they now how two websites both with one vote, instead of one websites with two votes.
additionally, you have two websites which are in competition to each other, and each of these websites has duplicated webpages which are in competition to each other. both websites and webpages usually perform poorer - if google has a doubt which of these duplicated pages on these duplicate sites is the best page to point the user to (said that, google is pretty good in stripping doubt out of the equation for subdomain duplicate pages issues)
if you have a webproperty with a "subdomains gone wild" issue, it is best practice to canonical (either via the canonical tag or via HTTP 301 redirect) them to one (sub)domain. it almost ever (depending on how big the issues was) results in a better performance of the canonicalized webproperty - it definitely helps the site on the (organic) linkbuilding front.
there are thousand reason why a webproperty can have a subdomain gone wild issue (it was (once upon a time) even a common black hat practice of spamming google with subdomain gone wild duplicate web-properties of the competition sites if possible (and it's possible with sites with a wildcard subdomain setting (i.e. wildcard.w3schools.com))
but in most cases "subdomains gone wild" does not have a positive impact on the SERPs. (blocking results is not one of this cases.)
but yeah, what the real issues with w3school? why does this sh/t rank so well?
well first of all it should be said: "you are not statistically significant" just because you (in this case we, the HN readers) are not happy with w3school does not mean the average searcher (searching for HTML web dev stuff) is not happy with it. they are happy (hey, they don't know better) and they use it like crazy. they are happy with what they find. as google is measuring SEPR "long click" very effectively they know exactly how well the average search users uses a page/site. if all users would click back immediately, would not stay long on the page, w3school would not be so dominant as it currently is.
secondly: links - i just did some backlinks check ons some obscure w3school URLs, they all have links. now you might say: oh they buy links... does not look like it, they have links from old forums, new forums, blogs, .edu domains, ...
and: where is the competition? mdn does a great job, but it is a resource for developers, for people who know what they are doing. w3school is a great resource for people who do not know what they are doing or what they are looking for - and w3school has a special page for every single thing / tag that we don't even bother to mention anymore (it's outdated, it's old, some say ugly, but it's there and has a unique description text, a unique example on the page) - that means they have a page for most of the people using the internet interested in HTML, people which think of HTML as a "programming language" - for them w3school is the perfect product, no competition in sight.
what's the solution:
in the xoogler book "I'm feeling lucky" the author describes a case where a wrong product keeps ocurring again and again for popular product searches. they tuned the algorithm again and again, the results got better and better, but the product showed up again and again. the engineers didn't know what to do. one day, it was gone. what happened: one engineer just bought the product. it wasn't listed in the store anymore. the issues was fixed.