How I work

From a search problem to a verified production result.

A systems-first engagement connects evidence, decisions, implementation, and measurement. Explore the delivery model, then use the interactive scope builder to see what a sensible first sprint could include.

01: Diagnose
02: Architect
03: Implement
04: Verify

The operating model

A finding is not finished until the live result is verified.

The work moves through a visible chain: evidence, decision, implementation, release, measurement. That keeps strategy connected to production and gives every recommendation an owner, an expected outcome, and a way to check whether it worked.

Interactive scope builder

Choose the problem. See the likely first sprint.

This is a planning guide, not an instant diagnosis. Select the situation closest to yours to see the evidence, decisions, and deliverables I would usually prioritize first.

Start with

Evidence to inspect

First deliverables

Verification signal

Build a project brief →

Four stages

The delivery cycle stays simple enough to follow.

The artifacts change with the problem. The decision logic does not.

Diagnose

Reconstruct what changed using Search Console, analytics, crawl data, release history, templates, and business context. Separate symptoms from causes.

Typical outputs

Evidence ledger
Issue map by template or directory
Prioritized findings with confidence

Architect

Translate findings into page roles, entity relationships, technical rules, ownership, sequencing, and measurable acceptance criteria.

Typical outputs

Page and query map
Technical specification
90-day priority plan

Implement

Ship changes through the real CMS, templates, content workflow, redirects, schema, internal links, automation, and team handoffs.

Typical outputs

Production-ready briefs
QA checklist and change log
Automated monitors or dashboards

Verify

Confirm the change is live, crawlable, rendered as intended, and moving the agreed signal. Record what worked and what needs another iteration.

Typical outputs

Release verification
GSC and analytics annotations
Outcome review and next queue

Working together

Clear ownership beats a black-box retainer.

You should be able to see what is being investigated, why it matters, who owns the next action, and how success will be checked. I can lead the strategy, work alongside an existing team, or translate between content, development, analytics, and leadership.

Weekly decision noteWhat changed, what was learned, and which decision follows.

Single priority queueImpact, confidence, effort, owner, status, and verification criteria in one place.

Evidence before scaleTest the rule on a bounded set before multiplying it across templates or thousands of URLs.

Reusable systemLeave behind the checklist, dashboard, script, or operating rule—not only a slide deck.

let's talk

Have a problem that does not fit a neat category?

Bring the symptom, the evidence you have, and the business constraint. We can shape the right first investigation together.

Build a project brief Run the SEO diagnostic