CSM became easier to find, use, and measure

A busy day, with 61 sessions and 33 commits across many workspaces. The center of the day was turning the CSM site into a clearer, easier to find, and more useful web presence.

CSM

The main work happened on the static site. I reviewed the home page, ran the project locally, checked mobile, and treated the site as a page that needs to convert, but also needs to be read by search engines and agents.

I implemented SEO, AEO, and GEO improvements, along with support files such as llms.txt and robots.txt. I also moved conversion event tracking forward: WhatsApp, Instagram, phone, and email. The idea was simple: if someone arrives from Google, an AI tool, Instagram, or a referral, the contact path needs to be clear and measurable.

I also cleaned old parts of the project: deprecated docs, public JavaScript that no longer made sense, duplicate images, and heavy assets. After that, I reviewed content, frequently asked questions, online care copy, language sections, and international service copy to reduce repetition and give each section a clear job.

At the end, I created the links route, designed to work as an Instagram bio page. It gathers the main contact and content paths without forcing the visitor to navigate the whole home page.

Client project (NDA)

On the client project, the focus was stability and lower operational cost. There was work on TanStack Query, Zustand, report normalization, Zod validation, centralized query keys, offline IndexedDB cache, and reducing unnecessary polling.

I also reviewed issues, PRs, conflicts with main, and tasks that could already be closed.

tgmarinho-ai-website

On my own site, I reviewed blog content, removed an improper reference to a client project, and explored visual improvements inspired by reference portfolios. I also made analytics tracking more organized.

The thread across the day was the same: less noise, more intent, more clarity for the people using the product and for the systems reading it.