SEO Consulting
A one-off audit catches today's problem. A growing site needs someone monitoring, prioritizing, and adjusting the technical strategy continuously, not a snapshot taken once a year.
The report goes stale, the site never stops changing
An audit report goes out of date fast. A site that changes every week, with releases, migrations, and content updates, needs someone tracking the SEO impact of each change, not a review that happens once a year.
Most SEO consultants only speak the content side of the language. When the problem lives in the code, like a botched migration or a deploy that broke rendering, those recommendations need translating to someone else, and that's where whole weeks get lost.
Scope of this engagement
What's included
Ongoing monitoring of Search Console, rankings, and Core Web Vitals, with review of every release that could affect technical SEO before it ships.
What you'll get
A technical roadmap that adjusts based on the site's real data, instead of a fixed plan that goes stale a month after it's written.
Estimated timeline
Ongoing, scoped per engagement
If your site changes constantly and you need someone watching technical SEO on an ongoing basis, let's talk about how to structure it.
What's included
Ongoing technical strategy: a prioritized roadmap that adjusts based on what the data shows, not a fixed plan written once.
Search Console, rankings, and Core Web Vitals monitoring over time, to catch regressions before they turn into traffic drops.
Direct collaboration with your dev and marketing teams. I speak both technical languages, which is uncommon among consultants who only know the content side.
Review of every release or deploy with potential SEO impact (architecture changes, migrations, redesigns) before it ships, not after.
How I work
Cadence is set based on the site's size and rate of change: from monthly reviews to weekly involvement on projects with frequent releases.
Every cycle delivers prioritized findings and a clear report of what changed, what got implemented, and what impact it had. No dashboards nobody interprets.
Since I also build (Next.js, headless CMS), I can review pull requests or implement the technical changes directly, not just recommend them.
Clients
Testimonios
“Trabajar con Juan fue lo mejor.”
Patricia Ibarra
CEO · Estylopia
A real example of how I work
There isn't a published case study for ongoing consulting yet, but here's a genuine example of how I approach working with clients.
Frequently asked questions
How is an ongoing consulting engagement structured?
We set a cadence (monthly, biweekly, or weekly depending on need) with a clear scope for what gets reviewed each cycle. It's not an open-ended contract with no goals: every cycle has concrete deliverables, and scope can adjust over time.
How is this different from the technical audit?
The audit is a point-in-time diagnostic focused on a specific moment. Consulting is continuous: monitoring, re-prioritizing, and reviewing changes over time, for sites that keep evolving and can't rely on a single snapshot.
Do you work directly with my dev team?
Yes, and that's where I add the most value versus a traditional consultant. Since I'm also a full-stack developer, I can review code, take part in architecture decisions, or implement changes myself, instead of just handing off recommendations the dev team has to translate.
What's the minimum commitment?
It depends on the project. We figure it out based on the site's current state and expected rate of change. There's no fixed package: the quote is scoped after understanding the context.
If your site changes constantly and you need someone watching technical SEO on an ongoing basis, let's talk about how to structure it.