Irritating that you have to do it, but:

html canvas -site:w3schools.com

Probably returns what you wanted.

There was a way to remove results from Google 5 years ago that worked and I've used before, but now you need to use a chrome plugin apparently this says. Post comments afterwards are still a few years old but may still apply today

https://webapps.stackexchange.com/questions/35786/is-there-a...

This is because we are lazy and we use a search even if we could go straight to a specific site eg MDN, Stack Overflow, Wikipedia.

For me lazy has nothing to do with it. Usually one or more of the following:

* You have to navigate a half dozen pages to get to what you want assuming you can navigate the maze of links.

* Site search incompletely indexes the site.

* Site search has poor ranking. Twenty pages of press releases and other crap mentioning what you want before the actual info.

* Site search doesn't handle spelling mistakes so you get no results.

* Site search doesn't handle related topics so if you search for the wrong or alternate phrase you miss what you need.

* No site search feature at all.

So yeah, search engine is my first choice.

Isn't exactly that the job of a search engine? I.e., that don't have to specify the exact site? Moreover, many searches are done be beginners who don't (yet) the best resource for what they search for.

But let's assume you use a search engine only for stuff you aren't intimately familar with - how could you trust the quality of the results? If they are so bad at the topics you know much about - why should they be better at the other topics?

Another way to look at it is people are expressing a need to have a single good search tool rather than having to learn every individual site's search tool. Site hosted search varies wildly in quality too since many don't get much direct use (perhaps largely because most people uses general search tools like Google). I know I've built up a (usually unconscious) decision making bias that "search on site always sucks" that makes me shy away from them in. It feels like a reasonably rational decision to do so vs being garden-variety lazy.

There's also the w3fools browser extension that removes w3schools from search results.

I agree. An easy workaround is to add "mdn" to the search.

That was my workaround, too.

But now I have a better workaround which doesn't only work for mdn, but any other high-quality resource: I edited my browser settings to use a different search engine by default. (currently DDG)

It's a bit more work but, alternatively, you could also add a "new" search engine to your browser that uses a custom keyword (e.g. "!mdn") and passes your query to the search interface on the MDN site.