Carlos Anaya Ruiz
ES

Technical SEO · Mexico City

Technical SEO Consultant in Mexico

Audits, structured data, Core Web Vitals, and migrations. I work on the code, not on a generic checklist.

Request an audit →All services →

Based in Mexico City. Remote work with teams in any time zone.

the problem

Why this matters

A beautiful site that Google cannot crawl, understand, or index is invisible. Technical SEO is the engineering layer that makes a search engine — and now a language model — see your content the way a person does: fast, structured, and unambiguous.

I have seen migrations drop a site’s organic traffic because nobody mapped the old URLs before shipping. I have audited platforms where half a template was blocked in robots.txt for months and nobody noticed, because the site looked perfect in a browser. These are engineering defects, so I look for them the way an engineer would: in the repository, in the response headers, and in the HTML that is actually served — not against a generic checklist.

It is also why this work does not always end in an audit. If the diagnosis points at content or at authority rather than at the stack, I say so on the first call. That is cheaper for both of us than a deliverable that was never going to move anything.

scope

What I actually do

Audits, structured data, Core Web Vitals, and information architecture

  • A full crawl cross-referenced with Search Console: what gets indexed, what does not, and what competes with itself
  • The structured data already in place: which types exist, which validate, and which produce nothing
  • Core Web Vitals in field data and in the lab, with the gap between them visible
  • Information architecture, URL structure, and internal linking

What changes afterwards

  • The pages that matter become crawlable and indexable, with no orphaned templates and no canonicals competing with each other.
  • Structured data passes Google Rich Results validation instead of failing silently.
  • Core Web Vitals measured on field data, not just on one favourable lab run.
  • Your team keeps a backlog prioritized by impact and effort that they can execute without me.

pendiente · imagen 1600×900public/media/servicios/seo-tecnico-antes-despues.png

How I work

How the work runs

  1. phase 1/4

    Crawl and baseline

    A full site crawl cross-referenced with Search Console and analytics. Current indexation, Core Web Vitals, and structured-data state are recorded so before and after can be compared with your own numbers.

  2. phase 2/4

    Prioritized diagnosis

    Every finding is documented with evidence, estimated impact, and implementation effort, ordered so the first thing fixed is the thing that moves the needle most.

  3. phase 3/4

    Implementation or guidance

    I implement the fixes directly in the repository, or support your team with technical specs and pull-request review. You decide who ships.

  4. phase 4/4

    Validation and follow-up

    Schema re-validation, field measurement of Core Web Vitals, and an index-coverage review after Google recrawls, with a closing report.

good fit · not a fit

Who this is for, and who it is not

Who this is for

  • Sites with existing content and traffic that underperform for technical reasons.
  • Product teams that need outside technical judgement before a migration or a redesign.
  • Businesses with large catalogues or templates, where a single indexation mistake multiplies across thousands of URLs.

Who this is not for

  • Not for anyone who needs results in two weeks: the pace is set by Google’s recrawl and your team’s deployment cycle, not by the audit.
  • I do not do link building, paid links, or PBNs. If your problem is authority or content rather than technical, I will say so on the first call instead of selling you an audit.

If one of those describes your situation, say so in the first message and we save each other a proposal.

What's included

What you get

Written, versioned, and yours to keep — including the reasoning behind each recommendation.

  • Full technical SEO audit with prioritized findings
  • Schema.org / JSON-LD implementation and validation
  • Core Web Vitals optimization (LCP, INP, CLS)
  • Information architecture and URL structure review
  • Indexation strategy: sitemap, robots, canonical, hreflang
  • Internal linking audit and optimization

reproducible

Tools I use

  • Google Search Console
  • Rich Results Test
  • Schema Markup Validator
  • Lighthouse
  • PageSpeed Insights
  • Chrome UX Report
  • Screaming Frog
  • Chrome DevTools
  • Next.js
  • Vercel Analytics
  • Google Search Console
  • Rich Results Test
  • Schema Markup Validator
  • Lighthouse
  • PageSpeed Insights
  • Chrome UX Report
  • Screaming Frog
  • Chrome DevTools
  • Next.js
  • Vercel Analytics
  • Google Search Console
  • Rich Results Test
  • Schema Markup Validator
  • Lighthouse
  • PageSpeed Insights
  • Chrome UX Report
  • Screaming Frog
  • Chrome DevTools
  • Next.js
  • Vercel Analytics
  • Google Search Console
  • Rich Results Test
  • Schema Markup Validator
  • Lighthouse
  • PageSpeed Insights
  • Chrome UX Report
  • Screaming Frog
  • Chrome DevTools
  • Next.js
  • Vercel Analytics

Standard tooling, named on purpose: every finding in the report can be reproduced by your team with the same tools, without taking my word for it.

FAQ

Frequently asked questions

What does a technical SEO audit include?

A full analysis of your site architecture, indexation status, structured data, Core Web Vitals, internal linking, canonical tags, hreflang, robots/sitemap, and rendering. You get a prioritized report with specific fixes and expected impact.

How long before I see results from technical SEO improvements?

Google decides when it recrawls, not me: a fix does not exist for the search engine until it crawls that URL again. That is why I do not put a date on ranking impact. What does carry a date is what is verifiable: the day the fix shipped, the schema revalidation, and the field reading of Core Web Vitals in the closing report.

Can you handle SEO migrations?

Yes. I handle migrations from WordPress, Angular, React SPAs, and other frameworks to Next.js. The process includes pre-migration audit, URL mapping, 301 redirects, schema migration, and post-migration validation to preserve organic rankings.

Services

Related services

Technical SEO usually arrives with a build or a measurement problem attached. These two are where that work continues.

Or compare the four services side by side before deciding where to start.

the proof · file pending

pendiente · imagen 1600×900public/media/servicios/seo-tecnico-crawl.png

pendiente · imagen 1400×900public/media/servicios/seo-tecnico-schema.png

three channels · parallel

How you reach me

or write to carlos@carlosanayaweb.com · +52 55 4416 7974

Send me the URL and what changed.

Search Console access helps, but it is not required to start. I reply with a first read on what is likely going on and whether an audit is even the right next step.

Book a call →carlos@carlosanayaweb.com

I reply in under 24 hours, Mexico City time.