About
A public notebook from an engineer learning SEO in the age of AI agents.
Why this exists
I am Edu, a software engineer with a broad background across front end, back end, full stack work, native mobile, set-top boxes, cloud, and security. The common thread is not a single stack. It is curiosity: the rush of finding a field I do not fully understand yet, building a mental model for it, and getting a little less wrong with each iteration.
SEO has always had that pull for me. It matters to anyone who builds for the web, but it is also obscure, changeable, and full of claims that are hard to separate from habit. I know the basics. This site is where I do the deeper work in public.
The angle
AI has changed software development quickly, and search is going through the same pressure. Pages are still read by people, but they are also read by crawlers, answer engines, and agentic systems deciding what to fetch, trust, summarise, or cite.
That is the part I want to understand: SEO from the position of a technical learner using AI heavily, testing tools as I find them, and turning the process itself into something useful for other people starting from a similar place.
What you will find here
This is a notebook, not a finished doctrine. Expect lessons learned, tools discovered, workflows adopted, experiments that were worth running, and the occasional negative result. Some pieces will use data and logs; some will simply explain a concept clearly enough that it becomes usable.
The aim is to stay practical and readable. I do not want every article to be a dense technical report. The useful thing is often the higher-level shape: what changed, what I tried, what helped, what failed, and what I would do differently next time.
What this is not
This is not daily SEO news, and it is not an agency blog. It may become a business one day, but that is not the point of the site right now. It is also not here to inflate every AI trend into a revolution. If something is genuinely picking up, I may write about it. The job is to make it clearer, not louder.
The name
I publish here under a first name. That keeps the public surface of this project focused on the work rather than on a searchable personal profile. It is a publishing preference, not a security model. How posts are sourced and corrected is set out in the editorial standards.