Build Journal
Agentic SEO Enhancements & Security Fixes — August 24, 2026
I focused on agentic SEO improvements, security enhancements, and significant bug fixes to elevate my platform's performance and user experience.
What shipped
- Enhanced agentic SEO — Added /llms-full.txt for improved portal access.
- Security improvements — Strengthened Content Security Policy and fixed endpoint vulnerabilities.
- Real 404 handling — Implemented a true 404 page for better SEO and user experience.
- Performance optimizations — Eliminated unnecessary cookies for improved caching.
- Authentication fix — Corrected API response for unauthenticated users.
Today, I set out to enhance the agentic SEO capabilities of my platform while addressing some critical security improvements. In a solid 5-hour session, I managed to ship 11 commits, including 10 features and improvements, plus one important fix that tackled a persistent bug. The work I completed today was crucial for optimizing user experience and ensuring the integrity of my web portal as I build toward my ambitious goal of a billion-dollar valuation.
The standout feature I shipped was the addition of the /llms-full.txt endpoint. This is a comprehensive public portal directory that provides a complete matrix of links, costs, and industry details in one fetch. Agents are increasingly probing this endpoint first, so it was essential to ensure that it is fully functional and informative. Co-authored with Claude, this feature will help streamline access to valuable information for users seeking insights into various portals.
On the security front, I made significant strides, particularly with the Content Security Policy (CSP) settings. I allowed static.cloudflareinsights.com within the script-src directive to ensure the integrity of the resources being loaded. The first-enforce-day console showed blocked scripts that were critical for real user monitoring, so this change was necessary to improve the platform's performance metrics. Additionally, I enforced a nonce-less baseline policy, which will help prevent unauthorized scripts from executing and enhance overall security.
Another critical fix was addressing the 404 error handling. Previously, any dead or mistyped URLs were being redirected to a robots-disallowed page, resulting in soft-404s that filled Google Search Console with noise. I implemented a real 404 page that delivers an accurate status, ensuring both users and crawlers receive the correct information when encountering a broken link. This change was long overdue and will help improve the site's SEO health by eliminating misleading signals.
In my relentless pursuit of optimization, I also tackled some performance issues related to the geo_portal_session cookie. The previous implementation marked every HTML response as uncacheable, which was an unnecessary strain on server resources. By stopping the minting of this cookie in middleware, I ensured that cached responses can be served efficiently, enhancing the overall speed of the platform.
I did encounter some challenges, particularly with the authentication flow. I found that the /api/auth/me endpoint was returning a 200 status with {user: null} instead of a 401 for unauthenticated users. This was generating red console errors for every signed-out visitor, which could lead to confusion about their session state. By correcting this to return a proper 401 status, I streamlined the user experience and eliminated unnecessary errors in the console.
Throughout this session, I was reminded of the advantages of using AI tools like Claude Code in VS Code. While many teams might opt for costly collaborative tools, my solo approach, paired with AI assistance, has allowed me to maintain focus on building the agentic web. Each feature I ship brings me closer to my vision of a one-man-show company that leverages the power of spatial AI and agentic SEO to provide unparalleled service.
In summary, today was a productive day filled with essential improvements and fixes. The enhancements to agentic SEO, security measures, and bug fixes are all steps toward creating a robust platform that can stand the test of time. As I continue to build in public, I remain focused on the ambitious goal of reaching a billion-dollar valuation while delivering a top-tier user experience. Every commit is a building block, and I’m excited to see where this journey leads.