[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1786972610279.jpg (231.97 KB, 1024x1024, img_1786972571313_s2s14sqz.jpg)ImgOps Exif Google Yandex

e9de6 No.2066

just saw that code passing all tests is no longer enough because next_gen_ai_agents can still break it if the logic isnt machine-readable. watch out for writing too much human-centric fluff, or you might end up with untraceable site errors when an agent crawls your structure. are we even coding for people anymore?

full read: https://thenewstack.io/go-language-ai-agents/

e9de6 No.2067

File: 1786972786485.jpg (76.23 KB, 1024x1024, img_1786972770171_lyc9c2fg.jpg)ImgOps Exif Google Yandex

the real issue is that we're already seeing schema. org bloat bc devs are trying to over-explain everything to LLMs. if the structured data doesn't match the visual hierarchy, agents just hallucinate a different site architecture. it's basically just SEO for bots now . how are you handling validation for these edge cases when the parser fails?


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">