"W3C validation isn't the same as using valid enough code for the search engines to index the site." isn't it? and i never said some w3c vaildity. i said some valid code (and therefore a degree of w3c validity.)
i'm not quite sure how you can make a distinction between some valid code for indexing and some (i.e. mostly) valid code for w3c validation.
by making the site with fewer coding errors then you are moving towards w3c validation and therefore better indexing (or at least indexing with fewer problems.
you're argument- if i understand it correctly - is that w3c validation isn't important at all, whereas i'm saying a largely valid site (and you surely must see that though a site might not validate because it has 2 errors is not the same as a site that doesn't validate with 100s of errors) is going to have fewer problems that being indexed and therefore
aiming for W3c validation is intrinsically tied up with improving indexing.
you said w3c validation is "
not at all important" but contradict yourself by saying "As long as the markup of the page/site is valid enough to be indexed properly,"
wouldn't you say that at least running your site through the validator will show any coding errors and therefore any potential problems with indexing?
no-one is talking about "Having a bright shiny W3C Valid logo on your footer" that would look amateurish nowadays anyway
