{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/115fd267532a4c3f812b5d763d8f451c\" frameborder=\"0\" width=\"1498\" height=\"1123\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1123,"width":1498,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1123,"thumbnail_width":1498,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/115fd267532a4c3f812b5d763d8f451c-85c6069c16c2ff95.gif","duration":392.708,"title":"Migrating RyanTurner.com to Next.js for Improved SEO and AI Accessibility","description":"In this video, I discuss a significant issue with my website, RyanTurner.com, where Gemini struggles to extract text, unlike my other sites. I’m in the process of migrating to Next.js, which involves substantial changes to routes and logic, and I’ve created blueprints to manage this transition effectively. Currently, I have over 35 sub-agents working on the migration, analyzing tasks and dependencies to ensure everything runs smoothly. My goal is to have this migration completed efficiently so that Gemini can pick up new content seamlessly. If your site isn't AI-friendly, I strongly recommend switching technologies to avoid being left behind."}