Work
Each of these started as a different kind of mess: a site nobody was watching, a keyword map nobody trusted, and four services fighting over one page. The write-ups cover what was actually wrong and what I did about it.
Technical site health at scale
Full ownership of weekly technical health monitoring across 70+ client sites — spotting error patterns, managing GSC error reporting, filing dev tickets and following them to closed, and cleaning up redirects after migrations.
Read the case study →Keyword mapping and architecture
Over 10,000 keywords audited against the pages they were assigned to, each rejection carrying a written reason. Plus content production from briefs, video scripting, and a credential compliance audit across 100+ published videos.
Read the case study →Site architecture for a rebuild
Four service lines sharing one page, with the highest-value offering the least searchable. Split each into its own page, mapped pillar content to the intent that sits upstream of it, and tracked copy changes through the rebuild.
Read the case study →Client and colleague names are omitted where the work was under contract — happy to walk through specifics in an interview or under NDA.
If one of them reads like your situation, that is usually a good sign the fix is known rather than exploratory.
Tell me what you need →