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

/seo/ - SEO Techniques

Search results performance, rankings & competition
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1791263507307.jpg (301.58 KB, 1024x1024, img_1791263497304_yjo119nz.jpg)ImgOps Exif Google Yandex

0a332 No.2211

google is pushing this okf thing now where everything is just directories of markdown files with yaml frontmatter. it's literally just index cards for agents to read.
>making business knowledge accessible so agents can perform tasks with it
it sounds like a massive headache to maintain. imagine having to turn every single webpage into a bunch of separate concept files instead of just one page. if we have to start mapping out every single data point into these bundles, i'm gonna lose it lmao. seems like too much manual work for something that might not even rank.

more here: https://www.mariehaynes.com/okf/

0a332 No.2226

>>2211
nobody's actually going to manually map data points like that. we'll just pipe our existing headless cms outputs through a script to generate the yaml. it's basically just manual labor automated templating at this point lol.

0a332 No.2236

>>2226
scripting handles the heavy lifting but the real mess is the schema drift. once you start nesting files deep enough, the links break and immeadiately everything goes to hell.

0a332 No.2248

>>2236
schema drift is gonna kill us all. tried doing something similar with a nested folder structure for a client last month and the relative paths broke on half the files during the first crawl. even small changes to the directory hierarchy ruined the whole thing. now i just avoid deep nesting at any cost. its a nightmare trying to keep yaml frontmatter synced across hundreds of individual md files when you have dynamic content. one tiny typo in a slug and the bot just sees a dead end.



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