{
    "schema_version": "1.0",
    "slug": "aimedicinetoday-com",
    "domain": "aimedicinetoday.com",
    "generated_date": "2026-07-15",
    "updated_at": "2026-07-15",
    "data_sources": [
        "config/site.json",
        "config/federation.json",
        "CLAUDE.md",
        "BUILD_BRIEF.md",
        "ai/health.json",
        "content directory counts"
    ],
    "confidence": "verified-facts-only",
    "identity": {
        "niche": "Public-understanding AI-in-medicine authority hub (distinct from clinical-adoption sibling aimedicinenow.com)",
        "constellation_slug": "healthcare-ai-longevity",
        "tier": "supporting",
        "priority": "3",
        "property_format": "Content hub: 5 articles, 8 category hubs, 10 specialty pages, 4 pages (17 total public items per ai/health.json)",
        "launch_stage": "Built, live",
        "for_sale": false
    },
    "executive_summary": {
        "headline": "Tracking the Future of Medicine, One Algorithm at a Time",
        "one_liner": "Research, analysis, tools, and practical insights on how artificial intelligence is changing diagnosis, treatment, clinical research, and modern medical practice.",
        "summary": "aimedicinetoday.com splits the AI-in-medicine topic with two siblings: aimedicinenow.com owns clinical adoption, aihealthcarenow.com is the flagship covering industry/business, and this site covers the broader/public-facing angle. It has 17 total public items (5 articles, 8 category hubs, 10 specialty pages, 4 pages) and a 4-phase monetization roadmap (authority-building, traffic/lead-capture, revenue, premium membership) with no dates attached. Notably, this site's config/federation.json contains no tier/priority/node_role or portfolio_listing fields at all, tier/priority ('Supporting/3') is documented only in CLAUDE.md, so its federation status can't be assessed as stale or current the way most other sites in this rollout can."
    },
    "traffic_seo": {
        "monthly_traffic": null,
        "traffic_trend": "Not documented. ai/health.json shows sitemapPresent: false despite deploy/generate-sitemap.php existing, a real gap: the sitemap generator exists but hasn't been run or wired up.",
        "domain_authority": null,
        "digital_karma_score": 0.6999999999999999555910790149937383830547332763671875,
        "karma_signals": [],
        "target_queries": [],
        "notes": "digital_karma_score of 0.7 comes from ai/karma.json (this site lacks the full federation.json signals block most siblings have)."
    },
    "monetization": {
        "status": "pre-revenue, 4-phase plan",
        "monthly_revenue": null,
        "revenue_streams": [
            {
                "stream": "Phase 1: Authority",
                "mechanism": "Evergreen explainers, specialty hubs, structured data, AI-ready summaries",
                "timeline": "not stated",
                "status": "in progress (content exists)"
            },
            {
                "stream": "Phase 2: Traffic/lead capture",
                "mechanism": "Newsletter, AI medicine briefing signup, physician AI tool checklist, vendor comparisons",
                "timeline": "not stated",
                "status": "named only"
            },
            {
                "stream": "Phase 3: Revenue",
                "mechanism": "Display ads, sponsored clinical AI reports/vendor explainers, affiliate revenue, lead gen for medical AI vendors, cross-referrals to medmarketingdr.com/aihealthcarenow.com",
                "timeline": "not stated",
                "status": "named only"
            },
            {
                "stream": "Phase 4: Premium",
                "mechanism": "'AI Medicine Pro' membership (weekly briefings, specialty updates, FDA-cleared AI tracker, vendor database, tool comparisons)",
                "timeline": "not stated",
                "status": "named only"
            }
        ],
        "notes": "4 clearly sequenced phases, currently sitting in Phase 1 based on content that exists."
    },
    "growth_opportunities": [
        {
            "opportunity": "Wire up the sitemap generator that already exists",
            "impact": "medium",
            "effort": "low",
            "notes": "deploy/generate-sitemap.php exists but ai/health.json confirms sitemapPresent: false, a quick fix relative to most gaps found in this rollout."
        },
        {
            "opportunity": "Add the missing federation.json fields (tier, priority, node_role, portfolio_listing)",
            "impact": "low",
            "effort": "low",
            "notes": "This site is one of only two found in this rollout (with aihealthcarenow.com) missing the standard portfolio_listing section entirely, worth a deliberate federation-schema alignment pass."
        },
        {
            "opportunity": "Move into Phase 2 (traffic/lead capture)",
            "impact": "high",
            "effort": "medium",
            "notes": "Content-authority phase already has 17 items; next step per the site's own roadmap is newsletter and lead-capture infrastructure."
        }
    ],
    "risk_factors": [
        {
            "risk": "Missing sitemap despite the generator existing",
            "severity": "low",
            "mitigation": "Confirmed via ai/health.json; a config/deploy step away from being fixed, not a content gap."
        },
        {
            "risk": "Federation config missing standard fields",
            "severity": "low",
            "mitigation": "Same gap as aihealthcarenow.com in this rollout, an older/incomplete config shape rather than a stale value."
        },
        {
            "risk": "Easily confused with two similarly-scoped siblings",
            "severity": "medium",
            "mitigation": "CLAUDE.md already documents the intended split: this site = public understanding, aimedicinenow.com = clinical adoption, aihealthcarenow.com = industry/business."
        }
    ],
    "sale": {
        "asking_price": 24970
    },
    "maker_notes": "This site's config/federation.json lacks tier/priority/node_role/portfolio_listing entirely, the same structural gap found on aihealthcarenow.com earlier in this rollout, suggesting a subset of properties were scaffolded from an older federation.json template before the portfolio_listing convention was standardized. Worth a dedicated pass to align these to the current schema alongside the separate stale-status-value issue found on most other sites."
}