Tools and deliverables: where I used each one, with date and case
Which tools I use, how I use them and where I actually used them. Each one with the date and the case study where you can check it.
Your business, translated into searches
You don't sell “keywords”: you sell a service. Your customer, on the other hand, types a question. My job is to connect the two: find how your customer searches for what you offer, and give each search a page that answers it.
| What the firm offers | What its customer types (in Spanish) | The page that answers it |
|---|---|---|
| Business insolvency advice | “ley 1116 de 2006”, “reorganización empresarial” | A pillar page on the law, with one page for each question |
| Calculating debts with the tax authority (DIAN) | “liquidador intereses de mora dian 2026” | A calculator that does the math |
| The first consultation | “cesación de pagos” | A guide that explains the term and ends in “let's talk” |
That's how regresoempresarial.com is built, a business insolvency site run by a family member. I defined the strategy and specified it; AI agents I directed and reviewed executed it.
Today it has 28 pages indexed and 0 not indexed (Search Console, report of Oct 11, 2026). From Sep 14 to Oct 14, 2026, Google showed it 2,805 times and it got 30 clicks. From Jul 12 to Aug 12, the figures were 336 and 6.
That's still few clicks, and that's why I say it. Google showing a site is the first step, not the last.
Source: Google Search Console, with the owner's permission. See case study 1: technical visibility and case study 2: architecture and content.
Tools and method
- Search Console
- GA4
- Screaming Frog
- Semrush
- DinoRank
- PageSpeed
- Cloudflare
- Base44
- Git
- Claude Code
- Cayu
I use Google Search Console, Screaming Frog, GA4, Semrush, DinoRank, and PageSpeed as data sources, among others. I also work with Cayu, an SEO suite I designed and built with Claude Code: I specified and tested it, and Claude wrote the code. For now, it's for internal use.
Cayu finds and classifies keywords, with difficulty calculated from the real top results, and analyzes competitors live. It also audits drafts and content briefs (the instructions for a text), checks readability in Spanish, and verifies structured data (a profile Google reads).
I use it because it lets me repeat the same method on every project and leave evidence behind. I use AI the way you'd use a calculator: it executes what I specify, code included. But whoever signs checks the sum, and I'm the one who signs.
I build tools with AI for my own work. I don't sell web development: I'd rather do one thing well, which is getting your site found.
The ruleI use AI the way I'd use a calculator. Whoever signs checks the math, and the one who signs is me.
Where I used each one, with date and case study
This is where I actually used each tool, with the date and the case study where you can check it. If I haven't used it on a project, it isn't listed.
| Tool | Where and when I used it | Where you can check it |
|---|---|---|
| Google Search Console | On regresoempresarial.com, a family member's site, since July 2026, and on this site since September. Indexing, impressions and the generative AI report the owner of regresoempresarial.com exported | Case study 1 and case study 2; the AI report, in the project log |
| Google Analytics 4 | On regresoempresarial.com: I separated my own tests from real visits (Sep 16, 2026) and froze the baseline (Sep 28, 2026). Later I kept organic apart from paid (screenshot of Oct 14, 2026) | Google Analytics 4 guide and case study 3: plan to convert |
| Screaming Frog (free version) | I crawled regresoempresarial.com without JavaScript: 24 to 35 words of content per page (Jul 18, 2026) | Case 1: technical visibility |
| Google Ads Keyword Planner, Ahrefs (free, through its interface) and DinoRank | I cross-checked the volume of 37 keywords on Colombia's insolvency law (Ley 1116) for regresoempresarial.com, in Colombia (Jul 22 and 23, 2026) | Project log; no published case study |
| DataForSEO and DinoRank | I measured volume and difficulty for the second keyword research of regresoempresarial.com, in Colombia (October 2026) | Case 2: architecture and content |
| PageSpeed Insights | On regresoempresarial.com: five runs per page with the PageSpeed API, in the lab (Aug 23 and 24, 2026) | Core Web Vitals: why five runs; the August runs, in the project log |
| Cloudflare: DNS, Workers and analytics | I took this site live with a Worker as a custom domain (Sep 15, 2026) and read which AI robots visit it (Oct 1, 2026) | Guide to SEO for single page applications and What is llms.txt |
| Claude Code | On regresoempresarial.com: in July, Base44's agent; in August, Antigravity to connect GitHub with Base44, and from August on, Claude Code. Also the code of this site, since September, and of Cayu: I specify and test it, and Claude Code writes it | Case 1: technical visibility |
| Cayu, the tool I designed | I read Search Console through its API and computed difficulty over the real top 10. It was for the second keyword research of regresoempresarial.com (October 2026) | Case 2: architecture and content |
What I deliver, and where you can see it today
A report with finding, impact, proof and recommendation: there's an excerpt on the technical SEO audit page.
A baseline with dates and instruments, saved before changing anything: the one from Sep 28, 2026 is in the project log.
A log of what is still pending and why: it closes every case study, under “Next steps”.
The full case studies, with their evidence, are in the portfolio. How to run these checks yourself is in the SEO guides, and what I find when auditing, on the technical SEO blog.