Rankings are an engineering problem.
I map the topic, build the WordPress that carries it, and run the content system that fills it in. Eight years of search work, now with the build attached — so nothing gets lost between the strategy deck and the theme.
Four jobs, one workflow.
Most sites fail in the handoff — the strategy is fine, the build ignores it, the writers never see it. I keep all four in the same pair of hands.
Four sites, four different problems.
An interactive statistics tool, in seven languages
Eight hundred computed cells and a twelve-page cluster — built as a tool first, so librarians would link to it without being asked.
Case study → RebuildA device database rebuilt from the schema up
Custom plugins hold the data and templates render it. No page builder, no options panel with four hundred switches.
Case study → ClientAn expired domain turned into a real publication
Strong historical links, no direction. Four categories, eight clusters and a drip calendar rebuilt it around one subject.
Case study → RecoveryDeindexed for scaled content, rebuilt to earn it back
Paid placements and scattered topics had cost it the index. The fix was narrowing hard and removing more than was added.
Case study →Proof beats promises.
The argument I make to clients — build something worth linking to — has to hold for my own site. So it does.
The order matters more than the effort.
Publishing before the architecture exists is the most common and most expensive mistake. This is the sequence I actually work in.
Tell me what isn’t ranking.
Send the domain and the queries you expected to win. I will tell you what I would change first, and whether it is worth paying anyone to do it.
Start a project