I built a website health audit. The numbers it returned on my own site were a starting line.

Why I’m launching Osita: a new sub-brand for the work that kept landing outside every existing one

A couple weeks ago I shipped the first cut of a Site Health dashboard inside WebOps Hosting. Every client on the platform now gets a weekly audit of their own site: rankings, competitors, backlinks, page speed, security headers, mail deliverability, the works. Free. The pitch is simple: hosting that doesn’t just keep your site online, but actively watches the health of the business it’s running.

To pressure-test the tagging engine I built, I ran the audit against three real client sites. One of them was ryandavis.com.

The numbers were exactly what they should be for a site that spent most of the last two decades as a coming-soon page:

• 0 commercial search terms my site ranks for on Google
• 1 referring domain in 20 years
• 0 measurable growth in the last 90 days

I’ve been operating a hosting company for almost twenty years, but I ran it white-label by design. The agency-of-record on every site was the agency client; I was the operator behind the curtain. Putting ryandavis.com on the map would have meant competing with the people I was building for. So I didn’t. The site stayed dark on purpose.

A couple of months ago I flipped that. The white-label posture made sense when the entire business was one layer of operating work. It doesn’t make sense now that there’s a holding company with multiple operating brands and a strategy practice on top. So the public Ryan Davis, LLC brand is new, actively new, and the audit’s three numbers are an honest read of the starting line.

That starting line is the reason this post exists.

What I was actually building

The Site Health audit started as a tier of a larger product. The free tier (every WebOps hosting client) renders raw analyzer findings in their admin panel. A paid tier sits on top, where each weekly crawl synthesizes those findings into an executive Health Brief, and the WebOps ops team works through them as remediation. The point was to make hosting a healthier baseline by default and to give every issue category a service tier that fixes it.

Once I had findings flowing, every finding needed to be tagged by which service category would fix it. I started with a five-bucket taxonomy: security, content cleanup, privacy, analytics, and a general “website health” add-on for the perf/links/uptime stuff. Plus a general fallback for anything else.

Then I ran three real audits and looked at what general actually caught.

What three audits showed me

The three sites were mine (ryandavis.com), a Barbados law firm I host (pinebridgelaw.com), and a long-running sports organization (barbadosturfclub.org). All three on identical hosting. All three with the same WebOps baseline of SSL, perf, security headers, and email authentication.

The findings broke down like this across the three:

Half of every audit was a category that none of my existing brands actually fulfills.

The specifics, anonymized into examples:

• A law firm has been online for nearly 10 years and has one inbound link. That link has a spam-score flag. The firm ranks on page 1 for nothing commercial. A direct competitor owns every search a potential client would type.
• A sports organization has 1,054 broken inbound links pointing at pages that no longer exist. The link equity is leaking. BBC.com links to their named competitor but not to them. They have 1,505 referring domains earned over decades that are slowly being thrown away.
• My own site is the same shape from a different cause: zero rankings, one backlink. Not because it failed, but because it was deliberately invisible.

These are not hosting problems. They aren’t security problems. They aren’t even content-cleanup problems in any honest reading. They are search-marketing problems: keyword strategy, on-page SEO that actually targets commercial intent, off-page authority work, outreach, the disavow file nobody wants to maintain, the directory placements nobody chases.

The taxonomy problem nobody warned me about

When you build a multi-brand business, you end up making a lot of small decisions about which brand owns what. Most of those decisions are easy. Web hosting belongs to WebOps. New WordPress builds belong to LuckyTyke. Strategy advisory belongs to Ryan Davis, LLC, the parent.

But “fix the fact that your competitors are eating your lunch on Google” had no clean home. I tagged it general in the audit and told myself the parent brand could absorb it as consulting work.

That lasted about ten minutes once I looked at the numbers.

Folding search-marketing fulfillment into Ryan Davis, LLC creates a contradiction the parent brand can’t survive. The whole point of a holding-company brand is that it sits above the operating brands and does the strategy work that only the principal can do: picking the stack, owning the client relationship, deciding when to deploy hosting vs. build vs. SEO vs. ads. If that same brand is also doing the link outreach and writing the meta descriptions and managing the Google Ads campaigns, it isn’t above anything. It’s just another agency wearing a holding-company hat.

There’s a labor-versus-leverage line that every operator knows but few articulate cleanly. The labor sits in operating brands so that the strategy brand can keep its altitude. Lose that, and the strategy brand becomes a freelancer with a website.

Stepping out of the white-label posture only sharpened this. As long as Ryan Davis was an invisible operator behind agency clients, the absence of a clear search-marketing offering was fine; the agency clients owned that work. The moment the parent brand started showing up publicly, the question of which brand owns search-marketing fulfillment got pointed and unavoidable. It had to belong somewhere. It couldn’t belong here.

Introducing Osita

So I’m launching a fourth brand.

Osita is a search-marketing brand. SEO and SEM together: keyword strategy, on-page optimization, technical SEO, backlinks and outreach, Search Console and Bing Webmaster setup, Google Ads campaign management, conversion-optimized landing pages. Everything between “your site exists” and “your right-fit customers find you.”

The name is Igbo, named for a friend. It’s a shortened form of Ositadimma, which means “from today, it is good.” Igbo names tend to function as declarations: they mark a turning point, after hardship or a long-awaited arrival, and announce that things will be well from this day forward. For a brand launching to do work that needed its own home, named to mark the moment it gets one, the meaning lined up better than I had any right to expect.

It slots alongside WebOps and LuckyTyke:

• WebOps Hosting keeps your site healthy and fast
• LuckyTyke builds new sites
• Osita fills the seats those sites are designed to hold
• Ryan Davis, LLC stays above all three, doing strategy and owning the relationship

The Site Health audit becomes the router. Every finding now has a named home. Findings tagged search_marketing route to Osita with an “Activate →” CTA in the client’s admin panel. Findings tagged hosting_baseline render as “Handled by your hosting” reassurance. Performance work beyond what hosting’s LSCache baseline can resolve routes to a speed_optimization lane and a paid Speed Optimization addon that launched the same week alongside Osita. Security, content, privacy, and analytics each have their own lane and CTA. There is no more general. Every problem the audit surfaces now has a named route to remediation.

The naming convention for the slug ended up being search_marketing, deliberately function-named instead of brand-named. If Osita ever rebrands, the taxonomy doesn’t move. That decision came from the same principle as everything else in this post: build the underlying machinery against the work, not against the marketing.

What’s next

Over the next few weeks I’ll be building out Osita: identity, positioning, pricing, the website, the WHMCS plumbing that lets WebOps clients add Osita services with one click from their dashboard. The first version will productize the three things I’ve been doing informally for years anyway: keyword strategy briefs, monthly link-earning programs, and managed Google Ads for SMB local search.

If you run a site and want to see what the audit says about it (your rankings, your competitors, what publications are linking to them and not you) you can run the free Website Health Report at osita.agency/free-audit — the funnel now lives where the work does. It returns in a few minutes. The same audit engine runs on every WebOps client site every week, and it’s about to start telling people exactly which of the four brands they need.

My own site will be one of the first to run through the new program.

Three takeaways for fellow operators

1. Build the audit before you build the service. If you can’t tell a client what’s broken in concrete numbers, your sales pitch is the problem. The audit forced me to find the gap. Without it, I’d still be telling myself my SEO was “okay.”
2. Watch where the general bucket fills up. Whatever taxonomy you use to organize your business, the catch-all bucket is where unbuilt services hide. Mine pointed straight at a brand-shaped hole.
3. Multi-brand businesses fail when brands drift into each other’s lanes. Putting fulfillment under a strategy brand looks like efficiency from the inside and looks like confusion from the outside. The work belongs in the brand built to do it, not in the brand that happens to have the relationship.

Ryan Davis runs Ryan Davis, LLC and its operating brands: WebOps Hosting, LuckyTyke, and now Osita. He writes about building, operating, and selling small businesses at ryandavis.com.