Blog
Notes on web development, teaching, and building in public.
-
I counted every change an AI agent made to a real Webflow site. There was no middle ground.
I gave Claude access to a real Webflow project and asked it to do 106 specific things. It got 92 right on the first try. But not one of the other 14 came back half-finished — and that turned out to be the more useful finding. Here is what it did cleanly, what it could not do at all, and the two things I got wrong along the way.
-
Google rejected 31 of my videos and told me why. The reason was wrong.
Search Console said 31 videos were not indexed because "the video is not on a watch page". That sounded exactly right — none of my pages has a player. So I compared the 31 rejected pages against the 115 accepted ones, and they were identical on every attribute I could measure. Here is what the numbers actually say, the explanation I think is true, and the test that would prove me wrong.
-
Nothing was broken. The link between my two homepages had never worked.
Search Console told me 228 of my 254 pages were indexed, which sounded like good news. Six of the rest said "page with redirect", and following them found one missing slash — which had quietly stopped Google from ever pairing my English and Italian homepages, for thirty-three days. Here is why some defects have no symptom at all, and why the only witness lives outside your project.
-
Every check passed. A lot of it was broken.
I translated forty pages of help documentation into eight more languages, and every check came back green — the build, the schema validator, the label checker. A placeholder that deleted itself, bold that stopped being bold in Japanese, and a report with a hallucinated row sitting next to a missing real one. Here is why a green check answers its own question, not yours.
-
Three kinds of AI crawler, and the one that decides whether you get credited
Anthropic's crawler read all 42 pages of my knowledge base in about an hour. Claude then answered a question about it and linked my old domain. Being read and being credited are not the same thing — and the crawler that decides is the middle one nobody looks at.
-
Nine wrong names shipped. A check I wrote afterwards stopped eight more.
I published nine identifiers that did not exist — attribute prefixes, a CSS variable, an ARIA value — reconstructed from my own spoken tutorials. Here is how each one sounded right, and the build check that now fails if a page carries a name nobody copied from the real project.
-
AI assistants already recommend my work. They just don't link it.
Before announcing my new GSAP knowledge base, I measured whether AI assistants cite me at all: ten questions, four assistants, 31 points out of 80. The knowledge base scored zero — and the real finding was something else entirely.
-
I was a guest on Webflow & Friends — here's what we talked about
I joined Janne Parri on the Webflow & Friends podcast to talk about building a career around Webflow — consistency, communities, and where the platform is heading. Here are the takeaways.
-
Starting a Journey: Why It's Tough, but Worth It
Why the spark fades so fast when we start something new, why every journey is walked alone — and why it is still worth taking the first step.
-
Change Doesn't Need a Plan: From the Comfort Zone to Tokyo
How I went from a stuck 9-to-5 developer in northern Italy to helping run a company in Tokyo — and why the first step matters more than the plan.