What is BloggerSpot?

BloggerSpot is a personal website-building laboratory and build-in-public journal. I'm documenting experiments, website projects, blogging, SEO, AI-assisted development, and vibe coding — the things that work, the things that fail, and what I actually learn along the way.

Why I started it

I wanted a place to document the process honestly, not a polished after-the-fact summary. Most tutorials online show you the finished result. This site is closer to the actual notebook — including the errors, the wrong turns, and the moments something worked for reasons I didn't fully understand until later.

My background

This is the long version, because I think it actually matters — the gap isn't a gap I'm hiding, it's most of the story.

2009–2010 — Where it started

A teacher introduced me and one friend to SEO back in 2009. We were the only two students in the class who got genuinely interested. By 2010, right after graduating, we were already working as SEO optimizers — and doing well enough to place in real competitions: 2nd place in a local SEO contest, 4th place internationally.

2011–2013 — Real jobs, real detours

SEO work alone couldn't cover the bills, so from 2011 to 2012 I took a 9-to-5 job at SM City Iloilo as an RDU Forwarder. When the earnings still weren't enough, I moved to Manila hoping to land office work. I got hired on the spot for a web development–related role — surprising, since I'd only completed a 2-year ladderized computer science course, not a full degree. But I hit a real wall there: I'm not a programmer, and I never fully understood the logic behind coding. That's the actual reason I stopped trying to learn web development back then, even though building websites was something I genuinely wanted to do.

In 2013 I worked as a Sports Mapper — a job that put me close to systems built by real, hardcore developers and programmers. My advantage there was that I already understood websites, even without being able to build them myself.

2015–2017 — The client that proved it worked

In 2015, I took on my first personal SEO client — the biggest personal project I'd done up to that point. I got his site to the #1 spot on Google for the keyword he actually cared about, and it earned me a six-figure income. That result is the reason I don't consider myself a total newbie at this, whatever the gap since then might suggest.

It didn't continue past 2017. The competition got heavier, and running it solo while also working a full-time 9-to-5 as a Data Analyst became genuinely difficult to sustain.

2017–2025 — Crypto, the pandemic, and getting by

In 2017 I started studying and trading crypto — real wins, real losses, some of my most useful failures. The 2019 pandemic pushed everything toward work-from-home. By 2021–2022, with no steady work and no income, I leaned hard into play-to-earn gaming during its rise — farming in Mir4 and a few others, which functioned as real informal income during a period when there genuinely wasn't much else. In 2023 I worked as a personal driver, and by 2025 that turned into work as a tourist guide, then driver and tour guide together.

2026 — Now or never

This year, I'm broke, and I'm coming back to the thing I've genuinely wanted to do since 2009: build and rank websites. I don't know exactly how this turns out. But between real SEO results I've already proven once, and AI-assisted development finally closing the gap that stopped me back in Manila — understanding the logic well enough to actually ship something — this felt like the moment to try again, seriously, in public, starting with this site.

What's changed is that AI-assisted development and "vibe coding" have made it possible to actually build real, working websites — not just theoretically learn to program, but ship something live, test it, and understand it well enough to explain it to someone else.

Why AI-assisted development?

AI didn't remove the need to understand what's happening — it changed what's possible to attempt in the first place. I still hit real walls: terminal confusion, Git errors, Cloudflare routing conflicts, SEO indexing issues. AI helped me get code written and problems diagnosed, but understanding why something broke, and documenting it, is still work I do myself. That's what this site is for.

What you'll find here

• Experiments — real tests, with real results, including the ones that failed
• Guides — step-by-step breakdowns of specific problems and how I solved them
• Build logs — the actual, unpolished process of building projects
• Website projects — case studies of things I've actually shipped
• SEO lessons — from someone who's tracked real rankings since 2010
• Honest failures — not everything works on the first try, and that's part of the record

Current stack

• Astro
• GitHub
• Cloudflare Pages
• AI-assisted development

I'm not a professional software engineer, and I'm not pretending to be one. The lack of traditional programming experience is part of what makes this documentation useful to someone else starting from the same place I did.