contact · mexico city
Tell me what’s broken, or what you want to build.
The more specific your message, the more useful my first reply. If you already have the URL, Search Console access, or a Lighthouse report, send them: I'll come to the call with hypotheses instead of questions.
carlos@carlosanayaweb.com →+52 55 4416 7974 →
Reply in under 24 hours
I reply in English or Spanish, and you write to the engineer who does the work.
three channels · parallel
How you reach me
- ch aThe formFive fields, and the URL is the one that helps most. If the site comes with it, my first reply already has a reading in it.
- ch bWhatsAppFor a thirty-second question. It opens with the subject already written, so nothing has to be explained twice.
- ch cBook a callThirty minutes, calendar open. Pick the slot that works and turn up with nothing prepared.
or write to carlos@carlosanayaweb.com · +52 55 4416 7974
the message · direct channels
after send · real sequence
After you press send
- 1
It reaches my inbox, not your email app
The form submits to the server, which sends it on as an email with your address as the reply-to, and files a copy in the system where I track enquiries. You get the acknowledgement on screen; nothing opens on your side and there is nothing for you to press twice.
- 2
I look at the site before I answer
With the URL I check how the page is crawled, what the raw HTML actually returns, and what field data says about its Core Web Vitals. I would rather arrive with hypotheses than with questions.
- 3
You get a first read, not a template
What is probably going on, and what it would take to confirm it. If it makes sense to keep going, I propose a call — that first conversation is not charged.
scope · channels a–d
Project types
Standalone audits of one to two weeks, builds of four to eight, and ongoing monthly work for teams that need an in-house SEO engineer.
index · before you write
Questions about getting in touch
How the engagement itself works — rates, scope, guarantees — is answered on the home page.
Should I use the form, email, or the phone?
All three land in the same inbox. The form only structures the message: it asks for the things I always end up asking for, and it arrives with your address set as the reply-to, so I answer by hitting reply — which usually saves one round trip. For a first contact I prefer writing, because it lets me look at the site before I answer. The phone is the better channel once something is already scheduled.
What happens to what I type into the form?
What you type reaches my server, and from there it goes to two destinations: an email to my inbox and a copy to the system where I track work enquiries. It is used solely to answer you and follow up, under Mexico’s federal data protection law (LFPDPPP). Which fields are collected, who else takes part in the processing, and how to exercise your ARCO rights are all in the privacy notice.
How do I know my message arrived?
The form tells you on the same screen, right below the button, as soon as it finishes sending. If something fails on my side it tells you that too, instead of pretending it went through, and the direct email address and WhatsApp are right there as an alternative. I do not promise delivery of an email I do not control end to end — that is why there is a second channel.
I do not know which of your services I need. Should I still write?
Yes. Describe the symptom — traffic that dropped, pages that will not index, a slow site, a manual process eating hours every week — and I will tell you which of the four it maps to. If it is not something I do well, you get that in the first reply instead of a proposal.
Can I attach files or send access credentials here?
The form is text only — there is no file field. And credentials should not travel by email. Paste a link instead — a public URL, a Lighthouse report, a Drive folder, the repository — or just say that it exists, and we agree on a safe channel for access once there is a defined scope.