How to Fix Invalid Date Formats in Event Schema

By Ryan York•

Learn how to correct invalid date formats in your Event schema to ensure your events are properly recognized by search engines.

What is the Correct Date Format for Event Schema and How Do You Fix Errors?

Incorrect date formats in Event schema can cause errors and prevent your events from appearing in search results. This guide explains the correct formats and how to fix common mistakes.

Required Date Properties

  • startDate
  • endDate (optional, but recommended)

Correct Date Format

  • Use ISO 8601 format: YYYY-MM-DD or YYYY-MM-DDThh:mm:ss+00:00
  • Example: 2025-03-15T19:00:00-05:00

Common Mistakes

  • Using slashes instead of dashes: 03/15/2025
  • Omitting time zone: 2025-03-15 19:00:00
  • Using month names: March 15, 2025

Example of an Invalid Date

{
  "@context": "https://schema.org",
  "@type": "Event",
  "name": "Spring Gala",
  "startDate": "03/15/2025"
}

Problem: Date uses slashes and is not ISO 8601.

How to Fix

{
  "@context": "https://schema.org",
  "@type": "Event",
  "name": "Spring Gala",
  "startDate": "2025-03-15T19:00:00-05:00"
}

Best Practices

  • Always use ISO 8601 format for dates
  • Include time and time zone if possible
  • Validate your schema with Google's Rich Results Test

Conclusion

Correct date formats are essential for event visibility in search. Always use ISO 8601 and validate your schema regularly.