CADE Media Localization & SEOLocal Fixes — October 3, 2026

Today, I set out to enhance the CADE media localization process and tackle some lingering issues in SEOLocal. What shipped? A feature to serve apex resources and several critical fixes to streamline our Content Engine migration and improve the handling of media references. It was a long haul—spanning about 21 hours—filled with both breakthroughs and frustrating bugs.

The first major task was to ensure that CADE correctly localizes migrated images. This involved fixing the media update to return source URLs, which was crucial for linking the right images in our posts. I found that the Content Engine migration was uploading each source image but failing to rewrite the post body correctly; instead, it was still referencing the old imagehosting.space URLs. This was a showstopper, as our apex posts were left incomplete with missing images. After digging into the API calls, I implemented a fix that now records the Content-Disposition filename during uploads and allows for retrieving media by either filename or ID. It was a tedious process, but VHC passed because it didn’t encounter the media-search flow that had been breaking things.

Next on my list was addressing the SEOLocal stylesheet issue. The premium stylesheet was being served from a different origin, which caused the apex service pages to carry the imagehosting.space references. This was another blocker that I needed to clear. By proxying the stylesheet via our API, I ensured that all apex service pages would now serve the CSS correctly without any external dependencies. This fix also cleared the Content Engine Finish image gate on the nine pillar pages, which had been a significant pain point.

While implementing these fixes, I also added a new feature to serve apex resources directly from the CADE. This was necessary because the Content Engine Finish was returning 404 errors for every resource slug we tried to access. I realized that the stored content was intact, but there was no proper route to serve it. By creating this new endpoint, I could mirror the blog structure, allowing users to access the resources seamlessly. It felt good to finally see the apex resources functioning as intended, even if I had to keep the base /resources route set to 410 for now.

As a solo builder, I often find myself battling with the limitations of my own time and capabilities. I could have opted for a collaborative effort or even paid for premium tools like Lovable or Cursor to ease my workload. Instead, I leaned heavily on Claude Code in VS Code. While it is a grind, I’m committed to proving that I can build this agentic web platform solo, one feature and fix at a time. Each commit, each bug resolved, brings me closer to my ultimate goal of establishing a one-man-show company with a billion-dollar valuation.

Reflecting on the day, I’m proud of the progress made, but it wasn’t without its challenges. The API issues caused significant delays, and I spent hours debugging the media localization process. However, every setback taught me valuable lessons about how the various components of our platform interact. I learned that attention to detail is crucial, especially when dealing with media references across different origins.

Overall, today was a mix of triumph and frustration, typical of the solo builder's journey. I shipped a feature that enhances our spatial AI portal’s usability and tackled some persistent bugs that have been haunting me for weeks. With every line of code, I am not just building a platform; I am crafting a vision for the future of agentic SEO and spatial AI. As I continue down this path, I remain determined to make hashtag.org a leader in this space, even if it means long days and sleepless nights.