EVENTODIT.
EDITABLE WORK DOCUMENT

Event information and structured-data comparison

Compare the session register, public page and search data; record code tests and indexing separately.

Audience recruitment and promotion
WHAT THIS TEMPLATE HELPS YOU PREPARE

A handover record of URL discrepancies, changes and post-release checks

File formats
English XLSX · CSV (UTF-8)
Version
2.0
Editorial review
31 Oct 2026
Use this for
Use for first publication and changes to session dates, venue, price, availability, cancellation or postponement.

When to use it

Use for first publication and changes to session dates, venue, price, availability, cancellation or postponement.

Check supported countries and languages first. Passing a code test is not indexing or rich-result approval. Compare example status values with current implementation guidance.

Start with the guide: Event search and structured-data review

Fill in the template step by step

When to use it

Complete before publishing an event detail page and after changes to dates, venue or sales conditions.

What to have ready

  • Approved session register and change approvals
  • Public URLs and structured-data versions
  • Supported region/language and data-type checks
  • Code tests and available Search Console or access results

  1. Link the session ID, unique URL and approved register version.

  2. Compare date, venue, price and availability for the same session across page and data.

  3. Recheck access and code using the corrected version.

  4. Record release time and later indexing; report actual search performance separately.

Worked example

Fictional example, not an actual event or supplier record

Eight columns · scroll horizontally to view the complete worked example.

Event information and structured-data comparison — fictional worked example
Session ID and detail URLApproved register and versionPublic-page checkStructured-data checkDifference and correctionAccess and code testRelease and indexingStatus, owner and deadline
EV-S1 / https://example.test/s1R01-v2 / planning approval A0111-12 14:00–16:00 / H1 / booking openJSON01-v2 / same date, venue and availabilityNo difference / QA01Crawl allowed; no test errors T01Released 11-01 15:00 / indexing unknownImplementation checked / search lead / recheck indexing 11-03
EV-S2 / https://example.test/s2R02-v3 / cancellation approval A02Cancellation notice updatedJSON02-v2 retains old availabilityJSON v3 correction requiredDo not reuse test results from before change—Hold / web lead / correct and retest by 11-01 16:00
EV-S3 / https://example.test/s3R03-v2 / postponed, new date unknownPostponement and date-pending noticeOriginal start retained; EventPostponed checkedNo invented date or midnight / QA03Access and code tests T03 checkedReleased 11-01 17:00 / recrawl pendingHanded over / planning / recheck when new date agreed
EV-S4 / https://example.test/s4R04-v1 / event approval A04Date, venue and price match QA04Matches JSON04-v1No differenceT04 passes; unintended noindex remainsIndexing blockedRelease correction / web lead / fix access and recheck by 11-02 10:00

Blank template preview

This preview shows a few rows. The downloaded file contains 24 prepared rows.

Eight columns · scroll horizontally to view the complete blank worksheet.

Event information and structured-data comparison — blank worksheet
Session ID and detail URLApproved register and versionPublic-page checkStructured-data checkDifference and correctionAccess and code testRelease and indexingStatus, owner and deadline
————————
————————
————————

Check your completed template

  • Page, data and approved register differences are checked.
  • Changed code and access settings were tested.
  • Release, indexing and outstanding owners and deadlines are distinct.

What to pass to the next person

Web sends revised versions and test results to marketing, and release/indexing follow-up to the search lead.

Check before using this template

The register guarantees neither search visibility nor policy approval. Check official support and actual indexing separately.

Sources used to develop this template

EVENTODIT created this template using the working methods described in the public sources below. It is not an official form and has not been reviewed or approved by those organisations.