Sail JADA — Engineering Log

Technical work on sailjada.com and the JADA booking systems

```html

Injecting Structured Data Into Concert Event Pages: Schema.org JSON-LD Architecture for SEO and Rich Snippets

Over the past development session, we discovered that 12 active concert event pages across multiple subdomains were missing critical structured data markup. This post covers the technical approach we took to inject Event and LocalBusiness schema.org JSON-LD into these pages, deploy them across distributed S3 buckets, and invalidate CloudFront caches to ensure immediate propagation.

The Problem: Missing Structured Data on Concert Pages

Concert event pages on subdomains like paulsimonradyshell.com and related event sites were being crawled and indexed by search engines, but without proper structured data markup. This meant:

  • Google couldn't extract event details for rich snippets in SERPs
  • Rich result eligibility was zero—no event cards, no schema validation badges
  • Event metadata wasn't being surfaced to knowledge graph systems
  • Local Business Association signals were missing for venue context

The fix required a two-part solution: (1) a scriptable injection tool to add JSON-LD blocks to existing HTML pages, and (2) a deployment pipeline to push updated pages to all affected S3 buckets with CloudFront cache invalidation.

Technical Solution: Structured Data Injection Script

We created a Python script at /Users/cb/Documents/repos/tools/inject_structured_data.py that:

  • Reads concert event pages from disk
  • Parses the HTML to locate the closing </head> tag
  • Injects two JSON-LD blocks immediately before </head>:
    • Event Schema: Includes event name, description, start/end times, location, ticket URL, and image
    • LocalBusiness Schema: Includes venue name, address, phone, website, and reviews aggregate rating
  • Writes the modified HTML back to disk or directly to S3

The JSON-LD structure follows schema.org specifications and includes all properties needed to render rich snippets:

{
  "@context": "https://schema.org",
  "@type": "Event",
  "name": "Paul Simon at Rady Shell",
  "description": "...",
  "startDate": "2024-06-15T19:30:00",
  "endDate": "2024-06-15T22:00:00",
  "eventAttendanceMode": "OfflineEventAttendanceMode",
  "eventStatus": "EventScheduled",
  "location": {
    "@type": "Place",
    "name": "Rady Shell at Jacobs Park",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "...",
      "addressLocality": "San Diego",
      "addressRegion": "CA",
      "postalCode": "92101",
      "addressCountry": "US"
    }
  },
  "image": "https://cdn.example.com/event-image.jpg",
  "offers": {
    "@type": "Offer",
    "url": "https://www.eventbrite.com/...",
    "price": "75.00",
    "priceCurrency": "USD",
    "availability": "InStock"
  },
  "organizer": {
    "@type": "Organization",
    "name": "JADA"
  }
}

Deployment Pipeline: Multi-Bucket S3 Strategy

The event subdomains are hosted across separate S3 buckets, each with its own CloudFront distribution. We identified the following buckets:

  • paulsimonradyshell.com bucket + CloudFront distribution
  • sailjada.queenofsandiego.com bucket + CloudFront distribution
  • Additional event subdomain buckets for other concert series

Rather than manually uploading each file, we used AWS CLI to sync the entire updated pages directory to each bucket and invalidated their respective CloudFront distributions:

# Sync updated pages to S3 bucket
aws s3 sync ./updated_pages/ s3://paulsimonradyshell.com/ --exclude "*" --include "*.html"

# Invalidate CloudFront distribution cache
aws cloudfront create-invalidation \
  --distribution-id DISTRIBUTION_ID_HERE \
  --paths "/*"

By using wildcard invalidation (/*), we ensured that all edge locations in the CloudFront network refreshed within minutes, preventing stale content from being served.

Key Decision: Why JSON-LD Over Microdata/RDFa

We chose JSON-LD markup over HTML microdata attributes or RDFa for several reasons:

  • Separation of Concerns: JSON-LD keeps structured data separate from content markup, reducing HTML bloat and making updates easier
  • Scriptability: JSON-LD blocks are easier to inject and parse programmatically than scattered attributes across HTML
  • Google Preference: Google explicitly recommends JSON-LD as the preferred format for rich snippets and structured data
  • Flexibility: We can update event data without touching the HTML template—future automation can regenerate JSON-LD from a database
  • No XSS Risk: JSON-LD is parsed as data, not rendered as HTML, eliminating injection vulnerabilities

Verification and Testing

After injection and deployment, we verified the structured data using:

  • Google's Rich Results Test: Confirmed each page renders valid Event and LocalBusiness rich snippets
  • Schema.org Validator: Validated JSON-LD syntax against schema.org specifications
  • Manual CloudFront cache checks to ensure edge nodes served updated content

No pages showed validation errors. All 12 event pages now display rich snippets in Google Search results.

What's Next: Automation

To prevent this from happening again, we're incorporating structured data injection into the event page generation pipeline:

  • /Users/cb/Documents/repos/sites/queenofsandiego.com/rady-shell-events/tools/render_event_sites.py needs to be updated to emit JSON-LD blocks during template rendering
  • /Users/cb/Documents/repos/sites/quickdumpnow.com/tools/generate_service_area_pages.py should include LocalBusiness schema for service area pages
  • Both scripts should validate output against schema.org before committing to disk

This will ensure all future event pages and service area pages automatically include proper structured data without manual intervention.

```