Enterprise SEO

SEO that survives the org chart. Value-ranked roadmaps your teams can ship.

Most large organisations know what good SEO looks like. Getting it through product, engineering and a dozen country teams is the hard part. That part is my job.

3 years leading SEO for the biggest classifieds platforms worldwide Developer since 1997 Ranked in 244 countries

Why I get called

Six situations. You will recognise at least two.

None of these are knowledge problems. The audit already exists, usually three of them. What is missing is a decision, an owner and a ticket.

01 / backlog

A backlog nobody can rank

Four hundred open SEO tickets, each one marked high priority by whoever wrote it. Nothing ships, because nobody can say which ten matter.

02 / roadmap

SEO loses the roadmap discussion

Product arrives with revenue estimates. SEO arrives with best practices. The sprint goes to the team that brought numbers.

03 / markets

Every market runs its own SEO

Twelve country teams share one template and hold three opinions about URL structure. A fix for one market quietly breaks another.

04 / reporting

The board asks what SEO delivers

The answer is buried in a dashboard with forty charts. The question was simpler: do we fund two more developers for this, yes or no.

05 / release

A release that can cost a year

A migration, a replatforming, or two brands merging into one domain. The date is fixed. The redirect map is a spreadsheet with three owners.

06 / dependency

Results that leave with the agency

Performance holds while the consultant is in the building. Two releases after the contract ends, the old mistakes are back in production.

What I deliver

Three documents. Each one changes what gets built.

No two-hundred-page audit. A roadmap, tickets and a report, each written for the people who have to act on it.

01

A roadmap ranked on value, with the evidence attached

Many SEO tasks do not drive value. I estimate what each ticket is worth from your own search and revenue data, set that against the build cost your engineers give me, and cut the list. The tickets I skip are named too, with the reason.

  • Evidence per ticket. Logs, crawl data or Search Console, never "best practice".
  • Effort from engineering, so the estimate is theirs and they stand behind it.
  • A skip list. Saying no to work is half of the roadmap.

02

Tickets developers accept

"Improve crawl efficiency" dies in refinement, and it should. I write the ticket the way an engineer wants to receive it: the problem in numbers, the exact change, acceptance criteria you can test, and what is out of scope. I have been on the receiving end of vague tickets for close to thirty years.

Where the numbers come from

03

Reporting a board understands

One page. What we said we would ship, what shipped, what it did to non-brand traffic and revenue, and which decision I need from the room. Rankings for forty keywords are not on it. If a number cannot change a decision, it goes in the appendix.

  • Brand and non-brand split, so growth is not just your TV campaign.
  • Shipped versus planned, including what slipped and why.
  • One ask per report. Budget, people or a priority call.

Markets and brands

One rulebook. Many markets, brands and teams.

International SEO fails on ownership long before it fails on tags. I write down who decides what. The platform team owns templates, market targeting and crawl rules. The markets own demand and content. Then I build that into the release process, so a local fix cannot break a shared template without anyone noticing.

I have ranked websites in all 244 countries Google recognises, including Christmas Island. The tags were never the hard part.

  • One source of truth for canonicals, language targeting and the market-to-URL mapping.
  • A release check every team runs, automated where that is possible.
  • Shared KPI definitions, so "non-brand" means the same thing in every country.
  • Room for local judgement on keywords, content and partnerships.

Process

How an engagement runs. From first call to a team that no longer needs me.

The order matters. Value before audit, tickets before slide decks, and handover from the first week.

  1. Intake. You describe the website, the problem and who is involved. I tell you whether I am the right person for it. Sometimes I am not, and I say so.
  2. Access and data. Search Console, analytics, server logs where they exist, the current backlog and the org chart. The last two tell me more than the first crawl does.
  3. Value model. Every open ticket gets an estimate: what it is worth, what it costs, which evidence supports it. Most tickets do not survive this step.
  4. The roadmap, in the room. I present the shortlist to product, engineering and marketing together and defend it there. Disagreement is cheaper in that meeting than in sprint six.
  5. Shipping. I write the tickets, join refinement, review the result where that helps, and check each release in the data afterwards.
  6. Reporting. A fixed rhythm for management and board: what shipped, what it did, what I need next.
  7. Handover. Documentation, training and playbooks, so your team runs the roadmap without me. Education of internal teams is what keeps performance up in the long run.

inside

3yrs

Leading SEO for the biggest classifieds platforms worldwide.

since

2011

The year I took my SEO work to the bigger players in the market.

reach

244

Countries I have ranked websites in. Google's count, including Christmas Island.

scale

50M+

Pages on the websites I handle large-scale technical challenges for.

Ways to work together

Three shapes. Pick the one that fits the problem.

There is no price list on this page. Scope follows the website and the organisation, so it starts with a conversation.

01 / embedded @team

Embedded SEO lead

I join your organisation as the senior SEO in the room. I own the roadmap, sit in planning and refinement, and report to whoever owns growth. An integrated team approach makes sure SEO is not the blocking factor.

  • Value-ranked roadmap and quarterly plan
  • Tickets, reviews and release checks
  • Reporting to management and board
Discuss an embedded role
02 / review diff

Second opinion

You have a strategy, an agency proposal or a migration date, and you want someone independent to read it before it ships. I work independently, so nobody's retainer depends on the answer.

  • Review of the strategy, audit or migration plan
  • A risk list, with what I would change
  • One session with the people who decide
Ask for a second opinion
03 / training man

Team training

I train SEOs, developers and product owners on your own data and your own templates, so the examples are the ones they will meet on Monday. I also teach as an SEO lecturer at SEO Pro Academy.

  • Workshops for SEO, development and product
  • Playbooks and checklists that stay behind
  • Coaching for the in-house SEO lead
Plan a training

Fair questions. Straight answers.

What I do and do not take over, how the value model works, and what stays behind when I leave.

Do you replace our SEO team or our agency?

No. I work with the people you have. The in-house team usually knows the website better than I ever will, and an agency does execution I have no wish to take over. What I add is seniority in the rooms where priorities are set, and a developer's eye on what is being asked of engineering.

How do you put a value on an SEO ticket?

With your data. Search demand and current positions from Search Console, conversion and margin from your analytics and finance teams, build cost from your engineers. The outcome is a range, with the assumptions written next to it.

It does not have to be precise. It has to be good enough to put ticket A above ticket B, and to show which tickets are worth nothing.

Can you work inside our sprints and tooling?

Yes. I use whatever issue tracker and planning rhythm the team already has. I join refinement, write acceptance criteria and check the result after release. I have been building for the web since 1997, front end and back end, so the conversation with engineering tends to be short.

We operate in many countries. Where do you start?

With ownership: who can change a template, who decides on a market's URL structure, where the market mapping is generated. Then the data per market. The technical side of international SEO, including audits across complete URL sets, is on the technical SEO at scale page.

Do we need to use GSC Wizard or your other products?

No. The products grew out of client problems and I use them where they save time, but consulting does not depend on them. They are separate products with their own pricing, apart from any consulting agreement.

What happens when the engagement ends?

The roadmap, the value model, the ticket templates and the reporting stay with you, documented. The aim from the first week is that your team runs them without me. If performance depends on me still being around, I did it wrong.

More about my background is on the about page. For software companies there is a separate page on SaaS SEO.

Four hundred tickets, one quarter. Let's decide which six matter.

Tell me about the website, the teams around it and what is stuck. I will tell you what I would look at first.

Independent consultant · working with teams worldwide