Skip to main content
All skills

Content Marketing & SEO

Technical and editorial SEO are one problem from two angles — whether the page can be found, and whether it deserves to be. Most engagements turn out to have a technical layer underneath a content problem, or the reverse.

How I use it

  1. A replatform about to drop a decade of rankings

    Wee Rock Art moved off WooCommerce with 150 product URLs that already ranked. I exported every legacy URL and built the redirect map before launch rather than after the traffic disappeared, so the equity moved with the catalogue.

  2. Content that silently goes stale

    Built a content registry for this site that records when a human last reviewed each route and fails CI when a page passes its refresh cadence. Freshness stops depending on somebody remembering.

  3. Pages that answer engines cannot parse

    Person, Organization, Service, Breadcrumb, FAQ and Article JSON-LD, plus an llms.txt policy — so retrieval systems get structured facts instead of inferring them from prose and getting it wrong.

  4. Programmatic that would otherwise be slop

    The information hierarchy gets designed before anything generates. Done in that order the templates keep earning after you stop touching them; done backwards you have published a liability at scale.

What I use

  • Google Search Console
  • Ahrefs
  • GA4
  • Screaming Frog
  • Schema.org

Where you can see it

Related skills

Want the detail behind any of this?

I can walk through any of it in as much depth as you want.

Get in touch