Validating an entire site

Using the W3C validator to check a single document is easy. But what if you need to validate an entire site consisting of hundreds or thousands of pages? Read Validating an entire site at Standards-schmandards, where Pete explains how to install the W3C validator and use it to batch validate entire sites.

Excellent stuff, and it caught a couple of errors that had managed to sneak their way into a site I’m currently working on.

Posted on May 10, 2005 in (X)HTML, Quicklinks, Web Standards


  1. May 10, 2005 by Agustin

    You might also try

  2. Huh, just use the “Validate entire site” option of the WDG HTML validator…!?

    By the way, this option is preselected if you even use’s Site Check; you just need to enter the URL and test your site.

  3. May 11, 2005 by Roger Johansson (Author comment)

    Well, what if you are working on a site that is behind a firewall, or a site that is not yet released? Or if you want to be able to control the output of the validation results? Get the results in a CSV file? There are plenty of uses for a local validator.

  4. Yeah, that’s right, but IMHO these are special cases so normally a web-based validator would suffice. And the WDG validator works quite fine.

  5. But the WDG validator is limited to a max of 100 pages. Either via the ‘Validate entire site’ option, or via the batch mode.

Comments are disabled for this post (read why), but if you have spotted an error or have additional info that you think should be in this post, feel free to contact me.