I was the developer before I was the consultant.
10+ years building the web before I started fixing it for other people: frontend, backend and architecture for high-traffic sites that had to stay up. I still ship code today.
Martin StepanekDeveloper-led enterprise technical SEO consultant
What your engineers get out of it
Your engineers are the ones who decide whether any of this ships. Everything below is about what reaches them, and who they are dealing with when it does.
I still write production code
Not a former developer. VitalSentinel — the platform I watch client indexation, Core Web Vitals and robots changes on — is mine: I wrote it and I still ship to it. Rendering, caching, edge config and build pipelines are this week's work, not a line on a CV.
I speak to your developers, not about them
Findings arrive as tickets your engineers can pick up without translating them first. I answer their questions myself, in the same thread, and stay on it until the change is live.
I tell you what not to do
Any crawler will hand you a hundred issues. Deciding which four are worth a sprint, and which forty can safely wait a year, is the judgement you are actually hiring.
Both of them mention the same thing
Neither was asked to. Both reached for the development background as the reason it worked.
“We've been working with Martin for several years now and we truly appreciate his professional and systematic approach, which also takes our business goals into account. In addition to his deep knowledge of SEO, he's able to break down proposed strategies into actionable steps and, thanks to his previous experience as a programmer, communicate them effectively to both our editorial team and our external developers.”
“Martin's development background established a foundation for implementing sophisticated strategies, particularly technical SEO initiatives. With him, our team significantly enhanced the performance of two high-traffic websites.”
Talks
Recorded, so you can check how I explain something before you pay me to explain it.
Four ways to work with me
Scoped and priced up front, with direct access to me. You always know what you are buying before you buy it.
01Technical SEO Monitoring
It opens with the full audit, then stays on: robots.txt, sitemaps and uptime checked every few minutes, indexation and Core Web Vitals as the data lands. A call each month to go through what changed, and a shared Slack channel for your engineers in between.
Starting at $1,750/month02Technical SEO Audit
A full crawl, render and log-file pass. Dozens of findings, each naming the exact place it lives and the fix — ordered by what it earns back.
Starting at $2,25003Website Migration Planning
Replatform without losing traffic: redirect mapping, parity testing and a launch checklist owned end to end.
Starting at $4,00004Technical SEO Training
A day with your SEO specialists and your developers in one room, worked through on your own stack.
Starting at $1,150/day
Bring the problem nobody can explain.
And bring the engineer who owns it — they get more out of the call than you will, and they are the one who has to ship the fix.
- No cost
- No commitment
The technical SEO newsletter engineers and SEOs actually finish
One specific problem, taken apart, with a position on what to do about it — argued against the primary documentation and against what I see in audits. Then three stories from the last two weeks, picked and explained.
Subscribe
A new episode every two weeks. Unsubscribe in one click.