100+ clients, and the week everyone called me about security

What does this cover?

My title at Prospecta Marketing is Senior SEO Specialist and Account Executive. That is the real title and I am not going to dress it up. It also undersells the job by a wide margin.

In practice I am the main technical point of contact for 30-plus accounts at a time inside a book of more than 100, and the work is front-end development, CMS architecture, custom plugin development, internal tooling and serverless automation. It is a small team with almost no formal onboarding, so the answer to "who handles this" has usually been whoever picks it up.

This page is an anonymized composite. Healthcare clients are not named here and will not be.

Recovering a launch that had already gone wrong

A large multi-location dental group came to us out of a site refresh that had gone badly. I owned the CMS architecture and a full site redesign, and I worked directly with their in-house engineering team rather than around them.

That last part is the whole thing. An agency arriving after a failed launch has an easy story available: the last work was bad, hand it over to us. It is also the story that guarantees friction with the people who will maintain the site afterward and who know things about it that were never written down.

So I treated their developer as a colleague. We got on Zoom, we got in a room, and we worked the problem together. Both the client and their own developer credited the work directly, and I would rather have that than the win.

The conversion-focused location page layouts I built for them were reusable by design, and the company ended up adopting them across other accounts.

What did the numbers do?

Every figure below is from tracked visibility reporting, with the exact window it happened in. No open-ended "since I took over" framing, because that hides when things actually moved.

• A dental client from Jun 2025 to Apr 2026: search visibility from 29.9% to 71.3%, the fastest sustained growth in the book.
• A practice at real risk of closing, Feb 2024 to May 2024: 5.4% to 28.3% in three months. That growth bought the owner enough time to sell the business with a patient base still attached, which mattered more than the number did.
• A client on organic SEO only, no paid, Sep 2025 onward: 74.6% to 90.1% over ten months. They paused the engagement because the patient influx got ahead of what the practice could take. That is the strangest compliment I have received at this job.
• Across the book: clients up 40% or more inside the first one to two months of dedicated work, landing pages moving from position 30-plus into the top ten inside a month, and 100% on quarterly review counts while carrying 30-plus accounts.

I also built the agency's answer engine optimization strategy from nothing: entity-based optimization, knowledge-graph and brand-entity work, and structured data aimed at AI Overviews, ChatGPT and Perplexity rather than at ten blue links. Early results are good. It is too new for me to hand you a number I would defend.

Decisions

Build the location pages once, properly. Multi-location businesses are the same page repeated with different content, which means the work is either done once well or many times inconsistently. Designing for reuse is why the layout traveled past the client I built it for.

Say the title accurately and let the bullets carry the scope. I could describe myself as a developer at an agency and nobody would check. The title on record says SEO Specialist, so that is what I put on things, and then I show what the work actually was. A title that does not survive a reference check is not worth the upgrade.

Becoming the security lead

We had a hack that exposed credentials.

I ended up as the team's subject matter expert on it, which is a polite way of saying I was the person who did not put it down. I built the remediation strategy and executed it, and every client account was secured within 24 hours with the exploited weak points closed.

Why 24 hours and not a phased rollout. With credentials exposed across a shared book of accounts, the exposure window is the entire risk. A staged plan leaves a known-compromised credential live on some accounts while you fix others, and an attacker holding a list does not work through it in the order you scheduled. Doing all of it inside a day cost a great deal more coordination and removed the window completely.

That week is also the clearest example of the thing I keep claiming about myself: the hard part was not the technical remediation. It was calling a lot of people, telling them something bad had happened, and keeping them calm enough to act on it quickly.