Some SEO analysts says that fixing W3C validation errors of a website is an important On Page Optimization if so why
www.google.com has 23 W3C validation errors, 4 warning(s)? Does Google consider those errors?
Webmasters Stack Exchange is a question and answer site for pro webmasters. It only takes a minute to sign up.Sign up to join this community
Google doesn't take into account W3C errors for SEO. There are so many big websites with a bunch of errors which have a good ranking in Google for many keywords.
Having a W3C compliant website is good practice because you're sure your website respect rules of web semantic but there is no influence for SEO unless you have invalid HTML which is creating difficulties for bots to read your content (like an unclosed
W3C Validity is not a direct ranking factor however several errors the validator may return for your website are considered as good practices for SEO. Problems like wrongly nested or placed tags can make your content impossible to crawl. Search Engines do a very good job to find their ways through the content inside non-standard or problematique code however if you want to increase your chances; just make your code valid, it's not that hard. Also valid code takes less space and can make your website load faster.
Google does not take W3C Validation into account for SEO.
From the Official Google Webmaster's Youtube Channel,
(taken via the video's transcript)
And while it's great to make valid code, and it can be easier to maintain if you know that all your nesting is in good shape and everything validates, we have to crawl and index and return results on the web even if pages don't validate. And so we don't give any sort of boost to pages if they validate. It may be a nice thing to do for your own internal purposes, but it doesn't get any sort of Google boosting in your rank or anything like that. And the simple reason is that the vast majority of pages on the web don't validate as it is right now.
A lot of those "errors" are their use of deprecated or obsolete markup but that markup is for older browsers and mobile devices that won't work well without it. Removing the obsoleted markup knocks that number down quite a bit.
While there are some flat out errors in there, if it's not intentional to help old browsers and devices along, are probably just simple mistakes. Google pages, including this "simple" home page, is quite complex and dynamically generated. Just look at the source. There's a lot of stuff going on in there and some simple, human errors may have creeped in.