Sail JADA — Engineering Log

Technical work on sailjada.com and the JADA booking systems

Diagnosing Multi-Property GA/GSC Cross-Contamination: QDN Ownership & Tag Placement Audit

We discovered a critical ownership and tagging issue across our multi-property portfolio while investigating GSC sitemap submissions for QuickDumpNow (QDN). This post documents the audit methodology, findings, and remediation strategy.

The Problem: What the Screenshot Revealed

A Google Search Console screenshot showed QDN's property being accessed via jadasailing@gmail.com — the JADA (SailJada) business account. While this seemed like cross-contamination at first glance, the real issue was more nuanced: GA and GSC ownership did not match QDN's operational email (admin@quickdumpnow.com). This creates operational friction and security risk.

Audit Scope & Methodology

We needed to answer three questions:

  • Are GA tracking IDs actually cross-polluted (same tag on different properties)?
  • If tags are separate, are they placed correctly on all pages (homepage + subpages)?
  • Who owns each property in Google Analytics and Search Console?

Step 1: Homepage GA Tag Inventory

We systematically fetched each property's homepage and extracted the GA tag from the <script> tag in the document head.

sailjada.com           → G-N6HKL4KLKT (JADA business)
queenofsandiego.com    → G-N6HKL4KLKT (JADA business — same tag, same owner ✓)
quickdumpnow.com       → G-539T97NM1Z (QDN — different tag ✓)
dangerouscentaur.com   → G-GGP987FJSW (DC — different tag ✓)
86from.com             → G-YJWFKWVWNQ (86FROM — different tag ✓)
burialsatseasandiego.com → UA-175171552-1 (legacy Universal Analytics — outdated ⚠)

Finding: Homepages were clean. JADA properties share one tag (intentional), QDN has its own.

Step 2: Subpage GA Tag Coverage Scan

The real risk is tag placement gaps on inner pages. We scanned QDN subpages that receive traffic:

/book
/track
/service-areas/carlsbad/
/service-areas/oceanside/

Initial shell-based loop (bash subprocess calls in a sandbox environment) hit restrictions. We switched to Python for direct HTTP requests and regex parsing:

#!/usr/bin/env python3
import requests
import re
from urllib.parse import urljoin

base_url = "https://quickdumpnow.com"
subpages = ["/book", "/track", "/service-areas/carlsbad/"]
qdn_tag = "G-539T97NM1Z"

for page in subpages:
    url = urljoin(base_url, page)
    try:
        resp = requests.get(url, timeout=10)
        if qdn_tag in resp.text:
            print(f"✓ {page}: GA tag present")
        else:
            print(f"✗ {page}: GA tag MISSING")
    except Exception as e:
        print(f"✗ {page}: Error fetching ({e})")

Finding: Pages /book, /track, and /service-areas/carlsbad/ were missing the QDN GA tag entirely. This means QDN traffic on those pages isn't being tracked in its own analytics property.

Step 3: GSC & Analytics Ownership Verification

We inspected the GSC property list for QDN. It showed ownership by jadasailing@gmail.com, not admin@quickdumpnow.com. The same applied to GA4 property G-539T97NM1Z.

Key insight: This isn't tag contamination—it's account ownership misalignment. QDN's analytics properties live under the JADA Google Workspace account, not QDN's own account.

Why This Matters

  • Operational Isolation: QDN team can't independently manage their GSC or GA settings without going through JADA account holders.
  • Data Governance: If JADA and QDN ever separate (business split, contractor exit, acquisition), GA/GSC data becomes entangled.
  • Tracking Gaps: Missing tags on high-traffic subpages means incomplete analytics for QDN's most critical user journeys (booking, tracking).
  • Legacy Debt: burialsatseasandiego.com still uses deprecated Universal Analytics (UA-175171552-1), which Google stopped processing in July 2023.

Remediation Strategy

Immediate Actions (High Priority)

  1. Transfer QDN GSC Property Ownership: Add admin@quickdumpnow.com as owner on the QDN Search Console property. This requires browser-based GSC UI access and verification (5 min, browser-only).
  2. Transfer QDN GA4 Property: Add admin@quickdumpnow.com with Editor role on GA4 property G-539T97NM1Z (Analytics > Admin > Account Access Management).
  3. Audit & Deploy Missing GA Tags on QDN Subpages: Add G-539T97NM1Z to head tags on /book, /track, and all /service-areas/* pages. This typically lives in a shared header template (e.g., _layout.html, header.jsx, or a CMS global block).

Medium-Term (Operational Cleanup)

  • Migrate burialsatseasandiego.com from UA-175171552-1 to GA4 (Google stopped processing UA data in 2024).
  • Document property ownership rules in a shared RACI matrix (who owns what, when access transfers happen).
  • Set up quarterly audits to catch tag placement gaps on new pages.

Kanban Cards Created

We documented findings in two cards:

  • t-77babced (updated): GSC sitemap submission workflow, with notes on GA/GSC ownership misalignment discovery.
  • New card: "QDN ownership transfer" — transfer GA4 + GSC to admin@quickdumpnow.com.
  • New card: "QDN GA tag coverage gaps" — deploy G-539T97NM1Z to missing subpages.

Key Decisions

Why we didn't flag this as "cross-contamination": The GA tags themselves are isolated (separate Google Analytics