Project
California Treatment Portfolio: The Technical Infrastructure Behind 125 Monthly Opportunities
AIO·GEO·Healthcare SEO·Performance Optimization·Schema & Structured Data
How multi-site schema architecture, cross-portfolio performance optimization, and AI visibility systems turned fragmented digital properties into a coordinated patient acquisition engine.
The Challenge
Multiple brands, multiple websites, zero technical coordination.
This was a portfolio problem, not a single-site problem. The organization operated several separately branded addiction treatment programs across Southern California. Each brand had its own website, its own identity, its own service mix, and its own market. Programs spanned medical detox, residential, PHP, IOP, outpatient, dual diagnosis, medication-assisted treatment, and recovery housing across six distinct geographic markets.
Every digital property had been built and managed independently. Some had real domain authority and years of traffic history. Others were newer with minimal organic presence. But across the board, the technical infrastructure was fragmented. Schema implementations were inconsistent from site to site. Some properties had auto-generated plugin defaults conflicting with manually injected JSON-LD. Others had no structured data at all. Google couldn’t establish verified entity relationships for any of the brands, let alone connect them to the parent organization.
Performance profiles varied wildly. Some properties loaded in under 2 seconds. Others took 6+ with unmanaged third-party scripts, unoptimized images, and no caching strategy. CallTrackingMetrics, Google Tag Manager, analytics scripts, chat widgets, and captcha implementations were configured differently on every site, with no standardized approach to script loading priority.
The result: roughly 45 qualified opportunities per month across an entire portfolio of California treatment brands. For organizations with this much combined domain authority, that number should have been three to four times higher. The infrastructure was the bottleneck.
Before Engagement:
- ~45 qualified opportunities per month across the portfolio
- Multiple sites with competing keyword targets and cannibalization
- Inconsistent schema across properties — no connected entity architecture
- No multi-location schema connecting individual facilities to parent organization
- Performance inconsistency — some sites at 2s load, others at 6+
- Third-party scripts unmanaged across every property (CTM, GTM, hCaptcha, chat)
- Zero AI search presence across any platform
Our Technical Approach
Rebuilding the infrastructure layer across every property in the portfolio.
Our role was the technical foundation: schema architecture, site performance, crawlability, structured data, and AI visibility across every property. Impact Dynamics led portfolio strategy, content development, keyword ownership mapping between brands, multi-brand positioning, and the admissions coordination that connected search visibility to patient acquisition. Here’s what we built:
Phase 1: Multi-Site Technical Audit
We audited every property independently before doing any cross-portfolio work. Each site got a full technical assessment: crawlability analysis, Core Web Vitals baseline measurement, schema inventory documenting every source of structured data and where implementations conflicted, internal link architecture mapping, redirect chain identification, and indexation health through Google Search Console.
The audit revealed that each site had been built with different themes, different plugin stacks, and different technical configurations. WP Rocket was installed on some properties but misconfigured on all of them. Rank Math was present on most but generating default schema that varied by theme. Some sites had manually injected JSON-LD in header/footer code that conflicted with the plugin output. The technical debt was site-specific, but the patterns repeated across the portfolio.
Phase 2: Multi-Location Schema Architecture
This was the most technically complex work in the engagement. Each brand needed a verified entity identity that Google and AI platforms could trust independently, while also connecting to the parent organization’s authority. We built a connected entity system using @graph/@id methodology:
MedicalBusiness entities per brand
Each property got its own MedicalBusiness typing with facility-specific address, geo-coordinates, phone, and credential markup. No generic Organization fallbacks.
hasCredential per facility
State licensing, accreditation, and program-specific certifications deployed on the correct properties only. A facility’s credentials were never claimed by a different brand.
MedicalClinic schemas per location
Individual facility schemas with areaServed properties targeting the specific California markets each one actually served: Greater Los Angeles, San Fernando Valley, Ventura County, Thousand Oaks, Coachella Valley, and Palm Springs.
Service-level schemas
Treatment program structured data (Medical Detox, Residential, PHP, IOP, Outpatient, Dual Diagnosis, MAT) deployed only on properties that actually offered those services. The schema matched the clinical truth, not a marketing aspiration.
Geographic entity disambiguation
Wikipedia sameAs URLs on every areaServed property so search engines could unambiguously identify which California cities and regions each facility served.
Rank Math as single authoritative source
All competing schema implementations were audited and deleted. Custom schema was built through Rank Math’s editor on every property, eliminating the header/footer code conflicts the audit identified.
Phase 3: Cross-Portfolio Performance Optimization
Performance work had to be site-specific in execution but consistent in standard across the portfolio. We established baseline performance targets and then optimized each property to meet them:
WP Rocket configuration standardized across all properties — caching, file optimization, JavaScript delay/defer settings customized per site for their specific plugin stacks
Third-party script audit and prioritization on every property — CTM, GTM, analytics, chat widgets, and form validation scripts categorized by load priority (immediate, delayed, conditional)
CTM exclusion patterns configured so dynamic number insertion loaded on first render while non-critical scripts were delayed
Core Web Vitals optimization — LCP through hero image preloading, INP through JavaScript deferral, CLS through image dimensioning and font loading
Cross-site consistency established so no single property dragged down the portfolio’s quality signals
Phase 4: AI Search Visibility
With the technical foundation in place across all properties, we configured each site for AI retrievability:
Content structure optimization on every property — summary-first paragraphs, query-aligned headers, citation-ready formatting
Robots.txt configured for 10+ AI crawlers on every site — OpenAI, Anthropic, Google, Perplexity, Microsoft, Meta
Connected entity architecture gave AI systems verifiable signals about which organization operated which facilities, what credentials each held, and what services each provided
Cross-platform monitoring across Google AI Overviews, ChatGPT, Perplexity, and Gemini for the full portfolio
The Results
From 45 to 125. From fragmented sites to a coordinated growth system.
The technical infrastructure we built was the layer that made portfolio-level growth possible. Content strategy, brand positioning, keyword ownership mapping, and admissions coordination by Impact Dynamics could only produce results because every property in the portfolio was now technically sound, consistently performant, properly structured for entity verification, and visible to both traditional search engines and AI platforms.
// BY THE NUMBERS
Results that speak for themeseves.
The Results
Organic Search Scale:
Two major properties alone grew to over 116,000 estimated monthly organic visits while ranking for more than 23,000 combined keywords. One focused initiative produced a 500% organic growth spike in its first two weeks, revealing how much market opportunity had been left uncaptured when the infrastructure wasn’t there. These figures represent two measured properties in the portfolio — the organization’s full multi-site footprint is larger.
Qualified Opportunity Growth:
Monthly qualified opportunities grew from approximately 45 to 125 — a 178% increase and roughly 2.8x the previous volume. This wasn’t traffic for its own sake. The portfolio strategy connected visibility to actual patient acquisition pathways, and the technical infrastructure ensured those pathways worked: pages loaded fast, schema verified entity credentials, internal links moved authority deliberately, and AI platforms could identify and cite the right facility for the right query.
Admissions:
The organization achieved 32 admissions in a single month. An admission represents someone who moved through the entire digital and clinical decision journey — from initial discovery through research, trust evaluation, contact, qualification, and into treatment. That number is the only one that matters commercially.
AI Search Visibility:
Properties began appearing in AI-generated responses for treatment-related queries across their respective California markets. The connected entity architecture gave platforms like Google AI Overviews and ChatGPT verifiable signals about each brand’s identity, credentials, location, and services — the kind of structured trust data that AI systems use when deciding which sources to cite.
Technical Highlights
The specific infrastructure that made the difference.
| Technical Work | Outcome |
|---|---|
| Multi-Site Technical Audit | Full infrastructure assessment across all portfolio properties, documenting per-site technical debt and cross-portfolio patterns |
| Multi-Location Schema Architecture | MedicalBusiness + MedicalClinic entities with @graph/@id linking, unique credential markup per facility |
| Geographic Entity Mapping | areaServed schemas for 6 California regions mapped to correct facilities with Wikipedia sameAs disambiguation |
| Service-Level Schema | Treatment program schemas deployed only on properties that actually offered each service |
| Schema Conflict Resolution | All competing plugin/theme/manual JSON-LD implementations audited, deleted, and rebuilt from single source (Rank Math) |
| Cross-Portfolio Performance | WP Rocket, script management, and CWV optimization standardized across all properties |
| Third-Party Script Management | CTM, GTM, analytics, chat, and captcha scripts audited and load-prioritized per site |
| AI Crawler Configuration | Robots.txt configured for 10+ AI platforms on every property in the portfolio |
| Content Structure Optimization | Summary-first paragraphs, query-aligned headers, and citation-ready formatting across all sites |
What Made the Difference
Portfolio-level technical infrastructure, not site-by-site band-aids.
A collection of websites and a coordinated digital portfolio are different things. The websites existed before we got involved. What didn’t exist was the technical layer that made them work as a system: consistent schema architecture that established verified entities across every property, standardized performance that met the same quality threshold on every site, deliberate internal linking that moved authority where it mattered, and AI visibility configuration that gave every property a path into emerging search channels.
The 500% growth spike that happened in the first two weeks of one initiative wasn’t a fluke. It was market demand that had been there all along, trapped behind infrastructure that couldn’t capture it. The technical foundation unlocked what the content strategy could reach.
A Partnership Approach
This was a joint engagement. Impact Dynamics led the portfolio strategy: which brand should own which keyword lanes, how to build content that reinforced each property’s identity without creating duplication, how to connect informational authority to commercial treatment pathways, and how to translate search visibility into actual admissions through opportunity tracking and conversion optimization.
Slacker SEO led the technical infrastructure: multi-site schema architecture with @graph/@id entity relationships, cross-portfolio performance standardization, crawlability and indexation management, AI crawler configuration, and the structural systems that search engines and AI platforms use to verify, trust, and cite sources.
The results required both. Strategy without infrastructure hits a ceiling. Infrastructure without strategy doesn’t know where to point. The portfolio grew because both layers were built in alignment.
