← All work

iGaming Affiliate Network.
Technical SEO, site architecture and content operations across nine publications.

Four years directing the technical strategy and the publishing operation behind a nine-property affiliate network, with a team of twenty producing against it.

Role
Managing director and technical head
Scale
Nine media properties
Team
20 writers, designers, publishers
Status
Confidential under NDA
Overview01

One engine, nine publications.

Nine specialised content-driven media properties ran on one shared technical spine: the same site architecture, the same internal linking model, the same schema markup and the same publishing pipeline, applied nine times rather than rebuilt nine times.

The role ran from 2019 to 2023 and covered all of it, from how a page was structured to who wrote it and how quickly it was indexed.

Under non-disclosure agreements the domain names, brand assets and financial figures behind this network are withheld, and the diagram beside this is a schematic rather than a live screen. The engineering, the team structure and the technical SEO described below are the work itself.

Network diagram: one central SEO engine connected to nine numbered publication nodes, with a content management wireframe and growth and indexation curves

One engine, nine propertiesFig. 01

How it ran02
01

Network scope

Directed technical strategy, site architecture and publishing pipelines across nine specialised content-driven media properties, each targeting its own audience while sharing one technical foundation.

02

Team leadership

A twenty-person team of writers, graphic designers, publishers and data-entry assistants. There were no other strategists or engineers on it: the technical SEO, the site architecture and the analysis were mine, and the team produced against them. Conversion, testing and performance sat in the same place.

03

Technical infrastructure

Standardised site architecture, internal linking structures, page speed and schema markup across all nine properties. The point of standardising was leverage: a fix made once applied everywhere, instead of nine separate pieces of work every time something needed correcting.

04

Content operations

Editorial workflows and production pipelines built to scale, so topical authority and indexation velocity held up as the network grew rather than degrading with volume.

What this page leaves out03

What is not here, and why.

The domains, the brand assets and the revenue figures belong to the operators and are covered by non-disclosure, so none of them appear here and none of them will.

What is here is the method: how indexation problems were diagnosed, how taxonomies were structured, how content production was scaled, and how twenty people were organised around all of it.