\n is responsible for most of Google’s informational websites like Google’s
\n Jobs site<\/a> v\u0259 ya
\n Privacy Centers<\/a>.
\n Maintaining tens of thousands of pages and constantly releasing new Google sites requires more
\n than just passion for the job: it requires quality management.\n<\/p>\n
\n In this post we won’t talk about all the different tests that can be run to analyze a website;
\n instead we’ll just talk about HTML and CSS validation, and tracking quality over time.\n<\/p>\n
\n Why does validation matter? There are different perspectives on validation\u2014at Google there are
\n different approaches and priorities too\u2014but the Webmaster Team considers validation a baseline
\n quality attribute. It doesn’t guarantee accessibility, performance, or maintainability, but it
\n reduces the number of possible issues that could arise and in many cases indicates appropriate
\n use of technology.\n<\/p>\n
\n While paying a lot of attention to validation, we’ve developed a system to use it as a quality \n Since the beginning we’ve been documenting the validation scores we were calculating so that we Here’s what our data say:<\/p>\n \n On average<\/b> there are about three validation issues per page produced by the Webmaster Team \n This information is valuable for us as it tells us how close we are to our goal of always shipping \n What has to be kept in mind are issues with the integrity of the data, that is, the sample size \n Although we track more than just validation for quality control purposes, validation plays an How do you use validation in your development process?<\/p>\n
\n metric to measure how we’re doing on our own pages. Here’s what we do: we give each of our pages
\n a score from 0-10 points, where 0 is worst (pages with 10 or more
\n HTML<\/a> and
\n CSS validation<\/a>
\n errors) and 10 is best (0 validation errors). We started doing this more than two years ago,
\n first by taking samples, now monitoring all our pages.\n<\/p>\n
\n could actually see how we’re doing on average and where we’re headed: is our output improving, or
\n is it getting worse?\n<\/p>\n![\"HTML](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-7d67e4e3e09e.png\")
<\/p>\n
\n (as we combine HTML and CSS validation in the scoring process, information about the origin gets
\n lost), down from about four issues per page two years ago.\n<\/p>\n
\n perfectly valid code, and it also tells us whether we’re on track or not. As you can see, with
\n the exception of the 2nd quarter of 2009 and the 1st quarter of 2010, we are generally observing
\n a positive trend.\n<\/p>\n
\n as well as “false positives” in the validators. We’re working with the
\n W3C<\/a> in several ways, including reporting
\n and helping to fix issues in the validators; however, as software can never be perfect, sometimes
\n pages get dinged for non-issues: see for example the
\n border-radius<\/code> issue<\/a>
\n that has recently been fixed. We know that this is negatively affecting the validation scores
\n we’re determining, but we have no data yet to indicate how much.\n<\/p>\n
\n important role in measuring the health of Google’s informational websites.\n<\/p>\n