Build Journal
CADE Media Routing & Author Profiles for Agentic SEO — June 29, 2026
I implemented CADE media routing and enhanced author profiles for agentic SEO. Discover the challenges I faced and the lessons learned in this solo build.
What shipped
- CADE Media Routing — New public image route for CADE media ensures accessible profile images.
- Enhanced Author Profiles — Public profile pages now feature names, bios, and social media links.
- Schema Verification Fix — Aligned CADE schema with real cade-seo plugin for accurate validation.
- Dynamic Footer Links — Footer now displays FAQ and Blog links upon CADE subscription detection.
- Multi-Tenant Support — Implemented domain-aware routing for improved CADE functionality.
Today, I set out to enhance the CADE platform by implementing media routing and improving author profiles, aiming to bolster our agentic SEO capabilities. I successfully shipped 38 commits over an exhausting 22-hour marathon, focusing on refining the user experience and ensuring seamless content delivery. The key features delivered include a new public image route for CADE media, enhanced author profile pages, and multi-tenant support for our WordPress emulation.
One of the primary hurdles I faced was the 404 errors caused by the previous media routing configuration. The single-segment route for serving images didn’t accommodate the CADE media subpath, which meant that uploaded profile images were inaccessible. To resolve this, I created a new API route at /api/files/cade-media/[name] that now serves these images correctly. I also updated Robert Bibb’s author headshot using his LinkedIn photo, ensuring a more polished presentation for our authors. This was a straightforward fix, but it took some time to pinpoint the routing issue amidst other ongoing developments.
Another significant feature I implemented was the enhancement of author profiles. The new public profile pages at /profiles/[slug] now showcase the authors’ names, headlines, bios, and social media links, complete with Person/ProfilePage JSON-LD for better discoverability by search engines and AI systems. This involved a lot of careful work to ensure the JSON-LD was injected correctly, and I had to emulate WordPress user creation to manage the new profiles effectively.
The most challenging part of today’s work involved the CADE schema verification process. I had to ensure that the schema matched the real cade-seo plugin's contract exactly. Initially, my echoes and injections were not consistent, leading to verification failures. After some deep debugging, I managed to fix the issue by ensuring that the CADE plugin health checks and schema injections returned the correct payloads. This was a classic case of needing to align my logic with the existing plugin structure, which took longer than I anticipated. It taught me the importance of thorough testing and validation against external dependencies.
In addition to these features, I made sure to reserve key segments like /blog and /faq, which are crucial for content discovery. This was part of a broader strategy to enhance our platform’s SEO capabilities, ensuring that users can access relevant content without unnecessary redirects. I also adjusted the footer to show links to the FAQ and Blog sections once a CADE subscription is detected, adding to the user experience.
The grind of the day had its ups and downs. The satisfaction of shipping new features was tempered by the frustrations of debugging and the endless cycle of testing and refining. But that’s part of the journey of building something impactful alone, especially with AI as my assistant. Each challenge faced is a step closer to that one-man-show vision I have for the billion-dollar valuation of this project.
Reflecting on today, I’m proud of the groundwork laid for our agentic web strategy. The enhancements to CADE’s media routing and author profiles are not just about functionality; they are about creating a richer, more engaging experience for users while optimizing for search engines. As I continue to build this platform, I’m learning to balance the technical demands with the broader vision, and I’m excited to see how these changes will resonate with our users and the wider agentic web community.