An enterprise B2B health data platform ranking for the wrong audience entirely, with 49 of 50 buyer keywords completely unclaimed

The client was generating organic traffic. The problem was who was showing up. Their content ranked well for clinical research topics, which brought clinicians and researchers reading their published findings. That's not who buys the platform. The actual buyers, VPs of HEOR, Heads of Pharmacovigilance, Chief Data Officers at pharmaceutical companies, couldn't find them when they searched for a real-world data solution. Their top competitor held 3,200 commercial keyword rankings. They held 107. And 80% of their traffic came from a single branded query.

What was delivered
50-keyword buyer opportunity matrix 8-competitor keyword gap analysis Tiered 30/60/90-day content roadmap C-level talking points Priority action checklist Persona-specific page briefs Competitive positioning analysis

The C-level talking points were written to explain the SEO situation in business terms, with zero jargon. Each one followed the same format: say this out loud, then here's the context behind it. Built so a marketing leader could walk into an executive meeting and explain the problem, the opportunity, and the recommended next step without needing a slide deck.

A full audit and implementation workbook for a B2B technology consultancy competing for high-intent keywords they weren't ranking for at all

The client had strong expertise and a real track record. Their site didn't reflect either. Their homepage title tag was just their company name. Eight characters, zero keyword equity. Eighty percent of all title tags were over the recommended limit. They were ranking for only 4 of 66 target keywords. Their AI Visibility Score was 16 out of 100, and AI tools were associating the brand name with something completely unrelated to their actual business.

What was delivered
26-slide audit deck 15-tab Excel workbook Title tag fixes for 128+ pages H1 and meta description rewrites Redirect audit Keyword gap analysis AI brand disambiguation plan AEO citation strategy 30/60/90-day action plan

Every fix in the workbook was written out with exact suggested copy and a character count formula built into the spreadsheet. The dev team could start executing on day one. Nothing to look up, nothing to interpret.

A phased content and schema program to build AI visibility across three competitive categories for a financial services brand

The client was competing in three distinct market lanes, each with its own set of competitors and content expectations. Their AI Visibility Score was 20 out of 100. No schema was in place. The site ran on a JavaScript framework that required specific implementation guidance to add structured data correctly. They needed a clear, prioritized program, not a list of recommendations they'd have to figure out how to sequence themselves.

What was delivered
12-week phased program 7-piece content strategy Schema implementation workbook Complete JSON-LD code blocks Framework-specific instructions Competitive landscape analysis Weekly AI performance tracking

The schema workbook included complete, ready-to-paste code blocks for every page type. Framework-specific implementation notes meant the dev team didn't need to research how to add schema to their specific platform. It was already written out for them.

Ongoing weekly AI Brand Performance reports and content strategy for a consumer technology product building Share of Voice from zero

The brand had a strong product and a real audience. In AI platforms, it didn't exist. Its top competitor held over 16% Share of Voice in AI responses in the same category. The brand sat at 0%. Every week, AI tools were sending potential customers elsewhere. The situation was urgent because the category was still fragmenting. There was still a window to enter the conversation before it consolidated around established players.

What was delivered
Weekly AI Brand Performance reports Share of Voice tracking Sentiment and perception analysis Competitor gap tracking Weekly content plan Content briefs with schema Internal linking recommendations

Each weekly report opened with the headline signal, explained what it meant, and ended with a specific content recommendation the team could act on immediately. Not a data dump. A brief with a clear next step attached.

A pre-migration risk assessment drawing on a full site crawl, 15 months of GA4 data, and a complete backlink analysis before anything moved

The client was planning to move from one domain to another. Before any redirects were mapped, I pulled three data sources together: a technical crawl of the full site, 15 months of organic session data, and a complete backlink export. The headline finding was that nearly all of the site's organic equity lived on one URL, the homepage. That changed the risk profile significantly. But there was also a confirmed technical issue that had to be resolved before the migration could begin: both the www and non-www versions of the site were returning live responses simultaneously, splitting domain authority between two hosts.

What was delivered
Pre-migration risk assessment Full site crawl analysis Organic traffic breakdown Backlink equity analysis Canonicalization issue diagnosis Prioritized pre-migration fix list Conditional go recommendation Timing guidance for concurrent changes

The recommendation wasn't just go or wait. It was a conditional go with a specific sequence: fix the canonicalization issue first, test the glossary errors, add noindex directives to app-specific URLs, and keep the pending site redesign at least four weeks away from the migration date. Each item had a plain-English explanation of why it mattered and what happened if it was skipped.

An ongoing monthly engagement covering technical SEO, content updates, schema, and redirect management for a local B2C service business focused on conversion

A local service business with a mature site that needed ongoing attention, not a one-time fix. The work spans technical cleanup, content improvements, and schema additions that compound over time. The goal isn't rankings in isolation. It's leads. That means fixing the technical issues that limit crawlability, improving the content that converts, and making sure the site structure makes it easy for search engines and prospective customers to find what they're looking for.

What's ongoing each month
Technical crawl monitoring Canonical tag fixes for tracking URLs 301 redirect mapping for discontinued products Duplicate content identification and resolution FAQ schema additions to high-traffic pages Content updates with keyword and intent alignment Monthly reporting with prioritized next actions

When a product line gets discontinued, that's not just a content update. It's a redirect mapping exercise that has to be done carefully so the existing link equity gets preserved. This kind of ongoing maintenance is what keeps a site's technical health from quietly eroding while the team is focused on everything else.

Deliverable Types

What CMM work actually looks like.

Every engagement produces something your team can use on its own. Here's what shows up in practice.

Audit Decks

Decks that explain, not just report

Findings organized by priority with plain-English explanations of what each issue means and why it matters. Built to be shared with an executive team or a dev team, not just filed away.

Implementation Workbooks

Spreadsheets built for execution

Every fix written out. Every code block complete. Character count formulas built in. Instructions clear enough that a developer can work through it on their own without a call to ask what something means.

Weekly Reports

AI performance briefs with a clear next step

Not a dashboard. A brief. The headline signal, what it means, and what to do next. Written so the person reading it knows immediately whether something needs to change this week.

Content Briefs

Briefs your team can act on the same day

Keyword targets, schema type, internal linking recommendations, FAQ structure, and a content outline. Everything the writer or strategist needs to produce something that earns visibility, not just traffic.

Risk Assessments

Go / conditional go / wait before anything moves

A clear recommendation backed by crawl data, traffic analysis, and backlink equity review. Not a list of things to worry about. A sequenced plan for what to fix first and why.

Schema Workbooks

Complete code blocks ready to paste

Schema markup written out for every page type, with platform-specific implementation notes so a developer knows exactly where to add it and how to verify it once it's in place.

Client names are kept confidential by default. If you want to know whether I've worked in your industry or with companies at your stage, ask. The first conversation is free and there's no pitch attached to it.

Want to see what this
looks like for your site?

Tell me what you're working on. I'll tell you what I'd look at first.

Get in Touch