Queen of San Diego — Tech Blog

Under the hood at queenofsandiego.com

```html

Multi-Property GA & GSC Audit: Fixing Cross-Contamination and Ownership Transfer on Four Distinct Domains

What Was Done

During a routine production incident investigation on sailjada.com, we discovered a critical infrastructure issue: multiple distinct web properties (sailjada.com, queenofsandiego.com, quickdumpnow.com, dangerouscentaur.com, 86from.com, and burialseasandiego.com) were being managed under a single Google account identity (jadasailing@gmail.com), creating analytics ownership and compliance risk. Additionally, the audit revealed that quickdumpnow.com—a separate business entity—had missing GA instrumentation on critical inner pages, and its Google Search Console property was accessible only through JADA's account rather than its own admin account.

This post documents the systematic audit methodology, findings, remediation strategy, and infrastructure changes required to properly segment these properties by ownership.

Technical Details: The Audit Process

GA Tag Inventory Across All Properties

We began by scanning the homepage and representative subpages of each property to catalog GA implementations:

# Verification commands (no sensitive output)
curl -s https://sailjada.com/ | grep -o 'gtag\|G-[A-Z0-9]*'
curl -s https://queenofsandiego.com/ | grep -o 'gtag\|G-[A-Z0-9]*'
curl -s https://quickdumpnow.com/ | grep -o 'gtag\|G-[A-Z0-9]*'

Findings by Property:

  • sailjada.com (homepage + /crew/, /faqs/): GA property G-N6HKL4KLKT (JADA measurement)
  • queenofsandiego.com (homepage + all subpages): GA property G-N6HKL4KLKT (same JADA measurement—intentional; same business entity)
  • quickdumpnow.com (homepage): GA property G-539T97NM1Z (QDN-specific measurement)
  • quickdumpnow.com (/book/, /track/, /service-areas/carlsbad/): MISSING GA tag entirely
  • dangerouscentaur.com: GA property G-GGP987FJSW
  • 86from.com: GA property G-YJWFKWVWNQ
  • burialsataseasandiego.com: Legacy UA-175171552-1 (deprecated Universal Analytics)

Subpage Scanning Strategy

To detect cross-contamination at scale, we built a Python scanner that:

  1. Listed all S3 objects under each domain's origin bucket
  2. Filtered for index.html files (representing subpage entry points)
  3. Extracted the GA measurement ID from each document's <script> tags
  4. Compared against the expected canonical GA ID for that domain
  5. Flagged mismatches (cross-contamination) and absences (missing instrumentation)

For sailjada.com specifically, we audited 16 depth-1 subpages in S3 (e.g., s3://sailjada-prod/crew/index.html, s3://sailjada-prod/faqs/index.html) and found consistent GA tagging with no cross-contamination.

For quickdumpnow.com, the scan revealed 3 critical inner pages missing the QDN GA tag:

  • /book/index.html
  • /track/index.html
  • /service-areas/carlsbad/index.html

Infrastructure & Account Ownership Issues

The Root Problem: GSC Property Ownership

When we checked Google Search Console for quickdumpnow.com, we found that the property was registered and verified under jadasailing@gmail.com, not under admin@quickdumpnow.com. This creates three operational problems:

  1. Access Control: QDN's administrator cannot directly manage its own search console property.
  2. Data Isolation: Search performance and indexing insights are mixed with JADA's account, complicating analytics separation.
  3. Audit Trail: Ownership and responsibility become ambiguous if the JADA account is ever compromised or revoked.

Why GA Tags Are Distinct But Ownership Is Unified

Google Analytics and Google Search Console operate independently:

  • GA tags are JavaScript measurement properties embedded in page source—they can be owned by any Google account that has access to the Google Analytics property.
  • GSC properties are site ownership records—they must be verified and managed by someone with legitimate authority over the domain (via DNS, sitemap, or HTML verification).

In this case, both the GA property G-539T97NM1Z (for QDN) and the GSC property for quickdumpnow.com are accessible via jadasailing@gmail.com because that account was used to set them up originally. However, they should be owned by QDN's own admin account to enforce proper separation of duties.

Remediation Plan & Kanban Cards

We created two kanban cards in the development backlog:

Card 1: QDN Ownership Transfer (Browser-Based, ~15 min)

  • Task: Transfer GSC property ownership from jadasailing@gmail.com to admin@quickdumpnow.com
  • Steps:
    1. Sign in to Google Search Console as jadasailing@gmail.com
    2. Navigate to quickdumpnow.com property settings
    3. Add admin@quickdumpnow.com as an owner
    4. Switch to admin@quickdumpnow.com account and accept ownership transfer
    5. Remove jadasailing@gmail.com from the property
    6. Verify ownership is now exclusive to QDN's admin account
  • Why: Ensures QDN can independently manage its search visibility and analytics without dependency on JADA's account.

Card 2: Missing GA Tags on QDN Inner Pages (Code Deploy, ~30 min)

  • Affected files:
    • quickdumpnow.com/book/index.html (S3 key: s3://quickdumpnow-prod/book/index.html)
    • quickdumpnow.com/track/index.html (S3 key: s3