Event Schema Generator

Build Event markup locally and use the JSON-LD validator as pre-publish QA rather than a search-feature certification.

Event name

Organizer

Description

Start date/time

End date/time

Attendance

Venue name

Street

City

Region

Postal code

Country

Online/ticket URL

Image URL

ReadyOutput is generated locally in your browser.

Structured data is not a rich-result guaranteeUse markup only for content that is visible and true on the page. Google eligibility also depends on feature-specific rules, content policies, crawlability, and validation after deployment.

Event Schema Generator: Eligibility & JSON-LD Audit

Audit Event JSON-LD for required and recommended fields, date ordering, attendance-mode location rules and URL/image readiness.

Complete Event schema workspace

Add ticket, status, organizer URL and performer fields that are often needed in a real event publishing workflow, then rebuild the JSON-LD above with readiness evidence.

StatusOrganizer URLPerformerPerformer typeTicket priceCurrencyAvailabilityValid fromTicket URL

0/3Core fields

0/6Recommended evidence

—Ticket offer

Generate the base event above, then complete the optional publishing fields here.

Search-engine boundaries

Local markup checks cannot know what a crawler fetched, rendered, indexed or selected as canonical. Search engines may rewrite title links/snippets, choose different canonicals, ignore invalid or ineligible structured data, and apply live HTTP/robots conditions that are not present in pasted text. Treat these tools as pre-publish QA, then verify live behavior with the relevant search-engine tools.

Schema.org Event and Google Event are not identical

The generator preserves valid Schema.org attendance modes, while the publication preflight distinguishes current Google event-search requirements from general Schema.org markup.

Practical guide and verification

Markup must match visible event content

Structured data should describe the same event details that visitors can see on the page. Adding ticket prices, performers or status only to JSON-LD while hiding or contradicting them in the visible page can make the markup misleading.

Attendance mode determines location requirements

In-person events need a physical Place and address, online events need a VirtualLocation URL, and mixed events can require both. Review the attendance/location evidence before publishing rather than relying on syntactically valid JSON alone.

Keep event status current

Scheduled, postponed, cancelled, moved-online and rescheduled states communicate materially different information. Update eventStatus when circumstances change, and keep dates and visible notices synchronized with the markup.

Ticket data should describe a real offer

Price, currency, availability, valid-from date and ticket URL belong to an actual offer. Use zero for a genuinely free event where appropriate rather than inventing a price solely to fill a recommended property.

Validate the deployed page separately

The complete-schema workspace can check field presence and internal consistency locally. Search engines still decide eligibility based on their current documentation, the rendered page, crawlability, policies and the structured data they actually fetch.