Sail JADA — Engineering Log

Technical work on sailjada.com and the JADA booking systems

```html

Injecting Structured Data Into Concert Event Pages: A Multi-Site Schema Implementation

During this development session, we tackled a critical SEO and discoverability problem across our event subdomain infrastructure: 12 concert event pages were completely lacking Schema.org structured data. This meant search engines couldn't parse event details, venue information, or booking availability—leaving significant organic search potential untapped. Here's how we solved it systematically across our distributed site architecture.

The Problem: Missing Structured Data Across Event Subdomains

Our event infrastructure spans multiple subdomains (event1.paulsimonradyshell.com, event2.paulsimonradyshell.com, etc.), each with individual concert pages. An audit revealed:

  • Zero structured data on any event detail pages
  • 12 active event pages across multiple subdomains without Event or LocalBusiness schema
  • No rich snippets in search results, despite having legitimate review data (63 Google reviews at 4.9★ rating)
  • Inconsistent head tag structure across dynamically generated pages

This is a classic infrastructure problem: we had beautiful brand assets and legitimate business data, but zero machine-readable distribution of that information to search engines.

Technical Solution: Custom Structured Data Injection Script

Rather than manually editing each page, we built a Python script to inject JSON-LD structured data programmatically. The script lives at:

/Users/cb/Documents/repos/tools/inject_structured_data.py

The script performs these operations:

  • Scans target directories for HTML files lacking Event schema
  • Parses event metadata from filename conventions and page structure
  • Generates valid Event + LocalBusiness JSON-LD blocks
  • Injects the schema into the <head> section before the closing tag
  • Preserves existing Google Analytics and meta tags without duplication
  • Writes updated files back to source directories

The key architectural decision: we use JSON-LD (not microdata or RDFa) because it's the least intrusive injection method. JSON-LD blocks can be appended to the head without modifying existing DOM structure, reducing the risk of breaking page rendering.

Infrastructure: Multi-Subdomain S3 + CloudFront Deployment

After injecting structured data locally, we deployed updated pages to production across our event subdomain infrastructure:

  • Event subdomain buckets: Individual S3 buckets for each event subdomain (paulsimonradyshell.com events), confirmed via AWS CLI listing
  • Deployment method: AWS S3 sync with selective paths for event pages only
  • Cache invalidation: CloudFront distribution IDs identified for each subdomain, with invalidation patterns targeting all updated event pages

Exact deployment flow:

aws s3 sync /path/to/updated/events s3://event-subdomain-bucket/events/ --exclude "*" --include "*.html"
aws cloudfront create-invalidation --distribution-id DISTRIBUTION_ID --paths "/events/*"

We also deployed a new referral partner brief template to the main QOS site at:

/Users/cb/Documents/repos/sites/queenofsandiego.com/notes/referral_partner_brief_template.html

And created a Ranch & Coast promotional redirect page deployed to sailjada.com:

/Users/cb/Documents/repos/sites/sailjada.com/ranch-and-coast.html

Key Decisions & Why They Matter

1. Why JSON-LD over microdata? We standardized on JSON-LD across all properties because it's Google's preferred format, requires zero DOM modification, and works reliably in dynamically generated pages. Our event pages are rendered by Python templating systems (render_event_sites.py), making JSON-LD insertion trivial: just append a <script type="application/ld+json"> block to the head template.

2. Separate injection script vs. template changes? We wrote a standalone injection tool rather than modifying the page generators directly (render_event_sites.py and generate_service_area_pages.py) because:

  • Existing pages already live in production without schema—they need immediate retrofitting
  • The injection script is reusable across multiple template systems and site properties
  • Template changes require regression testing across all generated pages; injection is surgical and reversible
  • Future template updates can include schema generation natively, but this unblocks immediate SEO gains

3. Why CloudFront invalidation instead of waiting for TTL? Concert event pages have time-sensitive content (ticket availability, dates). Waiting 24 hours for TTL expiration risks stale data in search results. We invalidated immediately post-deployment to ensure search engine crawlers see updated schema on their next visit.

Additional Infrastructure Updates

During this session, we also:

  • Injected Google Analytics tracking into 9 pages missing instrumentation across multiple sites (quickdumpnow.com, queenofsandiego.com, dangerouscentaur)
  • Added analytics to dynamically generated pages by updating template injection points in render_event_sites.py and generate_service_area_pages.py
  • Created an email popup component at /Users/cb/Documents/repos/sites/sailjada.com/assets/js/email-popup.js to capture contacts from the 3,676-person email list asset we're underutilizing
  • Updated the progress dashboard to track CMO initiatives and channel-specific visibility improvements

What's Next

The structured data injection is a tactical win, but the strategic opportunity lies ahead:

  • OTA Platform Integration: Event schema now being generated; next step is listing concert events on Eventbrite, Ticketmaster, and similar platforms to drive discovery
  • Email List Activation: The 3,676 verified contacts in our email system should be segmented and engaged with upcoming events via automated campaigns
  • Google Business Profile Optimization: GBP exists but isn't fully leveraged; we need to populate event listings and drive review generation
  • Template-Level Schema Generation: Update render_event_sites.py and generate_service_area_pages.py to generate schema natively, eliminating the need for post-injection retrofits on new pages

The infrastructure is now in place to measure impact: Google Search Console will show impressions for event schema, and we can track organic traffic attribution to venue + event structured data improvements over the next 4-6 weeks as search engines recrawl and update their indices.

```