Agentic Web AEO Enhancements & 404 Fixes — August 24, 2026

Today, I set out to enhance the agentic web platform's AEO capabilities and address some lingering 404 errors that had been a thorn in my side. In a focused 5-hour session, I managed to ship ten features and improvements, alongside one crucial fix, all aimed at making the platform more robust and user-friendly.

The first major feature I tackled was the addition of the expanded llmstxt.org variant, accessible at /llms-full.txt. This directory now includes a complete public portal directory along with a full cost/metro/industry URL matrix. Agents often probe /llms-full.txt first, so it was essential to ensure that this resource was comprehensive and linked properly from /llms.txt. I realized that the usage patterns were shifting, and it was crucial to adapt the platform to meet these evolving needs.

Next, I turned my attention to the content security policy (CSP). I allowed scripts from static.cloudflareinsights.com and the Jitsi host, which was necessary for the front-end to function without blocking essential scripts. The first-enforce-day console showed that both had been previously blocked, so I took the time to ensure that my security settings did not inadvertently hinder performance.

In an effort to improve SEO, I stopped stamping lastmod=now on static routes. This change was significant; it allowed the evergreen routes to omit lastModified honestly and prevented Google from misinterpreting the freshness of content. The last thing I wanted was for Google to distrust my core content because of unnecessary timestamps, especially since I have monthly refreshes for cost guides and changelog commit dates.

One of the fixes that took me longer than expected was creating a real 404 page with a genuine 404 status. Previously, a redirect-to-map catch-all had turned every dead or mistyped URL into a soft-404, which not only fed Google Search Console noise but also created a frustrating experience for users. Now, with a proper 404 page, users are directed to a helpful map and home fork, while crawlers receive the honest status they deserve.

I also made several security and performance optimizations. I turned off the poweredByHeader to eliminate any framework fingerprints, which is a small but essential step in maintaining security. Additionally, I adjusted caching for static assets to avoid unnecessary re-fetching. A hero image that was being cached every four hours for no reason has now been optimized for better performance. These small tweaks may seem trivial, but they collectively contribute to the overall efficiency of the platform, making it more responsive and user-friendly.

A significant issue I encountered involved the live-balance pill on the signed-in admin. Previously, the endpoint was exposed to every anonymous browser, resulting in a 403 error that cluttered the console. I gated this endpoint, ensuring that only signed-in users could access it, maintaining a clean and secure experience for all users.

Lastly, I fixed an authentication issue where the API was responding with a 200 status and a user:null object instead of a proper 401 when the user was not authenticated. This change was critical because the AuthProvider probes on every page load, leading to red console errors for every signed-out visitor. By making this adjustment, I not only improved the developer experience but also ensured that the platform provides a clear signal regarding user authentication.

Reflecting on the day’s work, I’m proud of the progress made, but it was certainly not without its challenges. The time spent debugging the 404 issues and refining the CSP settings ate into my day more than I anticipated. However, these hurdles provide valuable lessons in the solo development journey. They remind me that even when working with AI tools like Claude Code in VS Code, there are still complexities that require a human touch to navigate.

As I continue to build this one-man-show towards a billion-dollar valuation, each of these enhancements and fixes contributes to a more robust foundation. With each commit, I'm not just shipping features; I'm strategically shaping the agentic web platform into a powerful tool for users. The road ahead is long, but today's achievements mark another step forward in this ambitious journey.