{
    "schema_version": "1.0",
    "slug": "medmarketingdr-com",
    "domain": "medmarketingdr.com",
    "generated_date": "2026-07-15",
    "updated_at": "2026-07-15",
    "data_sources": [
        "config/site.json",
        "config/federation.json",
        "docs/medmarketingdr_php_json_build/README.md",
        "docs/content-plan.md",
        "content/ directory counts",
        "CLAUDE.md"
    ],
    "confidence": "verified-facts-only",
    "identity": {
        "niche": "Medical marketing / SEO for doctors and specialist practices",
        "constellation_slug": "professional-growth-markets",
        "tier": "flagship",
        "priority": "1",
        "property_format": "Authority/lead-gen site: 13 pages, 6 articles, research/services index collections",
        "launch_stage": "Built, partially through its own content roadmap (13 of ~24 planned niche pages live)",
        "for_sale": false
    },
    "executive_summary": {
        "headline": "Doctor-focused medical marketing authority site, flagship of the Professional Growth Markets constellation",
        "one_liner": "Medical Marketing for Doctors in the AI Search Era, helping practices gain visibility in Google, AI search, local search, and patient discovery systems.",
        "summary": "medmarketingdr.com positions itself explicitly as not a hospital marketing agency, not a generic SEO company, not a healthcare SaaS platform, and not a broad marketing blog, a doctor-specific niche play. It has 13 of a planned ~24 niche pages live plus 6 research articles, but no priced offer: the only live commercial mechanism is a mailto lead-capture link on an AI Visibility Assessment page. Six named service lines exist as marketing categories without stated pricing."
    },
    "traffic_seo": {
        "monthly_traffic": null,
        "traffic_trend": "Not documented. Marketing plan references Google Search Console showing doctor-intent query terms being tested, but no numeric values are given anywhere.",
        "domain_authority": null,
        "digital_karma_score": 0.7199999999999999733546474089962430298328399658203125,
        "karma_signals": {
            "schema_coverage": 0.8000000000000000444089209850062616169452667236328125,
            "content_freshness": 0.8000000000000000444089209850062616169452667236328125,
            "ai_endpoints": 0.9499999999999999555910790149937383830547332763671875,
            "federation_presence": 0.9499999999999999555910790149937383830547332763671875,
            "external_links": 0.75,
            "technical_quality": 0.81999999999999995115018691649311222136020660400390625,
            "dataset_quality": 0.7800000000000000266453525910037569701671600341796875
        },
        "target_queries": [],
        "notes": "docs/content-plan.md defines Primary/SEO/AI Search/Specialty content clusters as the intended query-targeting strategy, but no specific keyword list or session numbers exist in a machine-readable form."
    },
    "monetization": {
        "status": "lead-gen only, no priced offer",
        "monthly_revenue": null,
        "revenue_streams": [
            {
                "stream": "AI-native medical marketing assessment",
                "mechanism": "mailto lead capture (krisadaseo@gmail.com)",
                "timeline": "live",
                "status": "no price stated"
            }
        ],
        "notes": "Six service-line categories exist (Medical SEO, AI Search Optimization, Local Practice Visibility, Medical Content Strategy, Website Conversion Architecture, Structured Data Implementation) but function as marketing taxonomy, not priced offers. No retainer, project fee, or ad-revenue figures exist anywhere in config, docs, or content."
    },
    "growth_opportunities": [
        {
            "opportunity": "Finish the planned content roadmap",
            "impact": "high",
            "effort": "medium",
            "notes": "13 of ~24 planned niche pages are live per docs/content-plan.md's Primary/SEO/AI Search/Specialty clusters; the gap is already scoped, just not built."
        },
        {
            "opportunity": "Replace the mailto CTA with a real lead form",
            "impact": "medium",
            "effort": "low",
            "notes": "README's own 'Priority Build Order' step 8 ('Add lead form or CTA routing') is listed as not yet implemented beyond the mailto link."
        },
        {
            "opportunity": "Attach pricing to at least one of the 6 named service lines",
            "impact": "high",
            "effort": "medium",
            "notes": "Currently every service line is unpriced positioning copy; converting even one into a priced package (similar to aiwebsitesystems.com's tiered offer model) would give this site its first real monetization mechanism beyond a contact link."
        }
    ],
    "risk_factors": [
        {
            "risk": "No priced offer exists, only a lead-capture email link",
            "severity": "high",
            "mitigation": "Highest-priority gap: six service lines are marketed but none are packaged or priced, so there's no self-serve path to revenue yet."
        },
        {
            "risk": "Content roadmap roughly half-finished",
            "severity": "medium",
            "mitigation": "Scoped and documented already in docs/content-plan.md; remaining build is planning work, not strategy work."
        },
        {
            "risk": "Explicit brand-positioning tightrope",
            "severity": "low",
            "mitigation": "Marketing plan explicitly warns against reading as a hospital agency, generic SEO shop, healthcare SaaS platform, or broad marketing blog ... any future page or CTA copy should be checked against that list before publishing."
        }
    ],
    "sale": {
        "asking_price": 44970
    },
    "maker_notes": "Known portfolio-wide pattern flagged during this rollout: config/federation.json's portfolio_listing.status here also says \"domain-only\" despite the site being built with 13 live pages and 6 articles. Not corrected here without Krisada's explicit per-site go-ahead, see aidigitalkarma-com.json's maker_notes for the full context on why this wasn't batch-fixed."
}