Astro SEO Audit
An open-source CLI I built to check the final HTML an Astro site ships, find site-wide SEO issues, and catch real errors before deployment.
↗I work on SEO, build websites and small web tools, and write about what I learn while making them.
Most of it starts with me wondering, “could I make this better?” Then I disappear into it for a while.
An open-source CLI I built to check the final HTML an Astro site ships, find site-wide SEO issues, and catch real errors before deployment.
↗It started as one random-letter wheel and somehow turned into six small browser tools for games, classrooms, quick decisions, and wonderfully pointless fun.
↗A WordPress theme I’m building around a calmer, cleaner reading experience. It’s in beta while I keep refining the details.
↗My place for projects, experiments, and thoughts that are too long for a social post. Also the site I keep redesigning because apparently I enjoy that.
↗I write when I learn something worth remembering—or when an opinion refuses to leave me alone.
I set up a chief of staff, designer, engineer, architect, QA reviewer and SEO lead on one VPS. Here is what they built, what broke, and what I learned.
Astro SEO Audit began as a simple pre-publish check. It turned into an open-source CLI that reads the HTML Astro actually ships and explains what needs fixing.
I have a blog now, so obviously I had to use it to talk about One Piece, break weeks, Dragon looking east, and why I love this ridiculous pirate story.
What fixing a stubborn web wheel taught me about animation, anticipation, readable labels, and the difference between working code and a good interaction.
SEO charts need context. After cleaning spam URLs from a site, falling impressions can be evidence of recovery rather than failure.
If I’m not building something, I’m probably watching One Piece, drinking chai, or telling myself I’ll stop after one more chapter.