Service 01 · Foundation

SEO Systems

Topical architecture, internal linking design, and semantic authority engineered for compounding rankings. The foundation most other growth infrastructure is built on.

Typical result
3–8×
Organic impressions growth within 12 months of system launch
Compounding window
18 months
Where the architecture starts paying back the investment
01 · The problem

Most SaaS SEO is built on accidents, not architecture

Most SaaS companies treat SEO as a content marketing tactic — write blog posts targeting keywords, publish weekly, hope rankings appear. What they end up with is an accidental SEO surface: pages competing with each other, no clear topical authority, and no compounding mechanism.

The deeper issue is structural. Without a topical map, every new page weakens the existing ones. Without an internal linking model, authority leaks. Without semantic coverage, the site looks shallow to both Google and AI retrieval systems. The harder a team works without architecture, the more brittle the system becomes.

02 · The approach

SEO as system design, not campaign management

I treat SEO as a three-layer architecture problem: entity graph, topical clusters, and internal linking model. Get those three layers right, and content velocity becomes a force multiplier instead of a tax.

The engagement starts with a forensic audit of where the existing system leaks authority, where topical coverage is incomplete, and where the entity graph is ambiguous. From there, we design the architecture in dependency order — clusters before pages, links before content, semantic anchors before publication velocity.

The output is infrastructure your team can run for years. Not a list of recommendations gathering dust in Notion.

03 · What’s included

Deliverables

Discoverability audit

Forensic diagnosis of your current SEO surface, topical coverage gaps, technical issues, and authority leaks. Delivered as a working document, not a slide deck.

Topical map & entity graph

The architectural blueprint — every topic cluster, every entity, every relationship. The document your team will reference for the next 18 months.

Internal linking model

Authority-flow architecture, hub-and-spoke patterns, and the rules your team uses going forward. Includes a current-state link audit.

Technical SEO baseline

Site speed, indexability, schema, canonical structure. The unglamorous foundational fixes that compound rankings without anyone noticing them.

90-day execution roadmap

Prioritised, sequenced work plan with effort estimates, dependencies, and owner assignments. Your team can ship from this document on day one.

Team handover & documentation

Operating playbooks, brief templates, and the editorial framework. Built so the system keeps producing when I’m not around.

04 · Process

What 12 weeks looks like

Weeks 1–2

Audit & diagnosis

Discoverability surface, topical coverage gaps, technical baseline, authority leaks. The honest map of where you are.

Weeks 3–5

Architecture design

Entity graph, topical clusters, internal linking model, schema strategy. The blueprint document.

Weeks 6–10

Execution support

Working alongside your team to ship the foundational layer — technical fixes, page restructuring, initial cluster build.

Weeks 11–12

Handover & rhythm

Team enablement, ongoing operating documentation, and the cadence your team runs after I leave.

05 · Engagement

Pricing & structure

Option 01

Audit only

$6,500
4-week engagement

Full forensic audit, topical map, and 90-day roadmap. Your team executes.

  • Discoverability audit
  • Topical map & entity graph
  • 90-day execution roadmap
  • Async support during build
Option 03

Embedded retainer

$5,500/mo
3–6 month retainer

Ongoing operator role — embedded as your fractional growth systems lead.

  • Everything in Architecture sprint
  • Weekly system reviews
  • Content brief reviews
  • Ongoing optimisation loops
06 · Proof

A system in action

Case study · BetterBugs

A utility-led SEO engine that compounded into 40L+ monthly impressions

“Architected a discoverability system around 150+ utility assets and topical clustering. The system still compounds 6 months after the primary build phase ended.”

40L+ Monthly impressions
2L+ Organic clicks
38 Topical clusters
07 · Common questions

FAQ

Most agencies deliver content velocity. I deliver architecture. The output of a 12-week engagement here is the system your team uses for the next 18–24 months — not 40 blog posts they’ll have to rewrite next year.
No. Content production is rarely the bottleneck — and when it is, your existing team or freelancers will outperform a generalist consultant. What I build are the briefs, frameworks, and quality bars so the content your team produces actually fits the architecture.
Technical wins surface in weeks. Topical authority shows in months. Compounding curve emerges in 12–18 months. If a consultant promises faster than that, they’re either selling tactics that decay or describing a small-stakes win.
Often yes. Internal teams are great at velocity but rarely have the bandwidth to step back and architect. I work alongside them — the architecture sprint complements operational SEO rather than replacing it.
Probably too early. SEO architecture pays back over 18+ months. If you don’t have product-market fit yet, that’s the work that matters — not the channel. Happy to point you toward better fits at this stage.

Architect an SEO system that compounds.

I take 2–3 SEO Systems engagements per quarter. If you’re at a SaaS company past product-market fit and want to talk through what this would look like for your specific situation, let’s set up a call.

Other services