Build Journal
Local SEO Enhancements: FAQ Section & Humanization Features — September 26, 2026
I added a new FAQ section, improved humanization features, and optimized keyword processing for local SEO. Here's what I learned building solo with AI.
What shipped
- New FAQ Section — Added an engaging FAQ section in a colored callout box.
- Humanization Features — Implemented humanized flags for worker data.
- Mass Keyword Processing — Optimized skipKeywordApi for 232K scale keyword handling.
Today, I focused on enhancing my local SEO capabilities. Specifically, I shipped three significant features: a new FAQ section in a colored callout box, an incremental humanization of worker data, and a skipKeywordApi for handling mass batch keyword processing. These advancements are aimed at making the platform more engaging and efficient for users, particularly in local markets.
The FAQ section was a feature I had been contemplating for a while. It was essential to provide users with immediate answers to common questions, which can significantly boost user engagement and retention. I spent about 20 minutes designing the callout box to ensure it matched the primary tint of the ClaimBusinessCTA, creating a visually cohesive experience. It was gratifying to see this feature come together quickly, as it added value without the usual complexities of more extensive changes.
Next, I tackled the humanization aspect of worker data. The goal here was to make the generated worker bundles feel more relatable and authentic. I implemented a humanized flag that allows the platform to tag these bundles appropriately. This took a bit longer, around 30 minutes, as I had to ensure that the humanization didn’t compromise the data's integrity. I learned that even small changes can have a ripple effect on how data is perceived by users, and I was careful not to lose the essence of what the data represents while making it more engaging.
The final feature I worked on was the skipKeywordApi for processing mass batches of keywords at scale. This was a crucial improvement, allowing the platform to handle base keywords without autocomplete suggestions at a staggering scale of 232K. I spent about 10 minutes on this, but it demanded a lot of mental effort to ensure that everything would work seamlessly. The challenge was in managing the sheer volume of data without bogging down performance. After some initial testing, I was pleased to find that the optimization worked well and would facilitate smoother operations for users looking to scale their local SEO efforts.
Reflecting on today’s work, I felt a mix of pride and frustration. It’s empowering to see tangible progress in areas that directly impact user experience, but I also recognized the constant battle against bugs and the mental load of maintaining focus while working solo. With Claude Code as my partner in VS Code, I’ve realized how much I can achieve without needing to hire additional hands. This solo journey is intense, but every feature I ship brings me one step closer to the vision of a one-man-show company with a billion-dollar valuation.
As I wrap up this session, I can’t help but feel optimistic about the direction things are heading. The local SEO enhancements are not just about adding features; they’re about creating a platform that genuinely serves its users. Each improvement is a building block toward making the agentic web more accessible and effective. I’m excited to see how these changes will resonate with users and how they will help in scaling the platform’s reach. Tomorrow, I plan to dive deeper into user feedback to better understand how these features are being received. Building in public has its challenges, but it also offers invaluable insights that can steer my development efforts in the right direction.