Technical SEO Audit
If your site burns crawl budget on URLs that don't matter, renders content Google never sees in time, or has indexation gaps nobody caught, no content strategy makes up for that.
Losing traffic and nobody's telling you why
Search engines don't forgive silent technical issues: wasted crawl budget on URLs that don't matter, JavaScript that takes too long to render, content that never quite makes it into the index. None of it shows up just from browsing the site.
By the time the traffic drop shows up in Search Console, the problem has usually been sitting there for weeks. Without a real technical diagnostic, there's almost no way to tell if the cause is crawling, rendering, indexation, or something else altogether.
Scope of this audit
What's included
A full diagnostic of crawl budget, rendering, Core Web Vitals, and indexation, with findings ordered by real impact, not alphabetically.
What you'll get
An actionable report showing what's holding back your rankings and the order to fix it in, with no filler.
Estimated timeline
1 to 2 weeks
If you suspect there's a technical problem and can't pinpoint it, let's start there.
What's included
Crawl budget and information architecture analysis: what Google is actually crawling today, what it should be crawling, and which low-value pages are eating that budget.
Rendering diagnostics: the gap between what the server serves and what Google actually indexes, with a focus on render-blocking JavaScript and late-loading content.
Core Web Vitals measured under real conditions, not just in the lab, with root causes traced back to the code instead of just the symptom PageSpeed reports.
Indexation review: canonicalization, robots.txt, sitemaps, and orphaned pages that never get internal links.
Structured data (schema.org) audited against what Google actually uses to show rich results.
How I work
The audit doesn't end at a PDF nobody reads. I deliver findings prioritized by real impact and implementation effort, not a 200-item list with no order.
Since I'm also a developer, I can implement the fixes directly in your codebase instead of just pointing at them. I cover both the diagnosis and the fix, when the project calls for it.
Clients
Testimonios
“Trabajar con Juan fue lo mejor.”
Patricia Ibarra
CEO · Estylopia
A real example of how I work
I don't have a published case study specific to technical audits yet, but here's a real look at how I work with clients.
Frequently asked questions
How long does a technical audit take?
It depends on the size of the site. A mid-sized one, up to around 500 indexable URLs, usually takes one to two weeks, from tool access to the prioritized report.
Do you just hand off a report, or do you also implement the fixes?
Both options exist. By default I deliver a prioritized, actionable report for your team to implement. If you'd rather I implement the fixes in the code myself, we scope that as an extension: no need to bring in a separate developer for the technical part.
What tools do you use?
A mix of technical crawlers, Google Search Console and Analytics, Lighthouse and CrUX for field Core Web Vitals, and manual code review for the cases automated tools miss, mostly rendering issues in JS frameworks.
Does the audit work if I didn't build my own site?
Yes. Most audits I run are on sites I didn't build. The diagnosis is stack-agnostic; implementing the fixes depends on how accessible your codebase is.
If you suspect there's a technical problem and can't pinpoint it, let's start there.