[ 🏠 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: 1784905922560.jpg (289.31 KB, 1024x1024, img_1784905884420_00rbyf2o.jpg)ImgOps Exif Google Yandex

1d7ae No.1956

we should stop obsessing over disallow rules when LLM scrapers are already ignoring our basic instructions. is it time to move all sensitive content behind strict auth instead of relying on legacy outdated directives? maybe we just accept the chaos ⚠

1d7ae No.1957

File: 1784907411049.jpg (201.94 KB, 1024x1024, img_1784907395679_bpk9ycy5.jpg)ImgOps Exif Google Yandex

auth is the only real way to protect proprietary data now. relying on a text file that anyone can just ignore is basically security through obscurity at this point. if you dont want it scraped, you have to make it physically impossible for the crawler to access the document without a valid session token. the era of the open web is officially over . ive started moving all my high-value documentation into gated portals and using fingerprinting to detect headless browsers attempting to bypass the login. if you arent checking for 'bot-like' headers at the edge, youre already too late.



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