Tygart Media

Category: Martech & Analytics

You cannot improve what you do not measure, and most restoration companies are flying blind. CRM, call tracking, attribution, dashboards — the marketing technology stack is what separates companies that scale from companies that guess. We cover the tools, integrations, and data strategies that give restoration operators real visibility into what is working and what is burning money.

Martech and Analytics covers marketing technology stack architecture, CRM implementation, call tracking, attribution modeling, Google Analytics, dashboard creation, data visualization, conversion rate optimization, and marketing operations for restoration contractors and commercial services businesses.

  • The Fractional AI Optimization Partner: What It Is, How It Works, and Why It Beats Hiring

    The Fractional AI Optimization Partner: What It Is, How It Works, and Why It Beats Hiring

    The Machine Room · Under the Hood

    You Do Not Need a Department. You Need a Partner.

    The traditional agency growth model says: identify a capability gap, hire people to fill it, build a team, develop the service, sell it. This model works when the capability is well-established and the talent pool is deep. It fails when the capability is emerging, the talent pool is thin, and the methodology is evolving faster than any single hire can keep up with.

    AEO and GEO are emerging capabilities. The talent market is almost nonexistent — there are no universities producing AEO graduates and no certification programs for GEO. The methodology changes with every Google algorithm update and every new AI platform feature. Hiring a specialist today means hiring someone whose knowledge may be outdated in six months without continuous learning and experimentation.

    The fractional model solves this. Instead of hiring, you partner with a firm whose entire business is AEO and GEO. They invest in methodology development, tool building, and continuous experimentation because that is their core competency. You get the output of that investment without the overhead of maintaining it internally. Your clients get cutting-edge capability. Your agency gets margin without headcount risk.

    How the Fractional Model Works in Practice

    The fractional AI optimization partner operates like a fractional CFO or fractional CMO, but for a specific technical capability. They are not on your payroll. They are not in your office. They are a dedicated resource allocated to your agency’s client work on a retainer or per-client basis.

    Operationally, the partner provides four things. Strategic direction — what to optimize, in what order, for what expected outcome, based on a proprietary methodology refined across dozens of client engagements. Technical execution — schema implementation, AI citation monitoring, entity optimization, and LLMS.txt deployment. Quality assurance — reviewing the content enhancement work your team produces to ensure it meets the methodology standards. And methodology updates — as the AEO/GEO landscape evolves, the partner updates the playbook and retrains your team.

    The partner attends your internal planning meetings for relevant clients. They contribute to client strategy sessions when invited. They produce deliverables that go to the client under your brand. But they are not your employee — they are a specialized firm that provides capability on demand.

    The Economics of Fractional vs. Full-Time

    A full-time AEO/GEO specialist costs ,000 to ,000 per year in salary, plus benefits, equipment, training, and management overhead. Total loaded cost: ,000 to ,000 per year. That specialist can handle 8 to 12 client accounts depending on scope. Cost per client: to ,400 per month.

    A fractional partner charges ,200 to ,500 per client per month depending on scope. More expensive per-client than a loaded full-time cost. But: zero hiring risk, zero ramp time, zero benefits cost, zero management overhead, no training investment, and the ability to scale up or down instantly as your client portfolio changes.

    The breakeven point is typically around 10 to 12 active clients. Below that, the fractional model is cheaper than hiring. Above that, a hybrid model — one in-house specialist plus a fractional partner for overflow and specialized work — often produces the best economics. At a certain portfolio size, the in-house team may be more cost-effective, but even large agencies benefit from maintaining a fractional relationship for methodology updates and specialized projects.

    What to Look for in a Fractional Partner

    The partner must have a documented, repeatable methodology — not just individual expertise. You need to be able to train your team from their playbook, review their work against standards, and maintain consistency across clients. If the methodology lives in one person’s head, you have a contractor, not a partner.

    The partner must have cross-industry experience. AEO and GEO tactics vary by vertical — what works for a SaaS company differs from what works for a local service business. A partner who has only optimized one type of client will struggle to adapt their methodology to your diverse client base.

    The partner must be willing to work under your brand. White-label delivery is the default for fractional partnerships. If the partner insists on co-branding or direct client access, the model does not work for most agencies.

    The partner must provide reporting in your format. Deliverables that require reformatting before client presentation create unnecessary overhead. The right partner delivers work that is client-ready within your reporting framework.

    Starting the Relationship

    The smart way to start is a pilot engagement. Choose two to three clients with strong SEO foundations and high AI search opportunity. Run the fractional partner’s methodology on those clients for 90 days. Measure the results — featured snippet wins, AI citation appearances, client satisfaction. If the pilot produces results, expand to additional clients. If it does not, you have risked three months and a few thousand dollars instead of a six-figure hire.

    The pilot also gives your team supervised exposure to the AEO/GEO methodology. By the end of 90 days, your content team will have learned the core techniques through hands-on practice, which accelerates the eventual transition to the hybrid model where your team handles most of the work and the partner provides oversight and technical execution.

    FAQ

    How much time does a fractional partner need from the agency team?
    A few hours per week in coordination — reviewing deliverables, discussing strategy, and aligning on client priorities. This is substantially less than managing a full-time employee.

    Can you use a fractional partner for just a few clients?
    Yes. The fractional model scales down as easily as it scales up. Starting with a small group of clients is the recommended pilot approach. There is no minimum commitment beyond the individual client retainers.

    What is the typical contract structure?
    Month-to-month per-client retainers are most common. Some partners offer discounted rates for annual commitments or volume tiers. Avoid long-term lock-in contracts until the relationship is proven through a successful pilot.

    {
    “@context”: “https://schema.org”,
    “@type”: “Article”,
    “headline”: “The Fractional AI Optimization Partner: What It Is, How It Works, and Why It Beats Hiring”,
    “description”: “The fractional partner model gives SEO agencies full AEO and GEO capability at a fraction of the cost and risk of hiring dedicated specialists.”,
    “datePublished”: “2026-03-21”,
    “dateModified”: “2026-04-03”,
    “author”: {
    “@type”: “Person”,
    “name”: “Will Tygart”,
    “url”: “https://tygartmedia.com/about”
    },
    “publisher”: {
    “@type”: “Organization”,
    “name”: “Tygart Media”,
    “url”: “https://tygartmedia.com”,
    “logo”: {
    “@type”: “ImageObject”,
    “url”: “https://tygartmedia.com/wp-content/uploads/tygart-media-logo.png”
    }
    },
    “mainEntityOfPage”: {
    “@type”: “WebPage”,
    “@id”: “https://tygartmedia.com/the-fractional-ai-optimization-partner-what-it-is-how-it-works-and-why-it-beats-hiring/”
    }
    }

    Further Reading

  • Schema at Scale: How to Implement Structured Data Across 50 Client Sites Without a Dedicated Dev Team

    Schema at Scale: How to Implement Structured Data Across 50 Client Sites Without a Dedicated Dev Team

    Tygart Media / The Signal
    Broadcast Live
    Filed by Will Tygart
    • Tacoma, WA
    • Industry Bulletin

    Schema Is the Bottleneck Nobody Talks About

    Every SEO agency knows schema markup matters. Most agency SEO teams can explain what Article schema and Product schema do. Very few can actually implement it at scale across a portfolio of 20, 30, or 50 client sites with different CMS platforms, different themes, different hosting environments, and different levels of client-side technical access.

    The implementation gap is the dirty secret of agency SEO. The audit identifies schema opportunities. The recommendation deck says “implement FAQ schema.” And then the recommendation sits in a Google Doc for six months because nobody on the team has the technical bandwidth to write, validate, and deploy JSON-LD across dozens of pages — let alone across dozens of clients.

    This bottleneck is especially damaging for AEO and GEO because schema is not optional for these layers. FAQPage schema explicitly declares answer content for snippet extraction. Speakable schema marks content for voice readback. Entity schema builds the knowledge graph signals that AI systems use for citation decisions. Without schema, your AEO and GEO optimization is structurally incomplete.

    The Template Approach

    Schema at scale starts with templates, not custom code. Build a library of JSON-LD templates for the most common schema types across your client portfolio. Article and BlogPosting schema for content pages. Product schema for e-commerce. LocalBusiness schema for local clients. FAQPage schema for any page with Q&A content. Organization schema for about pages. Person schema for author pages. BreadcrumbList schema for navigation.

    Each template includes all required and recommended properties with placeholder variables that map to common CMS fields. The title maps to the post title. The author maps to the post author. The datePublished maps to the publication date. The description maps to the excerpt. The image maps to the featured image URL. When a content team member enhances a page for AEO, they fill in the template variables from the page’s existing metadata and the schema is ready to deploy.

    The template library eliminates the blank-page problem. Nobody needs to write schema from scratch. They need to populate a template that has already been validated against Google’s Rich Results requirements.

    CMS-Specific Deployment

    WordPress is the most common CMS in agency portfolios, and it has the most schema deployment options. For sites where you have theme access, add schema templates to the theme’s header.php or use a functions.php filter to inject JSON-LD programmatically based on post type and category. For sites where you use Yoast or Rank Math, these plugins generate basic schema automatically — but they typically produce only Article schema and miss FAQ, Speakable, and entity schema types. Supplement plugin-generated schema with custom JSON-LD blocks in the post content or through a custom field.

    For non-WordPress sites — Shopify, Squarespace, Wix, custom-built — the deployment method varies but the schema code is identical. JSON-LD lives in a script tag in the page head. How it gets there depends on the platform’s template system. Document the deployment method for each platform you encounter so the team does not re-solve the same problem for every client.

    Validation at Scale

    Individual page validation uses Google’s Rich Results Test — paste the URL, review the results, fix errors. This works for one page. It does not work for 500 pages across 30 clients. Scale validation requires a systematic approach.

    Site-level validation: use a crawler configured to check for JSON-LD presence and basic structural validity on every indexed page. Flag pages with missing schema, invalid schema, or schema types that do not match the page content. Run this crawl monthly for every client site.

    Spot-check validation: each month, manually validate 3 to 5 pages per client through the Rich Results Test. Focus on recently enhanced pages and pages with new schema types. This catches issues that crawl-based validation may miss — like valid schema that contains incorrect data.

    Cross-client reporting: maintain a schema health dashboard that shows schema coverage by client — what percentage of indexable pages have valid schema, which schema types are deployed, and which types are missing. This dashboard gives your team a portfolio-wide view of schema health and highlights the clients that need attention.

    The Schema Stacking Strategy

    Most agency implementations deploy one schema type per page — typically Article schema. This captures basic SEO value but misses the AEO and GEO benefits of stacked schema. A properly optimized content page should have four to five schema types simultaneously: Article schema for the content metadata. BreadcrumbList schema for navigation. FAQPage schema for any Q&A sections. Speakable schema for voice-ready content blocks. And Person schema for author attribution.

    Stacking schema types on a single page is technically simple — multiple JSON-LD script blocks coexist without conflict. The challenge is operational: ensuring the content team knows which schema types apply to each page type and can populate the templates efficiently. A decision matrix helps: if the page has Q&A content, add FAQPage schema. If the page has a named author, add Person schema. If the page has step-by-step content, add HowTo schema. The matrix reduces schema selection to a checklist rather than a judgment call.

    Maintaining Schema Over Time

    Schema deployment is not a one-time project. Content changes, author information updates, pricing changes, and CMS updates can all break or invalidate existing schema. The maintenance rhythm should include quarterly crawl-based validation across all client sites, immediate re-validation after any significant CMS update or theme change, and schema review as part of every content refresh or enhancement.

    The agency that maintains schema health across its portfolio delivers compounding SEO, AEO, and GEO value to every client. The agency that deploys schema once and forgets about it accumulates technical debt that erodes the initial investment.

    FAQ

    What is the minimum viable schema for an AEO/GEO-optimized page?
    Article schema plus FAQPage schema. The Article schema provides content metadata for SEO rich results. The FAQPage schema declares answer content for snippet extraction and AI parsing. Everything else — Speakable, Person, BreadcrumbList — adds incremental value.

    How long does it take to deploy schema across a typical client site?
    For a WordPress site with substantial content: a focused initial setup and deployment period. Monthly maintenance is lightweight per site for validation and updates.

    Should agencies use schema plugins or custom implementations?
    Use plugins for base Article schema — they handle the basics reliably. Use custom JSON-LD for FAQPage, Speakable, HowTo, and entity schema types that plugins either do not support or implement incompletely.

    {
    “@context”: “https://schema.org”,
    “@type”: “Article”,
    “headline”: “Schema at Scale: How to Implement Structured Data Across 50 Client Sites Without a Dedicated Dev Team”,
    “description”: “Schema Is the Bottleneck Nobody Talks AboutnEvery SEO agency knows schema markup matters. Most agency SEO teams can explain what Article schema and Product sche”,
    “datePublished”: “2026-03-21”,
    “dateModified”: “2026-04-03”,
    “author”: {
    “@type”: “Person”,
    “name”: “Will Tygart”,
    “url”: “https://tygartmedia.com/about”
    },
    “publisher”: {
    “@type”: “Organization”,
    “name”: “Tygart Media”,
    “url”: “https://tygartmedia.com”,
    “logo”: {
    “@type”: “ImageObject”,
    “url”: “https://tygartmedia.com/wp-content/uploads/tygart-media-logo.png”
    }
    },
    “mainEntityOfPage”: {
    “@type”: “WebPage”,
    “@id”: “https://tygartmedia.com/schema-at-scale-how-to-implement-structured-data-across-50-client-sites-without-a-dedicated-dev-team/”
    }
    }

    Further Reading

  • One Notion Database Runs Seven Businesses. Here’s the Architecture.

    One Notion Database Runs Seven Businesses. Here’s the Architecture.

    The Machine Room · Under the Hood

    When you run seven distinct business entities — an agency, two restoration companies, a golf league, an ESG nonprofit, a media company, and your personal brand — you either build a system or you drown in tabs.

    We chose the system. It’s a Notion Command Center with a 6-database architecture that routes every task, every project, every client interaction through a single operational backbone. Every entity has its own Focus Room. Every task has a priority, an entity assignment, and a status. Nothing falls through the cracks because there’s only one place anything can be.

    The Architecture

    Six databases power everything: Master Actions (every task across every entity), Master Entities (every business, client, and project), Content Calendar (what gets published where and when), Knowledge Base (SOPs, playbooks, reference material), Metrics Dashboard (KPIs across all entities), and Session Logs (every Cowork session, every decision, every output).

    A triage agent automatically assigns priority and entity to every new task. Focus Rooms filter the Master Actions database by entity, so when you’re working on restoration, you only see restoration tasks. When you switch to the agency, the view shifts instantly. Context switching becomes spatial, not mental.

    Why Notion Over Everything Else

    We evaluated every project management tool on the market. Asana, Monday, ClickUp, Linear, Jira. None of them could handle the specific requirement of managing multiple unrelated businesses through one interface without per-seat pricing that scales painfully. Notion’s database-first architecture and flexible pricing made it the only viable option for this use case.

    The real unlock was the API. Every Cowork session, every automation, every AI agent can read from and write to Notion. The command center isn’t just a project management tool — it’s the second brain that accumulates context across every session, every business, every decision. When we start a new session, the context of everything that came before is already there.

    The Compound Effect

    After six months of logging every session, every task, every outcome, the Notion Command Center contains more institutional knowledge than most companies build in years. Patterns emerge. What works in one entity informs strategy in another. The SEO playbook developed for restoration gets adapted for lending. The content pipeline built for the agency gets deployed for the nonprofit.

    This is the operational layer that makes everything else work. The 23 WordPress sites, the 7 AI agents, the multi-vertical content strategy — all of it coordinates through this single system. Build the foundation first. Everything else scales on top of it.

    {
    “@context”: “https://schema.org”,
    “@type”: “Article”,
    “headline”: “One Notion Database Runs Seven Businesses. Heres the Architecture.”,
    “description”: “One Notion database runs seven businesses. The 6-database architecture behind our multi-company command center.”,
    “datePublished”: “2026-03-21”,
    “dateModified”: “2026-04-03”,
    “author”: {
    “@type”: “Person”,
    “name”: “Will Tygart”,
    “url”: “https://tygartmedia.com/about”
    },
    “publisher”: {
    “@type”: “Organization”,
    “name”: “Tygart Media”,
    “url”: “https://tygartmedia.com”,
    “logo”: {
    “@type”: “ImageObject”,
    “url”: “https://tygartmedia.com/wp-content/uploads/tygart-media-logo.png”
    }
    },
    “mainEntityOfPage”: {
    “@type”: “WebPage”,
    “@id”: “https://tygartmedia.com/notion-command-center-seven-businesses/”
    }
    }

    Further Reading

  • The Honest Cost of Running a 23-Site Content Operation

    The Honest Cost of Running a 23-Site Content Operation

    The Machine Room · Under the Hood

    Agencies love to talk about results. They don’t love to talk about costs. Here’s the full breakdown of what it actually takes to manage 23 WordPress sites across 10+ industries with a team that’s smaller than you’d think.

    The Infrastructure

    Five knowledge cluster sites run on a single GCP Compute Engine VM. Monthly cost: under . The other 18 sites are spread across WP Engine, Cloudflare, and client-owned hosting. Our Cloud Run proxy — which routes all WordPress API calls to avoid IP blocking — costs pennies per month because it only runs when called.

    The local AI stack — seven autonomous agents running on a laptop via Ollama — costs exactly zero dollars per month in recurring fees. Site monitoring, SEO drift detection, vector indexing, email preprocessing, content generation, news reporting — all local, all free after the initial build.

    The Tool Stack

    Our total SaaS spend is embarrassingly low for an operation this size. Metricool for social media scheduling. DataForSEO for keyword and ranking data. SpyFu for competitive intelligence. Notion for the command center. Google Workspace for the basics. Claude for the heavy lifting. That’s essentially it.

    Everything else is custom-built. The WordPress optimization pipeline. The content intelligence system. The cross-pollination engine. The batch draft creator. These exist as skills and scripts, not subscriptions. Once built, they run indefinitely at zero marginal cost.

    Where the Money Actually Goes

    The biggest expense isn’t tools or infrastructure — it’s the time required to build and maintain the systems. Every custom pipeline, every skill, every automation represents hours of development. But those hours are an investment, not a recurring cost. The SEO refresh pipeline we built three months ago has processed hundreds of posts since then without any additional investment.

    The second biggest expense is content creation itself. Even with AI-assisted generation, every piece of content needs human judgment: is this actually useful? Does it represent the client accurately? Would I put my name on this? The AI accelerates the process dramatically, but it doesn’t replace the editorial function.

    The Takeaway

    You can run a serious multi-site content operation for less than most agencies spend on a single client’s tool stack. The trick is building systems instead of buying subscriptions. Every hour spent on automation pays dividends across 23 sites. Every process that gets encoded into a reusable pipeline removes a recurring cost from the ledger permanently.

    The agencies that survive the next five years won’t be the ones with the biggest tool budgets. They’ll be the ones with the most efficient systems.

    {
    “@context”: “https://schema.org”,
    “@type”: “Article”,
    “headline”: “The Honest Cost of Running a 23-Site Content Operation”,
    “description”: “The honest cost of running a 23-site content operation. Every dollar, every tool, every hour – fully transparent.”,
    “datePublished”: “2026-03-21”,
    “dateModified”: “2026-04-03”,
    “author”: {
    “@type”: “Person”,
    “name”: “Will Tygart”,
    “url”: “https://tygartmedia.com/about”
    },
    “publisher”: {
    “@type”: “Organization”,
    “name”: “Tygart Media”,
    “url”: “https://tygartmedia.com”,
    “logo”: {
    “@type”: “ImageObject”,
    “url”: “https://tygartmedia.com/wp-content/uploads/tygart-media-logo.png”
    }
    },
    “mainEntityOfPage”: {
    “@type”: “WebPage”,
    “@id”: “https://tygartmedia.com/honest-cost-running-23-site-content-operation/”
    }
    }

    Further Reading