SEO Portals & Map Enhancements for Agentic Web — May 12, 2026

I spent my day implementing improvements for the SEO portals and maps features on the agentic web platform. I shipped 5 new features and fixed 4 bugs during a long 17 hour shift. The improvements made it a lot easier for users to interact with the platform while eliminating potential friction points.

One of the features that I am the most proud of is allowing SEO domains to view PortalDetail panels just like other standard portals. This means that users can view additional information including a favicon portrait, website URL, and a Claim CTA, with the call, vault, book, and share rows hidden. I also made sure that the cyan marker is maintained on the map in order to identify it. This improvement helps users quickly identify SEO domains.

I also had a lot of bugs to address. While implementing some features, I ran into a problem where the map camera wouldn’t update when a keyword or hashtag was resolved in the nav-search. The user was frustrated because the map did not move when the slide-over opened. I had to do a lot of debugging and figured out that I was only updating the detailMapCenter. I had to ensure that the camera would fly to the resolved portal coordinates and after a lot of back and forth, I was able to implement that successfully.

I shipped another big feature that shows SEO domains as cyan map markers, which have a slide-over detail panel. This panel has a 'Visit website' link that opens the same panel as a scanner row click, allowing users to preview the website within the app before they leave the app. This was an important feature to add for increasing user engagement and to make checking out different SEO domains easier.

To integrate SEO Sara API for syncing live domains into seo_sara_domains using a durable BackgroundJob, I had to do some domain syncing work in the SEO API. I set up a public API listing for domains, which is a requirement for the SEO functionality, however, I had some key scope challenges. My upstream key was too narrow so location and keywords were left pending. I've been working on this and I'm confident that once I finish this task, it will greatly enhance the platform.

I also did some important work to fix issues in the system. For example, I had to widen the enrichment status filter in the seo-sync module, because the upstream was sending mixed case status values like PENDING. I made this change to avoid losing track of important work because of soft upstream errors. I also widened the list-endpoint status filter in the SEO module to be more resilient to inconsistencies so the system is less rigid and more resilient to upstream errors.

I spent a considerable portion of my day developing tests from the ground up to validate the latest changes and improvements. Specifically, I wrote three additional pure-function tests, which encompass the embed-origin allowlist, SSRF allowlist, and isAppOriginRequest boundaries, leading to the addition of 65 test assertions. Furthermore, I revised the documentation to add instructions regarding how to provision Upstash and Sentry DSNs for new users. The focus I put on testing and documentation is justified as I continue to transform this one-man-show into a company with a billion-dollar valuation.

In general, today was filled with challenges and success and was, therefore, quite productive. Moments like this remind me of the true grind that is required to build something from scratch. The fact that I am working with AI is a huge advantage, but more than that, it's my vision and unwavering determination to create a top-quality product that is driving the rapid progress of this venture. I am looking forward to the new features and the improvements they will bring to users’ interactions with the agentic web platform. I am also looking forward to the new challenges I will meet head on.