NewLeaf Recovery — Track C · SEO Foundation Build

Map Pack ranking is the biggest SEO lever for this client given GBP-centric search patterns in healthcare. Optimize accordingly.

LOCKED — Don't quote differently

• Keyword tiers per A1 addendum (2026-05-21) — Tier A (Lansing direct ~30/mo), Tier B (near-me national, geo-filtered to ~10/mo Lansing real), Tier C (topical authority), Tier D (per-city long-tail).
• 21 indexable URLs — each gets full on-page optimization (Workstream 2).
• DataForSEO hyperlocal pull complete (2026-05-21) — canonical row keyword_research.id = newleaf-recovery-2026-05-21-hyperlocal in Supabase.
• 8 workstreams scope — Keyword Architecture, On-Page SEO, Internal Linking, External Linking (citations + aggregators), Schema Markup, Technical SEO, CRO Foundation, AI Overview/Generative Search.
• Per-CMS-item content uniqueness ≥60% — your linking strategy and schema generation must handle this dynamically.
• Citation campaign volume: 50–75 business listings in 3 tiers.
• Data aggregator push: Data Axle, Localeze, Foursquare, Factual.

FLEXIBLE — Your professional judgment

• Specific schema entity @id URI patterns.
• Internal linking exact-match anchor variations per page.
• Per-CMS-item dynamic schema generation approach (Velo code patterns).
• AI Overview content patterns (which sentence structures to push).
• Citation campaign sequencing within tiers.
• Tool selection where alternatives exist (BrightLocal vs Yext vs manual citations).

Workstream 1 — Keyword Architecture & Mapping

• Primary keyword per page (no cannibalization — no two pages share a primary keyword).
• 5–10 secondary keywords per page (semantic cluster).
• Search intent classification per page (informational, navigational, commercial, transactional).
• Monthly volume + difficulty + CPC per keyword (from DataForSEO).
• Competitive ranking landscape per primary keyword (who currently ranks 1–10).
• Target ranking position + timeline per keyword.
• Priority tier (which pages first to optimize for what).
• Cannibalization risks identified + resolved.
• Sources: DataForSEO research pull (already in Supabase), manual SERP review, Google Keyword Planner cross-reference.

Locked Keyword Tiers (per A1 addendum)

Workstream 2 — On-Page SEO Implementation

• Title tag (60 char max, primary keyword in first 50 chars, brand at end).
• Meta description (155 char max, compelling, CTA-driven, keyword present).
• H1 (one per page, primary keyword present naturally).
• H2/H3 hierarchy aligned with semantic intent + secondary keywords.
• URL slug optimized (short, keyword-present, no stop words).
• Image alt text descriptive + keyword-aligned where natural.
• Image file names descriptive + keyword-aligned.
• Body copy keyword density + LSI keyword presence verified.
• Internal link placement per Workstream 3.
• External outbound links to authoritative sources (SAMHSA, NIDA, ASAM cited where relevant).
• Open Graph + Twitter Card meta tags.
• Canonical URL specified.
• robots meta directives where appropriate.

Workstream 3 — Internal Linking Strategy & Implementation

• MAT (Suboxone) page = primary conversion hub. Every service area CMS page links to it with anchor variations.
• Each service area CMS page also links to Counseling + Case Management with city-specific anchor variants (CMS-driven via Velo).
• Lansing — Downtown Clinic page = geographic hub. Links to all 12 service area pages.
• Services Overview links to all 4 dedicated service pages with primary-keyword anchors.
• Home features curated links to MAT, About, Insurance with high-conversion anchor text.
• Footer site-wide links to legal/compliance with nofollow on Terms/Privacy.
• Breadcrumb navigation on every non-home page.
• Anchor text variation library — exact-match, partial-match, branded, generic, contextual variants per primary keyword. Prevents over-optimization while maximizing relevance.
• Implementation — hand-built pages: manual link placement. CMS service area pages: dynamic generation via Velo code reading CMS fields, emitting links with correct anchor variations per city.

Workstream 4 — External Linking Foundation (Off-Page)

• Citation campaign — 50–75 business listings across 3 tiers (below).
• Data aggregator push to Data Axle, Localeze, Foursquare, Factual — feeds hundreds of secondary directories + GPS + voice assistants.
• NAP consistency audit — Name/Address/Phone IDENTICAL byte-for-byte across every citation, footer, schema, structured data.
• Initial high-authority profile creation — LinkedIn Company, Facebook Business, Crunchbase, BBB, Chamber of Commerce.
• Healthcare directory positioning — SAMHSA Behavioral Health Treatment Services Locator (FREE, federal, high-authority), state licensing directory verification.
• Backlink prospect list — 50–100 targets for FUTURE ongoing outreach (recovery publications, Lansing-area community orgs, healthcare partner referral relationships, alumni newsletters).
• Ongoing link earning is separate retainer.

Citation Campaign — Tier breakdown

Data aggregator cost: typically $0–$300 one-time per aggregator + annual maintenance. Quote in your budget.

Workstream 5 — Schema Markup Architecture

Entity relationship linking via @id: Every schema entity gets a unique @id URI; entities reference each other via those IDs. Examples — MedicalBusiness on home has @id: "https://newleafrecoveryservices.com/#organization". Each Physician references the organization: "worksFor": {"@id": "...#organization"}. Each MedicalProcedure references organization + location: "provider": {"@id": "..."}, "areaServed": {"@id": "...#lansing-location"}. Service area CMS pages dynamically generate Place entities referencing back to Lansing location.

CMS dynamic schema generation: For 12 service area dynamic pages, schema generated via Velo code reading CMS field values and emitting valid JSON-LD per dynamic URL. Each city generates Place schema with @id: "https://newleafrecoveryservices.com/service-area/[city]/#place"; references to providing organization + location; areaServed properties on parent organization schema dynamically populated.

Validation: Every schema block validated via Google Rich Results Test + Schema.org validator before launch.

Workstream 6 — Technical SEO

• XML sitemap properly generated, all 21 URLs incl. dynamic CMS, submitted to GSC + Bing.
• robots.txt configured (block staging, allow production).
• Canonical tag strategy — self-referential per page; CMS dynamic correctly generated.
• Hreflang — N/A unless multilingual (Add-On 5 in Track A).
• Core Web Vitals — LCP, FID, CLS verified post-launch (image optimization in Track A).
• Mobile-first indexing readiness — every page renders correctly on mobile.
• HTTPS implementation — SSL active, no mixed content, HSTS configured.
• 404 handling — custom branded 404 page.
• 301 redirect strategy — staging-to-production map documented.
• Crawl budget optimization.
• Page speed: Lighthouse mobile ≥85, TTI <3.5s on 3G.
• JavaScript rendering — verify Google can render CMS dynamic pages correctly (Wix Studio is SSR by default; verify).
• Structured data testing — all schema validates via Rich Results Test.
• Indexability audit — GSC URL Inspection on every priority page post-launch.

Tools Provisioned + Configured (Workstream 6)

Workstream 7 — Conversion Rate Optimization Foundation

• Conversion path mapping — every visitor path to inquiry documented.
• Primary CTA hierarchy — every page: clear primary (intake form), secondary (phone), tertiary (resource access).
• Form placement strategy — header, inline on Home + Service pages, footer, dedicated Contact page. Always 1 click away.
• Phone number prominence — sticky on mobile, prominent in header desktop, click-to-call site-wide.
• QR code positioning — Contact page (cross-references bus campaign + printed collateral).
• Trust signals layered — owner story, mission, insurance accepted, compliance badges, professional credentials, GBP review widget.
• Friction reduction on intake form — only 4 fields, mobile keyboard optimization, instant validation.
• Form confirmation flow — what happens after submit (SMS handoff to Behave portal via GHL — Track E).
• A/B test scaffolding — Microsoft Clarity for session recording; framework to identify friction after 30 days.
• Conversion event firing — every form submission, phone click, QR scan → GA4 + GHL with proper attribution.

Foundational Tracking — every conversion measured

Workstream 8 — AI Overview & Generative Search Optimization

Google's AI Overviews now appear above traditional results for the majority of healthcare queries. This is part of NewLeaf's premium positioning.

• Question-and-answer content patterns — every service page has structured FAQ with concise extractable answers (1–3 sentence answers). FAQs marked with FAQPage schema.
• "What is" / "How does" / "Who can" sentence patterns prominent in opening paragraphs — patterns AI extractors lift directly into AI Overview citations.
• Entity-rich language — canonical entity names (Suboxone, buprenorphine, MAT, opioid use disorder, 42 CFR Part 2) for clear topical entity identification.
• Author + expertise signals (E-E-A-T) — provider bios include credentials, training institutions, years of experience, board certifications; pages cite SAMHSA, NIDA, ASAM; medical content reviewed by clinical staff.
• Structured data for AI — schema markup (W5) directly feeds AI models.
• Conversational query patterns — content written for how patients actually phrase questions ("can I get Suboxone if I'm pregnant", "does Medicaid cover MAT in Michigan", "what's the difference between Suboxone and methadone").
• Citation-worthy content blocks — short, factual, defensible statements AI models can extract + attribute.
• ai_keyword_volume data pull from DataForSEO — identifies queries getting heavy AI Mode traffic.
• AI Overview monitoring setup — track which NewLeaf pages get cited (using llm_mentions_search from DataForSEO + manual SERP review).
• Anti-hallucination signals — clear date stamps, clear authorship, citation of medical sources.

You DELIVER to:

You RECEIVE from:

1. Scope Summary

Briefly restate the scope as you understand it. If you understand it differently than the scope file, flag it here. (Your 3–5 sentence restatement.)

2. Hours / Cost Quote by Workstream

3. Add-On / Optional (each independent)

4. Citation Campaign Detail

Per-tier hours + cost. Some directories charge listing fees; quote those as pass-through.

5. Schema Markup Detail

How many hours per schema type? Which require Velo code? How does dynamic CMS schema generation work in your approach?

6. AI Overview Optimization Detail (Workstream 8)

How will you approach AI Overview optimization? Specifically: question-and-answer patterns, entity-rich language strategy, E-E-A-T author/expertise infrastructure, ai_keyword_volume + llm_mentions_search monitoring setup, anti-hallucination signals. If new to W8, flag learning curve in hours.

7. Timeline

8. Dependencies — What You Need From Us

Brand approval + signed contract, final Lansing address (citations gate), Insurance carriers (Insurance page schema), GHL form embed (for conversion event firing), Track A's CMS Velo code structure (for dynamic schema generation), Tamesha-supplied provider credentials + headshots (for Physician schema + E-E-A-T).

9. Risk Flags — What YOU See

Be honest. Examples: "Wix Studio CMS Velo schema generation has X gotcha — adds Y hours". "AI Overview optimization for healthcare YMYL requires deeper E-E-A-T than I've delivered before — quote +30% on W8 to learn it right". "Citation campaign Tier 2 healthcare directories have ZocDoc / WebMD acceptance variability — pass-through fees uncertain until applications submit". Be bulleted, specific, actionable.

10. Anything Else

Open field. Tell us what we missed.

Return to chad@creativepartnersolutions.com. Subject: "NewLeaf Track C Quote — [Firm name]". By submitting this quote, [Firm name] confirms: we have read the scope + keyword strategy + README in full; the scope as quoted matches our understanding; we can meet July 1 Phase 1 SEO + August 31 Phase 2 (or flag in §7); we understand W8 (AI Overview) familiarity expectations; we will sign a white-label agreement (NewLeaf does not know we exist).