I Don’t Want to be an SEO Thought Leader; I Want the Work to be Useful

There are people in SEO who create important theories, study patents, name frameworks, and move the industry’s thinking forward. I learn from them. Olaf Kopp’s writing, in particular, helped me understand entities, semantics, E E A T, and the changing relationship between search and AI.

But that is not the role I am trying to imitate.

My work has usually started somewhere less polished: a sitemap that does not match the site, a dashboard that cannot answer a business question, a page template with poor LCP, a content team struggling with vague briefs, or a brand wondering why another source appears in an AI answer.

I like taking that mess and making the next decision clearer.

Ten years changed what expertise means to me

Early in my career, I thought expertise meant having an answer quickly. I wanted to know the correct rule, the correct tool, and the correct recommendation.

Experience made me more careful.

The same recommendation behaves differently in an international school, an iGaming company, an ecommerce site, a startup, and a global travel marketplace. The technical issue may look similar, but the risk, ownership, resources, and customer needs are different.

I now trust a good question more than a fast universal answer.

What is this page supposed to help someone do? Which part of the site owns this entity? What changed before the decline? Who can implement this recommendation? What evidence would change our priority?

Those questions are not impressive on a conference slide. They are useful in a working meeting.

Companies rarely fail because nobody knows SEO

Most teams I have worked with contain smart people who understand their part of the system. Problems appear in the spaces between those parts.

SEO notices a coverage gap, but engineering owns the generator. Content understands the destination, but the template limits what can be explained. Analytics reports the decline, but nobody has classified the affected page types. Leadership wants a priority, but receives a long audit with every item marked urgent.

The work is often translation: turning search evidence into a decision that content, engineering, product, and leadership can recognize and own.

My apps began as repeated work, not product ideas

I did not decide to build dozens of apps because the world needed more SEO tools.

I built them because I kept repeating pieces of analysis: comparing sitemap coverage, organizing citation evidence, classifying Search Console pages, checking entity language, mapping topic gaps, reviewing intent changes, and turning an audit into a smaller action plan.

The apps are my methodology made usable. They help me hold the questions in one place and make the output easier to discuss. They do not replace judgment, experience, or collaboration.

That boundary matters to me, especially now that almost any workflow can have AI added to it. A tool is valuable when it makes the work clearer, not merely because it uses AI.

What I want these articles to be

Some of my earlier articles began with concepts I was learning from experienced researchers and writers. I will continue to credit those sources. Their work deserves clear attribution.

This next group of articles has a different centre. They are notes from situations I have encountered, mistakes I have watched companies make, assumptions I have changed, and tools I built because a problem kept returning.

I will not pretend that one case proves a universal law. I can explain what I observed, what I checked, what helped, and what I would do differently now.

That feels more honest and, I hope, more useful.

What I would tell someone starting in SEO

• Learn the concepts, but do not hide behind their vocabulary.
• Ask what decision your analysis is supposed to support.
• Be specific about what you observed and modest about what it proves.
• Credit the people whose ideas helped you think.
• Understand the people and systems required to implement your recommendation.
• Build repeatable processes, but leave room for context.
• Measure success by what became clearer or better, not by how complex the audit looked.