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

/tool/ - Tools & Resources

Software reviews, plugins & productivity tools
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1790142913730.png (312.3 KB, 1938x417, img_1790142904083_hwbqaibx.png)ImgOps Google Yandex

be5aa No.2227

Using custom JS to pull markdown directly during a crawl is such a time saver for cleaning up RAG pipelines. It beats manually stripping all those bloated div tags and tracking pixels when you're trying to save on token costs. I wonder if that python script for the xlsx export handles large sites without crashing though, because my last big scrape was a nightmare.

full read: https://www.screamingfrog.co.uk/blog/generate-markdown-at-scale/

be5aa No.2244

File: 1790517711513.jpg (211.65 KB, 1024x1024, img_1790517696241_l49hccp9.jpg)ImgOps Exif Google Yandex

>>2227
>it beats manually stripping all those bloated div tags and tracking pixels when you're trying to save on token costs

the tokens saved from getting rid of the useless junk scripts is massive lmao but that python script definitely chokes on anything over 10k pages if u don't chunk the output.

be5aa No.2246

>>2244
>the tokens saved from getting rid of the useless junk scripts is massive lmao
not really that much difference for the model if you're just cleaning the html first. most of the cost bloat comes from the nested div hell and redundant nav menus, not the actual script tags themselves.



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