RankpediaA plain-English encyclopedia of search

Google Microformat

Adds machine-readable semantics to HTML content using existing markup patterns, helping search engines identify entities like people, events, and products.

If you have ever expected markup alone to improve rankings without meeting rich-result requirements, you already know the format matters less than validity.

Key points

  • Use JSON-LD for new implementations; Google recommends it for ease of maintenance.
  • Validate all markup with Google's Rich Results Test before expecting any search appearance change.
  • Do not confuse microformats with microdata; they are separate HTML standards.
  • Check feature-specific documentation: markup alone does not guarantee rich results if properties are incomplete.

A bakery's hours that never appeared

A local bakery marks up its opening hours using hCalendar microformat on its rich content page. Google's Rich Results Test shows no errors, but the hours never appear in search snippets. The bakery switches to JSON-LD with Schema.org's OpeningHoursSpecification, and within a week the hours show in local results. The markup was valid, but Google's rich-result features require specific Schema.org properties, not legacy microformat vocabularies.

Three ways it goes wrong

  • Wrong term Calling microdata or JSON-LD 'microformat' confuses discussions but has no direct SEO impact. It wastes time in team conversations and can lead to incorrect assumptions about format support.
  • Expecting ranking boost Markup alone does not improve rankings; it only enables eligibility for rich results. A page with perfect structured data can still rank poorly if content quality or relevance is lacking.
  • Ignoring feature requirements Legacy microformat vocabularies often yield no visible enhancement without checking Google's current rich-result docs. Each feature has specific property and format requirements that must be met exactly.

Three things to check before implementing

  • Validate with Rich Results Test Run Google's Rich Results Test to confirm markup is detected and error-free. This tool also shows which rich results are eligible, saving you from guessing whether your implementation works.
  • Use Schema.org vocabulary Google's structured data features are built on Schema.org; legacy microformats may not be supported. Sticking to Schema.org ensures compatibility with current and future rich-result types.
  • Prefer JSON-LD Google recommends JSON-LD as the easiest format for schema implementation and maintenance. It keeps markup separate from HTML, reducing the risk of errors and simplifying updates.

Common questions

What is the difference between microdata and JSON-LD?

Microdata embeds properties in HTML attributes; JSON-LD uses a separate script block. Google recommends JSON-LD for simplicity.

What is JSON-LD used for in SEO?

JSON-LD provides structured data in a script tag, enabling rich results like recipes, events, and reviews.

Sources

  1. Google Search Central: Intro to How Structured Data Markup Works Official Google documentation on structured data formats.
  2. MDN Web Docs: Using microdata in HTML Technical reference for microdata syntax.
  3. Microformats Wiki: Introduction to Microformats Community resource explaining microformat principles.
↑