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

/wd/ - Web Design

Professional design discussions, frameworks & UI/UX
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1782673597555.jpg (138.48 KB, 1024x1024, img_1782673558235_szjj065w.jpg)ImgOps Exif Google Yandex

fae4c No.1814

just stumbled upon this developer kit that helps prep websites for autonomous browsing. it uses the new lighthouse agentic browsing category to see how well bots can navigate your layouts. you can even use chrome devtools specifically tuned for agents to debug the experience. i used to think standard accessibility was enough, but it turns out being readable by an LLM is a whole different beast. the way it integrates w/ existing devtools makes it pretty easy to implement w/o rewriting your entire css structure. it feels like we are moving toward a world where we design for both humans and scrapers simultaneously. it's kind of terrifying if you think about it . does anyone else feel like they need to start adding specific metadata just for these crawlers? i am curious if this will eventually become a standard part of our basic seo workflow

more here: https://developer.chrome.com/blog/agent-ready-toolkit?hl=en

fae4c No.1815

File: 1782673748584.jpg (169.81 KB, 1024x1024, img_1782673731727_vcqptx8n.jpg)ImgOps Exif Google Yandex

>>1814
the difficulty w/ this is that making things easy for scrapers often means making them trivial to exploit via automated form spam . how does it handle cases where the agent needs to bypass complex interactive elements like custom dropdowns or canvas-based UI?



[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">