Skip navigation

Validating Multiple Pages on Your Blog

Building a blogValidating one web page full of code on your WordPress blog doesn’t help you find all the errors that may be hiding out among all the various pages and page views on your blog.

The W3C Canada Validator validates multiple pages on your blog, tracking down errors across the different pages and page views. You can now find errors on your front page, single post page, category pages, and more with one tool.

The W3C Multi-Page Validator uses Ajax to generate the list. You have several options for validating your blog. You can index your blog, which instructs the tool to process through the pages but only to count them, not validate them.

You can index and validate your blog’s pages, generating a report on the number of pages indexed, the number of pages with errors, number of valid pages, and the number of pages not validated.

Multiple Page Validator

Scroll down the list of red highlighted pages to find the pages with errors. Click on GO to validate a page or revalidate it. To view the errors on the page, click the number under the “Errors” column and a new page/tab/window will open with a report on errors from the W3 Markup Validation Service, which includes tips and instructions on how to validate most errors.

Multiple Page Validator Errors

It has a limit of validating 200 pages by folder. I highly recommend that you validate your blog’s design or WordPress Theme after any tweaking or updates. The sooner you can find the errors and clean them up, the better for your blog and its SEO quality control. Because WordPress only uses a few modules to generate every page on your blog, you will find that the majority of your XHTML and CSS errors within the first 20 or so page views. Fix those in your WordPress Theme template files, and it should fix the problems on most pages.

Another interesting feature is the ability to be easily add this multi-page validator to your Google Toolbar. I’d love to see it incorporated into the Web Development Tools Extension for Firefox.

It is also available in French.

Related Articles

Site Search Tags: , , , , , , , , , , , , , , , , ,
Copyright Lorelle VanFossen, member of the 9Rules Network
Feed on Lorelle on WordPress Subscribe Feedburner iconVia Feedburner Subscribe by Email

Member of the 9Rules Blogging Network


  1. Posted April 16, 2007 at 8:43 am | Permalink

    Great find Lorelle. This will definitely make my work a lot easier… I normally validate the homepage, pages and posts seperately.

  2. Posted April 16, 2007 at 11:02 am | Permalink

    Very, very handy! Good find. The most annoying part of validation is having to validate all the various kinds of pages on the site to make sure that there’s no hidden issues. This makes that much simpler.

  3. Posted April 16, 2007 at 12:26 pm | Permalink

    Thanks for the pointer: This tool revealed that a couple of the Spam Karma 2 plugins were generating invalid markup.

    One hitch I’ve found is that this validator seems to hang, well, endlessly reattempt validation for pages that aren’t found (404). It’s odd, the Stop button doesn’t appear in that case. The validator should just skip those. (I’ll drop ’em a note.)

  4. Jelle
    Posted September 28, 2008 at 5:05 am | Permalink

    Maybe, you’ll like this tool:

5 Trackbacks/Pingbacks

  1. […] writes about the W3C Multipage Validator. Validating markup of the entire site with the traditional […]

  2. […] Lorelle comenta un nuevo validador que nos permite analizar todas las páginas de nuestra web, The W3C Canada Validator hace uso del validador oficial para rastrear los posibles errores de xHTML. […]

  3. […] Lorelle nos habla de un validador que nos facilita la labor al analizar todas las páginas de nuestro blog, The W3C Canada Validator que hace uso del validador oficial W3C para analizar el sitio y dar con los posibles errores en XHTML. […]

  4. […] Validating Multiple Pages on Your Blog […]

  5. […] Validating Multiple Pages on Your Blog […]

Post a Comment

Required fields are marked *

%d bloggers like this: