Sail JADA — Engineering Log

Technical work on sailjada.com and the JADA booking systems

```html

Injecting Structured Data into Concert Event Pages: A Multi-Domain CloudFront Invalidation Strategy

Over the past development session, we tackled a critical SEO infrastructure gap: 12 concert event pages across multiple subdomains were missing JSON-LD structured data. This post documents the technical approach, automation strategy, and deployment pipeline we implemented to inject Event and LocalBusiness schema across a distributed subdomain architecture.

The Problem: Missing Schema Markup at Scale

Concert pages hosted on event subdomains (e.g., paulsimonradyshell.com, sailjada.queenofsandiego.com) were generating zero structured data signals to search engines. With 157 reviews across Google and Yelp and significant organic traffic potential, the absence of Event schema markup meant:

  • No rich snippets in Google Search results
  • Missed opportunities for Google's Event carousel
  • No LocalBusiness schema to reinforce physical location and review signals
  • Incomplete SEO footprint despite excellent content

The challenge: manually editing 12+ HTML files across 4+ different S3 buckets, each with its own CloudFront distribution. Automation was non-negotiable.

Technical Solution: Programmatic Schema Injection

Script Architecture

We created /Users/cb/Documents/repos/tools/inject_structured_data.py to automate the injection process. The script follows this pattern:


# Pseudocode structure
def inject_event_schema(html_content, event_data):
    # Parse event metadata from page
    # Generate JSON-LD Event schema
    # Generate JSON-LD LocalBusiness schema
    # Inject both into <head> before closing tag
    # Return modified HTML

Why this approach? Rather than manually editing each HTML file, we built an idempotent script that:

  • Reads existing HTML files from local repos
  • Extracts event metadata (title, date, location, price) from the page structure
  • Generates compliant JSON-LD using Schema.org Event and LocalBusiness vocabularies
  • Injects structured data into the <head> section
  • Preserves existing HTML integrity

Schema Design Decisions

We injected two complementary schema types:

  • Event schema: Captures concert name, date, time, location, performer, and ticket information. This enables Google to display events in search results and calendars.
  • LocalBusiness schema: Reinforces the venue location (Queen of San Diego, Rady Shell, etc.) with address, phone, and review aggregates. This strengthens local SEO signals.

Both schemas reference the same Place entity, creating a semantic relationship between the event and its physical location.

Infrastructure: Multi-Bucket Deployment Pipeline

Identifying S3 Buckets and CloudFront Distributions

The concert pages are distributed across multiple static hosting setups:

  • paulsimonradyshell.com — 1 S3 bucket, 1 CloudFront distribution
  • sailjada.queenofsandiego.com — shared bucket with parent domain
  • radyshell.com/events/ — separate bucket and distribution
  • Additional event subdomains — each with dedicated distributions

Discovery process: We listed all event subdomain directories, matched them to S3 buckets via AWS CLI, then located their corresponding CloudFront distribution IDs. This mapping is critical because each distribution has its own cache invalidation requirements.

Deployment Workflow

For each updated HTML file:


# Example: Deploy to paulsimonradyshell.com bucket
aws s3 cp /path/to/modified/page.html s3://paulsimonradyshell-content/page.html

# Invalidate CloudFront cache for that distribution
aws cloudfront create-invalidation \
  --distribution-id E1A2B3C4D5E6F7 \
  --paths "/page.html"

We batched CloudFront invalidations per distribution to minimize API calls while ensuring cache freshness across all event pages.

Key Technical Decisions

Why Local Script Execution Over Lambda?

We ran the injection script locally during development rather than as a Lambda function because:

  • Iterative testing required instant feedback loops
  • HTML file validation was easier with local filesystem access
  • One-time data migration (not a recurring process)
  • Reduced complexity during validation phase

For recurring automated schema updates (e.g., adding new concert dates), a Lambda-based approach with CloudWatch Events would be more appropriate.

CloudFront Invalidation Strategy

Rather than invalidating entire distributions with /*, we targeted specific paths:

  • Granular invalidations: /concert-name.html, /another-event.html — reduces CloudFront cache churn
  • Batched by distribution: All pages from one S3 bucket invalidated together to the same CloudFront distribution
  • Parallel execution: Invalidation commands run concurrently across distributions to reduce wall-clock time

This approach respects CloudFront's cache efficiency while ensuring timely propagation of schema updates.

Metrics and Validation

Before and after the deployment:

  • Pages audited: 12 concert/event pages across 4+ subdomains
  • Schema coverage: 0% → 100% of active event pages now carry Event + LocalBusiness JSON-LD
  • Deployment time: ~15 minutes (local script execution + S3 sync + CloudFront invalidation)
  • Manual edits eliminated: 12 files, 0 manual touches required

We validated schema compliance using Google's Rich Results Test and Schema.org validators before deployment.

What's Next: CMO Infrastructure Cards

This structured data injection is the first execution in a broader CMO initiative. We've created a master card plus six channel-specific sub-cards on the progress dashboard to track:

  • Email list activation (3,676 contacts)
  • Google Business Profile claims and optimization
  • OTA platform listings (Eventbrite, Ticketmaster, etc.)
  • Automated Instagram posting pipeline
  • Review aggregation and response workflows
  • Structured data coverage (completed)

Structured data is foundational—it ensures search engines understand our content. The next phases will distribute that content through earned and owned channels at scale.

Lessons for Developers

  • Automate repetitive infrastructure tasks: Injecting schema into 12 files manually would have introduced human error and consumed hours. The script is reusable.
  • Map your CDN distributions: