general purpose validators
The following validators will validate multiple microformats on a page:
Optimus microformats transformer and validator is a microformats transformer and validator that supports numerous microformats including hCard 1.0, hCalendar 1.0, hReview 0.4 (in progress), hAtom 0.1 (note: hAtom validation issues).
== Optimus validator is not working for the moment == Therefore any page you will check through will return the message: "Microformats at this page have no errors. Congratulations." which is a false message. We will update this message when (and if) Optimus will work again.
Please add issues to the optimus-issues page.
Bing Markup Validator
The Bing Markup Validator tests for various microformats support, including hCard 1.0, hCalendar 1.0, and others. Note: 2012-02-03 launch announcemnt: Bing Webmaster Center blog: Webmaster Tools Markup Validation Tool
Google Rich Snippets Testing Tool
The Google Rich Snippets Testing Tool can parse several microformats from a given URL and produces reports showing errors and a preview of what properties it detects. It supports a subset of properties on some microformats, however is continuously updated with more support.
browser microformat readers
Microformats for Google Chrome automatically detects most of the common microformats as you browse. Microformats: hCard 1.0, hCalendar 1.0, hReview 0.4 (in progress), hReview-aggregate 0.2, hRecipe 0.22, Geo
specific microformats validators
- The unofficial hCard Validator
- It's open-source and contributions are welcome! Please join the project and extend it to support more microformats.
Operator does a good job of compliant parsing for microformats in general, and includes a debug mode that can help identify errors in the structure.
There has been a suggestion to host an "official" microformats validator at microformats.org.
- hCard validator is open-source (BSD-licensed) and extensible enough to support other microformats (it's mostly a matter of hooking up XSLT templates that extract microformat data and find errors). The codebase is pretty clean, UI is internationalized.
Who wants to help make this happen, and what do you need?